To Rob Berendt's point, I should have added after the BRMS full save, run the STRMNTBRM
command to obtain the recovery reports. 1 item of note on that command is to set the RMVLOGE
parm to *NONE so the DSPLOGBRM is left in tact.
Remove log entries: RMVLOGE
Type . . . . . . . . . . . . . *NONE
From date . . . . . . . . . . *BEGIN
To date . . . . . . . . . . . 90
And
Print recovery reports . . . . . *ALL
We also make it a point to stash the reports on our LAN AND email them to an
Offsite mailbox like gmail or yahoo, etc.
Always good to have a current copy offsite where you can get to it if something happened
Internally.
Very Respectfully,
Michael Mayer
IBM i Support / System Admin.
IT Operations.
The Florida Bar
651 E. Jefferson St
Tallahassee, Florida 32399-2300
mmayer@xxxxxxxxxxxxxx
https://www.floridabar.org
Office: 850.561.5761
Cell: 518.641.8906
Please note: Florida has very broad public records laws. Many written communications to or from The Florida Bar regarding Bar business may be considered public records, which must be made available to anyone upon request. Your e-mail communications may therefore be subject to public disclosure.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of midrange-l-request@xxxxxxxxxxxxxxxxxx
Sent: Wednesday, September 9, 2020 1:00 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: MIDRANGE-L Digest, Vol 19, Issue 1356
Send MIDRANGE-L mailing list submissions to
midrange-l@xxxxxxxxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.midrange.com/mailman/listinfo/midrange-l
or, via email, send a message with subject or body 'help' to
midrange-l-request@xxxxxxxxxxxxxxxxxx
You can reach the person managing the list at
midrange-l-owner@xxxxxxxxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific than "Re: Contents of MIDRANGE-L digest..."
*** NOTE: When replying to this digest message, PLEASE remove all text unrelated to your reply and change the subject line so it is meaningful.
Today's Topics:
1. BRMS Go Save 21 (Mayer, Michael via MIDRANGE-L)
----------------------------------------------------------------------
message: 1
date: Wed, 9 Sep 2020 15:43:34 +0000
from: "Mayer, Michael via MIDRANGE-L" <midrange-l@xxxxxxxxxxxxxxxxxx>
subject: BRMS Go Save 21
The *system group in BRMS is a duplicate of go save 21.
Copy *system group to a control group named brmssave21 (example) - or name it to your shop's standard.
Here's a look at ours:
Display Backup Control Group Entries
Group . . . . . . . . . . : BRMSSAVE21
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Full System Save *SYSTEM.
Weekly Retain Save SWA
Backup List ASP Activity Object While Message Sync
Seq Items Type Device SMTWTFS Detail Active Queue ID
10 *EXIT *DFTACT
20 *EXIT *DFTACT
30 *SAVSYS *DFTACT
40 *IBM *SYSBAS *DFTACT *NO *NO
50 *ALLUSR *SYSBAS *DFTACT *ERR *NO
60 *ALLDLO *DFTACT *NO *NO
70 *LINK *ALLAVL *DFTACT *YES *NO
80 *EXIT *DFTACT
90 *EXIT *DFTACT
F11 on that gives you this and we add those messages into the control group.
Display Backup Control Group Entries
Group . . . . . . . . . . : BRMSSAVE21
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Full System Save *SYSTEM.
Backup
Seq Items Exit command
10 *EXIT
20 *EXIT SNDMSG MSG('** The Full System Save backup is starting **')
30 *SAVSYS
40 *IBM
50 *ALLUSR
60 *ALLDLO
70 *LINK
80 *EXIT SNDMSG MSG('** The Full System Save backup has completed **')
90 *EXIT
Set up a class for it (same name as the control group).
Set up a media policy for it (same name as the control group).
INZ tapes in BRMS via ADDMLMBRM and use the media class name used in the class you set up.
When running it, use the console and the STRBKUBRM command like this:
Control group . . . . . . . . . > BRMSSAVE21
Schedule time . . . . . . . . . > *IMMED
Submit to batch . . . . . . . . > *NO
Omits . . . . . . . . . . . . . > *IGNORE
Here is a go to BRMS website that I use quite frequently:
https://helpsystemswiki.atlassian.net/wiki/spaces/IWT/pages/165642461/Welcome+to+IBM+Backup+Recovery+Media+Services+BRMS+for+i
Very Respectfully,
Michael Mayer
IBM i Support / System Admin.
IT Operations.
The Florida Bar
651 E. Jefferson St
Tallahassee, Florida 32399-2300
mmayer@xxxxxxxxxxxxxx
https://www.floridabar.org
Office: 850.561.5761
Cell: 518.641.8906
1. BRMS - Go Save 21 (K Crawford)
2. Re: BRMS - Go Save 21 (Kevin Bucknum)
3. ldap query of IBM i (Rob Berendt)
4. RE: ldap query of IBM i (Alan Shore via MIDRANGE-L)
----------------------------------------------------------------------
message: 1
date: Wed, 9 Sep 2020 08:31:55 -0500
from: K Crawford <kscx3ksc@xxxxxxxxx>
subject: BRMS - Go Save 21
I know that BRMS can do the equivalent of the Go Save 21.
I have been searching for instructions on how to do it. I have not found anything that I would consider instructions. More like, yep you can do it.
Can anyone point me to some instructions? How to set it up and how to run it.
I have seen things about using BRMS console.
I know the Control Group *SYSTEM would be the group to use.
TIA
--
Kerwin Crawford
------------------------------
________________________________
Please note: Florida has very broad public records laws. Many written communications to or from The Florida Bar regarding Bar business may be considered public records, which must be made available to anyone upon request. Your e-mail communications may therefore be subject to public disclosure.
------------------------------
Subject: Digest Footer
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest 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@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com
------------------------------
End of MIDRANGE-L Digest, Vol 19, Issue 1356
********************************************
midrange.com
