|
Brian, What you can do is affect the logging level of that job. To be safe I think you might want sev 30 or 40 or higher messages sent to the log so a logging level of 1, 40, and *msg/*seclvl. That can be controlled in either the jobd, sbmjob, or even a chgjob. Message logging: Level . . . . . . . . . . . . 1 0-4, *SAME Severity . . . . . . . . . . . 40 0-99, *SAME Text . . . . . . . . . . . . . *SECLVL *SAME, *MSG, *SECLVL, *NOLIST With this setting only messages with a severity of 40 or higher will get listed and the second level help will also get listed. This is good if you want or need help in problem determination. If you don't you can change the level to 0 and the text to *NOLIST. I normally don't like to do that but that is totally based on your preferences. Jobs around here don't fail hardly at all but when they do I want some assistance in determining the cause. midrange-l-bounces@xxxxxxxxxxxx wrote on 12/01/2005 07:55:28 AM: > 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 > > > > -=-=-=-=-=-=-=-=-=-=-=-=-=- > > > > > > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.