Conference bulova::decw_jan-89_to_nov-90

       
       
       	Is someone defining DECW$DISPLAY in a startup file specific to
       that node?
       
       							mike

    Mike,
    	As far as I can tell, DECW$DISPLAY is NOT defined any differend
    	on the problem node. I believe it equates to WSA2:
    
    	thanks!

    I seem to have the same error message on an LAVC with 4 VAXstation
    3100s.  The enviroment for each 3100 is identical and different users
    logging in will successfully activate this remote copy of fileview from
    the same workstation.  When a failure occurs, the netserver.log file
    has the following:
    
        Connect request received at 26-JUL-1989 08:51:43.60
            from remote process PGVS3::"0=MKING"
            for object "SYS$MANAGER:FILEVIEW.COM"

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

$ open/read/error=error netfile sys$net
$ read/error=error netfile node
$ user = f$getjpi( "", "username" )
$ user = f$extract(0,f$locate(" ",user), user)
$ user = f$extract(0, 15, "V_PGVS3_MKING" )
$ set proc/name="V_PGVS3_MKING"
$ close netfile
$ set display/create/node=PGVS3/perm/tranport=decnet
$ run sys$system:vue$master
X Toolkit Error: Can't Open display
%DWT-F-DWTABORT, xtoolkit fatal error
$ error:
$ stop
  MKING        job terminated at 26-JUL-1989 08:51:52.89

  Accounting information:
  Buffered I/O count:          131      Peak working set size:   889
  Direct I/O count:             63      Peak page file size:    5750
  Page faults:                1384      Mounted volumes:           0
  Charged CPU time:     0 00:00:02.17   Elapsed time:     0 00:00:12.49
    
    I've checked screen permissions, DECnet proxies, priviledges, etc.
    All workstations worked successfully 7 days ago but something changed
    and I can't identify the change.
    
    Could someone give me ideas on what causes the X Toolkit Error message?
    
    Thanks for any assistance
    
    Mark King
    MAA Program Support Group
    

    I decided to remove the satellite from the cluster and re-add
    it, hoping that this would help.
    
    Now we're getting an access violation when trying to create
    a terminal window!
    
    I can provide more information if needed.
    If anyone else has had this problem and knows how to fix it, please
    let me know!!!??? thanks!
    

Re: .4

Have you tried increasing your GBLPAGES and GBLSECTIONS parameters in
SYSGEN?  Maybe it's time for an AUTOGEN.

				-- Bob

    
    Check that you have enough global pages and global sections.   For
    every client which runs locally on the machine, you need one global
    section and about 200 free global pages.   You can determine how many
    global sections are currently in use, and how many global pages are
    free by using the command
    	mcr install
    	mcr>/global
    
    F$GETSYI can also give you the count of free global pages and global 
    sections.
    
    At the end of the list of installed images, you will get the count of
    global sections used and global pages free.  
    
    The error that comes back from an application which tries to connect
    and the resources are not available is "Can't open display".   We
    are working on better error handling of the gblpages problem for V2.
    
    

    Upping GBLSECTIONS and GLBPAGES fixed it.
    The original values were 640 for GLBSECTIONS and 29120 for GBLPAGES.
    I upped GLBPAGES to 35000 and GBLSECTIONS to 680. So, I don't know
    which really fixed the problem. However, I'm baffled more now!
    I checked another C-VAX in another MIVC running DECwindows and
    GBLPAGES were 26800 (lower than the 29120 on the problem node) and
    GBLSECTIONS were 300 (lower than the 640 on the problem node)! There
    are a few other parameters that are different but none that I thought
    were significant.
    
    Would the sizes of each MIVC make a difference? The cluster that housed
    the problem CVAX has 45 nodes, the other CVAX with the lower values
    belonged to a cluster with 25 nodes.
    
    Thanks to everyone who responded!
    
    	-diane
    

Try the following.

$ install :==  $install/command
$ install
install>list/global

This will give you the global section and global page usage on your
machine.

For DECWindows V1 each local shared memory connection used 276 global pages
and 1 global section. Typically each application has one connection, I believe
that all the decterms go through only one connection. For DECWindows V2 FT1
each shared memory connection uses 171 pages and 1 global section. Most
of the other global page and global section usage are usually from installed
images.
						Bill

    RE: .8 (and others in this file)

    I don't remember exactly when it happened but I know that INSTALL is
    now a regular old DCL command since at least V5.1, maybe (probably)
    V5.0.

    $ install list/global/summary

    works just great, without needing the:

    $ install :== $install/command