Automation when a job ends
The Automation component uses this information in the following ways:
During a multiple-level automation request, the first automation level submits a job to take an action on the resource, and the next automation level begins when that job ends. For more information about multiple-level automation processing, see Multilevel automation (MLA) processing.
The information is used to ensure that an element is not processed by a job multiple times concurrently. The following examples illustrate this point.
Example 1
In this scenario, assume that the following command is issued against a pool every 30 minutes:
AUTOVOL POOL=pool,SOL=FRAGCHK
The FRAGCHK solution selects volumes that have a fragmentation index value that is greater than 500. Selected volumes are included in skeleton JCL job SRMJOB01, which submits a request to defragment the selected volume.
The first 30-minute interval elapses, and the command is issued. The solution runs against the volumes in the pool, selecting fragmented volumes and including them in skeleton JCL. When all volumes have been scanned, SRMJOB01 is submitted.
When the next 30-minute interval has elapsed, SRMJOB01 has not yet ended, but the command is executed again. The volumes in the pool are again included in the solution. However, any volumes that are included in the active SRMJOB01 are not included in this new occurrence of SRMJOB01.
Note
Because the job is processing volumes, the element is the volume name (volser), even though the AUTOVOL command specified a pool name.
Example 2
In this scenario, assume that the following command is issued every 60 minutes:
AUTODS POOL=poolName,SOL=DELNOPEN
The DELNOPEN solution checks for cataloged data sets that were allocated but never opened. When a data set is found that matches this condition, the data set name is included in job SRMJOB02 JCL to be deleted.
When the first 60-minute interval elapses, the command is issued. All data sets that are on volumes in the pool are included with the solution. Data sets that match the solution are selected and included in SRMJOB02, which is then saved to a data set or submitted.
When the next 60-minute interval elapses, SRMJOB02 has not yet ended, but the command is issued again. The data sets that are on volumes in the pool are processed against the solution. However, any data sets that are included in the active SRMJOB02 are not included in this new occurrence of SRMJOB02.
Note
You can use the AUTOSJOB view to see jobs that have been submitted by the Automation component and have not yet ended. However, if the submitted JCL contains multiple JOB statements, the AUTOSJOB view displays only one job.
Comments
Log in or register to comment.