SETHOLD

Purpose

SETHOLD lets you select which AOF messages are held for your operator ID. This command is used by the INGNTFY command but can be invoked separately.

Parameters

CONFIG

Specifying this option changes your hold settings to match the settings specified for your operator ID in the automation control file. If your operator ID is not defined as a notification operator, no messages will be held.

AUTO

Specifying this option changes your hold settings to match the settings INGNTFY has currently defined for your operator ID. If your operator ID is not a notification operator, or its definition as a notification operator has been deleted, no messages will be held.

i a e d w

Each character specifies the hold setting for the corresponding type of message. If a Y is specified, messages of that type will be held, if any other character is specified, messages of that type will not be held. A character must be specified for each type.

Restrictions and Limitations

The SETHOLD command is only useful on an OST task. If issued on an NNT or RMT task, the message-holding flags in the remote domain will be ignored, because the automation table on the OST task will override whatever message attributes may have been specified in the remote domain.

SETHOLD does not update the INGNTFY globals, so if you use it with anything other than the AUTO parameter, the hold settings shown by INGNTFY QUERY may not reflect reality.

Usage

SA z/OS® issues SETHOLD at SA z/OS initialization, when you log on to NetView interface, and when INGNTFY is used.

When you log on, an entry in the sample automation table (in member AOFMSGMS) will invoke SETHOLD AUTO for your operator ID. When INGNTFY is used to change an operator's HOLD settings, SETHOLD AUTO will be issued on the appropriate OST task after the global information has been updated.

A more efficient usage would be to modify your initial REXX scripts to issue SETHOLD with specific settings and to not have any hold settings specified in the automation control file or through INGNTFY. If you choose to do this, you will need to remove the automation table entry for the OST (in member AOFMSGMS) and set the AOFLOCALHOLD advanced automation option to 1. Doing this will stop INGNTFY from using EXCMD to issue SETHOLD AUTO, which can disrupt the hold settings specified from your profiles.

Note that the attributes for held messages are defined as automation table synonyms in the AOFMSGSY member.

It is recommended that you do not hold information messages because SA z/OS can generate quite a few of them. If you do hold them, use the CLRHELD command to remove them. You may want to modify the attributes for held information messages (held in the AOFMSGSY ACF member) so that held information messages will not actually be held.