Coding and Testing

Having an implementation and test plan is the prerequisite to coding the user modification. The implementation and test plans can be followed and reviewed during testing to ensure that testing is adequate.
rm
Having an implementation and test plan is the prerequisite to coding the user modification. The implementation and test plans can be followed and reviewed during testing to ensure that testing is adequate.
Certain coding conventions should be followed in coding user modifications to
MICS
.
MICS
/SAS Coding Conventions
give certain standards for
MICS
modification coding and SAS coding techniques. That section contains performance notes and structure guidelines, too.
Documented the design of the modification. This record is critical for long-term maintenance considerations to have accurate and complete documentation of changes that were coded. Also add 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
MICS
maintenance.
All modification coding must be done in iebupdte format to provide compatibility of your code with standard
MICS
maintenance
. Use the LOCALMOD.CNTL library that is provided in your
MICS Complex
for this purpose.
Test 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
MICS
Test database unit. Applying changes to
MICS
sharedprefix libraries enable the modification immediately, and can cause an interruption in production
MICS
database units or production database integrity problems.