Change Management and Application
Control Facilities Questionnaire

Feature	Weight	N2O Support
Check-in/Check-out
Check-in/Check-out feature	10.0	Yes.
Allow/Disallow concurrent checkout	9.3	Yes, check-out may be limited to 1-15 people, or disabled completely.
Ability to alert developers of check-out status (at time of edit)	10.0	Yes, developers attempting to edit or check-out a checked-out module will be alerted by warning messages and prevented from working with checked out objects.
Reporting - currently checked out objects and activity audit	8.1	Yes.
Migration Control
Administrator defined migration paths	7.9	Yes, Migration Profiles are created to specify valid migration paths to N2O. Only migrations between these paths are permitted.
Perform on-line migrations	10.0	Yes, N2O offers this capability.
Perform batch, or scheduled, migrations	9.3	Yes, N2O offers the capability to migrate objects in batch, and batch migrations may be postdated to take place on or after a specific date/time.
Synchronize multiple migration events	4.1	Yes. Multiple target migrations are supported, as are other methods for synchronizing multiple migration events.
Option to include selected referenced objects of migrated module(s)	7.0	Yes. N2O includes PREDICT XREF integration to identify objects related to those selected for migration. The related objects can optionally be included in the migration.
Automatic recompile	10.0	Yes. N2O includes an Autocompile option for automatically compiling selected objects after migration.
Ability to backout migration after compile errors	8.4	Yes.
Non-NATURAL object support (PREDICT DDMs, relationships, rules, etc.)	3.6	Yes. N2O migrates NATURAL, PREDICT, and SYSERR objects, with a single request.
3GL support (COBOL, JCL, etc.)	6.0	Yes, through the optional (and separately priced) N2O/3GL feature.
Reporting - migration audit	6.3	Yes.
Versioning/Archiving
Versioning during migration between environments	8.6	Yes. N2O will, if directed, automatically archive members overwritten during a migration.
Ability to restore selected version to environment	8.6	Yes. Any archived object may be restored to an environment.
Archival and/or deletion of obsolete versions	8.3	Yes. N2O offers a Purge Archive utility which allows the site to purge the on-line archive of obsolete versions. These purged versions can be put on tape or cartridge and archived for later reference.
View source code for a selected version	8.3	Yes. Source code for any NATURAL object located in a current library or archive file may be viewed by any individual authorized to do so.
Compare Utility
Ability to compare objects across environments	8.3	Yes. N2O supports comparison of objects across environments, including archived objects.
Ability to compare two versions of the same object	8.3	Yes.
Ability to compare source and object	1.0	Yes.
Security and Authorization
Administrator defined authorization levels	8.0	Yes. N2O security controls access to N2O functions, restricts users to valid migration paths, determines which users may approve which migrations, etc. N2O security can optionally be controlled through RACF, ACF2, or TOP SECRET.
User and group definition	9.1	Yes. By defining N2O security profiles support the use of a group concept, as well as "exceptions" for specific users.
Reporting
Version history	5.7	Yes.
Administrative reports	7.0	Yes.
Module cross-reference	7.4	Yes.
Miscellaneous
Customizable user exits (tie in to APIs)	10.0	Yes.
Integration of current environments to change management system	3.0	Yes. N2O has been designed to conform to a site's current environment (libraries, migration paths, etc.) and change management procedures/policies.
Allow for modules outside of the control facility (exceptions)	7.3	Yes. N2O provides support for emergency migration activity outside the normal development cycle. These exceptions are recorded in the N2O audit trail.