U84 & U85 may require an FRR in place of an ESTAE. On Mon, 19 Jul 2010 10:12:26 -0500 Dave Day <[email protected]> wrote:
:>Charles, :> This is what I do in my code. My code installs exits into IEFUSI and IEFACTRT. :> :> The server address space that installs the exits before doing anything else, queries the exits using CSVDYNEX REQUEST=LIST to determine if they are active on the system. I query for SYS., SYSJES2, SYSJES3, SYSSTC. By examining the output of the list request, you can determine if the exit you need is active. You can play around with the SMFPRMxx member to specify the exits in different exit points, and then watch the results of the list request to see how it changes. If you have XDC, its really easy to do. I have a data structure in my server that is updated with the status of he exit points as a result of the query. :> :> The server address space establishes a PC routine for use by the SMF exits. The PC routine adds work to the tail of a work-to-do chain, then posts the proper ecb. :> :> When the exit code itself is to be installed, I get ECSA storage, and move the code to it. At the beginning of the code area, there is a full word for an address, and a status flag. The status flag is checked by the exit code to determine if it should proceed, or just br 14. The full word I use as a pointer to a ECSA data area. This data area contains the status of the server address space, as well as the PC nbr to use. I do it this way so I don't have to chase the SSCT chain on every invocation of the exit. If you have a vendor word in the vendor table, use that. My code will be doing that soon. :> :> The exit code itself should be protected by an estae. And, the PC routine shoudl be protected by an arr or an estae. My server address space also sets a resource manager routine that will set the flag in the exit (if not set already), and set the ECSA data area to show the server is gone(if not set already). :> :> When the exits are installed, they are set as non-active. Last thing my server code does when it is ready to process is to run CSVDYNEX to set them active. 1st thing it does when it is terminating is to set them inactive. I believe it is CSVDYNEX REQUEST=MODIFY. The exit code itself is left in ECSA when the server comes down, but is anchored in the ECSA data area. That data area, once acquried, is there for the life of the IPL. I just need to re-activate the exit when the server comes back up. :> :> This works for me. Hope this helps. -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- 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
