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 your CA Bundl files.
CA Bundl 5.0
***** Early Warning of CA Bundl file full condition *****
- Prior to a CA Bundl file becoming FULL, there are 2 WARNING messages CA 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 you would want to look for in all CA Bundl job/task output.
- Additionally, add these same 2 messages to your automation package so that someone receives advanced notification of the files condition.
The appropriate "corrective action" may vary, depending on which CA Bundl file has reached it's capacity. Common actions to take might include:
- Verify you are performing the appropriate cleanup processing against the files on a regular basis.
- Verify EOD processing (pgm=DPMB096) is resetting/clearing the appropriate files on a regular basis.
- Lower the appropriate CA Bundl retention on the entries in the file.
- Manually delete any unwanted data from the file.
- Execute the CC50JORG process (Backup,Delete,Define,Repro) to increase the size of the file.
***** 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 CA Bundl VSAM file becomes FULL, the application attempting to write to that file will abend, and you will likely see one or more of the following messages associated to that abend:
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