P/TLF read count from IRB24TLR is excessive, Can we configure IRB24TLR read call intervals.

Highlighted
05 Base Camper

P/TLF read count from IRB24TLR is excessive, Can we configure IRB24TLR read call intervals.

Dear Team,

 

We have observed that IRB24TLR is having high read rate which causes system performance issue.

Please find below details for the read write stats gathered from measure proocess.

 

Can we configure any iterval time for IRB24TLR, so that we can set one period after which it should read P/TLF log file.

 

For eg. Now IRB24TLR is reading P/TLF file in each seconds, I want it to be read P/TLF file after 3 seconds or any no. of seconds. By this configuration I just want to reduce no. of read counts by IRB24TLR on P/TLF file.

 

VOLUME

SUBVOL

FILENAME

OPENER-PROGRAM-FILENAME

#

FILE READS

FILE WRITES

UPDATES REPLIES

DELETES WRITEREADS

FILE CALLS

READ RATE

WRITE RATE

$DATA02

UNG2ATLF

TL200130

$DATA20 UNG2OBJ AUTH

27

0

11926

0

0

11926

0

19.88

     

$OPSMON PRGN    IRB24TLR

2

55663

0

0

0

55663

92.79

0

 

Thanks,

tushR

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: P/TLF read count from IRB24TLR is excessive, Can we configure IRB24TLR read call intervals.

Hi @TushR 

If we can get some detail on the behavior.. such as looking at why the activity is occurring and causing performance issues that would be a good start as Prognosis should NEVER cause performance issues if following best practices. The B24TLR

 

The most common issue is users directly pointing the IRGUI to the Nonstop vs. utilizing a managing node (or even via a managing node) and then having an unfiltered IRTSVCOL (TRANDET) view open or leaving it open. This record should ALWAYS have a filter AND a TOP clause.   

 

Other common causes I have seen are home grown ODBC exports of TRANDET, and misconfigured Database collections.

 

If you create a display on Prognosis Views you can create a filter to quickly observe this..   I have a display I use when tracking things like this down .. that I cannot attach here but if you message me I can email you it.   If you use this and see anything accessing TRANDET record with a row count of greater than 250 I would track that down immeidately. Some customers have even created threaholds on the PVIEWs record to even look for this.

 

On your root question.. there is some parameters you can control the way it reads the TLF/PTLF/JOURNAL off of disk that are described here in our help under the reader's custom parameters section. I would however proceed very carefully on using them.

 

 


If my answer helped you today, please be sure to mark the resolved button to assist others.

Christopher R Souser - Solution Architect – MSci. PA, CISSP, ITIL.

View solution in original post

Tags (2)
1 REPLY 1
Highlighted

Re: P/TLF read count from IRB24TLR is excessive, Can we configure IRB24TLR read call intervals.

Hi @TushR 

If we can get some detail on the behavior.. such as looking at why the activity is occurring and causing performance issues that would be a good start as Prognosis should NEVER cause performance issues if following best practices. The B24TLR

 

The most common issue is users directly pointing the IRGUI to the Nonstop vs. utilizing a managing node (or even via a managing node) and then having an unfiltered IRTSVCOL (TRANDET) view open or leaving it open. This record should ALWAYS have a filter AND a TOP clause.   

 

Other common causes I have seen are home grown ODBC exports of TRANDET, and misconfigured Database collections.

 

If you create a display on Prognosis Views you can create a filter to quickly observe this..   I have a display I use when tracking things like this down .. that I cannot attach here but if you message me I can email you it.   If you use this and see anything accessing TRANDET record with a row count of greater than 250 I would track that down immeidately. Some customers have even created threaholds on the PVIEWs record to even look for this.

 

On your root question.. there is some parameters you can control the way it reads the TLF/PTLF/JOURNAL off of disk that are described here in our help under the reader's custom parameters section. I would however proceed very carefully on using them.

 

 


If my answer helped you today, please be sure to mark the resolved button to assist others.

Christopher R Souser - Solution Architect – MSci. PA, CISSP, ITIL.

View solution in original post

Tags (2)
Webinar: Top Ten Predictions in Retail Payments for 2020

Join IR, Celent and your peers as we discuss the top ten predictions for retail payments in 2020 and how evolving your payment solutions will help you stay ahead of your customers’ expectations ...

Join Webinar
Top Liked Members