Troubleshooting
Problem
In a very busy zWS environment, where many thousands of jobs may need to be submitted every minute, having extra trackers that just submit jobs can help with throughput
Cause
Performance issue
Resolving The Problem
A tracker can be set up to only SUBMIT jobs but not actually TRACK them. That is, if there is already a zWS tracker running on an LPAR which submits jobs and tracks them, additional trackers can be configured on the same LPAR just to SUBMIT jobs. This is helpful if submit processing is a bottleneck for the TWS configuration.
The only difference in the configuration for a SUBMIT-ONLY tracker is that EWTRTASK is set to
NO instead of YES:
OPCOPTS OPCHOST(NO)
ERDRTASK(0)
EWTRTASK(NO) /* submit only tracker */
NCFTASK(NO)
TRROPTS HOSTCON(XCF)
XCFOPTS GROUP(MAINZ)
MEMBER(TRKV&SMFID.)
The submit-only tracker also needs to be included in the controller ROUTOPTS parameter, along with the other trackers.
It is possible to use multiple Trackers on the same system just for the submission: in this case there must be an EVENT WRITER on ONLY ONE TRACKER on each LPAR, while on the others you need only the the submit task and the communication tasks. You have to define the ROUTOPTS and TRROPTS as if each Tracker was on a different z/OS system.
The workstation definition for a submit-only tracker looks like any other
tracker workstation, for example:
Work station : ECU0
Description : cpu w/s for this controller
Work station type : Computer
Reporting attribute : Automatic
FT Work station : No
Printout routing : SYSPRINT
Server usage : Both
Splittable : No
Job setup : No
Started task STC : No
WTO : No
Destination : XXXXXXXX
Transport time : 00.00
Duration :
The submit-only tracker can have an alternate workstation set up for it just
like any other tracker; so the submit-only workstation can be recovered
in the event that an LPAR is shutdown or has an unplanned outage.
Because any submit only tracker will never consume its WTRQ (as EWTRTASK(NO) is specified)
it is important that the subsystem definition is defined with ZERO as the INITPARM value otherwise
ECSA storage will be wasted.
For example:
Normal tracker with EWTRTASK(YES):
SUBSYS SUBNAME(TT10)
INITRTN(EQQINITO)
INITPARM('100,O')
Submit only tracker with EWTRTASK(NO)
SUBSYS SUBNAME(SUBO)
INITRTN(EQQINITO)
INITPARM('0,O')
The only difference in the configuration for a SUBMIT-ONLY tracker is that EWTRTASK is set to
NO instead of YES:
OPCOPTS OPCHOST(NO)
ERDRTASK(0)
EWTRTASK(NO) /* submit only tracker */
NCFTASK(NO)
TRROPTS HOSTCON(XCF)
XCFOPTS GROUP(MAINZ)
MEMBER(TRKV&SMFID.)
The submit-only tracker also needs to be included in the controller ROUTOPTS parameter, along with the other trackers.
It is possible to use multiple Trackers on the same system just for the submission: in this case there must be an EVENT WRITER on ONLY ONE TRACKER on each LPAR, while on the others you need only the the submit task and the communication tasks. You have to define the ROUTOPTS and TRROPTS as if each Tracker was on a different z/OS system.
The workstation definition for a submit-only tracker looks like any other
tracker workstation, for example:
Work station : ECU0
Description : cpu w/s for this controller
Work station type : Computer
Reporting attribute : Automatic
FT Work station : No
Printout routing : SYSPRINT
Server usage : Both
Splittable : No
Job setup : No
Started task STC : No
WTO : No
Destination : XXXXXXXX
Transport time : 00.00
Duration :
The submit-only tracker can have an alternate workstation set up for it just
like any other tracker; so the submit-only workstation can be recovered
in the event that an LPAR is shutdown or has an unplanned outage.
Because any submit only tracker will never consume its WTRQ (as EWTRTASK(NO) is specified)
it is important that the subsystem definition is defined with ZERO as the INITPARM value otherwise
ECSA storage will be wasted.
For example:
Normal tracker with EWTRTASK(YES):
SUBSYS SUBNAME(TT10)
INITRTN(EQQINITO)
INITPARM('100,O')
Submit only tracker with EWTRTASK(NO)
SUBSYS SUBNAME(SUBO)
INITRTN(EQQINITO)
INITPARM('0,O')
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB70","label":"Z TPS"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSWL3F","label":"IBM Z Workload Scheduler"},"ARM Category":[{"code":"a8m0z0000001epqAAA","label":"ZOS-\u003EIZWS-\u003ETechnote"}],"ARM Case Number":"","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
17 April 2024
UID
ibm17148392