New Xy-OS/2 Shell, RexxUtil, & the Future XyWWWeb Scripting Language under all OSes

[Robert Holmgren holmgren@xxxxxxxx]

For OS/2 XyWriters Only (or anyone interested in controlling
=== ==== ========= ==== their operating system from XyWrite)

As you may know, FixPack 13 represents a watershed in OS/2 development.
The core services and files of Warp Server (WSeB) and Warp 4 client are
now identical. Moreover, the new RexxUtil.DLL function library
distributed in FP13 offers complete cross-platform compatibility with
IBM's Linux, AIX, and Virus95/98/NT/2000 implementations of Rexx.
Powerful new functions are included in this RexxUtil.

NOTE WELL: **We do NOT encourage anyone to install FP13!**
Many glitches unrelated to Rexx have emerged, requiring incremental
fixes, which will be consolidated in FP 14, due shortly (see
ftp://service.boulder.ibm.com/ps/products/os2/fixes/v4warp/english-us/xr_m013/.message).

HOWEVER, we DO encourage all users to install the new RexxUtil.DLL now.
It works with all earlier versions of OS/2 Warp 4, and does NOT require
the installation of any new fixpack. It has enabled us to make
significant improvements to the Xy-OS/2 Shell embedded within XYWWWEB.U2.

Soon -- after a few more revisions of XYWWWEB.U2 (currently at version 97)
-- the new RexxUtil.DLL will be **REQUIRED** for users of the Xy-OS/2
Shell. A general description of Xy-OS/2 Shell is appended below. Our new
Shell is faster, more user-friendly, and much easier to install; see the
partial list of improvements and changes below.

In the longer term, we have decided, after lengthy debate, to adopt Rexx
as our cross-platform scripting language for manipulation of any operating
system from within XyWrite. The reasons are simple. The Linux and OS/2
versions are free, while the Windows interpreter costs US$ 49; see further
http://www-4.ibm.com/software/ad/obj-rexx/download.html#forfree. Rexx is
very powerful, relatively easy to code, innoculated against viruses, and
we already use it extensively. (If we hear any clamor for implementation
of the Shell under other OSes, we are prepared to give it a high
developmental priority.)

Anyone who wishes to test the new Shell during the present beta phase
may contact me by E-mail (holmgren@xxxxxxxx); the latest builds of Shell
beta will be available at XyWWWeb, and feedback will be thoroughly (and
gratefully) evaluated.

Both the Classic Rexx and Object Rexx versions of IBM Rexx for OS/2 work
interchangeably with Xy-OS/2 Shell -- it does not matter which one you
choose to install. Note that if you toggle between Classic Rexx and
Object Rexx (using SWITCHRX.CMD), you will need to acquire *both* new DLLs
as well as file REXXCRT.DLL.

I do not know whether these new Rexx DLLs work with Warp 3. Anyone using
Warp 3 (or anyone unwilling to upgrade to the new RexxUtil.DLLs) may
contact me for instructions on preserving old Shell (version 1)
functionality under forthcoming releases of XYWWWEB.U2. Likewise, anyone
with questions, don't be shy, send me a message. (As with Xy3, so with
Warp 3: why not upgrade to v4?)


To obtain new RexxUtil.DLL(s) from Warp 4 FP13:
----------------------------------------------
These DLLs work with all versions of OS/2 Warp v4.

 Backup old files:
copy [OS/2_Boot_Drive]:\OS2\DLL\REXXUTIL.DLL REXXUTIL.Old
copy [OS/2_Boot_Drive]:\OS2\DLL\REXXCRT.DLL REXXCRT.Old
 *One* of the following two files should be present also:
copy [OS/2_Boot_Drive]:\OS2\DLL\CREXUTIL.DLL CREXUTIL.Old
 or
copy [OS/2_Boot_Drive]:\OS2\DLL\OREXUTIL.DLL OREXUTIL.Old

 Download Classic Rexx DLL:
ftp://service.boulder.ibm.com/ps/products/os2/rsu/xr_m013/xr_m013e.zip
 and/or Download Object Rexx DLLs (2 files):
ftp://service.boulder.ibm.com/ps/products/os2/rsu/xr_m013/xr_m013f.zip
ftp://service.boulder.ibm.com/ps/products/os2/fixes/v4warp/english-us/xr_m013/rexxcrt.zip

 Extract DLL for Classic Rexx:
unzip -j xr_m013e.zip fix\os2.1\rexxutil.dl_
 and/or Extract DLLs for Object Rexx (2 files):
unzip -j xr_m013f.zip fix\os2.1\orxutil2.dl_
unzip rexxcrt.zip rexxcrt.dll

 Decompress Classic Rexx DLL:
unpack rexxutil.dl_ (should result in REXXUTIL.DLL, 68119 bytes, 3/27/00)
 and/or Decompress Object Rexx DLL:
unpack orxutil2.dl_ (should result in OREXUTIL.DLL, 42823 bytes, 3/27/00)

 Determine whether you're currently running Classic or Object Rexx, and
 then copy the operative DLL to [OS/2_Boot_Drive]:\OS2\DLL\REXXUTIL.DLL
