Special Considerations for Xpediter/TSO Settings for Topaz for Total Test Data Collection
Although Xpediter/TSO is primarily a debugger, it also supports other product functionality like Code Coverage, Visualization and Topaz for Total Test. While Xpediter/TSO has evolved to include many settings designed to accommodate “unorthodox” environments, be aware that some of these settings can cause a loss of Xpediter functionality.
- Choosing one breakpoint strategy (SET LETRAP, SVC breakpointing, TRAP breakpointing,…) over another may affect the performance of a collection run, but should not affect the integrity of the data being collected.
- Issuing SET CBLTRAP OFF will interfere with the collection of COBOL native (QSAM/VSAM) I/O data.
- Issuing SET STATIC, SET DYNTRAP, SET EXCLUDE (and site Runtime parameters CT2BLBOX and CT2VCONS) may adversely affect the collection of Db2 and/or IMS data when the target is the object of Topaz for Total Test data collection. As opposed to using STATIC or DYNTRAP to universally eliminate intercepts for all modules, consider using EXCLUDE to target problematic modules when they are other than the object of the Topaz for Total Test collection.
- Using SET DATETIME OFF when the user cannot guarantee that all DDIO members perfectly match the associated Load Modules is not advisable.
Related Topics
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*