Robot/CLIENT vs. Robot/SCHEDULE Enterprise—Big Difference!

Even though Robot/SCHEDULE Enterprise has been on the market for two years, I still run into customers using Robot/CLIENT to communicate with non-IBM i servers from Robot/SCHEDULE.

Robot/SCHEDULE Enterprise replaces Robot/CLIENT and offers improved scheduling and activity monitoring on non-IBM i servers. Here are six things it brings to the table:

1. Better security because TCP/IP “conversations” are encrypted.
2. Built-in return code testing that eliminates the need for CL programming.
3. Integration with the Robot/SCHEDULE Explorer graphical interface to manage your job schedule and interact with your remote servers.
4. File, directory, and process (daemons and services) monitoring, plus the ability to trigger reactive jobs.
5. The ability to view UNIX, Linux, or Windows server logs from Robot/SCHEDULE’s Job Completion History display.
6. Agent environments that allow you to define the user name, password, and working directory for jobs across your enterprise.

These are six good reasons to move forward. I know it's not always easy to switch technologies, but you have to trust me when I say that this change really is for the better. More good news—you can make the transition in phases because you can run the agent software for Robot/CLIENT and Robot/SCHEDULE Enterprise on the same server.

Our Sales team can help you with the economics of the switch. Just give them a call and they’ll work you through the details. And, our Support team can provide WebEx demos and help you transition from Robot/CLIENT. We're waiting to help.