The ADSO XREF Utility has been designed to assist analysts and programmers in the development and maintenance of ADS/ONLINE and ADS/BATCH applications. It has also proven valuable to Data and Database Administrators in the determination of entity usage and as an aid during database modification.
The primary objective of the AXU is to provide all of the necessary where used information which is a prerequisite to any project. While some of this data may be obtained from standard CA-IDMS reports, answers to the following questions would be difficult to find.
Which processes reference this data element?
In which processes is this record stored ? modified ? obtained ?
Which processes or maps issue this message (stored in the IDD) ?
Which processes include this module ?
Which maps use this edit table ?
Which dialogs link, transfer to, or invoke this dialog ?
The ADSO XREF Utility answers these, and many more, questions by scanning the contents of process code and map fields. In so doing, the AXU produces a variety of reports which cross reference the usage of dictionary entities which are related to ADS dialog(s). The entities cross-referenced by the AXU include elements, records, sets, areas, maps, tables, messages, modules, included modules, subroutines, and called dialogs. Most of the reports standardly display the issuing dialog name, process name, process text sequence, and the verb.
The AXU is supported in all environments which support any flavor of COBOL.
Release 10.7 of the AXU may be used with dictionaries supported by any release of CA-IDMS.
While it is recommended that you read this manual from cover to cover, we realize that it is highly unlikely that this recommendation will be followed. So, this is an attempt to highlight the required reading for new users of the AXU.
The Installation section explains the installation of the AXU.
System Overview within the System Description section will provide you with a high level overview of all available reports. It, also, gives an indication of which reports answer which kind of questions.
Input Statement Types, for each report, describe the types of input specifications which are available. Most reports require at least one Selection statement and, if you are reporting on a secondary dictionary, also require a Dictionary Definition statement. All other input is optional.