John (Bruce), I've only been glancing over this topic as the posts flew by so please excuse me if I've missed a vital consideration.
Now that Bruce has suggested a separate job, I remembered the days I put together some very crude automation where each started task procedure had a job step which fed a "card deck" to the "internal reader", INTRDR, in order to initiate the next activity - or something like that. (In order to make sense of the technique, you need to know that a job step which delayed execution of the following step, a program wrapped around the appropriate macro, is needed.) Isn't the "internal reader" trick the simpler way to implement this excellent idea? I dare say the COND code could be used in order to run the step with IEBGENER to the "internal reader" only when the file was known successfully to have been created. Chris Mason ----- Original Message ----- From: "Bruce Hewson" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <IBM-MAIN@BAMA.UA.EDU> Sent: Monday, 06 March, 2006 4:25 AM Subject: Re: Unusual FTP request. > Hello John, > > late response due to weekend. :-) > > My understanding is that application staff dont want to be called for FTP > problem. And that application staff are getting called due to jobname > prefix. > > You have indicated that existing jobs use a STEP to trigger the FTP > request, and that you are using CA-7. > > My simplistic response would be to solve the problem by turning each FTP > STEP into a new job. Use CA-7 to handle the COND code checking currently > being done in the JCL STEP. Each "new" FTP job would have a new FTP team > specific jobname. The applications staff can convert the FTP step into a > FTP job reasonably quickly. > > Coordination between application / scheduler / FTP teams would be required > for FTP jobname allocation. > > Result is that existing step jcl can be used, minimising testing and > implementation times. > > no need for any other product, external or in-house. :-D > > Regards > Bruce Hewson > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- 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
