3. Maintenance Policies and Procedures › 3.2 User Maintenance Procedures › 3.2.2 User Change Control Procedure › 3.2.2.5 Implementation

3.2.2.5 Implementation

Implementation of the modification may be done after
successful testing on the CA MICS TEST database unit. The
nature of the modification dictates the method of
implementation.

It is important to have an integration plan.  The modules
changed and their locations must be listed, and the module
movement order documented.

Tested, modified modules may be moved back to the CA MICS
sharedprefix libraries, if such is the nature of the
modification.  All affected modules must be moved at once,
and the change will be enabled in the next run of a
production CA MICS database unit.

If modules on database unit-oriented libraries have been
modified, they must be moved to all applicable database unit
libraries.  If those changes accompany changes at the complex
level, all the database unit changes must be activated at
once.  If they do not accompany such changes, the database
unit modules may be moved one database unit at a time, or all
at once.

After implementation, each database unit in the complex
should be reviewed.  The first DAILY update cycle of all
database units to run after the module moves should be
examined.  Check the SAS logs of each step of each update
output for unexpected messages.  List a few observations from
each database unit's database for every file that could have
possibly been affected by the modification, and examine the
contents of the data elements for correctness.