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 Statewhoami foo.whoami.24 foo 06/26/2007 07:19:35 0:00:01 Completed
You can use the zos jobinfo 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 foo.whoami.24---------------------------- 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: <none> Submit Time: 06/26/2007 07:19:35 Delayed Start: n/a Start Time: 06/26/2007 07:19:35 End Time: 06/26/2007 07:19:36 Elapsed Time: 0:00:01 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.5455/hr ($0.5455/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 logged in with ID: user_foo_4900 (comms ok)Launching 1 joblets for user 'foo'[foobar] cmd=whoami[foobar] root[foobar] result=0Agent ID: user_foo_4900 (comms ok) logged out.
If you want to use the ZENworks Orchestrator 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 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 console picks up the job activity and makes it available at the console.
Your data center might have an individual whose main function is to regularly schedule and run jobs on data center resources. That person, the Job Manager or Orchestrator User, has an graphical interface called the ZENworks Orchestrator User Portal where he or she can do their work. This section introduces the User Portal and how you can verify at the portal that a job has run.
On any machine with a Web browser, enter the following URL:
(The default port is 80, unless you have ZENworks Monitoring installed.) When you enter the URL, the User Portal is displayed in the browser.
Verify that the job you ran is displayed in the history of the User Portal.
Click thelink in the column of the job history to open the job log.
You now have a basic understanding of the User Portal and how to use it to verify that a job has run. As the last experiment in the walkthrough for ZENworks Orchestrator, you can use the zosadmin command line to gather information about your system. For more information, see Section 5.9, Walkthrough: Use the zosadmin Command to Gather Information.