Conference turris::decc

   It would appear you might have an LNK$* logical name referencing
   the VAX C object library around -- I can imagine no other reason
   why the DEC C IVP would be looking in the SYS$LIBRARY:VAXCRTL.OLB
   library for these symbols...

   The installation probably worked -- get rid of any VAX C logical
   names around (SHOW LOGICAL/OUT, then SEARCH for VAXC), and run the
   IVP (kept under SYS$TEST:) directly.  Or try some basic programming
   tests and see if the compiler is working as expected.

		Hello,

>
>   It would appear you might have an LNK$* logical name referencing
>   the VAX C object library around -- I can imagine no other reason
>   why the DEC C IVP would be looking in the SYS$LIBRARY:VAXCRTL.OLB
>   library for these symbols...
>

	I just logged in the system and no LNK$* logical defined.


>   The installation probably worked -- get rid of any VAX C logical
>   names around (SHOW LOGICAL/OUT, then SEARCH for VAXC), and run the
>   IVP (kept under SYS$TEST:) directly.  Or try some basic programming
>   tests and see if the compiler is working as expected.
> 

	No logical containing "vaxc". I cannot program in C.

	Any other clue ?

	Eric

         <<< TURRIS::DISK$NOTES_PACK:[NOTES$LIBRARY]DECC_BUGS.NOTE;1 >>>
                       -< DEC C Problem Reporting Forum >-
================================================================================
Note 662.14              AACRT060 install fails the IVP                 14 of 21
RTL::COWAN "Ken, TLG"                                16 lines  22-AUG-1994 16:04
--------------------------------------------------------------------------------
LNK$* logicals was my guess too.  Next guess ..

Is VAXCRTL in IMAGELIB?  Try:

$ LIBR/LIST/ONLY=VAXC* SYS$LIBRARY:IMAGELIB
%LIBRAR-W-NOMTCHFOU, no matches found for VAXC*

On a standard system, it is *NOT* there.  If you remove it
from IMAGELIB, in order that the DEC C IVP runs correctly,
then you're VAX C users will have to explictly link against
VAXCRTL.  We tried to have the DEC C installation co-exist
with VAX C; for us to automatically delete VAXCRTL from
IMAGELIB would mean that programmers link procedures
would need to change.

KC

		Hello,


>
>Is VAXCRTL in IMAGELIB?
>

	No.

	Thanks for the help, I didn't notice the note 662, I will read it

	Any other guess ?



					Eric Collart
					MCS Brussels

           <<< TURRIS::DISK$NOTES_PACK:[NOTES$LIBRARY]DECC.NOTE;1 >>>
                                   -< DECC >-
================================================================================
Note 1037.0                Troubleshooting the CRT kit                   1 reply
CAIRN::HARRIS "Kevin Harris, dtn 381-2039"           89 lines  16-DEC-1994 15:12
--------------------------------------------------------------------------------
I assume 2228 should be reply to here.  Can one of the moderators move
it?

There are lots of installation failure notes here, in TURRIS::DECC and
TURRIS::DECC_BUGS.  I just put together a crib sheet of things to
look for.  To the readership at large, please review this to see if
there are other 'gotchas' that you have run across.

KC
-------------------------

Revised 10/26/94.

    If you're having CRT kit problems, try the following:

    1.  Check for files in SYS$SPECIFIC:[SYSLIB].  Normally, this
	directory is empty.  Having any kit files there has
	been known to cause IVP failures.
	$ DIR SYS$SPECIFIC:[SYSLIB]
	%DIRECT-W-NOFILES, no files found

    2.  Check for a logical LNK$* that points to VAXCRTL.OLB.  You
	should not find one.
	$ SHO LOG LNK*

	(LNM$PROCESS_TABLE)

	(LNM$JOB_86FE7BC0)

	(LNM$GROUP_000312)

	(LNM$SYSTEM_TABLE)

	(DECW$LOGICAL_NAMES)
	%SHOW-S-NOTRAN, no translation for logical name LNK*

    3.  Be sure VAXCRTL.EXE is not inserted in IMAGELIB.  i.e. Expect:
	$ LIBR/SHARE/EXTRACT=VAXCRTL SYS$LIBRARY:IMAGELIB
	%LIBRAR-E-LOOKUPERR, error looking up VAXCRTL in
	    SYS$COMMON:[SYSLIB]IMAGELIB.OLB;2
	-LBR-E-KEYNOTFND, key not found

    4.  Be sure that CMA$RTL does not have references to VAXCRTL.
	$ ANALYZE/IMAGE/OUT=CMA.LIS SYS$LIBRARY:CMA$RTL
	%ANALYZE-I-ERRORS, SYS$COMMON:[SYSLIB]CMA$RTL.EXE;1     0 errors
	$ SEAR CMA.LIS VAXCRTL
	%SEARCH-I-NOMATCHES, no strings matched

    5.  Don't install the kit on a VMS V6.1 system.  It is not needed.
	The version number check in the kit is broken.
	$ WRITE SYS$OUTPUT F$GETSYI("VERSION")
	V6.0

    6.  Check that the principal CMA images and DEC C RTL are
	in SYS$COMMON:[SYSLIB] and got inserted into IMAGELIB.
	
	$ DIR SYS$LIBRARY:CMA$RTL,CMA$TIS_SHR,DECC$SHR

	Directory SYS$COMMON:[SYSLIB]

	CMA$RTL.EXE;1       CMA$TIS_SHR.EXE;1   DECC$SHR.EXE;1

	Total of 3 files.
	$ LIBR/EXTR=(CMA$RTL,CMA$TIS_SHR,DECC$SHR)/OUT=FILES.LIS
