Previous Topic: OPSVIEW Command Processor—Access OPSVIEW

Next Topic: OPSWAIT Used Without Event Keywords

OPSWAIT Command Processor—Suspend CLIST or REXX Processing

The OPSWAIT command processor enables you to suspend processing of a CLIST or REXX program until one of the following time events occurs:

OW is the abbreviation of OPSWAIT.

The OPSWAIT command processor has the following format:

OPSWAIT
{FOR(interval)|UNTIL(hh:mm:ss)|SYNCH(hh:mm:ss)}
[MAXTIME(hh:mm:ss)]
FOR

Use this keyword to delay CLIST or REXX program processing for a specific amount of time, either a number of seconds or an hh:mm:ss (hours, minutes, seconds) value. The following examples show how to specify these intervals:

Note: When specifying an interval as seconds without colons, you can use up to two decimal places to indicate fractions of seconds.

UNTIL

Use this keyword to delay CLIST or REXX program processing until a specific time of day. If the specified time has already passed, the OPSWAIT command either terminates or waits until the correct time of day tomorrow, depending on the value of the MAXTIME keyword. For example, suppose that the current time is 13:23:00:

SYNCH

Use this keyword to delay CLIST or REXX program processing until the start of a specified time interval. This interval can be the start of the next minute, next five-minute period, next hour, and so on. For example, suppose that the current time is 13:23:00:

MAXTIME

(Optional) Use this keyword to define the maximum amount of time that the OPSWAIT command is allowed to delay CLIST or REXX program processing by specifying either a value in hh:mm:ss format or the number of seconds (with up to two decimal places to indicate fractions of seconds).

If the command exceeds the specified maximum wait time, then it does not wait and a return code 8 is issued.

If this keyword is not specified, then the default maximum wait time of 8 hours is used.