• Non-Generated Systems
• Change Control
  (Change Management)
• Print Files
• Validations
• SCAN alternative
• Validman
• Field picker
• Map Enquiry
• Program Logic
• DATISO fields

Change Control
(Change Management)

For use with Generated, Non-Generated and Hybrid systems.

Genesis V will control the movement of Objects, Source and Specs (where appropriate) from Production to 4 layers of Test Environments (Individual Programmer Test, Consolidated Test, Q/A, Pre-production Hold) and back through the particular test phases. Most sites would probably set up Consolidated Test (all programmers), Q/A (senior checking) and Production.

The software includes allocating program changes and tasks to an individual, preventing multiple programmers working on the same object at the same time.

Several layers of Archive are possible.

The V3R4M7 version of change control works only on an individual AS/400 (i.e. Production and Test are on the same AS/400) but future planned developments include "batching-up" a PTF library, transmitting the library to multiple AS/400s and then applying the changes overnight if possible. If the automatic apply fails for whatever reason, the objects already applied are backed-out into the batch up library and the original objects restored to their previous place, and messages are sent to the originating system.

If running multiple connected AS/400s, we have already developed software (included in Genesis V) for transferring Libraries or Source members directly to another machine, or running a command on another machine without STRPASTHR.

Separate Change Control Documentation exists on request.