Subject: | |
From: | |
Reply To: | |
Date: | Wed, 20 Apr 2005 17:56:27 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
ECHO STATUS > STDIN
ECHO EXIT >> STDIN
SETVAR _COUNT 10
!WHILE (NOT BOUND(FTPLASTERR) OR FTPLASTERR<>0) AND
SETVAR(_COUNT,_COUNT-1)>=0
! RUN FTP.ARPA.SYS;INFO="QC6NT";STDIN=STDIN
! SHOWVAR FTP@, CIERROR
! IF FTPLASTERR <> 0 OR CIERROR <> 0
! pause 300
! ENDIF
!endwhile
!IF FTPLASTERR = 0 AND CIERROR = 0
!#FTP worked, so do something useful.
Consider using a netrc file to hide the username and password, and to make
changing the passwords humanly possible. If you need to parse the output of
the ftp session, add ;STDLIST=somefile,NEW to the RUN FTP. Exit is not
necessary in a command file. And, the command file can exist separately, as
its own file.If the job has only one ftp, I use a separate group, and just
use the job name for the command file. Actually, instead of having the job
loop the test, you can have it loop the ftp itself with the same logic as
above.
Greg Stigers
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|