Error: ident mismatch with shareable image

[Craigers01]

I am running OpenVMS 6.2. I am getting an error trying to run a program. This error started fairly recently, yet the executables have not been modified in decades.. Also, I am not intentionally trying to use DEC Windows for anything.

$ RUN COMETS$SYSTEM:SBL701
%DCL-W-ACTIMAGE, error activating image DECW$XTLIBSHRR5
-CLI-E-IMGNAME, image file DSA200:[SYS1.SYSCOMMON.][SYSLIB]DECW$XTLIBSHRR5.EXE;2
-SYSTEM-F-SHRIDMISMAT, ident mismatch with shareable image

$ dir/dat=mod COMETS$SYSTEM:SBL701
Directory COMETS1:[COMETS_55.CMT]
SBL701.EXE;6 4-JAN-1999 09:24:08.75

$ dir/dat=mod DSA200:[SYS1.SYSCOMMON.][SYSLIB]DECW$XTLIBSHRR5.EXE
Directory DSA200:[SYS1.SYSCOMMON.][SYSLIB]
DECW$XTLIBSHRR5.EXE;2 22-SEP-1995 15:39:07.95

Any help would be appreciated!

[Steven Schweda]

> This error started fairly recently, yet the executables have not been
> modified in decades..

   What _has_ changed?  OS patches since then?  Was the executable
linked on the same system as you're trying to run it?  Recently?

      help /message SHRIDMISMAT

   The usual (easier) cure is to relink the executable with the
currently available run-time stuff.

   Corrupt files could cause this, too, of course.

> [...] OpenVMS 6.2. [...]

   The advice is more extensive on a newer system than on an old VAX,
but the action is typically the same.  From V8.4-2L3 (IA64):

 SHRIDMISMAT,  ident mismatch with shareable image

  Facility:     SYSTEM, System Services

  Explanation:  The activation of a component shareable image failed; the
                calling image expected a different (and typically newer)
                version of the shareable image than the image that was
                found during the failed activation attempt. Specifically,
                the global section match (GSMATCH) value associated with the
                shareable image was found to be incompatible with the GSMATCH
                specification for the version of the shareable image against
                which the calling image was originally linked.

                This error can occur under the following conditions:

                o According to the GSMATCH value established when the
                  shareable image was built, there has been an incompatible
                  change to the shareable image.

                o An attempt was made to run an image built for a newer
                  version of the specific shareable image or a newer OpenVMS
                  version or a newer OpenVMS Engineering Change Order
                  (ECO) in an environment with an older version of the same
                  shareable image.


  User Action:  Relink the executable image against the older version of the
                shareable image, or upgrade to the newer shareable image. You
                may need to relink the executable code for the mismatched (and
                probably older) configuration, possibly specifying a different
                GSMATCH. Alternatively, you may have to upgrade the version
                or apply a patch to OpenVMS or the application to make the
                shareable image match the GSMATCH expectations of the calling
                image.

                For details about creating and maintaining shareable images
                and for information on correctly using the GSMATCH mechanisms
                of the OpenVMS Linker utility, refer to the HP OpenVMS Linker
                Utility Manual.

The advice there assumes that the shareable image is older, but newer
could trigger the same complaint.

[Volker Halle]

Try $ SET WATCH FILE/CLASS=MAJOR before running the image, this will list ALL shareable images, which are being activated. The error may be in one of the dependent images. $ SET WATCH FILE/CLASS=NOMAJOR to turn it off again.

$ ANALYZE/IMAGE can be used to check the GSMATCH MAJOR/MINOR IDs.

Volker.

[Craigers01]

I am not aware of aything happening to the VAX related to this (Patching, etc.). I can confirm that this worked "8/10/22". I have looked through my DISKS for all files changed since then, and I find nothing interesting.

Here is my WATCH results. I really don't understand why any call to DECW is being called. SBL701.EXE is supposed to "compile" some data. It should not cause a Dec Window to be interacted with.. Anyway, thanks for all the help so far.

$ RUN COMETS$SYSTEM:SBL701
%XQP, Thread #0, Access (0,0,0) Status: 00000910
%XQP, Thread #0, Access SBL701.EXE;6 (1576,1,0) Status: 00000001
%XQP, Thread #0, Deaccess (1576,1,0) Reads: 5, Writes: 0, Status: 00000001
%DCL-W-ACTIMAGE, error activating image DECW$XTLIBSHRR5
-CLI-E-IMGNAME, image file DSA200:[SYS1.SYSCOMMON.][SYSLIB]DECW$XTLIBSHRR5.EXE
-SYSTEM-F-SHRIDMISMAT, ident mismatch with shareable image

[Volker Halle · Accepted solution]

Did you check $ ANALYZE/IMAGE COMETS$SYSTEM:SBL701 ?

Could some logical(s) have changed ?

Volker.

[Craigers01]

Thanks so MUCH for your assistance. The advice about using WATCH taught me a new tool to diagnose issues. I has already used ana/image and according to the results I interpreted, I did not find a mismatch. My coworker copied three offending DECW executables from our PROD environment to DEV, and it is now working. I think the mystery will remain unsolved.

Thanks so much!

Craig

[Sunitha_Mod]

Hello Craig,

That's Excellent! 

We are extremely glad to know the problem has been resolved and we appreciate you for keeping us updated.