RACF manager return codes

This topic lists and explains the RACF® manager return codes. It contains Programming Interfaces that allow you to write programs to obtain the services of the z/OS® Security Server.

The RACF manager returns the codes to the caller (a RACF SVC, a command processor, or a user-written program) in hexadecimal in Register 15.

Code

Explanation

Hex (Decimal)

0 (0)

The requested operation was successful.

4 (4)

A recovery environment could not be established.

8 (8)

An attempt was made to add an entry (a profile) to the RACF database but an identical entry already exists.

Note: Identical entries have the same name, type, and (if specified) volume.

C (12)

For requests other than NEXT or NEXTC, the specified entry (RACF profile) did not exist.

For NEXT or NEXTC requests, no subsequent entries (RACF profiles) satisfied the request.

10 (16)

Reserved.

14 (20)

The RACF database did not contain enough space to satisfy the request.

18 (24)

An I/O error occurred while accessing the RACF database. The RACF manager uses the EXCP macro to access the RACF database. This error might be caused by a problem with the DASD on which the RACF database is stored.

1C (28)

RACF was not active at the time of the request; or, in an environment with multiple RACF data sets, the RACF data set containing the requested profile is inactive.

19 (25)

The number of actual tests for the ICHEINTY request for the CONNECT type profile is more than 254.

20 (32)

One of the following occurred:

The request type requires a user work area but the area was not provided (the address in the parameter list was 0).
For a RENAME, NEWNAME and NEWNAMEX was supplied.

24 (36)

The input parameter list or the associated ACTION and TEST blocks contain an error. For abend 482, 483, or 485, this RACF manager return code usually indicates that down-level templates are being used for the RACF database. Template conversion is done with IRRMIN00. Do the following:

Check the output of IRRMIN00 to be sure higher-level templates were used.
Check that the higher level of IRRMIN00 was run.
Check that IRRMIN00 was run against the correct RACF database. RACF uses the templates from the first primary RACF database activated.
Check that a database with lower level templates was not copied over the database that had IRRMIN00 run against it.

When this code is returned, register 0 contains one of the following reason codes:

Code: Explanation
Hex (Decimal)
1 (1): Entry name (profile name) or NEWNAME is not valid.
2 (2): Action(s) specified with DELETE or DELETEA.
3 (3): An action specified for an undefined field.
4 (4): Test(s) specified with RENAME.
5 (5): Reserved.
6 (6): Reserved.
7 (7): Incorrect entry type (profile type).
8 (8): DATAMAP(OLD) was coded on the ICHEINTY macro, and GROUP=YES was coded on the ICHEACTN macro, but the given data length was too long for the repeat group.
9 (9): DATAMAP(OLD) was coded on the ICHEINTY macro, and GROUP=YES was coded on the ICHEACTN macro, but the given data length was too short for the repeat group.
A (10): Consistency error between multiple input parameter lists. This error occurs if chaining is being used and all input parameter lists are not using the same options or the same values for: TYPE, RBA, CLASS, VOLID, ENTRY, SMC, GENERIC or INDEX.
B (11): Input parameter list chaining/request type combination error. This error occurs when the rules for types of input parameter list requests that might be chained are violated. For example, the first input parameter list can only be a NEXT or NEXTC, LOCATE, ALTER or ALTERI, DELETE with SEGMENT or ADD. The following input parameter lists can only be LOCATE (after LOCATE), NEXT/NEXTC (after NEXT/NEXTC), ALTERI (after ALTERI), ALTER (after ALTER, DELETE or ADD), and DELETE with SEGMENT (after ALTER or DELETE).
C (12): All input parameter lists specify RUN=NO.
D (13): Request type/segmentation combination error. This error occurs if a segment name is specified with ADD, DELETEA, or RENAME.
E (14): Invalid field for GROUP=YES. This error occurs if GROUP=YES was coded but the field is not a repeat group.
F (15): Input parameter list limit exceeded. More than 1000 input parameter lists were chained.
10(16): Segment not allowed. Specified SEGMENT name not allowed for the specified profile TYPE.
11(17): Inconsistency between ACTION data length and repeat group FIELDS, GROUP=YES. This is similar to return code 8, but DATAMAP(NEW) was coded on the ICHEINTY macro.
12 (18): Data length specified on ICHEACTN macro exceeded the length of the specified fixed-length field.
13 (19): Inconsistency between action data length and repeat group fields. GROUP=YES data is too short.
14 (20): Invalid ENTRYX. Current length is greater than 44 and either the primary or the backup database is not in the restructured (RDS) format.
15 (21): Invalid NEWNAMX. Current length is greater than 44 and either the primary or the backup database is not in the restructured (RDS) format.
16 (22): Data length specified on the ICHEACTN macro was less than zero and FLDATA=‘DEL’ and FLDATA=‘COUNT’ was specified.
17 (23): The generic entity name exceeds the maximum length after it has been encoded.
18 (24): Limit has been reached for the concurrent source request.
19 (25): Number of tests is greater than 254.
1A (26): Invalid date supplied on an ICHEACTN when DATEFMT=YYYYDDDF is specified.
1B (27): Repeat count cannot be updated when GROUP=NO is specified.
1C (28): Alias locate requested but database is stage 0 or 1.
1D (29): Alias processing not supported for request type.
1E (30): Alias locate requested for a non-alias field.
1F (31): Base pointer for test is 0 on an alias locate request.
20 (32): Alias name length is 0 or greater than 252.

