Comments on: How to trace JOB?

By: jackli

jackli — Wed, 21 Mar 2012 07:13:47 +0000

If you can find the output job log by wrkusrjob,use the joblog to trace.
But if no splf,you can trace the job,I thind you should ask user to provide more
information,such as which menu he was using,what data is unmatch by the error…and so on.
Follow the Programm according the using menu to find the crashed reason.
Jackli

By: deepu9321

deepu9321 — Fri, 09 Dec 2011 08:13:21 +0000

Thanks for Clarifying Tom.
Didnt had look at the Option ‘*INTERACT’. Clear now.

Pradeep.

By: tomliotta

tomliotta — Thu, 08 Dec 2011 20:57:39 +0000

it will be fine for verifying the Jobs Submitted by user(Batch Jobs).

The WRKUSRJOB command will cover all jobs under a user including interactive jobs; the JOBTYPE() parameter can choose which type. The WRKSBMJOB is a different command that handles submitted jobs by a user, and includes jobs that run under a different user profile.

Tom

By: deepu9321

deepu9321 — Thu, 08 Dec 2011 10:49:53 +0000

Hi Tom,

it will be fine for verifying the Jobs Submitted by user(Batch Jobs).
How this can be achieved if the error occured in an Interactive Job?

Pradeep.

By: tomliotta

tomliotta — Thu, 08 Dec 2011 07:20:57 +0000

Assuming the user’s ID is USERID, the only real choice is to run a command like this:

WRKUSRJOB USER(USERID) STATUS(*OUTQ)

If the user’s job left a joblog on an outq, the job will be in the list from the command. Find the job in the list and look at its output files.

If the user’s jobs don’t spool their joblogs, then there is nothing you can do. If you don’t create joblog output, you are telling the system not to keep a record of what happened.

Tom