Folks I am finally getting around to modifying our IEFUSI exit to do something sensible with MEMLIMIT as more tasks exploit 64-bit storage. This exit has lain untouched for many many years, although it still functions correctly for the things it is supposed to do with region size.
However, now I come to look at it, it becomes my responsibility to fix any anomalies I find. The first of these is the alarming comment: * ON ENTRY R10 POINTS TO THE LCT. * SEE MICROFICHE OF IEFSMFIE AT CURRENT PTF LEVEL COS IT'S * POSSIBLE FOR THIS TO CHANGE The documentation for IEFUSI makes no reference to R10 pointing to the LCT, indeed it states that R2-R12 are not applicable. My investigations have determined that R10 does indeed point to the LCT, but how long this will remain the case is not for me to gamble on, so I have to find another way. The exit uses LCTSCTVA as input to SWAREQ to get to the SCTX via the SCT. It then takes a copy of the SCTX using IEFQMREQ and updates (in certain circumstances) the SCTXSTL value and re-writes the SCTX using IEFQMREQ. Given that I can’t rely on R10 pointing to the LCT, should I be using JSCSCTP from the JSCB to get the SCT SVA token for SWAREQ (even though it is not part of GUPI)? Any enlightenment appreciated! Thanks Andrew ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
