GETNEXT TIMER
Browse the BTS timers associated with a BTS activity.
Description
GETNEXT TIMER returns the name of the next BTS timer associated with a BTS activity.
Options
- ABSTIME(data-area)
- Returns, in packed decimal format, the time at which the timer will expire, expressed in
milliseconds since 00:00 on 1 January 1900 (rounded to the nearest hundredth of a second).
You can use FORMATTIME to change the data into other familiar formats.
- ACTIVITYID(data-value)
- Specifies the identifier (1–52 characters) of the activity with which the timer is associated.
If this option is omitted, the current activity is assumed.
- BROWSETOKEN(data-area)
- Specifies a fullword binary data area, into which CICS® will place the browse token.
- EVENT(data-area)
- Returns the 16-character name of the event (if any) associated with the timer.
- STATUS(cvda)
- Indicates the state of the timer. CVDA values are:
- EXPIRED
- The timer expired normally.
- FORCED
- Expiry of the timer was forced by means of a FORCE TIMER command.
- UNEXPIRED
- The timer has not yet expired.
- TIMER(data-value)
- Specifies the name (1–16 characters) of the BTS timer.
Conditions
- 109 ACTIVITYERR
- RESP2 values:
- 3
- The activity indicated by the ACTIVITYID option could not be found.
- 29
- The repository file is unavailable.
- 30
- An input/output error has occurred on the repository file.
- 16 INVREQ
- RESP2 values:
- 1
- The command was issued outside the scope of a currently—active activity.
- 17 IOERR
- RESP2 values:
- 30
- An input/output error has occurred on the repository file.
- 70 NOTAUTH
- RESP2 values:
- 101
- The user associated with the issuing task is not authorized to access this resource in the way requested.
- 115 TIMERERR
- RESP2 values:
- 1
- The timer specified on the TIMER option could not be found.