IDMSDBAN

The IDMSDBAN database analysis utility analyzes the characteristics and structure of a CA IDMS/DB database (both non-SQL and SQL-defined). The utility provides information useful for system tuning, database structuring, and capacity planning.
idmscu19
The IDMSDBAN database analysis utility analyzes the characteristics and structure of a CA IDMS/DB database (both non-SQL and SQL-defined). The utility provides information useful for system tuning, database structuring, and capacity planning.
IDMSDBAN also verifies the integrity of:
  • Page structures
  • Line indexes
  • Record lengths
  • Record locations
  • Set connections for:
    • Chained sets
    • Constraints
    • Indexed sets
    • The CALC set
    • Variable-length-record fragment chains
This article describes the following information:
2
2
Authorization
To
You Need This Privilege
On
Analyze an area
DBAREAD
The area
Analyze a set, constraint, or table
DBAREAD
The area where the set, constraint, or table resides
Syntax
PROCESS statement
  Code on one line only. ►►─PROCESS ─┬─ SUBSCHEMA subschema-name subschema-specification ──────┬───────►             └─ SQL ───────────────────────────────────────────────────┘  ►─┬────────────┬─────────────────────────────────────────────────────────────►◄    ├─ LOCKed ◄──┤    └─ UNLocked ─┘  
Expansion of subschema-specification
►►──┬──────────────────┬─┬────────────┬─┬──────────────┬──────────────────────►◄     └─ DBNAME db-name ─┘ └─ OWNCHECK ─┘ └─ INComplete ─┘  
REPORT statement
  Code on one line only. ►►─┬──────────────────────────────────────────────┬───────────────────────────►◄    └─── REPORT ─┬─────────────────────────────┬───┘                 └─ report-number ─┬─────────┬─┘                                   └─ TERSE ─┘  
AREA statement
  Code on one line only. ►►─┬────────────────────────────────────────┬─────────────────────────────────►◄    └─── AREAs ─┬─ ALL ◄────────────────┬────┘                └─ area-specification ──┘  
Expansion of area-specification
►►─┬─────────────────┬─ area-name ─┬───────────────────────────────┬──────────►◄    └─ segment-name. ─┘             └─ PAGE start-page TO end-page ─┘  
SET statement
  Code on one line only. ►►───┬──────────────────┬────┬───────────────────────────────────────┬────────►◄      └─┬─ SETs ───────┬─┘    ├─ ALL ◄──┬──────────┬─┬─────────┬──────┤        ├─ CONSTRAINT ─┤      │         └─ NOCALC ─┘ └─ NOVLR ─┘      │        └─ INDEX ──────┘      ├─ set-name ─┬────────────────────────┬─┤                              │            └─ ON schema.table-id ───┘ │                              ├─ CALC ────────────────────────────────┤                              └─ VLR ─────────────────────────────────┘  
