The CICS (customer information control system) commands you can’t execute alone. For those workable, you need to embed in COBOL, PL/1, Assembler language. It is custom in Mainframe projects.
In any programming language, after coding, you need to compile it – to know syntax errors. In the case of CICS, the approach is different. Here are the five key steps to follow for CICS programs.
A Step-by-Step Approach to Develop CICS Program
- When you develop a CICS program, you embed CICS commands within another programming language like COBOL, PL/I, or assembler language.
- Before a CICS program can be compiled, it must be translated into the base programming language. This is done by the CICS translator.
You can’t run CICS program in Batch JCL. The reason is CICS run under CICS subsystem. So, CICS program load modules you can’t run in JCL
- For a CICS/COBOL program, the CICS translator converts CICS commands to COBOL Move and Call statements that can be compiled by the COBOL compiler.
- After a CICS program is translated, it is compiled and link edited just like any other source program.
- CICS programs run under the CICS subsystem, not as OS/390 batch jobs. As a result, you can’t run CICS load modules with JCL.
Get new content delivered directly to your inbox.