CA-TPX uses up to five VSAM-files: ADMIN1, ADMIN2, MAIL, NOTES and VIEW. This document gives some hints on how to take care about these files.
To keep the VSAM files used by TPX in a 'healthy' shape, we recommend the following preventive maintenance procedures:
This is a preventive maintenance procedure (i.e. REORG) that mitigates Control Area and Control Interval (CA and CI) splits and VSAM file corruption. Please note that if the CI/CA splits are excessive even after a REORG has been done, increasing the FREESPCE parameter in the VSAM cluster DEFINE will help alleviate this problem. Excessive CI/CA splits most typically occur during a new install when performing a high volume 'ADD' maintenance activity for information stored on the Unicenter CA-TPX VSAM files. The FREESPCE parameter can be lowered once the high volume of activity has ended.
We also recommend that you run the CA-TPX Batch Reset Integrity process (refer to library SAMPLIB, member BATCHINI for sample JCL) after any CA-TPX VSAM file REORG/restore process prior to starting CA-TPX. Refer to CA-TPX FAQS titled What causes VSAM integrity errors for more detailed information on the batch Reset Integrity.
Maintenance to the CA-TPX VSAM files, including running the batch Reset Integrity, should be done while the product is down.
Also, we refer you to library SAMPLIB (from the TPX product install tape), member $BATMAIL for sample MAIL batch programs. If you are storing email messages, you should consider running the TPXBATCH mail delete on a periodic basis to clean out the TPX MAIL.
The cluster definition for the TPXMAIL file is delivered in library INSTALL (from product install tape, member VMAIL) you need to adjust the space requirements based on the volume of data (lists/messages) that you expect to store on the MAIL file.