IMHO the problem here is probably one of misunderstanding or misapplication (Dr. Merrill's pointing out of a JCL oddity, for example) and any zapping or BSAM programming is likely to turn it into a real problem of corrupted data on disk.
The questions should be "how do we correct our error and read the data?" and not "how do we zap the data to make it fit our model of correct?" Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Blaicher, Christopher Y. Sent: Tuesday, July 19, 2016 12:07 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Bsam VS Qsam for VB records The I/O ERROR message should have a CCHHR associated with it. Using the CCHHR you can use AMASPZAP to dump that record or all the records on that track. You can then examine the record in question and determine if the BDW is correct, BDW should equal the block length reported by AMASPZAP, or if an RDW is incorrect. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
