IBM Support

DATASET TRIGGERING description and set up

Troubleshooting


Problem

Need to use DATASET TRIGGERING

Resolving The Problem

TWS DATASET TRIGGERING works by intercepting and examining all SMF DATASET CLOSE records.

To setup TWS DATASET TRIGGERING, complete the following steps:

1. Enable SMF14, SMF15, and SMF64 records on the systems where this function is to work.

2. Compile and install the IBM-provided IEFU83 OPC job- tracking exit (SEQQSAMP member EQQU831).

NOTE: To trigger only when a dataset is closed after creation or update, and not when it is closed after an open for READ (input), set the SRREAD parameter in the EQQEXIT macro in EQQU831 to SRREAD=NO.

NOTE: To filter DATASET TRIGGERs based on the USERID under which the specified dataset is created or modified, if the SMFxxUID field is blank for SMF records on the target system, set the SETUID=parameter of the EQQEXIT macro in the OPC-supplied IEFUJI exit (EQQUJI1) to SETUID=Y.

This will cause the OPC subsystem to set the JMRUSEID to the value found in the ACEEUSRI. SMF will then move this value into the SMFxxUID field where it can be compared by OPC to the value specified in the USERID field of the EQQLSENT macro.

3. Code a series of EQQLSENT macros as described in the "Installation Guide."

4. Compile the macros from step three using the EQQLSJCL member of the SEQQSAMP library.

5. Name the output file EQQDSLST.

6. Place it in the PDS specified by the EQQJCLIB DD statement in the TRACKER start process.

7. The first time a TRACKER is started following an IPL, it automatically attempts to load the EQQDSLST and EQQEVLST, but it is possible to force it to do so at any time by issuing the appropriate command as specified in "Appendex B" of the "Planning and scheduling the Workload" manual.

(In TWSz V8R5 and up, a new method (EDWA) is available to define and distribute the DATASET TRIGGERING criteria to the TRACKERs. See the product documentation for info on this option . Both EQQEVLST and EQQDSLST techniques can be used at the same time).

8. Define SPECIAL RESOURCE ETT TRIGGERS in the OPC CONTROLLER dialog, specifying the dataset names from the EQQLSENT macros as the special resource names.

NOTE: When the steps are all done, whenever any dataset is closed:


a. The IEFU83 exit is called to examine the SMF CLOSE record.
b. The exit invokes the TRACKER subsystem which compares the dataset name and other specifics from the SMF record against the entries in the EQQDSLST.
c. If a match is found, the TRACKER subsystem creates a SPECIAL RESOURCES STATUS CHANGE EVENT RECORD and places it on the WTRQ in ECSA.
d. The TRACKER EVENT WRITER task removes the record from the WTRQ, writes it to the EVENT DATASET and passes it to the CONTROLLER.
e. The CONTROLLER processes the event exactly the same as it would one created using an SRSTAT batch job. The dataset name is compared to the ETT TRIGGER DEFINITIONS, and if a match is made, an occurrence of the specified applicaiton is added to the CURRENT PLAN.

SOLUTION # 37121

.

[{"Product":{"code":"SSRULV","label":"IBM Workload Scheduler for z\/OS"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Not Applicable","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions;Version Independent","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Product":{"code":"SSRULV","label":"IBM Workload Scheduler for z\/OS"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Not Applicable","Platform":[{"code":"","label":"N\/A"}],"Version":"N\/A","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Historical Number

37121

Document Information

Modified date:
13 September 2019

UID

swg21020169