Reviewing the startup JCL procedures

Review the startup JCL procedures listed below and make the required changes for your system.

To review the startup JCL procedures and set up your environment

Perform the following procedure to review the startup JCL procedures:

In the HLQ.RSMSAMP samples library, locate the following sample startup procedures:
- BASPMM for the master address space
- BASPMS for the server address space
- (Optional) BASPMT for the optional TSO address space
Copy the procedures to your production environment that is running the procedure library and change the data set names to reflect those built when you installed Security Policy Manager.
Make sure that the RSSPARM DD statement refers to the Security Policy Manager configuration member that you prepared in Reviewing-product-configuration.

Notes

Multiple Security Policy Manager instances must share the same identifier within a sysplex.
If you use the BASPMT TSO address space, you must use the AutoStart configuration parameter. For more information about AutoStart, see Compliance-testing.

To assign an RSSID

Assign a Security Policy Manager identifier (RSSID) to a BASPMS instance.

The RSSID ties the TSO REXX address space and the Security Policy Manager address space together. At startup, RSS joins an XCF group designated by the RSSID parameter. This is the XCF group used for inter-RSS (inter-LPAR) communication, including communication with the TSO REXX address space, which must share the same RSSID.

If a Security Policy Manager address space needs to interact with another Security Policy Manager server address space (such as another LPAR running the server or the optional Security Policy Manager TSO address spaces), the same ID must be assigned to each address space, using the RSSID parameter.

To review the XCF group name

Security Policy Manager doesn’t use the RSS XCF group, so it joins a second XCF group managed by Security Policy Manager. This XCF group is named BMCSPM by default, but you can override the name in the GroupName parameter. For more information, see the "Security Policy Manager parameters" section of Configuring-parameters.

To specify the master address space

For the Security Policy Manager master address space, update the STEPLIB to reflect the load library (that is, HLQ.RSMLOAD):

//ZDTMPROC DLL=ZDTMSTR,MSTR=RSMZDTEC
//RSSMSTREXEC PGM=ECIMSTR,REGION=0M,TIME=1440,
//PARM='DLL=&DLL,MSTR=&MSTR'
STEPLIBDD DISP=SHR,DSN=HLQ.RSMLOAD

Only one master address space can run on an LPAR.

To specify the EXEC parameter statement

The EXEC PARM for the server and agent address spaces supports the following parameters:

//RSS PROC
//RSS MBR=config_member_name,MSTR=RSMZDTEC
// PARM=('ENVAR("TZ=GMT-1")',
'/RSSID=rssid,SCOPE=lpar_name,CONFIG=&MBR,MSTR=&MSTR',
MSTR=&MSTR,START=WARM)

Set the parameter settings as follows:

MSTR must match the MSTR parameter of the master task JCL.
START must be COLD for the initial run because this formats the checkpoint data set. After the initial startup, change this parameter to WARM.
TZ format must match the standard IBM time zone formats.
SCOPE is optional and is used to control the block of configuration parameters processed by this instance. For more information, see Configuring-parameters.

Security Policy Manager stores all data in an OMVS temporary directory database. If you have an issue with temporary space, you can specify TMPDIR on the EXEC statement:

//BASPMS   EXEC PGM=RSS,REGION=0M,TIME=1440,
// PARM=('ENVAR("TMPDIR=/SYSA/RSM/Policy_Manager/v20")',
//        '/RSSID=RSSID,MSTR=&MSTR,START=&START,CONFIG=&MBR')

To specify the TSO address space

For the optional TSO address spaces, the syntax to define the RSSID is slightly different due to the need for the IKJEFT01 entry point:

//RSSTSOPROC RSSID=rssIdName
//RSSTSOEXEC PGM=IKJEFT01
// PARM='CALL *(ECTSO) ''RSSID=&RSSID'' '