Bundl - File full condition - Early Warning and Diagnostic information
Article ID: 143092
Updated On:
Products
Issue/Introduction
The following information can be used for problem diagnosis and to establish early warning checks and balance procedures, relevant to the size and capacity of the Bundl files.
Environment
z/OS
Bundl 5.0
Resolution
***** Early Warning of CA Bundl file full condition *****
- Prior to a Bundl file becoming FULL, there are two WARNING messages Bundl issues when a file reaches 80% capacity:
BND7031I File DDNAME is XX% FULL. <-- Appears when, at least, 80% full.
BND7032E File DDNAME is 90% FULL. <-- Appears when, at least, 90% full.
- The above two messages would be the ones to look for in all Bundl job/task output.
- Additionally, add these same two messages to your automation package so that someone receives advanced notification of the files condition.
The appropriate "corrective action" may vary, depending on which Bundl file has reached its capacity. Common actions to take might include:
- Verify the appropriate cleanup processing is being performed against the files on a regular basis.
- DPMB007 - To cleanup expired time based archive (AIF) records - Review Archive Data Set Summary Report
- DPMB027 - To cleanup expired cycle based archive (AIF) records - Review Archive Data Set Summary Report
- DPMB008 - To cleanup expired time and cycle based view (VIF) records. - View Page File Utilization Summary Report
- Verify EOD processing (pgm=DPMB096) is resetting/clearing the appropriate files on a regular basis.
- Execute the CC50JORG process (Backup,Delete,Define,Repro) regularly to "REORG" the files so that Bundl can reuse the space in them.
- Lower the appropriate Bundl retention on the entries in the file.
- Manually delete any unwanted data from the file.
- Execute a modified CC50JORG REORG process (Backup,Delete,Define,Repro) should it become necessary to increase the size of a file.
See Increasing the size of a Bundl file for more information on this process.
***** CA Bundl tasks and jobs to be monitored *****
- Common task and job output to be monitored for space related problems would include:
Collector tasks - (Job=CC50J001)
Distribution process - (Job=CC50J002)
Archive process - (Job=CC50J004)
Reprint process - (Job=CC50J005)
End of Day (EOD) - (Job=CC50J029)
***** Diagnostic - CA Bundl VSAM file is full *****
- When a Bundl VSAM file becomes FULL, the application attempting to write to that file will abend, and one or more of the following messages associated to that abend will be issued:
BND7002E I/O function file full
BND7075I Page file n dsfid dsname is FULL
BND7030E FILE SPACE ISSUES
BNDL600- VSAM ERROR
BNDL622- DATA SET IS FULL
BNDL628- FILE IS FULL
Additional Information
Feedback
