FYI, the GA version of the PTF is available for this. While we didn’t see the problem either, this is one of those that could be very pervasive and maybe not noticed for awhile...
_________________________________________________________________ Dave Jousma Manager Mainframe Engineering, Assistant Vice President [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jesse 1 Robinson Sent: Tuesday, October 03, 2017 5:28 PM To: [email protected] Subject: Re: APAR OA53994 **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Even though we are not aware of having the problem, we've been pursuing the ++APAR fix just in case. In order to APPLY CHECK it cleanly, we had to include a cousin PTF that we had not yet received, let alone applied: UA92697. That PTF is also PEed but fixed by the same APAR. Level 2 didn't seem to understand our problem. IBM does advise, after all, receiving all maintenance on a regular basis. We don't. ;-( Just be aware that if UA92697 is not already installed (before it went PE presumably), then you need to include it in the same apply job with AA53994. BTW we're inclined to wait for the GA PTF. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jousma, David Sent: Monday, October 02, 2017 6:03 AM To: [email protected] Subject: (External):Re: APAR OA53994 All, just an FYI, we are in the middle of a maintenance cycle, and happened to pick up these offending PTF's awhile back. IBM does have an APARFIX available. I'm working with them trying to gauge the confidence level in it. They have updated the text of the APAR to include the conditions required for it to occur. Probably a fairly rare case, but good to close the hole. ERROR DESCRIPTION: During CLOSE processing of an extended format dataset, a logic error occurs causing the blocks at the end of the dataset to not be written out to the dataset if the I/O has not completed yet. Conditions for problem to occur: - QSAM and OUTPUT - Physical Sequential Extended Format dataset - During close processing, the dataset must run out of space in the current extent. This will drive EOV processing to get a new extent and re-drive i/o. - The i/o must not complete before we get to the invalid code path. If it completes, there is no problem. _________________________________________________________________ Dave Jousma Manager Mainframe Engineering, Assistant Vice President [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: Jousma, David Sent: Monday, October 02, 2017 7:51 AM To: 'IBM Mainframe Discussion List' Subject: RE: APAR OA53994 Thanks for the heads up Skip. _________________________________________________________________ Dave Jousma Manager Mainframe Engineering, Assistant Vice President [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jesse 1 Robinson Sent: Friday, September 29, 2017 3:11 PM To: [email protected] Subject: APAR OA53994 I just got a notice from ASAP that APAR OA53994 has PEed PTF UA91904 , which we installed in July. It looks pretty serious: records dropped at the end of an extended format sequential file. We have had no reports of such a problem, but it's pretty worrying. Has anyone stumbled on this crack in the sidewalk? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office <===== NEW [email protected]<mailto:[email protected]> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
