One of the more common reasons is someone updates the PDS with the incorrect DCB attributes.
Check out a backup dataset with the current on. Are the LRECL/BLKSIZE/DSORG all the same? If it is one module, see what happens if you copy the file without the member? Make sure you are not sharing the PDS across SYSPLEXs. Make sure your GRS functions are set correctly Lizette > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of > Peter > Sent: Sunday, March 18, 2018 11:44 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Reason for PDS corrupted > > Hi > > One of our loadlib dataset got corrupted and I get a message as An I/O error > was encountered reading the first record requested while trying to browse the > module. While I don't see any related message in syslog during this time. > > Also the started task trying to read that loadlib fails with s106 > > I understand this can be fixed by getting a copy from a backup but is there > any reason why it got corrupted ? This Dataset is shared between two zOS > system running on zVM and there are no serialisation set up. > > Please help me to understand why this happens and how can it be avoided in > future > > Peter > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
