BTS containers

A container is owned by a BTS activity and can be used to pass data between BTS activities or between different activations of the same activity.

Containers cannot be used outside of an activity; for more information, see the CICS® Business Transaction Services manual . An activity uses GET and PUT container to update the container's contents. CICS ensures that the appropriate containers are available to an activity by saving all the information (including containers) associated with a BTS activity in an RLS-enabled VSAM file. For this reason, note that a BTS environment cannot extend outside a sysplex (see CICS Business Transaction Services ), but you can use dynamic routing within a sysplex passing data in containers.

Some general characteristics of containers are:
  • An activity can own any number of containers; you are not limited to one.
  • There is no size restriction.
  • They are recoverable.
  • They exist in main storage only while the associated activity is executing. Otherwise they are held on disk. Therefore, you do not need to be overly concerned with their storage requirements, unlike terminal COMMAREAs.


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