|
-----Original Message-----DST
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Loyd Goodbar
Sent: Thursday, June 04, 2009 4:34 PM
To: Midrange Systems Technical Discussion
Subject: Re: BRMS CPF5140 Error
I should be more specific. One cannot directly monitor a batch job running
in the controlling subsystem when it has ended. Even the console goes
offline for the duration of the backup. The BRMS log and job log are
available after the fact. This is why it's very important to set an
appropriate value for the restricted state end time. If the system is
totally locked I think one can force DST from the front panel, there are
options to force the restricted state batch job to end. I've only had todo
that once so don't have specifics.sufficient
And just to reiterate, the console is *not* available during the backup.
So no, the developer can't monitor the backup *whle it's running* but (for
example) once tested on a couple of small libraries, it should be
to go for the whole system.Or
--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?
listdoes 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".
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.