On Mon, 14 Jan 2008 14:15:51 -0600, Ed Gould <[EMAIL PROTECTED]> wrote:
>> >> ------------------SNIP----------------------------- >> The real problem I've run into is that many sysprogs think you should >> never ACCEPT anything. I don't know where / when that was taught >> to sysprogs, but you'd be amazed how many live by that philosophy. >> >> --------------SNIP------------------- > >Mark: > >I think it has to do with these two reasons. >1. There is *NEVER* enough time after implementation to do so. b.s. Virtually all the work (research time, reviewing holds etc.) is with apply, not accept. And that is only for "large" products. >2. The proverbial it worked last year before you put the maintenance >on just go back the point and run my job. ?? Accept doesn't affect the running system / tgt libs. > >#2 is is typically some really important user and management has to >roll over and try and please him. ??? What does that have to do with the price of tea in China? -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