Input Parameter Statements
IDMSDBAN processing is controlled by the following input parameter statements. If coded, the three types of statements must be coded in the order shown. If not coded, all reports are provided for all areas and sets for the named subschema or SQL-defined database.
Statement descriptions
Statement
Required/ Optional
Description
PROCESS
Required
For non SQL-defined database:
Identifies subschema and DMCL module
Specifies whether areas are to be locked before processing
For SQL-defined database:
Identifies that an SQL-defined database will be processed
Specifies whether areas are to be locked before processing
REPORT
Optional
Controls generation of reports 2, 3, 4, and 5
AREA
Optional
Specifies area(s) to be processed
SET
Optional
Specifies set(s) or constraints and indexes to be processed
PROCESS statement
The PROCESS statement identifies the database to be processed and specifies whether areas are to be locked before processing begins. One PROCESS statement is required for each IDMSDBAN run.
Syntax
Code on one line only. ►►─ PROCESS ─┬─ SUBSCHEMA subschema-name subschema-specification ──────┬──────►              └─ SQL ───────────────────────────────────────────────────┘  ►─┬────────────┬─────────────────────────────────────────────────────────────►◄    ├─ LOCKed ◄──┤    └─ UNLocked ─┘
Expansion of subschema-specification
►►──┬──────────────────┬─┬────────────┬─┬──────────────┬──────────────────────►◄     └─ DBNAME db-name ─┘ └─ OWNCHECK ─┘ └─ INComplete ─┘
Parameters
  • SUBSCHEMA
    subschema-name
    Identifies the subschema containing the areas, sets, and records to be processed. The subschema must contain complete descriptions for all of its sets and records.
    When processing the DDLCAT and DDLCATX areas, you must use the SUBSCHEMA parameter and the IDMSCATZ subschema name.
    When processing the DDLCATLOD area you must use the SUBSCHEMA parameter and the IDMSCATL subschema name.
  • DBNAME
    db-name:
    Identifies the name of the database to bind to at run time. If no DBNAME is specified, the default is the DBNAME specified in the SYSIDMS parameter file.
  • OWNCHECK
    Indicates that checks for ownerless loops in chained sets is to be performed. If this parameter is omitted, IDMSDBAN will not check for chained sets that form a loop but do not include an owner record occurrence.
    This check will increase the run time of the utility and may require that the allocation for the SYS002 file in the IDMSDBN2 step be increased.
  • INComplete
    Specifies that the named subschema does not include all record types. INCOMPLETE suppresses messages that would otherwise appear for record types not included in the subschema.
  • SQL
    Specifies that an SQL-defined database is to be processed.
    Based upon the segments identified on the AREA statement and the sets or constraints identified on the SET statement, IDMSDBAN will build a subschema to process an SQL-defined database.
    When processing the DDLCAT and DDLCATX areas, you must use the SUBSCHEMA parameter and the IDMSCATZ subschema name.
    When processing the DDLCATLOD area you must use the SUBSCHEMA parameter and the IDMSCATL subschema name.
  • LOCKed/UNLocked
    Specifies whether IDMSDBAN is to lock the areas to be processed:
    • LOCKED
      (default) directs IDMSDBAN to lock the areas during IDMSDBN1 processing. When you specify LOCKED, the areas involved cannot be updated by another application during IDMSDBAN execution.
    • UNLOCKED
      directs IDMSDBAN not to lock the areas to be processed. When UNLOCKED is specified, the areas involved can be updated during IDMSDBAN execution.
REPORT statement
The optional REPORT statement controls the generation of reports 2, 3, 4, and 5. IDMSDBAN always generates reports 1 and 1A.
By default, if you do not supply a REPORT statement or if you supply a REPORT statement without any parameters, IDMSDBAN will generate all reports.
Syntax
Code on one line only. ►►─┬──────────────────────────────────────────────┬───────────────────────────►◄    └─── REPORT ─┬─────────────────────────────┬───┘                 └─ report-number ─┬─────────┬─┘                                   └─ TERSE ─┘
Parameters
  • report-number:
    Specifies the number of the report to be generated. Valid report numbers are 1, 1A, 2, 3, 4, and 5.
    If no REPORTS statement is coded or if a REPORTS statement is provided without any report numbers,
    all
    reports are generated.
  • TERSE
    Applies to reports 3, 4, and 5 only, as follows:
    • TERSE causes
      report 3
      to be produced only for sets that have at least one non-empty set occurrence.
    • TERSE causes
      report 4
      to be produced only for record types with at least one occurrence in the database.
    • TERSE causes
      report 5
      to be produced only for sets with at least one occurrence in the database.
AREA statement
The AREA statement specifies the areas to be processed. If no AREA statement is coded, all areas in the named subschema or segment are processed.
Syntax
Code on one line only. ►►─┬────────────────────────────────────────┬─────────────────────────────────►◄    └─── AREAs ─┬─ ALL ◄────────────────┬────┘                └─ area-specification ──┘
Expansion of area-specification
►►─┬─────────────────┬─ area-name ─┬───────────────────────────────┬──────────►◄    └─ segment-name. ─┘             └─ PAGE start-page TO end-page ─┘
Parameters
  • AREAs
    Specifies the area(s) to process.
  • ALL
    Specifies that all areas included in the specified subschema are to be processed.
    ALL is the default.
    You cannot use the ALL option if SQL was selected on the PROCESS statement.
  • segment.:
    For SQL-defined databases, identifies the name of the segment to be processed. You must specify
    segment-name
    if SQL was selected on the PROCESS statement.
    When processing a non-SQL-defined database, do not specify
    segment-name
    .
    Segment-name
    must be a 1 through 8-character value.
  • area-name:
    Identifies the name of an area to be processed.
    Area-name
    must be a 1 through 18-character value.
  • PAGE
    start-page-n
    TO
    end-page-n:
    Specifies the range of pages to be processed within the named area. The specified page range must be included within the area page range.
    By default, if you do not specify a page range, the entire area will be processed.
    If you do specify a page range, be sure that the page range selected includes all database pages that can contain owner or member records of all sets to be processed. Otherwise, they won't be processed.
    Start-page
    and
    end-page
    must contain numeric values and can be from 1 through 10-characters in length.
