Previous Topic: Test NCL Procedures

Next Topic: Debug an NCL Procedure

Test in Production and Testing Environments

While such facilities are ideal in a production environment they can interfere with testing. For example, you may have completed and tested a procedure and made certain corrections and want to run a second test. Although you have saved the corrected procedure in its library, you may notice the original errors are still occurring. This is most likely to be caused by NCL having retained the original procedure in storage and reused it when the second test was run. To overcome this apparent interference with your testing, use the NCLTEST command to signal to the system that you are in fact operating in a test mode and do not want your procedures retained or shared and that the latest copy is always to be loaded from the library. For more information about the NCLTEST command, see the Online Help.