×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
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.