On Sat, 21 Jun 2025 17:57:18 +0000, Seymour J Metz <[email protected]> wrote:
>No, there is no problem with a keyword being the same as the name of an >environment, >other than making the program harder to read. The statement "ADDRESS SAY" >would be >perfectly unambiguous should someone be perverse enough to use SAY as the name >of an environment.. Enough with wasting my time with obviously wrong answers! Do some research. In TSO REXX, call is valid both as a TSO command and a REXX instruction. They provide very different functionality. call ** always processed by REXX ** "call" ** always processed by TSO ** alloc ** always processed by TSO ** "alloc" ** always processed by TSO ** Mike used "say" instead of "message" because of the obvious confusion it would cause. Most likely he was unfamiliar with TSO when he created the REXX CALL instruction which cannot be accessed through ADDRESS ??? CALL because it does not have an associated environment. There are solutions but ALLOC functions in all forms where as CALL may not give you the answer you expect. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
