RE: CL Parameters sharing memory? -- MIDRANGE-L

Subject: RE: CL Parameters sharing memory?
From: Kurt Anderson <kurt.anderson@xxxxxxxxxxxxxx>
Date: Tue, 8 Dec 2009 14:19:12 -0600
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>

Ah, I never thought about submitting the command. Slow on the uptake today I guess.

Thanks

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Tuesday, December 08, 2009 11:51 AM
To: Midrange Systems Technical Discussion
Subject: Re: CL Parameters sharing memory?

Hi Kurt,

This definitely makes sense to me. However everyone is saying "use a
command," and I am, it's just that I'm passing along these parameters
in a call that's submitted.

The sample code you posted showed the SBMJOB running the 'CALL' command,
not running a *CMD object.

For the purposes of this discussion, the command you use on the SBMJOB
was CALL, and the use of CALL on the SBMJOB is the cause of the problem
that needed to be corrected..

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.