Re: BRMS failure

[Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>]

I've been rebooting it on a daily basis.

It gets an indeterminate distance through the backup job and fails.

Then it's gone until reboot.

On Thu, Sep 28, 2017 at 9:15 AM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

> Jack:
>
> Usually there is another back up job that is in MSGW or held for some
> reason, - or - BRMS maintenance is running at the same time.  Recently it
> seems maintenance is causing issues with record locks and high I/O.
> WRKMLBSTS will help you find the job.
>
> On rare occasions we've had to reboot the tape library to get it to release
> the lock.
>
>
> --
> Jim Oberholtzer
> Agile Technology Architects
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> Jack
> Woehr
> Sent: Thursday, September 28, 2017 8:50 AM
> To: Midrange Systems Technical Discussion
> 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