What to check when a DO MAIL in a Control-M for z/OS job definition is coded and the mail is not received.


 

This is a short description of how a DO MAIL works.

 - The job ends and the Control-M monitor writes a sysout to the JES spool based on parameters coded in the MAIL section of the IOAPARM member.

 - The SMTP started task then removes the sysout from the JES spool and sends the email to the email server.

So what can be checked when this does not work:

1) Does the sysout get written to the JES spool? You can see this from the output queue display using SDSF. If the sysout is still on spool then it probably means that the parameters set in the MAIL section in IOAPARM are not correct, specifically the following:

   - Parameter SMTPNAME. This must be the same name as the SMTP started task name that s running.

   - Parameter CLASS. Class of sysout from IOAMAIL to SMTP. 1 character. This must be a JES non-held class.

2) If the sysout IS removed from the JES spool and the email is is not received, look at the sysout for the SMTP started task to see if there are any errors there.

If this does not help then open a case with bmc Support providing the following:
a)    Content of member IOAPARM
b)    Does the sysout get created by the Control-M started task? You can check this be temporarily holding the Control-M started task, run the job, then look at the task in SDSF to see if the sysout is created. DON’T FORGET TO RELEASE THE STARTED TASK AFTERWARDS!