One other thing, your file is apparantly rather large. An Index CIsize of 1K
will guarantee a high number of Index Levels resulting in a relatively poor
level of performance.
Increase the data CI to 8K and the Index to 4K. That should keep your Index
levels to 2 or 3.
Also supply a Bufferspace of 1M to load as many index levels into memory as
possible when doing direct processing. Sequential processing will also be
aided. Currently you will need 90 I/Os to read a cylinder. With a large enough
Buffsp, it will be 1 I/O. The best I/O is still no I/O.
________________________________
Why not let SMS do its job?
Change your VOLUME parameter to (* * * * * * * * * * * * * * * * * *) -
depending on the number of available volumes in the pool up to 59 asterisks.
Change your CYL parameter to something like (300 200) which will allow more
volumes to be eligible for allocation.
________________________________
Willie wrote:
Good Morning,
I am trying to allocate a VSAM dsn on 3 volumes which are not SMS managed.
However, SMS tries to allocate the dsn in a SMS storage pool. How can I bypass
SMS so as that I can allocate the dsn on these 3 vols. Below is my jcl and the
error message.
DEFINE CLUSTER (NAME (Z8002D.TESTE.CLIFCPRK) -
INDEXED -
KEYS (20 0) -
RECSZ (2000 2000) -
FSPC (10 10) -
VOLUMES (VEBC5A,VEBC5B,VEBC5C) -
SHAREOPTIONS (1 3)) -
DATA (NAME (Z8002D.TEST.CLIFCPRK.KDATA) -
CYL (3300,400) -
CISZ(4096) ) -
INDEX (NAME (Z8002D.TEST.CLIFCPRK.INDEX) -
CYL(30 10) -
CISZ(1024) )
IGD17273I ALLOCATION HAS FAILED FOR ALL VOLUMES SELECTED FOR DATA SET
Z8002D.TEST.CLIFCPRK
IGD17290I THERE WERE 1 CANDIDATE STORAGE GROUPS OF WHICH THE FIRST 1
WERE ELIGIBLE FOR VOLUME SELECTION.
THE CANDIDATE STORAGE GROUPS WERE:LIBSG01
----------------------------------------------------------------------
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
