Database load reports

After the load job is submitted and executed, several reports can be produced. Some of the reports are generated by File-AID for IMS/ISPF, while others are from utility programs. Data Base Load Exception Report through Data Base Load Report - Related Data Base Summary (Part 2) show the File-AID for IMS reports that can be generated. Not all reports are produced every time.

Data Base Load Exception Report

The first report, shown in the following figure, is the Data Base Load Exception Report. In this report, error messages that describe problems that File-AID for IMS encountered during the load process are written. The concatenated key for the segment that is in error is shown below the error message, if applicable. If there were no errors during the load process, this report is omitted.

Data Base Load Exception Report

Data Base Load Report

The second report is the Data Base Load Report. It consists of the following parts:

• Data Base Dataset Summary (Data Base Load Report - Data Base Dataset Summary)
• Primary Data Base Summary (Data Base Load Report - Primary Data Base Summary)
• Related Data Base Summary (Data Base Load Report - Related Data Base Summary (Part 1) and Data Base Load Report - Related Data Base Summary (Part 2))

Data Base Dataset Summary

The top section of the Data Base Dataset Summary shows the FROM extract file name, the TO DBD dataset and member names, the load job type, and update mode. The bottom section shows all the databases with their associated ddnames and dataset names. This section is similar to the layout of the Data Base Load - Data Base Dataset Specification screen.

Data Base Load Report - Data Base Dataset Summary

Primary Data Base Summary

The Primary Data Base Summary (see the following figure) shows a count of the records read from the load FROM file, the segments loaded into the primary database, and the segments that were not loaded because of an error. The counts are shown by segment name, with the level and segment hierarchy shown to the left of the segment name. Informational messages that pertain to segment types are shown to the right of the Exception Segments column. Column totals are shown at the bottom of the page.

Data Base Load Report - Primary Data Base Summary

Related Data Base Summary

The Related Data Base Summary (Data Base Load Report - Related Data Base Summary (Part 1) and Data Base Load Report - Related Data Base Summary (Part 2)) shows information about each database related to the primary database. If there are no databases related to the primary database, this part of the report is omitted. Counts of the records read from the load FROM file, the number of segments loaded into the related database to resolve logical and application relationships, and the number of segments not loaded because of an error are shown. Informational messages that pertain to segment types are shown to the right of the Exception Segments column. Column totals are shown at the bottom of the page.

There are four informational messages that can appear on the Primary and Related Data Base Summary reports to the right of the Exception Segments column. Following are the possible messages:

SEGMENT PADDED/TRUNCATED

At least one segment occurrence of this segment type was padded with blanks or truncated. This action was taken because the segment length indicated on the load FROM file record was not valid for the segment in the DBD used for the load.

LCHILD SEG x USED FOR LOAD

Segment type x, which is logically paired with this segment type, was used during the load to establish the logical relationship. File-AID for IMS/ISPF chose segment type x based on the rules explained in Advanced Topics.

LCHILD MAY LINK TO 1ST LOG. PARENT

This segment type may have been linked to the first occurrence of its logical parent segment type and not to the logical parent occurrence where it was originally linked. This is possible because the logical parent did not have a unique concatenated key.

SOME LCHILD NOT ISRTD, NO LOG. PAR

At least one logical child segment that File-AID for IMS/ISPF attempted to insert did not have a logical parent on the database. This occurs when selection criteria was used by the Extract function to limit the number of logical relationships chased. The Exception Segment count is incremented for each logical child segment that was not inserted because of this condition.

Data Base Load Report - Related Data Base Summary (Part 1)

Data Base Load Report - Related Data Base Summary (Part 2)