SYS$LIBRARY:IMAGELIB

    7.  Check for VAXCRTL* logicals.  There should not be any.
	$ SHO LOG VAXCRTL*

	(LNM$PROCESS_TABLE)

	(LNM$JOB_834AB550)

	(LNM$GROUP_000011)

	(LNM$SYSTEM_TABLE)

	(DECW$LOGICAL_NAMES)
	%SHOW-S-NOTRAN, no translation for logical name VAXCRTL*

    8.  Check that CMA$TIS_SHR is not installed with privileges.
	$ INSTALL LIST SYS$LIBRARY:CMA$TIS_SHR

	DISK$VMS$SYSTEM:<SYS6.SYSCOMMON.SYSLIB>.EXE
	   CMA$TIS_SHR;1    Open Hdr               Lnkbl

    9.  If all else fails, modify the IVP to link with /MAP/FULL/CROSS,
	and SET VERIFY.  Compare the results, and .MAP files with
	the results of a working system.

        <<< TURRIS::DISK$NOTES_PACK:[NOTES$LIBRARY]C_PLUS_PLUS.NOTE;2 >>>
                                    -< C++ >-
================================================================================
Note 2216.14  Undefined symbols CMA$TIS_*ERRNO_*_ADDR after upgrade on  14 of 14
TLE::WHITMAN                                         36 lines   1-MAY-1996 13:24
                    -< make sure DECC$SHR gets off the kit >-
--------------------------------------------------------------------------------
One of the reasons that an installation of the aacrt060 kit would produce
IVP %LINK-I-UDFSYM messages for the symbols:

		CMA$TIS_ERRNO_GET_ADDR
		CMA$TIS_ERRNO_SET_ADDR
		CMA$TIS_VMSERRNO_GET_ADDR
		CMA$TIS_VMSERRNO_SET_ADDR

		CMA$TIS_ERRNO_GET_ADDR
		DECC$GA_STDERR
		DECC$GA_STDIN
		DECC$GA_STDOUT

is when DECC$SHR.EXE is in SYS$LIBRARY but is not in SYS$LIBRARY:IMAGELIB.OLB. 
Could you have a version of DECC$SHR.EXE in SYS$LIBRARY ?  If there is a 
version of DECC$SHR.EXE in SYS$LIBRARY which is either more recent or as 
recent as the version on the kit, the kit will not place DECC$SHR.EXE from 
the kit into SYS$LIBRARY and will not insert DECC$SHR.EXE into 
SYS$LIBRARY:IMAGELIB.OLB.

One of the assumptions of the CRT kit is that the DECC$SHR.EXE found in
SYS$LIBRARY  is the same as the one which has already in inserted into
SYS$LIBRARY:IMAGELIB.OLB.

Sometimes during testing or during the installation of another product
DECC$SHR.EXE  gets placed into SYS$LIBRARY but does not get placed into
SYS$LIBRARY:IMAGELIB.OLB.

On a "pure" OpenVMS VAX v5.5-2 system no copies of DECC$SHR.EXE should
exist in SYS$LIBRARY.
 
Another possibility is that a logical is defined from the SYSTEM account from
which you performed the installation.  If a logical points to a version
of DECC$SHR.EXE which is more recent than the one on the kit, the kit's
DECC$SHR.EXE will not be installed.
    

		Hello,


Thanks for your help, I performed the checks from below and there are
some differences (search for "***" string):


