--------------------<snip>----------------
My main reason for asking is we still have VSAM defined with IMBED.
Fortunately no KEYRANGE or REPLICATE, at least no IEC161I messages with
those sub codes.
Since the statement was made that there is a performance issue, I was
hoping to find some verification so that I could convince my users to
reorg their files over the next year to get those removed. But if I
cannot support the statement, it may be a more difficult road to travel.
Zapping something is so much easier than doing a reorg of a file that
may be 4GB or larger or having to have an application outage to do it.
Same issue with some user catalogs.
Since I know I am not the only shop, I was also wondering if anyone else
was running into this situation and how they are going about trying to
get their files reorg'd. This is just pure curiosity on my part.
-------------------<unsnip>-------------------
Unfortunately, I was reduced to writing a program that would read the
entire cluster, then do the same with a copy of the cluster with those
options removed. When I finished that demonstration, on a 3000 cylinder
cluster, senior management was convinced and issued a order that those
clusters still using those options would be immediately converted. No
exceptions. The process took 10 days, with all applications managers
cooperating fully. Probably the only time I got a change for the better
implemented in less than 6 months! :-)
----------------------------------------------------------------------
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
