C\TREK™

• C\TREK™ reviews all the parameters that have been specified for the system and resources such as transaction and program definitions. 
• C\TREK™ analyzes the System Initialization Table parameters and identifies those parameters that should be reviewed to improve performance. 
• Reviews the LE options parameters (CEECOPT) and Java definitions and identifies those that require attention

• C\TREK™ improves transaction response times by fine-tuning look-aside hit ratios in both NSR and LSR files. It reviews the string allocation by pool and makes recommendations as to how many should be allocated.
• Checks for NSR files that don’t have the proper BUFNI allocations. It also includes a series of transactions that help identify poor resource utilization such as buffer fragmentation, buffer monopolization by a particular file, or incorrect pool initialization. 
• C\TREK™ is the only tool that identifies how many buffers within an LSR pool are allocated to each file. This makes it easy to identify when a particular file is monopolizing a particular buffer in a pool

• C\TREK™ makes the tuning of VSAM files easy by identifying problem areas that would require a significant amount of system programmer time using other methods, such as traditional monitors. 
• In addition to assisting in the buffer tuning for NSR and LSR files, C\TREK™ provides recommendations on tuning:
• Cluster Definition parameters to ensure that the proper parameters are used, sufficient/correct free space is allocated, the data and index CISZ are optimum, the correct CA size has been defined, the file is not over/under allocated, and identifies files that should be reorganized. 
• Recommendations for the file cluster definition are provided 

• C\TREK™ provides recommendations and information on how the CICS-DB2 connection may be improved by :
•  Providing statistics that help determine the number of threads allocated (protected and   
•  unprotected) Reconciliation of threads assigned to the pool DB2 Entries and Command versus the connection thread limit  SIT MAXOPENTCBS parameter and the reuse of threads  

• C\TREK™ abend handler captures information regarding typical ASRA (program check abends) but more importantly, it captures information about storage violations and short-on-storage (SOS) conditions. 
• With the initial information captured regarding the storage violation, the user can quickly determine the active transactions, the damaged area, and the program and task involved. 
• In some cases, this avoids having to analyze a system dump. In the case of SOS conditions, the abend handler can identify the tasks involved, the amount of storage allocated and used by the task, and the amount of storage requested that caused the SOS condition. 

• It's important to note that several areas within CICS can significantly influence resource usage by CICS TS, including storage below the line. It's worth mentioning that C\TREK™ has an exceptional capability to scrutinize up to 180 potential problems that could negatively affect the performance of your CICS system.

 of customers surveyed said they would be “Extremely Likely” to recommend C\TREK™ to a friend or colleague

 of customers surveyed said they would be “Extremely Likely” to renew their C\TREK™ software license  

of customers surveyed said C\TREK™ is “Extremely Effective” in meeting their CICS performance management requirements