MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » April 2014

Re: Unattended backup



fixed

"Calling GO SAVE 21" (or the underlying program) won't work because this
option is designed to be run interactively.
It fails if submitted to batch as it can't output any screens.
There is some re-engineering required to make this viable.




On Wed, Apr 2, 2014 at 11:06 AM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>wrote:

We schedule BRMS system saves using AJS.
I see no reason why you couldn't use the base job scheduler and call the
GO SAVE 21.
Something else we do is we have another job scheduled, SYSRESTRIC, just
prior to the scheduled system save.
The jobs basically ends all subsystems, results in the system being in a
restricted state.
When system save starts, it immediately starts the save, subsystems
already end.
I've seen in the past that the system save gets hung up trying to end
jobs, subsystems, etc.

Paul

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Horn, Jim
Sent: Tuesday, April 01, 2014 5:54 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Unattended backup

We did this too. Later we created a jobscde to check that the backup job
was running (in case she forget or if she had the day off).

Jim

----------------------------

message: 3
date: Tue, 1 Apr 2014 16:18:44 -0500
from: "Paul Nelson" <nelsonp@xxxxxxxxxxxxx>
subject: RE: Unattended backup

I second this. I wrote a version of this called WEEKLY, where the
operator could type that command at the console on Friday afternoon,
and the program would sit and wait until the shift change on Sunday
afternoon.

The shop was a warehouse that supplies food to restaurants and
delicatessens, and Sunday afternoon was the only window for downtime.
The work week for the warehouse guys started at 7 PM on Sunday.



--


***********************************************************************
The information transmitted is intended solely for the individual or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or other use
of or taking action in reliance upon this information by persons or
entities other than the intended recipient is prohibited.
If you have received this email in error please contact the sender and
delete the material from any computer. As a recipient of this email, you
are responsible for screening its contents and the contents of any
attachments for the presence of viruses. No liability is accepted for any
damages caused by any virus transmitted by this email.

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









Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact