Defining your ETT criteria

About this task

Follow these steps to specify ETT criteria:
  1. Specify option 1 (DATABASE) on the main menu.
  2. Specify option 7 (EDWA) on the MAINTAINING DATA BASES menu.
  3. Specify option 2 (MODIFY) on the MAINTAINING EVENT TRIGGERED TRACKING menu.
    Figure 1. EQQJMTCL - Modifying ETT tracking criteria
     EQQJMTCL -------------- MODIFYING ETT TRACKING CRITERIA ----------  ROW 1 OF 3
 Command ===>                                                  Scroll ===> PAGE

 Change data in the rows, and/or enter any of the following row commands:
 I(nn) - Insert, R(nn),RR(nn) - Repeat,  D(nn),DD - Delete

 Row  Name of triggering event                      Id of associated  E  J  D  A
 cmd                                                application       T  R  R  S

 '' DAP*________________________________________  SAMPLEA_________  J  N  Y  N
 '' TESTJOBB____________________________________  SAMPLEB_________  J  Y  N  N
 '' SPECIAL RESOURCE 1__________________________  SAMPLE0_________  R  N  Y  Y
 ******************************* BOTTOM OF DATA ********************************
  4. Specify these fields for the criteria:
    Name of triggering event
    This is:
    • For a J-event, the name of the job that will act as the trigger
    • For an R-event, the name of the resource whose availability will act as the trigger

    You can specify the triggering-event name generically by using the generic search characters * (asterisk) or % (percent). If there is more than one match for generic filters, the most specific match is selected. For a J-event, for example, you could specify a job name of DAP* as the name of the triggering event. Whenever a job that is outside HCL Workload Automation for Z control with a job name beginning with DAP enters the system, HCL Workload Automation for Z adds an occurrence of SAMPLEA to the current plan.

    ID of associated application
    Specify the ID of the application to be triggered.
    ET
    The type of event (J or R). See Triggering event types.
    JR
    This specifies job-name replace tracking. Specify Y if HCL Workload Automation for Z will track the job that is being used as the trigger. If you specify N, HCL Workload Automation for Z will not track the trigger, and the job serves only as the means for automatically adding an occurrence to the current plan. Use of job-name replace can give you a single point for monitoring all tasks. Tracking the actual job also means that powerful error detection capabilities and dependency control will be available to you for that operation.
    For example, the JCL for IMS™ recoveries can be built by DBRC. If you want to track the recoveries and use HCL Workload Automation for Z to detect errors and establish dependencies, define the tasks to ETT with job-name replace tracking. You would need only a single application description in the AD for all DBRC-generated recoveries. When the occurrence is added to the current plan, the job name of the first operation, which must be defined on a z/OS® computer workstation, is changed to match the actual name of the triggering job.
    Note:
    1. You can specify Y only for J-type triggering events.
    2. If you specify Y and the trackers have the EWTROPTS HOLDJOB parameter set to USER or YES, the first operation in the application added via ETT (the one where job name replacement occurs) must have a destination that points to the location where the trigger job is submitted.

      For example: if an ETT criteria is defined with JR=Y to add the application APPLREM, and the trigger job JOBX is submitted on a Sysplex different from the Sysplex where the Z controller is located, the first operation in APPLREM must have a workstation with the destination of the tracker running on the LPAR where JOBX is submitted, because this is where the request to release the job will be sent.

    DR
    Specify dependency resolution for the occurrence to be added. As with the MCP panel and the program interface, you can choose:
    Y
    Resolve both predecessor and successor dependencies.
    N
    Ignore all dependencies.
    P
    Resolve only predecessor dependencies.
    S
    Resolve only successor dependencies.
    AS
    If this is N, ETT adds an occurrence each time the availability status is set to YES on a R-event. If you want an occurrence added only in the case of a true availability status switch for a resource from available=no to available=yes, set the availability status switch to Y. The availability status switch is valid only if the event type is R. If the event type is J, this field should have the value N, or blank.
    Note: Be aware that if an SRSTAT command (or equivalent) is issued for a resource that does not exist in either the resource definition database (panel option 1.6) or in the special resource monitor (panel option 5.7), HCL Workload Automation for Z reacts differently depending on whether the SRSTAT create option is set to YES or NO:
    • If you issue an SRSTAT command with CREATE(NO) AVAIL(YES), no resource is created in the plan and the resource status changes from NO to YES, then immediately back to NO. Each time the SRSTAT command is repeated, another availability switch to YES occurs, and ETT processing adds another occurrence, even if the ETT criteria has AS set to Y.
    • If you issue an SRSTAT command with CREATE(YES) AVAIL(YES), the resource is created in the special resource monitor, but HCL Workload Automation for Z does not count this creation as a real status change, and if AS in the ETT definition is set to Y, then no ETT triggering occurs.
    Thus for predictable processing, if you want to use the ETT ACTUAL STATUS option, all special resources, for which this option is to be set, should be predefined in the MAINTAINING SPECIAL RESOURCES panel (option 1.6)