|IDMS/ADSO in CMN/ZMF|

Printer-friendly version PDF version

Parallel development notifications for IDMS/ADSO

Because of the close integration of AbitMORE SCM for IDMS/ADSO with ChangeMan ZMF, various parallel development features included in ChangeMan ZMF automagically become available for IDMS/ADSO components also. One such feature is illustrated in the screen-print below:

Parallel development notifications for IDMS/ADSO in ChangeMan ZMF

Subject:
AbM SCM Solutions:

Source-to-load relationships for IDMS/ADSO

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

Source-to-load relationships (part 1)

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

Subject:
AbM SCM Solutions:

Bill of material to audit IDMS/ADSO components

The batch job that ChangeMan ZMF submits at the end of a checkin request for an IDMS/ADSO component, performs all sorts of processing to prepare for the migration of the IDMS/ADSO component to test- and/or production areas later on. Part of this processing relates to producing the bill of material for the IDMS/ADSO component being processed. The screen-print here shows such bill of material for an IDMS/ADSO dialog.

Subject:
AbM SCM Solutions:

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):

ChangeMan ZMF package with IDMS/ADSO components

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:

Subject:
AbM SCM Solutions:

Component attributes and processing options

To checkin and stage IDMS/ADSO components in ChangeMan ZMF, an IDMS/ADSO developer uses the traditional ChangeMan ZMF features available to do so. Typically using the CMNSTG04 panel for that.

Component attributes and checkin options

Subject:
AbM SCM Solutions:

IDMS/ADSO library types in ChangeMan ZMF

IDMS/ADSO library types in ChangeMan ZMF

To actually manage IDMS/ADSO components with ChangeMan ZMF, a number of library types are defined within global and application admin, as illustrated in the screen-print here via the library types mentioned in red.

 

Subject:
AbM SCM Solutions:

Does ASI store loads in IDD or in PDSs ?

When AbitMORE SCM for IDMS/ADSO promotes or installs ADSO executables, do they get stored in IDD load areas or in regular PDSs ?

For ADSO executables, AbitMORE ® SCM for IDMS/ADSO (ASI for short) offers an administrator choice about where to store ADSO executables: either in IDD load areas, or in regular PDS members. This choice may vary from one target to another (e.g.: lowest level of promotion in IDD load areas, while for the highest level of promotion they are to be stored in IDD load areas).

Taxonomy upgrade extras:

Does ASI require any regenerates to start using it?

Do we need to regenerate anything to implement AbitMORE SCM for IDMS/ADSO?

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:

Taxonomy upgrade extras:

AbitMORE SCM for IDMS/ADSO - Previews

Because a picture is worth more then 1000 words, how about a preview of some of the major features of AbitMORE SCM for IDMS/ADSO.

It should also give you a very good understanding of how it is perfectly integrated in vanilla ChangeMan ZMF ...

Subject:
AbM SCM Solutions:

Pages

Subscribe to |IDMS/ADSO in CMN/ZMF|