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



I couldn't say 100% but I'd say very likely not. My thinking is that QCTL
is already in a started state when QSTRUP runs so the system isn't
technically in a restricted state.

I'd suggest writing a short CL that would be run as QSECOFR or equivalent.
The CL would do an ENDSBS *ALL *IMMED (do controlled ends in front of this
as needed) to get to a restricted state, wait a few minutes for everything
to end or add monitor code to look for the "system ended to restricted
state" message, do the RCLSTG *DBXREF, then either IPL or STRSBS QCTL.

Then SBMJOB SCDTIME(23:30) JOBQ(QCTL) to run it at 11:30 PM (or pick another
date/time that works for the client).

That turns it into a one-time event (no editing QSTRUP at all) and in the
future you can modify the CL for a full reclaim or to do other
restricted-state processing or other general processing like PTF application
before an IPL.

On Wed, Jul 29, 2009 at 9:55 AM, Mark S. Waterbury <mark.s.waterbury@xxxxxxx
wrote:

Hi, everyone:

A client of ours has a small model 170 running V5R2 ... it uses a
genunie IBM twinax console (so we cannot access the console for that
system remotely, e.g. when it is running in 'restricted state').

Recently, they saw some error messages indicating that they need to do a
RCLRSC *DBXREF ...

Can we automate this by adding some code to their QSTRUP *PGM to invoke
the RCLRSC *DBXREF before it starts up any subsystems, so that, the next
time they IPL, this will happen automatically?

Thanks,

Mark S. Waterbury
--
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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.