You can define a z/OS-Manual job to create dependencies on z/OS jobs that are submitted outside the scheduling manager, such as a job that is submitted manually by a user. After the manually submitted job completes, the server releases the successors of the Manual job.
Note: To run these jobs, your system requires CA WA Agent for z/OS.
If more than one generation of the Application is active when a manually submitted job completes, the server posts the Manual job as complete in all active Applications.
To define a z/OS-Manual job
The Application appears in the workspace.
The z/OS-Manual icon appears on the Application workspace view.
The Basic page of the z/OS-Manual dialog opens.
Defines the name of the job submitted outside CA Workload Automation DE.
Specifies the name of the agent that monitors the manually submitted job.
Specifies the z/OS user ID that owns the job on z/OS.
Defines the authorization string the server uses to post the correct job. The server posts the Manual job complete when the manually submitted job runs under the corresponding user ID.
Note: Contact your agent administrator to confirm whether the agent checks the authorization string. Depending on the scenario, the action to take differs as follows:
Defines the number of hours and minutes, in the format hhh:mm, that the agent does a backward search for a manually submitted job.
Limits: 546 hours
Example: 000:30
The z/OS-Manual job is defined.
Example: Post z/OS Manual Job Complete Based on the User ID
Suppose that you want to post a z/OS Manual job complete when the manually submitted job ABC runs under CYBER. The ZOS1 agent monitors job ABC.
To post z/OS Manual job complete based on the user ID
|
Copyright © 2011 CA.
All rights reserved.
|
|