T.R | Title | User | Personal Name | Date | Lines |
---|
422.1 | | VWSENG::KLEINSORGE | Toys 'R' Us | Thu Mar 16 1989 17:01 | 10 |
|
VMS is VMS right? So you submit the turnkey application as batch
jobs from SYSTARTUP after having started DECwindows **without**
the session manager (it's all in the command files, you don't
*have* to start the session manager). There might be some issue
about access control, but I think that was addressed in other notes
on the topic of the DECwindows trusted access lists.
|
422.2 | Digital has it now.... | IO::MCCARTNEY | James T. McCartney III - DTN 381-2244 ZK02-2/N24 | Thu Mar 16 1989 17:21 | 23 |
|
In the system startup file:
$ !
$ ! Start DECwindows but don't start the Applications
$ !
$ @DECW$STARTUP "SERVER,LIBS"
$ !
$ ! Start the dedicated application
$ !
$ Run/detached blah, blah, blah...
$ !
$ ! Start a Window Manager for the Luser
$ !
$ Run/detached SYS$SYSTEM:DECW$WINMMGR.EXE .....
And just wait for everything to get started.
Instant dedicated application - just add code...
James
|
422.3 | Not quite there yet | MONSTA::COLLINS | | Mon Mar 20 1989 09:58 | 19 |
| re. Turnkey DECwindows application.
Thanks for the responses. I still have a bit of a problem.
re .1, I can't even find where the session manager is started! I found
decw$startsm.com but can't find where it is called from or where
decw$session.exe might otherwise be invoked from.
re .2, I tried that but found a problem with decw$startup.com. Where it
decides to spawn itself it does not pass on the parameters it was originally
called with and so the p1 parameter "SERVER,LIBS" ended up as null when the
code got as far as deciding whether to invoke decw$startapps.com. I
fixed this and all I ended up with on the screen was the default tile
pattern and a pointer. No windows no nothing....halt button only way out.
I'm sure I'm missing something somewhere, is what I'm trying to do explained
anywhere?
|
422.4 | The reason you didn't get anything up... | IO::MCCARTNEY | James T. McCartney III - DTN 381-2244 ZK02-2/N24 | Tue Mar 21 1989 22:17 | 13 |
|
Once DECW$STARTUP spawns itself the mainline of SYSTARTUP_V5 continues without
waiting for DECW$STARTUP to complete. This means that the command to start your
application will be executed well before DECW$STARTUP gets the server started.
If you check your startup logs, then you will most likely find that your
application died with a "can't open display" error...
I suggest you stick in a "WAIT 00:02:00" (or however long it takes) to wait
until DECW$STARTUP gets finished. Or even better, make decw$startup not spawn
by defining the logical DECW$IGNORE_SUBPROCESS.
James
|
422.5 | Magic | MONSTA::COLLINS | | Thu Mar 23 1989 04:00 | 4 |
| Thanks again. It works a treat and I now have a very happy customer.
Mike
|