Changing the CSAUSERKEY value whilst IDMS is up is a path fraught with dangers (like reloading a SVC)
Things to doublecheck
Authorize that load library by adding a control statement to the appropriate SYS1.
PARMLIB(PROG..) member, for example, APF ADD DSNAME(my.apflib) VOLUME(vvvvvv).
Update the appropriate SYS1.PARMLIB(SCHED..) member to include the following line:
PPT PGMNAME($STARTUP),KEY(4),NOSWAP
Where $STARTUP
Specifies the CA IDMS/DC startup module name - RHDCOMVS, IDMSDC, or IDMSDCV.
Assure #SVCOPT has either CVKEY=* or the new CVKEY ( we went with 4) (oh yeah, change the sysgen)
Refresh the new SVC with CAIRIM before bring up idms
Chris Hoelscher
Lead Sys DBA
IBM Global Technical Services on assignmemt to Humana Inc.
T 502.476.2538 or 502.407.7266
Original Message:
Sent: 1/12/2021 9:13:00 AM
From: Dan Kolb
Subject: RE: Has anyone applied IBM CSAUSERKEY=yes?
We followed it as well. But the CSAUSERKEY was changed to No while the CVs were up and running as a preliminary step by the ZOS folks and all the CVs abended, some not immediately.
I found that not all the steplibs were authorized, so we corrected that, still abending.
Scheduling another attempt.
Original Message:
Sent: 1/11/2021 5:09:00 PM
From: Chris Hoelscher
Subject: RE: Has anyone applied IBM CSAUSERKEY=yes?
I had to follow this exactly
Chris Hoelscher
Lead Sys DBA
IBM Global Technical Services on assignmemt to Humana Inc.
T 502.476.2538 or 502.407.7266
Original Message:
Sent: 1/11/2021 12:34:00 PM
From: Dan Kolb
Subject: Has anyone applied IBM CSAUSERKEY=yes?
An attempt was made to change the ALLOWUSERKEYCSA from No to Yes this weekend.
All IDMS regions abended with a SB78-5C.
Currently at r19.0 base with plans to go to latest maintenance upgrade in August.