The ADSO environments (like IDMS subsystems) and data sets (like executables stored in PDSs) to be managed by AbitMORE ® SCM for IDMS/ADSO (ASI for short), are populated from the existing pre-ASI environments and data sets containing ADSO components, using a combination of 1 or more of the following "strategies", and eventually varying from one ChangeMan ZMF application or library type to another:
- Option 1: the existing pre-ASI environments and data sets remain unchanged, and the ChangeMan ZMF started task receives the only update authority to them.
- Option 2: new environments and data sets are created for ASI usage only, populated via a MASS copy from the pre-ASI environments and data sets, without any regenerates.
- Option 3: new environments and data sets are created for ASI usage only, but not initially populated. Every time a modification to an ADSO component is required, it is staged into ASI, and deleted from the pre-ASI environments and data sets. After some time (like 6 months), the remaining (unchanged) ADSO components from the pre-ASI system are MASS staged into ChangeMan ZMF (e.g. using ASI’s conversion assistance facility).
- Option 4: new environments and data sets are created for ASI usage only, and all ADSO components residing in pre-ASI environments and data sets are MASS staged into ASI, including all regenerates.
When selecting an appropriate strategy from the available options above, it should be clear that:
- "The time needed to convert" will be minimal for option 1, and maximum for option 4, with option 2 and 3 in between.
- "The quality after the conversion" will be relatively low for option 1, and relatively high for option 4, with option 2 and 3 in between.
- "The degree of difficulty to convert" will be minimal for option 1, and maximum for option 4, with option 2 and 3 in between.
AbitMORE offers appropriate consultancy services to help you select from the available options, and if needed develop the required conversion facilities, e.g. using ChangeMan ZMF’s XML services.
The previous population steps may have to be combined with some kind of cleanup operation prior to moving them to ASI’s control. The need to do so however depends on the "quality" of the current pre-ASI environments and data set contents.
Note that for typically 3 GL components (like Cobol batch with IDMS pre-compile) the same options are available also.