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


  • Subject: Sv: Passing numeric fields to COBOL program
  • From: "Henrik Krebs" <Henrik.Krebs@xxxxxxxxx>
  • Date: Wed, 10 Jun 1998 01:52:08 +0200

As we have discussed earlier 'passing parameters' is just 'passing pointers to
memory'.

When called from a program the information in the area those pointers point to
is not THAT difficult to understand.

>From the command entry (program QCMD)/Command Line you can key:

CALL program PARM(a B 'c' 4)


Remember that:
1'st param. is translated (default) into capitals, i.e. First parameter is 'A',
not 'a'.
2'nd (actually: three first) forms a 64 byte char field (or is it less?. At
least a fixed number of bytes, only differing if the litteral is longer than
that fixed number)
3'rd parameter is NOT translated because it's quoted.
4'th is set up as a 15.5 packed numeric, i.e. x'000000000400000F'. 


Regards

Henrik Krebs

------------------------------------------------------------
Henrik Krebs
IT Consultant (IBM AS/400)
Phone +45 31 57 83 23
Mobile +45 40 88 83 23
Email: Henrik.Krebs@Scout.Net
Web: http://users.cybercity.dk/~dko3534
Snailmail: Amagerbrogade 62, 3-24, DK-2300 Copenhagen
------------------------------------------------------------ 

----------
Fra: Rob Berendt <rob@dekko.com>
Til: MIDRANGE-L@MIDRANGE.COM
Emne: RE: Passing numeric fields to COBOL program
Dato: 9. juni 1998 23:54

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.