Conference azur::mcc

3702.0. "ems - ethernim, ivp fails" by SORGEN::MATHILDE () Tue Sep 08 1992 06:25

    I've already asked this problem in ethernim-notes-file, but nobody 
    answered.
    
    Because Ethernim V2.3 is included in EMS V2.2 I assume this notes-file
    is the right place to ask.
    
    
    Perhaps someone can help to fix the following problem:

    
VMS V5.4-3, Ethernim V2.3, especially enim$ivp.com:

starting enim$ivp.com results into the following error:



This procedure verifies the installation of NMCC/VAX ETHERnim X2.3 on VMS

A VT125, VT240, VT241, or VT340 terminal is required to verify installation


Do you want to continue? (Y/N) [Y]: y
ETHERnim directory [ETHERNIM]: sys$sysdevice:[ethernim]
%DCL-W-PARMDEL, invalid parameter delimiter - check use of special characters
 \[SYS$SYSDEVICE\
%DIRECT-W-NOFILES, no files found
%DIRECT-W-NOFILES, no files found
%DIRECT-W-NOFILES, no files found

...

**** NMCC/VAX ETHERnim V2.3 installation was unsuccessful! ****

-----------------------------------------------------------------------------


--> we've turned on verification. please have a look, what happened:



$ !			   E N I M $ I V P . C O M 
$ !
$ !			  COPYRIGHT (C) 1990 BY
$ !		    DIGITAL EQUIPMENT CORPORATION, MAYNARD
$ !		     MASSACHUSETTS.  ALL RIGHTS RESERVED.
$ !
$ !  THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED
$ !  ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE AND WITH THE INCLUSION
$ !  OF THE ABOVE COPYRIGHT NOTICE.  THIS SOFTWARE OR ANY OTHER COPIES
$ !  THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY OTHER
$ !  PERSON.  NO TITLE TO AND OWNERSHIP OF THE SOFTWARE IS HEREBY TRANSFERRED.
$ !
$ !  THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT NOTICE AND
$ !  SHOULD NOT BE CONSTRUED AS A COMMITMENT BY DIGITAL EQUIPMENT CORPORATION.
$ !
$ !  DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS
$ !  SOFTWARE ON EQUIPMENT THAT IS NOT SUPPLIED BY DIGITAL.
$ !
$ !***************************************************************************
$ !
$ ! This procedure verifies the installation of NMCC/VAX ETHERnim V2.3 on VMS
$ ON CONTROL_Y THEN GOTO ERR_EXIT
$ ON WARNING THEN GOTO ERR_EXIT
$ ON ERROR THEN GOTO ERR_EXIT
$ !
$ ! Save the connected directory before changing it
$ CONN_DIR = F$ENVIRONMENT("DEFAULT")
$ !
$ ! Say hello to the user
$ !
$ WRITE SYS$OUTPUT ""

$ WRITE SYS$OUTPUT "This procedure verifies the installation of NMCC/VAX ETHERnim X2.3 on VMS"
This procedure verifies the installation of NMCC/VAX ETHERnim X2.3 on VMS
$ WRITE SYS$OUTPUT ""

$ WRITE SYS$OUTPUT "A VT125, VT240, VT241, or VT340 terminal is required to verify installation"
A VT125, VT240, VT241, or VT340 terminal is required to verify installation
$ WRITE SYS$OUTPUT ""

$ !
$ ! Ask the user if he has the right terminal, and decide what to do then
$ !
$ ASK_CONT:
$ INQUIRE ENIM$cont "Do you want to continue? (Y/N) [Y]"
y
$ IF F$LENGTH(ENIM$cont) .EQ. 0 THEN ENIM$cont = "Y"
$ IF ENIM$cont .EQS. "Y" THEN GOTO ASK_CHECK
$ ASK_CHECK:
$ !
$ ! Check if IVP is called from installation procedure.  If so, do not
$ ! bother user for directory.
$
$ ENIM$DIRECTORY = F$LOGICAL("ENIM$DIRECTORY")
$ if (ENIM$directory .NES. "") then goto CHECK_DEV
$ !
$ ! Ask the user where he put ETHERnim
$ !
$ ASK_USER:
$ !
$ INQUIRE ENIM$directory "ETHERnim directory [ETHERNIM]"
sys$sysdevice:[ethernim]
$ ENIM$directory = ENIM$directory - "[" - "]"
$ IF F$LENGTH(ENIM$directory) .NE. 0 THEN GOTO CHECK_DEV
$ CHECK_DEV:
$ !
$ ! Make sure directory name has brackets
$ ENIM$directory = ENIM$directory - "[" - "]"
$ ENIM$directory = "[" + ENIM$directory + "]"
$ !
$ ! Check if IVP is called from installation procedure.  If so, do not
$ ! bother user for device.
$ !
$ ENIM$DEVICE = F$LOGICAL("ENIM$DEVICE")
$ if (ENIM$device .NES. "") then goto SET_DEF
$ SET_DEF:
$ !
$ ! SET DEFAULT 
$ !
$ SET DEFAULT BNA-0[SYS$SYSDEVICE:ETHERNIM]
%DCL-W-PARMDEL, invalid parameter delimiter - check use of special characters
 \[SYS$SYSDEVICE\
$ !
$ DIRECTORY ENIM$MESSAGES.HLB
%DIRECT-W-NOFILES, no files found
$ DIRECTORY ENIM$SCREENS.HLB
%DIRECT-W-NOFILES, no files found
$ DIRECTORY ENIM$HOST_MAIN.EXE
%DIRECT-W-NOFILES, no files found
$ DIRECTORY sys$sysroot:[sys$startup]ENIM$HOST_STARTUP.COM

Directory SYS$COMMON:[SYS$STARTUP]

ENIM$HOST_STARTUP.COM;6                 

Total of 1 file.
$ DIRECTORY ENIM$SESSION_STARTUP.COM
%DIRECT-W-NOFILES, no files found
$ DIRECTORY ENIM$REMOTE_MAIN.EXE
%DIRECT-W-NOFILES, no files found
$ DIRECTORY ENIM$REMOTE_STARTUP.COM
%DIRECT-W-NOFILES, no files found
$ DIRECTORY ENIM$DTR_DEFINITIONS.COM
%DIRECT-W-NOFILES, no files found
$ DIRECTORY ENIM$DTR_EXAMPLE.COM
%DIRECT-W-NOFILES, no files found
$ !

...



------------------------------------------------------------------------------

also, the ivp won't be processed during installation of ethernim.


any comments?

thanks in advance.


mathilde schwemmer, dsc munich

The ivp was asking for the directory specification without any
device specification.

The ENIM IVP as part of the EMS 2.2 installation will not ask for
the device/directory specification since it already should know it.

If you run the ENIM ivp by hand, the IVP will explicitly ask for
the ENIM device and directory specification as a complete directory
specification.

< If you run the ENIM ivp by hand, the IVP will explicitly ask for    >
< the ENIM device and directory specification as a complete directory >
< specification.                                                      >

this is, what we've done.


please have a look to the lines below, especially to the logical enim$device.

because this logical points to the ethernet-device, the ivp gets the wrong 
directory-specification.

enim$device is defined in SYS$COMMON:[SYS$STARTUP]ENIM$HOST_STARTUP.COM.


 "ENIM$DEVICE" [exec] = "BNA-0" (LNM$SYSTEM_TABLE)



...

$ ! Check if IVP is called from installation procedure.  If so, do not
$ ! bother user for device.
$ !
$ ENIM$DEVICE = F$LOGICAL("ENIM$DEVICE")
$ if (ENIM$device .NES. "") then goto SET_DEF
$ SET_DEF:
$ !
$ ! SET DEFAULT 
$ !
$ SET DEFAULT BNA-0[SYS$SYSDEVICE:ETHERNIM]
              ~~~~~                            <-------------
%DCL-W-PARMDEL, invalid parameter delimiter - check use of special characters
 \[SYS$SYSDEVICE\
$ !
$ DIRECTORY ENIM$MESSAGES.HLB
%DIRECT-W-NOFILES, no files found
$ DIRECTORY ENIM$SCREENS.HLB
%DIRECT-W-NOFILES, no files found
$ DIRECTORY ENIM$HOST_MAIN.EXE
%DIRECT-W-NOFILES, no files found
$ DIRECTORY sys$sysroot:[sys$startup]ENIM$HOST_STARTUP.COM

...

**** NMCC/VAX ETHERnim V2.3 installation was unsuccessful! ****



mathilde.

    To state it clearly:

    The Ethernim IVP and KITINSTAL use the logical ENIM$DEVICE to point
    to the device the Ethernim directory resides on.

    This is a  B U G  because ENIM$DEVICE is already reserved and used
    to specify the Ether*NET* device for Ethernim.

    We have a logical name conflict here that needs to be solved.

    *Robert


    P.S.: cross-posted in ETHERNIM and MCC

Reply to .2 reply:

	The V2.3 version of the ENIM kitinstal.com in the EMS 2.1 Kit 
	DOES NOT use the ENIM$DEVICE logical but uses a symbol called
	ENIM$DEVIVCE.  I do not have a copy of the kitinstal as part
	of the ENIM kit to check it out.

	The ENIM$IVP procedure however does reference the ENIM$DEVICE
	logical.  This has been fixed for the EMS 2.2 Kit.

    By the way, I have been testing ETHERnim and DECmcc on a VAXstation
    4000 Model 90.  To date, the only way to get ETHERnim to work on this
    system with its EZA network device (ISA-0 in NCP) is to DEASSIGN
    logical names for ENIM$DEVICE, ENIM$NETWORK, and ENIM$SEGMENT.  You
    must then ensure that the ETHERnim files are specifically named as
    follows:
    
    	ENIM$NETWORK_EZA.EXP
    	ENIM$NETWORK_EZA_WORK.EXP
    	ENIM$SEGMENT_EZA.EXP
    	ENIM$SEGMENT_EZA_WORK.EXP
    
    -Regards,
     Dan