The coordinated refresh and coordinated change master key dialogs result in one or more dialog messages indicating the success or failure of the operation. In the case of a failure, there should be enough information in the dialog message to identify the problem. If there is not enough information in the dialog, you must use the ICSF job log to further identify the problem.
During coordinated change master key and coordinated refresh, a sequence of messages are written to the ICSF job log. CSFM622I messages are written to provide status for internal steps taken by the function. For example, one of the very first steps for a coordinated change master key operation is to make a copy of the in-storage KDS that will be used for the subsequent reencipher step. When this copy is made, the following CSFM622I message is written to the ICSF joblog.
CSFM622I COORDINATED CHANGE-MK PROGRESS: NEW IN-STORAGE KDS CONSTRUCTED.
CSFM616I COORDINATED operation FAILED, RC=return-code RS=reason-code
SUPRC=supplemental-return-code SUPRS=supplemental-reason-code
FLAGS=flags.
An explanation of the return
code and reason code provided in the CSFM616I message can be found
in the "Return and Reason Codes" section of the z/OS Cryptographic Services ICSF Application Programmer's Guide.
The rest of the information in this message is IBM internal diagnostic
information.The sequence of messages written to the ICSF job log during a coordinated change master key and coordinated refresh should indicate how far along the function progressed, and, if a failure occurred, should include enough diagnostic information to determine the cause of the problem. Use the CSFM622I messages to determine how far along the function progressed before the failure. Then use the failure messages to determine why the problem occurred.