Walt, I think there was a change to GETMAIN behavior, but it's rather subtle (low-end vs. high-end page-filling), and this part was merely to reassure everyone that from a program's point-of-view, nothing was really any different.
The key words are "remain unchanged". The behavior (which is the same as it's always been) is re-iterated for your convenience. Proper programming insures all variables are initialized, so this behavior should be irrelevant. However, programs often clear newly acquired storage for convenience or aesthetics. The main point of the clearing rule is that you should *not* clear storage when the system has done it already because that wastes resources. The APAR has nothing to do with CICS GETMAIN. Read CICS doc for how that works. sas On Thu, Nov 19, 2015 at 10:07 AM, Walt Farrell <walt.farr...@gmail.com> wrote: > On Thu, 19 Nov 2015 14:52:33 +0000, Leonard.John.J < > johnleon...@westfieldgrp.com> wrote: > > >Virtual Storage Manager in z/OS 1.10 HBB7750 which results in different > behavior when storage is Getmained > >We are trying to understand the ramifications of this change to the > GETMAIN and I was wondering if anyone else has dealt with this. I >have > this document that says > ... snipped... > > As I recall that documentation was not describing a change to GETMAIN > behavior, but merely documenting more clearly how it has worked for a very > long time. In any case, it is not up to you to determine whether > vendor-supplied GETMAINs are working nor to fix them; that's entirely up to > the vendor. > > By the way, I believe that z/OS V1.10 is long out of support. If you're > still using it I would say that is of far more importance than any > considerations of how GETMAIN might work. Also, I think your question is > more appropriate for the IBM-MAIN list (as it deals with z/OS) than the > ASSEMBLER list (which deals specifically with the assembler and the > hardware architecture). > > -- > Walt > -- sas
