RE: Preventing Writes to Log file

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@xxxxxxxxxxxxxxx>
> 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?
> 
> Thanks!
> 
> Brian.
> 
> -----Original Message-----
> From: Mike.Crump@xxxxxxxxxxxxxxxx [mailto:Mike.Crump@xxxxxxxxxxxxxxxx] 
> Sent: Thursday, December 01, 2005 7:41 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: Preventing Writes to Log file
> 
> 
> Brian,
> 
> I'm assuming you are referring to the system history log?  Is this the
> job
> start and job ended message?  I'm not aware of you being able to
> suppress
> that kind of information - I might suggest that you change the job to a
> NEP
> that sleeps for 30 seconds....again, that is assuming that you are
> talking
> about the system history log (DSPLOG, QHSTXXXXXX files, etc.)
> 
> 
> Michael Crump
> Manager, Computing Services
> Saint-Gobain Containers
> 1509 S. Macedonia Ave.
> Muncie, IN  47302
> (765)741-7696
> (765)741-7012 f
> (800)428-8642
> 
> "The probability that we may fail in the struggle ought not to deter us
> from the support of a cause we believe to be just"  Abraham Lincoln
> 
> 
> 
> 
> 
> midrange-l-bounces@xxxxxxxxxxxx wrote on 12/01/2005 07:24:46 AM:
> 
> > 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.
> 
> 
> 
> -- 
> 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.