Sorry, my mind was misfiring a neuron. That should have been DISP=MOD on the SYSUT2 DD statement for Gener.
Sorry about that. Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Thursday, August 29, 2013 6:37 AM To: [email protected] Subject: Re: DFDSS problem I cannot guarantee this will work but two things to try. 1) Preallocate the new file with your attributes. Restore to that file. DFDSS may honor your file with the blksize you want. 2) Restore the file even if it gets a BLKSIZE of 0. Then use IEBGENER to do the following //SYSUT1 DD * /* yes a null entry //SYSUT2 DD DISP=OLD,DSN=yourfilename,BLKSIZE=4096,LRECL=... When IEBGENER opens and closes the file, it could use your BLKSIZE in the JCL to override what was restored. Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Bill Ashton Sent: Thursday, August 29, 2013 6:30 AM To: [email protected] Subject: Re: DFDSS problem I'm sorry for leaving all this out...my brain is a bit weary. The file is a PS file, F/4096, and is one of 3 files in the backup (the other two have the same results). It was quite a while ago on disk (when it was backed up), and there is no output to review, but I am assuming the backup worked fine, since the data in the backup file looks good/ We have no HSM backups or archives - only this DFDSS backup - to work with. On Thu, Aug 29, 2013 at 9:20 AM, Lizette Koehler <[email protected]>wrote: > If you could provide a little more detail. > > Is the file being restored VSAM, SEQ, PDS, PDSE? > > What will be the file attributes when restored? > > When was the file last on DASD? Was there a backup then? What was > the results? Any warning messages? > > > When was the file backed up? What jobstream. Did you review the last > backup to see if there were errors for this file? > > Do you have DFHSM? If so, is there an HSM Backup of the file? HLIST > DSN(filename) BCDS will let you know > > If there is a DFHSM Backup then HRECOV filename should work > > Lizette > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Bill Ashton > Sent: Thursday, August 29, 2013 6:10 AM > To: [email protected] > Subject: Re: DFDSS problem > > Hi Lizette, and thanks for your note. I have done the restore with a > new name with no difference. I have also dumped the backup with > IDCAMS, and I can see the data, which looks like the right format - > there is a bunch of data as I expected. > > Unfortunately, the original file is no longer available, which is why > I am trying to get this backup to work. I have to say that I am not > the happiest guy at the moment. > > Billy > > > On Thu, Aug 29, 2013 at 8:52 AM, Lizette Koehler > <[email protected]>wrote: > > > Sometimes when I run into strange issues with DFDSS, I will bring > > the dataset back as a new name and then browse the file after it is > restored. > > > > If you are getting blksize 0 then maybe the file on backup is empty. > > > > I would try creating a new file: filename.recv (I use RECV as a > suffix > > so I know it is a recovered file.) and then browse it. > > > > It maybe that your file has no data. In which case I would just > > allocate it rather than trying to restore it. > > > > Lizette > > > > > > -----Original Message----- > > From: IBM Mainframe Discussion List > > [mailto:[email protected]] On Behalf Of Bill Ashton > > Sent: Thursday, August 29, 2013 5:43 AM > > To: [email protected] > > Subject: DFDSS problem > > > > Hello friends! > > I am trying to restore some files that were backed up with DFDSS > > some time ago, and I am having a problem with the results. > > > > If I let DFDSS allocate the file, I get an output file with a > > Blocksize of zero, although all the space amounts are fine. I then > > tried to use OUTDD(), and if I specify Blksize/Lrecl/Recfm or if I > > don't, I still get a Blocksize zero. > > > > If I specify the blocksize, I get this warning (but the file is > > Blksize > 0): > > ADR398W (001)-TDUNL(02), DATA SET xxx.xxx.xxx BLOCKSIZE OF 04096 IS > > INCORRECT. LARGEST BLOCKSIZE IS 4096. > > > > Does anyone have any idea what could be happening, or how I can > > override the DCB that DFDSS wants to use? I no longer have access to > > the backup job, so can't see the output. > > > > Here is my input: > > RESTORE DATASET(INCLUDE(xxx.xxx.xxx)) INDD(BKP) - > > OUTDD(FILE420) BYPASSACS(**) REPLACEU > > > > -- > > Thank you and best regards, > > *Billy Ashton* > > > > -------------------------------------------------------------------- > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO > > IBM-MAIN > > > > > > -- > Thank you and best regards, > *Billy Ashton* > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > -- Thank you and best regards, *Billy Ashton* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
