4OS2 and REXX

[Batchheizer]

I'm updating the TAME-WPI/INF. There is one sentence concerning 4OS/2:

3. Make sure that OS/2 own CMD processor is used. Usage of 4OS2 isn't supported at all as it shows severe errors together with ReXX (default in eCS).

Is that correct?

[andi.b]

I'm not aware of such errors but that does not mean that they do not exist. Only 'it shows severe errors together with ReXX' is a little bit too less specific to do anything with it. I think this statement is from Klaus S., isn't it? No clue how to contact him and if he remember the details.

Moreover AFAIK 4os2 is not specified with COMSPEC with default eCS installation. At least I've never seen it with various 2.xRCx installations. Will check with my eCS2.1D. On the other hand most times I did not select 4os2 in advanced installation cause I've my 4os2 at the application partition anyway. Which version of eCS sets COMSPEC= to 4os2?

There's a chance that Steven knows more about REXX incompatibilities. But as long as it is not assured that eCS sets COMSPEC to 4os2, I think we should not bother him with this.

[Steven Levine]

I'm not sure why this statement was made. I run 4OS enabled with both OS2_SHELL and COMSPEC on all my systems, unless I happen to be lazy. I also run OREXX as the default REXX.

If someone can provide a testcase of the so-called failures, we will be glad to look at them.

I do know of one REXX defect that is related to 4OS2. Under some circumstances, REXX gets confused when asked to run a 4OS2 script and claims that the 4OS2 script is a REXX script. Clearly REXX is confused.

[Batchheizer]

To Andib: the remark "default in eCS" means, that 4OS/2 is by default NOT used.

To Steven: So I will remove the line from "Basic Prerequisites" in the updated INF and will put a hint to Troubleshooting.

Thanks for your comments.