Generating system flow reports

This topic explains how to generate System Flow reports from within the mainframe component of Code Coverage. It also includes an example CICS report with an explanation of the data found there.

Important

System Flow data shows the logical relationships between transactions and programs, but is not intended to be a transaction trace. Consequently, if program A calls program B multiple times during the execution of a transaction, only one occurrence of this relationship will be reported.

The section provides information about the following topics:

System Flow Reports screen

The System Flow Reports screen shown in the following figure is accessed by entering option 2 on the Primary Menu. This screen is used to generate reports that detail the logical relationships between transactions and programs during the execution of your CICS transactions.

Press Enter to process any information in the screen fields and submit the job to generate a System Flow report. Use the END command (default PF3) to return to the Primary Menu without generating a report.

Reports can be run in foreground or batch mode. If the reports are run in the foreground, the output is directed to the terminal. When viewing of these foreground reports is complete, a Report Disposition screen is displayed that gives you the option of deleting the report, printing the report, or saving the report on disk. If the reports are run in batch, the Job Information screen determines the attributes of the output.

System Flow Reports Screen

------------------------- SYSTEM FLOW 17.02 - REPORTS ------- Row 1 to 1 of 1
Command ===>                                                  Scroll ===> CSR
  Line Commands:                       Primary Commands:
  I (Insert new report),               SEtup , DEL (Delete), ACT (Activate),
  D (Delete), A (Activate),            SUS (SUSpend), SUBmit , Edit (JCL),
  S (Submit), P (Suspend),             RUN (Online report),
  R (Run online report)                END (Exit and save),
                                       CANcel (Exit without saving)

Suppress Recurring headers    ===> Y ( Y / N )

CMD Status     System name      Test ID          User ID
_ ACTIVE     ROITEST1
******************************* Bottom of data ********************************

Line commands

The line commands displayed are defined as follows:

Line command	Description
I	Insert (add) a System flow report request.
D	Delete a System flow report request.
A	Activate a system flow report that was previously suspended.
S	Submit a System flow report request for batch processing for this line.
P	Suspend a System flow report that was previously active.
R	Enables a user to run a System flow report request online, and then browse the output.

Primary commands

The primary commands displayed are defined as follows:

Primary command	Description
SEtup	Modifies the global default values, including repository data sets and jobcards.
DEL	Deletes all System Flow reports in the ISPF table and inserts one new request.
ACT	Marks all System Flow report requests active.
SUS	Marks all System Flow report requests as suspended (suspnded).
SUBmit	Submits a System Flow batch job using all entries marked active.
Edit	Creates JCL for batch processing and repositions you into ISPF edit.
RUN	Invokes the report program for processing all entries marked as active.
END	Exits the display and saves all changes.
CANcel	Exits the display without saving any changes.

Suppress Recurring headers

Code Coverage System Flow reports show headers as if they are printed on paper (headers repeating after every 50-55 lines). Entering an option ‘Y’ will allow headers being displayed only on the '1st page' of the report. The default option of ‘N’ will keep displaying the headers at regular intervals.

Input fields

The input fields displayed are defined as follows:

Input field	Description
CMD	Specifies one of the six available line commands next to the system name you want to affect. See Line Commands for details of each command that can be entered in this field.
Status	A protected field indicating the active or suspended (suspnded) status of a repository program report. This field cannot be edited.
System name	Specifies the system name for which the System Flow report is to be generated. More than one system name can be specified by using additional lines. This field is limited to 15 characters in length and is subject to wildcard rules.
Test ID	Specifies the name of the test ID for which the System Flow report is to be generated. This field is limited to 15 characters in length and is subject to wildcard rules.
User ID	Specifies the user ID of user for which the System Flow report is to be generated. This field is limited to eight characters in length and is subject to wildcard rules.

Sample System Flow report

An example of a system flow hardcopy batch report is shown in the following figure:

Sample System Flow Report

06/08/2015                                    BMC AMI DEVX CODE COVERAGE 17.02                                 PAGE      1
                                                    REPORT SELECTION CRITERIA
REPORT SELECTED:                    SYSTEM FLOW REPORT
REPORT REQUEST-> SYSTEM: SF                  TEST ID: XVST             USER ID: ALL
REPOSITORIES:                       ACMJET0.XVTC.REPOSIT

                        ************************************************************
                        *                     ---- NOTICE ----                     *
                        * SYSTEM FLOW REPORTING SHOWS THE LOGICAL RELATIONSHIPS    *
                        * BETWEEN TRANSACTIONS AND PROGRAMS. IT DOES NOT REFELECT *
                        * REPETITIVE CALLS.                                        *
                        ************************************************************
