Customization › TCP/IP PrintDirect › Email Print Driver

Email Print Driver

Use this print driver to automatically distribute CA Spool print files, including PDF, HTML, and RTF wrapped text files, by email directly to users' mailboxes for viewing and printing.

The Email print driver provides support for:

• Attaching print files as text, PDF, PCL, Word, Excel, and other file formats
• Automatic conversion of text files into PDF, HTML, or RTF files when they are sent through email
• HTML-based email message body formatting including multiple fonts, colors and image support
• Web Link support

  Consequently, the email message includes a link to the CA Spool file, rather than the CA Spool file as an attachment. When the user clicks the Web Link, the CA Spool file automatically appears, through the CA Spool Web Interface.

• Control over recipients (including cc and bcc) subject line, and attachment file name
• Automatic creation of unique identifying names for recipient, subject, and attachment
• The OUTPUT statement email parameters MAILTO, MAILCC, MAILBCC, MAILFROM, MAILFILE and REPLYTO are supported

The email print driver can connect:

• Directly to a LAN-based email server such as Microsoft Exchange Server, Lotus Notes, or Novell GroupWise
• Indirectly through a z/OS-based IBM TCP/IP or TCPaccess SMTP server

You can specify the email subject, message body, recipients, copy recipients, blind copy recipients, and email attachment file name using the standard OUTPUT statement email parameters MAILTO, MAILCC, MAILBCC, MAILFROM, MAILFILE and REPLYTO. The SUBSYS, NJE and XFER interfaces convert these parameters to the corresponding CA Spool email parameters and store them as OUTPUT USERDATA parameters.

Or you can specify the email subject, message body, recipients, copy recipients, blind copy recipients, and email attachment file name at the printer level using the 4*60=240 bytes DRIVPRM1-4 parameters and at the print file level using the 4*60=240 bytes OUTPUT ADDRESS parameter and the 16*60=960 bytes OUTPUT USERDATA parameter, and through a predefined MAILBOOK or Writer specified MAILLIB email parameter members and inline first in the print file before the print data.

You can use CA Spool DESTID definitions to automatically assign OUTPUT ADDRESS parameters.

Inline email parameters are accepted on the first 16 records of the print file. A completely blank line terminates the search for inline email parameters previous to the 16th record. When passing email parameters inline, the carriage control attribute determines the column where the parameters must begin. Email parameters within files whose carriage control attribute is A or M must begin in column 2. Email parameters within files without a carriage control attribute, NOCC files, must begin in column 1. Inline email parameters are limited to 60 characters per line.

The inline email parameters MSGSTART=>> and <<MSGEND= support longer messages, message lines up to 252 bytes and blank lines. MSGSTART=>> and <<MSGEND= must be coded on separate lines above and below the inline message they delimit.

Note: The printer node DRIVPRM1-4 parameters are processed first, OUTPUT ADDRESS parameters are processed second, OUTPUT USERDATA parameters are processed third, MAILLIB email parameter members are processed forth, and inline email parameters are processed last. If you specify email parameters more than once, then the last specification is used with the exception of TO=, CC= and BCC=. Values for TO=, CC= and BCC= are combined from all of the possible sources. If MSG= is passed as an inline email parameter, it must be the last parameter specified.

MAILLIB PDS members can be used to supply addressing information for the SMTP driver. The MAILLIB PDS is searched for a member equal to the MAILBOOK=mail-book-member value. The first 64 records of up to 60 bytes may contain any email parameters except for MSGSTART=>> and <<MSGEND=. If MAILBOOK= is not specified, the Remote Dest or Writer file attribute, if specified, is used for searching the MAILLIB PDS for a match.

You can have unique identifying names automatically by specifying that email subject, recipient, and attachment file names be synthesized from userid, destination, file name, file number, print‑mode, origin host name, date, time, job number, job name, job class, job step, proc step, DD name, and fixed text.