Contents
The CA VM:Batch/CA VM:Schedule interface combines the powerful batch processing capabilities of CA VM:Batch with the flexibility of CA VM:Schedule scheduling. You can now run batch jobs that are only eligible to run during specific time periods, or jobs that are run repeatedly on a regular schedule. You can also cancel one or more runs of a job, change scheduling parameters after a job has been submitted, run a job in addition to its scheduled runs, and display information about all types of scheduled tasks at once.
How the Interface Works
- CA VM:Batch has a SCHEDULE option that passes a string of CA VM:Schedule scheduling options to the CA VM:Schedule service virtual machine.
- CA VM:Schedule checks the options for syntax. If any options have incorrect syntax, CA VM:Schedule will issue an error message and the job submission or change is halted.
- Once the scheduling syntax is correct, CA VM:Schedule creates a BATCH request for that user's CA VM:Batch job. This request runs on the CA VM:Schedule service virtual machine (not your user ID) and is named BATnnnn, where nnnn is the unique jobid designated by CA VM:Batch.
- The BATCH request will run on the CA VM:Schedule service virtual machine at the requested times. The BATCH request issues a CA VM:Batch READY command for the waiting CA VM:Batch job.
- The CA VM:Schedule database is updated with the status of the CA VM:Batch job.
- After the CA VM:Batch job has successfully initiated, the CA VM:Schedule request is considered completed.
- When the next scheduled run time arises, the process repeats itself.
- CA VM:Schedule repeats the job for the scheduled number of times and then ends the job and removes it from the system.
Restrictions and Requirements
If CA VM:Schedule is not available, the SUBMIT, CHANGE, and STATUS WHEN commands will fail. Repeat the failed command when CA VM:Schedule is available.
If CA VM:Batch is not available when CA VM:Schedule tries to start a job, the READY command will fail and be retried.
Recommendations
- Use the CA VM:Batch Staging Facility when using the CA VM:Batch/CA VM:Schedule interface. If users have scheduled CA VM:Batch jobs, the files associated with the user's jobs can be in the system for a long time. The Staging Facility ensures that these job files are stored on disk, rather than in spool file space.
- Give SKIPPASS authorization to all CA VM:Schedule users who will be using the interface. SKIPPASS authorization will prevent users from being prompted for their LOGON passwords when accessing CA VM:Schedule screen through CA VM:Batch.
- Give NOPASS authority to any local CA VM:Schedule users able to update other users' scheduling options.
Implementation
- Log on to VMSCHED.
- Enter the END command to shut down VMSCHED.
- Use XEDIT to edit the VMSCHED CONFIG file.
- Make sure there is a PRODUCT VMBATCH VMBATCH record in the VMSCHED CONFIG file. This configuration file record provides CA VM:Schedule with the CA VM:Batch service virtual machine user ID. This record activates the CA VM:Batch side of the interface.
- Make sure there is an AUTHORIZ BATCH * record in the VMSCHED CONFIG file. This record allows users on your system the ability to make use of this interface. Users not authorized for BATCH will not be allowed access to the CA VM:Batch/CA VM:Schedule interface.
- Save your configuration file changes.
- Enter the PROFILE command to restart VMSCHED.
- Log on to VMBATCH.
- Enter the END command to shut down VMBATCH.
- XEDIT the VMBATCH CONFIG file.
- Make sure there is a PRODUCT VMSCHEDULE VMSCHED record in the VMBATCH CONFIG file. This configuration file record provides CA VM:Batch with the CA VM:Schedule service virtual machine userid. This record activates the CA VM:Schedule side of the interface.
- Save your configuration file changes.
- Enter the PROFILE command to restart VMBATCH.