[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

3059.0. "display a message in the SM message window" by UNTADA::BACHNER (I'm not a bug, I'm a feature) Tue Jul 10 1990 12:46

I've already scanned a little bit through this conference and it's keywords, but
did not find a reference to this problem.

I've defined a local Application verb in the Session Manager which invokes a 
command procedure. How can I display messages from this procedure in the SM 
message area ?  I'd like to issue a message if (for some reason, which is 
checked for in the command procedure, I cannot invoke the actual application.

Thanks for your help, or any pointers to other entries in this conference,
Hans.
T.RTitleUserPersonal
Name		DateLines
3059.1SMAUG::MENDELIn some strange power's employTue Jul 10 1990 13:141
        Write to your parent process's terminal.
3059.2unfortunately notUNTADH::BACHNERI'm not a bug, I'm a featureWed Jul 11 1990 10:287
Doesn't work - apparently, the process to execute the application command is
created detached.

Any other ideas ?

Thanks,
Hans.
3059.3SMAUG::MENDELIn some strange power's employWed Jul 11 1990 13:138
>>> Any other ideas ?

    Patience?

    Well, the creating process then. Either way, its the Session Manager
    Process. The one executing DECW$SESSION.EXE.

    Kevin
3059.4Be careful it only works for single seat workstations...IO::MCCARTNEYJames T. McCartney III - DTN 381-2244 ZK02-2/N24Wed Jul 11 1990 13:383
Which one executing DECW$SESSION.EXE -- I have two...

James
3059.5Be careful of VT1000's too!PINALL::BRENNAN_JJ.D. Brennan, Boeing Business GroupWed Jul 11 1990 16:0012
    Ignoring multi-head workstations and VT1000s, it is easy to
    find the session manager. I've been playing with this problem
    too. I find the session manager's terminal and use sys$brkthru
    to send a message to it.

    You could however use sys$brkthru to send a message to the
    current username. This will definitely get to the session
    manager, but it may get to other places where you don't want
    it too.

    Good luck!
    JD
3059.6CLTMAX::dickSchoeller - Failed XperimentThu Jul 12 1990 07:476
I would send to the username.  If the user doesn't like all the crap on
the terminal windows, they can do set broad=none there.  I recommend that
anyway.  The only places I would want to see stuff is the SM window and
the popup in banner.

Dick
3059.7DEMON3::CLEVELANDNotes - fun or satanic cult?Thu Jul 12 1990 09:114
    One simple solution is to change the process name to something unique
    in DECW$LOGIN.COM...
    
    Tim
3059.8Is there no way to determine the creating process?SMAUG::MENDELIn some strange power's employThu Jul 12 1990 12:535
>>> Which one executing DECW$SESSION.EXE -- I have two...

    The one you want the message to appear on, of course! :-)

    Kevin
3059.9How are you related to your sister-in-law's brother's wife?IO::MCCARTNEYJames T. McCartney III - DTN 381-2244 ZK02-2/N24Thu Jul 12 1990 15:423
Not really since the processes are peers not parent-child.