Operational considerations

The output records of IRRDBU00 are determined by the structure of the RACF® database. The utility unloads all profiles in the database. It does not unload all fields in each profile and treats some fields in a special way.

Encrypted and reserved fields are not unloaded.
Fields that contain installation data are unloaded exactly as they appear in the database, with the exception of CSDATA fields.
Fields in the CSDATA segment are unloaded according to the data type defined within each field.
When possible, fields that contain UTF-8 data are translated to EBCDIC using the IBM-1047 code page. When not possible, these values appear in hexadecimal format. For details, see the note in Table 1.

The maximum length of unloaded data for most fields is 255 bytes. However, the entire length of data is unloaded for the following fields:

Up to 1023 bytes for the HOME and PROGRAM fields in the OMVS segment of a user profile.
Up to 1023 bytes for the HOME, PROGRAM, and FSROOT fields in the OVM segment of a user profile.
Up to 1100 bytes for each field in the CSDATA segment of a user or group profile.

See z/OS Security Server RACF Macros and Interfaces for the conversion rules of the database unload utility.

The database unload utility uses both the supplied class descriptor table (ICHRRCDX) and the installation-defined class descriptor table (ICHRRCDE) as it unloads profiles. If your database is imported from another system, you might also have to import ICHRRCDX and ICHRRCDE. Classes are unloaded only if there is an entry for them in ICHRRCDE or ICHRRCDX on the system running the utility, and the range table on that system correctly identifies the data set where the profiles are located. If the current range table does not match the database being unloaded, you must run the IRRDBU00 utility multiple times, specifying only one data set of the database as INDD1 for each run.

The database unload utility uses the supplied class descriptor table (ICHRRCDX), the installation-defined class descriptor table (ICHRRCDE), and the dynamic class descriptor table, as it unloads profiles. If your database is imported from another system, you might also have to import ICHRRCDX and ICHRRCDE and create new dynamic classes.

The database unload utility unloads a class only when both of the following conditions are true:

There is an entry for the class in either the ICHRRCDE, ICHRRCDX, or the dynamic class descriptor table on the system running the utility
The range table on the system running the utility correctly identifies the data set where the profiles are located.

If the current range table does not match the database being unloaded, you must run the IRRDBU00 utility multiple times, specifying only one data set of the database as INDD1 for each run.

To correlate the RACF profiles with the data unloaded by the utility, see z/OS Security Server RACF Macros and Interfaces.