Re: Optimal Tape Blocksize
- From: walter_marguccio@xxxxxxxxx (Walter Marguccio)
- Date: 27 Mar 2009 02:56:28 -0700
From: "Gibney, Dave" <gibney@xxxxxxx>
Still, why worry about details the system will handle for you.
I agree 100%. I told our programmers long ago to stick to
BLKSIZE=0 *and* DSORG=PS for datasets on DASD. This always work
(BLKSIZE close to half track).
Behalf Of Ted MacNEIL
On tape, it's as close to the maximum as possible.
I thought BLKSIZE=0 would also let the system choose the optimal bloksize
for datasets on tape. I'm starting to review datasets on tape the way Lizette
is doing, and I can see that in some cases the chosen bloksize is really poor.
(i.e. RECFM=FB,LRECL=22,BLKSIZE=0 in jcl, but I see BLKSIZE=4620 under DFSMSrmm)
In my DEVSUPxx I have only coded COMPACT=YES.
I can't understand why such poor BLKSIZE are chosen. I would really appreciate
if anyone could shed some light on this.
TIA
Walter Marguccio
z/OS Systems Programmer
BELENUS LOB Informatic GmbH
Munich - Germany
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.
- Follow-Ups:
- Re: Optimal Tape Blocksize
- From: John Kington
- Re: Optimal Tape Blocksize
- References:
- Re: Optimal Tape Blocksize
- From: Ted MacNEIL
- Re: Optimal Tape Blocksize
- From: Gibney, Dave
- Re: Optimal Tape Blocksize
- Prev by Date: AUTO: Geoffrey K Smith is out of the office. (returning 03/30/2009)
- Next by Date: Re: Optimal Tape Blocksize
- Previous by thread: Re: Optimal Tape Blocksize
- Next by thread: Re: Optimal Tape Blocksize
- Index(es):
Relevant Pages
|