In my case, it was all hand rolled and when COBOL2/COBOL for MVS & VM/COBOL
for OS/390 & VM (can't remember which, but probably the first one) did away
with Relative Record Addressing... somewhere around the early 90's or so.
At the time VSAM worked well for me, when VS FORTRAN wouldn't, but IDCAMS
scared off everyone else around me where I was... they *really really*
liked SAS... today, I think, I'd try it all with CSL.. and called from
EasyThieve... yust to scare 'em a bit a bit mo'.
Gregg
"No plan survives execution"
"McKown, John"
<[EMAIL PROTECTED]
insctr.com> To
Sent by: VM/ESA [email protected]
and z/VM cc
Discussions
<[EMAIL PROTECTED] Subject
.UARK.EDU> Re: end of VSAM product on VM?
12/07/2005 03:51
PM
Please respond to
VM/ESA and z/VM
Discussions
<[EMAIL PROTECTED]
.UARK.EDU>
We don't run z/VM any more due to ... nevermind. But I do have a
curiousity question. I am wondering how many need VM/VSAM simply for the
VSAM API to a "keyed" file. And how many really need the VSE/VSAM
interoperability? VSAM, at its base, is a fairly simple API. Duplicating
IDCAMS might be a bit harder, but doable. Sharing a VSAM file with
VSE/VSAM would likely be too difficult to emulate.
I guess that I'm wondering if the community could come up with a
functional replacement for VM/VSAM. That would be a nice FOSS project.
--
John McKown
Senior Systems Programmer
UICI Insurance Center
Information Technology
This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its
content is protected by law. If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited.
