Re: BRMS CPF5140 Error

Yes, the DSPLOGBRM command can be used to analyze BRMS activity, see my
previous post. The BRMS save process (from what I recall) look much like a
GO SAVE 21. The BRMS restore screens are a little nicer.

You also have standard job logging for the user initiating the backup (in
our case, CONSOLE. Gee, guess where that came from?).

CPI1125 Information 00 05/31/09 02:00:06.228152
QWTPCRJA QSYS 010F *EXT *N
Message . . . . : Job
971594/CONSOLE/WEEKLTOCG submitted.
...
BRM1081 Information 00 05/31/09 02:02:36.747176
Q1ACALG QBRM *STMT Q1ACALG QBRM *STMT
From module . . . . . . . . :
Q1ACALG
From procedure . . . . . . :
Q1ACALG
Statement . . . . . . . . . : 229
To module . . . . . . . . . :
Q1ACALG
To procedure . . . . . . . :
Q1ACALG
Statement . . . . . . . . . : 229
Message . . . . : Starting SAVSYS to
devices TAPMLB04.
Cause . . . . . : The operating
system is being saved using media on devices
TAPMLB04.


--Loyd


On Thu, Jun 4, 2009 at 2:30 PM, <rob@xxxxxxxxx> wrote:

Doesn't BRMS use a joblog or something? If the job is running in batch
underneath QCTL can't you see how it's doing by looking at it's joblog? Or
does BRMS really present pretty screens in which it tells you exactly
which object of which library it's on or some such thing?

I would think that if you used the job in QCTL then your console would
still be free to evaluate "issues".

Since you used the term "one of our programmers" then that infers you have
a "staff". When it comes to backups, normally "operations" trumps
"programming".

Rob Berendt