Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion SAV command with OUTPUT(*PRINT) causing a MSGW

Received: by 10.66.90.36 with SMTP id bt4mr13471106pab.5.1351803335558;
        Thu, 01 Nov 2012 13:55:35 -0700 (PDT)
Path: s9ni74599pbb.0!nntp.google.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nx01.iad01.newshosting.com!newshosting.com!87.79.20.101.MISMATCH!newsreader4.netcologne.de!news.netcologne.de!weretis.net!feeder1.news.weretis.net!usenet.pasdenom.info!dedibox.gegeweb.org!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder1-1.proxad.net!cleanfeed1-b.proxad.net!nnrp5-1.free.fr!not-for-mail
Newsgroups: comp.sys.ibm.as400.misc
Subject: Re: SAV command with OUTPUT(*PRINT) causing a MSGW
From: Marc Rauzier <marc.vers.d...@free.fr>
References: <dd24d04c-ca1b-4110-8cae-bdc99e564ff3@googlegroups.com>
Organization: En mon nom propre (et encore ...)
Message-ID: <XnsA0FEDF0CFFCF9MarcoDiMarco@127.0.0.1>
User-Agent: Xnews/2006.08.24 Mime-proxy/2.3.c.1 (Win32)
Mime-Version: 1.0
X-Face: "-N^"6b9mk=2BiQ`{w;~yIOs4YGU.;L6H=^kCcBw&v7*KW'TnZ@aIQ"zl(c)K)ikMV@,nYh=Uytwvk~#QOR?#eSxO5\GVHT]%C9164qR@njK\:vARJYQXXzNISW4cCCne>C.W}YK:11#~'PATsVNY|v3F.7<-B>{22hR<=GB|:H4NS.FQ[|0f$F?wLz~p_#C^eKu^6mlx`CR?<3#N|VM^K#rR5`a
Reply-To: marc.rauz...@laposte.net
Date: 01 Nov 2012 20:55:35 GMT
Lines: 22
NNTP-Posting-Date: 01 Nov 2012 21:55:35 CET
NNTP-Posting-Host: 82.228.94.71
X-Trace: 1351803335 news-1.free.fr 6486 82.228.94.71:53042
X-Complaints-To: abuse@proxad.net
X-Received-Bytes: 2120
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Mr. K.V.B.L. écrivait dans
news:dd24d04c-ca1b-4110-8cae-bdc99e564ff3@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)