Step 1C: Data Sets for Automation Managers (Primary Automation Manager and Backups)

SysOps ProcOps
✓  
The data sets in Table 1 are required once per sysplex or standalone system. In the same sysplex or standalone system, they should be shared by the primary automation manager and its backups, but they cannot be shared across sysplex or standalone-system boundaries. Except for the takeover file, they need to be referred to in the automation manager startup procedure in Step 4: Configure SYS1.PROCLIB Members.
Each subplex requires one separate set of the following:
  • The schedule override file
  • The configuration information data set
  • The automation manager takeover file
Table 1. Data Sets for All Automation Managers in a Sysplex or Standalone System
Purpose Sample job to allocate the data set Organization DD name in the automation manager startup procedure
Schedule override file INGALLC3 VSAM HSAOVR
Configuration information data set INGALLC3 Sequential HSACFGIN
PARMLIB INGALLC3 Partitioned HSAPLIB
Takeover file INGALLC3 VSAM —
Note: Use the following formula to work out the required size of the takeover file: 4000 records + n records of 4K, where n is the maximum numbers of resources.
The data sets in Table 2 must be allocated once for each automation manager. They cannot be shared between an automation manager and its backups on the same system. Therefore, when you edit the sample job that is to allocate the data sets for a particular sysplex or standalone system, make sure that you include a fresh job step for each automation manager that you plan to have on that particular sysplex or standalone system. For more details, see the comments in the INGALLC3 sample.
Note: You can safely use the same DD names in each job step because DD names are not shared across job step boundaries.

These files also need to be referred to in the automation manager startup procedure in Step 4: Configure SYS1.PROCLIB Members.

Table 2. Data Sets for Each Individual Automation Manager
Purpose Sample job to allocate the data set Organization DD name in the automation manager startup procedure
Internal trace files (optional) INGALLC5 Sequential TRACET0
INGALLC5 Sequential TRACET1
ALLOCOUT data set INGALLC5 Sequential SYSOUT
ALLOCPRT data set INGALLC5 Sequential SYSPRINT
DUMP data set for LE environment INGALLC5 Sequential CEEDUMP
The generation data groups (GDGs) in Table 3 must be created once for each automation manager. They cannot be shared between an automation manager and its backups on the same system. Therefore, when you edit the sample job that is to create the GDGs for a particular sysplex or standalone system, make sure that you include a new set of GDG definitions for each automation manager that you plan to have on that particular sysplex or standalone system. For more details, see the comments in the INGALLC6 sample.

These files also need to be referred to in the automation manager startup procedure in Step 4: Configure SYS1.PROCLIB Members.

Table 3. Generation Data Groups for Each Individual Automation Manager
Purpose Sample job to create the GDG Organization DD name in the automation manager startup procedure
Internal trace files INGALLC6 Sequential TRACET0
INGALLC6 Sequential TRACET1
ALLOCOUT data set INGALLC6 Sequential SYSOUT
ALLOCPRT data set INGALLC6 Sequential SYSPRINT
DUMP data set for LE environment INGALLC6 Sequential CEEDUMP