top of page

T24 COB Performance Analysis

Updated: Apr 14

Close of Business (COB) processing is mission-critical. Long processing times set the Bank's opening times for the following day at Risk and would result in significant reputation and business issues.


Several tools, such as our T24 Transact COB Monitor, can observe every aspect of this crucial processing. Classic COB processing consists of hundreds of jobs and service executions. Without an observability and analysis product, it's impossible to find the root cause of performance issues.


We also use Tools such as Job Times (JT) and Report Times (RT) Analyzers to get information about the time taken by any job or report routine during the previous COB. Once we get the timings, we can filter out the long-running jobs and reports. We can use this data for COB tuning.

 

JT – Job Time Analyzer

 

We use JT to fetch the details about the time the Jobs took in T24, usually in the COB.

 

Execute this command to start JT: tRun JT.ANALYZE

 

The result contains the following fields and their data.

  • BATCH.STAGE

  • BATCH JOB.NAME        

  • BATCH.DATE  

  • JOB POSITION                

  • START.TIME      

  • END.TIME          

  • ELAPSED.TIME               

  • PROCESSED RECS    

  • THROUGHPUT               

  • COMPLETED RECS

  • SELECTION.TIME         

  • BULK.NO           

  • TXN.MGMT      

  • WRITE.CACHE                

  • LOCK.COLLISION       

  • TOTAL WRITE 

  • DET PROCESSED         

  • DET COMPLETED

  • DET THROUGHPUT    

  • DET BULK.NUMBER  

  • DET SELECT    

  • TYPE OF SELECT          

  • DET SELECT TIME

 

 

 RT – Report time  Analyzer

 

The RT Analyser is used to fetch the details about the time the REPORTS took in T24, usually in the COB.


Execute this command to start JT: tRun RT.ANALYZE


The result contains the following fields and their data.

  • BATCH

  • COMPANY TYPE            

  • REPORT.NAME               

  • ENQ.USER        

  • REPORT.PRINTER        

  • START.TIME      

  • END.TIME          

  • ELAPSED.TIME

 

The above reports only provide the previous COB data. Alternatively, we can fetch the details using JOB.TIMES and REPORT.TIMES for comparison with the last few days' data. These contain the output data for at least the previous ten runs. The disadvantage of these is that they will contain limited field data in the output.

 

 

JOB.TIMES

 

Similar to JT.ANALYSE with the following limited output data. We can directly launch this in the browser.

 

  • Id            

  • Job         

  • Program              

  • Batch date       

  • Start time

 

REPORT.TIMES


Similar to RT.ANALYSE with the following limited output data. We can directly launch this in the browser.

  • Id            

  • Batch date       

  • Start time          

  • End time            

  • Elapsed time


Do you need COB Performance Troubleshooting support? Contact us today, we are happy to reduce your COB duration.


Keep up the great work! Happy Performance Engineering!




Comments


bottom of page