|
Thanks very much, Dawn. That's exactly what I needed. Gary > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dawn May > Sent: Friday, June 20, 2003 9:28 AM > To: Midrange Systems Technical Discussion > Subject: Re: QZSHSH joblogs > > > > Actually, batch immediate jobs inherit the job attributes > from the job that starts the batch immediate job, not the job > description. > > You could do a CHGJOB * LOG(4 0 *NOLIST) just prior to the > STRQSH command and change it back to LOG(4 0 *SECLVL) after. > The batch immediate jobs would then pick up LOG(4 0 *NOLIST) > and not generate a job log. > > > Dawn May Tie Line 553-2121 External 507-253-2121 > Internet: dmmay@xxxxxxxxxx > Work Management 47X/015-2 E118 > > > > > > "Gary L Peskin" > > > <garyp@xxxxxxxxxxxx> To: > <midrange-l@xxxxxxxxxxxx> > > Sent by: cc: > > > midrange-l-bounces@x Subject: > QZSHSH joblogs > > idrange.com > > > > > > > > > 06/19/2003 12:15 PM > > > Please respond to > > > Midrange Systems > > > Technical Discussion > > > > > > > > > > > > > I'm running a CL in batch that uses job description JOBD1. > It specifies LOG(4 0 *SECLVL) which is what I want for my batch job. > > The CL executes two STRQSH commands every five minutes, each > specifying a command to execute in the CMD parameter. Each > of these STRQSH commands in my CL spawns a QZSHSH job of type > BATCHI. The QZSHSH job inherits JOBD1 from by batch job > running the CL containing the STRQSH commands. This results > in joblogs hanging around for the numerous QZSHSH jobs that > are getting created. > > Is there a way to prevent these job logs from being retained > or to cause the shell command to be executed from a thread > inside my batch job, preventing the creation of the QZSHSH > job in the first place? > > We are on v5r1. > > Many thanks in advance, > Gary > > > _______________________________________________ > 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-2025 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.