|
Jerry:
Have an actual <userid> <password> on the line. Just replaced them not to
give out the real userid and pw.
Thomas
On Wed, Feb 18, 2015 at 10:51 AM, Jerome Draper <midrangel@xxxxxxxxxxxxx>
wrote:
A source PF is fine and building it with RPG is fine. I suggest youdo
change the record length to 128. 80 is short but is fine for what you
show below.
I believe your problem is the key word USER. Do not use that. Just put
the actual <userid> <passw> on that line.
Jerry
Monty:
Another person says the file does not have to be a source PF. But if I
10.41.84.20make it a source PF will I be able to put records in a source PF from a=========================================================================
RPG
program.
On Wed, Feb 18, 2015 at 10:26 AM, Monty G. James
<monty.james@xxxxxxxxxxxxxx
wrote:
The input file need to be a source PF, 3 fileds the third field(SRCDTA
CHAR 80) is where your ftp commands go.
Use CRTSRCPF to create your input file and add the appropriate FTP
commands to it.
subject: BATCH FTP question
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
=============================================================================using port 21.
220 Microsoft FTP
Service
Enter login ID (tburrows):
RPG
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
http://cp.mcafee.com/d/FZsSd20w76Qm4S4NPybW9KVJd5ZN5ZZYSCy-UyUYedFELK8LLK6QQjhOCyOO-rlH2prx7lvE2yti10IvkwgbsKr9R842NZi10JOVJwxF1zS7-LNEVvjsWZOWqtXYyYe79YJteOaaJXFYG7DR8OJMddEK6QhNK_8K6zBV55BeXNKVI06vaAWsH92eM8_O-2qKMM-l9OwXn5p8hS17OVVJmi4twhYKun8lrxrW01lH2prx7lvEsjGg85zWA21rBMkH92eM8_OVJ4sye76NId3wm80M93hsaCy0eAh-AM3d40pGuq84m03d40rizvCy1dxUSOUrtVyrrWaMsV4vprogram 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
------------------------------
Subject: Digest Footer
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://cp.mcafee.com/d/FZsS82gAcy1J5xdxcsUy-yrKrjhvshvvvdFELK8Kf3zqqbXybXXxJd4QsFEIILCRqMCmUhRnW0EDkwgb7R842TbCOti10IvkwgbsKro8qgoZx_HYqenQTeLsKCDu_8L3xOvbnjIyyHuWvaxVZicHs3jq8USyedTV5MQsL8EIFTudTdw0ZzoD8P_aOgzI2fYLyIA8X0zVsYSH92eM8-nfbAaJMJZ00GRxcJMzGLQe9R842NZi10JOUalAx7o4vVsSyeh73zoS6xMb40o4xEK5jh07i8_io1Cy0cRfd42b01Cy0dFhLPh0CMYrpsdzAsugaxKviYYor email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
list.--
------------------------------
End of MIDRANGE-L Digest, Vol 14, Issue 248
*******************************************
________________________________
This email message, including any attachment(s) is for the sole use of
the
intended recipient(s) and may contain confidential information. Any
unauthorized review, use, disclosure or distribution is strictly
prohibited. If you are not the intended recipient, please immediately
contact the sender by email.
--
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.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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 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.