× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: CPF2526 - Job message queue for "Job #"/"User"/"Job Name" can not be extended. Job ended.
  • From: "Cotes, Steven" <cotess@xxxxxxxxxxx>
  • Date: Fri, 23 Jan 1998 11:35:31 -0800

Chuck,
definitely change QJOBMSGQFL to *WRAP or *PRTWRAP.
Leaving it *NOWRAP leaves you open to exactly the problem
you had.
I prefer *WRAP, if you _really_ need to keep the messages then
use *PRTWRAP.

 - my .02,
 -Steve Cotes
 -cotess@data-io.com


> ----------
> From:         Chuck Lewis[SMTP:clewis@iquest.net]
> Sent:         Friday, January 23, 1998 10:27 AM
> To:   Midrange List
> Subject:      CPF2526 - Job message queue for "Job #"/"User"/"Job
> Name" can not be extended. Job ended.
> 
> Hello All,
> 
> We have users of third software that occasionally come up with the
> error
> message
> 
> CPF2526 - Job message queue for "Job #"/"User"/"Job Name" can not be
> extended. Job ended.  and the job they were running is terminated.
> (This
> message at the end of a 5,816 job log...)
> 
> From what I understand, what is causing this is "excessive" logging of
> CL commands.
> 
> I know there are several systems value's are involved with this:
> 
> 
> Current                 Shipped
>      Name
> Description
> value                     value
> 
> QJOBMSGQFL    (Job message queue full action)
> *NOWRAP            *NOWRAP
> QJOBMSGQMX   (Maximum size of job message queue)
> 64                                16
> QJOBMSGQSZ    (Job message queue initial size)
> 16                                16
> QJOBMSGQTL    (Job message queue maximum initial size)
> 24                                24
> 
> 
> The only one we have changed from the shipped value is QJOBMSGQMX.
> 
> There are also JOBMSGQMX and JOBMSGQFL associatted with the JOBD but I
> don't really want to start "tailoring" things like that if there is a
> good/safe "global" way to do this (i.e. via the system values...)
> 
> My question - is there any danger in changing QJOBMSGQFL to *WRAP
> (i.e.
> looping jobs, etc) or is it OK to do this ?
> 
> 
> 
> Thanks in advance !
> 
> --
> Chuck
> 
> 
>     _/_/_/_/   _/      _/   _/      _/   _/_/_/_/   _/      _/
>    _/            _/      _/   _/      _/   _/            _/    _/
>   _/            _/_/_/_/   _/      _/   _/            _/_/_/   Chuck
> Lewis
>  _/            _/      _/   _/      _/   _/            _/    _/
> CLEWIS@IQUEST.NET
> _/_/_/_/   _/      _/   _/_/_/_/   _/_/_/_/   _/       _/
> Indianapolis,
> IN
> 
> "The opinions that are shown, are exclusively my own. All my own, all
> my
> own..." and NOT my employer's (with apologies to Emerson, Lake and
> Palmer)...
> 
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.