Catalog Manager utility restrictions

Certain restrictions apply when you use the Catalog Manager utility.

The Catalog Manager utility has the following restrictions:

Restrictions that apply to all the functions

IMS catalog was introduced with IMS 12. Therefore, the Catalog Manager utility supports IMS resources that are created by IMS 12 or later. However, the compare function supports DBDs and PSBs that were created by an earlier version of IMS and that are stored in DBD libraries or PSB libraries. The Catalog Manager utility runs only when the IMS catalog is enabled and the active ACBs are managed by IMS in the IMS directory data sets of the IMS catalog.
Notes:
  • If you want to run the Catalog Manager utility when the IMS catalog is disabled and the active ACBs are managed by your ACBLIB data sets, create an alternate DFSDFxxx member of the IMS.PROCLIB data set with ACBMGMT=CATALOG, CATALOG=Y in the CATALOG section and use it to run the Catalog Manager utility as DLI batch region. If you use the Catalog Definition exit routine (DFS3CDX0), create an alternate DFS3CDX0 with "Catalog enabled" and "IMS management of ACB is enabled" and use it to run the Catalog Manager utility as DLI batch region.
  • When the Catalog Manager utility runs as a DLI batch job, only the CATALOG section of the DFSDFxxx member of the IMS.PROCLIB data set is valid.
Related reading: For more information about the DFSDFxxx member of the IMS.PROCLIB data set, see the topic "CATALOG and CATALOGxxxx sections of the DFSDFxxx member" in IMS System Definition.

Restrictions for the validate function

  • The Catalog Manager utility checks the DBDs and PSBs that are found in the IMS catalog database and ACB libraries when either of the following conditions is met:
    • IMS catalog was generated by IMS 13.
    • IMS catalog was generated by IMS 14 or later, and IMS catalog is enabled with CATALOG=Y and no ACBMGMT= parameter is in the CATALOG section of the DFSDFxxx member of the IMS.PROCLIB data set. In this case, only the DBDs and PSBs in the IMS catalog database and ACB libraries are checked.
  • DBDs and PSBs that are found only in the IMS catalog are not checked or included in the IMS Catalog Validation report.
  • If you are using IMS 13, depending on the maintenance level of IMS, the Catalog Manager utility cannot process PSBs that contain PCBs referring to a GSAM or a logical database. This is because no time stamp information is stored for such PSBs in the IMS catalog. To validate such PSBs, apply APAR PI27237 to IMS 13.

Restrictions for the compare function

  • When the Catalog Manager utility compares DBD-type ACBs for DEDB, the utility also uses the PSB-type ACB that references the DBD to obtain DBD VERSION or EXIT parameter value. If a problem occurs when reading the PSB-type ACB, the DBD VERSION or EXIT parameter value is not compared.
  • The Catalog Manager utility cannot process the following control blocks:
    • Control blocks for a logical database in the IMS directory because no control blocks for logical databases are stored in the IMS directory.
    • Control blocks for a GSAM or a logical database in the ACB library because no ACBs for GSAM or logical database are stored in the ACB library
    • Control blocks for a PSB that contains PCBs for a GSAM database in the ACB library because no PCBs for GSAM database are stored in the ACB library.
  • The utility compares only the parameters that exist in the ACBs in ACB libraries. When the utility compares ACBs in the ACB library with those in the IMS directory, it ignores parameters that exist only in the ACBs in the IMS directory, such as GSAM PCBs.
  • The reports generated by the compare function contain IMS DBDGEN and PSBGEN control statements. For the restrictions that apply to the generated control statements, see the following section.

Restrictions for generated IMS DBDGEN and IMS PSBGEN control statements

The following restrictions apply to IMS DBDGEN control statements that the Catalog Manager utility generates:
  • The order of the FIELD, LCHILD, and XDFLD statements that follow the SEGM statement is not the same as the user-required order in DBD control statements. The utility generates all the FIELD statements that belong to the segment following the SEGM statements, and then produces, if they exist, the LCHILD statements with paired XDFLD statements. This does not affect the database being accessed.
  • If the VERSION parameter on the DBD statement has a time stamp value, the utility converts the time stamp value to an Assembler comment statement.
  • The utility cannot convert control blocks for a logical database in the IMS directory because no control blocks for a logical database are stored in the IMS directory.
  • When the utility processes an ACB for DEDB, the utility also uses the PSB-type ACB that references the ACB to obtain the DBD VERSION or EXIT parameter value. If the utility processes an ACB in the IMS directory staging data set and the PSB-type ACB does not exist in the IMS staging data set, the DBD VERSION or EXIT parameter value is not converted. This restriction also applies to ACBs for MSDB but only for the DBD VERSION parameter value.
  • The utility cannot print the FREQ parameter because ACBs in the IMS directory contain no information about the FREQ parameter of the SEGM statement.
  • The utility cannot print the SIZE parameter, the second RECORD parameter, and the DEVICE parameter of the DATASET statement because ACBs in the IMS directory contain no information about these parameters.
The following restrictions apply to IMS PSBGEN control statements that the Catalog Manager utility generates:
  • The PCB label and the PCBNAME parameter in the PCB statement are mutually exclusive. If the utility finds a PCB label parameter, the utility prints the value as a PCBNAME parameter. If you want the PCB label parameter printed in the output, specify the PCB_LABEL=YES option for the FABXCIN control statement.
  • If the PGM_COBOL=YES option is not specified in the FABXCIN control statement, the utility prints the PSBGEN statement as PSBGEN LANG=ASSEM even if the statement is defined as PSBGEN LANG=COBOL or PSB LANG=, because there is no difference between the PSBs.
  • The utility always prints the TP PCB statement as PCB TYPE=TP,LTERM=nnnn even if it is defined as PCB TYPE=TP,NAME=nnnn, because there is no difference between the PSBs.
  • For a DEDB database, the utility always prints the POS parameter of the PCB statement as POS=S.
  • The utility always prints the REPLACE parameter of the SENFLD statement as REPLACE=YES.
  • The utility always prints the LIST parameter of the GSAM PCB statement as LIST=NO because GSAM PCBs in the IMS directory contains no information about the parameter.
  • When the utility processes a PSB-type ACB which includes DBPCB for MSDB and the ACB for MSDB which is referenced by the PSB-type ACB does not exist in the processing IMS directory data set, the utility does not convert such PSB.

Restrictions for the map function

Start of changeThe Catalog Manager utility can produce maps and reports of DBDs and PSBs from the IMS catalog database or DBD-type ACBs or PSB-type ACBs from the IMS directory. It generates maps and reports with the values stored in the IMS catalog database or the IMS directory. Some values of the generated report will be different from those of the DBD/PSB/ACB Mapper utility because some information is not stored in the IMS catalog database or the IMS directory, or the stored values are not the same. For details about differences between maps and reports, see FABXCRP2 data set (Map function). End of change

Start of changeThe Catalog Manager utility can produce only DBD report or ACB(DBD) report for GSAM DBD because GSAM has no segment. It also produces only PSB summary report or ACB(PSB) summary report for GSAM PCB.End of change

Start of changeThe Catalog Manager utility cannot generate ACB(PSB) maps, ACB(PSB) reports, and PSB summary report when the utility processes PSB-type ACBs and DBD-type ACBs that are referred to by the DB PCBs are not stored in the IMS directory.End of change