On Thu, 17 Jan 2008 00:15:31 -0600, Tony Harminc wrote:
>
>Then you write a REXX command environment handler (call it LINDYTSO or
>something, or even TSO if you want to be confusing; you can even make it the
>default), ATTACH each TSO command passing it a CPPL that you have set up,
>WAIT for it, and DETACH it. You have reinvented the TMP, sort of. IBM used
>to document how to write your own TMP, but withdrew (made OCO) the
>information needed in the 1980s. After all, why would any customer want to
>write their own replacement for IBM's fine IKJEFT01?
>
z/OS did much of this for us (including "TSO if you want to be confusing")
at v1r4:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/BPXZB630/CHANGES
Summary of changes
for SA22-7806-03
z/OS Version 1 Release 4
* Support for a TSO host command environment that permits a REXX
program to run TSO/E commands.
>Anyway - this works for most unauthorized commands, but to run APF auth
>commands requires a certain gung-ho attitude that may not be appreciated by
>all your colleagues sharing the same system.
>
It works for most authorized commands. But the TSO terminal interaction
design restrictions persist. For example, I have been unable to get
RECEIVE to work in that environment, presumably because of the DSN
prompt that must be answered. Can anyone else solve this?
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
