[Info-vax] LOADER-E-BADSVINDX

[Joukj]

hb wrote:
> On Mar 13, 8:51 am, Joukj <jo... at hrem.nano.tudelft.nl> wrote:
> 
>> valeta-jj) run set_display.exe
>> %DCL-W-ACTIMAGE, error activating image LIBMESAGLU
>> -CLI-E-IMGNAME, image file
>> BOLERO$DKA100:[joukj.public.mesagl.mesagl.mesa.lib]libMesaGLU.exe;3
>> -LOADER-E-BADSVINDX, symbol vector index is too large
>>
>> Since both machines share physically all the files, I only can imagine
>> that some sysgen-paramters are different and cause the problem, but
>> which ones can cause this effect?
> 
> No, this has nothing to do with system parameters.
> 
> The error message is explained by help/message as
> "There is an inconsistency between a shareable image that was
> activated at runtime and information used to create an image that
> calls it.", where the last part means, at link time. In other words,
> at activation time, a reference in a shareable image can't be
> resolved, because the given index exceeds the ones present in a
> shareable image.
> 
> This can be the result of linking against a shareable image, which was
> changed after linking against it: at least one symbol vector entry was
> removed.
> 
> This can be the result of having a logical name for a shareable image
> pointing to an old/incorrect version of a shareable image.
> 
> I would use the VOIT tools which do static analysis of main/shareable
> image. Google can find the latest version of these tools for you.

Thanks for the suggestion.

I figured out what the problem was:
    a misconfigured hard link pointing to
         /dka100/dir1/hhh.dir
    instead of
         /nodename$dka100/dir1/hhh.dir


              Jouk

P.S. the first definition of the hard-link will also fail on a single 
node after installing the RMS v3.0 patch.

               jj