SET Statement
The SET statement specifies the sets, constraints, or indexes to be processed.
Syntax
Code on one line only. ►►───┬──────────────────┬────┬───────────────────────────────────────┬────────►◄      └─┬─ SETs ───────┬─┘    ├─ ALL ◄──┬──────────┬─┬─────────┬──────┤        ├─ CONSTRAINT ─┤      │         └─ NOCALC ─┘ └─ NOVLR ─┘      │        └─ INDEX ──────┘      ├─ set-name ─┬────────────────────────┬─┤                              │            └─ ON schema.table-id ───┘ │                              ├─ CALC ────────────────────────────────┤                              └─ VLR ─────────────────────────────────┘
Parameters
  • SETs/CONSTRAINT/INDEX
    Identifies the sets, constraints, or indexes to process.
    The keywords SET, CONSTRAINT, and INDEX are synonyms and can be used interchangeably.
    All owners and members must be included in the area to be analyzed and page ranges must be identified in the AREA statement or no sets or constraints are processed.
  • ALL
    Indicates that all of the following sets associated with a specified subschema or segment are to be processed for either a non-SQL or SQL-defined database:
    • All chained and indexed sets defined in the subschema specified in the PROCESS statement
    • All constraints within the specified segment
    • The CALC set
    • Sets of variable-length record fragments located within the areas specified in the AREA statements
    ALL is the default.
  • NOCALC
    Removes the CALC set from the list of sets specified by ALL.
  • NOVLR
    Removes the set of variable length record chains from the list of sets specified by ALL.
  • set-name:
    Identifies the name of a set to be processed.
  • ON
    schema.table-id:
    If SQL was specified on the PROCESS statement, you must identify the name of the SQL schema and table identifier the constraint or index is associated with. You do not specify a
    schema.table-id
    for non-SQL-defined databases.
    Schema
    is a 1 through 18-character value and
    table-id
    is a 1 through 18-character value.
  • CALC
    Directs IDMSDBAN to process the CALC set within the specified area(s).
  • VLR
    Directs IDMSDBAN to process all sets of variable-length record fragment chains located within the specified area(s).
Usage
Input
Input to the IDMSDBAN utility consists of statements to control the utility processing.
Output
The IDMSDBAN utility generates message listings.
Execution mode
You can execute the IDMSDBAN utility in local mode only.
Usage considerations
Specifying dictionary name for SQL-defined databases
When processing an SQL-defined database, you must specify the dictionary name or catalog segment that IDMSDBAN connects to using the SYSIDMS DBNAME parameter (
not
the DICTNAME parameter).
For more information about the SYSIDMS parameter file, see the
CA IDMS Common Facilities Section
.
Subschema
The subschema that describes the database areas to be processed must include all member record types for all sets included in the subschema.
Processing DDLCAT, DDLCATX, and DDLCATLOD areas
When processing the DDLCAT and DDLCATX areas, you must use the PROCESS statement SUBSCHEMA parameter and the IDMSCATZ subschema name.
When processing the DDLCATLOD area you must use the PROCESS statement SUBSCHEMA parameter and the IDMSCATL subschema name.
Areas
By default, IDMSDBAN locks the areas to be processed. If IDMSDBAN attempts to lock an area that is already locked, the utility terminates. To prevent this, perform one of the following actions:
  • Either vary offline or vary to retrieval the areas to be processed before running IDMSDBAN.
  • Specify UNLOCKED in the PROCESS parameter statement.
    If you specify UNLOCKED and the database is updated by another application during IDMSDBAN processing, the statistics in reports 2, 3, 4, and 5 may be inaccurate, and the messages in reports 1 and 1A may be misleading.
