Re: noob ASP question

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Hi Jack

The IFS directory is always there - I think varying on makes the 
QSYS.LIB part of it usable in the usual expected way. Hadn't thought of 
this before, but that seems right.

There is also some DB initialization taking place during the vary on.

Vern

On 3/3/2015 7:21 PM, Jack Tucky wrote:
> So what's the deal with the IFS directory?  When the iAsp is varied off it goes away?
>
> Customer says the consulting firm is going to implement powerHa.  I'm learning Mimix maintenance at another customer.  It will be interesting to see the differences.
>
> Thanks again.  Jack
>
>
>
> > On Mar 3, 2015, at 9:33 AM, Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx> wrote:
> >
> > Call in a PMR.  You're in danger of losing things, although I think it's a
> > simple fix.
> >
> > --
> > Jim Oberholtzer
> > Chief Technical Architect
> > Agile Technology Architects
> >
> >
> > -----Original Message-----
> > From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack
> > Tucky
> > Sent: Tuesday, March 03, 2015 9:27 AM
> > To: Midrange Systems Technical Discussion
> > Subject: Re: noob ASP question
> >
> > We're getting this error when trying to vary off the iASP
> >
> > Message ID . . . . . . :   CPDB414       Severity . . . . . . . :   30
> >
> > Message type . . . . . :   Diagnostic
> >
> > Date sent  . . . . . . :   03/03/15      Time sent  . . . . . . :
> > 07:53:28
> >
> >
> > Message . . . . :   File system failure. Independent ASP may not be usable.
> >
> > Cause . . . . . :   Integrated file system failure occurred.  Independent
> >
> >   Auxiliary Storage Pool (ASP) may not be usable.  The reason code is 6
> >     6.  Unable to remove the independent ASP directory.
> >
> >
> > We have manually created our LANSA directory under the iASP already.
> >
> > Vary on doesn't show any messges.  Something is weird.  I've suggested we
> > remove the directories I created for LANSA and try vary off and on but
> > that's not being accepted yet.
> >
> > Jack
> >
> > > On Tue, Mar 3, 2015 at 9:25 AM, Jack Tucky <jacktucky@xxxxxxxxx> wrote:
> > >
> > > What process creates those directories?  RSTLIB to the iASP?  We tried
> > > vary off and on.  Customer is on with IBM tech support.
> > >
> > > Jack
> > >
> > > > On Mon, Mar 2, 2015 at 11:51 PM, Jack Tucky <jacktucky@xxxxxxxxx> wrote:
> > > >
> > > > It's an IASP.  And they aren't .  Again they were in the test box so
> > > > I figured I need them.
> > > >
> > > > Thanks for confirming.
> > > >
> > > >
> > > >
> > > > > On Mar 2, 2015, at 10:38 PM, DrFranken <midrange@xxxxxxxxxxxx> wrote:
> > > > >
> > > > > Do you have an ASP or an iASP?
> > > > >
> > > > > If you built a standard ASp you won't have any of that. If you
> > > > > built an
> > > > iASP then those directories get created automatically and better be
> > there.
> > > > > Also if you built it for IFS only (ASP Type UDFS) then it won't
> > > > > have
> > > > those directories. It needs to be built as ASP Type *PRIMARY.
> > > > > If the ASP number is 2-32 it's a traditional ASP.
> > > > >
> > > > >        - Larry "DrFranken" Bolhuis
> > > > >
> > > > > www.frankeni.com
> > > > > www.iDevCloud.com
> > > > > www.iInTheCloud.com
> > > > >
> > > > > > On 3/2/2015 8:24 PM, Jack Tucky wrote:
> > > > > >
> > > > > > I was involved configuring LANSA in an independent ASP on a test
> > > > system.
> > > > > > Everything finally went OK.
> > > > > >
> > > > > > I wasn't involved creating the ASP on either test or production.
> > > > > >
> > > > > > I'm replicating my steps on production, but I've noticed on the
> > > > production
> > > > > > machine the IFS directory for my iASP is missing QIBM, QSR and
> > > > QSYS.LIB.
> > > > > > The support people that created the ASP will be in tomorrow.
> > > > > > Until
> > > > then,
> > > > > > anyone have an idea how those directories get created?
> > > > > >
> > > > > > Thanks, Jack
> > > > > --
> > > > > 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.
> > --
> > 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.
> >
> >
> > --
> > 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.