This section describes how to use the module-specific sections of the initialization file to configure a scanning module for ALL-IN-1 V3.1 or later for OpenVMS.
The scanning module reads A1CONFIG.DAT, and checks logical names needed for a working configuration.
The section has this format:
[A1Config]
The logical names to check depend on the contents of the A1BASE record in A1CONFIG.DAT. The A1BASE record holds both mail resources and directory resources. Table 3-1 shows the A1Config section entry names, the corresponding A1BASE fields, and the logical names that the scanning module checks.
| Entry Name | A1BASE Record Field | Logical Name |
|---|---|---|
| MTAType | OA$MTI_API_TYPE | |
| BatchQueue | MAILQUEUE | OA$MTI_ QUEUE |
| MailBox | MBXNAME | OA$MTI_MAILBX |
| MRNode | MRNODE | OA$MTI_MR_NODE[1] |
| DSAType | DIR_TYPE | OA$DIRECT_TYPE |
| DSALevel | DIR_LEVEL[2] | OA$DIRECT_PRIME[3] |
|
[1] On a system that uses only MAIlbus 1 products, the logical name checked is MR$NODE. [2] On an ALL-IN-1 V3.1 system, the field is DDS$LEVEL. [3] On an ALL-IN-1 V3.1 system, the logical name checked is OA$DDS_PRIME. | ||
If any of these logical names either is not defined or has an unacceptable definition, Mail Monitor produces a Monitor Record with the severity level shown in this list, which uses the values defined in the note at the beginning of Section 3.3.
Apart from these logical names, the following entries in the [A1Config] section enable checking of the ALL-IN-1 OpenVMS manager's account, and checking of the ALL-IN-1 script symbiont queues:
Check the Manager account, and report at the error level specified if the account is expired or disabled. If you want to disable this check, remove the entry.
Check whether the queue exists, and whether there are any problems with access or errors with the queue. Report any problem at the error level specified. If you want to disable this check, remove the entry.
Check the number of pending script symbiont jobs, and report at the error level specified for SymbiontPendingJobsSeverity if the maximum is exceeded. If you want to disable this check, remove the entry.
Check the number of failed script symbiont jobs, and report at the error level specified for SymbiontFailedJobsSeverity if the maximum is exceeded. If you want to disable this check, remove the entry.
(All *Severity* entries in this section have error level values as described in the note at the beginning of Section 3.3).
For example:
[A1Config] MTAType=4 BatchQueue=4 MailBox=4 MRNode=4 DSAType=4 DSALevel=4 ManagerAccount=3 SymbiontSeverity=3 SymbiontMaxPendingJobs=10 SymbiontPendingJobsSeverity=3 SymbiontMaxFailedJobs=10 SymbiontFailedJobsSeverity=3
The scanning module checks the Mail Areas (also known as Shared Document Attribute Files - SDAFs) as long as RunCheck is set to 1 in this section. For each Mail Area, the scanning module checks files, logical names, and device space (at two levels, optionally).
The section has this format:
[A1MailAreas]
The section has these entries:
Check the ALL-IN-1 Mail Areas, using the values given in the rest of this section. 1 means check, 0 means do not check.
Produce a Monitor Record with this severity when reporting errors that do not have a severity defined, or that have a severity defined that is not appropriate.
Check the logical names that refer to the ALL-IN-1 Mail Areas, and report at this error level if a logical name is undefined or has an incorrect value.
Check for the SDAFs in each ALL-IN-1 Mail Area, and report at this error level if a file is absent.
Check for this amount of space (in 512 byte blocks) on each device serving the ALL-IN-1 Mail Areas, and report at the error level specified for DeviceSeverity1 if the minimum is not available. If you want to disable this check, remove the entry. The scanning module checks only ALL-IN-1 Mail Areas that are open.
Check for this amount of space (in 512 byte blocks) on each device serving the ALL-IN-1 Mail Areas, and report at the error level specified for DeviceSeverity2 if the minimum is not available. The scanning module checks only ALL-IN-1 Mail Areas that are open.
(All *Severity* entries in this section have error level values as described in Section 3.3)).
For example:
[A1MailAreas] RunCheck=1 DefaultSeverity=3 LogicalSeverity=3 FileSeverity=3 DeviceMinBlocks1=20000 DeviceSeverity1=2 DeviceMinBlocks2=2000 DeviceSeverity2=3
The scanning module checks each ALL-IN-1 pending file queue named in an A1Queue section. Mail Monitor checks the named queue and sends a Monitor record reporting the severity defined in this section if the queue is undefined or if there is any other error. The default value is 3 (error).
It has the following format:
[A1Queue queue-name]
For each queue that you specify, severity values are as defined in the note at the beginning of Section 3.3.
The severity value for the queue.
For example:
[A1Queue MAIL MANAGER] Severity=3
The scanning module checks the Shared Directories if RunCheck is set to 1 in this section. For each shared directory, the scanning module checks files, logical names, the size of the directory file (with two maximums, optionally), and device space (at two levels, optionally).
The section has this format:
[A1SharedDirectories]
The section has these entries:
Check the ALL-IN-1 Shared Directories, using the values given in the rest of this section. 1 means check, 0 means do not check.
Produce a Monitor Record with this severity when reporting errors that do not have a severity defined, or that have a severity defined that is not appropriate.
Check the logical names that refer to the ALL-IN-1 Shared Directories, and report at this error level (as explained in the note at the beginning of Section 3.3) if a logical name is undefined.
Check for the directory file in each ALL-IN-1 Shared Directory, and report at this error level if a file is absent.
Also, in Mail Areas that are open, the scanning module does these checks for Shared Directories that are in the write window:
Check the directory file for this maximum block-size, and report at the error level specified for DirectoryFileSeverity1 if the maximum is exceeded. If you want to disable this check, remove the entry.
Check the directory file for this maximum block-size, and report at the error level specified for DirectoryFileSeverity2 if the maximum is exceeded.
Check for this amount of space (in 512 byte blocks) on each device serving the ALL-IN-1 Shared Directories, and report at the error level specified for DeviceSeverity1 if the minimum is not available. If you want to disable this check, remove the entry.
Check for this amount of space (in 512 byte blocks) on each device serving the ALL-IN-1 Shared Directories, and report at the error level specified for DeviceSeverity2 if the minimum is not available.
(All *Severity* entries in this section have error level values as described in Section 3.3)).
For example:
[A1SharedDirectories] DefaultSeverity=3 LogicalSeverity=3 FileSeverity=3 DirectoryFileMaxBlocks1=100 DirectoryFileSeverity1=2 DirectoryFileMaxBlocks2=128 DirectoryFileSeverity1=3 DeviceMinBlocks1=20000 DeviceSeverity1=2 DeviceMinBlocks2=2000 DeviceSeverity2=3
The scanning module checks each ALL-IN-1 permanent symbol named in an A1Symbol section. Mail Monitor checks the named symbols and sends a Monitor record reporting the severity defined in this section if the symbol is undefined or if there is any other error. The default value is 3 (error), and by default the scanning module checks two symbols: OA$MTI_TIME_OFFSET and OA$_MTI_TIME_ZONE. If you do not choose to define more symbols to check, you can check these two by specifying an A1Time section, as described in Section 3.6.2.6.
It has the following format:
[A1Symbol symbol-name]
For each symbol that you specify, severity values are as defined in the note at the beginning of Section 3.3.
The severity value for the symbol.
For example:
[A1Symbol OA$MTI_TIME_OFFSET] Severity=3
By default, the scanning module checks the two ALL-IN-1 permanent symbols related to time: OA$MTI_TIME_OFFSET and OA$_MTI_TIME_ZONE. Mail Monitor checks these symbols and sends a Monitor record reporting the severity defined in this section if there is any problem related to time. The default value is 2 (warning).
It has the following format:
[A1Time]
Severity values are as defined in the note at the beginning of Section 3.3.
The severity value for a problem related to time.
For example:
[A1Time] Severity=2
The scanning module checks any OpenVMS account named in this section. By default Mail Monitor checks only three accounts.
The section has this format:
[Account filename]
Each Account section has these entries:
The severity value for a problem, as defined in the note at the beginning of Section 3.3.
The full name of the account.
For example:
[Account A1$SCRIPT] Severity=3 Full_Name="Script Symbiont account" [Account A1$XFER_IN] Severity=3 Full_Name="Transfer User import account" [Account A1$XFER_OUT] Severity=3 Full_Name="Transfer User export account"
The scanning module takes note when components are added to the ALL-IN-1 configuration while the Mail Monitor server is running. Each component has a Mail Area associated with it, and each Mail Area contains a number of shared directories. This section specifies whether and how to record updates. It also defines the severity of errors related to dynamically added components.
This section has the following format:
[Dynamics]
You can specify the following:
The default severity value for dynamically added components, as defined in the note at the beginning of Section 3.3.
Update the records about dynamically added components. The three settings send these instructions to the scanning module:
The setting Update=No is useful to prevent unused
processes, listed in the ALL-IN-1 intialization file, from being
added to the A1V3 configuration file.
For example:
[Dynamics] Update=All
This section specifies the severity value that Mail Monitor reports when certain logical names are not defined. This section also checks for any internal error.
It has the following format:
[Message_Severity]
For each of the missing logical names, Mail Monitor sends a Monitor record reporting the severity defined. The default value is 2 (warning) for SYS$NODE and 4 (fatal) for OA$IMAGE.
All the error values assigned to entries in this section are as explained in Section 3.3.
For example:
NoLogicalSYS$NODE=2 NoLogicalOA$IMAGE=4 InternalError=4
This section specifies the severity value that Mail Monitor reports for ALL-IN-1 process states. Mail Monitor checks the named processes and sends a Monitor record reporting the severity defined. The default value is 2 (warning).
It has the following format:
[Processes]
For each process state that you specify, severity values are as defined in the note at the beginning of Section 3.3.
The severity value for undetermined process states.
The severity value for running processes.
The severity value for disabled processes.
The severity value for stopped processes.
The severity value for starting processes.
The severity value for stopping processes.
The severity value for failed processes.
For example:
[Processes] Running | Disabled | Stopping | Starting = 0 Running=1 Disabled=1 Stopped=4 Starting=2 Stopping=4
The scanning module checks each OpenVMS queue named, or partially specified with a wildcard charcter, in a Queue section. The scanning module checks the queue for existence and status, including any pending jobs, or jobs that have failed and been retained on the queue, and generates a Monitor record and a Queue record. The Monitor record reports the severity defined in this section if the queue is undefined or if there is any other error. The default value is 3 (error).
It has the following format:
[Queue queue-name]
The full name of the queue.
The severity value for the queue.
Check the number of pending OpenVMS jobs, and report at the error level specified for PendingJobsSeverity if the maximum is exceeded. If you want to disable this check, remove the entry.
Check the number of failed OpenVMS jobs, and report at the error level specified for FailedJobsSeverity if the maximum is exceeded. If you want to disable this check, remove the entry.
(All *Severity* entries in this section have error level values as described in Section 3.3)).
For example:
[Queue OA$FORMATTER] Full_Name="Background Print Formatter Queue" Severity=3 MaxPendingJobs=10 PendingJobsSeverity=3 MaxFailedJobs=10
This section specifies the severity value that Mail Monitor reports for shutdowns, of ALL-IN-1 and also for faulty (or late) restarts, whether automatic or manual. The default value for a shutdown is 1 (informational).
It has the following format:
[Shutdown]
You can provide one general parameter, to send a Mail Monitor record whenever ALL-IN-1 shuts down:
Two parameters let you configure the sort of warning to send if, after a restart, there is an unexpected delay before ALL-IN-1 becomes operational again:
Maximum time (in minutes) to wait after the product's Restart Time before sending an error message if the product is not started (after a manual or automatic restart).
Severity level of Monitor Record to display after MaxRestartDelay has expired.
Two parameters let you configure the sort of warning to send if, for some specified time after a shutdown, there has been no restart:
Maximum time (in minutes) to wait after shutdown before sending an error message if the product is not started manually.
Severity level of Monitor Record to display after MaxNoRestart has expired.
Values you give for Severity, RestartDelaySeverity, and NoRestartSeverity are as defined in the note at the beginning of Section 3.3.
For example:
[Shutdown] Severity=1 MaxRestartDelay=30 RestartDelaySeverity=4 MaxNoRestart=180 NoRestartSeverity=4