3.6.7 MAILbus 400 MTA for OpenVMS (MB400)

This section describes how to use the module-specific section of the initialization file to configure a scanning module for the MAILbus 400 MTA for OpenVMS systems.

3.6.7.1 The Queue Section

This section specifies information that should be reported by the scanning module concerning MPDU queues on the MTA, Peer MTA, and MTA Agents. Many of the entries in this section interact in ways that have to do with different levels of check. The rest of this section divides settable features into three types:

• Generic features that do not use check-levels

• Entries related to the age of MPDUs in the queue

• Entries related to size of MPDUs in the queue, and how many there are

Generic Entries

You can specify the following:

• Command=Command

  The command used to get information about an MPDU.

• Full_Name=Full name

  Name of the queues being checked.

• Identifier=Identifier

  Which field to report in the monitor record message in the `Identifier' field. Specify more than one NCL field in a list separated by commas.

• Information=Information

  Which field to report in the monitor record message in the `Information' field. Specify more than one NCL field in a list separated by commas. For example, the entry Information=Type,Priority specifies that Mail Monitor should send one record for each Type or Priority field.

Entries Related to MPDU Age

The Report_Oldest_MPDU setting determines the way these three entries interact:

• Report_Oldest_MPDU=yes|no

  Whether to report the age of the oldest MPDU queued and whether to check the age against the value specified for MaxAge1 (and, optionally, MaxAge2), before producing an error with the appropriate AgeSeverity if the value is too high.

• AgeSeverity1=Age severity and, optionally, AgeSeverity2=Age severity

  What severity to report for an error in either one or two levels of check, for the check-level specified (1 or 2).

• MaxAge1=Maximum age and, optionally, MaxAge2=maximum age

  The maximum age in seconds for the check-level specified (1 or 2).

These entries interact with each other in this way:

• If you set Report_Oldest_MPDU to Yes and you specify a value for MaxAge1, the scanning module reports the age of the oldest MPDU in the queue and produces a Monitor record with that information. Mail Monitor produces a warning with the severity level specified for AgeSeverity1.

• If you set Report_Oldest_MPDU to Yes and you specify a value for both MaxAge1 and MaxAge2, the scanning module does two further checks: if the age exceeds the value specified for MaxAge1, the warning has AgeSeverity1, and if the age exceeds the value specified for MaxAge2, the warning has the severity level specified for AgeSeverity2.

• If you set Report_Oldest_MPDU to No, the scanning module does not report the age of any message in the queue.

Entries Related to Size of the Queue and Number of MPDUs

The Report_Total setting determines the way these five entries interact:

• Report_Total=yes|no

  Whether to report total amounts queued (size and count) for all queues, and whether to check the size and count against the values specified for MaxSize1 and MaxCount1 (and, optionally, MaxSize2 and MaxCount2), before producing an error with the appropriate CountSeverity or SizeSeverity if the value is too high.

• CountSeverity1=Count severity and, optionally, CountSeverity2=Count severity

  What severity to report for an error in either one or two checks on the number of MPDUs in that queue, for the check level specified (1 or 2).

• MaxCount1=Maximum count and, optionally, MaxCount2=maximum count

  The maximum count for number of MPDUs in that queue, for the check level specified (1 or 2).

• MaxSize1=Maximum size and, optionally, MaxSize2=maximum size

  The maximum size for any MPDU in that queue, for the check level specified (1 or 2).

• SizeSeverity1=Size severity and, optionally, SizeSeverity2=Size severity

  What severity to report for an error in the size specified (at level 1 or 2) for the size of the queue.

The entries CountSeverityn, MaxCountn, MaxSizen, Report_Total, and SizeSeverityn interact in the same sort of way, but the scanning module checks both size and count:

• If you set Report_Total to Yes, and the number of MPDUs in the queue exceeds the value specified for either MaxCount1 or MaxCount2, the warning has the severity level specified for the appropriate CountSeverity - either CountSeverity1 or CountSeverity2.

• If you set Report_Total to Yes, and the size of the queue exceeds the value specified for either MaxSize1 or MaxSize2, the warning has the severity level specified for the appropriate SizeSeverity - either SizeSeverity1 or SizeSeverity2.

• If you set Report_Total to No, the scanning module does not report the size of the queue or the number of MPDUs in the queue.