Re: blksize for ML2 migrated dataset via HSM
Hello Dave, Thank's for your answer, indeed it's not possible and IBM won't update and adjust the blksize according the dataset size without a RFE (request for enhancement) regards Alain -Message d'origine- De : IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] De la part de David Devine Envoyé : jeudi 7 février 2013 15:39 À : IBM-MAIN@LISTSERV.UA.EDU Objet : Re: blksize for ML2 migrated dataset via HSM Hi Alain, It is not currently possible to change the 16k blksize on Hsm migration or backup tapes. Regards Dave *** Hello, Thank's for your update, but do you an idea to change the value, just because I'm sure that the default value is not use Regards Alain -Message d'origine- De : IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] De la part de David Devine Envoyé : jeudi 7 février 2013 12:24 À : IBM-MAIN@LISTSERV.UA.EDU Objet : Re: blksize for ML2 migrated dataset via HSM Hello, The Datamover parameter of DSS or HSM only applies to Control dataset backups and is not for general usage. Hsm has used a 16k blocksize for backup and migration tapes since inception, possibly because originally it was a good performance match for the specs of existing 3420 polo tape drives and the upcoming 3480 cartridge tape drives. (People who read the announcment specs in the early 80's feel free to dive in!) Well overdue for an update. Dumps however are straight dfdss and depending on what Z/os release you are on, the blksize will be the default of 256K (Zos 1.12 up) or 64K (Zos 1.11 down) or even 32k if you use the patch! While we are at it, an ML3 level for long term archive datasets (greater than 5 years say) would be good to split them out from all the other stuff on ML2. regards, Dave *** Hello, I observed a blksize of 16k for all ml2 migrated dataset (seen on the CA1 product). I use DSS as datamover and i'm wondering about the size concerning the blksize. Why dss don't use 256k since zos 1.12 ? Everybody will have an answer. thank's -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Ce message est confidentiel; Son contenu ne represente en aucun cas un engagement de la part de AXA Technology Services (AXA Tech) sous reserve de tout accord conclu par ecrit entre vous et AXA Technology Services (AXA Tech).Toute publication, utilisation ou diffusion,meme partielle, doit etre autorisee prealablement. Si vous n'etes pas destinataire de ce message, merci d'en avertir immediatement l'expe- diteur. This message is confidential; its contents do not constitute a commitment by AXA Technology Services (AXA Tech) except where provi- ded for in a written agreement between you and AXA Technology Services (AXA Tech). Any unauthorised disclosure, use or dissemina- tion, either whole or partial, is prohibited. If you are not the intended recipient of the message, please notify the sender imme- diately. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: blksize for ML2 migrated dataset via HSM
Per MVS/QuickRef 7.6
Syntax
BLKSIZE= {value}
{valueK}
{valueM}
{valueG}
Subparameter Definition
value
Specifies the maximum length, in bytes, of a block.
The number of bytes that you specify for BLKSIZE depends on the
device type and the record format for the data set. The maximum
is 32760 for DASD data sets and 2,147,483,648 for tape or DUMMY
data sets, except for data sets on magnetic tape with ISO/ANSI
version 3 labels, where the minimum value for BLKSIZE is 18 bytes
and the maximum is 2048 bytes. To allow a block size greater than
2048, use installation exit routine IFG0193G. Version 4 labels do
not have this restriction but is 2,760 for DASD, ISO/ANSI Version 4
tape labels, and other data sets.
Thank you and have a Terrific day!
Jonathan Goossen, DTM
ACT Mainframe Storage Group
Personal: 651-361-4541
Department Support Line: 651-361-
For help with communication and leadership skills checkout Woodwinds
Toastmasters.
IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU wrote on
02/12/2013 02:22:30 AM:
From: Mike Wood mww...@ntlworld.com
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 02/12/2013 02:22 AM
Subject: Re: blksize for ML2 migrated dataset via HSM
Sent by: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
I wonder where CA-1 picks up the extra data from.
Further to my earlier answer about the DCBE
It is possible that CA-1 picks the value up from the Tape Exits
Parameters, Main parameter list. The TEPM, mapped by IFGTEP, created
by O/C/EOV and passed to tape installation exits. If CA-1 does not
use the installation exits interface it will have to crawl through
the DCB to DCBE for cases where the LBI is used.
There is a technote on the CBTtape http://www.cbttape.org/features/
Technote-largeblk.htm
Mike Wood
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
This e-mail message and all attachments transmitted with it may
contain legally privileged and/or confidential information intended
solely for the use of the addressee(s). If the reader of this
message is not the intended recipient, you are hereby notified that
any reading, dissemination, distribution, copying, forwarding or
other use of this message or its attachments is strictly
prohibited. If you have received this message in error, please
notify the sender immediately and delete this message and all
copies and backups thereof. Thank you.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: blksize for ML2 migrated dataset via HSM
I found this in our TMC: BLKSIZE= 229376 I vaguely remember seeing this increase a few versions back along with some other field sizes. Thank you and have a Terrific day! Jonathan Goossen, DTM ACT Mainframe Storage Group Personal: 651-361-4541 Department Support Line: 651-361- For help with communication and leadership skills checkout Woodwinds Toastmasters. IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU wrote on 02/07/2013 08:04:16 PM: From: retired mainframer retired-mainfra...@q.com To: IBM-MAIN@LISTSERV.UA.EDU Date: 02/07/2013 08:04 PM Subject: Re: blksize for ML2 migrated dataset via HSM Sent by: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU If memory serves, the CA1 TMC uses 16 bits to store the blksize. Even when treated as unsigned, it won't show more than 65535. On z/OS 1.11 system, the DFDSS default for DUMP tape blocks is 65520. I doubt if it was reduced for 1.12. There is an installation options exit which can change the default to 32760. If your system is actually writing 16K blocks, then something at your site (such as the DCB parameter on the DD statement) is causing that. On the other hand, the HSM Storage Administration manual mentions 16K blocks for ML2 tapes so it might not be DFDSS. :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU ] On :: Behalf Of Houzet Alain :: Sent: Thursday, February 07, 2013 2:26 AM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: blksize for ML2 migrated dataset via HSM :: :: Hello, :: I observed a blksize of 16k for all ml2 migrated dataset (seen on the :: CA1 product). I use DSS as datamover and :: i'm wondering about the size concerning the blksize. Why dss don't use :: 256k since zos 1.12 ? :: Everybody will have an answer. thank's -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: blksize for ML2 migrated dataset via HSM
From CA 1®Tape Management Systems Programmer Guide r11.5 SP5 BLKSIZE TMBLKSI 96(60) BIN 4 MAXIMUM BLOCK SIZE JFCB JFCBLKSI 4 bytes are used to store the block size. Thank you and have a Terrific day! Jonathan Goossen, DTM ACT Mainframe Storage Group Personal: 651-361-4541 Department Support Line: 651-361- For help with communication and leadership skills checkout Woodwinds Toastmasters. IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU wrote on 02/08/2013 03:11:59 PM: From: Neil Duffee nduf...@uottawa.ca To: IBM-MAIN@LISTSERV.UA.EDU Date: 02/08/2013 03:12 PM Subject: Re: blksize for ML2 migrated dataset via HSM Sent by: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU Caveat: I get the daily digest so you folx've probably already hashed this to death... Not sure about signed/unsigned but CA-1(R) r12.6 will not store a value 032760. FDR/ABR dumps backup records in approx. track length ie. 57k-ish for our 3390-3s, but they are recorded with the 032760 value in CA-1. I discovered this while trying to generate an Earl report showing the amount of data stored on our tapes. (How many 3592 tapes would we have to buy?) Had to manually fudge the results for FDR/ABR tapes otherwise I was under-reporting them by 1- (32/57) percent. signature = 6 lines follows Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada telephone:1 613 562 5800 x4585 fax:1 613 562 5161 mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee How *do* you plan for something like that? Guardian Bob, Reboot For every action, there is an equal and opposite criticism. Systems Programming: Guilty, until proven innocent John Norgauer 2004 -Original Message- From: retired mainframer [mailto:retired-mainfra...@q.com] Sent: February 7, 2013 21:04 Subject: Re: blksize for ML2 migrated dataset via HSM If memory serves, the CA1 TMC uses 16 bits to store the blksize. Even when treated as unsigned, it won't show more than 65535. [snip] -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: blksize for ML2 migrated dataset via HSM
Obviously memory didn't serve. The TMBLKSI field in the CA-1 TMC is indeed 4 bytes. But the manual says the data comes from the JFCBLKSI field in the JFCB and that field is only 2 bytes. I wonder where CA-1 picks up the extra data from. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jonathan Goossen Sent: Monday, February 11, 2013 9:20 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: blksize for ML2 migrated dataset via HSM I found this in our TMC: BLKSIZE= 229376 I vaguely remember seeing this increase a few versions back along with some other field sizes. IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU wrote on 02/07/2013 08:04:16 PM: From: retired mainframer To: IBM-MAIN@LISTSERV.UA.EDU Date: 02/07/2013 08:04 PM Subject: Re: blksize for ML2 migrated dataset via HSM Sent by: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU If memory serves, the CA1 TMC uses 16 bits to store the blksize. Even when treated as unsigned, it won't show more than 65535. On z/OS 1.11 system, the DFDSS default for DUMP tape blocks is 65520. I doubt if it was reduced for 1.12. There is an installation options exit which can change the default to 32760. If your system is actually writing 16K blocks, then something at your site (such as the DCB parameter on the DD statement) is causing that. On the other hand, the HSM Storage Administration manual mentions 16K blocks for ML2 tapes so it might not be DFDSS. :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM- m...@listserv.ua.edu ] On :: Behalf Of Houzet Alain :: Sent: Thursday, February 07, 2013 2:26 AM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: blksize for ML2 migrated dataset via HSM :: :: Hello, :: I observed a blksize of 16k for all ml2 migrated dataset (seen on the :: CA1 product). I use DSS as datamover and :: i'm wondering about the size concerning the blksize. Why dss don't use :: 256k since zos 1.12 ? :: Everybody will have an answer. thank's - - For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM- MAIN This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: blksize for ML2 migrated dataset via HSM
The DCBE where the larger block size is stored when the LBI is used (ie Application supports it). Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: blksize for ML2 migrated dataset via HSM
On Mon, 11 Feb 2013 19:46:31 +, EXT-Schwarz, Barry wrote: Obviously memory didn't serve. The TMBLKSI field in the CA-1 TMC is indeed 4 bytes. But the manual says the data comes from the JFCBLKSI field in the JFCB and that field is only 2 bytes. I wonder where CA-1 picks up the extra data from. LH? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: blksize for ML2 migrated dataset via HSM
Caveat: I get the daily digest so you folx've probably already hashed this to death... Not sure about signed/unsigned but CA-1(R) r12.6 will not store a value 032760. FDR/ABR dumps backup records in approx. track length ie. 57k-ish for our 3390-3s, but they are recorded with the 032760 value in CA-1. I discovered this while trying to generate an Earl report showing the amount of data stored on our tapes. (How many 3592 tapes would we have to buy?) Had to manually fudge the results for FDR/ABR tapes otherwise I was under-reporting them by 1-(32/57) percent. signature = 6 lines follows Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada telephone:1 613 562 5800 x4585 fax:1 613 562 5161 mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee How *do* you plan for something like that? Guardian Bob, Reboot For every action, there is an equal and opposite criticism. Systems Programming: Guilty, until proven innocent John Norgauer 2004 -Original Message- From: retired mainframer [mailto:retired-mainfra...@q.com] Sent: February 7, 2013 21:04 Subject: Re: blksize for ML2 migrated dataset via HSM If memory serves, the CA1 TMC uses 16 bits to store the blksize. Even when treated as unsigned, it won't show more than 65535. [snip] -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
blksize for ML2 migrated dataset via HSM
Hello, I observed a blksize of 16k for all ml2 migrated dataset (seen on the CA1 product). I use DSS as datamover and i'm wondering about the size concerning the blksize. Why dss don't use 256k since zos 1.12 ? Everybody will have an answer. thank's -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: blksize for ML2 migrated dataset via HSM
Hello, The Datamover parameter of DSS or HSM only applies to Control dataset backups and is not for general usage. Hsm has used a 16k blocksize for backup and migration tapes since inception, possibly because originally it was a good performance match for the specs of existing 3420 polo tape drives and the upcoming 3480 cartridge tape drives. (People who read the announcment specs in the early 80's feel free to dive in!) Well overdue for an update. Dumps however are straight dfdss and depending on what Z/os release you are on, the blksize will be the default of 256K (Zos 1.12 up) or 64K (Zos 1.11 down) or even 32k if you use the patch! While we are at it, an ML3 level for long term archive datasets (greater than 5 years say) would be good to split them out from all the other stuff on ML2. regards, Dave *** Hello, I observed a blksize of 16k for all ml2 migrated dataset (seen on the CA1 product). I use DSS as datamover and i'm wondering about the size concerning the blksize. Why dss don't use 256k since zos 1.12 ? Everybody will have an answer. thank's -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: blksize for ML2 migrated dataset via HSM
At least on modern tape drives 16K is not the actual physical block size on tape, so it doesn't cause inefficient media usage. Ever since automatic hardware compression has been forced, the actual tape media physical blocks have been superblocks with a size of the controller's choosing, transparent to the operating system. The smaller block size used by z/OS requires more buffer management overhead and more channel commands for the data transfer, but at least it doesn't kill physical space on the media. Not like the old days where a singularly bad choice of block size could easily waste 99% of the media. JC Ewing On 02/07/2013 08:39 AM, David Devine wrote: Hi Alain, It is not currently possible to change the 16k blksize on Hsm migration or backup tapes. Regards Dave *** Hello, Thank's for your update, but do you an idea to change the value, just because I'm sure that the default value is not use Regards Alain -Message d'origine- De : IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] De la part de David Devine Envoyé : jeudi 7 février 2013 12:24 À : IBM-MAIN@LISTSERV.UA.EDU Objet : Re: blksize for ML2 migrated dataset via HSM Hello, The Datamover parameter of DSS or HSM only applies to Control dataset backups and is not for general usage. Hsm has used a 16k blocksize for backup and migration tapes since inception, possibly because originally it was a good performance match for the specs of existing 3420 polo tape drives and the upcoming 3480 cartridge tape drives. (People who read the announcment specs in the early 80's feel free to dive in!) Well overdue for an update. Dumps however are straight dfdss and depending on what Z/os release you are on, the blksize will be the default of 256K (Zos 1.12 up) or 64K (Zos 1.11 down) or even 32k if you use the patch! While we are at it, an ML3 level for long term archive datasets (greater than 5 years say) would be good to split them out from all the other stuff on ML2. regards, Dave *** Hello, I observed a blksize of 16k for all ml2 migrated dataset (seen on the CA1 product). I use DSS as datamover and i'm wondering about the size concerning the blksize. Why dss don't use 256k since zos 1.12 ? Everybody will have an answer. thank's -- Joel C. Ewing,Bentonville, AR jcew...@acm.org -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: blksize for ML2 migrated dataset via HSM
If memory serves, the CA1 TMC uses 16 bits to store the blksize. Even when treated as unsigned, it won't show more than 65535. On z/OS 1.11 system, the DFDSS default for DUMP tape blocks is 65520. I doubt if it was reduced for 1.12. There is an installation options exit which can change the default to 32760. If your system is actually writing 16K blocks, then something at your site (such as the DCB parameter on the DD statement) is causing that. On the other hand, the HSM Storage Administration manual mentions 16K blocks for ML2 tapes so it might not be DFDSS. :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of Houzet Alain :: Sent: Thursday, February 07, 2013 2:26 AM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: blksize for ML2 migrated dataset via HSM :: :: Hello, :: I observed a blksize of 16k for all ml2 migrated dataset (seen on the :: CA1 product). I use DSS as datamover and :: i'm wondering about the size concerning the blksize. Why dss don't use :: 256k since zos 1.12 ? :: Everybody will have an answer. thank's -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
