Sorry, I apparently misunderstood where you were in the process. Since it
works sometimes and not others, I thought you were still analyzing "does the
override exist for that user at the time the file is opened" and "did
something delete the override before the program was called". My
suggestions seemed like the easiest ways to find that out. The first tells
you if it exists at all and if it does, what it looks like. The second
tells you if it was successfully overridden but something subsequently
deleted the override before the program was called. Also, following up on
Peter Dow's comment, these suggestions will also tell you if something
overrode the override.
Best of luck. Intermittent things are the worst!!!
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Justin
Taylor
Sent: Tuesday, March 31, 2020 1:22 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: QCMDEXC & OVRPRTF anomaly
The question is to programmatically process the current overrides. I'm
trying to avoid having to parse the DSPOVR spooled file.
Thanks
-----Original Message-----
From: smith5646midrange@xxxxxxxxx [mailto:smith5646midrange@xxxxxxxxx]
Sent: Tuesday, March 31, 2020 9:34 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: QCMDEXC & OVRPRTF anomaly
If you are just trying to find out if the override is still in place at the
time the program is called, can you add a DSPOVR *PRINT right before the
printfile is opened? Since it is only one user, you could condition it with
"if user = 'xxx'..." so it doesn't do the DSPOVR for everyone.
The other thing that I have seen done for weird stuff like this is to put a
library at the very top of the syslibl for her only that contains a custom
version of OVRPRTF and DLTOVR that logs when they are being executed.
Logging could be as simple as a dump of the call stack. Typically this ends
up being some rarely executed code triggered by "If Tuesday and raining in
Arizona then...".
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
