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



Hi again

When working with FTP you are in the IFS world - and that file system doesn't know about the multiple-object content of PFs created from source.

Both source PFs and files created with record length seem to be usable in this kind of scenario, although no guarantee on the flat files - they seem usually to work.

The same goes for the files used for the overrides of stdin (input) and stdout (output) - you COULD actually get output into a SPLF by using OVRDBF to QPRINT - heh!

HTH
Vern

On 2/18/2015 10:42 AM, Thomas Burrows wrote:
Michael:

Nothing is showing up in my SAW_FTP_O file.

Here is the DDS for SAW_FTP_F file

A R PRG_REC
A*
A LINE_A 80A COLHDG('FTP COMMANDS')

Monty James says the input file needs to be a source PF

Thomas

On Wed, Feb 18, 2015 at 10:28 AM, Michael Ryan <michaelrtr@xxxxxxxxx> wrote:

Have you run the same commands from the FTP command line? What shows up in
SAW_FTP_O?

On Wed, Feb 18, 2015 at 11:15 AM, Thomas Burrows <
thomas.burrows.1957@xxxxxxxxx> wrote:

Trying to do a BATCH FTP and something is not working.


CLRPFM FILE(SAW_FTP_O)

CALL PGM(SAW_FTP)

OVRDBF FILE(INPUT) TOFILE(SAW_FTP_F) MBR(SAW_FTP_F)

OVRDBF FILE(OUTPUT) TOFILE(SAW_FTP_O) MBR(SAW_FTP_O)

FTP RMTSYS(THOFS001)

DLTOVR FILE(*ALL)

My input file SAW_FTP_F has this in it.



Running the above CL commands in DEBUG all I get is

=========================================================================

File Transfer
Protocol


Previous FTP subcommands and
messages:
Connecting to host THOFS001.ACPRODUCTSINC.COM at address 10.41.84.20
using port 21.
220 Microsoft FTP
Service




























Enter login ID (tburrows):



=============================================================================
Appears that my file of FTP commands "SAW_FTP_F


REIN
USER userid password
NAMEFMT 1
ASCII
put qtemp/BIRC_0216O.saw_f_prg /omga/BIRC_0216.prg
put qtemp/MAPL_0216O.saw_f_prg /omga/MAPL_0216.prg
put qtemp/OAK__0216O.saw_f_prg /omga/OAK__0216.prg
put qtemp/WHIT_0216O.saw_f_prg /omga/WHIT_0216.prg
put qtemp/ALDE_0219O.saw_f_prg /omga/ALDE_0219.prg
put qtemp/BIRC_0219O.saw_f_prg /omga/BIRC_0219.prg
put qtemp/CHER_0219O.saw_f_prg /omga/CHER_0219.prg
put qtemp/MAPL_0219O.saw_f_prg /omga/MAPL_0219.prg
put qtemp/OAK__0219O.saw_f_prg /omga/OAK__0219.prg
put qtemp/WHIT_0219O.saw_f_prg /omga/WHIT_0219.prg
QUIT

is not being picked up.

If it matters the FTP commands in SAW_FTP_F are being generated by a RPG
program I wrote. Thus the SAW_FTP_F is not a TEXT file. But a straight PF
that has one field name that is an alpha 80.

Could this be a problem.

Thomas in
Dallas
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




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.