Pnina, Consider zapping the dataset entry (fmt1dscb) in the vtoc (or, if you are a CA client and has DMS, use DMS utility described in SPL). If you need instruction how to zap, please tell.
Best, ITschak ITschak Mugzach Z/OS, ISV Products and Application Security & Risk Assessments Professional On Wed, Jun 15, 2016 at 12:38 PM, פנינה קוניגסברג <penin...@education.gov.il > wrote: > Thanks for the amazingly rapid reply. > > A little bit more info : the original dcb was lrecl=80, blksize=27290, > recfm=fb dsorg=po. > The file as modified by IDCAMS is lrecl=125, blksize > =27920,recfm=vba,dsorg=po > > Built 2 sequential output files, each with the dcb paramaters of before & > after > When writing to the seq lrecl 80 file received IEB311I CONFLICTING DCB > PARAMETERS > when writing to the lrecl 125 received IEB351I I/O ERROR ,XXXXXXX, > ,138C,D,SYSUT1 ,READ ,WRNG.LEN.RECORD,00002517000000,BSAM > > BTW, there was one crucial member that I reconstructed using DITTO VOLUME > BROWSE and copy/paste . but I don't see myself doing that for 150 members - > > > . > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Clifford McNeill > Sent: Wednesday, June 15, 2016 6:49 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Read a PDS (all members) like PS dataset > > You could try to open, write, and close the PDS with the original LRECL > and BLKSIZE, IEBGENER will do fine. Then you should be able to recover the > previous members. Of course, get a backup first. > > Cliff McNeill > > > ________________________________ > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf > of ????? ????????? <penin...@education.gov.il> > Sent: Wednesday, June 15, 2016 10:39 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Read a PDS (all members) like PS dataset > > Always interesting, I am dealing this week with an error that I hoped > would be solved by the different solutions presented here, but after trying > some of the solutions presented herein have not recovered. > Background: In preparation for a system cutover, executed IDCAMS LISTC > with SYSPRINT to a PDS file containing very important cutover data. > (thought that was an efficient method of documentation :) - the laugh > is on me). > The original file was a typical jcl type (80 lrecl) after running the > LISTC and updating the results, the PDS members which existed prior to the > LISTC job execution were unreadable - IO ERROR. Since the disk was a > 'sandbox' type disk, it wasn't backed up nor dumped. I have been trying > various recovery methods - many of them as advised on this discussion list > to not avail. Any ideas ? Would it be preferable for me to specify the > actions I already did to try to recover the file? > > . > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of CM Poncelet > Sent: Wednesday, June 15, 2016 8:53 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Read a PDS (all members) like PS dataset > > Yes it works, although I used it with the STOW macro (afterwards) to > modify/update PDS directories. Use the List/Execute forms of the DCB > Macro/DSECT if it is to be modified (in getmained storage). > > The FIND macro can then be used to locate the start of each PDS member > returned by the BLDL. From there, read each PDS member in turn (some > Open/Read/Closes might be needed). > > BTW My correction: IEBUPDTE can write (but not read, AFAIK) a PS dataset > to a PDS. But IEBCOPY can read a PDS and write it to a PS - and vice versa. > > Paul Gilmartin wrote: > > >On Wed, 15 Jun 2016 04:14:04 +0100, CM Poncelet wrote: > > > > > >>I would suggest writing some assembler code that invokes the BLDL > >>macro to read the PDS directory, ... > >> > >> > >> > >Does that work? > > > >-- gil > > > >---------------------------------------------------------------------- > >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 > > ---------------------------------------------------------------------- > 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 > > ---------------------------------------------------------------------- > 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
