Re: COBOL 101 -- COBOL400-L

Subject: Re: COBOL 101
From: "Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>
Date: Sat, 14 Apr 2007 17:55:46 -0400
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/mailman/listinfo/cobol400-l>, <mailto:cobol400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/cobol400-l>, <mailto:cobol400-l-request@midrange.com?subject=unsubscribe>

"In answer to your question I think the linkage gets passed in as a big
blob and you can break down the parms into a data structure."

Which is also true for RPG - so I thought I'd clarify this for the archives.

COBOL parm passing is _exactly_ the same as for RPG (or indeed any other
language on the box). Of course the syntax is different but the mechanics
are identical.

For *PGM calls a pointer is passed for each parm.

For procedure calls the parms are passed on the stack (mostly) and will be
either a pointer (for reference parms) or the actual data for Value parms.

RPG maps parms to data via the *Entry PLIST or the Procedure Interface.

COBOL maps parms to data via the LINKAGE SECTION.

That's all there is to it.

Jon Paris
Partner400

www.Partner400.com

Follow-Ups:

Re: COBOL 101 , Joe Pluta

This mailing list archive is Copyright 1997-2026 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.