What is to be considered when sending mass mail to a large number of recipients in CA TPX?

Products

• TPX - Session Management
• Vman Session Management for z/OS

Issue/Introduction

This document describes what you should review in advance of sending a mass mail to a large number of users in a TPX region in order to avoid severe storage problems.

What is to be considered when sending mass mail to a large number of recipients in CA TPX?

Environment

TPX for z/OS

Resolution

Sending a mail to several thousand users can cause storage problems. But there is protection available inside TPX.

In the SMRT you can specify Mail Parameters so that any mass mailing is split into several packets containing a smaller number of mails:

• Send message or bulletin pacing - This represents the number of messages which will be sent at one time.
• Pacing time in 1/100 of seconds - This is the time TPX waits before the next group of messages is sent.

For example:

"Send message or bulletin pacing" = 50 
"Pacing time in 1/100 of seconds" = 100

... TPX will send 50 messages then wait one second. This will send 2000 messages in 40 seconds and avoids a peak in storage usage at one point in time.

 

Because the two above mentioned parameters are prefixed with an asterisk '*' they can be changed 'on the fly', while TPX is running.  Make the desired changes, save the table and reload the SMRT in TPXOPER with command: RELOAD SMRT=<name_of_SMRT>.

 

 

Additional Information

 

TPBL0071 or TPXL0071  MAILBOX TASK DELAYING DUE TO cause

Reason:

If the value of cause is PACING COUNT EXCEEDED, the number of recipients processed while sending or saving a message exceeded the pacing count set in the System Options Table (SMRT).

If the value of cause is STORAGE OVERLOAD, the internal storage usage exceeded the overload threshold set in the SMRT.

In either case, the product suspends the processing of the message, allowing the mailbox facility to process other user's tasks. The product resumes processing at the end of the queue of mailbox facility requests after a short delay.

If the cause of this message is an overload and the overload still exists, the processing will be delayed again. When the overload condition is resolved, the product issues message TPXL0072.

Action:  None.

 

TPBL0072 or TPXL0072  MAILBOX DELAY DUE TO cause ENDED

Reason:

The storage overload condition described in message TPXL0071 has been resolved.

Action:  None