z/OS Language Environment Customization
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Add program resource definitions for CICS

z/OS Language Environment Customization
SA38-0685-00

Update the CICS® system definition (CSD) file using the program definitions in the CEECCSD member in the Language Environment® sample (SCEESAMP). This member contains the necessary input to the CSD file utility program to define the Language Environment library routines to the CSD. The CSD group list that is used during CICS startup must include the CSD group that is associated with the Language Environment library routines. The group name for Language Environment routines is CEE in the sample CEECCSD.

For COBOL users, the OS/VS COBOL library routines (ILBOs) in Language Environment library SCEERUN are loaded by the operating system and do not require entries in the CSD.

Start of change The XPLINK program definitions in the CEECCSDX member, in the Language Environment sample (SCEESAMP) must be used to update the CICS system definition (CSD) file. Use the CEECCSDX member in addition to the CEECCSD member. End of change

Start of change If you plan to run with program autoinstall and use the Language Environment CLER transaction, you must define the following statements using the CEDA transaction:
DEFINE PROGRAM(CEL4RTO) GROUP(CEE) LANGUAGE(ASSEMBLER)
EXECKEY(CICS)
DEFINE MAPSET(CELCLEM) GROUP(CEE)
DEFINE MAPSET(CELCLRH) GROUP(CEE)
DEFINE TRANS(CLER) PROG(CEL4RTO) GROUP(CEE)
End of change

Tip: If you use program autoinstall, Language Environment event handler modules in the range CEEEV001-CEEEV017 that are present in the CEE.SCEERUN might load during CICS/LE initialization, depending on the definitions in the CICS CEECCSD member and the autoinstall program. You can remove program definitions from the CEECCSD member to prevent them from being loaded during CICS/LE initialization. However, if autoinstall is active, the missing definitions from the CEECCSD are loaded dynamically unless the autoinstall program is modified to bypass any Language Environment modules that you do not want loaded.

To prevent this from occurring, you should start CICS with PGAIPGM=INACTIVE in the CICS SIT. To take advantage of the program autoinstall feature, you can create a PLTPI program to perform a CICS SET SYSTEM PROGAUTOINST (auto_active/cvda) to enable the feature for use later on in initialization. The URM can also be set in the same PLTPI program through the same SET SYSTEM command with the PROGAUTOEXIT parameter. If you do want to run with the autoinstall program, you can modify the autoinstall exit program to bypass any CEEEV0* modules that you do not want loaded.

The following autoinstall exit sample demonstrates this procedure:
DFHPGADX CSECT
DFHPGADX AMODE 31
DFHPGADX RMODE ANY
DFHREGS ,
*
*        If there is no commarea, return
OC    EIBCALEN,EIBCALEN
BZ    RETURN0
*
*        Address the commarea
L     R2,DFHEICAP
USING PGAC,R2
*
*        Omit autoinstall for Language Environment modules
CLC   PGAC_PROGRAM(6),=C''CEEEV0''
BE    RETURNDD
*
*        Add user specific code here
*
*        Set the return code to OK
RETURNOK DS    0H
MVI   PGAC_RETURN_CODE,PGAC_RETURN_OK
B     RETURN0
*
*        Branch to this label if you elect not to define
*        the program
RETURNDD DS    0H
MVI   PGAC_RETURN_CODE,
PGAC_RETURN_DONT_DEFINE_PROGRAM
*
RETURN0  DS    0H
EXEC CICS RETURN,
END   DFHPGADX
Table 1. Excluding programming language support under CICS
If you do not run Exclude these program definitions from the CEECCSD sample job
COBOL applications under CICS Start of change CEEEV004 End of change, CEEEV005, IIGZMSGT, all programs that start with IGZ
C/C++ applications under CICS CEEEV003, IEDCMSGT, all programs that start with EDC or CEU
PL/I applications under CICS (Also VA PL/I) CEEEV010, CEEEV011, IIBMMSGT, all programs that start with IBM®

Guideline: If you use autoinstall and want to exclude one or more languages using this technique, be sure to implement these changes in your autoinstall exit to prevent them from being added dynamically.

Note: C was named AD/Cycle C/370™ before C++ was added. The sample JCL used the nickname C/370 to refer to either Language Environment-enabled version.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014