On Thu, Feb 27, 2014 at 2:23 PM, Frank Swarbrick <[email protected]>wrote:
> It can be used for that, but it is also used for indicating the return > code to be passed back to the operating system, which is the particular > situation I'm concerned about. > > I apologize in advance for being "tacky". But I consider this to be unnecessary. In the original message, you basically seem to say that the current crop of COBOL programmers are simply too ignorant, or lazy, to learn that the value of RETURN-CODE is volatile and can often be changed "behind the scenes". Perhaps whomever it is who is responsible for teaching programmers COBOL needs to emphasize that RETURN-CODE should be set at the last possible instant. In fact, I feel that programmers really should create their own variable, perhaps WS-RETURN-CODE and learn to modify that variable. And to always MOVE WS-RETURN-CODE TO RETURN-CODE just before any GOBACK or STOP RUN. I _can_ see your point. I simply think that a programmer who cannot learn this should not be entrusted with writing Enterprise Level code. In any language. -- Wasn't there something about a PASCAL programmer knowing the value of everything and the Wirth of nothing? Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
