|
Lim Hock-Chai wrote:
does message logging setting on CHGJOB command suppose to effect previously executed commands?
Lim:As I understand it, confusion comes from the use of the term "joblog" for what seem to be different things.
When you use DSPJOB OPTION(*JOBLOG), you don't see exactly the same thing as when you view the spooled "joblog" that can be created when a job ends. In the first case, you see the job message queue; in the second case, you see the result of the job message queue having been read and written to the spooled output. Note that when you try DSPJOB OPTION(*JOBLOG) for a completed job, the result is empty -- it tells you that the "job log" cannot be displayed even if the spooled "joblog" exists.
AFAIK, the CHGJOB LOG() parameter determines how messages are _written_ to spooled output after being read from the job message queue. It doesn't affect anything in the way the messages exist on the job message queue.
I suppose one way to think of CHGJOB LOG() is that it tells whether you want a 'detail' or a 'summary' report printed of the job message queue. It doesn't control how individual sections are printed; it controls the entire spooled report. Whatever the setting is when the "joblog" is spooled is how the messages will be printed. If you run DSPJOBLOG OUTPUT(*PRINT) multiple times for the same job with different logging levels, you should see detail info appear, disappear and reappear as new spooled files get created.
As others have mentioned, if you don't want messages to show in the joblog (spooled or otherwise), then you need to receive/remove the messages by coding to do so.
Tom Liotta
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.
midrange.com
