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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

2296.0. "Auto start a window?" by CVMS::DOTEN (Right theory, wrong universe.) Sat Feb 17 1990 19:09

I'm trying to figure out how to start up a window (probably within
DECW$LOGIN.COM) that will enable itself as an operator terminal and sit there
receiving OPCOM messages and allow me to enter OPCOM commands in it.

At first, I thought CREATE/TERMINAL/DETACHED was it but I can't specify a
command line using /DETACHED. So I tried /INPUT but that executes the commands
in the input file and then sits there without issuing a DCL prompt and just
loops accumulating lots of CPU time.

In a nutshell I'd like to automatically start a window and issue the
REPLY/ENABLE command in it and have it sit there at the DCL prompt so if a tape
mount message comes in I can click on that window and do the REPLY/TO stuff.

Possible?

-Glenn-

P.S.: I couldn't find any note titles that might discuss this type of thing.
T.RTitleUserPersonal
Name
DateLines
2296.1/PROCESS=fooIOSG::MARCHANTWeathering the weatherSun Feb 18 1990 16:4811
    Hi Glenn,
	the way I run arbitrary commands, is to set the process name on the
    CREATE/TERMINAL command. At the end of my login.com, I have:

	$ xlogin = f$search("[.login]"+f$getjpi(0,"prcnam")+".com")
	$ if xlogin.nes."" then @'xlogin'

    which will execute a <process-name>.COM file (if it exists) before exiting
    to DCL.

    Paul.