DBD, PSB, and ACB maps
DBD/PSB/ACB Mapper generates DBD, PSB, and ACB maps in the SYSPRINT data set.
- A DBD map for each DBD.
- A PSB map for each database PCB within the PSB.
- An ACB (PSB) map for each database PCB within the PSB-type ACB.
- An ACB (DBD) map for each DBD-type ACB.
Format of the maps
The maps produced by DBD/PSB/ACB Mapper depict the hierarchical structure of a database as described in a DBD. The map heading shows the DBD member name, volume serial number, and data set name of the library that contains the member. The creation date, time, and IMS™ version of the DBD are shown on the right of the data set name. It also shows the access method, or if it is a logical database LOGICAL, for the DBD currently being mapped. 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 2048 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 among DBD, PSB, and ACB maps
Although the format of the four types of maps is similar, certain elements are different. The following list summarizes the differences between the DBD map and other types of maps:
- Differences in PSB maps
- PSB maps are similar to the DBD maps that the DBD Map function
generates. The following fields are different in DBD maps and PSB
maps:
- DBDMAP OF dbdname in PSB-psbname is shown in the header.
- 2ND is shown in the upper-right corner of the box when the segment contains the secondary index specified in PROCSEQ of DB PCB in the PSB map.
- SXD is not shown in the PSB map.
- The processing options (PROCOPT values) used for the segment are shown at the lower-left corner of the box.
- A special case is introduced, however, in which the list of segments included in the map is customized to include only those called for in the database PCB sensitive segment table. Also, if the sensitive segment table and the database PCB attributes call for inversion of the database because of a secondary index processing sequence, this is simulated before the map is prepared. The order of the segments in the map is the same as the order of the SENSEG statements in the PSB.
- Differences in ACB (PSB) maps
- ACB (PSB) maps are similar to the PSB maps that are generated
by the PSB Map function. The following fields are different between
PSB maps and ACB (PSB) maps:
- If the sensitive segment is a virtual child segment, information about this segment is not shown in the ACB (PSB) map.
- 2ND and SXD are not shown in the ACB (PSB) map.
- Differences in ACB (DBD) maps
- ACB (DBD) maps are similar to the DBD maps that are generated by the DBD Map function.
Example of a DBD map (single-page)
The following figure shows an example of the DBD map that fits in a single page.IMS LIBRARY INTEGRITY UTILITIES - DBD/PSB/ACB MAPPER "DBD MAP" PAGE: A
5655-U08 DATE: 10/01/2018 TIME: 14.20.21 FABMDMAP - V2.R2
DBDNAME=PHDAM04 VOLUME=IMSVS DSNAME=IMSVS.DBDLIB DBDGEN:08/10/2018 18.21 IMS V13.1
DBDMAP OF PHDAM04 ACCESS=PHDAM VSAM
ALL SEGMENTS WITHIN A SINGLE DATA SET GROUP ARE DISPLAYED USING THE SAME CHARACTER FOR BOX DELIMITERS.
***********
* ROOTA *
*******001*
._____|______.
| |
+++++++++++ """""""""""
+ DEP1A + " DEP1B "
+++++++002+ """""""003" Example of a DBD map (multiple-pages)
The following figure shows an example of the DBD map that spans across pages.IMS LIBRARY INTEGRITY UTILITIES - DBD/PSB/ACB MAPPER "DBD MAP" PAGE: A
5655-U08 DATE: 10/01/2018 TIME: 12.13.02 FABMDMAP - V2.R2
DBDNAME=SAMP01Z VOLUME=IMSVS DSNAME=IMSVS.DBDLIB DBDGEN:08/10/2018 18.21 IMS V13.1
DBDMAP OF SAMP01 ACCESS=HDAM VSAM
ALL SEGMENTS WITHIN A SINGLE DATA SET GROUP ARE DISPLAYED USING THE SAME CHARACTER FOR BOX DELIMITERS.
*VAR*******
* A1111111*
*******001*
._____________________________________________________________|____.
| | |
*VAR******* +VAR+++++++ +VAR++
* AA222222* + AB222222+ + AC22
*******002* +++++++007+ ++++++
| ._________________________________.|
| |
*VAR******* +VAR+++++++ +VAR
* AAA33333* + ACA33333+ + AC
*******003* +++++++009+ ++++
._____|______. .___________.
| | |
*VAR******* *VAR******* +VAR+++++++
* AAAA4444* * AAAB4444* + ACBA4444+
*******004* *******005* +++++++011+
| .________|_________.
| | |
+VAR+++++++ "VAR""""""" "VAR"""""
+ AAABA555+ " ACBAA555" " ACBAB55
+++++++006+ """""""012" """""""01
|
|
"VAR"""""
" ACBABA6
"""""""01
|
|
"VAR"""""
" ACBABAA
"""""""01
._____|_.
|
"VAR"""""""
" ACBABAAA"
"""""""016"IMS LIBRARY INTEGRITY UTILITIES - DBD/PSB/ACB MAPPER "DBD MAP" PAGE: B
5655-U08 DATE: 10/01/2018 TIME: 12.13.02 FABMDMAP - V2.R2
DBDNAME=SAMP01Z VOLUME=IMSVS DSNAME=IMSVS.DBDLIB DBDGEN:08/10/2018 18.21 IMS V13.1
DBDMAP OF SAMP01 ACCESS=HDAM VSAM
ALL SEGMENTS WITHIN A SINGLE DATA SET GROUP ARE DISPLAYED USING THE SAME CHARACTER FOR BOX DELIMITERS.
*
*
*
_________________________________________________________.
| |
+++++++ .VAR.......
222222+ : AD222222:
+++008+ .......024.
_|___________________________________. |
| | |
AR+++++++ "VAR""""""" .VAR.......
ACB33333+ " ACC33333" : ADA33333:
+++++010+ """""""019" .......025.
___|______________. | |
| | |
"VAR""""""" "VAR""""""" .VAR.......
" ACBB4444" " ACCA4444" : ADAA4444:
"""""""018" """""""020" .......026.
| |
| |
"""" "VAR""""""" .VAR.......
555" " ACCAA555" : ADAAA555:
013" """""""021" .......027.
._____|______. |
| | |
"""" .VAR....... .VAR....... .VAR.......
A66" : ACCAAA66: : ACCAAB66: : ADAAAA66:
014" .......022. .......023. .......028.
|
|
"""" .VAR.......
AA7" : ADAAAAA7:
015" .......029.
_____. |
| |
"VAR""""""" .VAR.......
" ACBABAAB" : ADAAAAAA:
"""""""017" .......030.