After upgrading the IDMS CV, we get system abend SFF1 at startup. What are the reasons for this abend?

Products

• IDMS
• IDMS - Database
• IDMS - ADS

Issue/Introduction

The System ABEND SFxx (where xx is a hexadecimal number that corresponds to an SVC requested by the abending job) means the requested SVC is not known to the Operating System. In this article, SVC number 241 is used.

There could be several reasons why the IDMS CV could get this error at startup:

1. The IDMS SYSTEM definition in the SYSGEN may have the incorrect SVC number coded.
   
   
2. The security table RHDCSRTT may have the incorrect SVC number coded. Check the #SECRTT
   TYPE=INITIAL,SVCNUM=241
   
   
3. Both the IDMS SYSGEN and RHDCSRTT must have the same SVC number coded, and the CAIRIM job that should have installed the SVC may have gotten an error resulting in the SVC not being loaded. Run the CAIRIM job to install the SVC number.
   
   
4. Verify that the CAIRIM job completed with no errors after the IPL. Check for the following messages:
   
   CAS9115I - INPUT: PRODUCT(CA-IDMS) VERSION(GJG) INIT(GJG0INIT) PARM(SVC=241)
   GJG0INIT - SUCCESSFULLY ADDED SVC 241.
   GJG0INIT - SUCCESSFULLY LOADED RHDCSSFM.
   CAS9130I - MODULE GJF0INIT COMPLETE, RC=00
   
   
5. If the library CAIRIM was using is not APF authorized, CAIRIM will abend. The APFLIB should be authorized. See 7.10.5 Authorization in the IDMS Installation and Maintenance Guide.
   
   
6. Make sure the CAS9SEC is being loaded, run CAIRIM with:
   PRODUCT(CA-SECURITY/INIT) VERSION(S910) INIT(S910INIT)
   PRODUCT(CA-IDMS) VERSION(GJG0) INIT(GJG0INIT) PARM(REFRESH(SVC=241))
   
   By the way, S910INIT loads CAS9SEC into the LPA.
   
   References:
   
   CA IDMS Installation and Maintenance Guide, chapter 7.10 Loading the SVC, chapter 3.2.2 SVC supported; chapter 3.2.3 Common Services for z/OS, chapter 6.2.5 CV Number.
   

Environment

Release:
Component: IDMS