for Classic Rexx, copy REXXUTIL.DLL derived from xr_m013e.zip
 or else
for Object Rexx, copy OREXUTIL.DLL derived from xr_m013f.zip
 The *other* file, representing the RexxUtil.DLL that you are NOT
 currently using, should be copied to [OS/2_Boot_Drive]:\OS2\DLL as
for Object Rexx, OREXUTIL.DLL
for Classic Rexx, CREXUTIL.DLL
 Thus it stands in readiness to be SWITCHRXed, i.e. toggled into
 activity.

 Finally, if planning to run Object Rexx now or in future:
copy REXXCRT.DLL to [OS/2_Boot_Drive]:\OS2\DLL


Changes in Xy-OS/2 Shell Version 2 (5/29/00)
----------------------------------
REQUIRES: new REXXUTIL.DLL(s) from Warp 4 FP13+
NEW: If Switch-to Process is a (sub)string of more than one process in the
 Tasklist, SW.CMD asks user to choose between processes that match the
 Switch-Process "hint"
NEW: If Exit-Process is a (sub)string of more than one process in the
 Tasklist, both O2.CMD and SW.CMD ask user to choose between processes
 that match the Exit-Process "hint"
NEW: Faster user input; much more precise, reliable task switching
NEW: Improved use of Rexx queues. No longer any chance of deleting a
 named queue used by other Rexx processes. At worst (and very rarely),
 one (empty) queue may be in existence, until deleted the next time
 either SW.CMD or O2.CMD is run.
NEW: Hard-coded "case=" user variable in both O2.CMD and SW.CMD,
 controlling the case sensitivity of either the Exit-Process (/P) or the
 Switch-Process. Case SeNsItIvE=1, Case INsensitive (Default)=0
NEW: Synonyms that can be used in O2-ALIAS.DAT aliases, or in CMline
  commands:
 %COMSPEC% - replaced by current command processor, e.g. "C:\OS2\CMD.EXE"
 %ROOT% - replaced by OS/2 BootDrive root directory, e.g. "C:\"
 For usage, see new sample O2-ALIAS.DAT scripts.
REMOVED: PMSW.EXE - replaced by new functions in RexxUtil.DLL
REMOVED: TL.EXE (old Window List launcher) - ditto
REMOVED: INSTALL.CMD - there is no longer a need to customize an
 installation's OS/2 BootDrive, COMSPEC, etc; these data now evaluated at
 runtime by the new Rexx scripts.
REMOVED: UserVariables in frames {{5go2}}, {{5runcmd}}, and {{5go2dos}} -
 Two U2 frames (O2 and SW) still need to be configured by user,
 as in version 1: frame O2, 9 User Variables; frame SW, 2 User Variables
FIXED: Old bug from version 1 that ignored /FS, /WIN, /MAX, etc switches
 under certain conditions
NEW: All but one alias removed from evaluation, for speed and simplicity
NEW: "Process Title" (e.g. S/G 662 of frame {{5o2}}) now *REQUIRES*
 quotes, even if there are no spaces in the title
MOVED: Special Exit_Process name "#" deleted from SW.CMD and introduced to
 O2.CMD. It launches a process "forever", i.e. does NOT "return" to an
 Exit_Process (usually XyWrite) upon termination. O2.CMD quits
 immediately after launching the process. Less system load, more
 reliable performance
CHANGED: Meaning of /L switch: the /L switch no longer takes an argument.
 It is now stated simply as '/L' (not '/L:launch_process_title' or
 '/L:"launch proc title"'). Otherwise /L performs the same old function:
 monitor a 'L'aunched process until it exits (then call exit_Process).
 Good for processes launched as , for some PM apps, for VIO apps
 that terminate by Aborting or Ctrl-C, etc.
REDUCED: tendency to crash XyWrite sessions after prolonged and repeated use
WARNING: Do NOT use O2.ICO with OS/2 v4 FixPack 13 (apparent conflict with
 STARTOS2.EXE)

What is Xy-OS/2 Shell?
---------------------
Shell to OS/2 to perform any native OS/2, MSWindows, or DOS task(s),
 individually or in combination, in background or foreground, full
 screen or windowed, Presentation Manager or DOS
launch OS/2 applications from the XyWrite command line, either filenames
 or objects(!)
switch from any running task to any running task, generally supplying
 just a "hint" of the process's Window List (Ctrl-Esc) Title
return to XyWrite automatically on completion of your OS/2 task(s)
start and maintain as many simultaneous OS/2 sessions as you wish
launched apps never consume memory in XyWrite's DOS session
no manual task switching (Alt-Esc, Ctrl-Esc)
no mousing around
no overt OS/2 interaction whatsoever (unless you intend otherwise)
import data from the operating system
add significant new power and possibility to XPL programming
prolong the life of a great DOS "legacy" app
EVEN: control OS/2 from a XyWrite cockpit!
AND: it's Freeware

Anybody who runs XyWrite under OS/2 is *NUTS* not to use Xy-OS/2 Shell!

[3 June 2000]


-----------
Robert Holmgren
holmgren@xxxxxxxx
-----------