@JohnD I have not known DFDSS to truncate a dataset name.
Can you post the control cards you used to restore the file and the ADR messages that showed how it restored the file? The DB2 Names are very long to begin with, so if you changed the dataset name on restore, it might have just kicked it over the 44 char limit Otherwise that is a bug and should be reported. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of John Dawes > Sent: Friday, July 14, 2017 6:09 AM > To: [email protected] > Subject: Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E > > Another brilliant IBM moment. When I restored the dataset with a rename (DB2 > linear dsn) guess what?The new name CLUSTER was truncated. Besides the > message ADR418I it shows .A0 instead A001 .I wasted 30 minutes trying to > recatalog the cluster. Finally I ran a print of the VVDS entry of the volume > and lo and behold I found the cluster name.Thank you IBM for your useless > product (DFDSS) . Amen. > > From: John Dawes <[email protected]> > To: [email protected] > Sent: Friday, 14 July 2017, 7:18 > Subject: Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E > > Lizette, > The system default for DFDSS dump is set at 256K. Isn't that fantastic? Now > there is no way we can ever copy a tape to dasd because the lasrgest blksize > supported for a DASD dataset is 32760 bytes. IBM increased the blksize for > tape but not DASD. Brilliant !!!!!!! > > Thanks to all who responded. > > From: Lizette Koehler <[email protected]> > To: [email protected] > Sent: Thursday, 13 July 2017, 13:42 > Subject: Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E > > @JohnD > > I think the problem is the LBI. The DUMP tape was create with a HUGE > Blksize. You cannot copy that to DASD. Maybe you can change the way the > DUMP tape is created to use a BLKSIZE like 32760. Then you can probably use > COPYDUMP to copy it to DISK. > > From what I can tell, you could only copy tape to tape. > > Maybe restore the files to a disk, then backup the disk manually with DFDSS > > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of John Dawes > > Sent: Thursday, July 13, 2017 9:37 AM > > To: [email protected] > > Subject: Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E > > > > Rex, > > I tried your suggestion. I tried copying the tape to another tape > >using DCB=BLKSIZE=27998. However I got the same result :ADR331E > >(001)-CPYD (01), OUTPUT BLKSIZE 27998 FOR DATA SET ON DDNAME COPY1 IS > >SMALER THAN INPUT BLKSIZE 262144. > > From: "Pommier, Rex" <[email protected]> > > To: [email protected] > > Sent: Thursday, 13 July 2017, 12:15 > > Subject: Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E > > > > John, > > > > Based on error ADR331E, it appears that the only way you could do this > > would be if you had created the original tape backup using a block > > size of 32K - or 27998. That message explicitly states that you > > cannot copy a dump dataset to something with a smaller block size. > > > > Rex > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of John Dawes > > Sent: Thursday, July 13, 2017 10:24 AM > > To: [email protected] > > Subject: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E > > > > I am trying to copy a volume backup (which was created by DFDSS) to > > disk, using DFDSS. However I am encountering problems doing so.I tried > > using DCB=BLKSIZE=32760 to no avail. I tried running the job without > > the DCB and it returned the same result (ADR324E). According to the > > doc(SC23-6868- > > 01) this is feasible: > > > > "With the COPYDUMP command, you can make from 1 to 255 copies > >ofDFSMSdss- produced dump data. The data to be copied, a sequential > >data set, canbe on a tape or a DASD volume, and copies can be written to a > tape or a DASDvolume." > > Here is my job : > > //STEP1 EXEC PGM=ADRDSSU,REGION=0M,TIME=1440,PARM='UTILMSG=YES' > >//SYSPRINT DD SYSOUT=* > >//BACKUP DD > DISP=OLD, // > >DSN=HDFQ.DF > > DSS.TSB063.COPY1.WEEK(0) //COPY1 DD > >DISP=(,CATLG,DELETE), // > >DSN=SYS1.DF DSS.COPYTAPE, // > >UNIT=3390,VOL=SER=SPAR E1,, // > >SPACE=(CYL,(3200,20),RLSE),DCB=B > > LKSIZE=32760 //SYSIN DD > > * COPYDUMP - > > > >INDD(BACKUP) - > > OUTDD(COPY1) > > /* here is the output messages: > > COPYDUMP- > > > > INDD(BACKUP) - > > > > > > OUTDD(COPY1) > > > > > > ADR101I(R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND > > 'COPYDUMP ' > > > > ADR109I(R/I)-RI01 (01), 2017.194 10:55:25 INITIAL SCAN OF USER CONTROL > > STATEMEN > > > > ADR016I(001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK > > > > ADR006I(001)-STEND(01), 2017.194 10:55:25 EXECUTION BEGINS > > > > ADR331E(001)-CPYD (01), OUTPUT BLKSIZE 32760 FOR DATA SET ON DDNAME > > COPY1 IS SMALLERTHAN INPUT BLKSIZE 262144 > > > > ADR324E(001)-CPYD (01), THE VOLUME/DATA SET SPECIFIED BY DDNAME COPY1 > > HAS BECOME UNUSABLE > > > > ADR006I(001)-STEND(02), 2017.194 10:55:59 EXECUTION ENDS > > > > ADR013I(001)-CLTSK(01), 2017.194 10:55:59 TASK COMPLETED WITH RETURN > > CODE > > 0016 > > > > ADR012I(SCH)-DSSU (01), 2017.194 10:55:59 DFSMSDSS PROCESSING COMPLETE. > > HIGHEST > > > > TASK 001 > > > > > > Can someone advise me how to fix the problem? > > Thanks. > > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
