If the exit serializes access to the N/T pair then there should be no lost data.
________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Colin Paice <[email protected]> Sent: Wednesday, June 28, 2023 10:41 AM To: [email protected] Subject: Re: Counting EXIT invocations Having a WTO depends on how many exit calls there are per second. 100 a second might cause a problem. Depending on where your exit runs, and what state it is in, a system level name token pair might be a good compromise. On first use - allocate a name token, set use count = 0; do a STCK and add 10 minutes - and store it in name token. on every other call - increment counter - If stck(now) > the stored STCK - calculate the time delta - and WTO out # seconds and count - store now + 10 minutes in the name token. The time between WTOs may be > 10 minutes but it gives you a flavour of the count. You might lose the odd entry if two TSBs are trying to update concurrently. Or do the WTO every 1000 calls. On Wed, 28 Jun 2023 at 15:10, Jousma, David < [email protected]> wrote: > Best option would be to have the exit issue a WTO, and then scan operlog > for that. > > Dave Jousma > Vice President | Director, Technology Engineering > > > > > > From: IBM Mainframe Discussion List <[email protected]> on behalf > of [email protected] <[email protected] > > > Date: Wednesday, June 28, 2023 at 9:21 AM > To: [email protected] <[email protected]> > Subject: Counting EXIT invocations > Hi! We have recently implemented a RACF exit. Is there a way to know how > many times this EXIT was executed (on a given period of time)? Thanks in > advance for your help, Juan Mautalen > ---------------------------------------------------------------------- > > > Hi! > > We have recently implemented a RACF exit. Is there a way to know how many > times this EXIT was executed (on a given period of time)? > > Thanks in advance for your help, > > Juan Mautalen > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > This e-mail transmission contains information that is confidential and may > be privileged. It is intended only for the addressee(s) named above. If > you receive this e-mail in error, please do not read, copy or disseminate > it in any manner. If you are not the intended recipient, any disclosure, > copying, distribution or use of the contents of this information is > prohibited. Please reply to the message immediately by informing the sender > that the message was misdirected. After replying, please erase it from your > computer system. Your assistance in correcting this error is appreciated. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
