How about the following: 1. Job A step 1 creates a file to transfer.
2. Job A step 2 updates a log identifying file to transfer. The log should contain info about where to transfer file, status of transfer, who to contact should file needs to be recreated, and other info as needed. 3. Job B reads log and transfer files based on status. Job B can update status as needed. Job B can transfer files itself or trigger appropriate number of Job Cs. CA7 can trigger Job B after Job A or on some other timed schedule. If the log show no files to transfer then no action is taken and Job B ends. 4. If external customer calls programmer or FTP staff can check the log and based on status and date transferred inform the customer that the file was transferred or change the status to be triggered by the next schedule Job B. ---------------------------------------------------------------------- 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
