The strange thing is someone helped me find from GTF trace when dumpping an
extended format PS dataset, 56062 is used as tape dsn block size, however when
reading the same tape dsn, 262144 is used.It is very confusing, and at the same
time, the block size specified in JCL matched what's
Victor, You should be able to reply on the blocksize recorded in rmm. Just like
other tape systems it gets it from the system.
Assuming you are on a supported level of z/OS, rmm should record all you need
to know about logical and physical view of the data sent to tape by the
application and
Create a new DSN. Assign that new DSN to have a DATACLAS which is not
compressed. Use a utility such as IDCAMS REPRO, IEBGENER, or DFSORT to copy
the data from the old DSN to the new DSN. Back up the new DSN.
//COPY EXEC PGM=ICEGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD
Silly me. I assumed your DSN is on DASD. If it is on tape, then you should
be able to use ICEGENER to copy the data to another tape, but do something
like:
//COPY EXEC PGM=ICEGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD DISP=SHR,DSN=compressed.tape.dsn
//SYSUT2 DD DCB=TRTCH=NOCOMP,
Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Victor Zhang
Sent: Saturday, May 03, 2014 10:27 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: RMM and tape dataset block size
Hello experts,
I am trying to determine the tape dataset block size, can I
What I am facing a problem is :
When I tried to backup compressed dataset that have compression set to be on in
its data class, the backup speed will slow down dramatically.
For example, when I backup z/os 1.13 sysres volume, I got speed of about
40MB/s, however, when backup data that have its
Hello experts,
I am trying to determine the tape dataset block size, can I trust what recorded
in TMS's catalog? Is the block size accurate?
If the answer is YES, then I will not bother to dump SMF 21.
regards
Victor
--
For
