Critical bug patches raise experts' concern
HP reports its critical patches are GR'ed

Rebooting can be optional on new patches

While we call down the creative thunder of the promised podcast for this week, we decided to update the process to apply the latest HP patches, software the vendor has labelled critical for all HP 3000 customers.

OpenMPE's director Donna Garverick-Hofmeister clarified the need for reboots to apply those Large File fixing patches HP released on Oct. 31. One patch won't need a reboot, she says, while the other needs a reboot but can be staged.

Oh, and the no-reboot patch, to avoid data corruption in very big files, cannot be staged, according to Donna.

The HP 3000 millicode patch (MILNX10A), the first in 16 years, is needed to repair access to any in-house applications that have used Large Files, or do a sort with a temporary file that can exceed 4GB. If your app has not been modified since March 30, 2000, it's safe. That's when HP introduced the Large File feature.

Large Files has been engineering which HP has been trying to remove from customers' 3000s. A November 2006 patch was designed to turn off Large Files and get those files on the system converted to Jumbo files, much better engineered.

Donna says that HP's advice that both patches will require a reboot, and that both can be staged, is not what she understands as a 3000 administrator of several decades.

MILNX10A is NOT stageable because it requires a installation job. in my opinion, this patch is best/fastest/most easily installed by using ‘autopat’.  autopat, at its conclusion, will say ‘stream this.job’....which you do....and a couple of blinks later....milli.lib.sys (and friends) is joyfully updated.

On the other hand, MPENX11A is stageable and is the patch that requires a reboot. this time, use patch/ix to get this patch staged and schedule a reboot.

dig out your notes about how to download patches. pay attention when you run ‘unpackp’ and the rest is all pretty easy.