3. Maintenance Policies and Procedures › 3.2 User Maintenance Procedures › 3.2.2 User Change Control Procedure › 3.2.2.4 Coding and Testing

3.2.2.4 Coding and Testing

Having an implementation and test plan is prerequisite to
coding the user modification.  The implementation and test
plans should be followed and reviewed during testing to
ensure that testing is adequate.

Certain coding conventions should be followed in coding user
modifications to CA MICS. Besides the guidelines presented in
each section of this manual, chapter 5 of this manual gives
certain standards for CA MICS modification coding and SAS
coding techniques.  That chapter contains performance notes
and structure guidelines, as well.

It is important to have documented the design of the
modification.  It is absolutely critical for long-term
maintenance considerations to have accurate and complete
documentation of changes that were actually coded.  This
comes from entries in the CA MICS System Administrator Guide,
and from comments in the code provided.

The normal tendency in actually entering code is to use
a standard TSO-compatible editor.  Such direct changes are
not compatible with the application of standard CA MICS
maintenance.  ALL MODIFICATION CODING MUST BE DONE IN
IEBUPDTE FORMAT TO PROVIDE COMPATIBILITY OF YOUR CODE
WITH STANDARD CA MICS MAINTENANCE. Use the LOCALMOD.CNTL
library provided in your CA MICS complex for this purpose.

Testing should be done on the Test database unit.  This
database unit type provides all the facilities necessary to
perform unit and parallel testing, interference testing, and
separation of the tested logic from production libraries.

Coding should be applied to the libraries in the CA MICS Test
database unit.  Applying changes to CA MICS sharedprefix
libraries will enable the modification immediately, and may
cause an interruption in production CA MICS database units
or production database integrity problems.