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

Conference ilbbak::ibi_focus

Title:FOCUS, from INFORMATION BUILDERS
Moderator:ZAYIUS::BROUILLETTE
Created:Thu Feb 19 1987
Last Modified:Mon May 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:615
Total number of notes:1779

244.0. "Remote Image not Terminating!!!" by CSG001::PULSE () Tue Jul 25 1989 12:07

    
    	I am a data center technical manager at PDM.  We have FOCUS
    	users.  Currently, one of our FOCUS users is SETting HOST
    	from her workstation to use FOCUS on the site timesharing
    	VAXcluster.  
    
    	Each time she exits FOCUS, her FOCUS image keeps running,
    	and I mean running wild.  It is like having another NULL
    	job running, only this one runs at PRIO 4.
    
    	We are running VMS V4.7, IBI-FOCUS V5.2/VX5.2.1
    	
    	Any help with this would be appreciated.
    
    	Daya
    
T.RTitleUserPersonal
Name
DateLines
244.1Same problem with VMS 5.0-2 and LATEUCWS4::FAGETTIRed BaronWed Aug 02 1989 09:3823
I'm a member of Italian EUS team and we have experienced the same problem:

	1. Users via SET HOST who log out from terminal servers 
	2. Users connaect via LAT and kicked out from terminal servers
		
	When this happen issuing the command SH TERM xxx , VMS display the 
	message :

	Device OFF line or out of configuration.

	It seems that when these users are in HOT SCREEN or a CRTFORM and 
	the connection is lost the FOCUS i/o terminal handling go crazy.

	We have implemented a simple workaround checking the status of each 
	terminal every 20 minutes via the lexical F$GETDVI("xxx","DEVSTS");
	If the returned value is 9 then a reply warns the SUPPORT specialist
	to check that user/terminal.

	Any other solution which can avoid the problem is really WELCOME !

Best regards

Luca
244.2Then .. a workaroundEUCWS4::FAGETTIRed BaronFri Sep 15 1989 12:5466
Hi Daya,

i did a workaround which run in a batch /RESTART priveleged process :

It checks the terminal status to identify if it's into the 'disconnect' status.

it's running on our systems (ALL-IN-1 has the same problem sometimes) and it 
works fine with low CPU load.

Obviously you can trim it as you like.

Ciao

$!
$ ON ERROR THEN EXIT
$!
$ SET NOON
$ PURGE/KEEP=3 SYS$LOGIN:CK_TERM.LOG
$ SET ON
$!
$ SET NOVERIFY
$!
$ SET PROC/PRIV=ALL/PRIO=4	! to run well
$!
$WLOOP:
$!
$ SET NOON
$ SET PROT=O=REWD 	SYS$LOGIN:CK_TERM.LIS;*
$ DELETE/NOCONFIRM	SYS$LOGIN:CK_TERM.LIS;*
$ SET ON
$!
$ SHOW USER /OUT=SYS$LOGIN:CK_TERM.LIS
$!
$ OPEN IN_F SYS$LOGIN:CK_TERM.LIS
$!
$ READ/END=FINE IN_F IN_R
$ READ/END=FINE IN_F IN_R
$ READ/END=FINE IN_F IN_R
$!
$LOOP:
$!
$ READ/END=FINE IN_F IN_R
$!
$ IN_R=F$EDIT(IN_R,"COMPRESS,TRIM") 
$!
$ U_T=F$ELEMENT(3," ",IN_R)
$!
$ IF F$GETDVI("''U_T'","DEVSTS") .EQ. 9 THEN -
  REPLY/USER=(EUCOPNS,EUCTEST)/BELL/URGENT -
  "
----------
PLEASE CHECK PROCESS ---> ''IN_R'  
----------"
$!
$! SET PROC/ID='F$ELEMENT(2," ",IN_R)'/SUSP
$!
$ GOTO LOOP
$!
$FINE:
$!
$ CLOSE IN_F
$!
$ WAIT 00:15
$!
$ GOTO WLOOP
$!---