DBD and PSB maps for the IMS catalog database
The Catalog Manager utility generates DBD and PSB maps for the IMS catalog database.
- A DBD map for each DBD instance in the IMS catalog database.
- A PSB map for each database PCB within the PSB instance in the IMS catalog database.
Format of the maps
The maps produced by the Catalog Manager utility depict the hierarchical structure of a database as described in a DBD. The DBD map heading shows the DBD member name, and ACTIVE or PENDING status. If the status is neither ACTIVE nor PENDING, ******* is shown. The map also shows the database versioning number, its creation date, time, and IMS version of the DBD. It also shows the access method, or if it is a logical database LOGICAL, for the DBD currently being mapped.
The PSB map heading shows the PSB member name, and ACTIVE or PENDING status. If the status is neither ACTIVE nor PENDING, ******* is shown. The map also shows its creation date, time, and IMS version of the PSB. PSB map also shows its referenced DBD.
When the utility does not refer to an external DBD, its status, DBVER=, gendate, and ACCESS= in the header DBDNAME= section are shown with asterisks (*).
Both physical and logical relationships are shown. A map can be created for all full-function and Fast Path IMS database organizations except GSAM. A map cannot be created for a GSAM database, because it does not contain segments. However, a report can be created.
For physical relationships, each segment is represented by a box that contains the segment name and code. Each box (except for the root segment) is connected to its physical parent and siblings. The characters as shown in the following table are used to draw a box that shows the data set group that contains the segment. These characters are called data set group characters.
| Character | Explanation |
|---|---|
| * | The first data set group |
| + | The second data set group |
| " | The third data set group |
| . | The fourth data set group |
| = | The fifth data set group |
| - | The sixth data set group |
| # | The seventh data set group |
| % | The eighth data set group |
| ; | The ninth data set group |
| ' | The 10th data set group |
| V | Virtual logical child |
| C | Pointer and parent segment concatenation |
Data set group characters are used to express up to the maximum number of data set groups allowed for a database. A DEDB database can have up to 9999 areas. The area segments use the same characters as the data set groups. For more than 10 areas, the characters, are simply repeated; that is, 11 through 20 use the same characters as 1 through 10, 21 through 30 use the same characters as 1 through 10, and so on.
VAR in the top line of a box indicates a variable-length segment. SXD in the top line of a box indicates that the segment has secondary index fields. If the segment is a sequential dependent segment (SDEP), SDEP is shown in the upper-right corner of the box. The segment code is placed in the bottom line of each box.
MULT in the top line of a box indicates that the segment has multiple secondary indexes.
Logical relationships for the segment box are indicated by the segment name of the logical parent or logical child and, where necessary, the name of the database that contains that segment. Dependent logical segments are not connected as physical segments are; rather, they appear first under their associated segment in a vertical row, one under another.
If the map is too wide or long to fit on a single page, the map is split and printed on as many contiguous pages as needed.
Differences from DBD, PSB, and ACB maps generated by the DBD/PSB/ACB Mapper utility
The Catalog Manager utility generates maps from the stored values of the specified instance in the IMS catalog database. Although the format of the map is similar, certain elements are different between the maps generated by the Catalog Manager utility and those by the DBD/PSB/ACB Mapper utility.
- DBD maps
- LOGICAL DBDs are stored in the IMS catalog database, so the Catalog Manager utility generates a map of the LOGICAL DBD.
- PSB maps
- Even when the utility cannot find a referenced DBD instance in the IMS catalog database, the utility generates a PSB map from the IMS catalog database. When the utility cannot find a referenced DBD instance in the IMS catalog database, it generates a map with only the database PCB values stored in the IMS catalog database. In this case, some descriptions such as segment code, VAR, and 2ND cannot be described in the box.
Report field description
For details about report field description of DBD and PSB maps, see DBD, PSB, and ACB maps of the DBD/PSB/ACB Mapper utility.
Example of the DBD map
The following figure shows an example of the DBD map.IMS LIBRARY INTEGRITY UTILITIES - CATALOG MANAGER "DBD MAP" PAGE: A
5655-U08 DATE: 12/23/2024 TIME: 01.58.49 FABXCMAP - V2.R2
DBDNAME=DBD@D01A IMS CATALOG DATABASE ACTIVE DBVER=0 GENDATE:11/01/2024 02.19.04.89 IMS V15.1
DBDMAP OF DBD@D01A ACCESS=HDAM VSAM
***********
* D01SEG1 *
*******001*
._______________|________________.
| |
*VAR***SXD* ***********
* D01SEG2 * * D01SEG3 *
*******002* *******004*
._____|______. |
| | |
----------- *********** *******SXD*
LC=X01AS001 * D01SEG21* * D01SEG31*
DB=DBD@X01A *******003* *******005*
----------- .____________|____________.
| | |
----------- *********** ***********
LC=X02AS001 * D01S311 * * D01S312 *
DB=DBD@X02A *******006* *******007*
-----------
---
-----------
LC=X03AS001
DB=DBD@X03A
-----------
Example of the PSB map
The following figure shows an example of the PSB map.IMS LIBRARY INTEGRITY UTILITIES - CATALOG MANAGER "PSB MAP" PAGE: A
5655-U08 DATE: 12/23/2024 TIME: 02.00.08 FABXCMAP - V2.R2
PSBNAME=PSB@001 IMS CATALOG DATABASE ACTIVE GENDATE:11/01/2024 02.19.04.89 IMS V15.1
DBDNAME=DBD@H01A IMS CATALOG DATABASE ACTIVE DBVER=0 GENDATE:11/01/2024 02.19.04.89 IMS V15.1
DBDMAP OF DBD@H01A IN PSB-PSB@001 ACCESS=HIDAM VSAM
*VAR*******
* H01ASEG1*
*R*****001*
.__________________|___________________.
| | | |
*********** *********** *VAR******* ***********
* H01ASEG2* * H01ASEG3* * H01ASEG4* * H01ASEG5*
*G*****002* *R*****003* *G*****004* *G*****005*
|
|
***********
* H01ASG51*
*G*****006*