Files
org-hyperion-cules/README.REXX
Jan Jaeger 08d4ad5068 Add ABORT config statement
git-svn-id: file:///home/jj/hercules.svn/trunk@6424 956126f8-22a0-4046-8f4a-272fa8102e63
2010-09-10 06:07:18 +00:00

60 lines
1.5 KiB
Rexx

Hercules REXX support
Note: This documentation is incomplete, REXX support is still being further developed
REXX support is currently based on the regina-rexx package
To build Hercules with REXX support the regina3-dev package is needed
The default command environment is HERCULES
command errors may be handled with SIGNAL ON ERROR
command faulures may be handles with SIGNAL ON FAILURE
command returncodes < 0 are interpreted as ERROR returncodes > 0 are interpreted as FAILURE
e.g. command not found is an error
e.g. file not found on attach is a failure
The EXEC command may be used to explicitly invoke a REXX script, optional arguments will be passed
REXX will be invoked implicitly if existing script files start with /*
If REXX support is not installed, then /* will be ignored on the first line, */ will be treated as EOF, thus allowing for configuration, startup and script files that are bi-lingual
eg:
/* Classic config below
ARCHMODE S/370
.
.
.
*/
/* This is now where the REXX variant starts:
'ARCHMODE S/370'
.
.
.
exit
Hercules symbols can be retrieved as normal environment variables with value() or getvar()
Say 'LPARNAME=' value('LPARNAME',,'SYSTEM')
or
Say 'LPARNAME=' getenv('LPARNAME')
Not yet implemented are:
- capture output by means of ADDRESS 'HERCULES' command WITH OUTPUT STEM
- interactive trace input from the console
- stack underflow reads (pull) from the console
Partially:
- REXX support for the hercules.cnf config file
- bi-lingual config, rc + script files
Jan Jaeger