GIM69148S KEY RING xxx ASSOCIATED WITH USERID yyyyyyyy WAS NOT FOUND
search cancel

GIM69148S KEY RING xxx ASSOCIATED WITH USERID yyyyyyyy WAS NOT FOUND

book

Article ID: 244060

calendar_today

Updated On:

Products

ACF2 - z/OS Top Secret

Issue/Introduction

Attempting to set up SMP/E maintenance download batch job. The required certificates are connected to the Keyring. Getting message:

GIM69148S ** KEY RING xxx ASSOCIATED WITH USERID yyyyyyyy WAS NOT FOUND

Environment

Release : 16.0

Component : ACF2 for z/OS

Resolution

The SMP/E output shows the following message :

GIM69148S ** KEY RING AAA ASSOCIATED WITH USERID yyyyyyy WAS NOT FOUND.

The SMP/E job is running under logonid yyyyyyyy based on the ACF9CCCD message:

ACF9CCCD USERID yyyyyyyy  IS ASSIGNED TO THIS JOB - yyyyyyyX

The ORDERSERVER statement points to the Keyring:

keyring="AAA"

When pointing to the Keyring the syntax is ringowner/ringname. Based on the CHCKERT the user certificate is connected to keyring:

Key ring record: AAA                                                          
Key ring name: aaa

Based on the above to address the error,  change your ORDERSERVER keyring= to the following:

keyring="AAA/aaa"

Note that the ringname is case sensitive.

Additional Information

Additional notes to Top Secret sites

The ORDERSERVER definition needs to specify the Keyring label instead of the Keyring name. If the Keyring name is SMPECERT and the Keyring lable is "SMP/E CERTIFICATE", then the keyring= value should be "SMP/E CERTIFICATE". The same applies to the certificate= value.

If the key ring is owned by a user ID other than the ID used to run SMP/E, the key ring name must be prefixed with the associated user ID. The user ID and key ring name must be separated by a forward slash. For example, keyring="YYYYYYY/SMP/E CERTIFICATE".