In the course of our SR, there was never a hint of external problem indication. This is a logic error after all. Working as Coded, not as designed, so I would not expect any 'error code'. You would only know of a problem if a program reading the truncated file notices that something is missing at the end.
OTOH consider that the environment is pretty rarified. QSAM output to an extended format sequential file that gets 'distracted' at the very end by needing to grab an extra disk extent. What are the odds? The only responsible action is to install the fix and migrate it (via CLPA). In the meantime, you shouldn't lose too much sleep. . . 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 23, 2017 7:22 AM To: [email protected] Subject: (External):Re: APAR OA53994 I don't personally know. You might open an ETR with IBM asking that. We are in the middle of a maint cycle, so I included the now GA version of this PTF. Its worth mentioning that the PTF updates a LPA resident module. _________________________________________________________________ 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 Ward, Mike S Sent: Monday, October 23, 2017 9:05 AM To: [email protected] Subject: Re: APAR OA53994 **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Question, does the logic error produce any kind of message so that you can be warned of the potential problem? -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jousma, David Sent: Monday, October 02, 2017 8:03 AM To: [email protected] Subject: 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 **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** 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
