Richard Troth wrote:
And I note that although Rob mentions two different methods,
neither of those matches what I did here. As Adam pointed out,
it will appear a bit convoluted. But it seems to work well.
Neat, Sir Santa. That certainly does the trick as well. You could even
make the pipe tweak the file a bit and have it create the file in
DCSSBKUP format so that you can run DCSSRSAV (or friends against it).
You will have the DCSS start at and address above the largest Linux
virtual machine that uses it. So it is not very likely you run over your
CMS vital areas.
Yet another way: if you keep a full partition as the image for the DCSS
we could probably use CMS Pipelines' trackread stage to pull the data
in. Or even define a VDISK in the directory and link that R/W by Linux
to hand the data to a CMS virtual machine.
Rob (if I would attend SHARE this would make for a "Fifty ways to save
your segments" presentation)
