RE: BRMS failure

[Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>]

Rob, that is true with NPIV attached drives.  With SAS attach (direct) we allocate the drive.  


--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Thursday, September 28, 2017 10:55 AM
To: Midrange Systems Technical Discussion
Subject: Re: BRMS failure

My situation may be different as I use a fiber MLB shared between multiple lpars and Power 8's, but this is what I have:

<snip>
WRKCFGSTS *DEV CFGD(*TAP)
Vary off all beginning with TAP.  We use a media library, not a device, and these conflict.

WRKMLBSTS KDVLVTL
Should show:
Device/ 
  Resource     Status                 Allocation 
KDVLVTL        VARIED ON 
  TAP31        OPERATIONAL            UNPROTECTED
  TAP32        OPERATIONAL            UNPROTECTED
  TAP33        OPERATIONAL            UNPROTECTED
  TAP34        OPERATIONAL            UNPROTECTED
  TAP35        OPERATIONAL            UNPROTECTED
  TAP36        OPERATIONAL            UNPROTECTED
  TAP37        OPERATIONAL            UNPROTECTED
  TAP38        OPERATIONAL            UNPROTECTED

If the status of the media library itself (KDVLVTL) is varied off then use option 1 to vary it on.

It’s important that the Allocation of the individual drives be UNPROTECTED.  Unless, that drive is currently being used by some other lpar of IBM i.  If the Allocation is not UNPROTECTED, and if it is not currently in use by some other lpar of IBM i, then use “5=Allocate unprotected” on it.
</snip>


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to:  2505 Dekko Drive
          Garrett, IN 46738
Ship to:  Dock 108
          6928N 400E
          Kendallville, IN 46755
http://www.dekko.com





From:   Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:   09/28/2017 11:34 AM
Subject:        Re: BRMS failure
Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



So if it shows:

TAPMLB01       VARIED ON
  TAP01        OPERATIONAL            ALLOCATED

Should I de-allocate it?

On Thu, Sep 28, 2017 at 8:38 AM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

> Jack,
>
> WRKMLBSTS
>
> You should see all your drives.
> If another process has a drive, it should appear.
>
> Device/
>  Job
>   Resource     Status                 Allocation                name
> TAPMLB01       VARIED ON
>   TAP02        OPERATIONAL            UNPROTECTED
>   TAP01        OPERATIONAL            UNPROTECTED
>   TAP04        OPERATIONAL            UNPROTECTED
>   TAP03        OPERATIONAL            UNPROTECTED
>
> Paul
>
>
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> Steve Pitcher
> Sent: Thursday, September 28, 2017 10:09 AM
> To: Midrange Systems Technical Discussion
> Subject: RE: BRMS failure
>
> Here's a good troubleshooting guide on that.
>
> http://www-01.ibm.com/support/docview.wss?uid=nas8N1020679
>
>
> Steve Pitcher
> iTech Solutions
> Mobile: (902) 301-0810
> http://www.itechsol.com
> http://www.iInTheCloud.com
>
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> Jack Woehr
> Sent: Thursday, September 28, 2017 10:50 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Subject: BRMS failure
>
> Our backups are failing thusly. It makes no sense at all.
> There are tapes.
> There is nothing else accessing the library.
> What's going on? I've tried everything I can think of.
>
> Message ID . . . . . . :   BRM1033       Severity . . . . . . . :
> 99
> Message type . . . . . :
> Inquiry
> Date sent  . . . . . . :   09/28/17      Time sent  . . . . . . :
> 01:54:39
>
>
> Message . . . . :   Devices needed by control group not available. (C
> R)
> Cause . . . . . :   Devices TAPMLB01 in the device list for control
> group
>   type  cannot be allocated because they are being used by other jobs or
> other
>
> systems.
> Recovery  . . . :   Do one of the
> following:
>     -- Type C to cancel control group
> processing.
>     -- Wait for devices to become available, and type R to try the
> operation
>
> again.
> Possible choices for replying to message . . . . . . . . . . . . . . .
> :
>   C -- Cancel
> processing.
>   R -- Try the operation again.
>
>
> --
> Absolute Performance, Inc.
> 12303 Airport Way, Suite 100
> Broomfield, CO 80021
>
> NON-DISCLOSURE NOTICE:  This communication including any and all
> attachments is for the intended recipient(s) only and may contain
> confidential and privileged information.  If you are not the intended
> recipient of this communication, any disclosure, copying further
> distribution or use of this communication is prohibited.  If you 
received
> this communication in error, please contact the sender and 
delete/destroy
> all copies of this communication immediately.
> --
> 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: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
> moment to review the archives at https://archive.midrange.com/midrange-l
.
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD
> --
> 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: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD
> --
> 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: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD