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

Conference vaxaxp::alphanotes

Title:Alpha Support Conference
Notice:This is a new Alphanotes, please read note 2.2
Moderator:VAXAXP::BERNARDO
Created:Thu Jan 02 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:128
Total number of notes:617

61.0. "OPA1 port timeout...(with alpopdr02_062)" by FORAT::JLS (Are we in the same ship?) Wed Mar 12 1997 13:49

    
	Hello,

	A customer is getting into trouble working with the OPA1 port.
	Is there any solution?

	Thanks in advance,

						/jls 

	Data:

	Configuration:

		 ASTN 200 4/166  -  OVMS ALPHA 6.2 
		 ECO: ALPOPDR02_062 installed.
		      (SYS$OPDRIVER : X61Q-SSB-110 / 24-OCT-1995 18:17)
	         OPA1: Printer NON-DEC (MICROLINE 321) - speed: 9600.
		 TTA0: VT525 - speed: 19200.

	Problem: 

		 The customer application is issuing QIOs directly to port 
		 OPA1 and TTA0 according to messages ("alarms") received.
		 Sometimes,when there are several messages to send to port 
		 opa1....the port hangs and the customer has to reboot the 
		 system.

	         In the hang situation,if we stop the application and try 
		 to copy a file to opa1,we get the errors:

		   % copy-e-writeerr-
		   - rms-f-wer
		   - system-f-timeout
		   % copy-w-notcmplt

		 We see the error count of opa1 is incrementing too.


	         We have available a crash dump produced in the hang 
		 situation,if it can help in the troubleshooting.

		 We've intalled the ECO alpopdr02_062,but the problem has
	         been reproduced again.

		        	
	        note: Please,comment if it�s necessary to cross an entry 
    	              in another conference,like ALPHASTATION,for example.
T.RTitleUserPersonal
Name		DateLines
61.1IPMT, PleaseXDELTA::HOFFMANSteve, OpenVMS EngineeringWed Mar 12 1997 15:5325
		        	
:   note: Please,comment if it�s necessary to cross an entry 
:   in another conference,like ALPHASTATION,for example.

   If you want this looked at, please raise an IPMT, providing a copy
   of the crashdump and -- if at all feasible -- an example program
   that can be used to duplicate the problem here in engineering.

   You will also want to see if both the port and the printer have
   locked up waiting for the other to send the XON -- I'd definitely
   use the ALTYPEAHD on the port, and I'd look seriously at getting
   that printer onto a communications line other than the console.
   (DECserver via LAT, etc.)

   As a WAG, try issuing a SET TERMINAL/XON against the console port,
   when the port is locked up...

   (VAXAXP::VMSNOTES is better suited to OpenVMS questions -- this
   is the "generic Alpha" conference.)

   See the following support articles: "{Elev} AlphaStation 255 OpenVMS
   6.21H2 OPA0: Console Hangs Intermittent", "[OpenVMS] SYSTEMFTIMEOUT
   Using Console For DCL & TPU On 8xxx Alphas", and check for other
   elevations.
61.2Known problemSTAR::KENNEYThu Mar 13 1997 07:4610
    
    	This was fixed quite a long time ago.  We gave the group that makes
    up the kits the fix.  Some where along the way the fix managed to not to
    get into the kit that was supposed to fix it.  In the fall we     
    discovered this and asked that the kit be corrected.  I checked and 
    as far as I can tell this kit has never been released.  We have asked
    the folks who make kits to look into this.
    
    
    forrest
61.3AMCFAC::RABAHYdtn 471-5160, outside 1-810-347-5160Thu Mar 13 1997 10:045
re .1:

Hey, hey, hey, what the heck is SET TERMINAL /XON???

Tain't documented in the online help.
61.4Status update a kit is on the horizonSTAR::KENNEYThu Mar 13 1997 11:5412
    RE: .2
    	Got mail from the group that issues kits and they hope to get to
    this by the end of the month.  Which means that if you include the fact
    that we originally gave them a fix last spring it will be about 12 months
    before customers get a working kit.
    
    
    RE: .3 
    	Not documented because it does not really work.  In theory it is
    a way to force an XON to a stuck terminal.
    
    Forrest
61.5better one year than never....!FORAT::JLSAre we in the same ship?Thu Mar 13 1997 12:3715
    
    	Forrest,
    
    	How will I get the fix? You�ll write a reply pointing where I 
    	can get it? It will be accesible via TIMA,FTP...? Which will be
    	the name of the kit...ALPOPDR03_062,perhaps?
    
    
    	Thanks in advance,
    
    							/jls.
    
        Note: Not to bad to hear the "trip" is only 12 months...perhaps
        someone said:"...you'll get the fix at spring time..",but he forgot
    	to say the year....
61.6Will see if I can find a fixed image STAR::KENNEYThu Mar 13 1997 14:4610
    
    	Once, they produce the kit and release it, it should show up on the 
    web page etc.  I can probably hunt around and see if there is an image
    laying around somewhere and get it to you that way.  But it won't be a 
    kit.
    
    
    Forrest
    Ps.		Send me mail if you want a kit with a location to copy it
    		to or a place I email you an image.