This is a multipart message in MIME format.
[ Picked text/plain from multipart/alternative ]
Yes, it should be comp-3 to get it right inside the COBOL-program, but
there is no controll in the CALL-process, you can transfer a packed
decimal parameter in a CL to an alphanumeric parameter in the
COBOL-program, and the CALL will work just fine.  The problems come when
you try to use the parameter inside the COBOL-program(if you don't move it
to a properly defined packed field first...).

For the CALL, the important thing is that the NUMBER of parameters are
equal on both sides.


Sent by:
09.10.01 13:34
Please respond to cobol400-l

        Subject:        RE: Parameter List from CL to Cobol

ACBL1001-PROGRAMSEQ             PIC  9(03)

The COBOL definition should be a comp-3 (should'nt it?)

This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing
To post a message email:
To subscribe, unsubscribe, or change list options,
or email:
Before posting, please take a moment to review the archives

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-2022 by 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.