I believe SYSB-II requires ALLOWUSERKEYCSA(NO). Some months ago, H&W sent out an email asking for guidance in setting a priority for modifying SYSB-II to make it work with YES. I don't know what kind of response they got, but, given the fact that there's been no fix, it doesn't appear that their customers thought it was a priority either. (I think I neglected to respond at all...)
Greg Shirey Ben E. Keith Co. -----Original Message----- From: IBM Mainframe Discussion List On Behalf Of Mark Zelden Sent: Monday, July 14, 2008 9:03 AM <snip> 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. ---------------------------------------------------------------------- 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
