z/OS MVS Programming: Resource Recovery
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Creating a cataloged procedure for starting RRS

z/OS MVS Programming: Resource Recovery
SA23-1395-00

IBM® supplies, in SYS1.SAMPLIB, a cataloged procedure named ATRRRS that you can use to start RRS after system initialization. Your installation should copy SYS1.SAMPLIB(ATRRRS) to SYS1.PROCLIB(RRS). The membername RRS specified here can be replaced with any other membername, as long as it matches the subsystem name specified in the SYS1.PARMLIB(IEFSSNxx) used by the installation. If the names do not match, you may receive error messages when you start the subsystem.

The contents of ATRRRS are:
//RRS  PROC  CTMEM='',GNAME=''
//RRS  EXEC  PGM=ATRIMIKE,REGION=0K,TIME=NOLIMIT,
             PARM='GNAME=&GNAME,CTMEM=&CTMEM'
The parameters in the procedure are as follows:
CTMEM
Specifies the CTnRRSxx parmlib member that RRS component trace is to use. CTMEM='' indicates that the START command can supply the member name.
GNAME
Specifies the log group name. A log group is a group of systems that share an RRS workload. Specify a value if your installation needs an RRS log group that is a subset of the systems in a sysplex. Otherwise, the name defaults to the sysplex name.

If you specify a name, it must be 1-8 characters in length. The first character must be alphabetic or @, #, or $. The remaining characters must be alphabetic, numeric, or @, #, or $.

PGM=ATRIMIKE
Specifies the initialization routine for the RRS jobstep task. PGM=ATRIMIKE is required.
REGION=0K
Specifies that the address space is to have the largest allowable size on the system.
TIME=NOLIMIT
Specifies that there is no time limit for RRS.

If you used the GNAME parameter to define a log group that is a subset of the sysplex, take great care to ensure that a resource manager always restarts on a system within the same log group. If a resource manager restarts on a system within a different log group, RRS does not detect the discrepancy; it assumes that the resource manager is doing a cold start.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014