Job routing and termination options
If you are running a sysplex, you can route jobs to other systems in the sysplex either explicitly by using the /*ROUTE JCL statement or implicitly by allowing MVS Work Load Manager.
You can also route jobs outside the sysplex if you have MainView AutoOPERATOR or another automated operations package.
For more information, see:
Job routing within the sysplex
When the following requirements are met, you can route jobs from the Automation component to any system in the sysplex and have Automation track when the jobs end:
- SVOS and the Automation component must be active on the remote system.
- The AUTO_XCFCOM=YES keyword must be specified in the SMMSYS member on both systems.
Sysplex XCF messaging services are used to communicate between the SVOS systems. You turn XCF services on and off by using the SMMSYS AUTO_XCFCOM keyword.
The following information is useful when you are setting up or tuning the XCF environment at your site:
- The Automation component defines one XCF group, MVSRMESA.
- The Automation component that is started on each system in the sysplex becomes a member of MVSRMESA; that is, the number of members in the group equals the number of systems where the Automation component is started.
- No permanent status recording occurs.
- XCF message errors can prevent the Automation component from determining when a submitted job ends.
- Message traffic starts immediately before an SVESA instance on any system in the sysplex that is submitting a batch job:
- The submitting, or local, system requests that other systems in the sysplex return a message whenever a job with the same name ends or when a job ends and the name is unknown. (Some messages indicating a job ending do not contain the name of the job).
- Each notification of a job ending generates one XCF message from the remote system to the local system.
- All messages are less than 256 bytes long.
- Message traffic stops when all jobs from the Automation component have ended.
Job routing outside the sysplex
Jobs that are submitted by the Automation component can be routed to systems outside the sysplex only if you use MainView AutoOPERATOR or another automated-operations package.
If you use MainView AutoOPERATOR or other automated-operations package, it must be set up to recognize messages that are issued when a job ends. These messages should be filtered on job name or mask name so that only jobs that are submitted by the Automation component are processed. When the end of a job is recognized, a JOBEND command needs to be routed to the SVOS on the system that submitted the job. The Automation component ignores JOBEND commands for jobs that are not active; therefore, this command can be routed to every system.
MainView AutoOPERATOR rule sets are discussed in Customizing-MainView-SRM-products.
For job routing to occur through MainView AutoOPERATOR, a MainView AutoOPERATOR address space must be executing on the destination system, with the following conditions:
- The subsystem IDs of the MainView AutoOPERATOR address spaces that are running within the sysplex must be unique.
- The MainView AutoOPERATOR subsystem on the destination system must be in active communication with the MainView AutoOPERATOR subsystem on the system that submitted the job.
- Rule set RULSRS01 must be customized and active within the MainView AutoOPERATOR address space on the system where the job executes.
The MainView AutoOPERATOR on the remote system must detect the end of the job and communicate with the MainView AutoOPERATOR on the local system. The local MainView AutoOPERATOR then must issue the JOBEND command to the SVOS address space. The JOBEND command specifies the name and number of the ending job. For more information about JOBEND, see JOBEND-command.