Previous Topic: Change CICS Startup JCLNext Topic: CICS Exit Considerations


CICS Agent Storage Requirements

The DevTest CICS agent is a long running task. The agent requires approximately 16K of program storage in ESDSA and approximately 1K of dynamic storage in ECDSA.

The DevTest CICS exits require approximately 34K of program storage in ERDSA and approximately 3K of dynamic storage (for each transaction) in ECDSA.

The recorded images of a CICS LINK are built in ECDSA when using the VSE recorder.

The exits build recorded images and pass to the CICS agent. The CICS agent sends them to the LPAR agent and then frees them, so they are short lived.

The size of a recorded image is approximately 330 + 2 * ((COMMAREA length or sum of all CONTAINER lengths) + INPUTMSG length).

The amount of ECDSA required to accommodate the recorded images depends on the average size that is calculated in the previous paragraph, and the transaction rate.

Playback images of a CICS LINK are also built in ECDSA when a Virtual Service is deployed.

At the beginning of a virtualized CICS LINK, the exits build a playback request and pass it to the CICS agent. The CICS agent forwards it to the LPAR agent.

When the CICS agent receives the playback response, the response is matched to the original request. Both the request and response are passed to the exits, which free them and complete the CICS LINK.

The size of a playback request and response is approximately 300 + (COMMAREA length or sum of all CONTAINER lengths).

The amount of ECDSA required to accommodate the playback images depends on the average size that is calculated in the previous paragraph, and the transaction rate.