RE: Reg: Compiler Options Related

the local file wasn’t implemented when I started using Import/Export back then


-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jon Paris
Sent: Wednesday, May 12, 2021 16:43
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Reg: Compiler Options Related

Why not pass the DS as a parm? Or have it come back as a return value (with RTNPARM if large).

For the reasons outlined in my previous response I just don't find the risks associated with import/export worth any potential benefits.

Also - in many ways - I would prefer a service program to receive the file being used as a parm. That results in any lock being held by the program making the call. In your scenario a lock could easily be released by another call (from elsewhere in the app) to the same routine. The result being that the logic that thinks record X is locked and can therefore be updated is being lied to - and any update would change the wrong record. Not goodness - so I've seen people forced to code elaborate checks to make sure they are updating what they think they are. etc. etc.

Just my 5 cents worth.


Jon P

On May 12, 2021, at 1:37 PM, Francois Lavoie <Francois.Lavoie@xxxxxxxxxxxxxxxxxxxx> wrote:

Hey Jon,

Why aren’t you Data Structure Export fan?

So great to have to possibility to chain (and possibly lock) a db file
record in a Service Program, have the Exported DS filled up and only
have to Import the DS in other program(s) without having to re-chain

That technique was explain in a ILE Red Book a while ago

Francois

Confidentiality Warning/Avertissement de confidentialité:

This message is intended only for the named recipients. This message may contain information that is privileged or confidential. If you are not the named recipient, its employee or its agent, please notify us immediately and permanently destroy this message and any copies you may have. Ce message est destiné uniquement aux destinataires dûment nommés. Il peut contenir de l'information privilégiée ou confidentielle. Si vous n'êtes pas le destinataire dûment nommé, son employé ou son mandataire, veuillez nous aviser sans tarder et supprimer ce message ainsi que toute copie qui peut en avoir été faite.