RE: BRMS objs not saved issue

Hi Jerry

I built an omit list (omitting things is my preferred approach to saves of
any type). Also, I set the job up so it would continue if there were errors
to avoid having the job end if an object was locked and couldn't be saved so
you may want to explore that as well if the site policy permits it. This
also avoids holding up anything else waiting on the save to complete and
preventing big backlogs in the replication software.

As far as building the omit list, it's not that tedious. IIRC The IFS stuff
can be handled at the directory level, even if it can't, it doesn't take too
long to get all the objects in there. If you miss a couple you get woken up
and you add them in and pretty soon you've got them all.

The things I like about this is that the BRMS save shows as completed
normally - which prevents operators from getting the "that always ends with
an error" and not checking it properly and also that if you get some other
object not saved because it is locked you are alerted to it - a good thing
in my opinion.

You can also omit libraries from the *ALLUSR save in BRMS - theres an option
to maintain lists somewhere and one of the lists is libraries to be omitted
from saves; you just need to be careful to make sure they are saved when
doing a full system save. I think there's a parameter in either the BRMS
save command or the control group that says whether to use the omit list or
not. Maybe this approach will work better for you.

Regards
Evan Harris


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Draper
Sent: Saturday, 11 April 2009 4:57 a.m.
To: Midrange Systems Technical Discussion
Subject: BRMS objs not saved issue

We have a BRMS group that does an *ALLUSR but invariably there are some
objects that are locked and there are some objects on the IFS in QIBM
that are also locked (eclipse and univ conn). Thus these are not saved.

We reviewed the job log and are not concerned about any of these
particular QSYS or IFS objects. The total number of QSYS objs is 15 and
they are data areas related to Robot.

The general job stream running out of Robot Schedule is:

1. end a bunch of jobs, services, and subsystems to eliminate locks
2. run the BRMS Daily group with *ALLUSR
3. start the jobs, services, and subsystems we ended in 1 above

Options:

A. Make a CL for the BRMS Daily job and monitor for msg BRM10A1. This
is ok but there is no automatic transparency of objects not saved unless
we write a script to parse the joblog looking for objects not saved.

B. Mess with the omit objects feature in BRMS to specifically exclude
the objects we know are locked. Problem is that this is somewhat
tedious and if we miss something then the job fails at 2am and the pager
goes off (I like to sleep at night).

C. Use a custom *LIST in BRMS to save all the necessary libraries
instead of *ALLUSR. Naw. Don't want to go there. I like the *ALLUSR
sweep to get everything including any new libs a pgmr added the other
day without us really knowing about it.

How are others handling this? Ideas?

Jerry