Teach Robot/CONSOLE and Robot/ALERT how to handle messages

If you are a new user of Robot/CONSOLE and Robot/ALERT, you may be wondering how to get started. After you’ve installed the products, what’s next?

Typically, new users want to start by creating a Robot/CONSOLE message center to monitor the QSYSOPR message queue. To do this, we recommend you use Robot/GUIDE, the automated setup option. (Refer to the Robot/CONSOLE Getting Started manual for complete information on using Robot/GUIDE.)

Robot/GUIDE creates two operator message centers for the QSYSOPR message queue, creates message sets for messages to be suppressed or messages that can be answered with the same reply every time, and allows you to set up log and resource monitoring. You can have Robot/CONSOLE handling your messages and monitoring your system logs and resources in minutes.

Note: If you didn’t run the RBCCRTMFD command during installation, you must run it before starting Robot/GUIDE. This command creates the message file definitions Robot/CONSOLE needs to create message sets. Robot/GUIDE requires the same security authorities as those used to install Robot/CONSOLE.

For Robot/ALERT, the first thing you must decide is how you will be sending notifications from the System i—by modem or by using TCP/IP. If you plan to use a modem, you need specific information about setting up the modem from your cell phone or pager service provider. If you plan to use TCP/IP, you need to know the domain name and IP address of the e-mail server you will use to send messages to the e-mail address associated with your pager or cell phone. (Refer to the Robot/ALERT 5.0 User Guide’s TCP/IP Paging Services questionnaire for more information.)

After you set up Robot/ALERT and send and receive a test message, go back to the QSYSOPR message center and tell Robot/CONSOLE to notify you of response-required messages. Robot/CONSOLE can notify you via a pop-up window on a System i session (if you are logged on). Or, you can associate a Robot/ALERT device (pager, cell phone, or other e-mail address) with your message center and receive unanswered messages via Robot/ALERT. You can specify how long Robot/CONSOLE should wait to notify you. This allows you to track QSYSOPR messages without being tied to a monitor.

If you are using Robot/ALERT, it is a good idea to have it page you for all response-required messages initially. This allows you to note the message IDs you want to handle differently. Then, create message sets for those message IDs. In addition, if an unexpected critical message comes through, you won’t miss it!

Using the Most Common Messages report
Robot/CONSOLE also provides another useful tool, The Most Common Messages Report. Use this report to identify which messages occur most frequently on any message queue that you monitor. To analyze the report:

• Look for messages that can be answered the same way each time and create a message set to accomplish this.
• Look for messages that don’t require immediate attention. Create a message set to redirect these messages to a message center that doesn’t notify you, or send messages using Robot/ALERT.
• Look for messages that require a response, but aren’t urgent. Create a message table for these. Then, create a new message center. You could set up this message center to use Robot/ALERT to send messages to an e-mail address that is monitored periodically. Finally, create a message set, selecting Message Table for the message set type. Press function key 10 until the OPerator Assistance Language panel displays. Specify the operation REDIRECT and enter the new message center in the Operation Values field to complete the setup.

Populating message tables automatically
Robot/CONSOLE can help you populate your message tables.

1. Display the Message Table Elements panel and press function key 6 (Add Query).
2. Enter a search term.
3. Robot/CONSOLE will populate the table with all the message IDs that contain your search term.

Review this list and add or delete message IDs to tailor it for your environment. For example, use this approach to create a table of all printer messages.

If you don’t want to see certain messages, use Robot/CONSOLE to suppress them. If you ran Robot/GUIDE, you already have a message set and message table called MSTSUPPRES. This table contains message IDs for informational messages that users typically do not need to see. Once you are satisfied that this table contains the message IDs you want to suppress, activate the MSTSUPPRES message set.

Setting up two-way messaging
If your want to answer messages from your pager, cell phone, PDA, or another e-mail address that can send a reply to the e-mail from Robot/ALERT, set up Robot/ALERT for two-way messaging. You need a POP3 mail account on your e-mail server (or on another e-mail server, such as one at your ISP). You also need to know the POP3 server’s domain name and IP address, and information about the POP3 account: login ID, password, and e-mail address.

Go to the Robot/ALERT Directory menu and select Option 1 (Vendor Maintenance Menu). On the Vendor Maintenance Menu, select Option 1. Create your vendor using Robot/GUIDE. On the Robot/GUIDE Automated Vendor Setup panels, make sure you:

1. Give your vendor a unique name. (Don’t delete existing vendors or your devices will be deleted.)
2. Select TCP/IP (1) for Connection Type.
3. Select two-way (2) for Service Type.
4. Select SMTPPOP3.
5. Enter the information for the outbound e-mail server
6. Enter the information for the inbound server.
7. After the vendor is created, enter a 1 to create a device.

Verify that you can send a message and receive a response. Then, you can begin using this new device on your Robot/CONSOLE message centers. When you respond to a message, Robot/ALERT recognizes the reply in the POP3 account and gives it to Robot/CONSOLE. You’ve answered the message without having to dial in!

Contributed by Theresa Aleckson, Technical Consultant

This entry was posted on Wednesday, April 25th, 2007 at 9:38 am and is filed under Robot/ALERT, Robot/CONSOLE. You can follow any responses to this entry through the RSS 2.0 feed. Responses are currently closed, but you can trackback from your own site.