× 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.



On 28-May-2018 23:40 -0500, Booth Martin wrote:
The FTP examples show:

OVRDBF FILE(INPUT) TOFILE(ITSOLIB1/QCLSRC) MBR(FTPCMDS)
OVRDBF FILE(OUTPUT) TOFILE(ITSOLIB1/QCLSRC) MBR(OUT)

Is it possible to create INPUT & OUTPUT in QTEMP with SQL and
eliminate the need for overrides?


Seems unclear what the quoted query has to do with RPG.?.? Nonetheless, I offer:

In my recollection, and empirically with a quick test, the use of INPUT and OUTPUT by a client FTP request from the IBM i, requires the existence of a properly scoped Override as an explicit request to redirect to a _named_ file; i.e. the defaulted or explicit specification of the TOFILE(*FILE) seems insufficient, even with an explicitly named member using MBR(named), although, a To-File specified as the same-named File Being Overridden (FILE), such as for example the naming of TOFILE(*LIBL/INPUT) or TOFILE(OUTPUT), will enable the redirect to occur. The messaging associated with their utilization, from the messages in the message file QTCPMSGF in QTCP, seems to imply that as well:

TCP3C3C
Message: Input read from specified override file.
Cause: The FTP client detected that an override was specified for the input file. The client will accept input from this file.

TCP3C3D
Message: Output redirected to a file.
Cause: The FTP client detected that an override was specified for the output file. The client will write output to this file.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.