>> DISK //myshare/install
>< 200 Disk set to //myshare/install.
This is odd. You should have seen a list of the tapes (and holding disk
entries) for that disk. The implication is none of the images ever made
it to tape, or the log.YYYYMMDD.NN files are bad (which might happen if
you are debugging), which is what triggers the "No dumps available" error.
What happens if you do "amadmin <config> find localhost //myshare/install"?
I'm betting it says it couldn't find anything.
Next, go to the logdir area and grep for //myshare/install in the log
files. If it does not show up at all, the log files have been clobbered
some how.
>Dan
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
