RE: passing Call commands (with parms) from program to program -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Loyd,

I've never done anything with Environment Variables. Can you point to a good book?

Thanks for your input!

steve

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Loyd Goodbar
Sent: Wednesday, October 20, 2010 12:45 PM
To: Midrange Systems Technical Discussion
Subject: Re: passing Call commands (with parms) from program to program

Steve,

My earlier reply might have gotten lost in the shuffle, but you might try
setting environment variables in the first program, and have the other
programs read them. If you are submitting jobs, be sure to use the
CPYENVVAR() parameter [copy environment variables] as the default is *NO.

HTH,
Loyd

On Wed, Oct 20, 2010 at 12:07 PM, Needles,Stephen J
<SNEEDLES@xxxxxxxxxxxxx>wrote:

I agree!! Haha!

But I could not see another way to communicate it. Given some of the
responses I gotten, it seems the whole idea of manipulating these variables
will be of little value anyway. Considering telling management that this
idea sounds better in there heads than it truly is in reality.

steve

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.