Re: BRMS - full save with least amount of restricted time

Yes, my QALLUSRLNK matches that.

STRBKUBRM, When I do a full system save in restricted state I use
OMITS(*IGNORE) otherwise I leave that defaulted to *PROCESS. I forget how
QLNKOMT ties in with this but I've got other priorities calling me.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 01/21/2013 01:10 PM
Subject: Re: BRMS - full save with least amount of restricted time
Sent by: midrange-l-bounces@xxxxxxxxxxxx



I found an IBM document that states the QLNKOMT applies to any *LINK type
of save - which, if I read it right, means either *LINK or a named link
list defined by the user. That document is here

http://www-01.ibm.com/support/docview.wss?uid=nas1836337b1bd25f8948625700a004f04a2and

I THINK I'm reading it right.

I also have a link list called QALLUSRLNK that says it was created by
BRMS.
At first I assumed it corresponded to *LINK, but now I don't think it
does. The manual says *LINK "Saves all objects not in /QSYS.LIB and /QDLS
directories". But QALLUSRLNK on my system has this:

List . . . . . . . . . . . . . . > QALLUSRLNK Character value

Objects:
Name . . . . . . . . . . . . . > '/*' Path name
Include or omit . . . . . . . > *INCLUDE *INCLUDE, *OMIT

Name . . . . . . . . . . . . . > '/QSYS.LIB' Path name
Include or omit . . . . . . . > *OMIT *INCLUDE, *OMIT

Name . . . . . . . . . . . . . > '/QDLS' Path name
Include or omit . . . . . . . > *OMIT *INCLUDE, *OMIT

Name . . . . . . . . . . . . . > '/TMP/BRMS' Path name
Include or omit . . . . . . . > *OMIT *INCLUDE, *OMIT

Name . . . . . . . . . . . . . > '/QIBM/ProdData'
Include or omit . . . . . . . > *OMIT *INCLUDE, *OMIT

Name . . . . . . . . . . . . . > '/QOpenSys/QIBM/ProdData'
Include or omit . . . . . . . > *OMIT *INCLUDE, *OMIT
Directory subtree . . . . . . . *ALL *ALL, *DIR, *NONE, *OBJ
Text . . . . . . . . . . . . . . > 'Entry created by BRM configuration'

I do not recall having set this up. Does your QALLUSRLNK look like this?




On Mon, Jan 21, 2013 at 11:41 AM, <rob@xxxxxxxxx> wrote:

An option would be to add some *LINK items to your omit list.
WRKLBRM. A standard one is QLNKOMT. Out of these
/Bytware/StandGuard/AV/logs/avsvr.log (1 object, a log file)
/FAXD01/RCVFAX/00000001.FAX. (1 object)
/QIBM/UserData/HTTPA/admin/logs/error_log.Q113011900 (1 object)
/QIBM/UserData/OS/OSGi (40 objects in this directory or a subdirectory)
/QIBM/UserData/OS400/MGTC (4 objects in this directory or a

subdirectory)

/easy400apc/logs/access_log.Q113011900 (1 object)
/easy400apc/logs/basic_error_log.Q113011900 (1 object)

You could probably safely omit the logs.
/Bytware/StandGuard/AV/logs/avsvr.log (1 object, a log file)
/QIBM/UserData/HTTPA/admin/logs/error_log.Q113011900 (1 object)
/easy400apc/logs/access_log.Q113011900 (1 object)
/easy400apc/logs/basic_error_log.Q113011900 (1 object)
by omitting the directory containing them.
/Bytware/StandGuard/AV/logs
/QIBM/UserData/HTTPA/admin/logs
/easy400apc/logs
Leaving
/FAXD01/RCVFAX/00000001.FAX. (1 object)
/QIBM/UserData/OS/OSGi (40 objects in this directory or a subdirectory)
/QIBM/UserData/OS400/MGTC (4 objects in this directory or a

subdirectory)

Then you can decide on whether or not these can be safely omitted.
WPPMBS before omitting those?
-Would you ever restore one of these individually?
-Are they needed for a full system restore?
-Is there a purge that won't delete these files unless they've been

saved?

On the other hand, is trying to save them while active causing issues?

For

example, if you have a program which receives a fax as a file in RCVFAX
and then runs some process on it and then deletes the file would it

cause

