Have you verified you have updated IEASVCxx with the correct entry? >From the CICS manual
You must define the CICS SVCs in an IEASVCxx member of the SYS1.PARMLIB library, using SVCPARM statements. See the z/OS MVS Initialization and Tuning Guide and z/OS MVS Initialization and Tuning Reference manuals for a description of the SVCPARM statements. If you are using the default SVC numbers, the CICS entries are as follows: SVCPARM 216,REPLACE,TYPE(3),EPNAME(DFHCSVC) SVCPARM 215,REPLACE,TYPE(6),EPNAME(DFHHPSVC) [Only required for HPO] Once that is done and you have installed the DFHCSVC module into the LPA. Everything should work. Next question do you have a version of the DFHHPSVC module from an earlier release of CICS already link-edited into your MVS nucleus, you do not need to replace it with the latest version. Versions of the DFHHPSVC module from earlier releases of CICS are compatible with the current release. The CSECT name (EPNAME) of the version of the DFHHPSVC module from earlier releases is IGC215 (or IGCnnn, if SRBSVC=nnn was used as a CICS system generation parameter in the earlier release). CICS contains a test to verify that it is using the correct level of the CICS DFHCSVC module. If CICS calls an SVC module using the SVC number specified on the CICSSVC system initialization parameter, and the module is not at the current level, CICS issues message DFHKE0104. As a result of this message, CICS either abends with a system dump, or prompts the operator to enter an alternative SVC number, depending on the option specified on the PARMERR system initialization parameter. Lizette ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
