Danger: so long as you understand the risks. Not sure if it is possible in that environment to get back to user key but if you can it might be worthwhile.
WTO: well, the "legality" issue is not that the production police will come and take you downtown. The "legality" issue is that using it may cause odd and apparently unrelated results. STORAGE OBTAIN: I think under the covers it is the same service as GETMAIN. Again, in a test system, overhead may not matter. FWIW what I did in a ***VERY*** heavily driven production IEFU8x environment was use cell pool services one time to get a cell pool, and then on each call got and returned a cell from the pool to use as a work area. CELL pool GET is very lightweight. Note that IEFU83 is a "safer" situation than IEFU86, so lessons from an IEFU83 sample may not apply. For example, IEFU83 is not cross-memory, no locks and TCB. None of that is true for IEFU86. Charles -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Guillaume Boesel Sent: Saturday, July 8, 2023 10:05 AM To: [email protected] Subject: Re: IEFU86 WorkArea use ? Hi Charles, "This is not the environment for a learning exercise!" Yes I understand that it's dangerous. I'm working on my own system. "Is WTO even legal from IEFU86?" WTO is just used to test my exit. "STORAGE OBTAIN is a pretty "heavy" service to be using for every SMF record" IEFU83 sample in SAMPLIB uses getmain, is it lighter than storage obtain ? I use storage obtain because i'm not able to use the workarea safely. It was my initial question :) Thanks Guillaume
