On 11/19/2010 10:57 AM, McKown, John wrote:
I know that I'm missing something, but that seems to be addressed here:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ikj4a370/14.14
These are instructions for updating IBM's TSO/E REXX environment parameters
modules. The difficulty in going down this road is identifying every IRXINIT
issuer under which your HCE might execute and then updating each and every
associated EPM to include an entry for your HCE. If the EPMs are not delivered
in source form, you will need to work with the developers.
It's pretty easy for ISPEXEC and ISREDIT to be in ISPF's EPM since they are
delivered by a single component. And, if your HCE is tied to ISPF, you can do
the same thing.
But, IRXINIT can be issued by *any* program. For example, our multi-user Phoenix
TP Monitor Environment does this and it has its own EPM. I suspect Netview has
its own, various IBM and ISV automation products have their own, and so forth.
Basically, *any* environment in which REXX EXECs might run will likely need to
be inspected and possibly customized.
I was envisioning something a bit more automatic and global in scope...
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
310-338-0400 x318
[email protected]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
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
