Try a IDCAMS PRINT DUMP of the offending record. Especially examine the BDW and RDW at the start of the block.
On Mon, Jul 18, 2016 at 2:21 PM, Campbell Jay <[email protected]> wrote: > Have a current SR open with IBM... 57827 082 000 > Our output is VB LRECL=31996 BLKSIZE=32000. > Using BUFL=32600 fixes our problem. > SR was opened to find out why that works. > > Jay Campbell > IBM OS Support Section > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Joe Reichman > Sent: Monday, July 18, 2016 3:17 PM > To: [email protected] > Subject: RDW corruption > > Hi, > > > > I have a program that generates a corrupted RDW The file is a VB file. I > coded a synad exit but it didn't take (it was never given control) > > > > When I go into ISPF and I do a max down I can see where ISPF can't read the > next record as I get "* * * I/O error detected, i/o terminated * * *" > > > > As there anything/exit I can do to capture this the program seems to go to > EOJ > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
