Re: QJOBMSGQFL System Value

["Neil Palmer" <neilp@xxxxxxxxxxx>]

Agreed.  Usually you DO want the job to crash at that point - or you should
at least investigate jobs that are filling up the job messsage queue to see
WHY they are doing it, and if there's something you can do to reduce/clean
up the messages within the job itself.  Then if you find that "it just logs
lots of messages and there's nothing I can do about it" (or you bought the
package and don't have source) - try changing the JOBMSGQMX & JOBMSGQFL
values on the job description for that job (or if you have source use
CHGJOB to change JOBMSGQFL at start of the job) instead of changing the
system values for all jobs.

Neil Palmer         DPS Data Processing Services Canada Ltd.
                                             AS/400~~~~~
Markham,  Ontario,   Canada    ___________          ___  ~
Phone: (905) 474-4890  x303   |OOOOOOOOOO| ________  o|__||=
Cell.: (416) 565-1682  x303   |__________|_|______|_|______)
Fax:   (905) 474-4898          oo      oo   oo  oo   OOOo=o\
mailto:NeilP@DPSlink.com    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
http://www.DPSlink.com        AS/400  The Ultimate Business Server





Rob Berendt <rob@dekko.com> on 99-08-04 11:44:42

Please respond to MIDRANGE-L@midrange.com

To:   MIDRANGE-L@midrange.com
cc:    (bcc: Neil Palmer/Dpslink)

Subject:  Re: QJOBMSGQFL System Value




Many times I have wanted this.  For example I had a programmer who wanted
to change this value because his job crashed.  When we looked at his joblog
he agreed that crashing was a good thing.  Infinite loop.  There are rare
occasions when this is turned off.  When we install a new version of BPCS
on our 400 is about the only one that comes to mind.

barsa2@ibm.net on 08/04/99 10:07:22 AM
Please respond to MIDRANGE-L@midrange.com@Internet
To:  MIDRANGE-L@midrange.com@Internet
cc:
Fax to:
Subject:  Re: QJOBMSGQFL System Value
At 12:25 PM 8/3/99 -0400, you wrote:
>What can anyone tell me about the QJOBMSGQFL system value.  Ours is set to
>*PRTWRAP.  What do I gain or lose by setting it to *NOWRAP?
*WRAP or *PRTWRAP are the correct settings.  *NOWRAP (the shipped default,
so the system will act [crap out} as it did before this system value was
introduced in V2R3 is a bad setting.
If you have *NOWRAP, when the job message queue fills, the job will
die.  You don't want this.
Al



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---