RE: passing parms between Cobol/400 & ILE-RPG -- COBOL400-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.

Subject: RE: passing parms between Cobol/400 & ILE-RPG
From: "Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>
Date: Wed, 11 Dec 2002 14:48:46 -0500
Importance: Normal
List-archive: <http://archive.midrange.com/cobol400-l/>
List-help: <mailto:cobol400-l-request@midrange.com?subject=help>
List-id: COBOL Programming on the iSeries/AS400 <cobol400-l.midrange.com>
List-post: <mailto:cobol400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/cobol400-l>,<mailto:cobol400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/cobol400-l>,<mailto:cobol400-l-request@midrange.com?subject=unsubscribe>

 >>  I thought it was good programming style to use separate parameter
fields, you know, data type checking and whatnot.

Um - what type checking?  On a (dynamic) call the only thing passed is a
pointer to the data.  There is no type checking of any kind.  In fact the
system has no such capability - even operational descriptors don't cover
more than a small fraction of the available data types and so are
fundamentally useless.

Jon Paris
Partner400

As an Amazon Associate we earn from qualifying purchases.

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.