run-away-at-firstsign-trouble aka pdc You should keep checking from time to time in order to see whether or not the job has completed. This is a way of avoiding the "no traffic" timeout to which John is referring.
I have evidence of what you should be doing from an exercise I used in an "TCP/IP for MVS" class - you can already see it is somewhat old, around 1995, in fact. The sequence I used was equivalent[1] to the following: site filetype=jes put <jobfile> dir - as many times as is necessary until the output files appear get JOBzzzzz.s - where zzzzz is the sequence number and s is 1 to the number of output files Those repeated "dir" commands should keep your FTP command connection from timing out even if you have a telephone balanced on your shoulder trying to get hold of the tape operator[2]. [1] "Equivalent" because I was using an OS/2 tool FTPPM. [2] This reminds me of an Italian colleague I had who did systems programming work for my group and who sat nearby. I learned a lot of Italian swear words while he was trying to contact the tape operator. <g> Chris Mason ----- Original Message ----- From: "John S. Giltner, Jr." <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Saturday, 23 December, 2006 2:21 AM Subject: Re: ftp job submission > pdc wrote: > > Hi > > I am using FTP (with filetype=jes) to submit JCL on a remote system. > > Is there a timeout that might hit if I were to do something like wait on a > > tape mount? > > > > Cheers > > > > > What are you waiting for? The output from the the job being sent back > after job completions? If so, then yes. There is a session inactivity > timeout that will come into play. > > If your ftp client supports it, you may want to see if the other side > will code the keepalive timer. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
