N Custom Data Field (CSDATA)

Custom Data Fields (CSDATA) are user-defined segments available on the User and Group profiles. These fields provide an alternative to Installation Data or use of other predefined segments to keep the information in the RACF database.

CSDATA is defined in the CFIELD General Resource Class using the standard RACF commands. Multiple fields can be defined in the CSDATA. CSDATA may contain any information such as: Department, Employee ID, Email address, Physical Location (City/State), and so on.

This appendix contains the following topics:

• Adding CSDATA Fields

• Parsing CSDATA Fields

N.1 Adding CSDATA Fields

RACF administrators can create customized user-defined fields for specific segments.

For example, to add a field with 8 characters all numeric:

RDEFINE CFIELD USER.CSDATA.EMPSER UACC(NONE)
	       CFDEF(TYPE(NUM)
	       FIRST(NUMERIC) OTHER(NUMERIC)
	       MAXLENGTH(8)
	       MINVALUE(100000)
	       MAXVALUE(99999999)
	       HELP('EMPLOYEE SERIAL, 6-8 Digits')
	       LISTHEAD('Employee serial=')

To enter more than one value, separate each value with a vertical bar (|) character. Each field name should have a corresponding configDNames entry.

To include CSDATA in a LISTUSER command [true|false] -useCSDATA_=true/.

Note:

To include CSDATA as part of the ‘LISTUSER’ command, set the value of the command to true.

To add a custom attribute or custom dataset, set values for the _configAttrs_, _configDNames and _configDatasets_properties in the connector.properties file. Here:

• _configAttrs_: specifies the property that holds the field names of any custom target system fields that are defined in the CSDATA user segment and used during user provisioning operations. To enter more than one value, separate each value with a vertical bar (|) character. Each field name should have a corresponding configDNames entry. For example:

  # CUSTOM CSDATA RACF ATTRIBUTE FIELD NAME
  _configAttrs_=$PST15|VEND ID|

• _configDNames_: specifies the property that holds the display name(s) of RACF field(s) that are defined in the CSDATA segment and used during user reconciliation operations. If entering more than one value, separate each value with a vertical bar (|) character. Each display name should have a corresponding configAttrs entry. For example, to define a field with a display name of $PST15 and VEND ID, then enter:

  # CUSTOM CSDATA RACF ATTRIBUTE DISPLAY NAME
  _configDNames_=$PST15 =|VEND ID =|

N.2 Parsing CSDATA Fields

To properly parse the fields from the CSDATA section of a user extract, the following parameter must be defined:

_configExtractAttrs_=<fld1>|<fld>

Here, <fld> = 9-character field name including ending colon.

For example, if the user extract produces the following CSDATA listing:

Segment: CSDATA Fields:03
EMPSER :100101
ADDRESS1:20 Main St., Anytown, PA., 08011
PHONE :[phone]

The definition of the property would be: _configExtractAttrs_=EMPSER :|ADDRESS1:|PHONE :

It is important to make sure that the colon character is in the ninth character position on all fields being parsed from a user extract as that is considered the standard format of all field listings in a user extract.

To add a field with 8 characters all numeric:

RDEFINE CFIELD USER.CSDATA.EMPSER UACC(NONE)
	       CFDEF(TYPE(NUM)
	       FIRST(NUMERIC) OTHER(NUMERIC)
	       MAXLENGTH(8)
	       MINVALUE(100000)
	       MAXVALUE(99999999)
	       HELP('EMPLOYEE SERIAL, 6-8 Digits')
	       LISTHEAD('Employee serial=')