RE: Subprocedures and files (was: Procedures are FUN!)

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

>I've modified your code to try and
>emulate what I was doing.

I didn't expect to see the CALLB; the term subprogram threw me off I guess.
This is an interesting one.  It appears that the INFDS does not match the
internal "open" flag for the file INFDS FILE FEEDBACK

File . . . . . . . . . . . . . . . . . :   QRPGLESR
File Open  . . . . . . . . . . . . . . :   NO
File at EOF  . . . . . . . . . . . . . :   NO
File Status  . . . . . . . . . . . . . :   01215
             OPEN was issued to opened file  (C G D F).
File Operation . . . . . . . . . . . . :   OPEN F

If I put open(e) and ignore the 'already open' error, it fails on the read
src: I/O to closed file!  If I do the CALLB first, it runs.  Very curious.

I am going to tinker more, but I wanted to report that I can reproduce the
problem.
  --buck