ChangeMan ZMF package with IDMS/ADSO components

After the checkin of one or more IDMS/ADSO components in ChangeMan ZMF completed, they show up in the package content list as illustrated in the screen-print below (via the component names and types mentioned in red):

This screen-print illustrates that by using AbitMORE SCM for IDMS/ADSO, any IDMS/ADSO component can be included in a regular ChangeMan ZMF package just like any other package component:

• the ADS components are the various IDMS/ADSO components like dialog SITSDA1 or map SITSMA11 (indicated via the blue annotations to the right, which were added here to enhance readability).
• the components with library type S01 or C21 are just a few other package components (mixed in the same package).

What is more, you could use AbitMORE SCM for IDMS/ADSO to request a checkin of just 1 IDMS/ADSO application, and while performing this request also use the processing options to also checkin all its dependent components (in the same change package). Assume this IDMS/ADSO application would consist of (= has as depend components) say 1,400 dialogs, maps and tables. In this case/scenario, this single request would populate a single ChangeMan ZMF package that automatically got populated with all those 1,400 dependent components. And the above screen-print would not only contain 17 components, but over 1,400 components. This feature is one (out of many) unique features included in AbitMORE SCM for IDMS/ADSO.

To further illustrate the unique capabilities (and know-how ...) included in AbitMORE SCM for IDMS/ADSO, consider this variation of the above mentioned scenario about the 1,400 components (actually a real world situation that happened in the past): if you'd use the processing option to only checkin all its updated dependent IDMS/ADSO components (updated in development area as compared to production), you might end up with only 56 (instead of 1,400) ADS package components. Compare this to just regenerating the entire IDMS/ADSO application (with all its 1,400 dependent components) and think about:

• the huge improvement in performance (it now takes like 35 minutes instead of 25 hours ...)!
• the huge potential for reducing MIPs and MSUs (read: reduce the cost to build and migrate IDMS/ADSO applications)! Only this cost reduction factor pays many times for the license and M&E fee for AbitMORE SCM for IDMS/ADSO!
• being sure that for all the other 1,344 dependent components there is not at all any change in any of the building blocks used to generate an IDMS/ADSO executable. Whereas building blocks stands for any ADSO RECs (such as database record layouts, working storage layouts, etc) or ADSO PROs, as further illustrated in the bill of material which is (also automatically) maintained by AbitMORE SCM for IDMS/ADSO.