I think you need to ask a few questions first.
1) What functions have been added to VSE/VSAM that were not added to
VM/VSAM?
2) What functions are planned to be added to VSE/VSAM that would make
the current VM/VSAM incompatible with VSE/VSAM catalogs.
VM/VSAM can be used two different ways. First, to read or write to VSE
VSAM space. Second, for VM applications.
If it's just for VM applications, then a stabilized version of VM/VSAM
will meet the needs and having the current version available via some
method could solve this "issue".
If it's for VM and VSE file sharing, then we need to know the
limitations. They may be 'acceptable' and again, the current version
could be made available via some method.
If the file sharing limitations make the product unusable for this
purpose, then development time would be required and that may be a big
problem.
Tony Thigpen
-----Original Message -----
From: Bob Heerdink
Sent: 12/05/2005 02:02 PM
Reed Mullen, z/VM Platform Management suggests we all contact
Gerhard Zierl ( [EMAIL PROTECTED] ) -- Gerhard has ownership
responsibilities for VSE/VSAM.
By the way, Gerhard tells me that the VM/VSAM code has not received an APAR
since 1999.
