Re: Restricting RUNQRY interactive

I would have thought so, too. But if you take the
*INTERACT mode off the command and take option 9, you
get the message that this option is disallowed because
of restrictions on the command (QRY2294). If you try
RUNQRY on a command line you get a different message
(CPD0031) but the same idea - not allowed in this
environment.

So WRKQRY opt 9 maybe checks this setting, then calls
the CPP, rather than executing the command. Anyone know
this?
> > We have added a validity checker to RUNQRY. When RUNQRY
> > is run from a command line, the VCP gets called. When
> > you take option 9 from WRKQRY, it does NOT get called.
> > Anyone know why?
>
> I assume that an option 9 from WRKQRY does not run the RUNQRY command.
> It probably calls the CPP directly.
>
> > BTW, option 8 of WRKQRY (Run in batch) does call it.
>
> This option probably does a SBMJOB of the RUNQRY command,
>
> --
> Jeff Crosby
> Dilgard Frozen Foods, Inc.
> P.O. Box 13369
> Ft. Wayne, IN 46868-3369
> 260-422-7531
>
> The opinions expressed are my own and not necessarily
> the opinion of my company.  Unless I say so.
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>