G From:	CSBVAX::MRGATE!LEICHTER@Venus.YCC.Yale.Edu@SMTP 17-MAY-1988 09:09  To:	ARISIA::EVERHART= Subj:	re: Where do I look for SYSGEN param on MODEM hangups ?     T Received: from Venus.YCC.Yale.Edu by KL.SRI.COM with TCP; Sun 15 May 88 12:07:37-PDT Date: Sun, 15 May 88 14:36 EST3 From: "Jerry Leichter (LEICHTER-JERRY@CS.YALE.EDU)"   <LEICHTER@Venus.YCC.Yale.Edu>@ Subject: re: Where do I look for SYSGEN param on MODEM hangups ?, To: ANK@CUNYVMS1.BITNET, INFO-VAX@KL.SRI.COM* X-VMS-To: IN%"ANK@CUNYVMS1.BITNET",INFOVAX  C 	Of late we have been having problems with some of our MODEM lines. : 	People get HUNG or get a connect and no response, or USER 	authorization failure.    	our modems as defined as > 	$ SET TERM TTC1:/AUTOBAUD/DISCONNECT/MODEM/HANGUP/PERM/DIALUP  F 	a show term ttcX indicates that some are set as /nohangup even though 	all are will /HANGUP    Eh?  What does this line mean?  G 	I read in I/O users manual about setting it to HANGUP for all but I am  	not sure how.?   
 And this one?   G 	I listed the SYSGEN params list to find which one's if any were set by  	default to /nohangup   E The default terminal parameters are controlled by the TTY_DEFCHAR and I TTY_DEFCHAR2 parameters.  These are a bit painful to work with since they L are bit-encoded, corresponding to the terminal parameters defined in the I/OL User's Guide.  To manipulate them, you need to figure out which bit in whichK terminal parameter word is of interest, then set it appropriately.  This is M really only necessary for a couple of parameters (like DISCONNECT) and mainly M for LAT lines, not real terminal lines.  The easier way to set the parameters M for real terminal lines is as you appear to have done it:  With SET TERM/PERM & commands issued during system startup.  F 	I guess my question is: How can we assure that all modem ports behave; 	exactly as we set them out to be in our above definitions.   M There are two sets of parameters associated with a terminal line:  Active and K permanent.  Essentially, the permanent ones are copied into the active ones L when someone logs in on the line.  (This isn't really how it works; in fact,K as I recall they really get copied when the last channel to the terminal is J deassigned.  But it's probably OK to think of it as happening on login forK now.)  The permanent parameters are then not looked at again until the next M login - it is the active ones that control what happens on the terminal line, H and it is the active ones that a normal SET TERM changes.  They are also what a SHOW TERM will display.  L No matter what the permanent settings say, if a SET TERM/NOHANGUP is issued,M either as a DCL command or by a program doing the equivalent SETMODE QIO, the M terminal's active parameters will now say /NOHANGUP, and the line will not be  hung up on logout.  L But...there's an additional factor at play.  Because the /HANGUP - /NOHANGUPH distinction has security implications, VMS provides a way for the systemG manager to keep users from screwing around with the setting.  Normally, H privilege (LOG_IO or PHYS_IO) is required to change the /HANGUP setting.H It is possible to allow non-privileged users to change the setting for aL particular line by setting the TT2$M_MODHANGUP characteristic for that line.I There is no SET TERM qualifier for for this characteristic - it has to be H set by a program, or in the TTY_DEFCHAR2 parameter.  The bit you want isJ bit 3 (value 8).  (I found that by looking in SYS$LIBRARY:TT2DEF.H, by theM way.) If this bit is on, users will be able (by default) to modify the hangup N setting.  The default setting for this bit, i.e., in the value of TTY_DEFCHAR2J in VMS "out of the box" - is OFF:  Users CANNOT modify the hangup setting.L Check with SYSGEN to determine if the value on your system has been changed.M (CAUTION:  The value displayed by SYSGEN is always in decimal, and the values L accept by a SYSGEN SET command are normally in decimal, though you can use aL %X prefix to enter hex if you want.  Dealing with bits in decimal is painfulN and tricky.  Many systems have ended up in strange states when someone screwedF up and mixed bases in setting the TTY parameters, flipping some random! assortment of bits.  Be careful!)   C 	Our users are getting paranoid with the semester coming to an end.   K Having said all that about /HANGUP:  It's not clear to me what problems you J are actually seeing, or what they have to do with /HANGUP.  You've given aH vague description, and also provided a guess as to what you think is theK cause of the problem you've vaguely described.  That makes it very hard for I anyone to give you much help.  Next time, you would do better to DESCRIBE J THE SYMPTOMS YOU ACTUALLY SEE, not what you think is behind them.  You mayJ be wrong, in which case you will at best get advice that can only lead you further down an incorrect path.  							-- Jerry 