FTP logging

[ASingh]

Hello. I am setting up an FTP process and want to know if there is a way to generate one log file from the FTP process. In other words I need a log that has both the input and output streams together as one log. Is there a way to do that? Thanks for your help.

[tomholden]

Re: FTP logging

by input and output stream do you mean the sub commands and the responses? if so they are in the FTP log. it's a simple process:

OvrDBF Input ToFile(&ScrLib/&ScrFile) Mbr(&Script) +
       Share(*Yes) OvrScope(*CallLvl)               
OvrDBF Output ToFile(THLIB/QFTPLOG) Mbr(&LogMbr) +  
       OvrScope(*CallLvl) Share(*Yes)               
                                                    
FTP &Address                                        
DltOvr *All

the output from the FTP would be in the THLIB/QFTPLOG member.

[dhuesman]

Re: FTP logging

If you want the input and output logs together, I believe you'll simply need to copy the INPUT and OUTPUT from the OVRDBF suggestion below into whatever type of file you need.

One caution is the INPUT may (probably does) include the FTP site, user and password.

Things like this may be frowned upon.

good luck

[tomholden]

Re: FTP logging

If you want the input and output logs together, I believe you'll simply need to copy the INPUT and OUTPUT from the OVRDBF suggestion below into whatever type of file you need.

One caution is the INPUT may (probably does) include the FTP site, user and password.

Things like this may be frowned upon.

good luck

i haven't tried it but to me it would suck
for example:
FTP Script:

FTPUSER FTPUSER                  
quo rcmd SNDUSRMSG MSG('HI ME!!!') TOUSR(ME)
quit

FTP log added to the same member used as the script:

FTPUSER FTPUSER                  
quo rcmd SNDUSRMSG MSG('HI ME!!!') TOUSR(ME)
quit
Output redirected to a file.             
Input read from specified override file. 
Connecting to host
220-QTCP at NOTES1.                                    
220 Connection will close if idle more than 5 minutes. 
Enter login ID (xupd42ay):  
331 Enter password.         
230 FTPUSER logged on.      
250  Now using naming format "1".          
257  "/home/FTPUSER" is current directory. 
Enter an FTP subcommand.                   
quo rcmd SNDUSRMSG MSG('HI ME!!!') TOUSR(ME)
Enter an FTP subcommand.         
> quit                           
221 QUIT subcommand received.

what's so difficult reading just the log??

Output redirected to a file.             
Input read from specified override file. 
Connecting to host
220-QTCP at NOTES1.                                    
220 Connection will close if idle more than 5 minutes. 
Enter login ID (xupd42ay):  
331 Enter password.         
230 FTPUSER logged on.      
250  Now using naming format "1".          
257  "/home/FTPUSER" is current directory. 
Enter an FTP subcommand.                   
quo rcmd SNDUSRMSG MSG('HI ME!!!') TOUSR(ME)
Enter an FTP subcommand.         
> quit                           
221 QUIT subcommand received.

same info less garbage...but that's just me...heck i'm not even sure if you can use the same member for both input and output i ran a little test and it gives me errors

Get option list not valid for member FTPDBS.
Pointer not set for location referenced.

so unless it's a PTF issue (which i doubt) you'd have to CPYF the script into the log file

[dhuesman]

Re: FTP logging

another techinal term from the great state of Tn.

[tomholden]

Re: FTP logging

hey i may live in TN but i volunteer for nothing!!!