Re: RCLSTG on IPL?

On 23-Nov-2013 16:56 -0800, David Gibbs wrote:

On 11/22/2013 3:03 PM, CRPence wrote:

The [better IMO] option exists, to use the dedicated-batch
[restricted-state batch] feature of End Subsystem; i.e. the Batch
Time Limit (BCHTIMLMT) to have the request run for an allotted
amount of time.

Well, I had high hopes for this technique ... but it's not working as
I hoped.

I created a program that would, theoretically, take the system to
restricted state (using the BCHTIMLMT parameter) and then run a
reclaim.

The program runs, but when it tries to run the reclaim, it fails with
a CPD0031 "Command RCLSTG not allowed in this setting".

I even tried invoking RCLSTG via a call to QCMDEXC, but it didn't
like that either.

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]. Anything for which its processing can be performed in
batch [as noted, that since includes the Reclaim Storage
command], and for which the timing [length of time required to
complete] is either predictable or for which its termination
before that required length of time is either innocuous or
easily-recovered, that processing can be performed using the
Batch Time Limit (BCHTIMLMT) feature of the End Subsystems
(ENDSBS).

As such, it is recommended that the Reclaim request should
*not* include the *DBXREF portion, unless sufficient recovery
time is allowed to complete a separate RCLSTG SELECT(*DBXREF)
afterward; in case the RCLSTG was not able to complete in the
time allotted. The reclaim of the Database Cross-Reference
information is sensitive to cancellation whereas the request to
RCLSTG SELECT(*ALL) OMIT(*DBXREF) is designed to allow
interruption without negative consequences.

While a Google web search on just RCLSTG CPD0031 did not locate a link, adding it.comp.as400 to the web search did reveal _a_ link to the thread; that the link was not found without that, is just more evidence of the[ir] misdeed with regard to that USENET group:
http://it.comp.as400.narkive.com/JKUcmJwm/savsys