SB78 REASON CODE 0000005C abend at IDMS startup after ALLOWUSERKEYCSA(NO)

Products

• IDMS

Issue/Introduction

As of z/OS 2.4, AllowUserKeyCSA(NO) is compulsory.

Failure to configure IDMS properly for this change can result in an SB78-5C abend at CV startup.

Environment

Release: All supported releases.

Resolution

IDMS must be configured to run in a non-user KEY - that is, one in the range 1 to 7. The recommendation is to use 4. To accomplish this, the following must be done.

1. STEPLIB must be authorized and must contain RHDCTCKR, RHDCCKUR, RHDCOMVS and any other aliases if they are used for RHDCOMVS in the EXEC= statement in the startup JCL (e.g. IDMSDC). The easiest way to achieve this is to include only the IDMS software library, CAGJLOAD, in STEPLIB and authorizing it. It is also possible to create a separate library with only those modules in it (IDMS loads everything else from CDMSLIB), but that just provides an administrative overhead.
   Note: If STEPLIB contains more than one loadlib, then all of those loadlibs must be authorized for the entire STEPLIB ddname to be considered authorized. Note also that there is never any good reason to have more than one loadlib in STEPLIB. See What must be in STEPLIB of an IDMS CV? for a description of the minimum requirements for STEPLIB.
   
   
2. Create a PPT entry in the appropriate SYS1.PARMLIB(SCHED..) member for the startup module identifying the key. For example:
   
   PPT PGMNAME(RHDCOMVS),KEY(4),NOSWAP
   
   
3. Specify STEP=Y on the EXEC= statement in the startup JCL. For example:
   
   //IDMS     EXEC PGM=RHDCOMVS,REGION=0M,TIME=1440,PARM='STEP=Y'

It may also be a good idea to re-create the SVC with CVKEY=4 in #SVCOPT instead of CVKEY=*, but this is not necessary if the SVC was created with #SVCOPT parameter CVKEY=*. If the SVC has been created with an #SVCOPT with CVKEY=n where n is a number, then the SVC will check that the CV is running in that particular key, and if it isn't, the CV will abend with an SEnn abend code where nn is the number of the SVC in hexadecimal. If the SVC has been created with CVKEY=*, no such check is performed. Changing the SVC would only be necessary if it had already been created with CVKEY=n where n is a number other than the one which you specified in the PPT entry.

Additional Information

Storage Key Considerations for z/OS CSA Subpools
IDMS: AllowUserKeyCSA(NO) Frequently Asked Questions