Example of message suppression

The following example demonstrates when a message will be suppressed to prevent flooding of the operator console. This suppression occurs without regard to the suppression level assigned to the message in the USS table and without regard to the message suppression level assigned to VTAM® using the MODIFY SUPP command or the SUPP start option.

Message IST367I is a member of the message-flooding prevention table:

IST367I NO STORAGE TO DEFINE NODE nodename CONFIG configname

This message is issued when VTAM does not have enough storage to expand the host-node table. Therefore, a new host element address could not be assigned for the defined resource nodename in the configuration configname. The specifications for the message in the table are:

1. Time-span: 30 seconds
2. Variable fields: configname

Without message flooding prevention, this message is displayed every time it is issued without regard to time-span or configname.

Time  1:  IST367I  NO STORAGE TO DEFINE NODE NODE1 CONFIG CONFIG1
Time  2:  IST367I  NO STORAGE TO DEFINE NODE NODE1 CONFIG CONFIG2
Time  3:  IST367I  NO STORAGE TO DEFINE NODE NODE2 CONFIG CONFIG1
Time 35:  IST367I  NO STORAGE TO DEFINE NODE NODE1 CONFIG CONFIG1

With message flooding prevention, this message at Time 3 would not be displayed for the following reasons:

configname is the same as configname at Time 1.
The message at Time 3 was issued within 30 seconds of the message at Time 1.

The message at Time 2 would be displayed because configname is not the same.

The message at Time 35 would be displayed since it was issued after the 30 second time-span.

Time  1:  IST367I  NO STORAGE TO DEFINE NODE NODE1 CONFIG CONFIG1
Time  2:  IST367I  NO STORAGE TO DEFINE NODE NODE1 CONFIG CONFIG2
Time 35:  IST367I  NO STORAGE TO DEFINE NODE NODE1 CONFIG CONFIG1