[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

2560.0. "CREATE/TERMINAL command hangs" by ATSE::DMILLER (Cecil B D'Miller, the esoteric) Mon Apr 02 1990 17:26

	Our cluster was recently upgraded from VMS 5.2 to T5.4.  We can no
	longer create remote DECterms from the cluster onto our workstations.

	A CREATE/TERM/DETA/DISPLAY=node::0 command "hangs" for about 5 minutes
	and finally dies with "%NONAME-E-NOMSG, Message number 02DBC072".

	I suspect some quota on some account needs to be raised, but have
	no idea where to begin looking.

	Any help would be appreciated
	-Dave Miller
T.RTitleUserPersonal
Name		DateLines
2560.1Possible workaroundHANNAH::MESSENGERBob MessengerMon Apr 02 1990 17:3611
Re: .0

Try this:

	$ set display/create/node=xxx
	$ create/term/detach

Some people have had problem with the /display=node::0 method of specifying
the display name.

				-- Bob
2560.2Nope, happens either wayATSE::DMILLERCecil B D'Miller, the esotericMon Apr 02 1990 18:020
2560.3Make that run sys$system:decw$terminalHANNAH::MESSENGERBob MessengerMon Apr 02 1990 18:4718
Re: .2

Here are a couple more things to try:

1. Before giving the create/term command, define a logical name
   DECW$DECTERM_OUTPUT to point to the name of a log file; then you might
   be able to see why the DECterm controller can't start.

2. From a privileged account:

	$ set proc/priv=(share,sysnam,phy_io)
	$ set display/create/node=xxxx
	$ run decw$terminal

   Once the DECterm controller has displayed its startup message, try
   issuing the create/term command in another window.

				-- Bob
2560.4Hasn't worked for over a week, but today...ATSE::DMILLERCecil B D'Miller, the esotericTue Apr 03 1990 14:319
	I am now totally confused.

	I defined DECW$DECTERM_OUTPUT and issue my CREATE/TERM command...
	This time it worked!  I've gone and created 5 or 6 of them now
	without a problem.

	Curiouser and curiouser...

	-Dave
2560.5Still experiencing "hang" problem with CREATE/TERMREORG::GILLISMark Gillis, DTN 264-4167, NUO1-1/G10Wed Jun 20 1990 10:5838
I have also been experiencing this "hang" problem with the DECTERM Controller
but I haven't been able figure out why.

I am executing $CREATE/TERM on a remote node in a MI cluster running VMS V5.3
and "serving" my workstation. My security file is set up properly, as I have
other DECWINDOWS applications running remotely.

I set host from my workstation, TURGON, to a remote node on the MI cluster,
REORG and attempt the following:

$ show display
%SYSTEM-W-NOSUCHDEV, no such device available
-SHOW-W-OPENIN, error opening DECW$DISPLAY as input
$ set display/create/node=turgon
$ $ CREATE/TERM/DETACH/PROCESS="DCL1"/WINDOW=(INIT=ICON,TITL=DCL1,ICON_NAME=DCL1
)
REORG::_RTA23: 09:52:23 DECW$TERM CPU=00:00:02.15 PF=1355 IO=218 MEM=408
REORG::_RTA23: 09:52:33 DECW$TERM CPU=00:00:02.15 PF=1358 IO=219 MEM=411
REORG::_RTA23: 09:52:44 DECW$TERM CPU=00:00:02.15 PF=1358 IO=220 MEM=411
REORG::_RTA23: 09:52:58 DECW$TERM CPU=00:00:02.16 PF=1358 IO=221 MEM=411
REORG::_RTA23: 09:53:05 DECW$TERM CPU=00:00:02.17 PF=1358 IO=222 MEM=411
REORG::_RTA23: 09:53:16 DECW$TERM CPU=00:00:02.17 PF=1358 IO=223 MEM=411
REORG::_RTA23: 09:53:22 DECW$TERM CPU=00:00:02.18 PF=1358 IO=224 MEM=411
REORG::_RTA23: 09:53:24 DECW$TERM CPU=00:00:02.20 PF=1358 IO=225 MEM=411
 Interrupt

$ stop
$ show display

    Device:    WSA98:  [super]
    Node:      TURGON
    Transport: DECNET
    Server:    0
    Screen:    0

Any suggestions?

Thanks,
2560.6HANNAH::MESSENGERBob MessengerWed Jun 20 1990 14:5618
Re: .5

CREATE/TERMINAL (actually DECwTermPort) waits 5 minutes trying to create a
DECterm window before it gives up.  Normally it should never have to wait
the full 5 minutes because the DECterm controller sends it a termination
message, but for some reason this message doesn't always get sent.

To find out why DECterm can't create a new window, define a logical name
DECW$DECTERM_OUTPUT in the process that will do the CREATE/TERMINAL to be
the name of a log file.  Post the log file output as a reply to this note.

DECterm might be failing or hanging because some DECW$* logical names are
defined that make DECwTermPort think that the DECterm controller is running
when it isn't.  Another possibility is that your BYTCNT quota is too low,
which can cause DECterm to hang.  Some people have reported problems with
the /PROCESS qualifier, so you might want to try omitting it.

				-- Bob
2560.7my solutionBLKPUD::THOMASAWow I,ve got a colour ....Thu Aug 23 1990 06:3314
Hi all,
	I have seen problems with decterms in the past related to the process
DECW$TE_n which I think is used to controll all your DECterms on a particular
node .  This process was seen to go into an RWAST because it ran out of bytlm
quota. This process picks up its quotas from the PQL_ parameters, so adjusting
these fixed my problem.


in modparams.dat

	min_pql_dbytlm=32000
	min_pql_mbytlm=32000

			Andy