Page ranges
The page ranges selected for processing must include all database pages that can contain owner or member records of any set(s), constraints, or indexes to be processed.
If you specify a set, constraint, or index with an owner or member record outside the specified pages, IDMSDBAN will terminate with an error.
Indexed sets
If an indexed set is specified for processing, processing must also be requested for all other indexed sets for which the SR8 records can occur on the same pages as the SR8 records for the specified set.
IDMSDBAN has two parts
IDMSDBN1 and IDMSDBN2.
Intermediate work file size
The size of the intermediate work files will vary depending on the size and complexity of the database being analyzed.
  • IDMSDBN1 will generate one output record for each pointer position in each record for each set being processed. The file can be written to tape or disk; however, to ensure adequate space, tape is recommended.
  • IDMSDBN2 uses an intermediate work file to hold records it is working on. For every record it receives from IDMSDBN1, it will produce up to two intermediate work records. If the OWNCHECK option has been specified, it is necessary for the utility to produce these records for each occurrence of a record participating in a chained set.
Tape management systems and IDMSDBAN work files
The SYS002 work file used by IDMSDBN2 is written to and read from repeatedly. If this file is placed on a tape, then your tape management system may prevent IDMSDBN2 from overwriting the file after it has written to the file the first time. If the tape management system installation defaults allow, specify a zero retention period for the work file and/or specify DISP=(NEW,DELETE) for the work file.
If problems are detected
If the messages issued by IDMSDBAN indicate that problems exist in the database, the database should not be updated in between the time of the IDMSDBAN run and the time that the problems are corrected.
IDMSDBN1
IDMSDBN1 sweeps each specified area. For each area, IDMSDBN1:
  • Collects statistics
    • Detailed statistics for each area and record type.
    • Summary statistics for user-defined chained and indexed sets.
  • Generates an intermediate work file
    IDMSDBN1 generates input to IDMSDBN2.
    Each record in the file represents a pointer in a set connection between two records. For example, one record might represent the next pointer between two member records in a user-defined set; another might represent the connection between the root of a variable-length record and the first fragment of the record.
    Each record includes the database keys of the two connected records. The database key of the record that contains the pointer to the other record is the FROM database key. The database key of the record to which the first record points is the TO database key.
Output
Report
Required/ Optional
Description
#1: Messages
Required
Lists input parameters used in the run.
Lists all messages issued by IDMSDBN1. The messages:
Report errors in the parameter input
Trace the processing of areas
Define any unexpected conditions detected by the program
#2: Area Information
Optional
Provides detailed area statistics. The report includes histograms of space availability and of data records per page.
#3: Set Statistics
Optional
Presents summary set statistics.
#4: Record Information
Optional
Provides detailed statistics for each record type in each area being analyzed. The report includes a histogram of data records per page.
IDMSDBN2
As a performance enhancement for the IDMSDBN2 step, the SIZE=E99999999 parameter has been added to the various sorts that are executed. However, some sort packages do not allow the usage of the SIZE= parameter on their SORT statements. If your sort package does allow the specification of the SIZE= parameter, you can reduce the run time of IDMSDBN2 by coding SORTSIZE=ON in the jobstep's SYSIDMS input file.
IDMSDBN2 does the following:
  • Verifies set integrity. This is done in three steps.
    1. Reading the intermediate work file from IDMSDBN1
    2. Iteratively massaging and sorting the records
    3. Creating chains
      A
      chain
      is a path that originates at a record located at a FROM database key and terminates at a record located at a TO database key.
      IDMSDBN2 concatenates chains until a closed loop is created. A loop is created when the record at the last TO database key matches the record at the first FROM database key.
      Each chain created by IDMSDBN2 is associated with a set. IDMSDBN2 verifies the integrity of sets by ensuring that each chain is complete and contains one and only one owner.
  • Collects detailed set statistics.
