Re: starting group jobs at signon

[Sam_L <lennon_s_j@xxxxxxxxxxx>]

This hasn't been a issue for me, and it is years since I was at a job 
where we used group jobs in the main menu so I don't remember if it was 
an issue then.

Solution probably depends on how your folk signoff (and thus terminate 
all their group jobs) and the message logging level and how you control it.

So, if in your initial program you do a CHGJOB LOG(0 99 *NOLIST) or 
similar to suppress most logging, that would be inherited by your group 
jobs. Then, when a group job is actually selected the first thing it 
would do is a CHGJOB to whatever logging level you wanted.

And, FWIW, you can do ENDGRPJOB LOG(*NOLIST) if you can figure out some 
way to use it.

Sam



On 4/28/2017 8:39 AM, Gerald Magnuson wrote:
> Thanks Sam,
> this is exactly how we launch our group jobs...
> one of the problems I was wanting to resolve is all the job logs
> created (spooled) from jobs that never were selected.
> Maybe there is something I can do to NOT spool a log if the job was never
> selected...?

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus