Syntax of the IRRDPI00 command

IRRDPI00   {CHECK | LIST [(profile-type [segment-name [keyword-name]])] | UPDATE}

where:

CHECK

Performs syntax checks on the input data set (SYSUT1 DD statement).

If the CFIELD class is active, validity checking of the custom field definitions in the CFIELD class is performed. Fields with the following errors will result in an error message, and will not be included in the dynamic parse table:

TYPE is not NUM, CHAR, HEX or FLAG
MAXVALUE is less than MINVALUE for TYPE(NUM)
Missing MAXVALUE for TYPE(NUM)
Missing MINVALUE for TYPE(NUM)
Value of FIRST is not correct for TYPE(NUM), TYPE(HEX), or TYPE(FLAG)
Value of OTHER is not correct for TYPE(NUM), TYPE(HEX), or TYPE(FLAG)
MAXLENGTH is missing or is not correct for the TYPE
Values other than NOMINVALUE and NOMAXVALUE are set for TYPE(CHAR), TYPE(HEX), or TYPE(FLAG)
MIXED(NO) is not set for TYPE(NUM), TYPE(HEX), and TYPE(FLAG)
MAXVALUE/MINVALUE has more digits than is allowed by MAXLENGTH for TYPE(NUM)

LIST [(profile-type [segment-name [keyword-name] ] ) ]

Lists dynamic parse specification data. If you issue IRRDIP00 with no operands, LIST is the default. You can optionally specify for which profile type, segment, and keyword you want to list dynamic parse specification data. Note that if you do not specify a profile type and segment name, the output is quite large.

profile-type

The type of profile for which you want to list dynamic parse specification data. It can have the following values:

DATASET: DATASET profiles
GENERAL: General resource profiles
GROUP: GROUP profiles
USER: USER profiles

For example, to list dynamic parse specification data for all segments and keywords in the USER profile, issue:

IRRDPI00 LIST(USER)

segment-name

The name of the segment for which you want to list dynamic parse specification data, within the type of profile specified in profile-type. To specify segment-name, you must also specify profile-type. For a list of possible values for segment-name, see Table 1.

For example, to list dynamic parse specification data for all fields in the TSO segment of the USER profile, issue:

IRRDPI00 LIST(USER TSO)

To list all custom fields currently in effect for USER profiles, issue:

IRRDPI00 LIST(USER CSDATA)

To list all custom fields currently in effect for GROUP profiles, issue:

IRRDPI00 LIST(GROUP CSDATA)

keyword-name

The name of the keyword for which you want to list dynamic parse specification data, within the segment specified in segment-name and the profile specified in profile-type. To specify keyword-name, you must also specify profile-type and segment-name. The keywords are from the commands used to define the segments. Table 1 lists the profile types and segment names that you can specify, and identifies the commands that define them. To find the values of keyword-name that are valid for a combination of profile type and segment, look up the command in z/OS Security Server RACF Command Language Reference and find the keyword for the segment name. The subkeywords supported for the segment keyword are valid values for keyword-name on IRRDPI00.

For example, the TSO segment for the USER profile is defined by the ADDUSER command. The ADDUSER command allows you to specify keywords including ACCTNUM, COMMAND, DEST, and HOLDCLASS on the TSO keyword to define the TSO segment. To list the dynamic parse specification data for the ACCTNUM keyword, specify:

IRRDPI00 LIST(USER TSO ACCTNUM)

For the CSDATA segment of USER and GROUP profiles, valid values for keyword-name will be installation specific. This is because the CSDATA segment holds custom field data which can be defined by an installation using CFDEF segments in CFIELD profiles. For example, if your installation has defined the custom field keyword EMPSER for the CSDATA segment of the USER profile, you would enter the following to list the dynamic parse specification data for this keyword.

IRRDPI00 LIST(USER CSDATA EMPSER)

Contact your security administrator for information on the valid keyword-name values for the CSDATA segment of USER and GROUP profiles at your installation. Alternatively, you can omit the keyword-name to list all valid values for the CSDATA segment. For more information on custom fields and how to define them, refer to the z/OS Security Server RACF Security Administrator's Guide.

Table 1. Valid profile types and segment names for IRRDPI00
Profile type	Segment name	Command that defines the segment
DATASET	DFP	ADDSD
DATASET	TME	ADDSD
GENERAL	CDTINFO	RDEFINE
GENERAL	CFDEF	RDEFINE
GENERAL	DLFDATA	RDEFINE
GENERAL	EIM	RDEFINE
GENERAL	ICSF	RDEFINE
GENERAL	ICTX	RDEFINE
GENERAL	KERB	RDEFINE
GENERAL	PROXY	RDEFINE
GENERAL	SESSION	RDEFINE
GENERAL	SIGVER	RDEFINE
GENERAL	SSIGNON	RDEFINE
GENERAL	STDATA	RDEFINE
GENERAL	SVFMR	RDEFINE
GENERAL	TME	RDEFINE
GROUP	CSDATA	ADDGROUP
GROUP	DFP	ADDGROUP
GROUP	OMVS	ADDGROUP
GROUP	OVM	ADDGROUP
GROUP	TME	ADDGROUP
USER	CICS®	ADDUSER
USER	CSDATA	ADDUSER
USER	DCE	ADDUSER
USER	DFP	ADDUSER
USER	EIM	ADDUSER
USER	KERB	ADDUSER
USER	LANGUAGE	ADDUSER
USER	LNOTES	ADDUSER
USER	NDS	ADDUSER
USER	NETVIEW	ADDUSER
USER	OMVS	ADDUSER
USER	OPERPARM	ADDUSER
USER	OVM	ADDUSER
USER	PROXY	ADDUSER
USER	TSO	ADDUSER
USER	WORKATTR	ADDUSER

UPDATE

Performs syntax checks on the input data set and updates the dynamic parse table if no errors were found. If the CFIELD class is active, validity checking is performed on the CFIELD profiles, and the custom field keywords with no errors and their attributes are stored in the dynamic parse table.