--------------------------------<snip>-----------------------------
I cannot understand this problem. When I define the cluster for some reason
the CISIZE of the .INDEX component does not use the same value in the cluster
defintion. In this case it substitutes 2048 with 3584. I am befuddled by
this. Could someone shed some light? Would this cause a problem for the STC
DFHSM?
Here is my define cluster:
DEFINE CLUSTER -
(NAME(DFHSM.MCDS.COPY) VOLUME(PROD01) -
CYLINDER(798 0) FILE(HSMMCDS) -
RECORDSIZE(435 2040) FREESPACE(0 0) -
SPEED BUFFERSPACE(530432) -
INDEXED KEYS(44 0) SHAREOPTIONS(3 3) -
UNIQUE NOWRITECHECK) -
DATA (NAME(DFHSM.MCDS.COPY.DATA) CISZ(4096) ) -
INDEX (NAME(DFHSM.MCDS.COPY.INDEX) CISZ(2048) )
/*
Thanks in advance
--------------------------------------<unsnip>----------------------------------
Do what I've been telling users for years: let VSAM and IDCAMS figure
out the appropriate CISIZE. HSM will use whatever you hand it.
Let the system do what it's designed to do. :-)
--
Rick
--
Remember that if you’re not the lead dog, the view never changes.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
