SAV command with OUTPUT(*PRINT) causing a MSGW

Mr. K.V.B.L.

unread,

Nov 1, 2012, 4:22:45 PM11/1/12

to

Can someone tell me the cure for a nightly job that has decided to hang because QSYSPRT has become "full"? All I need is some way to specify NOMAX or change QSYSPRT somehow.

Marc Rauzier

unread,

Nov 1, 2012, 4:55:35 PM11/1/12

to

Mr. K.V.B.L. écrivait dans
news:dd24d04c-ca1b-4110...@googlegroups.com ce qui
suit:

> Can someone tell me the cure for a nightly job that has decided to
> hang because QSYSPRT has become "full"? All I need is some way to
> specify NOMAX or change QSYSPRT somehow.

Try to run OVRPRTF FILE(QSYSPRT) MAXRCD(*NOMAX) (if I remember properly
the command).
This command must be run in the same job as SAV just before it.

Another way is to use INQMSGRPY(*SYSRPYL)for the job running SAV
command and create an entry in the system reply list to answer NOMAX
for the inquiry message CPAxxxx sent to QSYSOPR message queue. You can
customize the reply list entry to apply only to SAV command by setting
up comparison values.

--
Cordialement
Marc Rauzier
(pour me répondre, ne pas utiliser le from mais le reply-to)

Ken Sims

unread,

Nov 1, 2012, 10:48:58 PM11/1/12

to

On Thu, 1 Nov 2012 13:22:45 -0700 (PDT), "Mr. K.V.B.L."
<kenvery...@gmail.com> wrote:

>Can someone tell me the cure for a nightly job that has decided to hang because QSYSPRT has become "full"? All I need is some way to specify NOMAX or change QSYSPRT somehow.

You can use OVRPRTF QSYSPRT MAXRCDS(*NOMAX) to override the default
maximum number of records just while that override is in effect. This
eliminates the need to change QSYSPRT.

--
Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.

CRPence

unread,

Nov 3, 2012, 7:04:13 PM11/3/12

to

There are several means for a "cure", but the following is easy and
typically chosen. Issue a properly scoped override to the printer file
to enable sufficient records for the upcoming SAV OUTPUT(*PRINT)
request, and then [maybe desirable, necessary, or optional to] delete
the override following that save request which generates the spool file
output:

OVRPRTF QSYSPRT MAXRCDS(*NOMAX /* or big# */) OVRSCOPE(as_required)
SAV OUTPUT(*PRINT) /* same as currently coded */
DLTOVR QSYSPRT LVL(accordingly)

An override request could instead specify an alternate printer file
to be opened, where the redirected-to printer file has been created or
changed to enable a sufficiently large number of records to be spooled;
e.g. issue the following command once, and then the OVRPRTF [and a
DLTOVR] at run-time on either side of the request producing the output:

CHGPRTF SysPrtBig MAXRCDS(*NOMAX /* or big nbr */)
/* SysPrtBig PRTF could be duplicated from the QSYSPRT *FILE */

OVRPRTF QSYSPRT TOFILE(SysPrtBig) OVRSCOPE(as_required)
SAV OUTPUT(*PRINT) /* same as currently coded */
DLTOVR QSYSPRT LVL(accordingly)

There is also the chosen INQMSGRPY setting for the job [*DFT or
*SYSRPYL] combined with a message default reply [which could come from
an alternate *MSGF using OVRMSGF, or less desirable, from the specific
message in the specific message file that will be used] or a specified
system reply list reply value which is very simple but not very specific
except when the "Compare value" can be utilized [ADDRPYLE].

Another option, though surely the least desirable [and therefore not
well-described; even if the most flexible since it can be programmed to
respond accordingly], is to use the exit point for inquiry messages.

--
Regards, Chuck