On Mon, 14 Jul 2008 08:25:06 -0500, David Waldman <[EMAIL PROTECTED]> wrote:
>We tried to run 3.5 on our z/OS 1.9 system. We had problems because we >have ALLOWUSERKEYCSA(NO). Jobtrac would abend. CA's official response >was to step-up to r11 on 1.9. > >Ironically, with the ALLOWUSERKEYCSA parameter set to "NO", Datacom had >to be setup to use a Global data space. This required an additional started- >task. > I'll probably get flamed for this but... While I applaud IBM for finally making this change and all the vendors who are modifying their code for this (and Sam K. and others for pushing the vendors), I really don't have a problem running with ALLOWUSERKEYCSA(YES) on my systems at this point. The exposure has been there forever and making it go away overnight (in relative terms of time) just isn't a big concern for me. I remember having to run JES2 jobclass definitions with SWA=BELOW for many years after MVS/XA (some shops might still have a few classes defined for SWA=BELOW). And getting to CSCBLOC=ABOVE took some time also. I realize it is a different issue since ALLOWUSERKEYCSA involves system integrity, I just am not going to lose any sleep over it at this point. Talk to me again in a couple of years... Mark -- 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
