Submitted by Tom Huntington on Wed, 03/21/2012 - 12:00am
Otten, the most common type of server placed next to an IBM i server is a Windows server running Microsoft SQL Server (MS SQL Server). Currently, Robot/SCHEDULE Enterprise can automate an MS SQL Server process, but you have to write your own scripts to monitor the process. Soon, we’ll be releasing a Robot/SCHEDULE Enterprise enhancement to increase its integration with MS SQL Server.
This enhancement adds a function that lets you reference your server and control SSIS packages directly from a Robot/SCHEDULE job.
Submitted by Tom Huntington on Wed, 03/14/2012 - 10:26am
In my last blog, we started discussing the question: “How long will it take to implement automation software?” My definitive answer was: “It depends.” That led to a discussion about the first three steps: Downloading the software; creating automation instructions (rules); and building a task list to keep things organized and prioritized.
What To Automate First?
The next question is, “What type of automation do you implement first?” A good idea is to start with an area that’s easy to automate, and provides fast, early success and positive feedback. Job scheduling and report management are harder to implement—there's just more detail and prerequisite work—than are monitoring and backups. So, I'd say the best place to start is by monitoring messages (QSYSOPR) and system resources. This type of automation is very similar from system to system.
Submitted by Tom Huntington on Wed, 03/07/2012 - 2:00pm
That question is very fresh in my mind after a visit to a local company in the Minneapolis area. I wonder how many times during my 23 years at Help/Systems I’ve heard: “How long will it take to implement this software?” My answer: “It depends.”
Implementation obviously depends on what areas of the IBM i system you are planning to automate and monitor. For instance, are you just interested in monitoring, or do you really want to automate? Do you want to automate job scheduling, backups, or both? How about report management? Monitor the QSYSOPR message queue? What you want to monitor and automate makes a big difference.
Submitted by Tom Huntington on Wed, 02/29/2012 - 12:14pm
This past week, I spent three days in St. Louis, MO visiting customers to learn about their needs and to share the Help/Systems Product Development Roadmap for 2012. Visiting seven customers in three days turned out to make for a busy schedule—I covered more than 250 miles driving from the airport to the hotel, to customer locations, and to dinners (plus a few wrong turns).
The IBM i platform is alive and well in this market. I visited financial and manufacturing companies, a consumer product company, and a service company. Several of these accounts are planning projects involving PowerHA, software replication, security, business intelligence, and automation.
Submitted by Tom Huntington on Wed, 02/22/2012 - 11:22am
About five years ago, IBM announced that Power Servers would support two operating systems—IBM i (i5/OS) and AIX (UNIX)—on the same server. I’m sure this is not news to most of you. What has changed is that IT staffs are mixing operating systems on the same hardware. What are the impacts of this?
Who’s In Charge?
First of all, there’s the political issue of which IT department—AIX or IBM i—is in charge. As it turns out, it really doesn’t matter much because both groups have to know about IBM i and AIX. The real political impact is on the infrastructure group. Yesterday, I had lunch with a group that runs both IBM i and AIX on a new Power 7 Server and they discussed their experiences.