Re: message wrapped error

[rob@xxxxxxxxx]

Generally I leave it at *NOWRAP.  I had one person that said his job 
filled up and wanted me to change it.  That would have been one way of 
handling it.  However we found out that his job had an infinite loop that 
was going nuts.  The *NOWRAP stopped it.  Now, you can override this on 
specific jobs, either through the job description, or through CHGJOB.  And 
if you have a job that is doing something rather intense, like a GO 
RESTORE, option 21, this may make sense.  (Definitely *PRTWRAP, not just 
*WRAP.  If I had used just *WRAP I would have lost too much.)
Another problem is that people often crank up the logging on some jobs to 
log every little thing. Now, it may have made sense when first 
implemented, but perhaps it's time to dial it back down a little. However, 
if you refuse to dial it down, and, you are some perfect programmer and 
know that you'll never get an infinite loop, then this might be the one 
exception to use *WRAP.  If it aborts you'll still get the tail end of the 
job log to analyze.  But I'd change that either through the job 
description, or CHGJOB and leave the system value at *NOWRAP.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/27/2004 10:29 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
Re: message wrapped error







There is a system value, QJOBMSGQMX, the maximum size of a job message
queue, and another QJOBMSGQFL, which is the action that the system takes
when a message queue fills.  The system value QJOBMSGQFL is shipped as
*NOWRAP, which is bad.  I tell people to change it to *WRAP, or *PRTWRAP,
which says print a job log and then wrap.  The action can be changes from
SBMJOB and CHGJOB, the size can only be set at the system value level.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

"i" comes before "p", "x" and "z"
e gads

Our system's had more names than Elizabeth Taylor!

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com
http://www.as400connection.com



 
             "Dwayne Allison" 
             <Dwayne.Allison@a 
             agai.com>                                                  To 

             Sent by:                  "Midrange Systems Technical 
             midrange-l-bounce         Discussion" 
             s@xxxxxxxxxxxx            <midrange-l@xxxxxxxxxxxx> 
                                                                        cc 

 
             09/27/2004 11:12                                      Subject 

             AM                        message wrapped error 
 
 
             Please respond to 
             Midrange Systems 
                 Technical 
                Discussion 
             <midrange-l@midra 
                 nge.com> 
 
 




Good Morning,

We had a job running this weekend and got the following message:


Job message queue for 986884 has been wrapped.


Cause . . . . . : The size of the job message queue for 986884 reached the
maximum size.  The maximum size is defined in the jobmsgqmx value of the
job description used by the job.


The message we are trying to send is." The job has completed".

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.