|
For the way you have it, yes, it will have to be manual, FTP is FTP, you cannot mix code. Without knowing the whole scope, does it matter what the file name will be? We do some "creative" things here to FTP files; basically we find out the file name, have either a C/L or RPGILE change our source script file, then run it. We also receive FTP's here with varied file names, but then too just read through to search for new ones to process - thus the programs do not care what the file names are. I am not sure if you can get away with it, but just some food for thought. HTH Mark -----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]On Behalf Of Mark Allen Sent: Thursday, February 21, 2002 11:19 AM To: midrange-l@midrange.com Subject: BATCH ftp ? Having a problem with getting this to do what I want. What I need it to do is stay in the FTP session after the dir in the sctipt file (listed below) because we do not know what the file name will be. I want the operator to manually enter the appropriate get command but the ftp session does an "implicit" quit after the last line of the FTP script and the runqry starts. Can I do wat I want or is the "whole" thing going to have to be manual. FTP script file Columns . . . : 1 71 Browse WTCCUSTOM/QFTPSCRIPT SEU==> ADSSCRIPT FMT ** ...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 *************** Beginning of data ************************************* 0001.00 user password 0002.00 lcd wtcfiles 0003.00 dir ****************** End of data **************************************** CL program ..+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 OVRDBF FILE(INPUT) TOFILE(*LIBL/QFTPSCRIPT) + MBR(ADSSCRIPT) OVRDBF FILE(OUTPUT) TOFILE(*LIBL/QFTPSCRIPT) + MBR(ADSLOG) FTP RMTSYS('207.144.248.6') RUNQRY QRYFILE((WTCFILES/ADS360RPT)) OUTTYPE(*PRINTER) DSPPFM FILE(*LIBL/QFTPSCRIPT) MBR(ADSLOG) Mark Allen I.S. Manager Wilkes Telephone & Electric A Dycom Company Phone: (706) 678-9565 Email: allenmark@nu-z.net http://www.nu-z.net _______________________________________________ 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.
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.