Building CICS applications
To build an application for WebSphere MQ for z/OS that runs under CICS(R), you must:
- Translate the CICS commands in your program into the language in which
the rest of your program is written
- Compile or assemble the output from the translator to produce object code
- Link-edit the object code to create a load module
CICS provides a procedure to execute these steps in sequence for each
of the programming languages it supports.
- For CICS Transaction Server for OS/390, the CICS Transaction Server for OS/390 System Definition Guide describes
how to use these procedures and the CICS/ESA(R) Application Programming Guide gives more information on the translation process.
You must include:
- In the SYSLIB statement of the compilation (or assembly) stage, statements
that make the product data definition files available to the compiler. The
data definitions are supplied in the following WebSphere MQ for z/OS libraries:
- For COBOL, thlqual.SCSQCOBC
- For assembler language, thlqual.SCSQMACS
- For C, thlqual.SCSQC370
- For PL/I, thlqual.SCSQPLIC
- In your link-edit JCL, the WebSphere MQ for z/OS CICS stub program (CSQCSTUB). Figure 22 shows
fragments of JCL code to do this. The stub is language-independent and is
supplied in library thlqual.SCSQLOAD.
When you have completed these steps, store the load module in an application
load library and define the program to CICS in the usual way.
Before you run a CICS program, your system administrator must define
it to CICS as a WebSphere MQ program and transaction, You can then run it in the
usual way.