CUM PTF apply

0 pts.
Tags:
AS/400
Database
The last two times I applied a CUM, the IPL did not complete because of false hardware errors. I was told by IBM that the microcode must have "gotten confused". I had to manual IPL from the B side which worked fine, then reIPL unattended to actually get the PTFs to apply. There was never any hardwarre problems nor were any errors logged. My question - should I be pursuing this further with IBM or could it really just be confused microcode? Thanks, Pat
ASKED: October 4, 2005  1:54 PM
UPDATED: November 14, 2009  9:44 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

I’ve seen this at times while I was working for a DR firm. Sometimes it would take 3 scratch installs of our microcode to finally get the system back to itself. I discovered that objects were being changed on the system by the customer’s developers that were directly affected by microcode (modifying items in the Qlibs were found to be reponsible) So yes, to answer your question, the microcode could have been “whacked” and probably it now is not an issue. Monitor closely for a while (at least till the next month end).Just as a recommendation you might want to A) test ptfs on a development box first then impliment when they are found to be stable and b) wait to impliment ptfs until they have been tested by others in the field (6 months was the old rule of thumb) C) read up on what the Ptfs could affect besides the product or code you are trying to fix(Read the APARS)Finally verify that the sysem really has no hardware issues. (WRKPRB or STRSST and checked for failed or non-reporting hardware would be the places to start)
Good Luck,

MJ

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • JohnDavid
    The reply you received seems to be from an ex Microsoft employee. Jokes aside, I had something similar some time ago and performed a SLIP install of the LIC and OpSys then applied all my PTFs (CUM and Groups) and the problem disappeared. A SLIP install is like an upgrade from one release to another but merely replaces what is installed. Same procedure a an automatic install.
    5 pointsBadges:
    report
  • Jbharvell
    You could have PTFs that need to be installed before the CUMe. I am getting ready to install the latest CUMe for V5R3. After reading the PSP information I found that there are 3 PTFs that are recommended to be installed before I try to install a CUMe. One PTF I have in hand right now sounds like it fixes your problem. I always make sure I review the Hardware LIC, and the Defective PTF PSP reports. Any problems that have been reported are listed there.
    0 pointsBadges:
    report
  • TomLiotta
    Modifying programs in "Qlibs" shouldn't touch microcode. But it could mess with the OS, though that should result in obvious errors. In any case, the combination of "false hardware errors" and "never any hardwarre problems nor were any errors logged" doesn't make a lot of sense. How were "false hardware errors" determined with no errors logged? I'd guess that wouldn't be much to follow up with if there is nothing logged to follow up. I'd mark it down to missing an instruction somewhere along the line and simply write it off. I'd make sure that all my PTF actions are taken care of and that I was in a generally stable position and go from there. Run DSPPTF to an outfile. Run a query to see if any actions are still outstanding. Clear up any that exist. Check the problem and handle any problem. Apply whatever individual PTFs are called out. Run for a week at least to establish a clean baseline. Then apply the cume with strict attention to detail. Make sure all history and job logs are kept. Call IBM at the first clear sign of trouble that has no obvious cause. Do not go forward with any unplanned manual IPLs if any MCHxxxx errors or other conditions indicate hardware in any way. If you don't have 24/7 support, call the hardware support number and let them decide if they'll handle it. If they say it's software and you might get stuck with an extra-cost support issue that you don't feel comfortable with, make the decision at that time. I'd want to err on the side of caution and hold any actions until I could go forward with support on the line. First, support can help confidence. You do as directed and responsibility goes to IBM. But second, it's an opportunity for conversation and asking questions. Lots of knowledge can come at those times. Don't hesitate to dig for info -- it's paid for. Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following