Two questions, one on the AOM Command Prefix and the other on the AOM Message Suppression Character.
- The AOM Command Prefix, when the term 'command sending is from the System Console', what does this actually mean? Does it mean the MVS System console, the SOLVE:Operations Automation r11.0 console, the OCS panel or SDSF ? Commands can be sent from all these locations. If "yes" to all of these places, does the Prefix need to be in front of the command? If "not all of these places", then which ones?
ANSWER - The AOM SSI Command Prefix String specifies the prefix to use when sending commands to the SOLVE:Operations Automation r11.0 Region interface from the MVS System Console, and will appear in front of the command.
In SOLVE:Operations Automation v5.0 the AOM SSI Command Prefix was a character.
In SOLVE:Operations Automation r11.0 the AOM SSI Command Prefix can be a string or a character.
- Is it possible to leave the AOM Message Suppression Character (default is '/' (slash)) as a blank and how can this be done ?
- A reason for this may be that the AOM Message Suppression Character causes conflict with another Application.
ANSWER - The AOM Message Suppression Character is 'tagged' onto the front of messages suppressed by AOM in the System Log. This character can't be a blank. If it is, you will get error message:
RMINWI01 AOM Msg suppression character is required.
The following are valid 'tag' character:
@ # , . / & + - ? < | ! ; % _ > ? : ?
The '/' (slash) character is not displayed with messages on the MVS System Console, but after processing by SOLVE:Operations Automation r11.0, this character is visible in SDSF.
So, to resolve this problem posed in this question, either:
- If an Application has coded in it that ignores messages 'tagged' with the '/' (slash) character, select another character to use as the AOM Message Suppression Character having no impact on the Application.
- Specify the Application ahead of SOLVE:Operations Automation r11.0 in the MVS member IEFSSNxx so that the Application has priority and gets access to the messages first.
- Use the primary automation tool, whether SOLVE:Operations Automation r11.0 or another Application, to suppress these messages.