Reporting on the contents of IDMS catalog load area
Article ID: 118439
Updated On:
Products
IDMS
IDMS - Database
Issue/Introduction
This document describes how to report on the contents of CATSYS.DDLCATLOD. Specifically, how to see a list of the load modules in order to be sure that the only ones are the DMCL and DBTABLE.
Environment
Release: All supported releases.
Resolution
Currently there is no OCF/IDMSBCF command to DISPLAY ALL for DMCL LOAD MODULE or DBTABLE LOAD MODULE.
A PRINT SPACE report for CATSYS.DDLCATLOD (FULL option) will show how many load modules reside in the area (number of SR156 records) but not the load module names.
For sites without the SQL option enabled, the long way to do this is described below.
For sites with the SQL option enabled, do this:
Example:
The harder way:
The subschema that describes the DDLCATLOD area that is provided with the product is IDMSCATL and this subschema is used by utilities that will access DDLCATLOD.
But no source for this subschema is provided, so it is not possible to use it in OLQ to report on the LOADHDR-156 records in the area.
Create a special schema and subschema (PLEASE do not use the name of any subschema load module already provided) that defines the DDLCATLOD area and the records and sets that reside in the area (the same records and sets that reside in DDLDCLOD). This special subschema can be used in OLQ to report on the LOADHDR-156 records (there is one LOADHDR-156 for each generated load module).
The SYSDIRL dictionary has all of the record definitions referenced so that is where this special schema and subschema should be defined. Sample source is provided in the attached .zip file. Define and VALIDATE the schema, and define and GENERATE the subschema. They can then be used in OLQ.
For sites without the SQL option enabled, the long way to do this is described below.
For sites with the SQL option enabled, do this:
CONNECT TO SYSTEM;SELECT * FROM SYSTEM.LOADHDR;Example:
SELECT * FROM SYSTEM.LOADHDR;*+*+ NAME VERSION RLDS EPA LENGTH DATE TIME TYPE*+ ---- ------- ---- --- ------ ---- ---- ----*+ DMCLBOBT 1 0 00000000 23968 11/03/09 092748 00*+ DBTB1700 1 0 00000000 5152 02/13/13 143951 00*+ DMCL1850 1 0 00000000 48060 07/08/13 103930 00*+ LABDMCL 1 0 00000000 9236 08/24/10 083020 00*+ DBTB1850 1 0 00000000 5152 09/17/14 122411 00*+ RELD1700 1 0 00000000 49648 01/13/16 083741 00*+ DBTB1855 1 0 00000000 948 12/10/15 130754 00The harder way:
The subschema that describes the DDLCATLOD area that is provided with the product is IDMSCATL and this subschema is used by utilities that will access DDLCATLOD.
But no source for this subschema is provided, so it is not possible to use it in OLQ to report on the LOADHDR-156 records in the area.
Create a special schema and subschema (PLEASE do not use the name of any subschema load module already provided) that defines the DDLCATLOD area and the records and sets that reside in the area (the same records and sets that reside in DDLDCLOD). This special subschema can be used in OLQ to report on the LOADHDR-156 records (there is one LOADHDR-156 for each generated load module).
The SYSDIRL dictionary has all of the record definitions referenced so that is where this special schema and subschema should be defined. Sample source is provided in the attached .zip file. Define and VALIDATE the schema, and define and GENERATE the subschema. They can then be used in OLQ.
Set DICTNAME to SYSDIRL (where the special schema and subschema are defined). Set DBNAME to SYSTEM (to report on CATSYS.DDLCATLOD). Select the special subschema (CATLODSS in the sample provided) and select record LOADHDR-156. Then select any record elements required. In this example, only LOADHDR-MODNAME-156 is selected. The DDLCATLOD in this case has 7 load modules.
LOADHDR-156 REPORT 10/24/18 LOADHDR-MODNAME-156 ------------------- DMCLBOBT DBTB1700 DMCL1850 LABDMCL DBTB1850 RELD1700 DBTB1855Attachments
Feedback
Yes
No
Powered by
