You've applied the necessary z/OS compatibility maintenance to CA Dispatch.
You're attempting to start CA Dispatch after upgrading to z/OS release 2.4 or higher, and you receive a SB78-5C abend in the Dispatch started task.
What caused this abend and how can it be prevented?
The abend is due to the CVKEY used to run the CA Dispatch product and it's related components. By default, the CA Dispatch programs use CVKEY=8.
If DIAGxx parmlib statement VSM ALLOWUSERKEYCSA(NO) is specified, CA Dispatch customer sites MUST change the default storage protection key being used by the Dispatch programs, in order to avoid the SB78-5C abend .
A storage protection key of 0 through 7 can be used in a ALLOWUSERKEYCSA(NO) environment. The ca/Broadcom Dispatch Support team recommends that our customers use a Storage Protection Key of 4 (CVKEY=4) for the Dispatch related programs. Refer to IBM documentation for additional information on Storage Protection Key usage.
Affected CA Dispatch programs are: CAISYS01, XTARMAIN, XTEXMAIN, and any Online Viewing Only (OLVO) region programs such as CAIOLV01, CAIOLV02, etc...
The immediate approach to resolving the SB78-5C abend used to be to set DIAGxx parmlib member with ALLOWUSERKEYCSA(YES). However, this is no longer permitted under current releases of z/OS.
Use the following procedures to change the CVKEY used by CA Dispatch, add the appropriate Program Property Table (PPT) entries, and reload the updated CADSSVC module into memory:
Change the CA Dispatch CVKEY
Above process taken from the CA Dispatch Installation Guide, available for download from the legacy CA Dispatch documentation bookshelf:
- Step 14A - "Change the CA Dispatch CVKEY
- Step 14C - "Load the New SVC"
** NOTE **
- If you are only implementing the CVKEY change, then no IPL is required, and you can Load the New SVC as documented in the resolution section of this article.
- In order to implement any z/OS compatibility changes, (If you are doing this at the SAME TIME as the CVKEY change), you will need to clear the previously loaded CADZSPLx related modules out of memory and reload them. This can be done in either of 2 ways:
1. A system IPL will clear and reload the CADZSPLx related modules.
2. If you are not going to IPL, perform the SVCREDO process as documented in Article Id: 10968