home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Power-Programmierung
/
CD1.mdf
/
rexx
/
ntrexx
/
readme
next >
Wrap
Text File
|
1994-06-15
|
6KB
|
161 lines
rxsh
Pre-Release version 0.0.1
* * *
+--+--+
+===+
A Rexx-aware command shell for the
Microsoft Windows NT v3.5 Operating System
Copyright (c) 1994 Wm. Potvin II All Rights Reserved.
rxsh is a command shell much like cmd.exe which includes support for
the execution of Rexx EXECs via Quercus Systems Personal Rexx for
Windows NT. This functionality is *NOT* available via the IBM OS/2
Rexx implementation; rxsh *requires* Personal Rexx for Windows NT.
rxsh has been compiled and link-edited under MS Windows NT v3.5 and
the SDK for that system. rxsh has *NOT* been tested with Windows NT
v3.1, so it may or may not work on that system. rxsh has been tested
with the most recent Beta release of Quercus Systems Personal Rexx
for Windows NT as well as with the most recent Beta release of my
merxutil function package for Personal Rexx for Windows NT. rxsh does
not in and of itself require my merxutil function package, however
that function package does provide access to many Windows NT system
services from a Rexx EXEC. For more information, down load the help
file for the merxutil function package from the Quercus Library on
PCVENA in Library 11 on Compuserve.
rxsh is meant to compliment the rexx.exe program which ships with
Personal Rexx for Windows NT. rxsh will *NOT* run an EXEC which is
specified on the command line, i.e. "c:\>rxsh myexec.rex". To do
that, use the rexx.exe program that ships with Personal Rexx.
To run rxsh, simply execute the program either from a cmd.exe command
line, or by double-clicking the rxsh.exe file via File Manager, or by
using the File|Run menu option in either the Program Manager or the
File Manager. You may optionally create a PIF file for rxsh and
install it in a Program Manager Group. A sample PIF file, as well as
a sample icon file are provided in this distribution.
To quit rxsh, type either "exit" or "quit" on the command line. Note
that, as with cmd.exe, any changes made to the environment via SET
commands persist only for the life of the current shell. rxsh also
recognizes the more common prompt strings such as $p, $g, $t, $d, $l,
$$ and $_, plus introduces a couple of it's own:
$u - prints USERID env var, or username if USERID does not exist
$c - prints the computer name on which rxsh was started.
Thus, you might set a prompt such as:
rxsh c:\>set prompt=$u on $c in $p at $t on $d$_$$
which would produce the following, (for example):
rxsh bill on mersoft in C:\ at 19:24:16.202 on Wed 1994/06/15
$
rxsh is a *preliminary* shell implementation released to determine
interest. There are many features standard in mature shells which
are not present in rxsh. For example, rxsh does not read and
execute a startup file, (ala autoexec.nt). rxsh does not offer a
direct interface with the Rexx interpreter in the sense of being
able to enter a command such as:
rxsh c:\>if date('w')=='Wednesday' then say '"hump" day'
or
rxsh c:\>do 5; say 'hello'; end
on the command line. You can, however, issue cmd.exe batch language
commands on the command line:
rxsh c:\>if exist myfile.data echo found
rxsh does *NOT*, however, support the command "stacking" capability
that exists in cmd.exe, i.e. "cls&dir".
This preliminary implementation of rxsh is designed only to offer a
method of seamless execution of Rexx EXECs:
rxsh c:\>myexec.rex
as opposed to having to use the rexx.exe utility:
c:\>rexx myexec.rex
If it is determined that there is sufficient interest in rxsh, then
follow-on development will progress; startup file processing will be
added as will the ability to issue Rexx statements on the command
line. The "down" side to that is the fact that access to cmd.exe
batch language commands from the command line will disappear. Other
enhancements such as documentation and built-in help will also be
included.
Contact Information
Please send any comments to me at either of the following addresses:
70540,120 (from CompuServe directly)
70540.120@compuserve.com (from the Internet)
For information regarding Personal Rexx for Windows NT, contact
Quercus Systems:
Quercus Systems
P.O. Box 2157
Saratoga, CA 95070
(408)867-REXX (voice)
(408)867-7489 (fax)
(408)867-7488 (BBS)
Compuserve PCVENA, Library 11
Distribution File List:
rxsh.exe - rxsh program
rxsh.pif - sample PIF file
rxsh.ico - sample icon
readme - this file
Warranty/Licence
This Pre-Release software is Copyright 1994 William Potvin II. All
Rights Reserved.
The author of this Pre-Release software will, as revisions evolve, make
those revisions available via the Compuserve Information Service in the
Quercus section, (Library 11), of the PCVENA forum.
This Pre-Release software is provided by the author without any warranty
of any kind, either expressed or implied, including, but not limited to,
the fitness of this Pre-Release software for a particular purpose or
merchantability. The user holds all risk with respect to the quality
and performance of this Pre-Release software and the user assumes all
costs relative to all necessary servicing, repair or correction.
Under no circumstances will the author of this Pre-Release software be
liable to the user for any damages whatsoever, including general,
incidental or consequential damages resulting from the use, or from the
inability to use this Pre-Release software, including, but not limited
to loss of data or business profits or business interruption or a
failure of this Pre-Release software to operate with any other programs
or any other pecuniary loss sustained by you or third party users, even
if the author has been advised of the possibility of such damages.
The general availability of this software does not in any way imply
that it will ever be released as a product. This software will remain
in Pre-Release or Beta Release status at least until Personal Rexx for
Windows NT is released from Beta test.