Trace support tells the Construction Client to generate additional source code, to allow you to step through the execution of the action diagrams for the application after you generate and install the source code. If you intend to test a load module or its components with the Trace option, you must generate Trace support at the time you generate the load module.
Enabling the Trace support flag first automatically enables the Code generation flag. (You cannot have trace code without source code.) Selecting the Code flag once it is set to Y turns trace and code off for the same reason. Select the Code flag first if you do not want Trace support enabled.
If you do not choose this option, you can still test the application, but you cannot view the underlying logic. The default choice is blank (No).
Trace code does not work in all environments, such as IMS or CICS. Trace code is unrecognizable to TP monitors native to operating systems. See the appropriate Build Tool documentation for instructions on invoking an application that contains Trace code.
Downstream Effects: The special code included to allow Trace significantly increases the size of each remote file. If space is a potential problem on either the code generation platform or the target system, consider adding trace selectively rather than globally.
|
Copyright © 2013 CA.
All rights reserved.
|
|