Select a Product
Select the product you have a question about from the following menu.
This is system setup option. Here's how to change it:
The "Successfully Sent" message in the transmission log indicates that Robot/ALERT established communications with your paging vendor's modem and the paging vendor received the message from Robot/ALERT. So if the log says the message was successfully sent, the problem may be with your paging vendor. The most likely causes are that the vendor had a problem of some sort at the time or you were out of range.
The problem is not with your pager or with Robot/ALERT. Message length is determined by your paging vendor. Different vendors support different maximum message lengths. Contact your paging vendor for details.
RBAHS is Robot/ALERT's message history file. This file should be purged periodically to prevent problems and keep the product cleaned up. For many users, once a month is a good schedule for this task. You can set up a Robot/SCHEDULE job to purge the file on a regular basis. You can also purge the file from the History Menu. A third option is change the file to remove the maximum number of records restriction (*NOMAX). There is a Help/FACTS that explains how to delete history.
Emergency mode is a process that temporarily suspends processing of a message set. It prevents Robot/CONSOLE from putting your system into an infinite loop.
It's easy.
No carrier can mean several things.
No phone line connection to the local modem.
To fix, startby checking all your cable connections. If all connections seem okay, check the number you've told Robot/ALERT to dial. Is this number correct? Does it have a leading 9 or 1, if needed? If that all seems okay, try connecting an telephone handset to the modem phone line. Is there a dial tone? Can you dial out to the paging vendor? Does the vendor's modem answer? If all that seems normal, you may need to contact your phone company.
The paging vendor's modem is not answering.
Call your paging vendor and verify the number Robot/ALERT should dial. Don't forget to adjust the dialing sequence if a leading 9 or 1 is needed.
The number that the modem is dialing is answered by a voice rather than a modem tone.
Call your paging vendor and ask for the TAP modem phone number. Change the number Robot/ALERT is dialing to this number.
FAIL-P means the message or pager ID has been rejected. Check that the pager ID is setup correctly in the Pager Directory. If it is, you may need to contact your pager vendor to activate the pager ID. Also check that the vendor is set up correctly.
Another possibility is that you have an equipment mismatch. The vendor may be trying to send an alphanumeric page to a numeric-only pager or vice versa. Vendors usually have separate phone numbers to use for alpha and numeric pagers. Make sure Robot/ALERT is dialing the alpha modem to send an alpha page. (Or, the numeric modem to send a numeric page.)
Emergency mode is activated when Robot/CONSOLE receives 15 identical messages in 10 seconds (default values). When this happens, Robot/CONSOLE turns on emergency mode. Robot/CONSOLE turns off emergency mode when the same message is not received for 30 seconds.
There is something about how your have the paging vendor set up that is not working. Write down the baud rate, data bits, stop bits, and parity bits information and verify this information with your paging vendor.
You can use the IBM 7852-400 modem with Robot/ALERT and IBM’s Electronic Customer Support without switching the modem from SYNCHRONOUS to ASYNCHRONOUS modes (the modem is set up in SYNCHRONOUS mode). You must have an existing Robot/ALERT modem-type communication job and you must know the name of this communication job’s line description. For more detailed instructions, download the Help/FACTS that discusses this topic.
No. Upgrade the host system first and the node systems as your maintenance schedule allows. Statuses from the nodes will continue to be reported to the host even though the host and node systems are running different versions. However, packets cannot be sent between systems on different versions.
Robot/NETWORK works with Tivoli the same way it works with other enterprise management systems -- by sending SNMP traps to it. We have a Help/FACTS document with more details, How Robot/NETWORK supports SNMP traps.
The purpose of Robot/NETWORK is to link Help/Systems products on multiple systems or multiple partitions of the same system. There is no point in having Robot/NETWORK without having at least one other Robot product.
As long as you are not using the product on any system in your network, you can delete the library.