RE: Variable Scope

["Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>]

 >> I thought I might have a misunderstanding as to the scope of a variable
defined outside of the subprocedure

No - as long as the variable containing the file name is in the global
section you have no problems.  RPG variable scoping is pretty simple - it's
local or it's global or it is shared through import/export.  That's pretty
much it.

My best guess is that this is a PTF issue.  There were a number of problems
in the early days of this release - have you checked your PTF level?

Since you say you wrote the note pre-coffee ..... you haven't used a name
for the variable that is also an input field have you?

You might also try just as a test using a literal not a variable and see if
that works.  Then a variable with just the file name (i.e. default to *LIBL)
and see if the log message is any different.

Jon Paris
Partner400
www.Partner400.com