When starting the SymDump for CICS trace format region the trace format region has 1169 MEGS of AVAILABLE EXTENDED PRIVATE.
CAIN5919 AVAILABLE EXTENDED PRIVATE: 1169 MEGS.
How do I determine (and/or change) the AVAILABLE EXTENDED PRIVATE allocation? I have a trace format region on one LPAR which has more available Extended Private Area that the same task on another LPAR. Both are using the same IN25OPTS options module and load library.
The available extended private value is not control by any on the SymDump for CICS IN25OPTS trace format region parameters. It is control by how the LPAR was configured by the z/OS System Programmer and it is the amount of the available extended private storage that is available on the LPAR. When the trace format region is started the SymDump CICS code issues and inquiry command to the operating system command LDAELIM to obtain the amount of available extended private storage. This value can be different on each LPAR unless the z/OS System Programmer team standardize the LDAELIM across LPAR on all LPARs.
The CAIN5919 message indicates that the AVAILABLE EXTENDED PRIVATE storage that is available on the LPAR is greater than the IN25OPTS parameter TRCFMEGM and the trace format region starts. If the AVAILABLE EXTENDED PRIVATE storage was not greater than the IN25OPTS TRCFMEGM then the trace region would fail with message CAIN5920 INSUFFICIENT EXTENDED PRIVATE AREA TO START FORMAT TASK
MM/DD/YYYY HH:MM:SS AVAILABLE EXTENDED PRIVATE: NNNN MEGS
An informational message telling you what the available extended private storage area is for the TRACE FORMAT REGION.
This value must be equal to or greater that the value specified in TRCFMEGM or the job will terminate.
MM/DD/YYYY HH:MM:SS INSUFFICIENT EXTENDED PRIVATE AREA TO START FORMAT TASK
The available Extended Private area must be equal to or greater that the value specified in TRCFMEGM or the job will terminate.