> -----Original Message----- > From: Skip Robinson [mailto:[EMAIL PROTECTED] > Sent: Friday, October 26, 2007 12:54 PM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Re: z/OS 1.8 Conditional Storage Obtain/Getmain Return Code > > One consequence might be shooting oneself in the foot. Or one's customers. > > Check out OA22812 , which describes a problem configuring storage offline. > The problem is real, by the way; an APAR fix is available. <Snipped>
This kind of problem just reinforces my point. If the system routine invoked for CMSET SSARTO was 64-bit-clean, the high-order part of the register would not have been 'dirty', perhaps avoiding the abend. The source-level bug of not issuing SYSSTATE AMODE64(YES) when the code was executing in amode 64 might still have caused trouble, but at least the register would not have had leftovers in it to compound the issue. I do realize they probably can't all be done at once, but IMHO it ought to be a publicly stated IBM goal that all system interfaces *will* be 64-bit-clean no matter what amode they are invoked from. Peter This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- 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
