RE: The problem with SAVCHGOBJ . . .

["Pete Massiello" <pmassiello-ml@xxxxxxxxxxxx>]

All you need to do is record the last time you do a full save, and then use
REFDATE with the date of the full save.  When it comes to a library that
hasn't been saved, since you are using REFDATE it WILL save the library.

	Pete

Pete Massiello
iTech Solutions
http://www.itechsol.com

Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120
Add iTech Solutions on LinkedIn: http://www.linkedin.com/groups?gid=2206093





-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Friday, May 07, 2010 6:20 PM
To: Midrange Systems Technical Discussion
Subject: Re: The problem with SAVCHGOBJ . . .

CRPence wrote:
> SAVCHGOBJ OUTPUT(*OUTFILE)

I think you're onto something there. I was seriously considering a 
DSPJOBLOG OUTPUT(*OUTFILE), and I'd never even considered the 
possibility that SAVCHGOBJ would have an OUTPUT parameter.

Thanks.

(And it's not "concurrent batch jobs" that I was ranting about 
yesterday; it was "concurrent batch jobs coming out of the default 
queue." And the simplest way to keep jobs that are guaranteed to fight 
with each other if run concurrently from so running is to launch them 
through a queue whose entry is guaranteed to be one-at-a-time.)

--
JHHL