Just as a side note, I remember learning long ago to always initialize static areas, for example:
use DC .... instead of DS .... wherever possible (same equivalents for all languages). It follows that the rule same rule would be wise for dynamic storage. Seemed simple enough at the time. I do understand though why IBM had to come up with this, IMO, very generous "fix". Guy Gardoit z/OS Systems Programming On Thu, Feb 5, 2009 at 1:57 PM, Ted MacNEIL <[email protected]> wrote: > >For the life of me, I can't understand why this is such a surprise or > problem. > > I agree! > In 1976, I was taught, whether getmain, malloc, or whatever the memory > allocation method was, to always initialise, unless the function > specifically stated it would do it. > That was my first year university programming courses. > When in doubt, assume it's not initialised. > > > >How many bad programmers were-there/are-there anyway? > > Sadly, too many to count on fingers and toes. > And, unfortunately, they're not restricted to mickey-soft. > > If you allocated it, initialise it. > If you allocated, de-allocate it when you're done! > If you open it, close it. > If you ENQ it, DEQUEU it. > > Basic, but missed! > Too many times!!!!!!!!!!! > - > Too busy driving to stop for gas! > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
