home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!ucbvax!CCS1.BBN.COM!RMCEWEN
- From: RMCEWEN@CCS1.BBN.COM (Regis McEwen)
- Newsgroups: comp.os.vms
- Subject: Re: TT_AccPorNam field remains null on a SHOW USERS o
- Message-ID: <01GTBXRE6WEO002FVU@ccs1.bbn.com>
- Date: 10 Jan 93 02:37:00 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: world
- Organization: The Internet
- Lines: 46
-
- In article <930104133534.21c002ab@LUDWIG.CTD.ORNL.GOV>,LPZ@LUDWIG.CTD.ORNL.GOV, (Lawrence MacIntyre - 615.576.0824) writes:
-
- [...]
-
- > This is all very nice, but the point is, if I have an xterm, and I have it set
- > to a different size than 24x80, I don't want you changing it to 24x80 just
- > because you never used an xterminal or a workstation and don't understand what
- >set term/inquire does. I would want to shoot you as well, after about the 23rd
- > time. You can detect the xterminal unless it is used to set host or telnet to
- > you, so the short answer is DON'T put Set Term/Inquire in the system login.
-
- I agree with what you are saying and I would like to offer some
- thoughts to an alternative invocation of SET TERMINAL/INQUIRE.
-
- Here are some interesting tidbits that may be useful at some sites:
-
- If you are ONLY interested in keeping the same dimensions of your
- screen AND you wish to execute a SET TERMINAL/INQUIRE, you can:
-
- $ set terminal/inquire -
- /page='f$getdvi("sys$command","tt_page") -
- /width='f$getdvi("sys$command","devbufsiz")
-
- This will preserve the length and width of the screen, xterminal or
- workstation and can be used in conjuction with whatever other checks
- you wish to make, such as executing it only if the SYS$COMMAND is
- indeed a terminal and/or any other conditions. [The /WIDTH qualifier
- is best only used with SET TERMINAL/INQUIRE if the width you wish to
- preserve is not 80, because it clears the screen].
-
- When part of the system-wide SYLOGIN procedure, stringent test should
- be made *first* before it is executed in order for it to not undo any
- of the characteristics set that may be desirable. This is especially
- true for a KNOWN terminal, which in most (all?) cases the command
- probably should NOT be automatically executed upon LOGIN, if at all.
-
- I would also recommend that the qualifier /WIDTH in the case of a
- system-wide SYLOGIN NOT be used because it causes the terminal screen
- to be cleared. Important messages, like, "why wasn't I able to LOGIN?"
- might be missed if that "terminal" that that LOGIN session was invoked
- in, disappeared, for whatever reason.
-
-
- -Regis
-
-
-