RE: System JobLogs

Andy,
        you answer is correct in principle but there are two more issues:

1.      Frequently the subsystems (and therefore also the jobs) are ended
*IMMED,
        this will cause a *NOLIST job to produce a joblog anyway.
2.      Some jobs set their LOG job attribute at run-time, regardless of the
jobd
        setting

Dang annoying as joblogs can be, I feel they are probably here to stay,
wanted or not.

Why not use the Cleanup options (GO CLEANUP), and set the Joblogs value to a
low
value, "1" perhaps.  If not, it is a fairly straightforward task for a piece
of CL
to tidy up joblogs automatically.  This will help keep your table space
utilisation
down to a reasonable level.

Kind Regards

Jeffrey E. Bull
Software Support Consultant
IBM Certified AS/400 System Administrator
ITM Group Limited

tel.        +44 [0] 149 487 8589
mbl.    +44 [0] 786 750 4961
web.   http://www.itm-group.co.uk

Chalfont Grove, Narcot Lane, Chalfont St Peter,
Gerrards Cross, Buckinghamshire,  SL9 8TY, UK




-----Original Message-----
From: Andy Nolen-Parkhouse [mailto:aparkhouse@attbi.com]
Sent: 21 March 2002 12:00
To: midrange-l@midrange.com
Subject: RE: System JobLogs


Al Mac,

If you follow these jobs back to their origination, check the job
description associated with each job.  The logging level associated with
the job log will determine whether a job log is generated all of the
time or only when a certain error level is reached.

You have three elements of the LOG parameter:
1) Logging Level - a number from zero through four which determines the
amount of detail in your job logs.
2) Message Severity Level - a number from 00 through 99 which determines
the severity of messages written to your logs.
3) Message Text Level - a parameter (*NOLIST, *MSG, or *SECLVL).  If you
set this to *NOLIST, you will produce no logs unless a specific error
message is reached within the program.

I have oversimplified the interrelationships between the parameters
above, but this is where you want to look.  If you have the three
parameters set to 4 (highest level of detail), 00 (lowest severity
level), and *SECLVL (most verbose logging), then you should expect a job
log all the time, every time.  Many of your system jobs may be located
in the subsystem descriptions as prestart or autostart jobs.  You can
find the job description as part of the subsystem entries.

You probably want to tinker with them so that you don't get a log with
normal completion but you do get one if a specific error level is
reached.

Regards,
Andy Nolen-Parkhouse



> Subject: System JobLogs
>
> Each nite I clear off the system a few hundred joblogs.
> I suspect we have a lot of requirements for job tables just because of
> this.
>  DSPJOBTBL
>
> I suspect system performance for many users might be better if this
stuff
> not
> going on in the background.
>
> 99% of the time the only job log I need is when some human is having a
> problem.
> I do not believe I have EVER used a system joblog.
>
> Is there some place I can go to turn this stuff off & then be able to
> remember where that place is when some time in the future we might
ever
> need
> them again?
>
> MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)

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


________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________


DISCLAIMER

Any opinions expressed in this email are those of the
individual and not necessarily the Company. This email
and any files transmitted with it, including replies and
forwarded copies (which may contain alterations)
subsequently transmitted from the Company, are
confidential and solely for the use of the intended recipient. If you are not 
the intended recipient or the
person responsible for delivering to the intended recipient,
be advised that you have received this email in error and
 that any use is strictly prohibited.

If you have received this email in error please notify the IT
manager by telephone on +44 (0)208 4762000 or via
email to Administrator@itm-group.co.uk, including a copy
of this message. Please then delete this email and
destroy any copies of it.

________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________