ERDROPTS
Purpose
The ERDROPTS statement defines run-time options to an event-reader task. You can specify this statement for a tracker, controller, or standby controller. This statement is required if you do not specify ERDRTASK(0) on the OPCOPTS statement.
ERDROPTS is defined in the member of the EQQPARM library as specified by the ERDRPARM keyword on the OPCOPTS statement.
Format
Parameters
- ERSEQNO(event reader sequence number)
- Defines which event reader is being
started. This number must
be in the range 1 to 16 and defines the ddname of the input event
data set.
The ddname of the corresponding input event data set has the format EQQEVDnn, where nn is the event-reader sequence number specified as a 2-digit number. If the sequence number is less than 10, you must add a leading zero. For example, if you specify ERSEQNO(1), the ddname should be EQQEVD01. Ensure that this ddname is in your JCL procedure.
Note: You can start only one event reader for each input event data set. You must not specify the same number for ERSEQNO and the event-writer sequence number (EWSEQNO) if both tasks are active on the same system. - ERWAIT(wait limit|10)
- Defines how long the event reader waits (in seconds) before rechecking the input event data set after all event records have been read. It will influence the rate with which the ready list is updated.
- RELDDNAME(ddname of submit/release data set)
- RELDDNAME is used in a shared DASD configuration, where the target system uses the hold/release function. It identifies the submit/release data set to which the controller writes release commands. RELDDNAME is required if events are not created on the same system that the event reader is started on. The ddname is the same name that you specify in the workstation destination field and the DASD keyword of ROUTOPTS.
In this example of an ERDROPTS statement:
- 1
- Reader number 1 is started.
- 2
- The reader will wait 5 seconds before rechecking its input event data set.