"Peacock, Tom" <TPeacock AT DETMA DOT ORG> writes:
> Cloning absolutely demultiplexes save sets from the source to the target
> clone volume.

Could you perhaps provide some evidence of that? Remeber, if you're
just quoting what you've "heard", then you're probably just re-quoting
a common myth. Could you perhaps list a couple of your clone tapes and
check?

> Remember this - cloning clones save sets, not volumes.  When you
> select to clone a volume, cloning uses a list of save sets from a
> volume to accomplish that task using this list.

Agreed, but if those save sets are interleaved on the original, then
to avoid interleaving on the clone the software has to either: do
multiple passes on the source tape; or have many gigabytes of
temporary storage somewhere to store save sets being read that are not
being written (other streams in the interleaving). Since by timing a
clone I can see the system is not doing multiple passes, and
additionally I know neither of two conditions in the second case is
true in the systems I manage, I have to assume there is no
de-multiplexing. But then simply listing a tape shows that.

So if your clones are de-multiplexed, you must be cloning a ss at a
time, or your source tapes are not multiplexed (saving to disk first?)
or you're using some command we don't know about.

Thanks,
gdm

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=