To determine the type of event that has caused the automatic addition
of a new occurrence to the plan, use the variables provided by ETT.
For example, consider that a company is asked to produce customer-oriented
reports according to an external demand. The on-demand request is
created by a job name that identifies the customer and is contained
in a new generation of an input GDG data set. You can resolve the
on-demand process by using the ETT definition and ETT variables in
a single job, as follows:
In the CREATING A SPECIAL RESOURCE panel (option 1.6.2 on the
main menu), define the special resource that identifies the input
GDG data set root.
In the MODIFYING ETT TRACKING CRITERIA panel, specify the ETT
criteria for the GDG data set root.
Update the selection table for the
tracker to identify the ETT criteria for the GDG data set root. The
file to be edited depends on which kind of selection table the tracker
uses:
If the tracker uses EQQDSLST as selection table, update the EQQLSJCL
member of the sample job JCL library as follows:
If the tracker uses EQQEVLST as selection table, updated
it as described in Data set triggering.
Write a sample JCL that includes the ETT occurrence-related variables.
When you create a request, a new generation of HWA.REQUESTS.GDG is created. The ETT
criteria schedule a new occurrence and the variable is resolved.
Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.