|
I'll see if I have a copy around.
Charles
On Tue, Nov 13, 2012 at 11:14 AM, Daniel T. Rowan <danieltrowan@xxxxxxxxx
wrote:
That sounds exactly like what I could use. Are you willing to share thea
source code?
Thanks.
On Tue, Nov 13, 2012 at 10:10 AM, Charles Wilt <charles.wilt@xxxxxxxxx
wrote:
One more thing, I put a command front end on...
So at 5pm Friday, the operator does a
SAVESYSTEM
which display's the standard option 21 UI, and presses enter. There's
afterRESTART parm with *IPL as the default on my SAVESYSTEM command, so
andthe save, the system IPLs.danieltrowan@xxxxxxxxx
HTH,
Charles
On Tue, Nov 13, 2012 at 11:04 AM, Charles Wilt <charles.wilt@xxxxxxxxx
wrote:
On Tue, Nov 13, 2012 at 9:17 AM, Daniel T. Rowan <
dowrote:tired
Second, can this new program be run through WRKJOBSCDE? I am getting
of either staying late on Fridays or getting up early on Saturday to
my
full system saves.Other's have given you the program name(s), you can RTVCLSRC on it
entirethemodify it to your hearts content.QMNSRBND...as
Personally, instead of modifying QMNSAVE I always start with
that's allows me to make use of the standard IBM UI for the save menurestart. On
option 21...along with controlling the ENDSBS...and handling the
a daily basis, you'd just press enter. I leave QMNSAVE alone, so that
actual objects being saved are still the IBM defaults for "save
tosystem".
Note that the standard save menu option 21 allows you to specify up
abut
should24hr delay. So there's no need to stay late or get up early. You
looktake a look at GO SAVE, option 21 and see what IBM provides. Also,
atdata
GO SAVE option 20 - Define save system and user data defaults; keeps
entry during option 21 to a minimum.
In the past, my custom versions have
1) cleanly brought down custom daemon jobs/subsystems
2) started MessengerPlus restricted state monitor
3) Allowed for choosing between standard restart, IPL, or staying
restricted.
4) added an extra 24hr delay. So you could start it Friday at 5pm,
listlistthe save wouldn't happen till 2am Sunday.--
HTH,
Charles
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.
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.
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.