Previous Topic: Step 1a. Add the New Email ParametersNext Topic: Step 1b.Modify Existing RMOPARM Values


Considerations for Using Email with CA Spool

Review the CA Spool parameter deck to be sure that the values specified on the EMAILQ definition route the file to CA Spool for delivery.

CA Spool customers use several input interfaces. One or perhaps all of them are available at your site.

To process the report pre-spool, the Sysout Allocation Intercept can be used. That interface is controlled by the CA Spool parameters SUBS and SUBSCLAS.

By default, CA Spool checks the writer, if specified, to determine whether to intercept the allocation. Consider the following:

Review the SUBS and SUBSCLAS parameters you have specified in the CA Spool parameter deck and their meanings in the CA Spool documentation to determine how best to code the EMAILQ values to use the Sysout Allocation Intercept to route your CA Deliver files to CA Spool.

To process the email message after it has been written to the JES Spool by CA Deliver, the CA Spool NJE interface or SAPI interface can be used.

To use the NJE interface, the destination specified in EMAILQ must be the CA Spool NJE node name and the writer value is the CA Spool printer node that has been defined to use the Email print driver (TCPDRIV=SMTP).

The SAPI interface is controlled by the XFER, XFERDEST, XFERCLAS, XFEROPT and XFERSAPI parameters. Be aware of the following:

Review the XFERDEST and XFEROPT parameters you have specified in the CA Spool parameter deck and their meanings in the CA Spool Customization Guide to determine how best to code the EMAILQ values to use the SAPI interface to collect the files that CA Deliver writes to the JES Spool.