|
SO my original CL looks like this below
DIRSAVE: SBMJOB CMD(SAV DEV('/qsys.lib/tap03.devd') +
OBJ(('/dtmdir' *INCLUDE)) +
ENDOPT(*UNLOAD)) JOB(DIRSAVE)
Should it look like
CHGJOB: SBMJOB CHGJOB dftwait(2)
DIRSAVE: SBMJOB CMD(SAV DEV('/qsys.lib/tap03.devd') +
OBJ(('/dtmdir' *INCLUDE)) +
ENDOPT(*UNLOAD)) JOB(DIRSAVE)
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, April 24, 2008 11:56 AM
To: Midrange Systems Technical Discussion
Subject: Re: IFS save issue
Maybe the original one was in batch also. Perhaps he just wanted to spawn
it off as a separate task?
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
"Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/24/2008 11:53 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc
Subject
Re: IFS save issue
But then you have to maintain two programs.
I always like to make such CL programs "smart" enough to detect if
running interactive, and just submit themselves to run in batch. ;-)
Mark
> rob@xxxxxxxxx wrote:
You have to change this:--
DIRSAVE: SBMJOB CMD(SAV DEV('/qsys.lib/tap03.devd') +
OBJ(('/dtmdir' *INCLUDE)) +
ENDOPT(*UNLOAD)) JOB(DIRSAVE)
Put
SAV DEV('/qsys.lib/tap03.devd') +
OBJ(('/dtmdir' *INCLUDE)) +
ENDOPT(*UNLOAD)
into a CL program. Preceed the SAV command with the CHGJOB command.
Then your original program is
DIRSAVE: SBMJOB CMD(CALL MYSAVEPGM) JOB(DIRSAVE)
Rob Berendt
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.
--
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-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.