Possible causes of protection exceptions referencing CICS DSAs
The following list summarizes some of the causes of protection exceptions that can occur in user key programs
- Issuing an MVS™ macro request. Most MVS macros and services are not supported in EXECKEY(USER) application programs. Use of unsupported macros and services might cause a failure if these macros or services attempt to reference MVS storage outside the CICS DSAs.
- Referencing storage that is obtained by an MVS GETMAIN request or another MVS macro. MVS storage that is obtained by these methods resides outside the CICS DSAs, and is therefore protected from user key programs.
- Using PL/I statements, COBOL verbs or compiler options that are
not permitted in CICS application programs (see Developing applications for details of prohibited language
statements and compiler options). For example, the use of CALL with
the RES compiler option, or a verb such as INSPECT, might also cause
MVS storage outside the CICS DSAs to be obtained or updated (such
storage is protected from user-key programs).
In previous releases of CICS, these might have worked, or at least might not have caused the application to fail. However, the use of these statements and options can have other effects on the overall execution of the CICS system, and should be removed where possible.
- Modifying the CWA when CWAKEY=CICS is specified as a system initialization parameter. In a user key program, this is an invalid reference to storage allocated from the CDSA or ECDSA.
- Modifying the TCTUA when TCTUAKEY=CICS is specified as a system initialization parameter. In a user key program this is an invalid reference to storage allocated from the CDSA or ECDSA.
- Issuing EXEC CICS EXTRACT EXIT command and attempting to update
an exit program’s global work area. In a user key program this is
an invalid reference to storage allocated from the CDSA or ECDSA.
Note: If you are using CSP/AD, CSP/AE, or CSP/RS, you must ensure that the definitions for programs DCBINIT, DCBMODS, DCBRINIT and DCBNCOP specify EXECKEY(CICS). These are all examples of programs that modify global work areas that are set up by global user exit programs.
- If you are using DB2 and you use the DB2 message formatting routine DSNTIAR, which is link-edited with your application programs, you should apply the PTF for DB2 APAR PN12516, and relink-edit the applications using DSNTIAR so that they can run in user key. If the applications are not re-link-edited after this PTF is applied, they will have to run in CICS key. As a first step, until you have applied this PTF, you can define the applications which use DSNTIAR with EXECKEY(CICS).