| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1047.1 | | LESLIE::LESLIE | Gentlemen! Let's broaden our minds! | Sat Jul 01 1989 03:49 | 5 |
| You can't. What are you trying to acheive? Is there an alternative way
of doing this?
- ���
|
| 1047.2 | What I was trying to do... | AISG::COMELLA | John Comella, DTN 291-8483 | Wed Jul 26 1989 23:29 | 23 |
| What was I trying to do?
I used to ask myself if I was logged-in from home so I could keep track of my
home-usage. But I have since realized that I can't log into a DECW machine
anyway. I guess that I'll have to log into the local cluster from home.
It looks like I'll just read the nodename in LOGIN, and if it's my uVAX, I'll
bypass the INQUIRE statement.
Not being able to log-into a DECW machine remotely is a real pain in the
neck. Maybe I should write a routine that shuts my machine down when I log
out at 6 PM and reboots it under UIS. But then I'm faced with either
waiting forever in the morning to reboot it or having another automatic
routine do the reverse at 7:30 AM (except weekends). Hmmm. This DECwindows
stuff had better be really good.
Thanks.
John
Does anyone have a strategy for dealing with modems? I think I know the
answer: someone will probably make a fortune when they come up with one.
|
| 1047.3 | Did I miss something? | QUARK::LIONEL | Free advice is worth every cent | Wed Jul 26 1989 23:40 | 5 |
| I don't understand - why can't you log into a DECwindows system from
home? I'm doing that just now.
Steve
|
| 1047.4 | | STAR::MFOLEY | Rebel without a Clue | Thu Jul 27 1989 00:17 | 6 |
|
What are you trying to do? I'm confused...
mike
|
| 1047.5 | VWSLAT? | VANPYR::BLAKE | The Rottweiler did it | Thu Jul 27 1989 05:43 | 6 |
| You wouldn't be running VWSLAT from your workstartion, would you? That
disables incoming LAT connections. If so, simple stop VWSLAT before
going home (and @LTLOAD) and restart it in the morning.
Colin.
|
| 1047.6 | Workaround for DCL INQUIRE for DECterm LOGIN.com ?
| SAC::WOOD_J | | Mon Mar 12 1990 06:50 | 41 |
|
I had a "$ INQUIRE _purge" statement in my LOGIN.COM, which would ask me if
I wanted to purge certain files. This worked fine on DECwindows workstations
with VMS v5.2, but when I upgraded to v5.3 both my Fileview and DECterm
sessions failed to appear.
I have played about with my LOGIN.com, and have observed the following:
o If my LOGIN.com just says
$ INQUIRE _something ! i.e. one line
no DECterms nor Fileviews appear.
o If my LOGIN.com ia as follows: (based on VMS v5.3 Release Notes example,
1.7.3.2, p1-10):
$ if f$getdvi( "sys$output:", "trm" )
$ then
$ devnam = f$getdvi( "sys$output:", "devnam" ) - "_" - "_"
$ devnam = f$extract( 0, 2, devnam )
$ write sys$output "Devnam is ''devnam'"
$ if devnam .nes. "TW" then goto skip_inq
$ inquire _input
$ skip_inq:
$ endif
the effect seems to be as I want it. That is, when the DECterms are created
I am prompted for input, and the Fileview session appears OK. Can I rely on
this ?
I wonder if I am not understanding something here. Why should the first
LOGIN.com (of just INQUIRE) prevent the DECterms being created, whilst
the second LOGIN works OK ?
What about captive accounts on workstations ? Are these not possible ?
Thanks in anticipation,
John Wood
|
| 1047.7 | | SMAUG::MENDEL | In some strange power's employ | Mon Mar 12 1990 12:18 | 11 |
| See Note 2320, and others.
Session Manager starts up interactive processes with mailbox
terminals. Therefore, the Inquire either fails, or reads the the
"CREATE/TERM" command from the SM as its input.
Check to see, in login.com, if the terminal is a mailbox.
(f$loc("MBA",f$trn("TT")) .eq. 0). If it is, treat it as a batch or
network process - only define logicals and symbols.
Kevin
|
| 1047.8 | Test whether input source is a terminal | BOMBE::MOORE | Eat or be eaten | Mon Mar 12 1990 21:53 | 4 |
| I think all you really need is:
$ if f$getdvi("SYS$COMMAND","trm") then INQUIRE etc...
|
| 1047.9 | | DECWIN::FISHER | Prune Juice: A Warrior's Drink! | Tue Mar 13 1990 12:18 | 4 |
| Looking for the TW device won't work forever. We will be switching to a new
pseudo-terminal sometime, and that will have a different device name.
Burns
|