Re: free opcode

Well the sad truth is that the FREE opcode probably didn''t do 
what you thought it did in the first place.   It just "Ended" the program.
It didn't close the associated files or other resources.   In laymen's 
terms "It Didn't Work"  to begin with.   

What do you WANT to do is the question,  forget HOW you were trying 
to do it.   Was the REAL need to end the program as if *INLR was on 
when it ended?   There are a number of system design approaches
that could be used.  I say "system design" because I find that most
shops don't think of having standards for things like this that will be 
needed throughout a system.   

One benign way is to have a "Terminate" flag as a parm being passed
to a lower module.   Set it to "YES" and call the program when you want
to "FREE" it.   that would tell the lower module to seton *INLR and end.

Other ways is to use Activation groups, or terminating bound calls, 
or or or.   But again,  these things should be a "System Design" 
construct done the same way thoughout the shop.

Just my opinion.

John Carr
--------------------------------
Can anyone tell me what to use instead of the FREE opcode.  We are
converting to RPGIV from III and are getting conversion errors stating
FREE is no longer a good opcode.  Any assistance would be GREATLY
appreciated.

TIA
Mark A McCarty

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---