×
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 checked the docs and see v7r1 shows the command has ALLOW(*ALL),
whereas the v6r1 shows only ALLOW(*INTERACT *IPGM *IREXX *EXEC) such
that the RCLSTG is allowed only in an /interactive/ environment in that
older release. But of course there are *no change indicators* in the
7.1 docs :-(
AFaIK there should be no harm in just changing the command(s) named
RCLSTG in an earlier release, as I noted in my earlier reply. While I
recall the RCLSTG may have been updated to present a progress panel, it
must be optional, i.e. no 5250 device required, because I had never had
any difficulty performing batch reclaim tests in the lab. But be sure
to implement that Change Command request as part of the System Change
Management; at least for your current release. Of course even if the
change gets applied on newer releases, such a change would just be
redundant; i.e. if the changed 7.1 doc can be trusted.
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/cl/rclstg.htm
_Reclaim Storage_ (RCLSTG)
"Where allowed to run: All environments (*ALL) ..."
http://pic.dhe.ibm.com/infocenter/iseries/v6r1m0/topic/cl/rclstg.htm
_Reclaim Storage_ (RCLSTG)
"Where allowed to run: Interactive environments (*INTERACT *IPGM *IREXX
*EXEC) ..."
Regards, Chuck
On 24-Nov-2013 09:01 -0800, CRPence wrote:
Not sure what release is being used, but the docs I recall reviewing
[would've been v7r1 InfoCenter] showed the Allowed-to-run in
environments listed as *ALL. If DSPCMD of the RCLSTG being issued
does not show every value for the "Where allowed to run" [i.e. *IMOD
*BMOD *IREXX *BREXX *BPGM *IPGM *EXEC *INTERACT *BATCH], then you
will want to issue the following:
CHGCMD RCLSTG ALLOW(*ALL) /* library-qualify as appropriate */
I wrote recently on it.comp.as400 [which Google underhandedly,
effectively obliterated] in response to an inquiry about using the
BCHTIMLMT, but apparently I was wrong about v5r3 for the change:
On 18-Nov-2013 10:57 -0800, CRPence wrote:
On 18-Nov-2013 09:36 -0800, Franco Lombardo wrote:
<<SNIP>> <ed: translated:> Do you know if the same thing can
be used for RCLSTG?
Since v5r3 I believe... when the command was changed to
ALLOW(*ALL) to avoid CPD0031 [or a warning on compile per
CPD0772]. <<SNIP>>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.