CCSS Outlines ‘Disk Danger Zones’ for IBM i Servers
November 16, 2010 Alex Woodie
Disk is a different creature on the IBM i platform than it is with other platforms. For starters, it’s not called disk. It’s called direct access storage device, or DASD. That bizarre name should be the first clue that failure to adhere to best practices can be a very expensive proposition. Luckily, IBM i systems management vendor CCSS recently published a handy guide called “Disk Danger Zones” that identifies the five most expensive DASD-related mistakes you shouldn’t make with your IBM i server.
The nature of DASD on the IBM i platform requires administrators to pay close attention to all warning signs. When problems do crop up, they sometimes have symptoms that might seem unrelated. However, administrators can’t ignore these symptoms without putting the entire system in jeopardy. Often, the quickest and easiest solution may be to buy more DASD, and while that may be cheaper than in the old days, it can still be a more expensive option than arming oneself with the appropriate information.
That is the goal of CCSS’ “Disk Danger Zones” guide: to inform operators and administrators and to help them from making mistakes that result in unnecessary purchase of DASD, or worse–the collapse of an IBM i environment due to runaway DASD.
CCSS pegs the five biggest threats to good DASD housekeeping as: journal receivers; temporary storage; Auxiliary Storage Pools (ASPs); “important” files; and looping jobs. To see how each of these areas affects DASD, download the four-page guide, which is available at www.ccssltd.com/resources/best-practice.php.
In addition to discussing common causes of DASD problems, CCSS’ guide provides some advice on how to avoid the situations. CCSS, which develops software that monitors DASD (among many other IBM i server attributes), says it developed the list as a result of experiences with customers.
Ray Wright, president and CEO of the U.K. company, says the new guide is a reflection of his company’s desire to seek new communication channels and to share its experience and expertise with the IBM i community.” It’s an important part of driving the development in our field of performance and message monitoring and being an active participant as the industry continually evolves,” he says.