Tokens and identifiers

A browse token uniquely identifies a browse within a CICS region. An activity identifier is a means of uniquely referring to an instance of an activity that has been retrieved from a BTS repository data set.

The browse token that is returned on a STARTBROWSE command must be supplied on the corresponding GETNEXT and ENDBROWSE commands. CICS discards it after the ENDBROWSE command.

The lifetime of a browse token is from a STARTBROWSE command to an ENDBROWSE command or sync point, whichever comes first. Therefore, your applications:
  • Should not attempt to use a token after the browse has ended
  • Should not attempt to use a token if a sync point is encountered before the browse has completed

When an activity identifier or a process name is known, it can be used as a scoping argument to a new browse. It can also be specified on certain API commands which cause actions to be taken against existing activities or processes, or their containers and events - see Commands that take identifiers returned by browse operations . The lifetime of an activity identifier is the same as the lifetime of the activity it refers to. Thus, it can be used after an ENDBROWSE and after a sync point.

A data-container or an event cannot be identified in the same way as an activity or a process, because it forms part of a record on a BTS repository data set. Instead, it must be referenced through the activity or process to which it belongs.



dfhp9c00128.html | Timestamp icon Last updated: Monday, 5 June 2017