QAOSMTP1


QAOSMTP1 is a sample EXEC that demonstrates how you can pass e-mail data to QAOSMTP2, which performs the actual e-mail transmission.

You might not have to make any modifications to the QAOSMTP2 EXEC.

However, to use the solution, you mist customize QAOSMTP1. Make a copy of QAOSMPT1, rename the EXEC, and store it in UBBPROC. In UBBPROC, edit the EXEC to use values from your system.

You can also incorporate the logic in QAOSMTP1 into your own REXX application to generate e-mail messages.

Related topic

The areas that need to be modified in QAOSMTP1 are listed in the following table.

Name

Description

SMTP_SERVER

Is the name of the local mail server

This server distributes mail to the POP3 and Exchange mail servers.

You can manually specify the SMTP_SERVER name in the EXEC or you can predefine the value in a PROFILE variable via the windows-mode EZAOSOL menu. Using a PROFILE variable is preferable, as the values can be easiy changed in the future without having to edit the EXEC source code. For more information about the EZAOSOL menu, see the Using-BMC-AMI-Ops-Automation-basic-applications.

SMTP_REPLYTO

Is the e-mail message address that receives replies when responding to this e-mail message

It must be a valid address (or example, yourName@yourCompany.com).

Sender of the e-mail message

Is the first line queued (your name), which might be different from the REPLYTO e-mail ID

Valid formats are dependent upon the mail server that is being used. Most mail servers accept '<user@yourCompany.com>'. Other typical formats that are accepted are ''your name'' and ''your name'<id@bid.company.com>'. Verify with your site's SMTP documentation for acceptable values.

Recipient(s)

Is a blank-delimited list

It is queued second. Do not use the format 'name'<user@bigCompany.com>.

Email Subject

Is the text for the subject line of the e-mail

Email text

Is a line or multiple lines of text that that will be sent to the recipients

This information is displayed in the body of the e-mail. message

CC_USERS

Is a list of users who will receive a copy of this e-mail message

Use the same syntax as used for the Recipient(s) field.

TLS

Specifies if TLS encryption is used.

Valid values are Y or N and the default value is N (do not use TLS encryption).

Specifying Y means use TLS encryption.  See comments in the QAOSMTP1 member for more information (including the need for an AT-TLS policy).

USERID and PASSWORD

Specify the User ID and password for login to the mail server using the AUTH LOGIN method.

Mail servers might require that TLS=Y is specified in order to offer the AUTH LOGIN method.     

Warning

Important

A sender's name, subject, and at least one line of message text are required. Keep line lengths reasonable so that the e-mail message has a readable format. The utility EXEC (QAOSMTP2) inserts a CrLf after each text line in the generated e-mail message.

See BBSAMP member QAOSMTP1 for a sample EXEC. 

Some SMTP servers depend on its users to supply the correct time offset from UTC (GMT). Other SMTP servers supply this time offset internally and do not depend on its users. If you see an inaccurate 'sent' time on an Email that you received, this is a common symptom of an incorrect time offset.

The EXEC QAOSMTP2 obtains the local time offset from MVS and appends this value to the Date and Timestamp. The example below shows a timestamp for an email generated on a MVS with local time 7 hours behind UTC.

Date: Wed, 12 Oct 2005 16:16:58 -0700

If your MVS system does not have the correct time offset from UTC (for example, this applies to some customers who run MVS with the local time set to the GMT) , you may need to customize the QAOSMTP2 EXEC to hard code the appropriate time offset. You might also have to do this if you change the time to observe Daylight Savings Time (DST).

To view the local time offset on your MVS, issue the command MVS D T (display time).

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Automation 8.4