[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

2947.0. "Error information from session manager" by COPPER::D_BERRY () Mon Jun 18 1990 13:18

I would like to know why the session manager doesn't pass back Error status to
the session manager window??!?!?!?!?!?!?!?!!?!?!?!?!?!?!?!?!!!!!!!!!!!!!!?????




It is very frustrating to try to start an application and have it fail with
no indication of what happened.  I usually have to go start it from a file
view.


Could someone please tell me where to go get this information.  If it is
not available, then I think the session manager should be modified
to show status of failed applications.  At least with fileviews you can
see what is happening to currently running or failed applications.

T.R Title User Personal
Name Date Lines

2947.1 SMAUG::MENDEL In some strange power's employ Tue Jun 19 1990 13:44 6

T.R	Title	User	Personal Name	Date	Lines
2947.1		SMAUG::MENDEL	In some strange power's employ	`Tue Jun 19 1990 13:44`	6
	I know there are several notes in here about debugging these problems, because I wrote a few. Look around. Add a section to your login.com such that, if the process executing it is interactive and the terminal device is a mailbox, sys$output is defined to a log file. This will put the error messages there.

        I know there are several notes in here about debugging these problems,
	because I wrote a few. Look around.

	Add a section to your login.com such that, if the process executing it
	is interactive and the terminal device is a mailbox, sys$output is
	defined to a log file. This will put the error messages there.