Re: CL Parameters sharing memory?

Subject: Re: CL Parameters sharing memory?
From: Buck <kc2hiz@xxxxxxxxx>
Date: Mon, 07 Dec 2009 17:14:37 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@xxxxxxxxxxxx?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@xxxxxxxxxxxx>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@xxxxxxxxxxxx?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@xxxxxxxxxxxx?subject=unsubscribe>

Kurt Anderson wrote:

I tried really hard to figure this one out on my own, but am coming up short.

Search the FAQ for 'garbage' It's a common enough misunderstanding
about constants as parameters. http://faq.midrange.com

Yes, I know you are using variables, but what is happening is the CL
program is essentially building a string to pass to the command
interpreter (the CMD() parameter of SBMJOB) and you're ending up with

call pgm(testcl2) parm(kurt test N)

--buck

This thread ...

Re: CL Parameters sharing memory?, (continued)
- Re: CL Parameters sharing memory?, Buck <=
  - Re: CL Parameters sharing memory? , Vern Hamberg

Follow-Ups:
- Re: CL Parameters sharing memory? , Vern Hamberg

Prev by Author: Re: Something that goes along with how to ask a good question
Next by Author: Re: Save file to tape
Previous by thread: RE: CL Parameters sharing memory?
Next by thread: Re: CL Parameters sharing memory?
Index(es):

Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2010 by MIDRANGE dot 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 here. If you have questions about this, please contact