John, you are correct! Unless you have absolute control over all of the libraries in the LINKLIST you should use CSVLLAxx otherwise you could accidentally install someone else's pre-staged change. In a large shop that is a real issue. ROT is to always go for the least possible impact to the system.
Jon L. Veilleux [EMAIL PROTECTED] (860) 636-2683 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of John Kington Sent: Thursday, September 18, 2008 9:16 AM To: [email protected] Subject: Re: Update datasets defined in lnklst Tom, > As DB2 guy, I used to religously use the CSVLLAxx member to avoid > impacting others. > > However, my main zos guru recommended to me a while back (maybe the > last > 2 ZOS releases?) that the benefits were so minimal now that it wasn't > worth the effort to code the CSVLLA route any longer, and to just go > ahead and do a total refresh each time. > > Anyone concur? > I prefer to use the parmlib member to limit the scope (and possible fallout) of updates to linklist but that just may be my conservative nature. If you are the only one in the kitchen, you can be sure that no one else is cooking another dish. Regards, John ---------------------------------------------------------------------- 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 This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna ---------------------------------------------------------------------- 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
