× 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.



Hi Raul,

The 3rd element of the LOG parameter of the CHGJOB command, and in job descriptions, is probably what you want to change to the following:

*NOLIST
If the job ends normally, no job log is produced. If the job
ends abnormally (if the job end code is 20 or higher), a job log
is produced. The messages that appear in the job log contain
both the message text and the message help.

--*
Peter Dow*/
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /



On 8/12/2011 6:44 AM, Raul A. Jager W. wrote:
Help!!
I'm replacing an i5 V5.3 with a p7 v 7.1. In the old computer only the
jobs that ended "abnormal" leave a joblog in the outq QEZJOBLOG, in the
new one, all jobs end up in the output queue.
I imagine it is because one of the default values is different, but I
have no idea which one. I looked several manuals, up to now wihtout success.
Can somebody give a hint?

TIA
Raul


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.