|
midrange.com
Ok, your database server prestart job can be run from a couple of possible
locations - either QUSRWRK or QSERVER. So, you can either check the
existing active job or track stuff down through SBSD, PJE, and JOBD...but
going the existing active job is probably quicker.
Check and see what jobd it is using. If it using QDFTJOBD, I'd recommend
changing the system to use a different JOBD. Of course, this opens the
debate about changing system default settings or creating new objects.
That debate can be kind of never ending. My suggestion would be to
create a new jobd (copy the one that the job is using now), change the
logging levels to your preferred level, and then change the prestart job
entry to use your new job description. The other option is to just change
the logging levels on the existing jobd. To me that is up to your
preferences. I happen to default to I want everything logged and I will
then restrict what I think is necessary.
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
Brian Piotrowski
<bpiotrowski@simc
oeparts.com> To
Sent by: Midrange Systems Technical
midrange-l-bounce Discussion
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
12/01/2005 08:15 Subject
AM RE: Preventing Writes to Log file
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
Whoops, I just realized which system is the culprit.
Before I moved all of our data to the AS/400, our data was housed in an
MSSQL database. I have a web page that hits this data every 30 seconds.
Before it didn't matter because there wasn't any AS/400 interactivity
between the web pages.
However, last week I moved all data to the AS/400 and pointed my web
services to begin looking there for the data. The web page is refreshed
every 30 seconds (hence the reason why it queries the AS/400 for data).
Here's a sample of one of the logs:
Job name . . . . . . . . . . : QZDASOINIT
User . . . . . . : QUSER
Number . . . . . . . . . . . : 361571
Job description . . . . . . : QDFTJOBD
Library . . . . . : QGPL
MSGID: CPF1124
TYPE: Information
SEV: 00
DATE: 28/11/05
TIME: 22:17:29.019224
FROM PGM: QWTPIIPP
LIBRARY: QSYS
INST: 05D4
TO PGM: *EXT
LIBRARY:
INST: *N
Message . . . . : Job 361571/QUSER/QZDASOINIT started on 28/11/05 at
22:17:28 in subsystem QUSRWRK in QSYS. Job entered system on 28/11/05 at
22:17:28.
>From module . . . . . . . . : QZBSSECR
>From procedure . . . . . . : QzbsProcessStartServerReq
Statement . . . . . . . . . : 2357
To module . . . . . . . . . : QZBSSECR
To procedure . . . . . . . : QzbsProcessStartServerReq
Statement . . . . . . . . . : 2357
Message . . . . : User SYSOPR from client 192.168.0.4 connected to
server.
192.168.0.4 is our Win2k3 web server.
I don't think it's the other job that runs every 45 seconds, but is this
one. So it is here where I would like to suppress the messages.
Any ideas?
Thank you!
Brian.
-----Original Message-----
From: Brian Piotrowski
Sent: Thursday, December 01, 2005 7:55 AM
To: Midrange Systems Technical Discussion
Subject: RE: Preventing Writes to Log file
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.
--
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 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.
