×
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.
Dennis,
This would be great if I was writing both pieces from scratch. What I am attempting to do is replace a physical file in existing code with a program that will take the old record format and populate new table(s) with it without affecting the logic structure. In other words, other than the F spec and maybe a parm list the code should be exactly as it was before.
Rick
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Dennis Lovelady
Sent: Thursday, September 23, 2010 2:57 PM
To: 'RPG programming on the IBM i / System i'
Subject: RE: Special file parameter issue
This is a key reason that it's a good idea to keep parameters as read-only (VALUE or CONST), and to only use them as source to EVAL. If they're to be two-way, then perhaps they should be set explicitly via EVAL, perhaps just before RETURN.
myKeyData = parmKey ;
myDate = parmDate;
... code
parmReturn = returnValue ;
The whole process just gets so much simpler (at the cost of a couple more
variables) when you do that.
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"I find television very educating. Every time somebody turns on the set I go into the other room and read a book."
-- Groucho Marx
Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.
midrange.com
