RE: Parameter List from CL to Cobol

[geir.kildal@xxxxxxxxxxxxxx]

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.


Mvh.

Geir






Chris.Chambers@v2music.com
Sent by: cobol400-l-admin@midrange.com
09.10.01 13:34
Please respond to cobol400-l


        To:     cobol400-l@midrange.com
        cc:
        Subject:        RE: Parameter List from CL to Cobol




ACBL1001-PROGRAMSEQ             PIC  9(03)
VAR(&PGMSEQ) TYPE(*DEC) LEN(3 0)

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



_______________________________________________
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing
list
To post a message email: COBOL400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/cobol400-l
or email: COBOL400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.