Given your circumstance, it seems hat no service fix would work for you,
since no fix would be provided at all the releases you might require.
Again, is this a big deal?
CLI FLCARCH-PSA(0),0
JE NotZArch
SAM64
NotZArch DS 0H
If you have taken the trouble to write a program that will work whether you
are running z/Architecture or not, AMODE 64 or not, more power to you. We
have found that typically to be far more trouble than it's worth.
Regarding your question, you're certainly right that you must not change
the ETE.
Some circumstances might result in an abend prior to z/OS 1.8 (such as
setting ETDEAM, but providing a routine address that is above 16M -- it
falls into an old check pertaining to validating AMODE 24 things). It
actually does look like if you set ETDEAM and specify a routine name,
rather than providing an address, on your ETDEF (and your routine is in
LPA, nucleus, or your JPQ), things might work. Or even if your routine name
locates an entry that was bound as AMODE 64 (such that, for example,
CDENTPT has the low bit on), things might work.
Peter Relson
z/OS Core Technology Design
----------------------------------------------------------------------
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
