Here are the steps for changing the SVC number of the CA Disk Open SVC from 252 to 230:
1) Restore the Usermods of the 4 Open SVC Zaps via SMP/E.
2) Update the 4 Open SVC Zaps to the new SVC number
Note: The Open SVC Zaps are delivered for SVC number x'0AF4' (244)
So you need to change these Zaps to refer to SVC number x'0AE6' (230)
3) Reapply the 4 Open SVC Zaps via SMP/E
Please see these sample USERMOD members in the CCUWJCL lib -
and consider to double-check via following DUMPT:
//DUMPT EXEC PGM=AMASPZAP
//SYSPRINT DD SYSOUT=*
//SYSLIB DD DSN=SYS1.LPALIB,DISP=SHR
//SYSIN DD *
DUMPT IFG0194A IFG0194E
DUMPT IGC0001I IFG0196W
DUMPT IGGDADSM IGGDAU01
DUMPT IGC00020 IFG0201R
4) Update the CA Disk entry in the active IEASVCnn member in SYS1.PARMLIB to point to SVC 230, for example:
SVCPARM 230,REPLACE,TYPE(4),APF(NO),EPNAME(ADSMVS60) /*DISKOS*/
6) Run a DMSTEST job to verify the hooks are in place.
Once you have the 4 Open SVC Zaps correctly installed to the 4 IBM modules/Csects, an open of a non-VSAM data set will branch to our ADSMVS60 module.
Using a jobname of DMSTEST will activate a diagnostic facility within the SVC that displays applicable data used to determine if DSCB updates are to be made to maintain fields within the DSCB. That means, if our ADSMVS60 module is processed via a job named DMSTEST it will produce corresponding diagnostic messages.
Note: IEFBR14 does not open a dataset. You may try for example with an IEBGENER.