The reason for the problem is the following:
- In the schedule definition on the mainframe side there is at least one schedule definition with at least one DO MAIL which have at least one of the TO or CC field which contains over 255 bytes.
- The TO and CC have a limitation of 255 bytes each.
This is documented in the following manual:
Control-M for z/OS User Guide
Chapter 3 - Job Production Parameters
DO MAIL: Post–Processing Parameter
Table 182 DO MAIL Subparameter Formats
TO
Destination of the message, limited to a maximum of 255 characters. Mandatory. Valid values are:
- the full e-mail address
- a recipient name
If you use a recipient name, the full e-mail address is supplied by the MAIL section of the IOAPARM member in the IOA PARM library. The IOAPARM member also includes the value of the DFLTSFFX field, which specifies the e-mail address suffix (such as MAIL.DOMAIN.COM), the SMTP STC name, and the HOST name. Note: The @ character is taken from the ATSIGN parameter in the IOAPARM member.
- the nick name or group name defined in MAILDEST member. For more information regarding MAILDEST member, see the INCONTROL for z/OS Administrator Guide.
You can use AutoEdit variables in this field, in any combination of text and valid AutoEdit variables.
CC
Destination to which a copy of the message is to be sent, limited to a maximum of 255 characters. Optional.
Valid values are:
- the full e-mail address
- a recipient name
If you use a recipient name, the full e-mail address is supplied by the MAIL section of the IOAPARM member in the IOA PARM library. The IOAPARM member also includes the value of the DFLTSFFX field, which specifies the e-mail address suffix (such as MAIL.DOMAIN.COM), the SMTP STC name, and the HOST name. Note: The @ character is taken from the ATSIGN parameter in the IOAPARM member.
- the nick name or group name defined in MAILDEST member. For more information regarding MAILDEST member, see the INCONTROL for z/OS Administrator Guide.
You can use AutoEdit variables in this field, in any combination of text and valid AutoEdit variables.
The best solution to address this problem is the following:
Define GROUPs and NICKname in &ilprefa.PARM(MAILDEST)
Using GROUP of email and NICKname will drastically reduce the number of characters set in TO or CC fields.
=> DO MAIL can use in TO and CC
- Full email address
- NICKname defined in &ilprefa.PARM(MAILDEST)
- GROUP defined in &ilprefa.PARM(MAILDEST)
=> To avoid the maintenance of email address in each and every schedule definition using DO MAIL, define and use GROUPs and NICKnames in MAILDEST:
- working groups for operators, production analysts, system team, management...
- nickname for Production Director, IT Director...
So the email is sent to a function or a group of users and the real final user email is maintained in the &ilprefa.PARM(MAILDEST) once for all.
=> To define the GROUP in MAILDEST please review the manual:
INCONTROL for z/OS Administrator Guide
1)
Chapter 2 - IOA Administration
Message Destination Tables
The Mail Destination Table
2)
Chapter 3 - Control-M
Basic Administrative Functions
Shout / Mail Facility Destination Table Administration
Setting up the Mail Destination Table (MAILDEST)
The MAILDEST can be dynamically reloaded using the modify command: F CONTROLM,NEWMAILDST
See the manual:
INCONTROL for z/OS Administrator Guide
Chapter 3 - Control-M
Basic Operations
Refreshing the Mail Destination Table (MAILDEST)
Other solutions/bypass for the very short term:
1. Split the recipients between the TO and CC fields. NOTE: usually TO recipients are for action CC recipients are for information!
2. Use multiple DO MAIL statements in the same schedule definition