Creating the z/OS PAS startup procedure
This task is required for the following products but does not apply to other products:
MainView for z/OS
MainView for Unix System Services
MainView SYSPROG Services
When you create the z/OS PAS started task procedure, specify the same subsystem ID on the SSID parameter of the PROC statement as you did in the CAS started task procedure. The PAS uses this SSID during initialization to identify its CAS connection.
To create the started task procedure
- Copy BBILIB member BBMPAS to SYS1.PROCLIB or another system procedure library and give it an appropriate name for a started task procedure.
By default, configuration during installation creates a member called MVSPAS.
- Follow the instructions at the top of the member to modify the procedure to your site requirements.
- (Optional ) Define the z/OS PAS started task procedure to your IPL procedure so that the PAS starts at system initialization.
BMC recommends that you modify the COMMNDxx member in SYS1.PARMLIB to add a START command for the PAS procedure:
procname is the name of the z/OS PAS started task procedure.
The START commands are issued in the order that they appear in COMMNDxx. The z/OS PAS START command must occur after the CAS START command.
- If you do not define the z/OS PAS to start at IPL, see Managing the z/OS product address space for information about manually issuing a START command for the PAS.
Where to go from here
During PAS execution, BMC recommends that you:
Initiate the z/OS PAS as a started task (STC) through a system IPL procedure
Execute only one z/OS PAS per system image
Execute the z/OS PAS with a dispatching priority of 255