Question & Answer
Question
What is filling up my 00000INT data space for CICS Interdependency Analyzer for z/OS (CICS IA) and what I can do to prevent it from filling up? My CICS IA V5.2 collector was running and then produced an IEATDUMP along with the following messages indicating my collector data space was full:
CIU4200S mm/dd/yy hh:mm:ss applid Dataspace is full
CIU3374I mm/dd/yy hh:mm:ss applid Transaction CINS has
terminated - Collector is stopping
CIU3303S mm/dd/yy hh:mm:ss applid CINB has abended IUXB in
program CIUCINB1
My data space allocation size was increased from the default 16M to 500M when this failed.
Answer
In this particular case, analysis of the CIU4200S IEATDUMP showed that the 00000INT CICS IA data space of 500M was full of data.
You have a few options available to mitigate the CIU4200S:
Continue to run the full suite of collectors and increase the size of the CICS IA data space from 500 to say 750. See Data space allocation in the CICS IA documentation.
Collect fewer types of commands. See Changing the data collection options dynamically in the CICS IA documentation.
Define temporary storage queue and enqueue name filters for the resource prefix list table to reduce duplicates. See Identifying patterns in resource names for more information.
If you collect for a certain application, you could load the VSAM collector files to DB2 as a unique collection-id and then not restore the VSAM files to the IA data space on startup and begin a new collection. See Identifying the data by using a collection ID in the CICS IA documentation.
Product Synonym
CICSIA CICS IA
Was this topic helpful?
Document Information
Modified date:
07 January 2016
UID
dwa1244864