The following rules apply to data-container usage at run time:
- Process containers can be read by all the activities that comprise a process
but written to and updated by only the defining or acquiring program and the
root activity of the process, DFHROOT.
- Each adapter program data-container can be read and updated by the owning
activity, by the activity's parent, or by a program that has acquired the
activity. These containers are used by the Navigation Manager and Navigators.
- Each server adapter program data-container can be read and updated by
the activity itself, by the activity's parent (Adapter program activity),
or by a program that has acquired the activity.
- Each FEPI server adapter program data-container can be read and updated
by the activity itself, by the activity's parent (Adapter program activity),
or by a program that has acquired the activity.
- Each Link3270 server adapter program data-container can be read
and updated by the activity itself, by the activity's parent (Adapter program
activity), or by a program that has acquired the activity.
- The Error, Journal and Shared Context containers can be characterized
as one of the various CICS® Service Flow Runtime data-container types, depending on how and
when it is used. The Error and Shared Context containers are never process
containers. Each activity implementing an Adapter service program, can have
its own error container.