Re: Monitor on OVRPRTF

On 3/19/2015 12:14 PM, Gary Thompson wrote:

I'm curious, anyone bother to monitor the OVRPRTF command ?

OVRPRTF just(!) sets some flags in the job that take effect at the
moment the FILE() is opened. Try this:

ovrprtf qpdsplib tofile(nope)
dsplib qgpl output(*print)
File NOPE in library *LIBL not found or inline data file missing.
Error occurred while opening file QPDSPLIB.

That said, if your program /builds/ an OVRPRTF and puts improper
contents into a parameter, the validity checked is going to punch the
eject button at the moment the OVRPRTF executes. That should throw CPF0001.