Re: Monitoring for BRM1429 not working

On Feb 15, 2019, at 3:58 PM, Steinmetz, Paul via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Jim,

LPAR B job goes to MSGW, the MONMSG for BRM1429 not working.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Friday, February 15, 2019 4:57 PM
To: Midrange Systems Technical Discussion
Subject: Re: Monitoring for BRM1429 not working

Seems to me you just resolved the issue, if that tape is being used BRMS won't allow it to be used elsewhere.

Jim Oberholtzer
Agile Technology Architects

On Feb 15, 2019, at 3:25 PM, Steinmetz, Paul via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Rob,

I have the BRMS networking feature.
Running all the processes you mentioned.

The issue here is that volume X is still in use by LPAR A (nightly save) ran longer than normal.
LPAR B has a RSTLIBBRM that needs volume X. (not yet available, in use by LPAR A.


Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Friday, February 15, 2019 4:19 PM
To: Midrange Systems Technical Discussion
Subject: RE: Monitoring for BRM1429 not working

Get the BRMS networking feature.
Install it properly.
Run the required maintenance functions. Have daily job schedule entries like
STRMNTBRM RMVMEDI(*REUSE)
PRTEXPMED(*NO)
PRTVSNRPT(*NO)
PRTBKUACT(*NO)
PRTRCYRPT(*RCYANL *SAVEXCP)
STRMNTBRM RGZBRMDB(*YES)
Make sure you balance your BRMS media with STRBALBRM ACTION(*SET) to give a "reserve" for each lpar.
Make sure you balance regularly after you've set your reserves with STRBALBRM ACTION(*BALANCE)
Maybe check it with STRBALBRM ACTION(*REPORT)
Then if you're still having this issue contact us and/or IBM.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Friday, February 15, 2019 4:01 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: Monitoring for BRM1429 not working

I have an automated process that uses a BRMS volume.
If the volume is still being used on a different LPAR, I get BRM1429.
Volume sets not available on devices TAPMLB01.(C G)

I tried monitoring for the BRM1429, adding a delay, but the MONMSG was ignored.
What am I missing with the BRM1429.

RETRY: RSTLIBBRM SAVLIB(TEST) DEV(TAPMLB01) +

MONMSG MSGID(CPF412F CPF3794 CPF4528 CPF0000 +
BRM1429) EXEC(GOTO CMDLBL(DELAY)) /* +
delay job for 5 minutes */

DELAY: DLYJOB DLY(300)
GOTO CMDLBL(RETRY)

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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: https://amazon.midrange.com