Unicenter CA-Scheduler Job Management for VSE User Guide

Unicenter CA-Scheduler Job Management for VSE User Guide Unicenter CA-Scheduler Job Management for VSE User Guide

supportcontent.ca.com
from supportcontent.ca.com More from this publisher
03.03.2015 Views

7.5 Multiple CPU Considerations 7.5.1 Installation Considerations When installing Unicenter CA-Scheduler, you have to indicate that it is going to run in a multi-CPU environment which means that five things have to be done. 1. You must code the parameter MCPU=YES in the CAIJGEN macro, which indicates that you have a multi-CPU environment. 2. You must code the parameter SHARE=YES in the CAIJGEN macro. This specifies that you are to share the Unicenter CA-Scheduler database and associated files, which includes the database, the tracking file, the staging library, and the documentation file and optionally the Unicenter CA-Driver procedure library. This must always match the SHARE field on the FORMAT and RESTORE commands (see number 4, following). By using the SHARE database facility, you ensure the integrity of accessing the databases and libraries from different CPUs at the same time, which is done with software (spin) locks and not with IBM LOCKs. 3. You must code the parameter SYSID=(sysid1,sysid2,...) in the CAIJGEN macro, which specifies the valid SYSIDs in your multi-CPU environment. The first SYSID in the list is the default SYSID that governs which CPU tracks schedules, which will be explained later. The list is also used to validate any SYSID defined with a schedule or job. 4. You must specify INSRSYS=YES in the CAIJGEN macro to cause Unicenter CA-Scheduler to insert the SYSID on the POWER job statement automatically for designated jobs (jobs defined with a value for the SYSID keyword on their job base records). 5. You must code the parameter SHARE=YES in the FORMAT statement when initializing the Unicenter CA-Scheduler database (CAIJMST), the tracking file (CAIJTRK), the staging library (CAIJSTG), and the documentation file (CAIJDCM). It must also be performed when formatting the the Unicenter CA-Driver procedure library. See the Unicenter CA-Driver Systems Programmer Guide. This is done by executing the program CAJUTIL0. These steps are discussed further in the Unicenter CA-Scheduler Systems Programmer Guide. 7.5.2 Control Of Jobs in a Multi-CPU Environment Discussion in this topic pertains to multi-CPUs in a POWER shared spool environment. This can be depicted as: 7-20 Unicenter CA-Scheduler User Guide

7.5 Multiple CPU Considerations Normally you would not specify a specific CPU on which a job is to execute. That is, you would let POWER determine which CPU is available to handle the job and then let POWER start it on that CPU. This is called centralized control. If you direct a schedule to a specific CPU by defining the SYSID from which it will be controlled (by defining the SYSID on the schedule base record), you will have a degree of decentralized control. The more schedules you do this to, the more decentralized control you have. In the case of decentralized control, be aware that the RUN ON SYSID fields (and the equivalent SYSID batch keywords) on the schedule base record and job base record perform different functions. RUN ON SYSID on the schedule base record defines the CPU on which Unicenter CA-Scheduler controls the schedule (that is, the CPU from which the schedule's jobs are submitted.) On the other hand, RUN ON SYSID on the job base record specifies the CPU on which the job actually executes. The following steps through what happens in the control of a multi-CPU environment on a daily basis. Autoscan During the autoscan process, all schedules that have a SYSID that matches the one for the CPU on which autoscan is being run, will be selected for control on that CPU. That is, all jobs will be submitted from the controlling CPU and internally Chapter 7. Techniques 7-21

7.5 Multiple CPU Considerations<br />

7.5.1 Installation Considerations<br />

When installing <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong>, you have to indicate that it is going<br />

to run in a multi-CPU environment which means that five things have to be<br />

done.<br />

1. You must code the parameter MCPU=YES in the <strong>CA</strong>IJGEN macro, which<br />

indicates that you have a multi-CPU environment.<br />

2. You must code the parameter SHARE=YES in the <strong>CA</strong>IJGEN macro. This<br />

specifies that you are to share the <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> database and<br />

associated files, which includes the database, the tracking file, the staging<br />

library, and the documentation file and optionally the <strong>Unicenter</strong> <strong>CA</strong>-Driver<br />

procedure library. This must always match the SHARE field on the<br />

FORMAT and RESTORE commands (see number 4, following). By using<br />

the SHARE database facility, you ensure the integrity of accessing the<br />

databases and libraries from different CPUs at the same time, which is<br />

done with software (spin) locks and not with IBM LOCKs.<br />

3. You must code the parameter SYSID=(sysid1,sysid2,...) in the <strong>CA</strong>IJGEN<br />

macro, which specifies the valid SYSIDs in your multi-CPU environment.<br />

The first SYSID in the list is the default SYSID that governs which CPU<br />

tracks schedules, which will be explained later. The list is also used to<br />

validate any SYSID defined with a schedule or job.<br />

4. You must specify INSRSYS=YES in the <strong>CA</strong>IJGEN macro to cause <strong>Unicenter</strong><br />

<strong>CA</strong>-<strong>Scheduler</strong> to insert the SYSID on the POWER job statement<br />

automatically <strong>for</strong> designated jobs (jobs defined with a value <strong>for</strong> the SYSID<br />

keyword on their job base records).<br />

5. You must code the parameter SHARE=YES in the FORMAT statement<br />

when initializing the <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> database (<strong>CA</strong>IJMST), the<br />

tracking file (<strong>CA</strong>IJTRK), the staging library (<strong>CA</strong>IJSTG), and the<br />

documentation file (<strong>CA</strong>IJDCM). It must also be per<strong>for</strong>med when<br />

<strong>for</strong>matting the the <strong>Unicenter</strong> <strong>CA</strong>-Driver procedure library. See the<br />

<strong>Unicenter</strong> <strong>CA</strong>-Driver Systems Programmer <strong>Guide</strong>. This is done by executing<br />

the program <strong>CA</strong>JUTIL0.<br />

These steps are discussed further in the <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> Systems<br />

Programmer <strong>Guide</strong>.<br />

7.5.2 Control Of <strong>Job</strong>s in a Multi-CPU Environment<br />

Discussion in this topic pertains to multi-CPUs in a POWER shared spool<br />

environment. This can be depicted as:<br />

7-20 <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> <strong>User</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!