> 1. It's clearly an HDS bug that needs fixing
If you say so. Our HDS expert is on leave. If fixing it avoids the
DAT_WEIRD error, then that addresses my request.
> 2. Users get this quite often now even though all files should be getting
> made with HDS4 and HDS3 shouldn't be used. How can this be an HDS3 to
> HDS4 conversion issue? How can GLOBAL.sdf even be made in HDS3?
In my case I think it was HDS4 but then I ran an HDS3 task in error
(still have an old Starlink release as may users), then came back to
HDS4. I suppose GLOBAL.sdf might have started life as HDS3. It's not
something I rm often unlike say the AGI database.
> Are you saying that it's a short term issue because people have left over
> GLOBAL.sdf files from their old starlink distributions and that once
> they've deleted the file the problem is never going to come back?
Probably. I just don't want users put off or stuck if they also
encounter the alleged bug.
Malcolm
|