CTnRSMxx parmlib member

The following table indicates the parameters you can specify on a CTnRSMxx parmlib member.

Parameters	Allowed on CTnRSMxx?
ON or OFF	Yes
ASID	Yes
JOBNAME	Yes. To trace all batch jobs, specify ‘INIT’ in the list of job names.
BUFSIZE	Yes
OPTIONS	Yes
SUB	No
PRESET	No
LIKEHEAD	No
WTR	Yes
WTRSTART or WTRSTOP	Yes

IBM® provides two sample CTIRSMxx parmlib members in SYS1.PARMLIB. These are not default members.

CTIRSM01: Shows how to request tracing of all RSM functions and events using the options DMPOFF, NOCOMASID, and NODMPREC.
CTIRSMSP: Shows how to request address space, job name filtering, and trace request options to limit the tracing.

RSM trace data in high virtual private storage: RSM supports collecting trace data into high private memory. This storage is used as a secondary buffer data, which is first collected into buffers in fixed high common storage, and later moves out into high private memory. Having a secondary buffer is another way, besides trace data sets, to handle a large number of RSM trace records. Note that the paging activity for the secondary buffer can appear in the RSM trace records.

If you suspect that your system has a paging problem, collect the RSM trace records in page-fixed primary buffers to keep from losing records while paging. A record can be lost as the system reuses a full secondary buffer

For RSM, use BUFF in the CTnRSMxx OPTIONS parameter to specify the number of page-fixed buffers and their page sizes. In Figure 1, the statements in CTWRSM05 specify four page-fixed buffers that are 64 pages and a secondary buffer in high private memory of 640 KB.

Figure 1. Example: Using the CTWRSM05 parmlib member

TRACEOPTS
   ON
   BUFSIZE(640K)
   OPTIONS('BUFF(4,64)')

For RSM, the BUFSIZE parameter in the CTnRSMxx parmlib member specifies the total size of the high virtual private buffers located in the RASP address space. The space in the buffer is divided evenly between the amount of installed processors.