Re: QCMDEXC & OVRPRTF anomaly

[Peter Dow <petercdow@xxxxxxxxx>]

Hi Justin,

If there is more than one OVRPRTF within the job, the overrides are 
cumulative, unless you use the SECURE(*YES) parameter.

No idea if that's your user's problem, but thought I'd mention it.

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx>

/
On 3/31/2020 10:21 AM, Justin Taylor wrote:
> 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...".