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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, August 29, 2013 5:43 AM To: IBM-MAIN@LISTSERV.UA.EDU 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN