> > Yes but it doesn't name the component. I might have lots of values that
> > I want to retain and removing the file is undesirable.
>
> So in this case do an HCOPY, that seems to resolve the internal
> structuring issues at the heart of what's going on (which I'd say is an
> error with HDS's accounting of the free space in the file).
That's fine. thanks. I'm just trying to put myself in a user
perspective. The current message may leave users concerned and puzzled.
A helpful "Try copying the file with the hcopy command from the HDSTOOLS
package" offers a solution immediately, and reduces user support in the
HDS3->HDS4 phase. If it's not appropriate in HDS itself, please can we
have the error documented somewhere so a Google search will find it
and the solution.
Malcolm
|