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



Great, thanks Al.

Brian.

-----Original Message-----
From: Al Barsa [mailto:barsa@xxxxxxxxxxxxxxxxxxx] 
Sent: Thursday, December 01, 2005 10:48 AM
To: Midrange Systems Technical Discussion
Subject: Re: Preventing Writes to Log file


There are a few things that you can do:

First of all, you can filter job log messages.  The LOG parameter on
CHGJOB
is a three part list (ELEM).  The second part is the "severity".  By
raising that number higher than the message that is causing it to log,
those messages would not log.

Another alternative is either changing the message description in
QCPFMSG
to have a lower logging level, or to create a duplicate message in
another
message file and lower the severity (SEV) of that message description,
and
having the offending job (assuming that you have a job in your control)
override QCPFMSG to that message file.  Message descriptions not found
will
revert to QCPFMSG in QSYS.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

"i" comes before "p", "x" and "z"
e gads

Our system's had more names than Elizabeth Taylor!

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com
http://www.as400connection.com



 

             "Brian

             Piotrowski"

             <bpiotrowski@simc
To 
             oeparts.com>              "Midrange Systems Technical

             Sent by:                  Discussion"

             midrange-l-bounce         <midrange-l@xxxxxxxxxxxx>

             s@xxxxxxxxxxxx
cc 
 

 
Subject 
             12/01/2005 07:24          Preventing Writes to Log file

             AM

 

 

             Please respond to

             Midrange Systems

                 Technical

                Discussion

             <midrange-l@midra

                 nge.com>

 

 





Hi All,



I have a program running that hits our AS/400 for information.  This
program runs every 30 seconds, and every time it runs, it writes a
record to the job log.  As a result, our job log has grown horrendously
large.  Is there any way I can suppress the writing to the log for
scheduled jobs so that the job log does not become unruly?



Thanks!


Brian.



-=-=-=-=-=-=-=-=-=-=-=-=-=-

Brian Piotrowski

Specialist - I.T.

Simcoe Parts Service, Inc.

PH: 705-435-7814

FX: 705-435-6746

-=-=-=-=-=-=-=-=-=-=-=-=-=-



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




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.