• Subject: RE: CPF2526 - Job message queue for "Job #"/"User"/"Job Name" can not be extended. Job ended.
  • From: Neil Palmer <npalmer@xxxxxxxxxxx>
  • Date: Mon, 26 Jan 1998 22:13:47 -0700

Yeah - and while the joblog is doing it's Print/Wrap business the rest
of the system crawls to a halt.   :-)

I guess it depends on each systems jobs.  For example, I KNOW that none
of the jobs running on my system should EVER generate a joblog large
enough to fill the job message queue, and if they do they must be
runaway jobs that need killing anyway.

... Neil Palmer                                     AS/400~~~~~      
... NxTrend Technology - Canada     ____________          ___  ~     
... Thornhill, Ontario,  Canada     |OOOOOOOOOO| ________  o|__||=   
... Phone: (905) 731-9000  x238     |__________|_|______|_|______)   
... Cell.: (416) 565-1682  x238      oo      oo   oo  oo   OOOo=o\   
... Fax:   (905) 731-9202         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
... mailto:NPalmer@NxTrend.com          http://www.NxTrend.com

        -----Original Message-----
        From:   Cotes, Steven [SMTP:cotess@data-io.com]
        Sent:   Monday, January 26, 1998 8:10 PM
        To:     'MIDRANGE-L@midrange.com'
        Subject:        RE: CPF2526 - Job message queue for "Job
#"/"User"/"Job Name" can not be extended. Job ended.

        I agree with investigating excessively large joblogs for
        logging levels,
        hardware errors or whatever else might be a problem. But leaving
        set to *NOWRAP means you are leaving your system open to
        abnormal ending of jobs. If you change it to *WRAP or *PRTWRAP
you still
        receive notification of wrapping with CPI2417. The advantage
being that
        don't also have users asking why their screen died.

         -Steve Cotes

        > ----------
        > From:         Neil Palmer[SMTP:npalmer@NxTrend.com]
        > Sent:         Monday, January 26, 1998 12:40 PM
        > To:   'MIDRANGE-L@midrange.com'
        > Subject:      RE: CPF2526 - Job message queue for "Job
        > Name" can not be extended. Job ended.
        > Hold on there.  I disagree with the statement "Definitely
        > QJOBMSGQFL to *WRAP or *PRTWRAP" without first investigating
to see
        > just
        > what is filling up a 5000+ page joblog in the first place.
        > Take a look, you may find a series of error messages start
around page
        > 2
        > and keep repeating to the end of the joblog.
        > A common cause that I have seen is a case where for some
reason or
        > other
        > the system loses contact with the device (could be a PC, could
be a
        > dumb
        > terminal) and starts looping and repeatedly logging the
        > messages (or similar) to the joblog:
        > RPG1211, RPG9001, CPF4128, CPF9999
        > When this error occurs, the interactive job is usually eating
up all
        > available CPU cycles (WRKACTJOB often shows 90%+ CPU usage).
At least
        > with QJOBMSGQFL set to *NOWRAP a runaway job like this will
        > end (when it fills the job message queue).  If you let it wrap
        > could
        > just keep looping forever if no one notices it and kills it.  
        > (Of course, you could probably avoid this looping on a device
error if
        > you do not set sysval QDEVRCYACN to *MSG or *DSCMSG).
        > ... Neil Palmer
        >       -----Original Message-----
        >       From:   Cotes, Steven [SMTP:cotess@data-io.com]
        >       Sent:   Friday, January 23, 1998 2:36 PM
        >       To:     'MIDRANGE-L@midrange.com'
        >       Subject:        RE: CPF2526 - Job message queue for "Job
        > #"/"User"/"Job Name" can not be extended. Job ended.
        >       Chuck,
        >       definitely change QJOBMSGQFL to *WRAP or *PRTWRAP.
        >       Leaving it *NOWRAP leaves you open to exactly the
        >       you had.
        >       I prefer *WRAP, if you _really_ need to keep the
messages then
        >       use *PRTWRAP.
        >        - my .02,
        >        -Steve Cotes
        >        -cotess@data-io.com
| 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

This thread ...

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

This mailing list archive is Copyright 1997-2020 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].