RE: EXTPROC(*CL) and V6R1

[David FOXWELL <David.FOXWELL@xxxxxxxxx>]

> -----Message d'origine-----
>
> > We are obliged to code all our exported subprocedures with 2 data 
> > structures as parameters. One for input, the other for output. The 
> > "parameters" are actually the DS subfields. This idea was a work 
> > around to avoid changing modules when one needed to add a parameter.


Here's an example to demonstrate why :

Procedure GetClientProductInfo

In : ClientNumber
Out : ClientProductDescriptionShort

Modification : Colleague wants to add parameter ClientProductDescriptionLong

Procedure GetClientProductInfo :
	GetClientProduct ( ) //procedure that chains to client file for associated product.
	CHAIN ClientProduct ProductFile  // This file contains all the descriptions.


Personally, I wouldn't expect a procedure to return product descriptions for a client number. I'd have charged the client then pass the product to get the description.

Then, the argument would be that the caller would have to do several calls instead of one.

Someone help!