Hi Hennie,
Sorry - I don't think I explained correctly. This is the message we want to trap:
09.30.50 STC26813 SVTM052I COPY001 COPY SANFD002( 8,007) PNODE=OS16 989
989 SVTM052I FROM XFR.PRD.PAR.SAV.FACT.R2.D180204
989 SVTM052I TO VPPN.B8.SANFD002.FPS.PAYMENTS.PS.G0001V00
989 SVTM052I COMPLETED 00000000/SCPA000I
to test my new rule, I wrote the following in a little OpsEXEC:
msgid = "SVTM052I"
wto.1 = "COPY001 COPY SANFD002(8,007) PNODE=JHB-MWAY-PRD2 "
wto.2 = " FROM FROM.DATASET "
wto.3 = " TO TO.DATASET "
wto.4 = " COMPLETED 00000000/SCPA000I "
wto.0 = 4
Address WTO "Msgid("||msgid||") Textvar(wto.) Route(1)"
except that this produces:
13.56.10 TSU14419 SVTM052I COPY001 COPY SANFD002(8,007) PNODE=JHB-MWAY-PRD2 826
826 FROM FROM.DATASET
826 TO TO.DATASET
826 COMPLETED 00000000/SCPA000I
where the 2nd, 3rd and 4th lines of the MLWTO don't have the MSGID on them, which is causing my )MSG rule to fail, as I'm looking for the text
'SVTM052I COMPLETED 00000000/SCPA000I'
in msg.text.4. Now I think that whether or not each line of an MLWTO has the message id is down to the programmer who constructs the WTO, so I could update my exec to manually add the MSGID to each line, but I'd like to know exactly whats going on.