Re: The problem with SAVCHGOBJ . . . -- MIDRANGE-L

Subject: Re: The problem with SAVCHGOBJ . . .
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Fri, 07 May 2010 15:20:04 -0700
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: The problem with SAVCHGOBJ . . . , Pete Massiello

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.