The Start Message Queue Monitor (STRRSFMSGM) command is used to monitor remote message queues from a central AS/400. This function is often called Remote Console Support because it allows you to forward system console messages from remote machines to a central machine.
Messages forwarded from remote machines are directed to a message queue on the central machine. Answering forwarded inquiry messages on the central machine causes the specified reply to be sent automatically to the originating machine. The prompted version of the STRRSFMSGM command is shown below. Click on the image to see parameter descriptions.
Start Message Queue Monitor (STRRSFMSGM) Type choices, press Enter.
Send or retrieve messages . . . *SND, *RTV From message queue . . . Name
Library . . . *LIBL Name, *CURLIB, *LIBL To message queue . . . Name
Library . . . *LIBL Name, *CURLIB, *LIBL Server ID . . . Name, *CURRENT
Message retrieval delay . . . . 900 Seconds, *NOMAX Disconnect delay . . . 180 Seconds, *NOMAX Severity code filter . . . 0 0-99
Omit message IDs . . . *NONE Name, *NONE + for more values
Header messages . . . *YES *YES, *NO
Job description . . . *USRPRF Name, *USRPRF, *NONE Library . . . Name, *LIBL, *CURLIB
Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys
The parameters for the STRRSFMSGM command are described below.
Send or Retrieve Messages
Specify whether to send messages from your machine to a central AS/400, or whether to retrieve messages from a message queue on a remote machine.
To monitor messages on satellite machines from a central site, there are two strategies you can employ: 1. Have each satellite machine send its messages to the central machine. (Push)
2. Have the central machine periodically poll each remote and retrieve the messages. (Pull)
Each method has its advantages and disadvantages. The Push method makes the most efficient use of communication resources by only contacting the central machine when there are actually messages to be sent. However, the Push method puts the remote machines in control. If an error occurs on a remote that prevents messages from being sent, the central machine will never know it.
The Pull method puts the central machine in control, but wastes communication resources as the central machine polls remotes that infrequently have messages to send. The Pull method also uses greater machine resources on the central AS/400 because one job must be active in batch for each remote being polled.
The possible values are:
*SND: Send messages from your machine to another machine. *RTV: Retrieve messages from a remote machine.
From Message Queue
Enter the qualified name of the message queue to be monitored. If *SND is specified for "Send or Retrieve Messages", this message queue is on the local AS/400. Otherwise, this message queue is on the remote machine. The possible values are:
message queue name: Enter the name of the message queue to be monitored.
*LIBL: Use the library list to locate the message queue. *CURLIB: Find the message queue in the job's current library.
library name: Enter the name of the library containing the message queue. To Message Queue
Enter the qualified name of the message queue to which messages should be sent. If *SND is specified for "Send or Retrieve Messages", the message queue is on the remote AS/400. Otherwise, the message queue is on the local machine.
The possible values are:
message queue name: Enter the name of the message queue to receive the forwarded messages.
The possible library values are:
*LIBL: Use the library list to locate the message queue. *CURLIB: Find the message queue in the job's current library.
library name: Enter the name of the library containing the message queue. Server id
The name of a server directory entry to be referenced. The entry must exist in the server directory on your machine.
Click here for a complete description of this parameter.
Message Retrieval Delay
Specify the number of seconds to wait before looking for more messages.
When *SND is specified for "Send or Retrieve Messages", this parameter indicates the number of seconds to wait before contacting the central machine again to check for replies to outstanding inquiry messages.
When *RTV is specified for "Send or Retrieve Messages", this parameter indicates the number of seconds to wait before contacting the remote machine again to check for new messages.
The possible values are:
900: Check every 15 minutes.
seconds: Enter the number of seconds to wait before checking again. Disconnect Delay
Specify the number of seconds to wait for new messages before ending the connection. For switched connections, this is the number of seconds to wait for new messages before hanging up.
This timer is reset each time a new message to be transmitted is found. The possible values are:
180: Keep the connection active for 3 minutes after transmitting a message to wait for new messages. seconds: Enter the number of seconds to wait for new messages before ending the connection. Severity Code Filter
Specify the lowest severity for messages to be transmitted. Messages are transmitted if the message severity is greater than or equal to the severity filter specified.
The possible values are:
0: All messages are transmitted, regardless of the message severity. 1-99: Enter a severity filter from 1 to 99.
Omit Message IDs
Specify one or more message IDs to omit. Messages with omitted message IDs are not transmitted. You can specify up to 50 values for this parameter. Specifications ending in zeros are treated as generics. For example, OMIT
(MCH0000) would omit all messages beginning with "MCH". The possible single values are:
*NONE: No message IDs are omitted.
The other possible values are:
message-ID: Enter message IDs to omit. Header Messages
Specify whether a header message should be sent with each transmitted message. Header messages are sent to the target message queue immediately preceding each transmitted messages. The first level text for the header message indicates the machine of origin for the transmitted message. The second level text contains information about the sender of the original message.
When header messages are sent, a trailing blank message is also placed in the queue after the message being transmitted.
The possible single values are:
*YES: Header messages are sent. *NO: Header messages are not sent. Job Description
Specify the name of a job description to use to submit the monitor job to batch. The possible values are:
*USRPRF: The monitor job is submitted to batch using the job description from your user profile. *NONE: The request is not submitted to batch. The request is run immediately.
job-description: Enter the name of an existing job description to use to submit the monitor job to batch.
The possible library values are:
*LIBL: Use the library list to locate the job description. *CURLIB: Find the job description in the job's current library.
library name: Enter the name of the library containing the job description. Related Commands:
The following commands are discussed elsewhere in this manual:
Send Message Using RSF (SNDMSGRSF)
For more information about the following commands, prompt the command and press F1 to view the on-line help text:
End Message Queue Monitor (ENDRSFMSGM)
Events
RSF Events can be used to coordinate dependent processes running on one or multiple machines, allowing you to condition the execution of one function on the successful completion of other functions.
Events are logged to a data base file. You can retrieve the status of an event by using the Retrieve Event Attributes
(RTVEVTRSF) command in a CL program. (See the on-line help text for more information.) You can schedule a function to execute when one or more events attain a specific status by using the Wait For Events (WAITEVTRSF) command.