IMS Connectivity in an On Demand Environment: A Practical Guide to IMS Connectivity

170 IMS Connectivity in an On Demand Environment: A Practical Guide to IMS Connectivity

Figure 11-8 Set System Definition panel

The Tracing Level field enables you to activate and set the level of tracing for IMS Connect

Extensions. It writes the tracing records to the Active Journal data set, from where they are

archived to the Archive Journals.

The acceptable field values are:

 0: No tracing records are written.

 1: Basic tracing records are written (OTMA, IRM, and RSA data).

 2: In addition to the basic tracing information, client application data is written to the trace

records.

11.2.4 Event Collection print utility

The IMS Connect Extensions print utility, CEXEVTPR, prints summary and detailed event

records. It produces report output of formatted IMS Connect Extensions event records. You

set the level of detail to print.

The IMS Connect Extensions print utility accepts input from one Active Journal or Archive

Journal data set.

Example 11-6 shows a sample JCL and the commands needed to request a report from the

print utility.

Example 11-6 Sample JCL to run IMS Connect Extensions print utility

//userid JOB (ACCOUNT),

//* IMS Connect Extensions Print Utility

//CEXEVTPR EXEC PGM=CEXEVTPR,REGION=8M,

Note: The SET command allows temporary changes. If you recycle IMS Connect, the

tracing level is set to 0 again.

Chapter 11. IMS Connect Extensions 171

// PARM=’D’

//STEPLIB DD DISP=SHR,DSN=CEX.V1R1M0.SCEXLINK

// DD DISP=SHR,DSN=FUN.V1R1M0.SFUNLINK

//EVNTIN DD DISP=SHR,DSN=journal.data.set

//SYSUDUMP DD SYSOUT=*

//MSGOUT DD SYSOUT=*

/*

IMS Connect Extensions print utility, CEXEVTPR, has a parameter to specify the type of

report to be written. The acceptable values are:

 T: Transaction summary report

 D: Transaction detail report

Transaction summary report

Example 11-7 shows output for the transaction summary report for a commit mode 1, sync

level none transaction.

The amount of data shown on the report varies depending on the collection level defined. In

this case, we use collection level 4 to produce the most output.

Example 11-7 Print utility transaction summary report

ID=3C,060, V=01, TSKID=0105, KEY=BD2BAD70AD2B6765, PREPARE READ SOCKET

ID=49,073, V=01, TSKID=0105, KEY=BD2BAD70AD2B6765, READ SOCKET

ID=3D,061, V=01, TSKID=0105, KEY=BD2BAD70AD2B6765, MSG EXIT ENTERED

ID=3E,062, V=01, TSKID=0105, KEY=BD2BAD70AD2B6765, MSG EXIT RETURN

ID=41,065, V=01, TSKID=0103, KEY=BD2BAD70AD2B6765, MSG SENT TO OTMA

ID=42,066, V=01, TSKID=0103, KEY=BD2BAD70AD2B6765, MSG RCV FROM OTMA

ID=42,066, V=01, TSKID=0103, KEY=BD2BAD70AD2B6765, MSG RCV FROM OTMA

ID=3D,061, V=01, TSKID=0105, KEY=BD2BAD70AD2B6765, MSG EXIT ENTERED

ID=3E,062, V=01, TSKID=0105, KEY=BD2BAD70AD2B6765, MSG EXIT RETURN

ID=4A,074, V=01, TSKID=0105, KEY=BD2BAD70AD2B6765, WRITE SOCKET

ID=0C,012, V=01, TSKID=0105, KEY=BD2BAD70AD2B6765, BEGIN CLOSE SOCKET

ID=0D,013, V=01, TSKID=0105, KEY=BD2BAD70AD2B6765, END CLOSE SOCKET

ID=48,072, V=01, TSKID=0105, KEY=BD2BAD70AD2B6765, TRIGGER EVENT

This report enables you to follow the message processing flow in IMS Connect, in this case,

the same flow introduced in Example 11-3 on page 168.

The transaction summary report displays the following fields:

 ID

The ID identifies the event record number. This is displayed in hexadecimal and decimal

formats.

 V

The V identifies the version of IMS Connect Extensions.

 TSKID

The TSKID identifies the task in which the event occurred.

 KEY

The event key. This is either EVNT for Connect status event records or the token key for

message related event records.

You use the event key to identify all the events related with a transaction. In Example 11-7,

you can see that every event has the same key.