This sounds like a debugging routine. It would seem logical to process all the variables with you default buffer size and then individually get the ones that were truncated.
On Wed, 17 Mar 2021 06:25:44 -0500 Willy Jensen <willy.h.jen...@outlook.com> wrote: :>The reason is that IRXEXCOM GET does a MOVE, meaning that you must already have a buffer big enough to hold the data. For a normal GET you can just redo the request with a bigger buffer and IRXEXCOM will tell you how big it needs to be. For GETNEXT however you must start again from the top as a a specific GET will destroy the information that REXX stored for GETNEXT. At least that is how I read the documentation, and experimentation seems to prove it. :>So perhaps what I really need is a GET LOCATE. -- 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...@listserv.ua.edu with the message: INFO IBM-MAIN
