[ From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX"  6-DEC-1990 09:26:33.79  To:	MRGATE::"ARISIA::EVERHART" CC:	2 Subj:	Re: Session Manager window enabled for OPCOM  * Received:  by crdgw1.ge.com (5.57/GE 1.80)( 	 id AA08059; Thu, 6 Dec 90 09:09:42 ESTk Received: From ucbvax.Berkeley.EDU ([128.32.130.12]) by CRVAX.SRI.COM with TCP; Wed,  5 DEC 90 19:09:33 PST , Received: by ucbvax.Berkeley.EDU (5.63/1.42)) 	id AA06740; Wed, 5 Dec 90 18:39:39 -0800 9 Received: from USENET by ucbvax.Berkeley.EDU with netnews . 	for info-vax@kl.sri.com (info-vax@kl.sri.com); 	(contact usenet@ucbvax.Berkeley.EDU if you have questions)  Date: 5 Dec 90 05:23:04 GMT ! From: infopiz!mark@decwrl.dec.com ? Organization: INFO COMM - Computer Consulting, Redwood City, Ca 5 Subject: Re: Session Manager window enabled for OPCOM ( Message-Id: <5163.275c21c8@infocomm.com>2 References: <1990Nov26.084300@uvphys.phys,uvic.ca># Sender: info-vax-request@kl.sri.com  To: info-vax@kl.sri.com   W In article <1990Nov26.084300@uvphys.phys,uvic.ca>, zapantis@uvphys.phys,uvic.ca writes: N > Does anyone know how to enable the DECWINDOWS(VMS) session manager window toM > receive OPCOM messages? There must be a way of doing a REPLY/ENABLE on that 	 > window.   K This was asked a week or so ago, and no one has answered, so I'll post what L I've got on our systems here.  With this procedure any account that has OPERJ priv will end up with the Session Manager Message window enabled for OPCOMI messages while logged in.  This can obviously be altered depending on the > requirements of your site.  Digital supplies an empty templateG SYS$MANAGER:DECW$SYLOGIN.COM file, use this in it's place and have fun.    --  @ Mark Pizzolato - INFO COMM Computer Consulting, Redwood City, CaL PHONE:	(415)369-9366	UUCP:  decwrl!infopiz!mark or uunet!lupine!infopiz!mark DOMAIN:	mark@infocomm.com    $ ! = $ ! DECW$SYLOGIN.COM - Initialize the DECwindows applications  $ !  $ ! L $ ! This command procedure is executed when a user logs into the workstationF $ ! with DECwindows.  You may run clients from this command file whichE $ ! you would like all users of your system to have running when they  $ ! log into their workstation.  $ ! D $ ! If this process doesn't have an owner, then we are being invokedK $ ! directly from the session manager, if we do have an owner, we are being K $ ! called recursively in the context of a subprocess.  The reason we need  K $ ! to use a subprocess, is that for some strange reason, when a DECwindows N $ ! session is initially created with the session manager, the session managerE $ ! process is actually created with it's input being the appropriate M $ ! DECW$DISPLAY device (i.e. WSAn:).  A PTY (TWAn:) is later attached by the K $ ! session manager to provide the session "Messages" window. and to have a I $ ! window to catch things like newmail messages, etc.  Here we create a  I $ ! subprocess actually running this procedure.  When the subprocess runs O $ ! it's ONLY job is to hang around for a while waiting for it's OWNER (parent) ? $ ! process to have a "TERMINAL" associated with it.  Once this I $ ! process/terminal relationship is observed, the PTY (TWAn) that is the D $ ! "TERMINAL" is enabled as an operator console.  Note: all of thisK $ ! foolishness is only done if the original (Session Manager) process has  O $ ! OPER priv, which will allow the eventual enabling of the PTY as an operator  $ ! console, anyway. $ !  $ owner = f$getjpi("","OWNER") $ if owner.NES."" 	 $    then  $ loop:	wait 0:0:20 6 $	if f$getjpi(owner, "TERMINAL").eqs."" then goto loop7 $	assign/user 'f$getjpi(owner, "TERMINAL")' sys$command  $	reply/enable $	exit	 $    else G $	if f$privilege("OPER") then spawn/nowait @'f$environment("PROCEDURE")  $ endif   