Output
Report
Required/ Optional
Description
#1A: Messages
Required
Lists all messages issued by IDMSDBN2. The messages:
Trace the processing of the chain file.
Report inconsistencies detected during chain processing.
#5: Set Analysis Information
Optional
Provides detailed statistics for each set type processed.
Chained sets -- The report includes histograms of chain length, of page changes, and of pages used to store the set.
Sets of variable-length-record fragments -- The report includes a histogram of pages used to store the set.
Indexed sets owned by a user record -- The report includes histograms of SR8 usage in set occurrences, of members in set occurrences, and of SR8 levels in set occurrences. (SR8 records are internal index records.)
JCL Considerations
The JCL to execute the IDMSDBAN utility program must include statements to define:
  • For IDMSDBN1:
    • For SQL databases, you must specify the name of the catalog to be processed on the SYSIDMS DBNAME parameter and
      not
      the DICTNAME parameter.
    • The files that map to the areas to be processed.
    • The SYSIPT file containing input parameters.
    • SYS002 contains output for use by IDMSDBN2 (this file is known to IDMSDBN2 as SYS001).
  • For IDMSDBN2:
    • SYS001 containing the output from IDMSDBN1 (this file was known to IDMSDBN1 as SYS002).
    • SYS002 is a temporary storage file.
    • SORTWK
      nn
      are sort work files. The number and size depends on the sort package you use.
    • SORTMSG containing sort output messages.
    • SYSLST is the destination for the reports the utility creates. If this DD points to a sequential file, pre-allocate the file before the IDMSDBN2 step and ensure the file has a disposition within the step of DISP=MOD. If you fail to do so, Report 1A will not be present on the file at step completion.
For more information about the generic JCL used to execute the batch command facility, see the section for your operating system in this section.
Example
No REPORT parameter specified
If you run IDMSDBAN with the following input parameters, all areas and all sets in the EMPSS01 subschema will be processed and all reports will be produced. All reports are produced because a REPORT parameter is not specified.
process subschema empss01 dbname empdemo unlocked;
With REPORT parameters
If you run IDMSDBAN with the following input parameters, only the named areas and sets will be processed as follows:
  • The entire EMP-DEMO-REGION area
  • Pages in the range 5007102 through 5007149 in the ORG-DEMO-REGION
  • Reports 1, 1A, 3 and 5 will be generated
  • Report 3 will be produced for all of the named sets
  • Report 5 will be produced only for the named sets that have at least one occurrence in the database
process subschema empss01 incomplete report 3 report 5 terse area emp-demo-region area org-demo-region page 5007102 to 5007149 set dept-employee set office-employee set emp-name-ndx;
Sample Output
The following reports are generated when no REPORT parameters are specified as in the first example.
Report 1: Messages Phase I
 IDMSDBAN - DATA BASE ANALYSIS                          REPORT 1:  MESSAGES                         DATE        TIME      PAGE                                                                                                   mm/dd/yy    20234050       1  PARAMETER CARD:    PROCESS SUBSCHEMA EMPSS01 DBNAME EMPDEMO UNLOCKED  PARAMETER CARD:    AREA EMP-DEMO-REGION  IDMSDBAN - DATA BASE ANALYSIS                          REPORT 1:  MESSAGES                         DATE        TIME      PAGE                                                                                                 mm/dd/yy    20234050       2
Report 2: Area
 598601 - AREA PROCESSING BEGINNING: EMPDEMO.EMP-DEMO-REGION  IDMSDBAN - DATA BASE ANALYSIS                         REPORT 2:  AREA DATA                         DATE        TIME      PAGE                                                                                                                mm/dd/yy    20234050       1  AREA:      EMPDEMO.EMP-DEMO-REGION  SUBSCHEMA: EMPSS01  AREA PAGE RANGE - START PAGE:                                            75,001                      END PAGE:                                            75,100  PAGES ALLOCATED FOR AREA:                                                   100  PAGE RANGE ANALYZED - START PAGE:                                        75,001                          END PAGE:                                        75,100  PAGES PROCESSED FOR AREA IN THIS RUN:                                       100  NUMBER OF SMP WITHIN PAGES PROCESSED:                                         1  PAGE SIZE IN BYTES:                                                       4,276  MAXIMUM RECORDS ALLOWED PER PAGE:                                           255  BYTES USED IN PAGES PROCESSED:                                           29,204  BYTES AVAILABLE IN PAGES PROCESSED:                                     394,120   NUMBER OF LOGICALLY FULL PAGES:                                               0  BYTES AVAILABLE ON LOGICALLY FULL PAGES:                                      0  NUMBER OF DATA RECORDS IN PAGES PROCESSED:                                  346  NUMBER OF PAGES WITH EMPTY CALC CHAINS:                                      58  NUMBER OF RELOCATED RECORDS:                                                  0  NUMBER OF LOGICALLY DELETED RECORDS:                                          0  NUMBER OF VLR FRAGMENTS:                                                      0  NUMBER OF LINE INDEXES FOR PHYSICALLY DELETED RECORDS:                        0  SPACE AVAILABILITY HISTOGRAM  PERCENT OF BYTES             PAGES         TOTAL      PERCENT OF     GRAPH  AVAILABLE ON PAGE                        BYTES (000)  TOTAL PAGES    ...10...20...30...40...50...60...70...80...90..100        100                      57              242         58        XXXXXXXXXXXXXXXXXXXXXXXXXXXXX      90 - 99                    22               86         22        XXXXXXXXXXX      80 - 89                    14               51         14        XXXXXXX      70 - 79                     2                7          2        X      60 - 69                     2                5          2        X      50 - 59                     0                0          0      40 - 49                     1                2          1        /      30 - 39                     1                1          1        /      20 - 29                     0                0          0      10 - 19                     0                0          0       1 -  9                     0                0          0    LESS THAN 1                   0                0          0  AVERAGE BYTES AVAILABLE PER PAGE (ALL PAGES)                   3,981  AVERAGE BYTES AVAILABLE PER PAGE (NON-EMPTY PAGES)             3,624
