If a dataset of any sort -- especially a PDS -- is shared for write among two or more systems with no explicit provision for managing the sharing then corruption is an inevitable outcome. If you and I were both writing on the same piece of paper without any attempt at coordination, would what we wrote be likely to make any sense?
Others can tell you more than I about the specific sharing mechanisms that you need to set up. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Sent: Sunday, March 18, 2018 11:44 AM To: [email protected] 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
