The master scheduler dumps for module ADSMVS60, when IPLing after z/OS upgrade,

Products

• Disk Backup and Restore - MVS
• DISK BACKUP AND RESTORE- ADD-ON OPTIO
• DISK BACKUP AND RESTORE

Issue/Introduction

When starting a system with a new level of z/OS, with Disk™ Backup and Restore OPEN SVC Zaps installed, during IPL several tasks abend. The Master Scheduler abends FF4-N/A and the IPL stops, the FF4 abend is caused because the system can not find the module ADSMVS60 during IPL.

Console messages that can be seen are:

IKJ147I IKJEFXSR ABNORMAL TERMINATED
IEE480I SET COMMAND ABEND FF4-N/A
IEE480I SET COMMAND ABEND FF4-N/A
IEFE001I ENF SYSPLEX-WIDE NOTIFIED
IEA794I SVC DUMP HAS CAPTURED:
DUMPID=001 REQUESTED BY JOB (SMF)
...
DUMP TITLE=COMPON=SMF INITIALIZATION, ISSUER=IEEMB827, COMPID=SC100
*3190 IEA793A NO DUMP DATA SETS AVAILABLE FOR
DUMPID=001 BY JOB (SMF ). USE THE DUMPDS COMMAND OR REPLY D TO DELETE THE DUMP
IRA600I SRM CHANNEL DATA NOW AVAILABLE FOR ALL SRM FUNCTIONS
*IEE479W MASTER SCHEDULER ABEND FF4, DUMPED, REIP - CODE 27
IEA794I SVC DUMP HAS CAPTURED:
DUMPID=002 REQUESTED BY JOB (*MASTER*)
DUMP TITLE=COMPON=MSTR-REGION,COMPID=SC1B8,ISSUER=IEEMB860,MAST
ER SCHEDULER REGION INITIALIZATION DUMP
*3191 IEA793A NO DUMP DATA SETS AVAILABLE FOR
DUMPID=002 BY JOB (*MASTER*). USE THE DUMPDS COMMAND OR REPLY D TO
DELETE THE DUMP

Resolution

Make sure that:

1. The Disk OPEN SVC member ADSMVS60 is in the LPA library concatenation.

2. The SVC table has been updated by adding the following line to the IEASVCxx member of your SYS1.PARMLIB:
SVCPARM 244,REPLACE,TYPE(4),APF(NO),EPNAME(ADSMVS60)

3. The number assigned to the OPEN SVC is the same as the value specified in each of the four SVC Zaps installed. The default value in the zaps is x'F4' (d'244') and the instruction in the zaps is '0AF4'.

Generally the problem is the SVC number assigned and following is the explanation.
The IEASVCxx entry is setup to use a different SVC number than SVC 244 (x'F4').
Changing the open zaps to the correct SVC number will solve the problem and permit the system to IPL successfully.

 

NOTE:

If EPNAME(ADSMVS60) is not listed in the IEASVCxx member, it could be a good indication that a very old method was used to install the Disk SVC with name IGC0024D from before Disk R9.  In that case update the customer's Disk SVC installation to specify SVCPARM with EPNAME(ADSMVS60) and copy the current default Disk SVC code in ADSMVS60 from CCUWLPA into their LPALIB concatenation.

If the above has been verified and the client still continues to experience the problem look for 

IEA826I IEASVC3: SVCxxx TYPE x ROUTINE xxxxxxxx NOT FOUND messages.

If there are several of these messages for other modules then this is a good indication that not only is the DISK LPA library not being found but other products and can point to having an incorrect LPALIB concatenation for their IPL.