Question & Answer
Question
All current releases of TWSz include a DIAGNOSE-activated trace of SUBMIT processing. This trace can be used in conjunction with the JCLDBG trace to analyze performance problems in submission of TWSz-scheduled jobs.
Cause
The TWSz JCLDBG trace covers OPERATION START and JCL FETCH AND PREPARATION. The SUBMIT trace described here picks up where the JCLDBG trace ends, covering JOB SUBMIT processing in the DATA ROUTER, SUBMIT, and EVENT WRITER subtasks.
In particular, the SUBMIT TRACE covers the interaction between the TWSz SUBMIT subtask and the JES2.
For details on setting and interpreting the JCLDBG trace, check technote 1252806 at:
>
> http://www-01.ibm.com/support/docview.wss?uid=swg21252806
>
.
SUBMIT TRACING follows the movement of the SUBMIT DQE (Data Queue Element) from the Workstation Analyzer subtask in the CONTROLLER through the SUBMIT SUBTASK for the workstation(s) in question, and the creation of the IJ1 SUBMIT EVENT in the TRACKER subsystem and its transmission to the CONTROLLER. This trace should be used together with the JT logs that contain the TRLTYP25 record logged by the WSA subtask and the TRLTYP29 tracking events logged by the Event Manager.
.
The submit trace can be used for workstations with a BLANK destination, and those connected to the Controller via XCF, NCF, or TCP/IP. It CANNOT be used for TRACKERS connected to the Controller via SHARED DASD.
.
For a workstation with a BLANK destination, the SUBMIT SUBTASK runs in the Controller address space. For workstations with NON-BLANK destinations, the pertinent SUBMIT subtask runs in the Tracker represented by the workstation destination.
Answer
Two new DIAGNOSE flags have been defined to control the new trace:
In the WSA subtask (CONTROLLER):
DIAGNOSE MAJORFLAGS(X'00000004')
In the SUBMIT subtask (CONTROLLER or TRACKER):
DIAGNOSE MAJORFLAGS(X'00000008')
In the EVENT WRITER subtask (TRACKER)
DIAGNOSE MAJORFLAGS('00000008')
To trace ALL submit activity (WSA and SUBMIT subtasks) for a workstation with a BLANK destination (Where both the CONTROLLER and actual SUBMIT processing occur in the CONTROLLER address space, the invocation is:
In the controller parm:
DIAGNOSE MAJORFLAGS(X'0000000C')
To start and stop these traces without restarting the affected TWSz Started task, the following z/OS MODIFY commands can be used:
/F xxxx,SDIAMAJ,FLAG(00000004)
or
/F xxxx,SDIAMAJ,FLAG(0000000C)
or
/F xxxx,SDIAMAJ,FLAG(00000008)
Where "xxxx" is the subsystem name of the CONTROLLER or TRACKER started task
To start the trace both for the controller subtask (xxxx) and tracker (yyyy) use:
/F xxxx,SDIAMAJ,FLAG(0000000C)
/F yyyy,SDIAMAJ,FLAG(00000008)
Where "xxxx" is the subsystem name of the CONTROLLER and "yyyy" is the subsystem name for the TRACKER started task
To stop the trace, use the command:
/F xxxx,EDIAMAJ
/F yyyy,EDIAMAJ
If more than one tracker is involved the tracker commands would have to be issued to
multiple subtasks (i.e. "yyyy", "zzzz", etc )
The trace output will appear in the CONTROLLER and TRACKER EQQMLOGs.
The following is the list of trace entries in chronological order:
1. If the job is scheduled on a workstation with a NON-BLANK destination, the Controller will create an initial trace entry similar to this (If the workstation destination is blank, this entry is not created.):
DXQPR: sending DQE via XCF
+++++
The following entries are created by the SUBMITTING task (either CONTROLLER or TRACKER, depending on workstation destination:
2. Data Router task after receiving the DQE from the communication task,
DXQPR: received DQE from comm task
3. Data Router task before writing the DQE to the SUBQ (submit task queue)
DXHOM: put DQE on SUBQ
4. Submit task in EQQSUSUB beginning with previous user
SUSUB: prev user
5. Submit task in EQQSUSUB if the JCL user is different and there is need to close-open JES reader
SUSUB: new user
6. Submit task in EQQSUSUB before invoking EQQZSUBX that writes the JCL to the JES internal reader
SUSUB: put DQE on JES2 internal reader
7. Submit task in EQQSUSUB after invoking EQQZSUBX that writes the JCL to the JES internal reader
SUSUB: back from JES2 internal reader
+++++
The following entries are always created by the TRACKER on the LPAR where the job is submitted, regardless of workstation destination.
8. Event Writer task while processing the IJ1 event created after the job submission
EWEVH: processing IJ1 event
9. Data Router task after sending the IJ1 event to the Controller (only when XCF is used)
DXQPR: IJ1 sent back to Controller
+++++
Each trace entry has a timestamp to the 1/1000 of a second, and a short hex dump identifying the operation for which it was written.
In instances where it is suspected there may be a performance problem in JES2 ENDREC processing, the most pertinent entries are those listed in items 6 and 7, above. The difference in timestamps of these two records is the time required for JES2 to return a JOBNUMBER to TWSz after accepting the submitted JCL. TWSz cannot submit the next job until it has received the JES JOBNUMBER for the last job submitted.
Was this topic helpful?
Document Information
Modified date:
13 September 2019
UID
swg21424093