that process to blow if the file is locked for saving during the delete?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 01/21/2013 11:24 AM
Subject: Re: BRMS - full save with least amount of restricted

time

Sent by: midrange-l-bounces@xxxxxxxxxxxx



All,

I tested this BRMS control group on Saturday:

10 *EXIT *DFTACT
20 *EXIT *DFTACT
30 *SAVSYS *DFTACT
40 UPSLIB *SYSBAS *DFTACT *YES *NO
50 QMPGDATA *SYSBAS *DFTACT *YES *NO
60 *EXIT *DFTACT
70 *IBM *DFTACT *YES *LIB
80 *ALLUSR *SYSBAS *DFTACT *YES *LIB
90 *ALLDLO *DFTACT *YES *YES
100 *LINK *ALLAVL *DFTACT *YES *YES
110 ALLSPLF *SPL *DFTACT
120 *EXIT *DFTACT
130 *EXIT *DFTACT

The *EXIT at sequence 60 returns the system to a normal state via CL
program starting the controlling subsystem and waiting on a data queue
entry from the QSTRUP program before proceeding. Everything after that

is

save while active. The entire control group took 90 minutes. The
restricted state portion took about 18 minutes. This is a vast
improvement
over what I'm currently doing, which is everything in restricted state,
which takes about 75 minutes.

*BUT* the *LINK backup had 49 objects not saved because they were in

use.

These were:

/Bytware/StandGuard/AV/logs/avsvr.log (1 object, a log file)
/FAXD01/RCVFAX/00000001.FAX. (1 object)
/QIBM/UserData/HTTPA/admin/logs/error_log.Q113011900 (1 object)
/QIBM/UserData/OS/OSGi (40 objects in this directory or a subdirectory)
/QIBM/UserData/OS400/MGTC (4 objects in this directory or a

subdirectory)

/easy400apc/logs/access_log.Q113011900 (1 object)
/easy400apc/logs/basic_error_log.Q113011900 (1 object)

I have a feeling that trying to figure out a way to do these 49 objects
save while active would/will be an exercise in futility.

If I were to move the *LINK to run before restarting the controlling
subsystem, the rearranged control group would look like this:

10 *EXIT *DFTACT
20 *EXIT *DFTACT
30 *SAVSYS *DFTACT
40 UPSLIB *SYSBAS *DFTACT *YES *NO
50 QMPGDATA *SYSBAS *DFTACT *YES *NO
60 *LINK *ALLAVL *DFTACT *YES *NO
70 *EXIT *DFTACT
80 *IBM *DFTACT *YES *LIB
90 *ALLUSR *SYSBAS *DFTACT *YES *LIB
100 *ALLDLO *DFTACT *YES *YES
110 ALLSPLF *SPL *DFTACT
120 *EXIT *DFTACT
130 *EXIT *DFTACT

Based on the timings for each step, the restricted state portion would
take
an additional 21 minutes, bringing it up to 39 minutes. That's a lot
better than the current 75 minutes, but double the 18 minutes I saw.

If anyone is getting a complete *LINK save while active, I'd love to

hear

about it.

Thanks.


On Fri, Jan 11, 2013 at 11:23 AM, Jeffrey Carey
<Jeffrey.Carey@xxxxxxx>wrote:

We did a full save with minimal down time like so if I recall

correctly:

1) Take the system to restricted state
2) Control group changes startup program to *NONE, does the SAVSYS. We
also had it do LINK and DLO (DLO always gave us a few objects not

saved

if

we didn't do it restricted) and I think *IBM.
3) Control group starts a subsystem, submits job to monitor for SWA

sync

and kicks off SWA of ALLUSR
4) The MONSWA program would wait for the SWA sync point (which was

pretty

quick since the system was still very close to restricted) and kick

off

the

startup program and change the QSYSSTRUPGM back to what it should be.

It's been a while since we did that (previous shop), but it worked

pretty

well (especially since it replaced GO SAVE 21!)







Jeff Carey, MSIT, MBA
Sr. Systems Administrator



This communication, including any attachments, may contain information
that is confidential and may be privileged and exempt from disclosure

under

applicable law. It is intended solely for the use of the individual or
entity to which it is addressed. If you are not the intended

recipient,

you

are hereby notified that any use, disclosure, dissemination, or

copying

of

this communication is strictly prohibited. If you have received this
communication in error, please notify the sender. Thank you for your
cooperation.
--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.