× 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.



> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx / CWilt@xxxxxxxxxxxx
> Sent: Tuesday, July 20, 2004 1:46 PM
>
> Look in the FAQ.
> http://faq.midrange.com/data/cache/70.html

Thanks Charles,

I did see that, maybe I didn't read closely enough, but in my case, I'm not
passing literal values, I'm passing variables of the same definition between
the two programs.

Does SBMJOB convert the value in the variable to a literal?  And, thus,
literals are passed as 15,5?

I think I see it now.  I didn't pick up the implication of "the _system_ is
converting those variables to literals before issuing the CALL command."

I forgot where I put my memory improvement pills.  <sigh>

Booth, thanks for the response.  That's what I ended up doing.  To me, it
seems "klutzy" to have to do CHGVAR alpha VALUE(numeric) for every numeric
variable being passed in the CL SBMJOB, then have to either use data
structures on the parms in the RPG program or move alpha to numeric
stand-alone variables.

Someone else suggested to just change all variables to 15,5.  This works as
well, but I'll end up having to do the same moves as the numeric>alpha and
alpha>numeric process that I ended up going with.  The CL program gets these
numeric values from a SNDRCVF on a display file, so they are defined as they
need to be.  Then, in the RPG program, they are used as key fields.

Relearned something very old today!

db


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.