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...".
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Justin
Taylor
Sent: Tuesday, March 31, 2020 9:59 AM
To: MIDRANGE-L (midrange-l@xxxxxxxxxxxxxxxxxx)
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: QCMDEXC & OVRPRTF anomaly
I still haven't found an answer on this. I'm thinking about putting a check
to determine if the override is in place. Is there an API or IBMi Service I
can use to retrieve active overrides? DSPOVR doesn't offer an *OUTFILE
option (and I'm loathe to return to the dark ages of parsing spooled files).
Thanks
From: Justin Taylor
Sent: Tuesday, March 10, 2020 11:08 AM
To: MIDRANGE-L (midrange-l@xxxxxxxxxxxxxxxxxx)
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: QCMDEXC & OVRPRTF anomaly
We have a program that uses the QCMDEXC API to run an OVRPRTF OVRSCOPE(*JOB)
command. It has been in production for years. It works virtually all the
time. We have a new employee and for her alone it "fails" about 5% of the
time. I put the word fails in quotes because the QCMDEXC completes
successfully, but the override doesn't actually happen.
We have joblogs and DSPOVR print-outs for when it works and when it doesn't,
and they're identical. We have been unable to identify any pattern for when
it doesn't work, and it cannot be replicated on demand.
Does anyone have any suggestions of what to check next?
TIA
--
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
