Hi David -
Please do the Cume before the HIPERS.
Although the Cume instructions say to set MF35829 and MF36653 to apply
delayed and IPL to the B side, you are in the middle of a restore and
you will already be on the A side, so you should be able to use APYPTF
LICPGM(MFxxxxx) DELAYED(*IMMDLY). Then you should apply the Cume (the
current one is OK, I'd use C6080520.) Then IPL to the B side, wait for
INZSYS to complete and install the HIPERS, DB and other groups.
If you have an 8 GB load source the drive size is not the problem.
Regards,
Scott Ingvaldson
System i Administrator
GuideOne Mutual Insurance Company
-----Original Message-----
From: David C. Shea [mailto:dshea@xxxxxxxxxxxx]
Sent: Tuesday, September 11, 2007 9:59 PM
To: Midrange Systems Technical Discussion
Subject: RE: Link Loader Failure and B600 0901 after v5r2 cume install
So a 'big bang' isn't a good idea...
I did this in v4r5... took a scratched model 150 (now _there_ is a small
box...), loaded vanilla v4r5 and the final cume/groups and it was OK.
I agree that 2004 to 2007 is a lotta new stuff.
I'm in the middle of the scratch full restore now (my DR practice
run...).
When it's done, I'll test the 'smaller bites' approach:
1. The 2004 PTFs are already 'perm'. I'll install the two ptfs
that are required before the install of the rest and reboot. I survived
this last time.
2. I'll install the hipers and reboot. Although - the CUME CDs
come with the cume and the hipers and the DB ptfs all on one set of
CDs... Can I parse them out? I think it's all one happy PTF Package
now. If I can't parse them out, I'll do the cume/hiper/db package and
reboot.
3. If I survive to here, I'll do the groups. But - I essentially
ALL the groups on one set of CDs (so it's one big package). What's the
consensus - is this a bad approach? Plus, I ordered _all_ the PTF
groups, including, I'm sure, some for stuff that I don't have, like one
of the 17 flavors of Websphere...
RSTLIB *NONSYS chugging along... Woo-hoo!
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S. Waterbury
Sent: Tuesday, September 11, 2007 8:52 PM
To: Midrange Systems Technical Discussion
Subject: Re: Link Loader Failure and B600 0901 after v5r2 cume install
Hi, David:
It is my understanding that a Link-Loader failure can occur when
applying many, many PTFs, and especially when many of the MFxxxxx PTFs
must be linked into the "nucleus" of the system ...
From your description, it sounds like you jumped from a PTF dated Nov.
2004, all the way up to the last, latest PTF package and group PTFs for
V5R2. Perhaps it was just "too much"...
You might try this approach ...
First, apply all of the previous PTFs as "Perm".
Next, apply only the HIPER PTFs from the latest CUMe package. Then,
re-IPL.
Then, apply all of the non-HIPER PTFs. Then re-IPL.
Then, one by one, apply the various group PTFs.
You get the idea?
The idea is not to try to apply too many PTFs all in one go.
HTH,
Mark S. Waterbury
David C. Shea wrote:
I have a small 170 (a 2289 - a P05...). It's one of my development
boxes, running v5r2 until one of the drives died. Bought a
replacement
drive, did a scratch install of v5r2 (always good practice once in a
while... :) .
Applied the latest cume and groups I had laying around, dated Nov
2004.
Good as new. I took a full system backup, bootable tape.
I then ordered the latest cume (it arrived yesterday) and groups for
v5r2. I loaded them just like always - groups/hipers/cume. When
rebooting to apply them (B side), the dreaded yellow light came on.
B6000901. Now, I can boot to the A side but not the B side. The
history log says the 'link loader' failed. Then one of the LIC ptfs
fails to apply (MF30209), but I think that's caused by the link loader
thing, not the ptf itself. I tried removing MF30209, but that won't
work. I tried removing all the PTFs for 5722999 but that won't work.
I
tried rebuilding the LIC from DST, but got the complaint about the
link
loader not being happy.
Good thing I took that backup.
I am currently booting to the D side (the tape). I'll scratch the
disks
and do a full restore from tape (more useful practice... good thing
it's
a dev box).
From what I googled about 'link loader failure' it may be that my
load
source disk (6713, 8GB) ran out of space. I did load and apply a
couple
PTFs before starting the Big PTF Install (5722999 mf35829 and
mf36653).
MF36653 relates to the link loader... It's a HIPER... and it's in the
cume. Something about compaction.
MF35829 is also related to the link loader. It's in the cume, and it's
a
hiper. Something about compaction.
I found that MF35829 has a related PTF - MF41170 - that fixes a
problem
with MF35829... MF35829 is in the cume. MF41170 is not in the cume
but
is in the hipers. Something about compaction.
I'm seeing a pattern here...
I am posting this here for the next poor guy that ends up in my shoes,
so that he has something more to GOOGLE....
But - does anyone have any comments on this? I have never had a cume
PTF croak the box like this... I think I'll restore to the tape I
have
and just leave it there... put a big skull and crossbones on the new
cume... wait for the final v5r2 collection...
Thanks in advance for any thoughts...
****************************************************
Go...FASTER! Without an Upgrade!
ARCTOOLS/400(tm) and ReorgWizard(tm)
www.arctools.com
DCSoftware,Inc.
Ph: 508.435.8243 x200
Fax:508.435.4498
Current versions: ARCTOOLS v7.1.1, ReorgWizard v3.1.5, JDE Module v3,
BPCS Module v1
*****************************************************
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
-----------------------------------------
DISCLAIMER:
This message and accompanying documents are covered by the
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, and
contains information intended for the specified individual(s) only.
This information is confidential. If you are not the intended
recipient or an agent responsible for delivering it to the intended
recipient, you are hereby notified that you have received this
document in error and that any review, dissemination, copying, or
the taking of any action based on the contents of this information
is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail, and delete the
original message.
midrange.com
