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

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

166.0. "How to avoid the 'bell' during a terminal input ?" by PADKOA::COSTEUX (Le Plat Pays qui est le mien...) Mon Feb 10 1997 12:04

    A customer has the following problem:
    - his terminal was NOHOSTSYNC - TYPE_AHEAD - NOALTYPEAHD
    - we changed this setting to be NOHOSTSYNC - TYPE_AHEAD - ALTYPEAHD 
     ... and now when he does (as an exemple) a 'long' DIR - then while
    typing one character on this terminal during the running DIR he gets a
    'bell' alarm... How can we avoid that ? The Type_ahead buffer is 256
    char long so it looks to me that the problem is from another cause .
    
    Thanks for help.
    
    Jean-Pierre
T.RTitleUserPersonal
Name
DateLines
166.1Here is the version used.PADKOA::COSTEUXLe Plat Pays qui est le mien...Mon Feb 10 1997 12:051
    ... I forgot to mention that the customer uses OVMS VAX-V7.0 ...
166.2Device?XDELTA::HOFFMANSteve, OpenVMS EngineeringMon Feb 10 1997 13:444
   What type of system, and what type of terminal or DECterm?  (If this
   is a DECterm on an OpenVMS workstation, is the margin bell enabled?
   If so, see the <Options> <Keyboard> display.)
166.3AUSS::GARSONDECcharity Program OfficeMon Feb 10 1997 19:3411
    re .0
    
    If margin bell isn't it...
    
    Please post full SHOW TERMINAL output.
    
    What is the value of the SYSGEN parameters
    	TTY_TYPAHDSZ?
    	TTY_ALTYPAHD?
    	TTY_ALTALARM?
    
166.6SZAJBA::COSTEUXLe Plat Pays qui est le mien...Mon Feb 17 1997 06:0629
	The TTY values are:

	TTY_TYPAHDSZ	256
	TTY_ALTYPAHD	200
	TTY_ALTALARM	242

	... and the terminal (VT340) setup is:


Terminal: _TXA3:      Device_Type: VT300_Series  Owner: GM

   Input:    19200     LFfill:  0      Width:  80      Parity: None
   Output:   19200     CRfill:  0      Page:   24      

Terminal Characteristics:
   Interactive        Echo               Type_ahead         No Escape
   No Hostsync        TTsync             Lowercase          Tab
   Wrap               Scope              No Remote          Eightbit
   Broadcast          No Readsync        No Form            Fulldup
   No Modem           No Local_echo      Autobaud           No Hangup
   No Brdcstmbx       No DMA             Altypeahd          Set_speed
   No Commsync        Line Editing       Overstrike editing No Fallback
   No Dialup          No Secure server   No Disconnect      No Pasthru
   No Syspassword     SIXEL Graphics     Soft Characters    Printer port
   Numeric Keypad     ANSI_CRT           Regis              No Block_mode
   Advanced_video     Edit_mode          DEC_CRT            DEC_CRT2
   DEC_CRT3           No DEC_CRT4        No DEC_CRT5        No Ansi_Color
   VMS Style Input
    
166.7Look In Terminal Setup MenusXDELTA::HOFFMANSteve, OpenVMS EngineeringMon Feb 17 1997 09:3611
   Look in the terminal setup, not at the OpenVMS settings.

   As this is apparently a `real' terminal, look in the terminal's setup
   menus.  There are similar menu options available for DECterm terminals.

   OpenVMS does not normally ring a bell unless explicitly asked to.  To
   see if host software is requesting the bell, enable display of control
   and escape sequences -- most terminals can be configured this way using
   menu options, again, in the terminal setup menus.

166.8Try /HOSTSYNCGIDDAY::GILLINGSa crucible of informative mistakesMon Feb 17 1997 20:0912
> look in the terminal's setup 

  Check for a setting which says "margin bell" or similar. That may cause
  the bell to ring whenever the cursor goes past a particular column

  Remembering behaviour of a *long* time ago, I distinctly remember terminals
  ringing a bell if you continued typing when the typeahead buffer was full. 
  You should be able to prevent that by setting /HOSTSYNC (IMHO that should
  be a default on all systems anyway). I can't reproduce the beep on a 
  DECterm, but it may still happen on a "real" terminal with /NOHOSTSYNC.

						John Gillings, Sydney CSC
166.9AUSS::GARSONDECcharity Program OfficeMon Feb 17 1997 20:3217
re .6
    
>	TTY_TYPAHDSZ	256
>	TTY_ALTYPAHD	200
>	TTY_ALTALARM	242
    
    Those are a little unusual although I can't say that I can see how they
    would cause the problem. Usually TTY_ALTYPAHD is greater than
    TTY_TYPAHDSZ. TTY_ALTALARM only makes sense when it is <= TTY_ALTYPAHD
    (and would typically be at least a few characters less than TTY_ALTYPAHD).
    
    You need to follow the advice from other notes i.e. establish whether
    you have a margin bell and establish whether a bell is being sent
    explicitly by the host. You probably ought to check what flow control
    the terminal is set to generate and what flow control it is set to respect.
    You need to use the terminal's own setup menu for all the things in
    this paragraph.