Report 2: Area
 IDMSDBAN - DATA BASE ANALYSIS                         REPORT 2:  AREA DATA                         DATE        TIME      PAGE                                                                                                                mm/dd/yy    20234050       2 0  AREA:      EMPDEMO.EMP-DEMO-REGION         (CONTINUED)  SUBSCHEMA: EMPSS01  DATA RECORDS PER PAGE HISTOGRAM   DATA RECORDS                PAGES                    PERCENT OF     GRAPH     PER PAGE                                           TOTAL PAGES    ...10...20...30...40...50...60...70...80...90..100         0                       57                          58        XXXXXXXXXXXXXXXXXXXXXXXXXXXXX       1 - 25                    40                          40        XXXXXXXXXXXXXXXXXXXX      26 - 51                     2                           2        X      52 - 76                     0                           0      77 -102                     0                           0     103 -127                     0                           0     128 -152                     0                           0     153 -178                     0                           0     179 -203                     0                           0     204 -229                     0                           0     230 -254                     0                           0        255                       0                           0  AVERAGE DATA RECORDS PER PAGE (ALL PAGES)                          3  AVERAGE DATA RECORDS PER PAGE (NON-EMPTY PAGES)                    8
Report 3: Set Statistics
 IDMSDBAN - DATA BASE ANALYSIS                       REPORT 3:  SET STATISTICS                      DATE        TIME      PAGE                                                                                                                 mm/dd/yy    20234050       1 0  SET:         EMP-EMPOSITION       MODE:  CHAIN        ORDER:  FIRST  SUBSCHEMA:   EMPSS01                  NAME         SET MEMBERSHIP   NUMBER OF      EMPTY SETS    UNCONNECTED     LOCATION MODE                                    TYPE         RECORDS                       MEMBERS  OWNER:       EMPLOYEE                             56              0                            CALC  MEMBERS:     EMPOSITION             MA            68                              0            VIA EMP-EMPOSITION                                                _________                    ___________                                                    68  MEMBER RECORDS              0  UNCONNECTED MEMBERS  AVERAGE MEMBERS PER SET FOR NON-EMPTY SETS                         1
Report 4: Record Data
 IDMSDBAN - DATA BASE ANALYSIS                        REPORT 4:  RECORD DATA                        DATE        TIME      PAGE                                                                                                                 mm/dd/yy    20234050       1 0  RECORD:        EMPLOYEE          RECORD ID:    415           LOCATION MODE: CALC  SUBSCHEMA:     EMPSS01  AREA:          EMPDEMO.EMP-DEMO-REGION  FLR/VLR:       FLR  DATA LENGTH:                                                                116  RECORD LENGTH (DATA AND PREFIX):                                            188  PAGE RANGE FOR RECORD IN AREA - START PAGE:                              75,003                      END PAGE:                                            75,100  PAGES ALLOCATED FOR RECORD IN AREA:                                          98  PAGE RANGE ANALYZED - START PAGE:                                        75,003                          END PAGE:                                        75,100  PAGES PROCESSED FOR RECORD IN AREA IN THIS RUN:                              98  NUMBER OF SMP WITHIN PAGES PROCESSED:                                         0  PAGE SIZE IN BYTES:                                                       4,276  BYTES USED FOR THIS RECORD TYPE IN PAGES PROCESSED:                      10,976  BYTES AVAILABLE IN PAGES PROCESSED:                                     392,736  NUMBER OF RECORDS OF THIS TYPE IN PAGES PROCESSED:                           56  NUMBER OF RELOCATED RECORDS:                                                  0  NUMBER OF LOGICALLY DELETED RECORDS:                                          0  DATA RECORDS PER PAGE HISTOGRAM   DATA RECORDS                PAGES                    PERCENT OF     GRAPH     PER PAGE                                           TOTAL PAGES    ...10...20...30...40...50...60...70...80...90..100         0                       57                          58        XXXXXXXXXXXXXXXXXXXXXXXXXXXXX       1 - 25                    41                          42        XXXXXXXXXXXXXXXXXXXXX      26 - 51                     0                           0      52 - 76                     0                           0      77 -102                     0                           0     103 -127                     0                           0     128 -152                     0                           0     153 -178                     0                           0     179 -203                     0                           0     204 -229                     0                           0     230 -254                     0                           0        255                       0                           0  AVERAGE DATA RECORDS PER PAGE (ALL PAGES)                                       0  AVERAGE DATA RECORDS PER PAGE (PAGES WITH THIS RECORD TYPE)                     1
