Re: CPI2417 - job message queue wrapped

Tom,

I didn't catch the thread on this a few weeks ago, but:

All messages go to the job message queue, but only some of the messages go to
the job log, if any, as you have observed.

I usually tell folks to think of the job message queue like you would a data
queue.  The program that creates the job log, if any job log is to be created,
filters what it receives from the queue.

Unlike data queues, job message queues have the ability to wrap instead of
having runaway growth or job termination when full.

The message queue exists as long as the job does (like a data queue in qtemp)
and the job log persists after the job, like a spool file.

I've never tried this, but if you change the logging level of an active job,
does the job log magically change to reflect the messages it previously
filtered?  Maybe not when displayed, but when spooled at job end?

If not, it would make more sense to me if job message queues behaved more like
data queues in that the message is deleted upon receipt by the message
filter/job log creation process.

hth

thomas@inorbit.com wrote:
>
<<snip>>
>
> I've never seen a decent, clear explanation of the full difference between 
>"joblog" and "job message queue" (or "external job message queue"?), but 
>clearly differences exist as you see. A discussion in this list a few weeks 
>ago didn't manage to clarify much.
>