28 (40)

The maximum profile size (65,535 bytes) has been reached; the profile cannot be expanded.

2C (44)

The user-supplied work area was not large enough to hold all the data returned. The work area is filled with data up to, but not including, the first field that did not fit.

30 (48)

The user-supplied work area was smaller than the minimum amount required (30 bytes).

34 (52)

A test condition specified in the TESTS keyword of the ICHEINTY macro was not met; RACF stopped processing.

38 (56)

You requested an operation on an entry (profile) in class DATASET that has multiple RACF definitions, but you did not specify a VOLUME to single out a specific entry.

3C (60)

For DATASET class entries, you specified a VOLUME that did not exist in the volume list of any entry with the specified name. For TAPEVOL class entries, a request tried to add a new TAPEVOL to a nonexistent tape volume set.

40 (64)

You attempted to delete one of the IBM-defined entries (such as SYS1 or IBMUSER) from the RACF database.

44 (68)

An ALTERI request attempted to increase the size of the profile being updated.

48 (72)

A request to add an entry to the RACF database would have caused the RACF index to increase to a depth that RACF does not support (the maximum depth is 10 levels).

4C (76)

ICHEINTY encountered an invalid index block or read a non-index block when it expected an index block.

50 (80)

An attempt was made to update one of the following (by a request other than ALTERI):

The RACF database that has been locked by a RACF utility
The RACF database from a system that is in read-only mode (in a RACF sysplex data sharing environment)

54 (84)

Reserved (used internal to RACF).

58 (88)

Some field-level access checks failed for data retrieval.

5C (92)

All field-level access checks failed for data retrieval.

60 (96)

Field-level access checks failed for data update.

64 (100)

Reserved for use by the ICHEINTY macro for RELEASE=(xx,CHECK).

68 (104)

Invalid data in a RACF profile. Detail code is in the reason code:

Code: Explanation
Hex (Decimal)
1 (1): Profile too short

6C (108)

The RACF manager has been invoked recursively, and an exclusive reserve/enqueue is required. However, a shared reserve/enqueue is already held.

70 (112)

The RACF manager received an unexpected return code from a reserve/enqueue. The reserve/enqueue return code is passed back in register 0.

78 (120)

Reserved (used internal to RACF).

7C (124)

Reserved (used internal to RACF).

80 (128)

This is a data sharing mode return code. A coupling facility function had a problem when dealing with the ICB.

84 (132)

Maximum alias index entry size has been reached.