|
I believe that you can put the following over ride in your CL and then the FTP process will log to the screen. Otherwise it logs to a file. (In my example, ISY2 is the library and QFTP is the file. The file holds two members. You may want to look at the members btw to see what's already in them.) /* OVRDBF FILE(OUTPUT) TOFILE(ISY2/QFTP) MBR(FTPLOG) + By commenting this command the FTP process prints the + log file to the screen. Uncommenting the command will + print and save the log in ISY2/QFTP/FTPLOG */ In <3.0.5.32.19980614230518.0096e100@goldengate.net>, on 06/14/98 at 11:05 PM, Vernon Hamberg <hambergv@goldengate.net> said: >Andre >At 12:12 PM 5/31/1998 +0200, you wrote: >> >>We have a lot of ftp initiated by the as/400. They work very well and we >use the >> log to check the good completion. >> >>But we want now to start FTP from a mainframe to the as/400. It works >well, but >> the programmers would like to have some messages on the as/400 >showing the >> status of the transfer. >> >>I suppose the only way is to have an exit on FTP which monitors the transfer. >> >>Does anyone have an example, or a model of an FTP exit ? (we have V4R1) >Is the 400 the server or the client? The following assumes the 400 is the >client. >As with all ftp implementations, there are messages returned to the >client system for each subcommand that executes on the server. These >messages go to STDOUT, or are redirected OVRDBF or OVRPRTF in AS/400 >terms. >There are no messages on the 400 during the process, unless you count the >byte count that appears at the bottom of the screen while a get/put is in >effect. >Come to think of it, though, you could use the 'syscmd' subcommand to >execute a 400 command. This could do anything allowed on a command line >or from a program, I think. It could ooh, this is getting good! call a >program that'd look at the output file up to that point (barring lock >conflicts) and check for return codes. Then it could send messages as >needed. D'ya think? >These things would execute from an ftp script. See the TCP/IP Config & >Ref for details. >HTH >Vernon Hamberg >Systems Software Programmer >Old Republic National Title Insurance Company >400 Second Avenue South >Minneapolis, MN 55401-2499 >(612) 371-1111 x480 >+--- >| This is the Midrange System Mailing List! >| To submit a new message, send your mail to MIDRANGE-L@midrange.com. >| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. >| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. >| Questions should be directed to the list owner/operator: david@midrange.com >+--- -- ----------------------------------------------------------- boothm@ibm.net Booth Martin ----------------------------------------------------------- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.