| 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 |
I'd like to use my VS3100 as server to a LARGE VAX Client under DECwindows. I did the following: 1) edit the file SYS$MANAGER:DECW$SERVER_ACCESS_ALLOWED.DAT on my VS3100 2) type the following commands on LARGE VAX where DECwindows is installed and started $ SET DIS/CREATE/NODE = node-name(VS3100) $ RUN SYS$SYSTEM:DECW$STARTLOGIN $ SET DISPLAY/NOPERM I didn't have error messages, and LOGIN BOX did't appear on VS3100. I have other things to do ? If you did before,please tell me how to do. AIKO
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3074.1 | Running DECW$LOGINOUT remotely is not supported | STAR::VATNE | Peter Vatne, VMS Development | Fri Jul 13 1990 13:01 | 19 |
What you are doing is not supported. Perhaps other people have gotten this to work, and can tell you what hacks they did. I'm somewhat confused as to why you want to do this, as you say you'd "like to use my VS3100 as a server to a LARGE VAX Client under DECwindows." If this is all you want to do, then I don't understand why you don't just log into the VS3100 normally, and then use Customize Security to allow the remote application to display on the work station. If you are trying to achieve some sort of automatic way to start the application on the large VAX, then I recommend you put the VS3100 in the same cluster as the large VAX, and then in your AutoStart menu submit a batch job to the large node that runs the application. The batch job just needs to do a SET DISPLAY command as the first line. If you are clever with DCL, you can even pass the workstation node name as a parameter to the batch job, so that the same command file can be used from any workstation in the cluster. Please let us know if this doesn't solve your problem. | |||||
| 3074.2 | But Peter is still right about it being unsupported! | HELTER::FISHER | Prune Juice: A Warrior's Drink! | Fri Jul 13 1990 13:48 | 8 |
Most likely the reason this is not working is because you are deleting
the workstation pseudo-device immediately after you run STARTLOGIN.
Startlogin passes the device name to loginout. As soon as it runs, it
no longer needs DECW$DISPLAY, but it still needs the device. You need
to create it permanently.
Burns
| |||||
| 3074.3 | PRAVDA::JACKSON | Niche, or be niched | Mon Jul 23 1990 11:21 | 11 | |
You'll also have to install DECW$STARTLOGIN with CMKRNL in order for things to work properly. If you don't it will work from SYSTEM accounts but not others. Take a look at how ELNDW (VAXeln notesfile on THRUST::VAXELN has a pointer) starts things up using a DECnet object. (you'll want the ELNDW_SERVER.COM file from I think the "A" saveset) -bill | |||||