Statements/parameters for AUTORxx

NOTIFYMSGS

May only appear once in a parmlib member. If multiple members are specified in the SET AUTOR= command, the first NOTIFYMSGS value is accepted. The other specifications are ignored.

HC: Indicates that the auto-reply notification messages (CNZ2605I, CNZ2606I and CNZ2608I) only appear in the hardcopy log. If NOTIFYMSGS is not specified, HC is the default value.
CONSOLE: Indicates that the auto-reply notification messages (CNZ2605I, CNZ2606I and CNZ2608I) are displayed on consoles receiving routing codes 2 (operator information) or 10 (system programmer information) and also appear in the hardcopy log.

MSGID()

The first keyword of the message definition.

msgid

Must be in the range of 1 to 10 characters. The message ID must be enclosed in quotes if it contains non-alphanumeric characters, like equal signs, parenthesis, etc. The quotes do not count as part of the message ID. If enclosed in quotes, the msgid is not converted to uppercase.

Wildcards are partially supported in the msgid:

The question mark "?" is supported, because some messages (e.g., JES2 messages) start with an installation-specified character (not always $). For instance, ?HASP1234 is allowed.
The asterisk "*" is not treated as a wildcard in a msgid. If a msgid contains both a question mark and an asterisk, the message definition is rejected.
Multiple question marks in the msgid is supported. For instance, eight question marks ???????? would match on any eight character message ID.

Note: The maximum number of message IDs that do not contain wildcards is limited to 10,413. The maximum number of message IDs that contain wildcards is limited to 1,500.

NOAUTORREPLY

Can be specified to cause subsequent MSGID() specifications of this message ID (in this member or subsequent members) to be ignored. With the NOAUTOREPLY option, you can have your own AUTORxx member and use it to remove messages specified in the AUTOR00 member without actually removing the AUTOR00 statements. No auto-reply processing is performed for this message ID.

DELAY(nnn{M|S})

Can appear in any order and on different lines from REPLY() and MSGID(). nnn is the minimum amount of time, in minutes (M) or seconds (S), to delay after the WTOR is issued but before the system issues a reply. Only three digits are supported, which gives a limit of 999 minutes (16.65 hours) or 999 seconds (16.65 minutes). The delay value of 0 is supported, but specifying the value of 0 can prevent automation or an operator from providing a reply.

REPLY([‘]replytext[‘] [,[‘]replytext[‘]…])

Can appear in any order and on different lines from DELAY() and MSGID(). A null reply can be provided by specifying REPLY(‘ ‘).

replytext is limited to 64 characters. If the reply contains blanks, non-alphanumeric characters, or is not to be folded to uppercase, enclose the reply in single quotes. The single quotes count towards the total of 64 characters. If the reply is too long for the WTOR requestor, the notification message CNZ2608I is issued when the WTOR is issued. Where message CNZ2608I appears depends on the setting of NOTIFYMSGS. It is displayed on consoles receiving routing codes 2 (operator information) or 10 (system programmer information), and also appears in the hardcopy log.

To specify quotes in the reply, specify two contiguous single quotes, like REPLY(‘That”s all folks.’). The reply may contain system symbolics that are resolved when the parmlib member is processed. If you want to have the symbolic resolved when the REPLY command is issued, specify two contiguous ampersands, like REPLY(‘Here is the ‘,‘&&SYSNAME’,’.’). The symbolic must be in uppercase and enclosed in quotes along with the two contiguous ampersands &&.
If the auto-reply policy entry contains a symbolic (like &&name) that is to be resolved when the reply is issued, auto-reply is unable to validate that the reply length would be acceptable by the WTOR issuer. If the reply with the symbolic resolved is longer than what the WTOR issuer expects, when auto-reply processing issues the reply, the REPLY command rejects the reply with:
```
IEE700I REPLY xxxx IGNORED; REPLY TOO LONG FOR REQUESTOR
```
Auto-reply no longer monitors this WTOR, and the response to the D AUTOR,WTORS command (CNZ2604I) indicates that the WTOR has been replied to.
Do not have the reply text span parmlib source lines. Otherwise, the use of symbolics might cause problems. For example, if you specify
```
REPLY(‘system=&SYSNAME.,option1 
,option2’)
```
and &SYSNAME resolves to SY1, the reply text is
```
‘system=SY1,option1     ,option2’
```
To prevent the substitution from causing problems, split the reply text into separate strings. A correct specification is:
```
REPLY(‘system=&SYSNAME.’,             
            ‘,option1,option2’)
```
and the reply text is
```
‘system=SY1,option1,option2’
```
Auto-reply processing can concatenate the strings specified in REPLY. For example, if you specify REPLY('String1'), the quotes are part of the reply 'String1'. If you specify REPLY('String1','String2'), auto-reply processing concatenates the strings and the reply is 'String1String2'. The leading and trailing quotes are part of the reply.
You can also have a mixture of strings. By specifying
```
REPLY(Word1,'String1',Word2,'String2')
```
you will get a reply of
```
WORD1'String1'WORD2'String2'
```
The REPLY command accepts only one quoted string if the first character of the reply is a quote. For example:
```
'This is the reply' but not this
```
The REPLY command will only pass
```
This is the reply
```
to the WTOR issuer. The WTOR issuer does not see
```
but not this
```
Although it is possible that auto-reply can build this type of string, you should be aware that it may not yield the results you wanted.

RATELIMIT(nnn)

nnn is the rate limit value that can be set to indicate (for a specific message ID) the number of replies that can be issued per second. After 1 second has passed, the message count is reset. Only three digits are supported, which gives a limit of 999 replies per second for the specified message ID. The rate value of 001 is the lowest value supported. The default value for rate limit has been set to 020. RATELIMIT is only valid when DELAY is set to 0; otherwise it will be rejected. End of change

Note:

Both DELAY() and REPLY() are required if NOAUTOREPLY is not specified.
Duplicate DELAY() or REPLY() keywords for an MSGID() are rejected and cause the MSGID() specification to be rejected.
Specification of the same message ID in different message definitions results in the first definition being used.