Re: Must not redefine DB field in subproc

Simon

You hinted at this, but, explicitly stated, until recent releases, fields in files named in F-specs are global - now I think it is possible to have F-specs in subprocedures - or was I dreaming!! Maybe those are local.

The use of a DS as the target of the fields when reading a file also means one can put on a prefix or qualify the names, IIRC, but these would still be in the scope of wherever their respective F-specs are.

Hope I am remembering ANYthing correctly right now - heh
Vern

Simon Coulter wrote:

On 04/05/2009, at 8:27 AM, Peter Connell wrote:

This issue may have already arisen previously but it has caused me such
a significant problem that I wish to mention it.

Known and well documented. Discussed in the RPG documentation and beaten to death on this list.

I took a while to realize that the sub-procedure does not populate the
value of SEQ_NO from the file when it has also been defined locally.

Locally scoped variables override global variables of the same name. Languages with qualified variables allow you to force access to global storage (e.g., this.varname) but RPG and others do not support that behaviour.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------