[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

3637.0. "Can't start Transports" by OHWELL::SYSTEM () Mon Nov 12 1990 10:29

    
    I  have a problem starting decwindows on a few satellites. Problem
    did not initially occur, after upgrade windows worked fine..after
    pausing or rebooting the following error appears in the
    Decw$server_0_error.log
    
    12-nov-1990 09:32:57.0 Hello, this is the X server
    Dixmain address=13074
    Now attach all known txport images
    Can't start transports
    
    The pointer appears on the screen but nothing else..restarting
    decwindows ..the process runs an then disappears.
    
    thanks/david
T.RTitleUserPersonal
Name
DateLines
3637.1forgot vms/decw versionsOHWELL::SYSTEMMon Nov 12 1990 10:306
    forgot..
    
    system was upgraded to T5.4-1 of vms and decwindows on thurs 11/8
    
    /david
    
3637.2Very strangeSTAR::VATNEPeter Vatne, VMS DevelopmentMon Nov 12 1990 13:594
Do you have a DECW$PRIVATE_SERVER_SETUP.COM file in SYS$MANAGER:?
If so, could you post it?

Also, could you post a directory/size/date/prot of SYS$LIBRARY:DECW$TRANS*.*?
3637.3DECW$PRIVATE,*TRANS* INFOOHWELL::SYSTEMMon Nov 12 1990 15:21115
    HERE IS THE INFO YOU REQUESTED...ALSO PLEASE NOTE THAT THE SYSTEM
    WAS UPGRADED ON THURS AND ALL WORKED FINE. 3 NODES THAT HAVE RELOADED
    SINCE FRIDAY OR THIS MORNING MONDAY HAVE ALL FAILED. SEVEN OTHER
    SATELLITES ARE WORKING FINE. I RESTARTED DECWINDOWS ON ANOTHER
    SATELLITE WITHOUT REBOOTING AND IT WORKED FINE.
           THANKS/DAVID
    
  *********
Directory SYS$COMMON:[SYSMGR]

DECW$PRIVATE_SERVER_SETUP.COM;1
                          7   1-NOV-1988 16:45:20.88

Total of 1 file, 7 blocks.
$exit
$ ! This is a sample server customization file.  You can specify a number of
$ ! things about how you want the server to configure itself by defining some
$ ! DCL symbols here. You can use this file to specify the following:
$ !
$ !	 - The density of your screen.
$ !
$ !	 - Whether the screen is monochrome or color.  You must specify
$ !        monochrome or color only for hardware where both screen types are
$ !	   available, such as the VAXstation II/GPX or the VAXstation 2000/GPX)
$ !	   For hardware like the VAXstation II or the VAXstation 2000 which
$ !	   support monochrome only, the specification here will be ignored.
$ !	   look for font files by default.
$ !
$ !	-  The default keyboard map.  This specifies what language your keyboard
$ !	   is designed for.  You also specify the country in the DECwindows
$ !	   session manager setup, but the specification here will prevail
$ !	   before you log in.
$ !
$ !	You make these specifications by defining DCL symbols.  The symbols
$ !	are listed in the following table:
$ !
$ !	Characteristic	Symbol			Values		Default*
$ !----------------------------------------------------------------------------
$ !	Density		DECW$SERVER_DENSITY	75 or 100	75
$ !	Color		DECW$COLOR		T OR F		T**
$ !	Keyboard Map	DECW$DEFAULT_KEYBOARD_MAP ***		NORTH_AMERICAN_LK201LA
$ !----------------------------------------------------------------------------
$ ! * Defaults may be changed in future software versions, or for future hardware.
$ ! **On a monochrome-only hardware, the default is F, and a value of T will
$ !   have no effect.
$ !***Valid values are the file names (without extension) in the directory
$ !   SYS$SYSROOT:[DECW$KEYMAP]
$ !
$ !-----------------------------------------------------------------------------
$ !
$ !	This file is setup so that you can customize it to act differently
$ !	depending on the node that it is being executed on.  This allows a
$ !	single file to reside in the cluster common SYS$MANAGER directory
$ !	and yet start different workstations in the cluster with different
$ !	characteristics.  To use this, replace the definition of node_list
$ !	with your own list of node names, and add a label "do_nodename" with
$ !	the DCL code that you want to execute on that node.
$ !
$ !	Here is a sample list of valid node names:
$ !
$ node_list = "GPXBW/GPXCOL/DUTCH/UK100"
$ !
$ !	Find out if we have node that this file has been customized for.
$ !	If so, go there.  Otherwise, do the default.
$ !
$ node_number = 0
$ node_loop:
$   node = f$element(node_number,"/",node_list)
$   if node .eqs. "/" then goto do_default
$   if (node .eqs. f$getsyi("NODENAME"))then goto do_'node
$   node_number =  node_number + 1
$   goto node_loop   
$ !
$ ! Here is a sample list of definitions for each node:
$ !
$do_default:
$ !Don't know anything about it.  Don't specify anything.
$exit
$ !
$do_gpxbw:
$ ! A gpx monochrome server.  We need to specify a monochrome monitor
$ decw$color == "F"
$exit
$ !
$do_gpxcol:
$ ! A gpx color server.  Color is the default, but we will specify it for
$ ! good measure.
$ decw$color == "T"
$exit
$ !
$do_dutch:
$ decw$keymap == "DUTCH_LK201LH_DP"
$exit
$ !
$do_UK100:
$ !This user wants a UK keyboard and has a 100 dpi monitor
$ decw$keymap == "DECW$UK_LK201RE"
$ decw$server_density == 100
$exit
    ****************************************************************************
    
Directory SYS$COMMON:[SYSLIB]

DECW$TRANSPORT_COMMON.EXE;1
                         33  20-JUL-1990 09:34:39.67  (RWED,RWED,RWED,RE)
DECW$TRANSPORT_DECNET.EXE;1
                         16  20-JUL-1990 09:34:41.57  (RWED,RWED,RWED,RE)
DECW$TRANSPORT_LAT.EXE;1
                         24  20-JUL-1990 09:36:24.38  (RWED,RWED,RWED,RE)
DECW$TRANSPORT_LOCAL.EXE;1
                         16  20-JUL-1990 09:34:40.82  (RWED,RWED,RWED,RE)
DECW$TRANSPORT_TCPIP.EXE;1
                         18  20-JUL-1990 09:34:42.22  (RWED,RWED,RWED,RE)

Total of 5 files, 107 blocks.
3637.4Nothing obviously wrongSTAR::VATNEPeter Vatne, VMS DevelopmentMon Nov 12 1990 17:542
I don't see anything obvious here.  I suggest entering a QAR
in the V5.4-1 database.
3637.5Problem Solved (decw$startserver.com)CIMNET::BELCULFINETue Nov 13 1990 13:294
    With much help from Warren in Colorado software support,
     we found the problem. Someone modified decw$startserver.com.
    
    /David