Robot/CLIENT is the first step in creating a tight-knit, effective operations automation team. A Robot/CLIENT-managed server runs more smoothly, more reliably, and with fewer operational crises. And, it reduces the need for off-shift operators.
Robot/CLIENT helps you coordinate your iSeries with your Windows, NT, and UNIX servers. Robot/CLIENT can monitor Windows or NT applications and services on your server, even if they weren't started by Robot/CLIENT. Use Robot/CLIENT to check the server and return a status at specified intervals. If your business depends on your Web server, mail server, and print server, Robot/CLIENT brings you peace of mind. Robot/CLIENT also can run as a service on your Windows and NT systems, so it's always available to run tasks, even before a user signs on.
Two-way event communication builds team players
Robot/CLIENT accomplishes the key two-way communication you need for automation. Its easy-to-use interface lets you initiate tasks from your iSeries programs on your attached servers. It notifies you (or the program) whether or not the task completed successfully and in the time you specified. Because your programs get feedback on the tasks they send, you can readily integrate your client procedures and OS/400 procedures.
It allows Windows systems to receive tasks from multiple iSeries systems. Users can register a single Windows PC client to multiple iSeries systems and rotate among them using the Robot/CLIENT task processor and a rotation list.
The easy to use Rotation feature allows users to indicate which iSeries will be included in a rotation process, the length of the rotation interval on each iSeries, as well as how Robot/CLIENT should handle active or pending tasks at the end of a rotation interval. During the rotation process, Robot/CLIENT connects to each iSeries in the list, communicates and performs tasks, and disconnects at the end of the rotation interval, automatically. The process even uses an improved method of error recovery to recover from communication errors automatically.
This feature is especially beneficial for high availability (HA) environments or in data centers where multiple iSeries systems must send tasks to Windows systems. By setting different length rotation intervals for different iSeries systems, users can give higher priority to the systems that send the most tasks.
Robot/CLIENT commands and APIs enable your iSeries programs or users to initiate tasks and communicate with the client or server:
- Transfer files between your iSeries and non-iSeries systems--automatically.
- Send a Windows or UNIX task to execute.
- Send Robot/SCHEDULE reserved command variable values to communicate with your Windows tasks.
- Send a status request to a client to determine if it is ready to receive a task.
- Check the status of a critical NT service.
Robot/CLIENT also brings the concept of a job queue to servers and other client systems. If the client can't execute a task immediately, the tasks are queued and executed in the order they were received--automatically, with no human intervention. Users can manage the task queue themselves.
Robot/CLIENT provides APIs that allow your servers to communicate with other Robot products. With Robot/CLIENT, your client or server tasks can:
- Send pager or e-mail messages using Robot/ALERT.
- Send messages to a Robot/CONSOLE message center.
- Send status messages to the Robot/NETWORK Status Center.
- Send a job completion status to Robot/ SCHEDULE to start a reactive job.
- Send a message to any message queue on the iSeries.