iNN - eNews - SSS-Software
iNN - eNews - SSS-Software
iNN - eNews - SSS-Software
Erfolgreiche ePaper selbst erstellen
Machen Sie aus Ihren PDF Publikationen ein blätterbares Flipbook mit unserer einzigartigen Google optimierten e-Paper Software.
There’s a whole bunch to tell you on this one, but, we’ll start with first telling you how<br />
to figure out if you’ve got an issue or not. Briefly, for those of you who have never done it,<br />
if you have to "restore the licensed internal code" (otherwise referred to as "slip the LIC"),<br />
you’ve got some anxiety in front of you. It’s simple, it’s well documented, and there’s lots<br />
of help out there to get you through it, but it is cause for worry. If you get into a situation<br />
with your disk drives that require the use of the screens in question, and, they come up<br />
corrupted, you then may be in a situation where you have to slip the LIC before you can trust<br />
what you see on the disk screens. This is not a pleasant position to be in, if you catch my meaning.<br />
To determine where you are, use the command DSPPTF for each of the PTFs above<br />
(MF34369, MF38536, MF38576, MF35091, MF38575 and MF38658, all for 5722999 Licensed<br />
Program Product). If any of them come up with a status of superseded or permanently applied,<br />
you are probably into a slip the LIC situation. You can always contact your next level of support<br />
and get a confirmation.<br />
Instructions on what is involved and steps to perform a restore of the Licensed Internal Code<br />
(which IBM may or may not call a slip of the LIC) can be found in the Backup and Recovery<br />
Guide (SC41-5304-07), Chapter 4.<br />
If you have never done this procedure, or, if you’re the least bit anxious about doing this<br />
procedure, I urge you to seek the guidance of your next level of support for your iSeries or<br />
System i. If you are not experiencing an issue with this at this point, then I suggest you do the<br />
preparatory research, seek the guidance of your next level of support, and be patient. There is no<br />
need for panic in any of this; it’s just a matter of being prepared.<br />
Now for the fun part: I will try to explain how this happened. The defective PTFs were<br />
first made available in Cumulative Group C6101530. At the time they were issued, they were<br />
not known to be defective. They were found to be defective about six weeks later. Many of us<br />
had installed cume 6101 by that time, and, several HIPER PTFs and other group PTFs as well.<br />
IBM posted the note in the install instructions for cume 6101 at that time to omit these PTFs<br />
when putting on cume 6101. So, the only people with issues were those that installed cume<br />
6101 in that six-week period (yours truly and some of my customers), or those who ignored the<br />
installation instructions (yes, people do this). IBM also immediately issued cume C6142530,<br />
which automatically omitted the offending PTFs. So, today, if you have to go with a cumulative<br />
PTF update, do not put on cume 6101, put on cume 6142 instead. If you need to put on 6142,<br />
and you already have 6101 installed, putting on 6142 does not put you in any greater jeopardy.<br />
Also, you might want to be cautious with a PTF called SF99503-530 DB2 UDB for iSeries<br />
Level 10. Level 11 is now available, so go with that instead. Level 10 has issues with defective<br />
PTFs as well.<br />
...more information<br />
The Four Hundred 19.06.2006<br />
www.inn-online.de < Seite > Seite: 32