Step 5B: Startup Procedures Required for System Operations Only
| SysOps | ProcOps |
|---|---|
| ✓ |
- Automation Manager Startup Procedure
You can use the sample provided in the INGEAMSA member of the SINGSAMP data set. Copy it to a member of the SYS1.PROCLIB data set of all systems where System Automation will be installed and run.
Configure that copy to your needs. In particular, make sure that the DD concatenations mentioned in Step 2: Allocate System-Unique Data Sets include the data sets that you allocated there. In addition, consider configuring the following point:- If you prefer not to place the automation manager
PARMLIB member in the SYS1.PARMLIB concatenation, include a HSAPLIB DD statement in the automation manager startup procedure (see also Step 9: Configure the Automation Manager):
In place ofHSAPLIB DD DSN=ING.PARMLIB, DISP=SHRING.PARMLIB, use the PARMLIB data set that you allocated in Step 2: Allocate System-Unique Data Sets.
- If you prefer not to place the automation manager
PARMLIB member in the SYS1.PARMLIB concatenation, include a HSAPLIB DD statement in the automation manager startup procedure (see also Step 9: Configure the Automation Manager):
- Other System Operations Startup Procedures
Copy the following members from the SINGSAMP data set to members of the SYS1.PROCLIB of all systems where System Automation will be installed and run:
- HSAPIPLC
- This procedure gathers IPL statistics and stores the information in the IPLDATA file. Once set
up, you can view sysplex-wide IPL data with the command
INGPLEX IPL.You can give the procedure any name.
It is recommended that you define this procedure in your automation policy as an application with the option 'START ON IPL ONLY'.
Alternatively, you can start this procedure during every IPL. This can be accomplished by adding
COM='S HSAPIPLC,SUB=MSTR'to a COMMANDxx parmlib member that is shared by all systems in the sysplex. - INGPHOM
- This procedure is used internally by SA z/OS to process sysplex data for CF paths.
The procedure name must not be changed.
- INGPIPLC
- This procedure is used internally by SA z/OS to compare IPL data.
The procedure name must not be changed.
- INGPIXCU
- The procedure is used internally by SA z/OS to process sysplex data for Sysplex utilities (for example, Couple Data Set management, Coupling
Facility management, and so on.). Once set up, you can view and manage related Sysplex CDS and CF
data with the commands
INGPLEX CDSandINGPLEX CF.The procedure name must not be changed.
Follow the configuration instructions that are contained in the HSAPIPLC member.
Note: These procedures make use of certain data sets and must have the appropriate authorizations. For details refer to Granting NetView and the STC-User Access to Data Sets. - Optional: Startup Procedure for the External Writer
of the Component Trace
Copy member HSACTWR from SINGSAMP. At least the SYSNAME parameter must be specified before the procedure is stored in a library of the PROCLIB concatenation.