------------------------------------------------------------------------
Chapter 2. Host Emulator (HostEmu)
*Table of Contents*
EXECIO subcommand <cid:part2.02040905.05080800@arrl.net>
HI subcommand <cid:part3.06000009.06030101@arrl.net>
TE subcommand <cid:part4.01030407.08030904@arrl.net>
TS subcommand <cid:part5.04080905.04000404@arrl.net>
HostEmu is a subcommand environment that partially emulates a TSO/CMS
environment. It provides a small subset of commands avaliable in those
environments which make the transition from a real host Rexx programming
environment to a Linux/Windows ooRexx environment much easier. The
following subcommands are available:
EXECIO
an I/O mechanism.
HI
halts the current Rexx program.
TE
deactivate the Rexx trace mechanism.
TS
activate the Rexx trace mechanism.
The HostEmu HI, TS, TE commands have no arguments that are acceptable in
the HostEmu environment. Thus their syntax is very simple. The EXECIO
subcommand is more complicated and requires some explanation. It is a
simplified version of the mainframe command but will provide most of the
functionality you will need on a daily basis.
To include and use the HostEmu subcommand environment you must place a
ooRexx directive in your script. The following shows how to accomplish this.
*::requires "hostemu" LIBRARY*
This will activate the environment. The subcommand name is "HostEmu"
(the case of this string is not important). You can send commands to
this environment via the ooRexx address statement. Here is an example.
*(Editor: T**he following allows you to use the EX**ECIO statement from
within your ooRexx program.*)
*address hostemu 'execio * diskr "./inputfile.txt" (finis stem in.'*
Note that the file name MUST be placed within a set of quotation marks.
The example above should look very familiar to a mainframe Rexx
programmer. The big difference is that a real file name is used instead
of a DDNAME and the HostEmu environment is not the default address
environment, thus the requirement that you either include the 'HostEmu'
environment name in the address statement or you make the 'HostEmu'
environment the default environment.
*Never tried to use the TS/TE commands. Not sure what good them are,
since I have better control with imbedded "TRACE xx" commands**
**
**I f debugging a very difficult routine, or one that takes a while to
get where the trace is useful then I use**conditional statement like**
**the following...**
*
*If i=5000 then trace I**
**
**
**if I=5002 then trace n*
On 08/23/2015 11:05 AM, J. Leslie Turriff wrote:
So, I guess nobody knows how these are supposed to work usefully in
ooRexx?
On Tuesday 18 August 2015 05:35:03 J. Leslie Turriff wrote:
The Rexx Extensions Library Reference (sort of) documents the HI, TS and
TE immediate commands (syntax only) but does not explain how they are used.
When a Rexx program is running and I type TS on the command line the system
does not recognize it. I get one of two messages:
sh: TS: command not found
which is output from bash if I type it on the console where the
Rexx
program is running; or
If 'ts' is not a typo you can use command-not-found to lookup the
package
that contains it, like this:
> cnf ts
if I type the command on another console.
Prefacing it with 'rexx' does not help. So, how are these used in the
*nix environment?
------------------------------------------------------------------------------
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
