June 21, 2002 Timothy Prickett Morgan
I have several clients that still run RPG II
code in the S/36EE and the code runs fine.
I don’t believe in conversion for conversion
sake. [See the article, “One Way to Ease Conversion of RPG II Programs,” Midrange Guru, OS/400 Edition, April 5, 2002.] When an old program needs more than minor modification, I’ll convert it to RPG IV (first to RPG III, then to RPG IV). Sometimes the code is ugly, but I clean it up and add new and improved logic. I’ve read a lot of your stuff, so I know you’re an RPG II guy like me. Just my two cents on conversion.
Take the guesswork out of iSeries DASD Management with disk/HUNTER
Why wait until your system slows down or stops because a run-away query eats up your disk space?
Many application and database problems can lead to disk spikes, including:
Once installed and configured, disk/HUNTER runs continuously in the background on your AS/400 iSeries, and “wakes up” at intervals that you specify. Every time disk/HUNTER wakes up, it will measure the amount of free space remaining within specified ASPs or all ASPs.
When the amount of free space decreases by a user-specified percentage or by a user-specified amount (in megabytes or gigabytes), disk/HUNTER will go to work, generating messages and reports pointing to the origination of the spike.
The combination of detection and diagnostic capabilities within disk/HUNTER provides a powerful element of control to iSeries shops that experience high levels of activity and that also need to be proactive in managing storage.
To really see how disk/HUNTER can be both an insurance policy and a time-saver in your shop, click here to download a demo or order a no-charge 30-day support-assisted trial evaluation.