ADSM-L

Re: does using HSM under ADSM make it impossible to do mksys

1997-04-18 14:13:57
Subject: Re: does using HSM under ADSM make it impossible to do mksys
From: Susan McClure <smcclure AT IS.RICE DOT EDU>
Date: Fri, 18 Apr 1997 13:13:57 -0500
On Apr 18, 12:41pm, Matt Anglin wrote:
> Subject: Re: does using HSM under ADSM make it impossible to do mksys
> Classification:
> Prologue: From the desk of  Matt Anglin, ADSM Development
> Epilogue:
>
> A week or so ago, I suggested that the people having mksysb problems
remove the
> "nodename = -" parameter from the failing HSM file systems in
> /etc/filesystems.  Has anyone tried that yet, and does it fix the
problem?
>
> Matt Anglin
> ADSM Development

Matt
I haven't tried your nodename=  in the /etc/filesystems

BUT  I have been working these last couple weeks with IBM L2 in the
mksysb group.  I have pmr 28071/branch 004 open.
Basically, they sent me a newer version of the /usr/sbin/mkinsttape
file which is called
by the mksysb process.  The one they sent is from level 4.2, with some
apar applied to it
and I used it on my AIX 4.1.4 system.   I ran a mksysb with it and it
all worked normally-
that is no error messages about mounting the hsm filesystems under
/ethan.
They just called yesterday and said they successfully ipl'd and
restored my mksysb
tape.  Now they want me to send a copy of the bosinst.data file for
them to check a
few things.   If everything looks OK and they determine this is in fact
a valid mksysb
tape..... they will use my pmr to have the apar from 4.2 sysrouted back
to the 4.1.4 level.

(ps I can't create another mksysb tape right now and send the
bosinst.data file-- my 8mm
has frozen up- so it might be a couple days)

Bottom line.... looks like there is a problem for hsm users at the
4.1.4 level.
Once the apar is retro fitted back to 4.1.4, I am going to post the new
apar number
to the group.

Susan McClure
Rice University
<Prev in Thread] Current Thread [Next in Thread>