Hello When you submit the job, use the parameter LOG(4 0 *SECLVL), perhaps you need to change the job description for this. So this give you a job log in the QEZJOBLOG outq. You can see the process of your job. Regards
Hello When you submit the job, use the parameter LOG(4 0 *SECLVL), perhaps you need to change the job description for this. So this give you a job log in the QEZJOBLOG outq. You can see the process of your job. Regards
Hi, I run a job that passes through several programs (CL and RPG), and I noticed that this job slows down somewhere. I used the STRJOBTRC command to trace the steps of this job, but the spool generated with this command is not understable. Is there another way to know all the job steps (which shows the program names, the subroutines etc ...) ?
Mamadou, Use TRCJOB *ON, run the job and use TRCJOB *OFF - you can specify either *PRINT or *OUTFILE. If you use *OUTFILE, you can use a query over it to ignore all the IBM programs and things like that. I find it much easier than STRJOBTRC... Rory