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
*****************************************************