R
Rick Terrell
Guest
If you’re running r-code, -NL has no effect. It only applies during compilation. No need for it in a production environment running r-code. Rick Terrell Principle Consultant, Professional Services Progress Sent from my iPhone On Oct 5, 2018, at 3:40 AM, frank.meulblok wrote: Update from Progress Community frank.meulblok Kinda doubt statement caching is is going to show anything meaningful here. Unless the client didn't have any database (so no record fetches or buffer releases etc. at all) after the lock was obtained (for the middle row) or downgraded (for the other 2) it won't tell you where in the code the locking status changes. AFAIK Individual locks aren't timestamped either, so promon also won't tell you how old a lock is. (and neither will the VSTs). Still, these locks are held within an active transaction.(trans state is FWD, not DEAD/NONE) so it looks like these locks are held because of transaction scoping issue. Only reliable way to see how your transactions are scoped at runtime is to flip on the 4GLTrans logging on the clients. But word of caution: Logs can get large. Especially if you need to generate them in production. View online You received this notification because you subscribed to the forum. To unsubscribe from only this thread, go here . Flag this post as spam/abuse.
Continue reading...
Continue reading...