TraceMaster CodeTrack provides CICS Path Analysis so that a developer can know with certainty exactly how often each instruction is, or even is not, executed. It also ensures that storage violations, amongst the nastiest of problems, won't occur when an application targets a memory area.

CICS Path Analysis enables the extent of testing carried out on new or enhanced applications to be determined. CodeTrack monitors every instruction issued by the target program, accumulates a count of the number of times the instruction has been executed and can then produce reports clearly showing the executed code and non-executed code. It is an effective tool in the quality control process of promoting applications to a production environment.

Storage Violation Detection tracks the execution path of CICS applications. When a monitored application is about to execute a store instruction - one whose effect is to update an area of storage - the tool verifies that the targeted memory area is actually owned by the application. If an application attempts to update storage lying outside of its ownership, the update is detected; optionally, the impending violation can cause the application to abend. Other actions are also supported.

TraceMaster CodeTrack's pre-emptive process is more efficient, and safer than trying to detect a storage error after it has occurred, which is a considerable advantage over the standard CICS mechanisms. TraceMaster CodeTrack's low-level interception approach means its monitoring can be applied in almost all circumstances, particularly to transactions which might preclude the use of standard CICS mechanisms. Used in development or system testing environments, TraceMaster CodeTrack is the perfect tool to ensure that none of the code going into the production environment will cause storage violations.

TraceMaster CodeTrack
Key Features

Easy Upkeep
TraceMaster CodeTrack can be readily implemented in any number of CICS systems as there is minimal setup and maintenance required. This benefits when monitoring for errors that occur rarely or under unusual circumstances. It is also a significant advantage when compared to standard CICS functions.

Inclusion and Exclusion Lists
When a program is started in a region where CodeTrack is active, CodeTrack determines whether it should be monitored by referencing the Exclusion and Inclusion lists.

Accurate Reporting
When monitoring CICS application(s) for storage violations, CodeTrack creates a record in the log file that contains the session start and end time, as well as detailed information on each detected storage violation.

When performing code analysis, CodeTrack provides complete analysis reports that can be used for review and stored for auditing purposes. These reports enable testers to determine the level of testing carried out on new or updated applications.

Detects Redundant Code
CodeTrack analysis reports reveal leftover fragments of unused and potentially malicious code that testers need to remove or correct.