When trying to modify & generate a new DMCL we receive the following message:
DB001042 T929 C-4M6001: TABLE:LOADTEXT-157, AREA:DDLCATLOD SPACE EXHAUSTED. Running the CLOD task to delete logically deleted records in the DDLCATLOD area will allow us to generate the DMCL that originally failed, but a longer-term solution is desired, so we would like to expand the page range of CATSYS.DDLCATLOD. Can CATSYS.DDLCATLOD page range be expanded using the UNLOAD and RELOAD utilities?
CATSYS.DDLCATLOD can be expanded using UNLOAD and RELOAD utilities just as any other database area can. Use subschema IDMSCATL.
However , in many cases an UNLOAD/RELOAD is not necessary for the SYSTEM CATALOG Load Area CATSYS.DDLCATLOD in order to expand the page range.
If you use the SYSTEM CATALOG only for Physical database definitions as recommended, then the only load modules in DDLCATLOD will be ones generated from the DMCL and DBTABLE source definitions you have added to the catalog using OCF or IDMSBCF. The source definitions reside in areas CATSYS.DDLCAT and CATSYS.DDLCATX.
In most cases clients will have very few DMCL and DBTABLE definitions. Rather than going through the process of unloading and reloading all of the records that make up these load modules in CATSYS.DDLCATLOD, an easier and faster method of increasing the page range would be as follows:
- Increase the page range in the Area definition for CATSYS.DDLCATLOD to the desired size.
- Generate, punch and link the DMCL that contains the new page range for area CATSYS.DDLCATLOD.
- Allocate the new larger file for the area.
- FORMAT the new file using the updated DMCL.
- Rename files such that the new larger file will be accessed by the CV (if not using dynamic file allocation you must be sure the new file is defined by a DD in the CV startup JCL)
- Bring CV up with the updated DMCL.
- In OCF or IDMSBCF you can now GENERATE each DMCL and DBTABLE for which you have source definitions, thus recreating the DMCL and DBTABLE load modules in CATSYS.DDLCATLOD.
NOTE: If you use the SYSTEM Catalog for application SCHEMA and TABLE definitions and create ACCESS MODULES this method may not be practical as you may have many more load modules that will need to be recreated.
Typically clients will have a separate application Catalog such as SYSSQL for application Schemas, Tables and Access Modules. The SYSTEM Catalog CATSYS is typically used only to contain the physical database definitions that are used to create DMCLs and DBTABLEs.