RE: confused over this prototype definition -- RPG400-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.

Probably the callee uses the same copybook. This way he can use the same
DS on the PI for the procedure parameters.

Regards

Mihael

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: Tuesday, January 12, 2010 10:56 AM
To: RPG programming on the IBM i / System i
Subject: confused over this prototype definition

Hi,

I don't fully understand the two DS declarations that follow this
prototype definition. The prototype is in the module source, ie, with
all the rest of the code. The caller uses compiler directives to copy in
only the code shown below. Why does the module compile when MyProcIn and
MyProcOut are declared twice each? Why does the caller need the
declarations that follow the prototype?

Thanks.

D MyProc PR N
D MyProcIn...
D LIKEDS (MyProcInDs)
D CONST
D MyProcOut...
D LIKEDS (MyProcOutDs)

* Input parms.
D MyProcInDs...
D DS BASED (template)
D QUALIFIED

D Parm1 LIKE ( xxxxx )

D Parm2 LIKE ( xxxxx )

* Output parms.
D MyProcOutDs...
D DS BASED (template)
D QUALIFIED

D Parm1 1

* Definition parameters for callers.
D MyProcIn...
D DS LIKEDS (MyProcInDs)
D MyProcOut...
D DS LIKEDS (MyProcOutDs)

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.