Re: CPF2526 - Job message queue for "Job #"/"User"/"Job Name" can not be exte...

Chuck,

In a message dated 98-01-23 12:13:48 EST, you write:

> My question - is there any danger in changing QJOBMSGQFL to *WRAP (i.e.
>  looping jobs, etc) or is it OK to do this ?

Only if you ever need the entries for debugging problems.  If so, you can
change it to *PRTWRAP so that the current entries are printed to QPJOBLOG
prior to wrapping.  You can also control this at the job level via the JOBD.

Sounds like the JOBD might be set to too high a logging level (several vendors
are doing this these days).  I prefer LOG(4 09 *SECLVL) LOGCLPGM(*NO).  Many
vendors are shipping LOG(4 00 *SECLVL) LOGCLPGM(*YES), which not only slows
overall system performance but is entirely unnecessary in 99% of cases.  You
can always do a CHGJOB if you really _NEED_ to see every single message and CL
command...

JMHO,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@aol.com

"One of the greatest labor-saving inventions of today is tomorrow." -- Vincent
T. Foss
+---
| 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
+---