|Contents:||Main||Chapter||See Also:||Getting Started Manual||Programmer Manual|
In order to ensure that the internal structure of your files and subfiles is consistent, use the Check/Fix DD Structure option from the Data Dictionary Utilities submenu. You must have READ access to the files being analyzed. In addition, you need DD access for this option to correct erroneous nodes.
This utility looks at a file's identifiers, cross-references, POINTER TO A FILE, VARIABLE-POINTER, and COMPUTED fields. If there are inconsistencies or conflicts between the information in the data dictionary and the structure of the file's global nodes, the Check/Fix DD Structure option will note them.
If you want, the Check/Fix DD Structure option will correct inconsistencies found in the data dictionary. The process will not change any file structures; it only removes or corrects unnecessary or incorrect DD nodes. Data is not affected.
The dialogue for running this option is simple. You specify the file or files you want to check and indicate whether you want to delete incorrect nodes. Then the progress of the checking is displayed followed by a report of any discrepancies found or any changes made. For example:
Select DATA DICTIONARY UTILITY OPTION: CHECK/FIX DD STRUCTURE Check the Data Dictionary. START WITH WHAT FILE: 16033 GO TO WHAT FILE: Remove erroneous nodes? NO// YES DEVICE: HOME// DECSERVER Checking file # 16033 Checking 'ID' nodes for 'Q'. Checking 'IX' nodes. Checking 'PT' nodes. File: 16037 Field: .01 is not a pointer. ^DD(16033,0,"PT",16037,.01) was killed. Checking FIELDs.... Checking subfile # 16033.04 Checking 'IX' nodes. Checking FIELDs... Checking subfile # 16033.42 Checking FIELDs. Returning to subfile 16033.04. Returning to main file....... Checking subfile # 16033.01 Checking 'IX' nodes. Checking FIELDs. Returning to main file.........
In the previous example, the check is being run on a single file. Correction of erroneous nodes has been requested. An incorrect "PT" node was found and deleted.
NOTE: Subfiles are inspected, too.
Application developers might use this tool to clean up their files before export. Site managers may find the reporting function useful for checking a package's files after installation. Erroneous nodes found by this option may be remnants of prior versions of the files; the current install may not be to blame.
Reviewed/Updated: March 4, 2007