RE: Passing numeric fields to COBOL program

[Rob Berendt <rob@xxxxxxxxx>]

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
+---