Dave:
We took the other one and in addition there were side bennies. We
also got burned by an OEM that depended on some slight alterations to
the catalog that were really not documented although I think IBM and
the vendor agreed to disagree on the peculiarity (use of undocumented
fields) in the catalog. I got caught in the middle as I raised the
flag. IMO the vendor was at fault but its water under the bridge. I
will never use the other vendor again as a result (although its a
great vendor) I do not like getting burned.
Ed
On May 25, 2012, at 12:51 PM, Gibney, Dave wrote:
In the spirit of evenhandedness, faster mergecat is one of the
good reasons to acquire T-Rexx from Dinosoft, or the other one :)
Dave Gibney
Information Technology Services
Washington State University
On May 25, 2012, at 11:02 AM, Mary Anne Matyaz wrote:
Can MERGECAT performance be improved by altering the buffer space
values for either the input or output catalog, or both?
If you have a lot of VSAM, probably not. As I recall, doing a large
repro mergecat with a lot of VSAM was very slow, but it was mostly
due to the need to go change every vvds entry.
In other words, I don't think you'll get a lot of bang for your
buck.
Mary Anne
--------------------------------------------------------------------
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
---------------------------------------------------------------------
-
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
