Re: starting group jobs at signon

ok, thanks...
this appears to fix my situation of all those job logs from "unused" group
jobs...

in my program that launches the group job, I do a "CHGJOB LOGOUTPUT(*PND)"
before the TFRGRPJOB back to the RETURN job....
then just before the actual CALL, I do a "CHGJOB LOGOUTPUT(*JOBEND)"




On Fri, Apr 28, 2017 at 3:07 PM, Voris, John <john.voris@xxxxxxxxxxxxx>
wrote:

To suppress joblogs, note that there is also CHGJOB LOGOUTPUT( *PND ) or
CHGJOBD LOGOUTPUT( *PND )

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.

--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD