| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2214.1 | Check your LOGIN.COM and SYLOGIN.COM files | HANNAH::MESSENGER | Bob Messenger | Tue Feb 06 1990 12:25 | 13 |
| Re: .0
Make sure their LOGIN.COM or SYLOGIN.COM files don't try to read from
sys$command, e.g. with the DCL INQUIRE command, if they are on a mailbox
device. When you start an application, such as DECterm or FileView, from the
session manager, the session manager creates a process that runs on a mailbox
device. The session manager writes the command to start the application to
this mailbox. If your LOGIN.COM reads from the mailbox, the command can't
be read by DCL.
I think SET TERM/INQ might have this same problem.
-- Bob
|
| 2214.2 | no DCL INQUIRE in LOGIN.COM or SYLOGIN.COM | EIGER::SCHMITT | Swiss Made | Wed Feb 07 1990 03:21 | 6 |
|
I advised the customers to remove all special things in LOGIN.COM or
SYLOGIN.COM and we tried it also with empty files but without success ...
Kurt
|
| 2214.3 | Suggestions to try | DECWIN::FISHER | Burns Fisher 381-1466, ZKO3-4/W23 | Wed Feb 07 1990 10:16 | 15 |
| Let's just make sure we understand completely:
The session manager runs. If you pull down Customize/Autostart, DECterm and
FileView are included in the right-most box. Correct? If not, they won't
start automatically.
Have you tried pulling down Applications and manually starting DECterm or
FileView? Does that work?
Try looking at sys$login:DECW$SM.LOG and see if there is useful info. Try
seeing if there are any processes sitting around named DECW$TE* or DECW$SM*.
Try looking in the accounting log to see what happened to processes that
the session manager may have started.
Burns
|
| 2214.4 | more information | EIGER::SCHMITT | Swiss Made | Wed Feb 07 1990 10:53 | 14 |
|
RE .3
- The session manager runs
- DECterm an FileView are included in the autostart
- I tried to start DECterm and FileView manually, but I got the same result
as described in .0 (Starting DECterm or Starting FileView message in the
Session Manager Window and nothing more ...)
- with SHOW SYSTEM you can't see a DECW$TE* or a *VUE process
- in the DECW$SM.LOG isn't useful information.
|
| 2214.5 | | SMAUG::MENDEL | I don't want to burn in Paradise! | Wed Feb 07 1990 12:42 | 23 |
| Here's something to try. I've debugged many problems in this way...
A. In LOGIN.COM, add near the top:
$ if f$mode() .eqs. "INTERACTIVE" then -
if f$loc("MBA",f$trn("TT")) .eq. 0 then -
DEFINE sys$output SYS$LOGIN:SMAPP_LOGIN.LOG
B. Create a command procedure SYS$LOGIN:SMAPP.COM
(1) defines sys$output to SYS$LOGIN:SMAPP_RUN.LOG
(2) does the same command as in the application definition
C. Since you can't change system definitions, create a new application
definition that is @SYS$LOGIN:SMAPP.COM instead of running the command
directly.
D. Start this new one instead of the system-defined one.
This might put some juicy error messages in SMAPP_LOGIN.LOG or
SMAPP_RUN.LOG.
Kevin
|
| 2214.6 | Here's one solution!! | TOPKAT::SYSTEM | | Thu Feb 22 1990 15:51 | 7 |
| I've just had the same problem described in .0. The solution was
to remove an INQUIRE command from sys$login:login.com and everything
fired up correctly. Thanks to -.1 et al.
Dave
ps using a GPX w/16MB & VMS V5.3
|