× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Here's what I ended up doing:

ovrprtf file(QPQXPRTF) tofile(MYQUERY)
ovrprtf file(MYQUERY) usrdta(&locnbr)

But I'm curious as to why I couldn't do it in a singlele OVRPRTF.
From the online help for OVRPRTF, it seemed as a single override would
have been enough...

"The Override with Printer File (OVRPRTF) command is used to (1)
override (replace) the file named in the program, (2) override
certain parameters of a file that are used by the program, or (3)
override the file named in the program and override certain
parameters of the file processed."

I guess "certain" doesn't include USRDTA. Does anybody know what
"certain" does include?

"If a file named in the program is overridden, the name of that file
is specified in the FILE parameter and the name of the overriding
file (the file processed) is specified in the TOFILE parameter. The
OVRPRTF command also specifies parameters to override values
contained in the file description of the overriding file."

Again, seems to imply that a single OVRPRTF should have been enough,
but it didn't work for me.

Charles


On Wed, Oct 15, 2008 at 5:04 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:
All,

In a CL should this work?

ovrprtf file(QPQXPRTF) tofile(MYQUERY) usrdta(&locnbr)

According to the online, it seems like using the TOFILE along with
other params like USRDTA should. But it doesn't appear to be working.

Thanks!
Charles


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.