[Default] On 18 Jun 2017 09:38:24 -0700, in bit.listserv.ibm-main
[email protected] (Lizette Koehler) wrote:

If were trying to copy an Innovation Data Processing FDR dump tape
created with LBI to disk would it work using the equivalent of the
DF/DSS COPYDUMP command?  This is just a matter of curiosity.

Clark Morris
>John
>
>You are doing a copydump.  So this means, you are trying to make additional 
>copies of a DFDSS dump tape.  Is that correct?
>
>If not, what is the intent of coping the DUMP TAPE to DASD?
>
>
>
>With the COPYDUMP command, you can make from 1 to 255 copies of 
>DFSMSdss-produced dump data. The data to be copied, a sequential data set, can 
>be on a tape or a DASD volume, and copies can be written to a tape or a DASD 
>volume. If the dump data is produced from multiple DASD volumes by using a 
>physical data set dump operation, you can selectively copy the data from one 
>or more of those volumes.
>
>The COPYDUMP command cannot change the block size of the DFSMSdss dump data 
>set. If you are copying a dump data set to a DASD device, the source block 
>size must be small enough to fit on the target device.
>
>You can probably copy tape to tape, but I do not think you can copy tape to 
>disk with a DFDSSD Dump tape.
>
>You would need to change the way you create the DFDSS DUMP Tape to use the 
>BLKSIZE=32760 if that is going to be used in a COPYDUMP operation later.
>
>Lizette
>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List [mailto:[email protected]] On
>> Behalf Of John Dawes
>> Sent: Sunday, June 18, 2017 9:30 AM
>> To: [email protected]
>> Subject: Re: help with DFDSS and LBI (large block interface)
>> 
>> I am able to do a tape to tape copy without any issues.  However tape to disk
>> doesn't work because the default of tape blksize is 262144 and the maximum
>> blksize that is supported for DASD is 32760.  I guess nothing can be done.
>> --------------------------------------------
>> On Fri, 16/6/17, Carmen Vitullo <[email protected]> wrote:
>> 
>>  Subject: Re: help with DFDSS and LBI (large block interface)
>>  To: [email protected]
>>  Received: Friday, 16 June, 2017, 3:12 PM
>> 
>>  a better example
>>  tape to tape
>> 
>> 
>> 
>>  //STEP1 EXEC
>>  PGM=ADRDSSU
>>  //TAPEI DD
>>  DSN=OTCTR.OMVS19.DUMP,
>>  //
>>  UNIT=3390,VOL=SER=(OTCTR3,OTCTR4),DISP=SHR
>>  //TAPEO DD DSN=OTC.OMVS19.DUMP,
>>  // UNIT=3390,VOL=SER=(OTC047,OTC053),
>>  // DISP=(,CATLG),SPACE=(CYL,(1100,100))
>>  //SYSPRINT DD SYSOUT=*
>>  //SYSIN
>>  DD *
>>  COPYDUMP INDDNAME(TAPEI)
>>  OUTDDNAME(TAPEO)
>>  IF LASTCC GT 0 -
>>  THEN DO
>>  WTO
>>  '****************************************************'
>> 
>>  WTO '********* DSSU TAPE COPY HAS
>>  ABENDED ! *************'
>>  WTO
>>  '****************************************************'
>> 
>>  END
>>  ELSE DO
>>  WTO
>>  '****************************************************'
>> 
>>  WTO '*** DSSU TAPE COPY HAS COMPLETED
>>  SUCCESSFULLY ! ****'
>>  WTO
>>  '****************************************************'
>> 
>>  END
>>  ----- Original Message
>>  -----
>> 
>>  From: "Carmen
>>  Vitullo" <[email protected]>
>> 
>>  To: [email protected]
>> 
>>  Sent: Friday, June 16, 2017 2:11:17 PM
>>  Subject: Re: help with DFDSS and LBI (large  block interface)
>> 
>>  I've
>>  done this alot creating a second copy of a dump tape and  never forced a
>> blocksize -
>> 
>>  //STEP1 EXEC PGM=ADRDSSU
>>  //SYSPRINT DD SYSOUT=T
>>  //INVOL1 DD VOL=SER=RMDS01,UNIT=3380,DISP=SHR
>> 
>>  //TAPE1 DD
>>  DISP=(,CATLG),DSN=xxxxxxxxxxxxx,UNIT=T3480,DCB=X
>>  //SYSIN DD *
>> 
>>  /SYSIN DD *
>>  COPYDUMP
>>  INDDNAME(INVOL1) OUTDDNAME(TAPE1)
>>  IF LASTCC
>>  GT 0 -
>>  THEN DO
>>  WTO
>>  '*++++++++++++++++++++++++++++++++++++++++++++++++++*'
>> 
>>  WTO '********* COPYDUMP OF TECHD7
>>  ABENDED ! *************'
>>  WTO
>>  '*++++++++++++++++++++++++++++++++++++++++++++++++++*'
>> 
>>  END
>>  ELSE DO
>>  WTO
>>  '*++++++++++++++++++++++++++++++++++++++++++++++++++*'
>> 
>>  WTO '*** COPYDUMP OF TECHD7 COMPLETED
>>  SUCCESSFULLY ! ****'
>>  WTO
>>  '*++++++++++++++++++++++++++++++++++++++++++++++++++*'
>> 
>>  END ----- Original Message -----
>> 
>>  From: "Lizette
>>  Koehler" <[email protected]>
>> 
>>  To: [email protected]
>> 
>>  Sent: Friday, June 16, 2017 2:03:26 PM
>>  Subject: help with DFDSS and LBI (large block
>>  interface)
>> 
>>  This is from
>>  John Dawes who is having issues posting to IBMMAIN. I only  have the
>> following details
>> 
>>  G'Day,
>> 
>>  Here is the jcl:
>>  //STEP1 EXEC
>>  PGM=ADRDSSU,REGION=0M,TIME=1440,PARM='UTILMSG=YES'
>> 
>>  //SYSPRINT DD SYSOUT=*
>>  //BACKUP DD
>>  DISP=OLD,DSN=SYS2.STORDSK.BKUP.G0001V00
>>  //COPY1 DD DISP=(,CATLG,DELETE),
>>  // DSN=SYS2.DFDSS.BKUP2,
>>  //
>>  UNIT=3490,VOL=(,,,99),DCB=BLKSIZE=32760
>>  //SYSIN DD *
>>  COPYDUMP -
>>  INDD(BACKUP) -
>>  OUTDD(COPY1)
>> 
>>  /*
>>  I am trying to copy the
>>  tape (which has the default blksize of 262144). I  tried to force a blksize
>> of 32760 so that it  would be copied on to DASD in a  later step.
>> 
>>  Here is the error message of copying the  tape to another tape:
>>  ADR331E (001)-CPYD
>>  (01), OUTPUT BLKSIZE 32760 FOR DATA SET ON DDNAME COPY1 IS
>> 
>>  SMALLER THAN INPUT BLKSIZE 262144 ADR324E  (001)-CPYD (01), THE VOLUME/DATA
>> SET  SPECIFIED BY DDNAME COPY1 HAS BECOME UNUSABLE
>> 
>>  The tape dsn does not have a
>>  DATACLAS.
>> 
>>  I tried a copy
>>  of the tape to dasd which didn't work which prompted my  first  post. To
>> bypass the problem I tried  to copy the tape to another tape with a  blksize
>> of 32760 and encountered the above  error.
>> 
>> 
>>  ----------------------------------------------------------------------
>> 
>>  For IBM-MAIN subscribe / signoff / archive
>>  access instructions,
>>  send email to [email protected]
>>  with the message: INFO IBM-MAIN
>> 
>> 
>>  ----------------------------------------------------------------------
>> 
>>  For IBM-MAIN subscribe / signoff / archive
>>  access instructions,
>>  send email to [email protected]
>>  with the message: INFO IBM-MAIN
>> 
>> 
>>  ----------------------------------------------------------------------
>>  For IBM-MAIN subscribe / signoff / archive
>>  access instructions,
>>  send email to [email protected]
>>  with the message: INFO IBM-MAIN
>> 
>> 
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to