The idea behind executing something after ftp in build into many data movers. Instead of seperating a single ftp step into several, synchronized somehow, is not the best operational idea.
ITschak On Fri, Apr 4, 2014 at 8:55 AM, Paul Gilmartin <[email protected]> wrote: > On Fri, 4 Apr 2014 08:23:50 +0300, Itschak Mugzach wrote: > > >Have a look at zen ftp control from william data systems that among othrr > >things allow remote execution. It used ftp exit. > > > In my view, using an FTP exit is hardly different from coding your own > TCP/IP > server, except: > > o it uses the existing FTP port number rather than requiring tnat an > idiosyncratic > one be assigned. > > o It can rely on the FTP authentication mechanism > > The z/OS FTP server as shipped; no exit required can submit jobs and > retrieve their > output with the command: > > quote SITE FILETYPE=JES > > (and it doesn't suffer the 80-column limit of TSO SUBMIT.) Also, in > recent releases > it has named pipe (FIFO) capability. > > Likewise, a "submit" command is shipped with Unix System Services, and an > SSH > server can be installed with the ported tools, so I can do the following: > > 505 $ ssh user@mvs "set -x; /bin/submit" < myjcl > user@mvs's password: ******** > + /bin/submit > JOB JOB07768 submitted from stdin > 506 $ > > ... Then I logged on with tn3270 and viewed the output. I didn't need to > use /bin/submit; I could have run any command or script of my devising, > passing it input and reading its output. > > What was the OP looking for? > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
