Some senseless babbling from David Noon to Steve Mccrystal
on 08-31-99  19:20 about Classic REXX files?...

 DN> In a message dated 08-29-99, Steve Mccrystal said to All about
 DN> "Classic REXX files?"

 DN> Hi Steve,
 
 SM>Does anyone have (or has anyone seen) a list of all the 
 SM>files needed to use classic REXX?  Somehow, my CREXX files 
 SM>got munged, I suspect a FIXPAK, but I'm not sure.  In any 
 SM>case, it appears as tho some of the files are missing.
[snip]

 DN> The only files that differ, AFAIK, are REXX.DLL and REXX.INF. Your
 DN> CREXX ones should be called CREXX.DLL and CREXX.INF when you are
 DN> running OREXX, and when you are running CREXX the OREXX ones are called
 DN> OREXX.DLL and OREXX.INF.

 DN> You could try SWITCHRX and re-boot. This might switch you back to
 DN> OREXX. However, if you are running Warp 4 then the CSF should have
 DN> handled the REXX maintenance correctly regardless of which interpreter
 DN> you are running. 

There's also the following:

REX.MSG (CREX.MSG)
REXH.MSG (CREXH.MSG)
REXXUTIL.DLL (CREXUTIL.DLL)

I do believe, however, that REXX.DLL is all that's required for SAA REXX to 
function.  It'd probably simply display incorrect messages, or break when 
the need for a message arose, if the above two files were not replaced.  

I have no idea what would happen if one attempt to use OREXX's REXXUTIL 
library with SAA REXX.  I can't think of any reason why it wouldn't work.

Mike Ruskai
thannymeister@yahoo.com


... I'm not always right. Only 99.938742% of the time.

___ Blue Wave/QWK v2.20
--- Platinum Xpress/Win/Wildcat5! v3.0pr2
346/3
805/4