CICS Environment

17.1. Introduction

Customer Information Control System (CICS) is a system for online processing of information. The applications are organized in menus. All CICS online resources (transactions, programs, files, maps, terminals, connections) are previously defined and configured in the CICS environment using special CICS transactions. Information about these resources can be retrieved using the CICS system utility DFHCSDUP. This utility produces a CSD file in text format.

The CSD file contains all defined CICS online resources: files, transactions, programs, maps, connections, etc. Enterprise View performs two different processes on the CSD file. The first one is performed by the Enterprise View MVS Agent on a z/OS or MVS system. This agent processes the sequential file obtained from the CICS utility DFHCSDUP and transforms it into an XML file. The second process is performed on the server machine by Enterprise View. The product processes the XML file to retrieve all the information about defined CICS resources.

Enterprise View analyzes the CICS System Definition file and describes the relationships between the objects listed in the CSD file and the application.

17.2. CICS Online Resource Definition File

You can use the extensions .csd or .CSD for CSD sources, predefined in the Enterprise View Knowledge database, in order for the sources to be properly analyzed and handled by the parser.

Note: It is important to point out that Enterprise View does not directly handle the

output from the CICS system utility DFHCSDUP. The Enterprise View Agent transforms the output from the DFHCSDUP utility to XML format on the mainframe environment.

The analysis type of the CICS CSD files is ‘Extended’. After transferring the CICS CSD file to the Enterprise View server machine and analyzing it, the following information will be extracted:

• Transaction names included in the CSD file.

• Program names included in the CSD file.

• Transaction - Program relationships. Possible problems:

• Transactions not included in the package are loaded as unresolved objects.

• Programs not included in the package are loaded as unresolved objects.

17.3. CICS Map Definitions

A map is a definition of the size, shape, position, potential content, and properties of BMS map sets, maps, and fields within maps, by means of macros. A mapset is

80

Basic mapping support (BMS)

You can use the extensions .map, .mapbms, .MAP or .MAPBMS for map sources, predefined in the Enterprise View Knowledge database, in order for the sources to be properly analyzed and handled by the parser.

There is no specific parser for these objects.

The analysis type of the Map definitions is ‘Disabled’. No metrics are calculated for these objects. They are included in the Enterprise View Repository for inventory purposes only.

The analysis type of the BMS Map definitions is ‘Extended’. Metrics are calculated for these objects.

If, during the analysis of a CICS program, Enterprise View does not find the source of the map definition called by the program, this missing map definition will be stored as an unresolved object.

17.4. CICS COBOL Transactions and Programs

The COBOL transactions and programs running in the CICS environment contain CICS statements.

You can use the extensions .cblcic or .CBLCIC for CICS COBOL sources, predefined in the Enterprise View Knowledge database, in order for the sources to be properly analyzed and handled by the parser.

The analysis type of the CICS COBOL transactions and programs is ‘Extended’. Every embedded CICS statement begins with the phrase EXEC CICS. After this phrase the CICS statement with specific key words follows. The CICS statement ends with the END-EXEC statement. For example:

EXEC CICS START TRANSID('AC01') FROM(ACCTDTLO) LENGTH(DTL-LNG) TERMID(PRTRC) RESP(RESPONSE) END-EXEC.

During the analysis, when the parser meets CICS statements, it starts the CICS analyzer, which retrieves the type of relationships between the programs and the objects found in the CICS statements. At the end of the analysis phase, the gathered information provides the following information:

• Transactions - programs relationships

• Programs - copy books relationships

• Programs - called/caller programs relationships

• Programs - maps relationships

• Programs - transitions relationships

• Programs - queue relationships

This information is available using the References and Browse Object functions of the Enterprise View Tech solution. It is important to point out you can use these functions to identify the line that generates the relationship in the source program. The statement number that indicates the line of source that generates a relationship (i.e. program-file relationship) is always the statement number in which the EXEC CICS statement begins in the original source. For CICS statements in the copy books, the reported statement number is the number of the inclusion in the original source include book.

the following table:

Relationship

Type Related Object

Call Program Read File Name Insert File Name Update File Name Send Map Name Receive Map Name Call Trans Transaction DeleteQ Queue ReadQ Queue WriteQ Queue CancTrans Transaction Unlock File Name CICdelete File Name CIChandle Program CIClink Program CICread File Name CICreadNx File Name CICreadPr File Name CICreceive Map Name CICresetbr File Name CICreturn Transaction CICrewrite File Name CICsend Map Name CICstart Transaction CICstartbr File Name CICwrite File Name CICxctl Program CICendbr File Name CICunlock File Name CICcancel Transaction CICdeleteQTD Queue CICdeleteQTS Queue CICIssueAdd File Name CICload Program CICreadQTD Queue

82

CICrelease Program CICwriteQTD Queue CICwriteQTS Queue