Conference bulova::decw_jan-89_to_nov-90

2701.0. "RFI on session management." by SDOGUS::HOOKER (Waikiki when you can San Diego) Wed May 02 1990 17:38

For any DECwindows/VMS guru:
	I need to know the cleanest way from an application to stop a users
session and startup the login window.  To define clean, I am looking for 
ways that can use the VAX calling standard (this is so it can be implemented
by ZCALLS in MUMPS ((that's right MUMPS))), takes as little time as possible,
and can be supported.  I prefer avoiding any hacks if possible.  We are trying
to invoke the QUIT function in the DECwindows session manager from a MUMPS
application for a customer.  The need arises from preventing the end user
from exiting without MUMPS having a chance to clean-up the database.  I 
personally don't know why this is required since I do not know MUMPS, but the
customer says they need this badly.  We have already gone in and lobotomized
the session manager to prevent anyone from getting to VMS, since DECwindows
won't work in captured accounts.  Perhaps they method used in the session 
manager could be employed? 
	On a related topic, how can the session managers application menu
be hardcoded either from the .uil itself or from a DECW$SM_GENERAL.DAT
file.
	And finally, is there a way with logicals to get a group of
users to see a different set of .UID's for their applications than the
general system definitions.  Normally, DECW$SYSTEM_DEFAULTS is the logical
used and it points to 2 directories: [.decw$system_defaults] and 
[.decw$user_defaults].  Could it be I need to use seperate logicals for each?
						Many Thanks in advance,
						John Hooker

P.S.
	Vince if you're out there, the other mods I've made worked like a champ!
Many thanks.

P.P.S.
	I am cross-posting this to both the decwindow and decwindows_programming
notes files.

    I've been working some of the same issues, so here goes.
    
    1) See note 2350.x for the resource names in the SM, and how to grey
       them out.
    
    2) If you look at the search list for the decw$defaults you'll see that
       it finally gets to sys$specifc:[syslib]. What we did to get a
       login to use a specific .UID was to put the specific .UID in the
       sys$specific:[syslib] AND use the login.com to set the decw$defaults
       to go to this sys$specific. This assignment bypasses the normal
       search that starts at sys$common:[decw$defaults].
    
    Hope this helps,
    
    Bill Z.
    
    

    Thanks, however I still need the session start/stop info.  Are there
    resources to set which applications are available by the application
    pulldown?   Something like,
    
    	AppPullDownButton1:	DECW$calendar

    If not, is there some way to do it in the .UIL file without breaking
    the session manager?  (I have the .uil file available.)
    

    You should look into the Xlib routine XKillClient as a way to
    fake a quit session. It's kind of hacky, but any client can
    issue XKillClient requests if they have a resource id. The
    session manager used to use XKillClient in DECwindows V1 as
    part its Quit function.