From: ptjm@interlog.com (Patrick TJ McPhee)
Subject: Re: Want to run REXX CMD files on a NT Box
Date: Tue, 21 Oct 1997 00:00:00 GMT
Message-ID: <62h43u$e4t$1@news.interlog.com>
References: <01bcddad$ff3d2810$15417392@gizmo>
Organization: Crampton Vinegar Works
Newsgroups: comp.lang.rexx


In article <01bcddad$ff3d2810$15417392@gizmo>,
jason dubreuil <asdf@asdf.com> wrote:
% Is there a way that i can configure a nt 4.0 machine to run simple rexx
% programs.


First, you need to get hold of a rexx interpreter. You can purchase one from
IBM, Quercus Systems or one or two other vendors whose names I don't know,
or you can down-load Regina from http://www.lightlink.com/hessling.

Regina is currently lacking the support libraries (rexxftp, rexxutil et al)
that come with IBM's Rexx, but that stuff is under development and will
appear over time. The most common rexxutil routine I use is SysFileTree,
and this can be replaced in regina by a non-standard interface to external
programs:
 parse arg fname .
 files = 'dir'('/b', fname)

Once you have a rexx interpreter, you can associate the executable with
files with the .rex extension (I think the GUI will prompt you for an
executable if you click on a .rex file in the file manager).

Once you've got the association set, you can set an environment variable
(I think it's called PATHEXT) which tells the command-line to treat .rex
files as executiable files. From that point, creating a file with a .rex
extension will be the same as creating a file with a .cmd extension in
OS/2, more or less.

To find the correct environment variable, type 'set > file' to dump the
environment to a file, and search for a line that's something like:
 PATHEXT=.bat;.cmd;.exe;.com

Note that when you set this variable, you must include all those
extensions or, for instance, .exe files won't run.

Hope that helps.
--

Patrick TJ McPhee
East York  Canada
ptjm@interlog.com