RE: Passing numeric fields to COBOL 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.

You are passing it in hex because you are sending a literal instead of a 
variable.  As it receives the variable in the called program it wants it 
packed.  Hence the hex.

One CASE tool developer generates all of their CL numeric parameters as 15,5 
and converts them into the proper format before calling the HLL program.  I 
think that it has to do with this same situation.  I don't know why 15,5, nor 
do I care.  We always change the CL, or write a separate cl to call their CL.  
We hate having to call 15,5 variables in the main programs that call these 
programs.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.