To save into CMS files, somebody would have to teach CP how to WRITE CMS
files - MUCH more challenging than its current ability to ("simply") read
them. (SAVESYS needs to be a CP function - just because most SAVESYS
commands are executed within CMS doesn't mean that we can simply throw
away the capability to SAVESYS any image.)
SAVESYS onto a single SPOOL volume - yes, very nice, but to what end?
Being able to DDR restore that volume for recovery? Yes, quite reasonable
.
Being able to avoid loss of a SDF if a single SPOOL volume fails?
Reasonable, but long odds and probably of minor consideration alongside
the other problems you'll be mitigating against to cover that scenario.
Missing SDF's at IPL time? This problem is already solved by V/SEG -
AUTOVSEG (with an IPL 190 in its directory entry) already scans for
missing SDF's and replaces them - and even comes with instructions on how
to make AUTOLOG1 wait until the restores are complete before proceeding.
(It's fun at a DR to do a CLEAN start and watch all those SDF's
automagically appear at IPL time.)
So far, I haven't seen a single goal expressed which hasn't already been
solved by V/SEG so, once again I ask the question - what business reason
can we show IBM that would make it worthwhile investing time money and
effort in providing a second solution to a problem that's already been
solved? I'm not trying to suggest that a more modern set of solutions
wouldn't be attractive (V/SEG is seriously showing its age in some places
and has a certain, "clunkiness" about it which makes it kind-of endearing
)
and I'd love to see CA investing some serious manpower in the product (I
still suspect they aren't really aware of what a gem they acquired here)
-
but I just can't see how it'd make commercial sense for IBM to develop a
rival product unless it solves some real operational problem that's not
already been solved by V/SEG. So far, (unless I've missed it) nobody's
come up with one. (Folk have suggested alternative METHODS, but nobody's
yet pointed out a significant PROBLEM that's outside of V/SEG's scope.)
Regards
Jeff
