Job Message Queue Full

[kiam]

I have a batch job that ended mysteriously. Looking at the system log, I
found the message "Message queue has been wrapped" a couple of times
before the message "Job ended with end code 0". System value for job
message queue full is WRAP.

Any help appreciated ...

akl.

[Frank Healy]

The messages that you cite are normal messages and really don't indicate
anything bad, although, if you are seeing many of the Wrap messages in a
short span of time your message Job message queue may be too small,
check QJOBMSGQMX system value.

Getting the End Code 0 that means the program(s) behaved as designed and
did not abnormally terminate. You should see more detailed information
for the job in the Job Log. If it was a submitted job you should look
at the QPJOBLOG for this job. Use a WRKSPLF USERNAME to find it or look
in the QEZJOBLOG outq, this is the default outq for job logs. You can
use DSPJOBLOG if the job is run interactively and you are still logged
on to the session that initiated the job.

Regards,

Frank

[Charles R. Pence]

kiam wrote:
>
> I have a batch job that ended mysteriously. Looking at the system log, I
> found the message "Message queue has been wrapped" a couple of times
> before the message "Job ended with end code 0". System value for job
> message queue full is WRAP.

So what's the mystery? Seems the job just completed; ie. ended without errors
when it was done. If you want more joblog data, you could use *PRTWRAP instead
of *WRAP.

Regards, Chuck
All comments provided "as is" with no warranties of any kind whatsoever.

[Chi Ho Suen]

I encountered the same situation as you. The batch job was ended because the
joblog was full and the system therefore killed your batch job.

Don't be fooled by the end code returned, your batch was ended abnormally.
The first thing you can do is increase the QJOBMSGQMX system value to
maximum. This will let your job run longer but does not solve your problem.

You have to check the joblog to see why so many messages were sent to the
joblog. Since I am not a programmer, I can't tell you how to do this. My
experience was the job has error and loop forever, the error messages
generated by the system made the joblog full and system force my job ended.
My situation was the program does not handle error condition correctly so a
fix of the application was needed.

Hope this can help you.

Chi Ho