Using status containers

Use status containers to make it easier for a root activity to identify which of its descendant activities are stuck.

About this task

Status containers are data-containers that contain information about what an activity is currently doing. Whereas you can use an INQUIRE ACTIVITYID command to discover the mode and completion status of an activity, the information in a status container is likely to be at a more detailed level. For example, each activity in a process might have a data-container called, perhaps, STATUS, which it regularly updates—perhaps at the beginning and end of each activation, and each time it starts new work. A status container might, for instance, contain the date and time, and a string describing the work that the activity has started or ended, or the fact that it is dormant because it is waiting for the completion of a particular child activity.

You can think of an activity as a finite state machine—it is always in one of a limited number of processing states. The "processing states" we refer to here are application-dependent and distinct from the BTS-defined modes of an activity. Each activity could regularly update its status container with its current processing state.



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