Ah. VQI. Makes me yearn for the old days at Softworks. A great company
with some great people! I did very little work on VQI during my long tenure
a Softworks, but I am very familiar with it. When IDCAMS was updated to use
the internal house sort (back in 91, 92 ??), the need for VQI really became
slim to none. The only real case you can make for keeping VQI is if you
need to build multiple alternate indexes over a single cluster. VQI can
build multiple alternate indexes with one pass (read) of the input file.
VQI accomplished its task much faster than IDCAMS when IDCAMS has its own
internal sort.
I would think you could convert your job(s) to use IDCAMS and not suffer
much, if any, performance.
Larry Crilley
Dino-Software Corporation
800.480.DINO
www.dino-software.com
T-REX - Superior ICF catalog mgmt with full Tape support and HSM Auditing
REORGadon - First ever online REORG for HSM
TERADON - First ever REPRO MERGECAT While-OPEN
XTINCT - Secure DASD/TAPE data eradication
RTD – DASD Real Time Defrag
DAL - DINO healthcheck Analysis service for Legato
SENTINEL – Real-time FTP Management. All Secure, all the time.
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf
Of Doug Fuerst
Sent: Wednesday, September 15, 2010 8:51 AM
To: IBM-MAIN@bama.ua.edu
Subject: VSAM Quick Index
Has anyone converted from Quick Index back to regular IDCAMS
processing? We only have about 12 jobs actually using QI and would like
to eliminate it.
Thanks.
Doug Fuerst
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
