More Y2K compliant — like more pregnant?

August 1998

Click here for Technical Directions sponsor message

More Y2K compliant — like more pregnant?
HP noted that PowerPatch 5 for MPE/iX 5.5 includes software that makes the 3000 more Year 2000 compliant. You may recall that the 3000’s operating system and hardware became Y2K compliant in late ’97, right? Well, yes and no, apparently. It speaks to the issue of the complexity in determining Year 2000 compliance, which suggests that getting a testing tool you trust is a pretty good idea.

See, HP didn’t have a company-wide conformance policy for Year 2000 in late ’97 when it first came out with PowerPatch 4. That meant that a handful of 3000 compiler tools, Allbase/SQL and the Architected Interfaces need patching to comply with the new company-wide conformance policy. Given the new functionality in PowerPatch 5 — MDX for big shops, and support for the new 929s for smaller shops — it seems like a good idea to take the patch just to be safe. The 3000 products patched for Y2K in PowerPatch 5 include HP’s Date Intrinsics, so it seems kind of vital to us. PP5 also includes Perf Collector/iX patches for Year 2000 fixes. DCE/3000 also gets a patch, but it’s not part of the PowerPatch, distributed separately as usual. You need to call the Response Center to get the following products patched for Y2K, since PP5 doesn’t carry the fixes: SNA/IMF/XL, RPG/iX and RPG/V, System Dictionary Cobol Definition Extractor, Dictionary/V, System dictionary/iX, Allbase/BRW and BRW Desk/iX. Link Editor/iX gets its Y2K fix in MPE/iX 6.0, expected to ship in October. HP has a table with patch IDs for that last group of products at the CSY Jazz Web site, under the MPE/iX Year 2000 Information section.
Copyright 1998 The 3000 NewsWire. All rights reserved




		Click here for Technical Directions sponsor message
		More Y2K compliant — like more pregnant? HP noted that PowerPatch 5 for MPE/iX 5.5 includes software that makes the 3000 more Year 2000 compliant. You may recall that the 3000’s operating system and hardware became Y2K compliant in late ’97, right? Well, yes and no, apparently. It speaks to the issue of the complexity in determining Year 2000 compliance, which suggests that getting a testing tool you trust is a pretty good idea. See, HP didn’t have a company-wide conformance policy for Year 2000 in late ’97 when it first came out with PowerPatch 4. That meant that a handful of 3000 compiler tools, Allbase/SQL and the Architected Interfaces need patching to comply with the new company-wide conformance policy. Given the new functionality in PowerPatch 5 — MDX for big shops, and support for the new 929s for smaller shops — it seems like a good idea to take the patch just to be safe. The 3000 products patched for Y2K in PowerPatch 5 include HP’s Date Intrinsics, so it seems kind of vital to us. PP5 also includes Perf Collector/iX patches for Year 2000 fixes. DCE/3000 also gets a patch, but it’s not part of the PowerPatch, distributed separately as usual. You need to call the Response Center to get the following products patched for Y2K, since PP5 doesn’t carry the fixes: SNA/IMF/XL, RPG/iX and RPG/V, System Dictionary Cobol Definition Extractor, Dictionary/V, System dictionary/iX, Allbase/BRW and BRW Desk/iX. Link Editor/iX gets its Y2K fix in MPE/iX 6.0, expected to ship in October. HP has a table with patch IDs for that last group of products at the CSY Jazz Web site, under the MPE/iX Year 2000 Information section. Copyright 1998 The 3000 NewsWire. All rights reserved