On Wed, 17 Dec 2014 17:56:38 -0600 John Sullivan <[email protected]> wrote:
:>I have a problem in that the FRR Parameter Area (24 bytes) returned in SETFRR A,PARMAD= is too small! :>I am having to re-work some code to support 64-bit (and prior 31-bit) callers in SRB mode and am curious what others do in this situation. :>The 24 byte FRR Parameter area used to hold 6 registers but now only 3 for 64-bit support. :>The thought of getting storage and later freeing it seems expensive, just to have an "Extended FRR Parameter Area". :>FRR STACK size is fairly small, so not sure if getting 2 areas (2 SETFRR requests) and chaining them is likely to run out and lead to disaster. :>Also probably frowned upon, i.e. it is both ugly and asking for problems, especially if there is recursion (occasionally can happen). :>Anyone else hit this? :>And what have you done to get around it? I am sure that most have found even the 24 bytes to be insufficient in most cases and thus save a pointer to the real recovery stuff. I guess you were lucky to only require 24 bytes. You must certainly hate PC-ARRs, where you only have eight bytes of data to save for the recovery routine. -- 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: INFO IBM-MAIN
