Jake, Please post complete messages.
Go to option 3.4 and view TKOL01. Use PF11 to move through the panel displays. Do all datasets except this one look valid? If not, you may have a larger issue. Did you recently init this volume? Is the dataset in a usercat or master cat? Is that catalog available for that system? Can you access the dataset from any other system? If not, you can do a couple of steps. 1) If possible, vary the device offline/online to all systems. 2) Dump the VTOC of the volume. Rebuilding the IXVTOC will not necessarily fix your issue. You need to determine the actual problem first. If all datasets but this one are available, it is possible someone left a catalog entry and not the physical dataset. You may need to recover your file. Identify when the last good backup of this volume occurred. And verify if you have other backups of the files on this volume. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Jake anderson > Sent: Thursday, January 09, 2014 1:58 AM > To: [email protected] > Subject: Re: VTOC index broken > > Apology for the wrong header(Not a VTOC index problem).. The volumes are > accessible from other LPAR but not sure why it is stopping me to access these > volumes from the current LPAR. > > > On Thu, Jan 9, 2014 at 2:20 PM, Jake anderson > <[email protected]>wrote: > > > Hello, > > > > I am trying to access some of the dataset sitting on a particular > > volume called TKOL01,but I end up with the error: > > > > IEC143I 213-18,IFG0196X > > > > Manual : 18 An I/O error occurred in writing back a format-1 DSCB. > > > > Will it be safe to run a build index Job. Post the Buildix the > > Datasets would be accessible on that particular volume ? > > > > Jake > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
