Source-to-load relationships for IDMS/ADSO

To complete the checkin request for an IDMS/ADSO component, ChangeMan ZMF will submit a batch job.

If the job completed without errors, various outputs (stored in the ChangeMan ZMF package) will be created by such job. E.g.:

• for an IDMS/ADSO map a component of type 'map decompile syntax' (e.g.: IMD) will be created, among other types that will be created also.
• for an IDMS/ADSO dialog a component of type 'load without debug options to be stored in IDD' (e.g.: ILI) will be created, among other types that will be created also.

To keep track of what actually got produced by such job, appropriate source-to-load relationships are created, and which will vary by type of IDMS/ADSO component.

The screen-print here shows the source-to-load relationships for an IDMS/ADSO message, an IDMS/ADSO application and an IDMS/ADSO dialog.

After paging down on the above shown panel, the source-to-load relationships are also shown for an IDMS/ADSO map and an IDMS/ADSO table, as shown in the next screen-print.

To understand what all these relationships actually stand for (the 3 chars mnemonics shown here are rather cryptic), it may help to first look up the various library type definitions as configured in application administration (which include descriptions for ILI, IDI, IMD, ...).

Some types of staging output (library types) are created for (nearly) all types of IDMS/ADSO components, such as:

• IXF, the bill of material of the IDMS/ADSO component, used for all sorts of impact analysis features.
• IEC, used to extend standard ChangeMan ZMF's audit function so that special out-of-synch situations for IDMS/ADSO components will be flagged, such as:
  • ensure that all IDMS/ADSO dialogs are (re-) generated after generating a map that it is displayed by the dialog (to prevent runtime errors later on in test or production areas).
  • ensure that all IDMS/ADSO maps are (re-) generated after generating an IDMS/ADSO table that it is used by the map (to prevent runtime errors later on in test or production areas).
• LSI, containing the (compressed) listing with all sorts of interesting SYSPRINTs, etc produced as part of the batch job.