|
that will probably never be known unfortunately........No two companies have the same hardware components, licensed programs, etc., etc.............It would be almost impossible to know the combinations that causes this............ I think Al hit right on the nose in lack of testing........... In terms of install time: 12 + hours by the time all the PTF's had applied........ Regards, Mike Shaw ----- Original Message ----- From: "jt" <jt@ee.net> To: <midrange-l@midrange.com> Sent: Saturday, December 15, 2001 10:15 AM Subject: RE: V5R1 Lic Pgm install failures > Thanks, Mike...! > > But... aaaaaaaargh...:-( ! > > And then again, I've heard folks say they had few, if any problems...?!? > Right...? > > Is there any way of knowing, in advance, if I have the set up that's gonna > trigger all this ackus-morackas (sp? ;-)... > > I have to have a decent idea how long this is gonna take.. and I doubt if > the time-estimates they give (I'm assuming they give, as haven't looked at > it, yet) are NOT gonna include time for this kinda stuff. > > jt > > | -----Original Message----- > | From: midrange-l-admin@midrange.com > | [mailto:midrange-l-admin@midrange.com]On Behalf Of Mike Shaw > | Sent: Saturday, December 15, 2001 12:56 PM > | To: midrange-l@midrange.com > | Subject: Re: V5R1 Lic Pgm install failures > | > | > | Larry, > | > | I just did a V4R4 to V5R1 on a Model 720 on Thursday. The > | pre-install stuff > | ran fine, but the install failed. I wound up calling the support > | center to > | get it going again.....Wound up having to abort the automatic installation > | and install the licensed program products manually. > | > | >From the call and the install job log, it appears that something happened > | with the install of OS/400 Optional Part 3 (Extended Directory Support). > | >From there, the system hung and nothing happened. > | > | The workaround was to go to manual mode and force the system to do an IPL. > | > | Once IPL'ed to the B side in normal mode, I used Option 11 on the LICPGM > | menu to load all the products that were flagged as *ERROR or *BACKLEVEL. > | Once those were on, I went and got the stuff that was set in the Install > | List so that I had everything. > | > | >From there it was on to the CUME, HIPER Group PTF's, and DB2 Group PTF's. > | > | You are not alone, I know of a 730 that had the same > | problem...........From > | what we concluded looking at the install job log, something happened > | installing Optional Part 3 of OS/400......I have had the same problem with > | installs at V4R5 and V5R1 just as you have. > | > | Keep me in the loop if you get more info. I'll do the same........ > | > | Regards, > | > | Mike Shaw > | > | ----- Original Message ----- > | From: "Larry Bolhuis" <lbolhuis@arbsol.com> > | To: "Midrange Systems Mailing List" <MIDRANGE-L@midrange.com> > | Sent: Friday, December 14, 2001 8:17 PM > | Subject: V5R1 Lic Pgm install failures > | > | > | > Greetings to the highly intelligent Midrange community. > | > > | > The last two V4R5 to V5R1 upgrades that I have done have each failed to > | > install at least a dozen program products. I didn't keep the lists but > | > in each case they were smattered all over from pieces of SS1 all the way > | > to XE1. In each case history log messages indicated the products were > | > not copied from the media. LICPGM Option 5-prepare for install- had > | > successfully located these products. After failing during the initial > | > install the use of option 11-install licensed programs for each of the > | > failed programs successfully loads them no problem. > | > > | > Both of these upgrades were dual processor 820 machines with lots of > | > memory and disk. > | > > | > Nothing in the archives, or on the iSeries pages. > | > > | > Thoughts? Similar experiences? I'm full of ****? > | > > | > Thanks, > | > > | > - Larry. > | > > | > _______________________________________________ > | > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > | list > | > To post a message email: MIDRANGE-L@midrange.com > | > To subscribe, unsubscribe, or change list options, > | > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > | > or email: MIDRANGE-L-request@midrange.com > | > Before posting, please take a moment to review the archives > | > at http://archive.midrange.com/midrange-l. > | > > | > | _______________________________________________ > | This is the Midrange Systems Technical Discussion (MIDRANGE-L) > | mailing list > | To post a message email: MIDRANGE-L@midrange.com > | To subscribe, unsubscribe, or change list options, > | visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > | or email: MIDRANGE-L-request@midrange.com > | Before posting, please take a moment to review the archives > | at http://archive.midrange.com/midrange-l. > | > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.