Statements/parameters for AXRxx

CPF('<cpf value>',SYSTEM|SYSPLEX)
AXRUSER(<Userid>)
REXXLIB ADD DSN(<Rexxlib data set name>) VOL(<volser>)
or
REXXLIB ADD DSNAME(<Rexxlib data set name>)
MaxWorkerTasks(nn)

Note:

VOLSER (or VOL) is optional when the data set is cataloged.
The <volser> can be a quoted string.

CPF defines a 1-8 character command prefix value for System REXX that can be used instead of specifying the MODIFY AXR command. This prefix may be defined as either SYSTEM or SYSPLEX in scope.

SYSTEM scope indicates that the CPF will only be recognized on the system it is defined on.
SYSPLEX scope indicates that it will be recognized throughout the SYSPLEX and the command will be routed to the system on which it is defined.

The default value of CPF is:

CPF('REXX&SYSCLONE.',SYSPLEX)

For more information about CPF, see the topic on Using the Command Prefix Facility Using the Command Prefix Facility in z/OS MVS Planning: Operations.

Example: To obtain information about System REXX, enter @SYSREXX STATUS instead of MODIFY AXR,SYSREXX STATUS.

CPF('@',SYSTEM)

The AXRUSER parameter specifies a 1-8 character user ID that is used to define the security environment that an exec initiated using the AXREXX macro when SECURITY=BYAXRUSER is specified. The exec will run with the level of authorization associated with the specified user ID.

The installation needs to provide the user ID with SAF access to the resource SYSREXX.<userid>. There is no default for this parameter. If it is omitted, any subsequent AXREXX invocation using AXRUSER will be rejected. Also, the installation security product must be active when system REXX initializes; otherwise, system REXX initialization is delayed.

The REXXLIB concatenation is an ordered list (by appearance in AXRxx) of data sets specified by REXXLIB ADD. When the AXREXX macro is called directly or indirectly from the operator console, System REXX searches this list for the specified exec. If the cataloged SYS1.SAXREXEC is not among the data sets specified, it is appended to the end. All data sets specified in the REXXLIB concatenation must have the same record type and record length as SYS1.SAXREXEC. The data set must either be a PDS or PDSE.

Adding data sets to the REXXLIB concatenation: The number of data sets that you can add to form the REXXLIB concatenation is limited by the total number of DASD extents the data sets will occupy. A partitioned data set extended (PDSE) counts as one extent. The total number of extents must not exceed 255 that is the current system limit.

The system will concatenate as many of the REXXLIB data sets as possible until the system limit of 255 extents is reached. If each data set in the REXXLIB concatenation occupies just a single extent, 255 data sets can be concatenated. The effective size of the concatenation is reduced if data sets in the concatenation occupy secondary extents. Each secondary extent reduces the concatenation size by one. The total reduction is the sum of all secondary extents. When the system limit is exceeded, message AXR0115E is issued, and no further requests are processed by System REXX.

The MaxWorkerTasks(nn) parameter indicates the maximum number of worker tasks that are running TSO=NO work in the AXR address space, where nn is a value in the range of 4 to 64. The default value is 32.

For more information, see z/OS DFSMS Using Data Sets.