Parameters for Facilities › AOF Parameters › AOFDEST Parameter

AOFDEST Parameter

The AOFDEST parameter specifies the default destination of messages (such as SAY and TRACE statements) generated by AOF rules. AOFDEST is valid only when the message has one of these severity levels: I (informational messages), W (warnings), E (error messages), or S (severe error messages).

Default Value: X'C300000000000000'

Other possible values

Any valid destination, expressed in hexadecimals. To specify a value for AOFDEST, it may be helpful for you to think of the value as 8 bytes of information. These 8 bytes break down as follows:

• The first byte can be either C3, which is the hexadecimal representation of the character C; or C2, which is the hexadecimal representation of the character B.

  If you specify C3, the messages are sent to the specified console (that is, the console specified by the fourth byte of the AOFDEST value) and also to OPSLOG Browse.

  If you specify C2, the messages are sent to OPSLOG Browse only, and the second through eighth bytes of the AOFDEST value are ignored.

• The second byte of the AOFDEST value is reserved; this value should always be 00.
• The third byte of the AOFDEST value indicates the MCS flags code. There are two values you can specify for this byte: 00 (for X'00') indicating that the messages should be queued for the console and hard copy; and 02 (for X'02') indicating the messages should be queued for hard copy only.

  Note: The integer value of X'02' is 7; the OPSBITS() character string that corresponds to this value is HRDCPY.

• The fourth byte indicates the default console ID. You can specify a console ID from 00 to 99, but you must represent it in hexadecimals (the decimal values 00 through 99 are equivalent to the hexadecimal values X'00' through X'63').
• The fifth and sixth bytes indicate the default routing codes for the messages. The routing codes that you specify here are the same as the routing codes that you may specify for the AOFROUTE parameter. For more information, see the description of the AOFROUTE Parameter in this chapter.

  So, if you use the AOFROUTE parameter to set default routing codes for AOF messages and then later use bytes 5 and 6 of the AOFDEST value to set different routing codes, the values you set last override the earlier settings. The opposite is also true. For a list of routing codes and their descriptions, see AOFROUTE Parameter in this chapter.

• The seventh and eighth bytes indicate the default descriptor codes for the messages. The descriptor codes that you specify here are the same as those that you may specify for the AOFDESC parameter. For details, see the description of the AOFDESC Parameter in this chapter. In other words, if you use the AOFDESC parameter to set default descriptor codes for AOF messages and then later use bytes 7 and 8 of the AOFDEST value to set different descriptor codes, the values you set last override the earlier settings. The opposite is also true. For a list of descriptor codes and their descriptions, see the list of descriptor codes in AOFDEST Parameter.

Set or modify this parameter...

Anytime

Example: AOFDEST

This function sends messages generated by AOF rules to console 5.

OPSPRM('SET','AOFDEST','C300000500000000')