[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

910.0. "Troubleshooting DECW$LOGIN.COM?" by CLOSUS::DCHAVEZ (Dale - KDT Colo Spgs) Thu Jun 08 1989 19:36

I've discovered that it's hard (if not impossible) to troubleshoot login
problems that are actually located in DECW$LOGIN.COM.  Since you can't SET
VERIFY and see the output of the login process, how does one troubleshoot
errors ?  I'm trying to use CHILD via my DECW$LOGIN, but it won't start
automatically at login time; it works fine interactively, so I assume there
is nothing wrong with CHILD.

Is there someway to watch what's happening as you're logging in to a
DECWINDOWS VAXstation?

Thanks,

Dale

T.R	Title	User	Personal Name	Date	Lines
910.1	Try looking at DECW$SM.LOG	PROOF::BRYSON		`Thu Jun 08 1989 19:42`	9
	SET VERIFY will work but you have to look at the session Manager log file created in SYS$LOGIN: by the name DECW$SM.LOG. Looking at this file may give you some indication what is going wrong without SET VERIFY. Note that this file will not be written to until the file is closed (or the session has been terminated). Log back in and look at DECW$SM.LOG;-1. David
910.2		PRNSYS::LOMICKAJ	Jeff Lomicka	`Fri Jun 09 1989 15:00`	24
	When you use CHILD from DECW$LOGIN.COM, CHILD needs to create the terminal emulator process for you. This requires a sufficiently recent version of CHILD. Get CHILD from topic 111, not from METOO. (I should update that one one of these days.) Synchronization problems in the V5.1 DECTerm can cause problems with CHILD's creating the emulator process, if your system is too busy at the first invocation of CHILD. These details are also in 111. I've found that most DECW$LOGIN CHILD problems fall into one of several simple categories: 1. Attempts to use /DECTERM, or any other terminal type qualifer (such as /LINE/INSERT), in combination with /IMAGE, will cause things to fail in funny ways. See 111.123 for a classic example. 2. People tend to leave off or have an extra DCL line continuation character "-". 3. Aforementioned synchronization problem. To fix this one, use the latest version of CHILD and set the CHILD_INIT_PAUSE to something larger than 10.
910.3		CLOSUS::DCHAVEZ	Dale - KDT Colo Spgs	`Mon Jun 12 1989 09:25`	7
	RE: Note 910.2 PRNSYS::LOMICKAJ "Jeff Lomicka" Thanks for the insight! I'll take a look at 111 and see what happens next! Dale
910.4	/PAGE bug?	CLOSUS::DCHAVEZ	Dale - KDT Colo Spgs	`Mon Jun 12 1989 10:15`	19
	Okay...isolated the problem. When I use CHILD without the /PAGE qualifier, I get a DECterm window and everything is great. If I use the /PAGE qualifier, CHILD attempts to create a window, (the ICON 'flashes' for a second), then goes away. This is the way my DEC$LOGIN.COM looks: $! $! DECW$LOGIN $! $ newterm :== child/image=sys$system:loginout.exe/detach/nopassword/pause $ newterm/shrink/page=35/proc="COOKIE"/TITLE="COOKIE"/ITITLE="COOKIE" Any suggestions? Thanks, Dale
910.5		PRNSYS::LOMICKAJ	Jeff Lomicka	`Mon Jun 12 1989 17:31`	11
	That should have worked. What's the creation date on CHILD.EXE? I think and older version had this problem. All the other qualifiers look good. Since you are using /PAUSE, you should have an error message in your DECW$SM.LOG file. Funny - DECW$LOGIN.COM versus interactive use, shouldn't make a difference here. Perhaps you have something CHILD related in your LOGIN.COM that makes it work interactive? LOGIN.COM isn't run from DECW$LOGIN.COM unless you explicitly ask for it.