>
>    If you're having CRT kit problems, try the following:
>
>    1.  Check for files in SYS$SPECIFIC:[SYSLIB].  Normally, this
>        directory is empty.  Having any kit files there has
>        been known to cause IVP failures.
>        $ DIR SYS$SPECIFIC:[SYSLIB]
>        %DIRECT-W-NOFILES, no files found
>

	It was not empty, I moved files to another directory but
	still problem in IVP.


>    2.  Check for a logical LNK$* that points to VAXCRTL.OLB.  You
>        should not find one.
>        $ SHO LOG LNK*
>

	No LNK* logical defined (as said in previous reply).


>
>    3.  Be sure VAXCRTL.EXE is not inserted in IMAGELIB.  i.e. Expect:
>        $ LIBR/SHARE/EXTRACT=VAXCRTL SYS$LIBRARY:IMAGELIB
>        %LIBRAR-E-LOOKUPERR, error looking up VAXCRTL in
>            SYS$COMMON:[SYSLIB]IMAGELIB.OLB;2
>        -LBR-E-KEYNOTFND, key not found
>

	VAXCRTL is not in IMAGELIB


>    4.  Be sure that CMA$RTL does not have references to VAXCRTL.
>        $ ANALYZE/IMAGE/OUT=CMA.LIS SYS$LIBRARY:CMA$RTL
>        %ANALYZE-I-ERRORS, SYS$COMMON:[SYSLIB]CMA$RTL.EXE;1     0 errors
>        $ SEAR CMA.LIS VAXCRTL
>        %SEARCH-I-NOMATCHES, no strings matched
>


	No refence found to VAXCRTL


>    5.  Don't install the kit on a VMS V6.1 system.  It is not needed.
>        The version number check in the kit is broken.
>        $ WRITE SYS$OUTPUT F$GETSYI("VERSION")
>        V6.0
>

	I installed on a VMS 5.5-2 system.


>    6.  Check that the principal CMA images and DEC C RTL are
>        in SYS$COMMON:[SYSLIB] and got inserted into IMAGELIB.
>        
>        $ DIR SYS$LIBRARY:CMA$RTL,CMA$TIS_SHR,DECC$SHR
>
>        Directory SYS$COMMON:[SYSLIB]
>
>        CMA$RTL.EXE;1       CMA$TIS_SHR.EXE;1   DECC$SHR.EXE;1
>
>        Total of 3 files.

	They are in SYS$COMMON:[SYSLIB].

>        $ LIBR/EXTR=(CMA$RTL,CMA$TIS_SHR,DECC$SHR)/OUT=FILES.LIS
>SYS$LIBRARY:IMAGELIB
>

*****
*********** ONLY CMA$RTL FOUND IN IMAGELIB *****
*****

	Do I need to insert them ? If yes, how to do ?


>    7.  Check for VAXCRTL* logicals.  There should not be any.
>        $ SHO LOG VAXCRTL*
>


	NO VAXCRTL* logical found.


>
>    8.  Check that CMA$TIS_SHR is not installed with privileges.
>        $ INSTALL LIST SYS$LIBRARY:CMA$TIS_SHR
>
>        DISK$VMS$SYSTEM:<SYS6.SYSCOMMON.SYSLIB>.EXE
>           CMA$TIS_SHR;1    Open Hdr               Lnkbl
>


	I found following:

DISK$SYSTEM:<SYS0.SYSCOMMON.SYSLIB>.EXE
   CMA$TIS_SHR;1    Open Hdr Shar          Lnkbl


>    9.  If all else fails, modify the IVP to link with /MAP/FULL/CROSS,
>        and SET VERIFY.  Compare the results, and .MAP files with
>        the results of a working system.
>

	I did not perform this test.




					Thanks for help

					Eric Collart	
					MCS Brussels

    From the system account:
    
       $ LIBRARY /INSERT SYS$SHARE:IMAGELIB.OLB SYS$SHARE:CMA$TIS_SHR.EXE
       $ LIBRARY /INSERT SYS$SHARE:IMAGELIB.OLB SYS$SHARE:DECC$SHR.EXE
    
    
    This does explain the undefined globals, but does not explain what
    failed during the installation.  There is a data file which tells the
    KITINSTAL.COM procedure which images are to also be inserted into 
    IMAGELIB.  Both of these images are marked as such.
    
    Duane

I experienced the same problem on a VAXstation with VMS, UCX and DECC
installed from scratch (VMS 5.5-2H4, UCX V4.1, DECC V5.5). It looks like the
images cma$tis_shr.exe and decc$shr.exe are also in the UCX kit. I saw a
message during the installation but didn't pay much attention to it. Looks
like they only copy them to sys$share. Later on, the DECC ivp failed. Inserting
them into the imagelib resolved the problem.

Hartmut

   re: .9, If this is the case, please log a bug against the UCX kit.