After you have run the job, there are several ways to verify that it has run. This section explains those methods.
The following sections explain some of the zos commands that you can use to verify that a job has run and monitor some of the results of the job:
You can use the zos jobs command to list all of the jobs that have run while you have been logged in as a user. Running this command yields an output like this:
Job JobID User Started Elapsed State whoami userA.whoami.60 userA 12/24/2008 02:35:38 0:00:00 Completed
You can use the zos jobinfo -e job_name command to display information for a named job the last time it was run. Running this command yields an output like this:
Jobname/Parameters Attributes ------------------ ---------- whoami Desc: This is a demo example of enhanced exec numJoblets Desc: The number of joblets to schedule Type: Integer Default: 1 resource Desc: The resource id to run on Type: String Default: .*
You can use the zos status --detail command to display the status of the most recently run job. Running this command yields an output like this:
Job Status for userA.whoami.60 ------------------------------ State: Completed Resource Count: 0 (0 this job) Percent Complete: 100% Queue Pos: n/a Child Job Count: 0 (0 this job) Joblet Counts: 1 (0) (1 (0/0/1/0/0) this job) Instance Name: whoami Job Type: whoami Memo: Priority: medium Arguments: resource=tszen4_agent Submit Time: 12/24/2008 02:35:38 Delayed Start: n/a Start Time: 12/24/2008 02:35:38 End Time: 12/24/2008 02:35:39 Elapsed Time: 0:00:00 Queue Time: 0:00:00 Pause Time: 0:00:00 Total CPU Time: 0:00:00 (0:00:00 this job) Total GCycles: 0:00:00 (0:00:00 this job) Total Cost: $0.0002 ($0.0002 this job) Burn Rate: $0.8982/hr ($0.8982/hr this job) Termination Type: n/a Job Error: <none> Joblet Error Count: 0 (0 this job) Node Error Count: 0 (0 this job) Excluded Nodes: 0 (0 this job) Bad Provision Count: 0 (0 this job) Excluded Provisions: 0 (0 this job)
If you know the Job ID for a particular job that has run, you can use the zos log job_id --verbose command to display its detailed job log. Running this command yields an output like this:
Agent connected with ID: user_userA_64 (comms ok), Session ID: 52 Launching 1 joblets for user 'userA' [tszen4_agent] cmd=whoami [tszen4_agent] root [tszen4_agent] result=0 Agent ID: null logged out.
If you want to use the Orchestration Server Console to verify that the job has run, you can open theMonitor to look at the Job Log and see the result of the job being run.
In the Orchestration Console, clickin the main toolbar to open the Jobs Monitor view.
In the Jobs Monitor view, click thetab to open the Jobs page in the workspace panel.
In the whoami job.drop-down list box, select the user who ran the
Although there is much more you can learn about a job in the Jobs Monitor view, you can see by displaying a recent job that the Orchestration Console picks up the job activity and makes it available at the console.