We know this, but this approach using TRAP2 seemed so much nicer to us
than our original 0C1 / ESPIE approach - no need to go through the RTM
processing -
that we gave it a try. We will be able to go back to the old approach
within hours or days, should it be necessary.
The updating of the DUCT is done using a private SVC routine which does
just this.
No security violation.
IIRC, TRAPx was invented by IBM to do something about the Y2K date
simulations,
that is, to support application testing: am I right? So even if it is
not supported by
the OSes, the original goal was to support application testing. So I
think we do it right,
given the original idea of IBM.
Kind regards
Bernd
Am 10.04.2013 14:05, schrieb Peter Relson:
wrap all content supervision (LOAD, LINK, XCTL
and ATTACH), RTM exit (ESTAE(X), STAE, (E)SPIE and SETFRR) and selected
schedule (such as IEAMSCHD) service calls.
As all should understand, very little of this would be considered
supported in any way shape or form and if anything in this realm caused a
problem (or could conceivably have caused a problem), IBM service might
take a hard line about helping.
Peter Relson
z/OS Core Technology Design
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
