× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. February 2019

RE: Monitoring for BRM1429 not working

BRM1429 is an "inquiry" message, thus MONMSG cannot monitor.
However, I did find BRM1429 has a default reply of "C".

This doesn't explain why the system handled the BRM1429 differently on two occasions.

Occasion 1) Job went to MSGW, waiting for a response for message at QSYSOPR.
Occasion 2) Job continued, BRM1429 was auto answered with a "C".

Paul



-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Bruce Vining
Sent: Saturday, February 16, 2019 11:51 AM
To: Midrange Systems Technical Discussion
Subject: Re: Monitoring for BRM1429 not working

From the MONMSG help text for MSGID:

Specifies the message identifiers of one or more *escape, *
*notify, or status messages* that are to be monitored by
this command. As many as 50 specific or generic message
identifiers can be specified on one command.

On Sat, Feb 16, 2019 at 10:47 AM Steinmetz, Paul via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Jim,

< BRM1429 is not a monitorable error
How do you know if a message cannot be monitored?

I had the error this morning, "something" in the system "auto-answered"
the message with a "C"
Where and what could that be?

Also, it appears my MONMSG did pick up the CPF412F- Cartridge 001387 not
available.

Cartridge 001387 not available.
Volume sets not available on devices TAPMLB01.(C G)
Volume sets not available on devices TAPMLB01.(C G)
C

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf
Of Jim Oberholtzer
Sent: Saturday, February 16, 2019 10:51 AM
To: Midrange Systems Technical Discussion
Subject: Re: Monitoring for BRM1429 not working

That would be because BRM1429 is not a monitorable error. It will never
get picked up by MONMSG.

Jim Oberholtzer
Agile Technology Architects



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
--
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




As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.