Because error processing, journaling and sharing application data might be necessary at different stages of run time processing, the Error, Journal and Shared Context data-containers are listed together.
Container Type | Contents and usage | Size (bytes) | Name | Comments |
---|---|---|---|---|
ERROR | Detailed error information that can be used in problem determination. |
256 | ADAPTER.ERROR | No Comments. |
JOURNAL | Application data modeled at build time. Used in compensation and recovery by Adapter service. Navigation Manager writes a copy of Adapter activity Journal container for purposes of compensation and recovery. |
4MB | ADAPTER.JOURNAL | During compensation, the DPL Stub program (DFHMADPL) writes a copy of this container to a process container for use in the compensating sequence flow. |
SHARED CONTEXT |
Application context shared between Adapter activity and child FEPI server adapter or child Link3270 server adapter. | Compiler limit for IBM® COBOL | ADAPTER.SHARED.C | Optional based on modeling. Separate containers for each Adapter activity and FEPI server adapter or Link3270 server adapter, but mappings are the same and data is kept consistent. |
See How CICS Service Flow Runtime programs use data-containers for a list of the CICS® Service Flow Runtime programs that use (read, write or read and write) these miscellaneous data-containers.