| 0 |
0 |
0 |
The service was successful. |
| 4 |
0 |
0 |
RACF is not installed. |
| 8 |
8 |
0 |
Invalid function code. |
| 8 |
8 |
4 |
Parameter list error. |
| 8 |
8 |
8 |
An internal error was encountered. A record
may be written to LOGREC with more diagnostic information. |
| 8 |
8 |
12 |
A recovery environment could not be established. |
| 8 |
8 |
16 |
Not authorized to use this service. |
| 8 |
8 |
20 |
The LDAP Server address space has not been started
or is terminating, or the PC interface has not been started. |
| 8 |
8 |
24 |
Unable to decode the data retrieved from LDAP.
A record is written to LOGREC with more diagnostic information. |
| 8 |
8 |
28 |
Unable to determine BIND information for LDAP. |
| 8 |
8 |
32 |
Function not supported for problem state caller. |
| 8 |
12 |
8 |
LDAP Server invocation failed-parameter buffer
overflow. This indicates an internal error in IRRRPY00. |
| 8 |
12 |
12 |
LDAP Server invocation failed-unable to allocate
storage. The region size for the LDAP Server program should be increased. |
| 8 |
12 |
16 |
LDAP Server invocation failed-LDAP PC handling
is not enabled. |
| 8 |
12 |
20 |
LDAP Server invocation failed-abend in the PC
service routine. The symptom record associated with this abend can
be found in LOGREC. |
| 8 |
12 |
24 |
LDAP Server invocation failed-no control area
(internal error). Report the problem to the IBM® support center and provide an SVC dump of
the LDAP Server address space. |
| 8 |
12 |
36 |
LDAP Server invocation failed-the LDAP Server
is busy. Retry the operation. |
| 8 |
12 |
40 |
LDAP Server invocation failed-PC request processing
was terminated before completion (the PC catcher initiated the termination).
This indicates either an internal error in IRRRPY00 or that the LDAP
Server is terminating. If the LDAP Server is terminating, restart
it and retry the operation. |
| 8 |
12 |
44 |
LDAP Server invocation failed-PC request processing
was terminated before completion (the server agent initiated the termination).
This indicates either an internal error in IRRRPY00 or that the LDAP
Server is terminating. If the LDAP Server is terminating, restart
it and retry the operation. |
| 8 |
12 |
52 |
LDAP Server invocation failed-a lock could not
be obtained. This indicates either that the LDAP Server is busy or
that an internal error is preventing it from processing requests.
If the LDAP Server is not busy, report the problem to the IBM support center and provide an
SVC dump of the LDAP Server address space. |
| 8 |
16 |
nn |
The requested function was not successful. The RACF reason code code is set to
the return code from LDAP. See z/OS IBM Tivoli Directory Server Administration and Use for z/OS for
more information about LDAP return codes. For reason codes other than
32, a record is written to LOGREC containing the LDAP reason string.
No record is written for reason code 32, which indicates that the
requested information does not exist in the LDAP directory. |
| 8 |
20 |
40 |
Invalid BIND password information was found
in either the PROXY segment of the invoker's USER class profile, or
in the PROXY segment of the IRR.PROXY.DEFAULTS profile in the FACILITY
class. |
| 8 |
20 |
44 |
RACF was
unable to retrieve or update the master key/master key token in the
SSIGNON segment of the LDAP.BINDPW.KEY profile in the KEYSMSTR class. |
| 8 |
20 |
52 |
RACF cannot
locate the CCA support routine. |
| 8 |
20 |
56 |
The invocation of the CCA support routine has
failed. |
z/OS Security Server RACF Callable Services
Copyright IBM Corporation 1990, 2014