On Mon, 8 Aug 2011 07:06:45 -0500 Donald Likens <dlik...@infosecinc.com> wrote:
:>I need to update common storage from my IEFU85 SMF exit. I am currently using a compare and swap loop to serialize on this update but I think there is a problem with this approach and looking at using SETLOCK. My question is... Why do you think there is a problem with this approach? Also, have you considered PLO? :>IEFU85 is in cross memory mode. I need the CMS lock. To get the CMS lock you must have the CML or LOCAL lock first. Since IEFU85 is in cross memory mode must I get the CML lock or can I get the LOCAL lock? Why do you - need - the CMS lock? Also, U85 may already be locked. :>Part 2: If I must get the CML lock which address space should I place in R11? It must be an address space that you have a bind to. As you are arbitrarily taking the lock .... :>Note: I never used locking before so if I have stated anything incorrectly, please correct me. I also have not delted with cross memory before. Be careful. Look for another solution. :>Part 3: To issue the SETLOCK command, do I have to worry about AR mode before issuing in an SMF exit? The documentation of the SETLOCK macro answers this question. This is not a game to be played without reading the rules. -- Binyamin Dissen <bdis...@dissensoftware.com> 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html