Start a browse of events known to a BTS activity.
STARTBROWSE EVENT
>>-STARTBROWSE--EVENT--BROWSETOKEN(data-area)------------------->
>--+------------------------+----------------------------------><
'-ACTIVITYID(data-value)-'
Conditions: ACTIVITYERR, INVREQ, IOERR, NOTAUTH
Description
STARTBROWSE EVENT initializes a browse token which can be used to identify
each event (including each sub-event and system event) that is within the
scope of a specified BTS activity. If you do not specify an activity, events
within the scope of the current activity are browsed.
A browse started by STARTBROWSE EVENT returns:
- Atomic events. An atomic event returned on this command may or may not
be included in the predicate of a composite event—that is, it may or
may not be a sub-event.
- Composite events.
- System events.
Options
- ACTIVITYID(data-value)
- specifies the identifier (1–52 characters) of the activity whose
events are to be browsed.
If you omit this option, events known to the
current activity are browsed.
- BROWSETOKEN(data-area)
- specifies a fullword binary data area, into which CICS® will place
the browse token.
Conditions
- 109 ACTIVITYERR
- RESP2 values:
- 1
- The activity identifier specified on the ACTIVITYID option does not
relate to any activity that is within the scope of this task.
- 29
- The repository file is unavailable.
- 30
- An input/output error has occurred on the repository file.
- 16 INVREQ
- RESP2 values:
- 1
- There is no current activity within the scope of this task.
- 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.