z/OS Assembler EXEC CICS commands

---

This page shows, with small examples, the objects that the extension creates for the EXEC CICS commands that use a CICS resource: a transient data (TD) queue, a file, a transaction or a map. Each command produces one object, named after the resource, child of the program (or of the copy member) that holds it, with a link from it. Universal Linker then links each of these objects to the CICS resource of that name.

The examples come from the program CICSPGM.asm.

TD queue commands

WRITEQ TD, READQ TD and DELETEQ TD commands produce one object each. The queue name is a literal, or the DC constant of a data area such as QNAME:

In CAST Imaging:

WRITEQ TS QUEUE('TSQ1') uses a temporary storage (TS) queue: it creates nothing, since Universal Linker links no TS queue. A command without the TD option uses a TS queue, as CICS does.

File commands

READ, WRITE, REWRITE and DELETE commands produce one object each. STARTBR, READNEXT and READPREV produce one browse object each. The file is named by the FILE option or by its synonym DATASET:

In CAST Imaging:

The constant CL8'HISTFILEXX' is 8 characters long, so the file name is HISTFILE.

Transaction commands

START, RETURN and CANCEL commands with a TRANSID option produce one object each:

In CAST Imaging:

A RETURN without TRANSID creates nothing.

Map commands

SEND MAP and RECEIVE MAP commands produce one object each. The object keeps the mapset of the MAPSET option. When the command has no MAPSET option, the mapset is the map name, which is what CICS assumes:

In CAST Imaging:

SEND TEXT and SEND CONTROL use no map: they create nothing.

How the resource name is read

The name of the resource is read from the argument of the command option:

• a literal, such as FILE('CUSTFILE'), or a literal constant, such as FILE(=CL8'CUSTFILE');
• a data area of the program defined by a DC constant, such as QUEUE(QNAME) with QNAME DC CL4'TDQ2'. Trailing blanks are removed, and the constant is cut to its length;
• a data area defined in a copy member that the program copies;
• for a command of a copy member, a data area of the program that copies it.

When the name cannot be found, the command creates nothing, and the analysis log shows the warning ASMZOS-005. This is the case for a data area without a DC constant, or with a value set at run time. An argument with a variable symbol, such as FILE(&FNAME), creates nothing either.

Data area of a copy member

CICSPGM.asm copies CICSCONS.asm, which defines the data area CONSNAME:

CICSCONS.asm:

In CAST Imaging:

Data area of the program that copies the copy member

CICSPGM.asm copies CICSFRAG.asm, whose command uses the data area FRAGQ of CICSPGM.asm:

CICSFRAG.asm:

CICSPGM.asm:

In CAST Imaging:

The TDQF object is a child of the copy member CICSFRAG.

Data area without a constant

BADNAME has no DC constant: its value is only known at run time. The command creates nothing, and the analysis log shows the warning ASMZOS-005:

Commands of a copy member

The EXEC CICS commands of a copy member used by a COPY statement produce objects that are children of the copy member, with a link from it. CODEPGM.asm copies CODECPY.asm (see Links from the code of a copy member), which also holds these commands:

In CAST Imaging:

The commands of a macro file create no object: a macro definition is only a model of the code it generates. Its EXEC CICS LINK, XCTL and LOAD commands are still linked to their program, as shown below.

EXEC CICS LINK and XCTL to a program

EXEC CICS LINK, XCTL and LOAD with a PROGRAM(data area) option are linked to the program named by the DC constant of the data area, like a CALL. SUBNAME names CICSSUB.asm, an Assembler program of the same analysis. COBNAME names CICSCOB, which is not part of the analysis:

CICSSUB.asm:

In CAST Imaging:

The same is found in the IBM MQ sample program CSQCSPLT.asm, where CSQCQCON is not part of the analysis:

In CAST Imaging:

A quoted name, such as PROGRAM('CICSSUB'), is linked the same way.

Links to the CICS resources

These cross-technology links are created by Universal Linker, not by this extension. Universal Linker matches the name of each command object, case-sensitively, with the CICS resources that the Mainframe Analyzer creates from the CSD definitions and the BMS map sources of the application. A map command is matched by its map name and its mapset.

For example, the commands of CICSPGM.asm above are linked to the resources of this CSD extract:

and of these BMS maps:

In CAST Imaging:

The SEND MAP(‘MAP2’) command has the mapset MAP2, which is not defined: it stays unresolved.