Report 1A: Messages Phase II
 IDMSDBAN PHASE II - SET ANALYSIS                         REPORT 1A:  MESSAGES                      DATE        TIME      PAGE                                                                                                                 mm/dd/yy    20240900       1  599001 - PHASE II PROCESSING BEGUN  599803 - END PASS                                          0  599801 - FROM-RECORDS WRITTEN TO SORT                    630  599802 - TO-RECORDS WRITTEN TO SORT                      630  599806 - INDEX SR8  DESCRIPTORS WRITTEN                    4  599807 - INDEX DOWN DESCRIPTORS WRITTEN                   58  599808 - INDEX UP   DESCRIPTORS WRITTEN                   58  599809 - INDEX NO-UP MEM  DESCRIPTORS WRITTEN              0  599810 - INDEX NO-UP DOWN DESCRIPTORS WRITTEN              0  599803 - END PASS                                          1  599801 - FROM-RECORDS WRITTEN TO SORT                      0  599802 - TO-RECORDS WRITTEN TO SORT                        0  599805 - INDEX PATHS WRITTEN TO SORT                       0  599806 - INDEX SR8  DESCRIPTORS WRITTEN                    1  599807 - INDEX DOWN DESCRIPTORS WRITTEN                   19  599808 - INDEX UP   DESCRIPTORS WRITTEN                   19  599803 - END PASS                                          2  599801 - FROM-RECORDS WRITTEN TO SORT                      0  599802 - TO-RECORDS WRITTEN TO SORT                        0  599805 - INDEX PATHS WRITTEN TO SORT                       0  599806 - INDEX SR8  DESCRIPTORS WRITTEN                    0  599807 - INDEX DOWN DESCRIPTORS WRITTEN                    0  599808 - INDEX UP   DESCRIPTORS WRITTEN                    0
Report 5: Set Analysis
 IDMSDBAN PHASE II - SET ANALYSIS                    REPORT 5:  SET ANALYSIS DATA                   DATE        TIME      PAGE                                                                                                                    mm/dd/yy    20240900       1  SET:            EMP-EMPOSITION     MODE:   CHAIN        ORDER:  FIRST          SUBSCHEMA:   EMPSS01  OWNER:          EMPLOYEE  MEMBERS:        EMPOSITION  CHAIN LENGTH HISTOGRAM    CHAIN LENGTH                 NUMBER OF SETS         PERCENT OF     GRAPH                                                        TOTAL SETS     ...10...20...30...40...50...60...70...80...90..100         0                                   0                0         2                                  47               84        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX         3                                   6               11        XXXXX/         4                                   3                5        XX/       5 -   8                               0                0       9 -  16                               0                0      17 -  32                               0                0      33 -  64                               0                0      65 - 128                               0                0     129 - 256                               0                0     257 - 512                               0                0    OVER   512                               0                0  AVERAGE CHAIN LENGTH (ALL SETS):                            2  AVERAGE CHAIN LENGTH (NON-EMPTY SETS):                      2  MAXIMUM CHAIN LENGTH:                                       4
More Information
  • For more information about database structures analyzed by IDMSDBAN, see the
    CA IDMS Database Administration Section
    .
  • For more information about database tuning, see the
    CA IDMS Database Design Section
    .