06/08/2015                                    BMC AMI DEVX CODE COVERAGE 17.02                                 PAGE      2
                                                        SYSTEM FLOW REPORT
                              FOR SYSTEM=SF                TESTID=XVST              USERID=ACMJET0
TRAN OR   LOAD      FROM                      LOAD      TO                 ------COMPILE------   ------COLLECTION-------
PROGRAM   MODULE    SYSID ACTION   PROGRAM   MODULE    SYSID   LANGUAGE      DATE      TIME        DATE        TIME
-------- -------- ----- ------   -------- -------- ----- ---------- ---------- --------   ---------- ------------
TRN=XVTC            C093   INITAL   XVSTCDRV XVSTCDRV C093   ZOS COBOL   07/14/2014 08:18:47   06/07/2015 19:25:04.625
XVSTCDRV XVSTCDRV C093   STATIC   XVSTINLE XVSTCDRV C093   HLASM       07/14/2014 08:13:00   06/07/2015 19:25:04.627
XVSTCDRV XVSTCDRV C093   LINK     XVSTCX01 XVSTCX01 C093   ZOS COBOL   07/14/2014 08:18:41   06/07/2015 19:25:08.964
XVSTINCM XVSTCDRV C093   STATIC   XVSTINLE XVSTCDRV C093   HLASM       07/14/2014 08:13:00   06/07/2015 19:25:04.628
XVSTINLE XVSTCDRV C093   STATIC   XVSTINCM XVSTCDRV C093   HLASM       07/14/2014 08:13:00   06/07/2015 19:25:04.627
XVSTCX01 XVSTCX01 C093   LINK     XVSTCX02 XVSTCX02 C093   ZOS COBOL   07/14/2014 08:18:35   06/07/2015 19:25:09.246
XVSTCX02 XVSTCX02 C093   LINK     XVSTCX03 XVSTCX03 C093   ZOS COBOL   07/14/2014 08:18:30   06/07/2015 19:25:09.568
XVSTCX03 XVSTCX03 C093   LINK     XVSTCX04 XVSTCX04 C093   ZOS COBOL   07/14/2014 08:18:24   06/07/2015 19:25:09.774
XVSTCX04 XVSTCX04 C093   LINK     XVSTCX05 XVSTCX05 C093   ZOS COBOL   07/14/2014 08:18:18   06/07/2015 19:25:09.993
******************************** BOTTOM OF DATA ***********************************************************************************

System flow report heading explanations

The following are explanations of each of the columns in the System flow report:

Heading	Explanation
Report selected	This indicates that this is a System Flow report.
Report request	This reflects the system, test ID, and User ID of the report requested from the System Flow reports screen. There will be one entry here for each report requested from the System Flow Reports screen.
Repositories	This reflects the Code Coverage repositories that were supplied on the Code Coverage repositories screen. One to nine repositories may be listed here. If System Flow data for the selected system name, test ID, and user ID is contained on more than one repository, the data from all repositories will be combined into a single report. To report on data from a single repository, specify only that repository on the Code Coverage repositories screen and rerun the report.
Notice	This notice is meant to highlight that the System Flow reporting is not a transaction trace. If repetitive calls are made to a calling program only the first occurrence of that call will be reported. The notice will appear on each report.
TRAN OR PROGRAM	For CICS transaction records, this will contain the literal TRN- followed by the 4-byte transaction code (for example, TRN-XVTC). For program records, this will contain the name of the calling program (CSECT).
LOAD MODULE	This is the load module that contains the calling program.
FROM SYSID	This is the 4-byte CICS system identification of the CICS region where the calling program is executing.
ACTION	This field is the type of call that the calling program is using to invoke the called program. The possible entries for the ACTION field are LINK for EXEC CICS LINK, XCTL for an EXEC CICS XCTL, STATIC for a static call, DYNAM for a dynamic call, or INITIAL for the first program collected in a CICS transaction. If the type of call could not be determined, the ACTION field will contain ERROR. Important A program listed as INITIAL might not be the first program given control by CICS when executing a transaction. This is because System Flow collection masks on the Test Definition/Collection Specification screen can limit which programs System Flow “sees” during collection for a transaction.
PROGRAM	This field is the called program (CSECT).
LOAD MODULE	This is the load module that contains the called program.
TO SYSID	This is the 4-byte CICS system identification of the CICS region where the called program is executing.
LANGUAGE	This is the language of the called program. The language could be any language supported by CICS.
COMPILE DATE/TIME	This is the compile date and time from the BMC language processors of the called program. Is it not required that a program have a BMC source listing to be collected for System Flow. Therefore the compile date and time in the report may be blank.
COLLECTION DATE AND TIME	This field is the collection date and time of the System Flow record. This is expressed as a Coordinated Universal Time, formerly known as Greenwich Mean Time (GMT).