This is a common theme in our distribution process. Our job scheduler does all that for us. We use ESP. Our collective CA-7 memories had a half decade of rust, but we think it ought to be ale to do what you need.
HTH and good luck -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Friday, March 03, 2006 8:52 AM To: [email protected] Subject: Unusual FTP request. What the programmer would like would be for the production job to simply create the dataset which is to be ftp'ed. All datasets which are to be ftp'ed are created with a specific, unique, high level qualifier. Whenever a dataset with this high level qualifier is created, "something" triggers a process (job, started task, other) which is passed the name of the dataset just created. This process then does some sort of "look up" on the name of the dataset just created and generates the appropriate ftp commands, which are "somehow" passed to an "ftp processor". If the "ftp processor" has a problem, then the "ftp team" would be alerted that an ftp failed. The "ftp team" would be able to look at the ftp output and hopefully determine what failed, why, and then fix it. This would releave the normal programmers from being called. These people: (1) don't have the authority on the ftp server to see what the problem might be, if the problem is there; (2) don't know how to determine if the problem is on the server or the z/OS side; (3) don't want to be responsible for ftp processing at all. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology ---------------------------------------------------------------------- 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
