How does ESP process job tracking from one Master to another Master using TP Server?

Products

• ESP Workload Automation

Issue/Introduction

How does ESP process job tracking from one Master to another Master using TP Server?

Resolution

In a Master to Master configuration, when LU6.2 is specified on the ISCOPT statement in the initialization parameter as the mode of communication, the following takes place:

SMF data is intercepted and the XMTMDL is checked to verify where the data should be sent. Once this is determined, control is passed to the Inter System Cross Tracking Data Transmitter (module JS121), and the XME is written to the TP CHKPT. JS121 creates and schedules a TPAR to send the XME to its target ESP system. This XME is retained until notification is received from TP-Server that transmission was successful. At that point the XME storage is released.

Control is then passed to the Cross Tracking Data Transmitter Monitor(module JS122), which is attached as a thread to each XME. Its purpose is to monitor the TPAR transmission for its completion, while keeping a look-out for any return codes.

JS122 calls the Inter Application Transmission API (module TP000). This module builds the TPAR and places it on the work Queue, before calling TP001. TP001 (the Inter Application Transmission Server Mainline), is the main control point of the transmission subtask, whose purpose is to initiate the CNOS transmission.

From This point, VTAM takes control. It connects with VTAM on the other system, and the transmission is performed. At the other end, TP001 task takes control of the information being received, and queues the Inter System Data Receiver (module JS118), who writes the XMEs to the TP CHKPT and to an XME queue. A post is then made to the tracking manager (module JS82) to pickup the XMEs and perform its updates.