RE: RE: Preventing Writes to Log file

Tom,

You are correct -- messages get logged to the joblog regardless of the
logging level specified for the job.

However messages can be filtered out (removed) after the initial logging
has been done.  There is a description of this removal in the CL
Programmers Guide in Chapter 8 Working with Messages, Message Logging, and
Joblog.  Basically when a request processor requests a message the system
implicitly removes messages from the joblog based on the message logging
level set for the job.

Many interactive jobs have a request processor in the call stack and if it
is actively used filtering will be performed.  Most batch jobs have no
request processor and so removal/filtering is not done.  Adding (and using)
a request processor to a batch job would cause the removal of messages
based on the message logging level of the job.

Bruce Vining



                                                                           
             qsrvbas@netscape.                                             
             net                                                           
             Sent by:                                                   To 
             midrange-l-bounce         midrange-l@xxxxxxxxxxxx             
             s@xxxxxxxxxxxx                                             cc 
                                                                           
                                                                   Subject 
             12/14/2005 10:32          RE: RE: Preventing Writes to Log    
             PM                        file                                
                                                                           
                                                                           
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
                                                                           
                                                                           




I know this one is old, but I haven't had time lately...

There's a chance that this has been misunderstood. I'm not sure that
changing the logging level will help. AFAIK, the messages get logged
regardless of logging level; they just don't necessarily get copied to the
spooled output.

I had the understanding that the logging level controlled more how much of
the messages would be sent to an external device such as a display or a
spooled file rather than how many messages would go into the job's external
message queue.

The problem is in the term 'joblog'.

Sometimes we think of 'joblog' as being the message queue. Sometimes it's
what gets displayed when we run DSPJOB OPTION(*JOBLOG). And sometimes it's
the printed output in the spooled QPJOBLOG file. Those aren't always
equivalent and logging level is one way to make significant differences.

Does anyone know of a clear description of differences?

Tom Liotta


midrange-l-request@xxxxxxxxxxxx wrote:

>   3. RE: Preventing Writes to Log file (michael)
>
>date: Thu, 01 Dec 2005 06:05:41 -0700
>
>So, are you talking about spooled file entries in output queue
>QEZJOBLOG? That the 'every 30 second' job is writing a job log tooutput
>queue QEZJOBLOG? If so, change the logging level of the 'every 30
>second' job. Probably the best place to do it is in a job description.
>Create a new job description (or modify an existing one) and specify
>the logging level:
>
>CRTJOBD JOBD(MICHAEL/MY30SECJD)
>        LOG(4 0 *NOLIST)
>
>This means that a job log will *not* be produced (*NOLIST) if the job
>ends normally.
>
>> -------- Original Message --------
>> Subject: RE: Preventing Writes to Log file
>> From: "Brian Piotrowski" <bpiotrowski>
>> Date: Thu, December 01, 2005 7:55 am
>> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
>>
>> Hi Mike,
>>
>> Actually, the job queue that is being affected is QEZJOBLOG.
>>
>> What is happening is that I am calling an RPG program from a CL Batch
>> program.  Can I add any additional code to either the RPG program or the
>> CL program to suppress log entries?

--
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788 x313
Fax    253-872-7904
http://www.powertech.com



__________________________________________________________________
Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at
http://isp.netscape.com/register

Netscape. Just the Net You Need.

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp
--
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.