If it doesn't matter if all the files are at a known point, then
quiescing the system isn't necessary-- a SAVLIB SAVACT(*SYSDFN) saves
"Objects in a library... while they are in use by another job. Objects
in a library may reach checkpoints at different times and may not be in
a consistent state in relationship to each other." All objects are
saved, but you may end up with half an order in the order file-- header
records without detail records, for example.
Otherwise, you'll have to examine your system activity and determine
when a 'quiet time' for your application occurs. You can tell all
interactive users to get off the system, and not run any batch jobs
against the library(ies) used by your application, and then do your
save.
If you have PC or Web users, then you need to explore HTTP and WebSphere
and other such applications.
Ending TCP is not a good idea these days-- your system console is most
likely running via TCP (or do you still have Twinax consoles), and
ending TCP may lock yourself out of the system!
Paul E Musselman
IT Technical Support
General Cable Corporation
(859) 572-8030 phone
(859) 760-8030 cell
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Monday, August 23, 2010 11:17 AM
To: Midrange Systems Technical Discussion
Subject: Quiescing the system prior to Save While Active?
For a system running v5r4, are there any recommended ways of Quiescing
the system prior to Save While Active?
I've found some old posts from Ken Graap and other which basically say
the following subsystems:
QINTER, QSPL, QHTTPSVR, QSNADS, QSVCDRCTR, QSERVER and QUSRWRK.
and also end the Mail Server Framework via the ENDMSF command.
I also found and old post from Al Barsa which recommends:
1. Achieve a restricted state. This can be determined programmatically
by executing an ENDSBS command monitoring for a CPF1035 message (isn't
it disgusting that I remembered the CPF message ID?) repeatedly in a
loop (say every 'n' seconds), and then going forward to step #2. Make
sure that you are not in an endless loop by putting a time-out by virtue
of a counted to end at some time, say 30 minutes.
2. Starting a private subsystem, call it QDUMMY.
3. Ending subsystem QSYSWRK *IMMED, because starting by any subsystem
starting to start, in violation to the laws of work management.
4. Submitting a job that:
o clears a private message queue
o submits a job that waits on the SWA quiescence message in that queue o
doing the SWA request specifying that message queue which has a break
program that starts the controlling subsystem (I know that there are a
lot of variables there, but that's life.)
Just wondering if there are any official recommendations, updated lists
of subsystems, or alternatives.
For example, why not ENDTCPSVR *ALL? Instead of ending QSERVER?
Thanks,
Charles
--
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.
midrange.com
