In order to do your omits and still use the character based terminal, create
a list for objects. Specify an entry that would include all the user
libraries, then omit the libraries you don't want using the same wild card
notation. It's not as elegant but it will work and I have done it that way.

Keep in mind that starting at V6 IBM stopped putting any of the real
enhancements into the character based interface, (green screen) all the new
features can only be found in the graphical interface from the *ADMIN
server. Since last December the *ADMIN server is much better and it gets
more improved with each HTTP group PTF that is delivered.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Porterfield, Sean
Sent: Friday, May 09, 2014 3:26 PM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS system save of R&D test LPAR - adding GUI omits

We have 1977 libraries omitted by one entry on our system. Acknowledging
Rob's warning, it's a wonderful feature. It's one of the reasons I went to
the GUI to configure BRMS; I would much prefer to stay on green screen.
Sean Porterfield

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Friday, May 09, 2014 15:02
To: 'Midrange Systems Technical Discussion'
Subject: RE: BRMS system save of R&D test LPAR - adding GUI omits


I also have done the same for some IFS directories.
I did get burned already, omitted some IFS directories that caused some LPP
not to restore completely.
How about on the library side, have you done any there.
The other thing I do is if there are certain libraries that MUST be saved,
but the GUI omit excludes them, I created a list of libraries that must be
I've been told that the specific object type omits that currently have to be
done in GUI omits can now be done with green screen omits in 7.2 I prefer
using green screen when managing BRMS, only reason I use OpsNav with BRMS
is for the GUI omits.

Link to BRMS 7.2 enhancements.!/wiki/IBM%2


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Sent: Friday, May 09, 2014 11:53 AM
To: Midrange Systems Technical Discussion
Subject: Re: BRMS system save of R&D test LPAR - adding GUI omits

I think that wildcards can be dangerous. For example, if I make a library,
QRYROB is that considered *IBM or *ALLUSR?
Now, if someone on your system makes a library that matches one of your
I'm not vehemently opposed. Just something to be aware of.

Rob Berendt

From: "Steinmetz, Paul"
Date: 05/09/2014 10:22 AM
Subject: BRMS system save of R&D test LPAR - adding GUI omits
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

I'm revisiting our BRMS system save for our R&D LPAR.
This LPAR is 12tb, currently 50%.
Current system save is about 6 hours, using multiple LTO5 HH fiber drives.
40% of the 50% is all test data, which really does not need be saved.
If this LPAR had to be restored or reloaded, we would rather have the BMRS
restore/recovery be done quicker without all the test data.
That data can be restored later via a separate process.
Our new thought is to omit all the test libraries in future system saves.
I'm currently reviewing the GUI omit options.
Since most of the test environment libraries begin with the same letters, we
can create wildcard omits as such.
Each of the omits below will omit 22 libraries, 40%, or about 4tb of data.
This will significantly shorten both the system save and recovery, if and
when needed.
Has anyone ever done a similar BRMS config?


Thank You
Paul Steinmetz


This email is confidential, intended only for the named recipient(s) above
and may contain information that is privileged. If you have received this
message in error or are not the named recipient(s), please notify the sender
immediately and delete this email message from your computer as any and all
unauthorized distribution or use of this message is strictly prohibited.
Thank you.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at

Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact