You use the pdmlgput operand to specify the messages that are to be suppressed. This operand can also be used to specify the following:

• Suppress output of all messages
• Specify the messages that are to be output
• Output the specified messages by changing their displayed severity (See 8.1.5 Changing the severity of the messages to be output to syslogfile.)

When message output suppression is specified, the specified messages are not output to syslogfile. Suppressed messages are output to the message log files. The following table shows the differences in message output processing depending on whether message output suppression is in effect.

Table 8-3 Differences in message output processing depending on whether message output suppression is in effect

Legend:

Y: Messages are output.

N: Messages are not output.

Note

For a HiRDB single server configuration, use the columns for Server machine in which the system manager is defined.

#1: For a HiRDB parallel server configuration, message logs are output to syslogfile and the message log files of the server machine where the system manager is defined. However, in the following cases, messages might not be output at all or might be output to syslogfile of the server machine that issued the messages:

• The system monitor unit has not started yet or has encountered an error.
• The message log server has terminated abnormally or has not been restarted yet.
• The server machine is a standby system.

#2: Messages that are normally output to both syslogfile and the message log files are now output only to the message log files.

#3: For a HiRDB parallel server configuration, pdlog1 and pdlog2 (message log files) are created under $PDDIR/spool of the server machine in which the system manager is not defined, and messages that used to be output to syslogfile are now output to these message log files.

In the cases below, message output is not suppressed; instead, messages are output to syslogfile.

(a) When an error occurs in a message log file

When an error occurs in a message log file, an error message is output to syslogfile. Messages that cannot be output to the message log file because of the error are output to syslogfile.

(b) When the HiRDB system definition contains an error

Messages that report a HiRDB system definition error are not suppressed. Such error messages are output to syslogfile.

(c) Messages that are output when commands are executed

Messages that are output when the following commands are executed are not suppressed:

• pdsetup
• pdplgset
• pdlodsv

(a) Example 1

No messages are output to syslogfile and all messages are output to the message log files. The following an example of specifying the pdmlgput operand for this case:

 
pdmlgput -s N -c ALL
 

(b) Example 2

The KFPS01820 and KFPS00105 messages are not output to syslogfile, but instead are output to the message log files. The following is an example of specifying the pdmlgput operand for this case:

 
pdmlgput -s N -m KFPS01820,KFPS00105
 

(c) Example 3

Only the KFPH00211 and KFPH00212 messages are output to syslogfile and all other messages are output to the message log files. The following is an example of specifying the pdmlgput operand for this case:

 
pdmlgput -s N -c ALL                          ...1
pdmlgput -s Y -m KFPH00211, KFPH00212         ...2
 

Explanation

1. No messages are to be output to syslogfile and all messages are to be output to the message log files.
2. The KFPH00211 and KFPH00212 messages are to be output to both syslogfile and the message log files.

(a) Processing when a message log file becomes full

When a message log file's capacity (value of the pd_mlg_file_size operand) is reached, the output destination for messages is swapped to the other message log file. When this swapping occurs, the KFPS01910-I message is output to syslogfile. If output of the KFPS01910-I message is suppressed, it is output to the message log file that was being used before swapping. If you are monitoring the message log file, you must swap the monitoring-target message log file whenever the KFPS01910-I message is output.

(b) Message log file size

When message output suppression is in effect, you must allocate a sufficient size for the message log file. Use the pd_mlg_file_size operand to specify a message log file size.

When message output suppression is in effect, a large volume of messages might be output to the message log file depending on the operating environment. Therefore, if the message log file size is insufficient, message log files are overwritten frequently, and there is a possibility that important messages, such as system operating status and troubleshooting information, which are output only to message log files might be erased.

The following table shows HiRDB processing when message output suppression is used in combination with message log output dispersion.

Table 8-4 Processing by HiRDB when message output suppression is used in combination with message log output dispersion