Hi,
Normally you should see an error message in the QSYSOPR message queue and the job should have created a joblog spooled file.
Regards,
Martin Gilbert.
=============================================================
That depends on what you mean by "failed". If it means it encountered an error condition and ended abnormally from an *ESCAPE message, it will be very different from a job that 'handled' a problem and ended itself normally.
Without being told what failures are involved, we can't guess how to recognize a failure.
Please describe some example conditions and we can provide more detailed replies.
Tom
Last Wiki Answer Submitted: April 23, 2010 7:26 am by Gilly40023,625 pts.
If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
You can always do a WRKJOB JOB(jobname). This will pull up several if the job has been run multiple times and you can look at the different dates to see the job log for each to find where the job failed.
WRKJOB also lets you see the spooled files for the job, so if the job has created a joblog spooled file and it’s still in the system then you can still see the joblog.
Hello,
You can always do a WRKJOB JOB(jobname). This will pull up several if the job has been run multiple times and you can look at the different dates to see the job log for each to find where the job failed.
Teresa
hi,
WRKJOB gives the joblog only if the job is *ACTIVE. If the job is already ended with error, we can see the error message in QSYSOPR messages.
Regards
Reddy
Hi,
WRKJOB also lets you see the spooled files for the job, so if the job has created a joblog spooled file and it’s still in the system then you can still see the joblog.
Regards,
Martin Gilbert.