Re: BRMS objs not saved issue

I did the "read the joblog to get the objects not saved and write to a history file" and ignore objects in the 2 libs (you may have more))
and send msg if ok or not.

Jim Franz

DSPJOBLOG OUTPUT(*OUTFILE) OUTFILE(QGPL/ZDSPJOBLOG) +
OUTMBR(*FIRST *REPLACE)
CALL PGM(JOBLOG1) PARM(&LOG1)

c* pardon the old code..
c* for every file not saved - write hist
c if qmhmid = 'CPF3741'
c 'QUSRSYS' scan qmhmdt 10
c N10'QMPGDATA' scan qmhmdt 10
c if *in10 = *off
c eval svstart = QMHTIM
c eval errors = errors + 1
c eval log1 = 'N'
c eval sverror = %subst(qmhmdt:18:10) +
c ' ' + %subst(qmhmdt:1:10) + ' Not Saved'
c write @savehist
c endif
c endif
c* for every save error (lib not fully saved) write hist
c if qmhmid = 'CPC3771'
c 'QUSRSYS' scan qmhmdt 10
c N10'QMPGDATA' scan qmhmdt 10
c if *in10 = *off
c eval svstart = QMHTIM
c eval errors = errors + 1
c eval log1 = 'N'
c eval sverror = %subst(qmhmdt:11:10) +
c ' Not Fully Saved'
c write @savehist
c endif
c endif
----- Original Message ----- From: "Jerry Draper" <midrangel@xxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, April 10, 2009 12:56 PM
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

--
Jerome Draper, Trilobyte Software Systems, since 1976
iSeries, Network, and Connectivity Specialists -- iSeries, LAN/WAN/VPN
Representing WinTronix, Synapse, Netopia, HiT, and others .....
(415) 457-3431; www.trilosoft.com

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