On 5 December 2014 at 16:34, Jim Mulder <[email protected]> wrote: I remember what happened in 1991 in SP4.2.0 when a code change and recompile of IEFSMFIE resulted in R10 no longer containing the address of the LCT when IEFUSE was invoked. [...] > SO, the module > was changed to set Reg 10 to the address of the LCT prior to invoking > the exits (copying the value from a local variable) AND arrangements > are being made to update the interface documentation in the User Exits > books to include this information. > > <end quote> > > So that's what happened, although it looks like the documentation > either didn't happen, or subsequently got lost.
I observe that in 2011 (not sure what release that would be), the "external classification" of the LCT itself was changed from DMTI to NOTPI. The comment says "8 char jobclass Feature ME22289", which seems hard to relate to a classification change. Was the change announced or documented? The DMTI itself was put in only as part of "SHOWHDR Compliance" in 1993, i.e. after the reversal you describe. I don't even remember what DMTI is or was; there used to be GUPI and PSPI (General Use- and Product Sensitive- Programming Interface, respectively), then simplified to just PI or NOTPI. Was DMTI just an older way of saying NOTPI? It seems not, since all the above strings still occur in a current MACLIB. Are these classifications documented somewhere? Regardless, it seems that any non-IBM use of any LCT fields may be suspect. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
