Sorry in advance for the product plug. Our syzMPF/z console automation product (and SyzEMAIL/z if you want to get really fancy with the process) will do this and it's a lot cheaper than other automation software.
The script can key off the message ID (and fully parse the message) and can set variables so that you don't start the later job until all three of the datasets you are concerned about are received. Using SyzMPF/z you can either just collect the data and tell the operator (or anyone via email or Cell phone text message), or you could simply have SyzMPF/z start the task the uses those 3 FTP.DATA.** datasets. Personally I would have SyzMPF/z start the job/task because you never know if the operators are going to get around to checking their email or text messages before you send another set of the datasets and you don't want to miss a set's processing because your operators were not paying attention. :) You can also set it up so that if you don't receive all three of them by a certain time of day that you start sending email and/or text messages to people to tell them that they need to look into what happened to whichever one(s) are/is missing. You could also send the people who sent the data a email or text message that you have received that particular part as each one is received, there are lots of options for how to approach the task at hand, and SyzMPF/z has many options to choose from when you are deciding what you want to do. The script would be pretty simple to write, if your SVTM052I messages are one continuous multi-line message then you just collect the words of the message. In the case of your first series, "E2PP.DW801P.WTALZUP.XM.G0520V00" is &W7 (word 7) and "FTP.DATA.ATRAIL.G0458V00" is &W10 (word 10). If they are individual SVTM052I messages then both datasets are &W3 (word 3) of their respective messages. So, while it doesn't do what you want yet by starting the task (because you only have one of the datasets), you could send an email right away and say (to whoever you want) that: &W7 was received at &SYSID as &W10 at &HH:&MM:&SS on &MM/&DD/&YYYY which would be received as: "E2PP.DW801P.WTALZUP.XM.G0520V00 was received at PRODA as FTP.DATA.ATRAIL.G0458V00 at 11:02:23 on 05/06/2018." You can make this (or something similar) the subject and/or the body of the email or text message. At the time this data is being built there are more than 200 variables that are "known" about this process including the nodes, the users, the times, etc. (it's a long list). The email or text message can be any length or contain any information you want and can go to (up to 255 separate destinations/people) although I doubt you need to do that. Where you to start to build JCL you could insert this particular DD into the JCL //ddname1 DD DISP=SHR,DSN=&W10 which builds //ddname1 DD DISP=SHR,DSN=FTP.DATA.ATRAIL.G0458V00 In any case, you could just save the message to either a variable (or series of variables) and then when it's time to use them you just recall the saved variables and either build the task dynamically, or use them as text within the email or text message depending on which one you decided to go with. What this means is that &W10 is only &W10 which it's being processed within that particular script from that original message, you have to save it as a persistent variable if you want to "pass" it to some other task or script (in this case the script for the second and third datasets when they are processed, which might even be this same exact script), so you would just code a SETVAR within the script before you exit that processing. You could call one ATRAIL, one AUDIT and the last one IAS (so that it's meaningful to the dataset name it points to) SETVAR <IAS> &W10 would load the third dataset in your series of messages into the <IAS> variable. You could also just build the JCL up to the point of this dataset and then build it some more when the next one is received and finally when the 3rd dataset is there, just finish the JCL and submit it. To make sure you don't do anything until you have all of the variables, you simply check to see which one(s) you have and which ones you are still waiting for. That way it would not matter what order they arrived, you don't take action (of starting the job/task or email message until you have them all. Once you have all three, you build the job or start the task, clear the existing variables and let it wait for the process to start the next time. Not knowing the sequence involved, you could even set this up so that you could get any number of these and process them all at once at the end of the day if you wanted. The possibilities are as endless as your imagination. There are lots of ways to approach this process, I only covered one of the possibilities, but there are many ways to skin this cat. Script-wise it's really simple, and almost any automation product can probably handle it. The advantage we have is that SyzMPF/z is less than 5% the cost of the automation products from IBM, CA, BMC and most others. We have over 300 sites that use SyzMPF/z. We have other automation products as well, SyzCMD/z (our on-demand automation product) could handle this as well, but it seems to me to fit the console message processing product (SyzMPF/z) much better. Also, we offer a discount to that already low price to IBM-MAIN members. If you decide to look at the product make sure you mention that you are a IBM-MAIN member because they won't ask you if you are. You can read more about it at www.SyzygyInc.com/SyzMPFz.htm Brian Westerman ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
