When a CA-7 job fails, a SMF3 message is issued. We key on these messages via OPS/MVS to generate tickets. If this CA-7 job is changed to now utilize ARF to let's say perform an automatic restart of the job on a particular type of abend and the subsequent rerun is successful, the original abending run of the job still issues the SMF3 message saying the job failed. Is there a way to not issue the SMF3 message if ARF is handling the situation ?
The CA-7.SMF3 message is issued because WTO=YES is coded in the initialization deck for CA 7. This is set at a global level for all CA 7 jobs that fail. There is no way for CA 7 to not issue the message because the job has an ARFSET attached to it.
I can't think of a simplified way to have OPS/MVS know the rerun of the job was successful and generate something to
close the ticket.
Any ideas from the user community?????
Would there be a way to delay the ticketing using OPS/MVS when it get the CA-7.SMF3 say sub-seconds and then check the queue to validate the job failure? My shop does not use OPS/MVS to generate a ticket as we have an alternate tool and it is set up with that logic to wait and then check the queue, if it exists in abend status then continue with the ticket creation of job abend.