As those of you following my IEFU8x thread know, I've just taken over responsibility for some IEFU8x code. It needs some serious re-writing and while I've got a lot of 360 to Z experience, this is my first SMF exit, so I'd like to tap the collective wisdom of the group.
- What's the best way for the IEFU8x code to "find" its companion non-exit code? In the current code the non-exit module defines itself as a subsystem, anchors a table in SSCTSUSE, and then the IEFU83 exit scans the SSCT to find it by name. Is this recommended, or is there a better way? - What's the best way to parametize an IEFU8x exit? The existing code has a customization utility named AMASPZAP <g>. I obviously can't read a parameter file. It can't get the information from the SSCT technique described above because the sub-system name is one of the things that needs to be parametized. What do people recommend? - What's the best way for the IEFU8x code to pass messages to its companion non-exit code? The current code uses GETMAIN SP=241, CS, and an x-memory POST. It looks pretty good to me but is there a more recommended way? Thanks all. Note this code is all working so I don't need advice on getting any of the above-mentioned techniques to work (although pointing out very subtle gotchas is always helpful). I really want to know the best way to accomplish these things, big picture. Charles Mills ---------------------------------------------------------------------- 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
