I'd have to check some archived manuals to see it they were added to CMS at the same time Rexx was, or ask Mike.
Thing is, as the first person outside of the UK to have a running copy of Rex, (as it was then known; the 2nd 'x' was added when it went into the Product CMS to avoid Copyright infringement, iirc) by the time we had it on our RALVM8 system, all the VM users of my Tools disk (RG62LLKE 194) had been using Rex whether they knew it or not! I had bet my IBM career that Rex would replace most usage of EXEC and EXEC2! I was busily converting the Most Used EXECs to Rex w/o them being any the wiser. I won that bet. Les On 9/5/2015 10:10 PM, CVBruce wrote: > I feel that I overstated the case, in that I do believe they are a part of > Rexx, in that they are supported in a particular Rexx implementation. There > are always going to be locally implemented features that are not universally > available in every implementation of the language. > > Bruce >> On Sep 5, 2015, at 7:03 PM, Les Koehler <vmr...@tampabay.rr.com> wrote: >> >> No, they're not part of Rexx, but as mentioned by Leslie earlier, they >> *are* part of CMS and were specifically added to improve the usability >> of Rexx. I was with IBM at the time and we cheered there addition! >> >> Les >> >> On 9/5/2015 9:29 PM, CVBruce wrote: >>> I’m not an expert on this, but the example you gave in your bug report >>> would never work. This has nothing to do with rexx, but with the way >>> Linux/Unix works. When you typed the ampersand “&” at the end of the >>> command, you disconnected your keyboard from the running process and >>> reconnected it to the shell. You can type all day and your program won’t >>> see a single character. >>> >>> I played around with this and this example works on Linux (Raspbian) with >>> ooRexx (5.0.0). >>> #!/usr/bin/rexx >>> X = 0; >>> Do I = 1 to 100000 >>> X = X + 1; >>> If X//5 == 0 Then Do; >>> address hostemu TS >>> end >>> If X//7 == 0 Then Do; >>> address hostemu TE >>> end >>> end; >>> ::requires "hostemu” LIBRARY >>> >>> When you run this program, it must be in foreground or your keyboard will >>> not be attached to the program. I got this example working by reading the >>> documentation provided in the ooRexx Extensions V4.1.3 manual. I don’t >>> find this functionality particularly useful, and you may not either. That >>> doesn’t mean that they are buggy. And just because you find something in a >>> TSO or CMS manual doesn’t mean that it is a part of “Rexx”. I just checked >>> “The Rexx Language, 2ed” and TE, TS, and HI are not mentioned. >>> >>> Bruce >>> >>>> On Sep 5, 2015, at 4:04 PM, J. Leslie Turriff <jlturr...@mail.com> wrote: >>>> >>>> Apparently, the ooRexx developers are happy with their crippled >>>> implementation of these emulated commands, since their response to my bug >>>> report is essentially, 'working as designed,' as IBM would have said (or >>>> broken as designed, as IBM users sometimes have been wont to say about >>>> broken >>>> features). >>>> See https://sourceforge.net/p/oorexx/bugs/1350/ >>>> >>>> Leslie >>>> >>>> On Tuesday 18 August 2015 05:35:03 J. Leslie Turriff wrote: >>>>> The Rexx Extensions Library Reference (sort of) documents the HI, TS and >>>>> TE immediate commands (syntax only) but does not explain how they are >>>>> used. >>>>> When a Rexx program is running and I type TS on the command line the >>>>> system >>>>> >>>>> does not recognize it. I get one of two messages: >>>>>> sh: TS: command not found >>>>> >>>>> which is output from bash if I type it on the console where the >>>>> Rexx >>>>> program is running; or >>>>> >>>>>> If 'ts' is not a typo you can use command-not-found to lookup the >>>>>> package >>>>> >>>>> that contains it, like this: >>>>>> cnf ts >>>>> >>>>> if I type the command on another console. >>>>> >>>>> Prefacing it with 'rexx' does not help. So, how are these used in the >>>>> *nix environment? >>>> >>>> >>>> >>>> -- >>>> A Caution to Everybody >>>> >>>> Consider the Auk; >>>> Becoming extinct because he forgot how to fly, and could only walk. >>>> Consider man, who may well become extinct >>>> Because he forgot how to walk and learned how to fly before he thinked. >>>> >>>> -- Ogden Nash >>>> >>>> ------------------------------------------------------------------------------ >>>> _______________________________________________ >>>> Oorexx-users mailing list >>>> Oorexx-users@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/oorexx-users >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> >>> >>> _______________________________________________ >>> Oorexx-users mailing list >>> Oorexx-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/oorexx-users >>> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Oorexx-users mailing list >> Oorexx-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-users > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > Oorexx-users mailing list > Oorexx-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-users > ------------------------------------------------------------------------------ _______________________________________________ Oorexx-users mailing list Oorexx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-users
