| 0 |
0 |
0 |
The service was successful. Output
from the RACF command may be
present. The Out_message_strings parameter should be interrogated
by caller. |
| 4 |
0 |
0 |
RACF is
not installed. |
| 4 |
4 |
0 |
For ADMN_XTR_PWENV, the user does not have a
password envelope. For ADMIN_XTR_PPENV, the user does not have a password
phrase envelope. |
| 4 |
4 |
4 |
The target profile does not exist. For ADMN_XTR_PWENV
and ADMN_XTR_PPENV, the target user does not exist. For extract functions,
the requested profile does not exist. For extract-next requests,
there are no more profiles that the caller is authorized to extract. |
| 4 |
4 |
8 |
For ADMN_XTR_PWENV, a problem was encountered
while retrieving the password envelope. For ADMN_XTR_PPENV, a problem
was encountered while retrieving the password phrase envelope. |
| 4 |
4 |
12 |
The specified class could not be found in the
class descriptor table. Note that the class cannot be USER, GROUP,
CONNECT, or DATASET. |
| 4 |
4 |
16 |
A discrete profile was not found, and a matching
generic profile could not be located because the class is inactive
or SETROPTS NOGENERIC is in effect for the class. A matching generic
profile may or may not exist for the resource name specified. |
| 4 |
4 |
20 |
On an extract-next request, the next profile
encountered is a discrete profile which contains at least one generic
character. See usage note 8 for
more information. |
| 8 |
8 |
0 |
Incorrect function code |
| 8 |
8 |
4 |
Input parameter list error. See usage
note 7 for possible causes. |
| 8 |
8 |
8 |
Invalid data in the input parameter
list may cause the program to abend. Some fields in the parameter
list must be coded with the defined length and data format. The profile
segment name, for example must not be longer than 8 bytes. If more
than 8 bytes are passed, unpredictable results may occur and the user
gets a return code of 8 8 8 with a possible program abend. If
the program ABENDs before GTF trace records are created, then you
do not have GTF trace records to use for debugging. Check the input
parameter list for errors.
|
| 8 |
8 |
12 |
Recovery environment could not be
established. |
| 8 |
8 |
16 |
Invalid request specified. For ADMN_RUN_COMD,
the input command image represented an incorrect or unsupported command.
For all other functions, the input parameter list contained an incorrect
segment name, field name, or flag byte, or incorrectly specified field
data. The function-specific parameter list header contains an offset
to the segment or field entry in error, relative to the start of the
parameter list. |
| 8 |
8 |
20 |
Function not supported for problem
state caller. |
| 8 |
8 |
24 |
Caller not authorized |
| 8 |
12 |
IEFSSREQ return code |
Unable to invoke the RACF subsystem. Reason code field contains
a return code from the IEFSSREQ macro invocation. See z/OS MVS Using the Subsystem Interface for
information about possible return codes from IEFSSREQ. Note: A LOGREC
record is cut by RACF with
the function_code, cmd, and cmd_length.
|
| 8 |
16 |
RACF command return code |
RACF request
failed. Reason code field contains the return code from the RACF request. See z/OS Security Server RACF Command Language Reference for
information about possible return codes from the RACF commands. In addition, diagnostic output
resulting from the RACF command
may be present. The Out_message_strings parameter should be interrogated
by the caller. |
| 8 |
20 |
ICHEINTY return/reason code |
An unexpected ICHEINTY macro error was encountered
during an extract or extract-next request. The high order halfword
of the reason code contains the ICHEINTY return code and the low order
halfword contains the ICHEINTY reason code. See z/OS Security Server RACF Macros and Interfaces for
ICHEINTY return and reason code documentation. |
| 8 |
24 |
xx |
Unexpected internal error occurred. The value
of xx is an internal code to be used by the IBM® support center. |
z/OS Security Server RACF Callable Services
Copyright IBM Corporation 1990, 2014