IKYL003I

Explanation
PKI Services LDAP bind
processing is trying to retrieve its LDAP bind information in preparation
for communicating with the LDAP server. The bind information is contained
in either an LDAPBIND class profile or the IRR.PROXY.DEFAULTS profile
in the FACILITY class. Either the profile does not exist or some of
the information is missing or incorrect. The name of the profile in
question is displayed.

System action
PKI Services attempts
to bind to your other LDAP servers, if any. If PKI Services is unable
to bind to any LDAP servers, the LDAP posting of certificates and
CRLs is temporarily suspended. PKI Services attempts
to bind again during the next posting interval. All post requests
remain in the request database to be attempted later, subject to being
deleted after one week of unsuccessful attempts.

System programmer response
Locate the profile name in the PKI Services configuration
file and correct it if needed. If you make corrections, stop and restart PKI Services. If the
profile name is already correct, contact your RACF® administrator. For more information, see (Optional) Steps for updating the configuration file.

RACF administrator
response
Display the PROXY segment of the profile using
the RLIST TSO command. Check the LDAPHOST for accuracy, and correct
it if needed. If non-anonymous access is required, do the same for
the BINDDN and BINDPW. Note: The BINDPW value is not displayed. Respecify
it to ensure that it is accurate.
 To alter the fields, use
the RALTER TSO command. If the profile does not exist, create it using
the RDEFINE TSO command. For more information, see z/OS Security Server RACF Command Language Reference.

Explanation

System action

System programmer response

RACF administrator response