Conference bulova::decw_jan-89_to_nov-90

    Just two things:
    
    Why must we have a SYS$TOOLS: directory. Can't the .UID be put is
    DECW$USER_DEFAULTS, like the style guide says? ANd can't the
    server and exe be in sys$system: ?
    
    2)
    It would also be nice to have radio buttons to select a screen on the
    destination server (pass it a screen=0).
    
    Other than that, this is what has been needed for a long time.
    
    Jeff
    

	First: Great tool!! Thank you for the hard work...

	Second: Jeff and I discussed .1 before he entered it. I agree
	with him 100%. PLEASE get rid of SYS$TOOLS. Also, your
	KITINSTAL.COM need to be re-written. If I have a moment, I'll
	re-write the parts that need it and send it back.. You make
	assumptions (like sys$tools) and should really add some extra
	logic in there with regard re-installing DCLTABLES.EXE and the
	CLD file.. Trust me, it would seriously break my clusters up
	here in VMS. (and we develop VMS DECwindows too!)

	PLEASE, PLEASE re-consider the SYS$TOOLS stuff at a minimum.

					Thanks,
							mike

The server does not have to be put in sys$tools it can be put anywhere.  
SYS$TOOLS is actually just a logical name used to tell DW_NET where the UID is 
located.  I suppose I could change the name to DW_NET_UID_LOCATION or something.
If you could make the changes to KITINSTAL I would be glad to release a new kit.
I really do not know VMSINSTALL all that well.  

	
The reason we use sys$tools is that is where we load tools on our clusters.

UID files should either be in DECW$SYSTEM_DEFAULTS or DECW$USER_DEFAULTS.

The X_SERVER.COM,DW_NET.EXE,DW_NET_SERVER.EXE could go in SYS$SYSTEM:

If you did these things, then you wouldn't need the SYS$TOOlS: logical.

Jeff

    I can't seem to copy the PMAX version.  I get "Transfer Error, DAP file
    transfer Checksum error." when using dcp -i on a PMAX and I get
    "network operation not supported..." when I use spool/transfer=block or
    when I use exchange/network on the VMS side.  Looks like a great tool
    on the VMS side though...thanks for the effort!
    
    mike

dw_net.uid now resides on DECW$SYSTEM_DEFAULTS
dw_net.exe now resides in sys$system
dw_net_server.exe now resides in sys$system
dw_net_server.com now resides in sys$system

on PMAX
dw_net.uid resides on /usr/lib/X11/uid/
dw_net resides on /usr/bin
dw_net_server resides on /usr/bin
dw_net_error_server resides on /usr/bin
error_box resides on /usr/bin

Here's my vote for an Ultrix VAX version . If need be, I can build a kit here if
I have access to the sources.

This appears to be a very nice tool -- but it requires that the DECW programming 
option be installed on the workstation. This is because it tries to compile the 
UIL file. Can this be changed? None of our workstations have this option 
because of limited disk space...

Thanks

PS Obviously there are  workarounds....but they are a hassle

	I think the following kitinstal.com should clear up the 
	questions I had.  Please double-check my code, anyone that's
	interested..

	Thanks,

							mike
$ on control_y then exit vmi$_failure
$ on warning   then exit vmi$_failure
$ !
$ ! kit install command procedure to install dw_net
$ !
$ dw_net_vers = "V1.0"
$ internal_kit = "TRUE"
$ !
$ if p1 .eqs. "VMI$_INSTALL" then goto BEGIN_INSTALLATION
$ if p1 .eqs. "VMI$_IVP" then goto BEGIN_IVP
$ exit VMI$_UNSUPPORTED
$ !
$BEGIN_INSTALLATION:
$ !
$ write sys$output ""
$ write sys$output "  Installing DW_NET version ''dw_net_vers'..."
$ write sys$output ""
$ !
$ vmi$callback SET PURGE ask
$ vmi$callback SET IVP YES
$ !
$ type sys$input
$deck

  New features, enhancements, and bug fixes:

	1	DW_NET allows you to modify existing entries without adding 
		new ones.
        2	DW_NET allows resize.
	3	DW_NET stores PASSWORDS for each node so that you will not 
		have to reenter them if you switch nodes
	4 	DW_NET allows you to switch passing passwords on or off.
	5	DW_NET no longer resizes the modify window to match the size 
		of the command.

   Read SYS$HELP:DW_NET.RELEASE_NOTES for details.

$eod
$! wait 0:0:8
$ write sys$output ""
$ write sys$output "  Now linking DW_NET..."
$ link/nodebug/trace/exe=vmi$kwd:dw_net.exe vmi$kwd:dw_net_kit.opt/opt          
$ write sys$output "  Now linking DW_NET_SERVER..."
$ link/nodebug/trace/exe=vmi$kwd:dw_net_server.exe vmi$kwd:dw_net_server_kit.opt/opt
$ write sys$output "  Now Building DW_NET.UID..."
$ define uil$include vmi$kwd,decw$include
$ uil vmi$kwd:dw_net.uil/output=vmi$kwd:dw_net.uid
$ set file/prot=w:e vmi$kwd:dw_net.exe
$ set file/prot=w:e vmi$kwd:dw_net_server.exe
$ set file/prot=w:r vmi$kwd:dw_net.uid
$ set file/prot=w:r vmi$kwd:dwnet_help.hlp
$ vmi$callback PROVIDE_FILE  error dw_net.exe          vmi$root:[sysexe]
$ vmi$callback PROVIDE_FILE  error dw_net_server.exe   vmi$root:[sysexe]
$ vmi$callback PROVIDE_FILE  error dw_net.uid          vmi$root:[syslib]
$ vmi$callback PROVIDE_FILE  error dwnet_help.hlp      vmi$root:[syshlp]
$ vmi$callback PROVIDE_FILE  error dw_net_server.com   vmi$root:[sysexe]
$ vmi$callback PROVIDE_FILE  error dw_net.release_notes vmi$root:[syshlp]
$ vmi$callback PROVIDE_DCL_COMMAND dw_net.cld
$!vmi$callback PROVIDE_DCL_HELP    dw_net.hlp
$!
$ type sys$input
$deck


  *** REQUIRED ACTIONS ***

      o Users currently running dw_net must exit and restart it 

      o If you are a server node you must install it in NCP execute the
	following command
	    $ MCR NCP
	    ncp> def obj x_server number 0 file sys$system:dw_net_server.exe
	    ncp> set obj x_server number 0 file sys$system:dw_net_server.exe
	    ncp> EXIT

      o If you are installing on a cluster you will have to INSTALL/REPLACE
	the latest version of the DCLTABLES on all the other nodes.

        $ install
	install>replace sys$share:dcltables.exe/open/header/shared

$eod
$ exit VMI$_SUCCESS
$!
$BEGIN_IVP:
$!
$! Notify DW_NET development of this installation.
$! Gather and send statistics about nodes installing DW_NET.
$!
$ if .not. internal_kit then goto DONE
$!
$ write sys$output ""
$ write sys$output "  Notifying DW_NET development of this installation."
$ write sys$output "  Please ignore any error messages from MAIL or ANALYZE."
$ write sys$output ""
$ installer = f$edit(f$getjpi("","USERNAME"),"COLLAPSE")
$ hw_type = f$edit(f$getsyi("NODE_HWTYPE"),"COLLAPSE")
$ sw_type = f$edit(f$getsyi("NODE_SWTYPE"),"COLLAPSE")
$ sw_ver = f$edit(f$getsyi("VERSION"),"COLLAPSE")
$ clust = f$getsyi("CLUSTER_NODES")
$ if clust .eq. 0 then clust_str = "Standalone node"
$ if clust .ne. 0 then clust_str = "''clust' node cluster"
$ mail_subj = "Installed DW_NET ''dw_net_vers', ''hw_type' running ''sw_type' ''sw_ver', ''clust_str'."
$ create vmi$kwd:mail_msg.log
installed
$ if f$search("sys$library:nm_mailshr.exe") .eqs. "" then goto MAIL
$ if f$trnlnm("nm$work") .eqs. "" then goto MAIL
$ goto NMAIL
$!
$MAIL:
$ mail/noself vmi$kwd:mail_msg.log marx::walsh/su="''mail_subj'"
$ goto DONE
$!
$NMAIL:
$ mail/noself vmi$kwd:mail_msg.log nm%marx::walsh/su="''mail_subj'"
$ goto DONE
$!
$DONE:
$ exit vmi$_success

With this sort of kit you should install it by default in,

/usr/local/bin for executables.
/usr/local/lib/X11/uid for uid files.

If you install this into /usr/bin and /usr/lib then these files get blown 
away when you upgrade. (No rolling upgrades in ULTRIX, yet). However if all
your local toys, utilities, games etc. are stored under /usr/local then you can
back this up seperately and restore it after the upgrade.

Joe.

I had a come file to do the same function as dw_net but dw_net is about 15-25 
seconds faster. So I migrated. 
One but was I start up applications (such as decwrite, cms) in directories other
than my default. Also like to start some things with initial states other
than default.

So with a slight mod to dw_net_server.com multiple commands can be passesd 
to the remote process. I used a '<' to seperate commands 

	IE: dw_net remnod set def [.doc] < mcr decwrite 

This brings up decwrite in a subdir [.doc]. Keep in mind that only 8 
params are allowed. but a command could be enclosed in "" to make it only 1
parm. The above examlpe is 7 params and 
	
	IE: dw_net remnod "set def [.doc]" "< mcr decwrite" 

is only 3 params.

*******************************************************************************
$!      This command file accepts a node name and a DECwindows/X command string
$! 	and attempts to execute it with its output pointed towards the node.
$!
$ command_line0 = ""
$ multi_cmds = "MCMD/</./"                ! set up commands 
$ multi_cnt = 0
$ x = 1
$!
$!	Extract destination node name off of the command line
$!
$ nodename	= F$EDIT(P1, "COLLAPSE, UPCASE, UNCOMMENT")
$!
$!	set the decwindows display device to the node
$!
$ set display/node='nodename/create
$!
$!	Take all of the rest of the parameters and compress them into command
$!
$ PARM_CHECK:
$   x=x+1
$   if x .GT. 8 then goto done 
$   if p'x' .EQS. "" then goto done
$   IF F$LOCATE(f$element(0," ",p'x')+"/",multi_cmds) .NE. F$LENGTH(multi_cmds) 
$       THEN multi_cnt = multi_cnt+1
$       command_line'multi_cnt' := 
$       p'x' = p'x' - f$element(0," ",p'x')
$       if F$LENGTH(p'x') .EQ. 0 then goto parm_check 
$   ENDIF
$   command_line'multi_cnt' = command_line'multi_cnt' + p'x' + " "
$   goto parm_check
$ DONE:
$!
$! 	execute the DECwindows command
$!
$ x=0
$ DO_COMMAND:
$   ''command_line'x'
$   x=x+1
$   if x .LE. multi_cnt then goto DO_COMMAND
$exit

	Ive installed this on a cluster with multiple workstations
	all running vms 5.3.

	when i try an start a process via dcl i get the following:

	'invalid device name'

	if i try from the dw_net window, nothing at all ?

	any ideas ?

	jim

go to remote node and type

$set display/node=yournode/create

If this fails then check to make sure the remote node knows about your node. 
What verion of vms is the Server running?

If this works type

$run sys$system:decw$clock

The clock should come up on your screen.

If both these work then there must be some other problem.

This stuff is really neat. It would be nice to have a screen number
radio box or smoething, then pass that to the X_SERVER as a parameter
and include it in the SET/DISPLAY.

This way multi-head WS. work.

Jeff

DCL eats <">s.


if you want to use dw_net from dcl command line with your username and password
type

$dw_net "node""username password""" command

Multiple heads will be taken care of in the next release.

Anyone know how the X-terminals work.  Do these have node names?

Dan

    I still can't access the Ultrix files from jisuzu.  Has anybody
    copied the files successfully.  Pointers to another node?
    
    Thanks...mike

I'm getting -RMS-E-PRV, insufficient privilege or file protection violation
on MARX::USER2:[WALSH.PUBLIC]DWNET010_MAX.TARZ

and

dcp -iv 56.81::/public/dwnet010_max.tar.Z .
56.81::/public/dwnet010_max.tar.Z ==> /usr/users1/miller/./dwnet010_max.tar.Z
dcp: close error "/public/dwnet010_max.tar.Z", I/O error
    Transfer Error, DAP file transfer Checksum error.

on the PMAX pointer.

Thanks,

          == ken miller ==

P.S.  Did you need any volunteers for build time on ULTRIX-VAX?

I have inspect running and had to disable proxy to my account and due to 
that when I run dw_net to create a terminal I gae some message comming back
that comes in as user ILLEGAL and in turn sets on security. after the third time 
the evasion goes into effect and I am locked out for 24 hours. 

How can I catch the message and determine whats wrong?

Paul H.

I tried 
	$dw_net "node""username password""" command
on the cmd line and I get 
	remote node is unknown

Paul H.

	Shouldn't it be 

	$dw_net node"user pass":: command

	???

							mike

I have finally gotten a VAX Ultrix kit.  It is in 
MARX::{walsh.public].

Also there is a problem in the CLD that is trapping "".  The new CLD 
seems to fix this.

!	CLD for DW_NET utilitiy

MODULE dw_netcld

define verb dw_net
    image sys$system:dw_net
    parameter p1,value(type=$quoted_string)
    parameter p2
    parameter p3 
    parameter p4 
    parameter p5 
    parameter p6 
    parameter p7 
    parameter p8 

dir MARX::user2:[walsh.public]dwnet010_vax.tarz

Directory MARX::USER2:[WALSH.PUBLIC]

DWNET010_VAX.TARZ;1
                   no privilege for attempted operation

Total of 1 file, 0 blocks.
<golly::miller> copy MARX::user2:[walsh.public]dwnet010_vax.tarz [.dw_net]
%COPY-E-OPENIN, error opening MARX::USER2:[WALSH.PUBLIC]DWNET010_VAX.TARZ;1 as i
nput
-RMS-E-PRV, insufficient privilege or file protection violation


Regards,

          == ken miller ==

I just don't understnd. I installed DW_NET and set up the X_SERVER object
as in the instructions. However whenever I try to run DW_NET I get "network
object is unknown at remote node.". Now, either DW_NET.EXE is sending to an
object named X_SERVER or it isn't. If it isn't then it won't work for anybody,
but that is obviously not the case.

Here is my DECnet object on the remote node:

	Object Volatile Characteristics as of 23-FEB-1990 12:13:02
 
	Object = X_SERVER
 
	Number                   = 0
	File id                  = SYS$SYSTEM:DW_NET_SERVER.EXE

Any suggestions? 

    If you don't have the TASK object defined on the local node you'll get
    this message. If you define it (TASK) like this:
    
    NCP> DEFINE OBJ TASK NUMBER 0 USER TASK PASS *ILLEGAL* PROXY BOTH
    
    it will be secure, and it will also allow inbound TASK connects to
    succeed if the remote node::user has proxy access to your system.
    
    /harley

    I thought the whole point of creating a seperate X_SERVER object was
    to avoid having to mess around with the TASK object?  At the risk of
    getting jumped on, why is any association with the TASK object
    necessary at all?

               Dave

    DW_NET.EXE evidently tries to connect to the X_SERVER object like this:
    
    node::"task=x_server"
    
    You need TASK defined on your node (not the X_SERVER node) or the
    connect will fail because DECnet won't be able to translate "task=" to
    an object number (in this case, "0=").
    
    /harley

    Oh, I see.  I thought that DW_NET would define itself as a network
    object on both sides and do task to task stuff.

                 Dave

If DW_NET used the syntax "0=X_SERVER", it would not require the TASK
object to be declared at all.

					Steve

    Proxy access from Ultrix to VMS may be somewhat confusing. We had to
    discover the following by trial and error and DECNET-ULTRIX notes file,
    so to save you some trouble, here's some help:
    
    Suppose I have two accounts: VMS::HALBERT and ULTRIX::HALBERT, with a
    proxy for ULTRIX::HALBERT as HALBERT on VMS:: .
    
    If Ultrix dw_net has the setuid bit set and runs as root, then the
    proxy will work. If Ultrix dw_net is not setuid, then dw_net will pass
    a proxy name that is the ASCII decimal representation of halbert's
    uid, e.g. something like ULTRIX::247.
    
    You have two choices: 1) set up a proxy for ULTRIX::247 as HALBERT on
    VMS::, or 2) setuid root dw_net.
    
    --Dan

    Proxy access from Ultrix to VMS may be somewhat confusing. We had to
    discover the following by trial and error and DECNET-ULTRIX notes file,
    so to save you some trouble, here's some help:
    
    Suppose I have two accounts: VMS::HALBERT and ULTRIX::halbert, with a
    proxy for ULTRIX::halbert as HALBERT on VMS:: .
    
    If Ultrix dw_net has the setuid bit set and runs as root, then the
    proxy will work. If Ultrix dw_net is not setuid, then dw_net will pass
    a proxy name that is the ASCII decimal representation of halbert's
    uid, e.g. something like ULTRIX::247.
    
    You have two choices: 1) set up a proxy for ULTRIX::247 as HALBERT on
    VMS::, or 2) setuid root dw_net.
    
    --Dan

RE: 2216.30:

> If DW_NET used the syntax "0=X_SERVER", it would not require the TASK
> object to be declared at all.

How about considering this as an enhancement for the next version?

I've just installed DW_NET on my standalone workstation.  It seems to work
pretty well, though our site support group doesn't seem to have the server
running properly on our cluster yet.

Anyway, as one who'se responsible for my own system manglement, I've run into
a question that I can't answer.  After running VMSINSTAL, I'm used to other
kits telling me that I have to "add the following command procedure to
SYSTARTUP_V5.COM."  This causes the application to be installed whenever the
system reboots.

It surprised me that I didn't see anything for that with DW_NET.  Am I missing
something?  If DW_NET needs to be reinstalled on system reboot, what's the
command?

Thanks,

Stew

    dw_net is a single program that you run.  It is not all ways running so
    there is nothing to put in your sys$startup command files.  
    
    The server is added to the known objects list in DECnet permanently so
    nothing has to be started up.
    
    I have a new version of dw_net but it has not been totaly tested out
    and the documentation is not up to snuff yet.  I need some one to test
    it out.  I do not have access to machines with multiple servers or
    screens and this tool will support them.  Please send me mail if you
    can test the new functionality.  
    
    Dan
       

I have had some sales people ask me if this tool is going through assets so they
could use give it to some customers.  

What is involved in this?  

Which assets group should I submit dw_net to?

Dan

  Not sure of all the details but there is a conference that I believe can
definitely point you in the right direction.

	BUFFER::ASSETS_PROGRAM  (Press KP7 to select conference)

					-=> Jim <=-

Do the Server portion instructions assume the availability of the DECWindows
Development kit?  Or can this be installed on a system that only has the
DECWindows runtime installed?

We're trying to run it on a system that only has the DECW runtime installed
and we're wondering if that could be causing our problem.

Thanks,

Stew

	You need the programming support in order to get this to install.
	It needs the support to compile the UID file with UIL.

							mike
						(Who ran into this today)

I have the kit DWNET012.A dated 9-MAR-1990. I have installed it on KAIRYS, my
workstation, and on WADE, a 3300 on which I want to run clients. I have set and
defined WAU_SERVER in my DECnet database on both nodes. In DW_NET, I have 
customized the node WADE and defined three commands. My resulting DWNET.DAT is: 

	dwnet.x:	11
	dwnet.y:	113
	dwnet.WADE.username:	kairys
	dwnet.WADE.server:	0
	dwnet.WADE.screen:	0
	dwnet.WADE.Design:	@sys$login:decw_application design
	dwnet.WADE.DECterm:	@sys$login:decw_application term
	dwnet.WADE.DECwrite:	@sys$login:decw_application decwrite
	dwnet.WADE.toggle_password:	0
	dwnet.WADE.toggle_username:	1
	dwnet.WADE:	DECwrite,Design,DECterm

The aforementioned command file decw_application.com is what I use for applica-
tion startup everywhere. (I either call it with a parameter, as here, or use it
as sys$input to a run/detach of loginout, in which case I get the parameter via
the process name). But I digress...

I bring up DW_NET, select WADE, select one of the commands, hit Connect, and go 
over to WADE and examine the NETSERVER.LOG file that ends up in my login
directory. I find:

********************************************************************************

       	--------------------------------------------------------

       	Connect request received at 23-MAR-1990 11:50:45.20
       	    from remote process KAIRYS::"0=KAIRYS"
       	    for object "SYS$SYSTEM:WAU_SERVER.EXE"

       	--------------------------------------------------------

read=0,0,@sys$login:decw_application term
server=0
screen=0
command=@sys$login:decw_application term
WADE::KAIRYS will execute @sys$login:decw_application term on server 0 screen 0
@sys$login:decw_application term failed
%RMS-E-FNF, file not found
network object is unknown at remote node
  KAIRYS       job terminated at 23-MAR-1990 11:51:50.04

********************************************************************************

NCP on WADE says:

	NCP>show object wau_server char

	Object Volatile Characteristics as of 23-MAR-1990 12:13:38

	Object = WAU_SERVER

	Number                   = 0
	File id                  = SYS$SYSTEM:WAU_SERVER.EXE
  
..and likewise on KAIRYS. I do not have a TASK object defined on either node.


So my first problem is, why doesn't it work for me?

My second problem is: how can I use the command line interface and still
get DW_NET to use account KAIRYS on the remote node? When I try it I get

	$ dw_net wade decwrite
	WADE::DECNET will execute DECWRITE on server 0 screen 0

I don't want DECNET to execute anything for me! I want my own account, with my
own defaults files, etc. But I really want to use the command line interface,
so that I can put DW_NET commands in the session manager application startup
menu and in my Motif root menu.

Thirdly, a few defaults file nits:

  - DWNET.DAT is read from and written to SYS$LOGIN, not DECW$USER_DEFAULTS.

  - The .x and .y resources that end up in the file are not the accurate
    posiition of the window. However if I edit those lines before starting
    DW_NET then the window does end up where I specified.

  - DW_NET does not respond to initialState.

I'm getting the same problem as Michael when trying to connect to a host
with CREATE/TERMINAL.  It works when I connect to one node, but not to the
other.  The main difference here is that the node I can't connect to doesn't
have the DECwindows development kit installed, just the runtime.

I thought that need (for the development kit) was removed with the latest
DW_NET kit.  Wrong?

Thanks,

Stew

             Hi,


i installed DWNET012_MAX.TARZ (dated 20-mar-90) on a Decstation 3100 booting 
on a VAx ultrix system, copy Dw_net,wau_server,dw_net_error_server in /usr/bin and copy UID
in X11.... accordingly to DW_NET_010_INSTALL (didn't find DW_NET_020_INSTALL )
define  X_SERVER under NCP on Decstation .

i then run  dw_net in order to start an application on a VMS system,and ..
got the following error 'Connect failed, no response from object'

i have a look in Netserver.log on VMS side and modify WAU_SERVER.Com to see
if P1 ,P2,P3 where defined ,it seems that those parameters are note defined.

The only things i put on VMS side is a proxy for my Dectation and the file 
WAU_SERVER.COM in my default directory .


Any idea why those parameters are defined ?,should i add anything else on the
VMS or Ultrix side.


Thanks


Jean


$!
$!
$ IF F$MODE() .NES. "INTERACTIVE" THEN EXIT
$ !  Copyright (c) 1987 Digital Equipment Corporation.  All rights reserved.
$ IF "" .NES. "" THEN NETSERVER$COMMAND
$ IF ""  .EQS. "" THEN NETSERVER$VERIFY = 0
$ V = F$VERIFY(NETSERVER$VERIFY)

        --------------------------------------------------------

        Connect request received at 28-MAR-1990 14:37:03.75
            from remote process CHEEKY::"0=NAVARRO"
            for object "WAU_SERVER"

        --------------------------------------------------------

$!      This command file accepts a node name and a DECwindows/X command string
$! 	and attempts to execute it with its output pointed towards the node.
$!
$!	Extract destination node name off of the command line
$!
$ show symbol p1
  P1 = ""
$ show symbol p2
  P2 = ""
$ show symbol p3
  P3 = ""
$ nodename	= F$EDIT(P1, "COLLAPSE, UPCASE, UNCOMMENT")
$ server	= F$EDIT(P2, "COLLAPSE, UPCASE, UNCOMMENT")
$ screen	= F$EDIT(P3, "COLLAPSE, UPCASE, UNCOMMENT")
$!
$!	Take all of the rest of the parameters and compress them into a command
$!
$ command_line	= F$EDIT(P4 + " " + P5 + " " + P6 + " " + P7 + " " + P8, -
			 "COMPRESS, TRIM, UNCOMMENT")
$!
$!	set the decwindows display device to the node
$!
$ set display/node=/screen=/server=/create
%DCL-W-VALREQ, missing qualifier or keyword value - supply all required values
$!
$! 	execute the DECwindows command
$!
$ 
$exit
$ IF	 = "IF"
$ THEN	 = "THEN"
$ DELETE = "DELETE"
$ IF F$TYPE(SET)      .NES. "" THEN DELETE/SYMBOL/GLOBAL SET
$ IF F$TYPE(RUN)      .NES. "" THEN DELETE/SYMBOL/GLOBAL RUN
$ IF F$TYPE(GOTO)     .NES. "" THEN DELETE/SYMBOL/GLOBAL GOTO
$ IF F$TYPE(DEFINE)   .NES. "" THEN DELETE/SYMBOL/GLOBAL DEFINE
$ IF F$TYPE(WRITE)    .NES. "" THEN DELETE/SYMBOL/GLOBAL WRITE
$ IF F$TYPE(DEASSIGN) .NES. "" THEN DELETE/SYMBOL/GLOBAL DEASSIGN
$ SET DEFAULT ADG$DISK:[NAVARRO]
$ IF STARTUP_FLAG .EQS. "Y" THEN GOTO STARTUP_NETSERVER
$STARTUP_NETSERVER:
$ STARTUP_FLAG = "N"
$ IF F$SEARCH("SYS$LOGIN:NETSERVER.LOG;-10") .NES. "" THEN -
	PURGE /KEEP:3 SYS$LOGIN:NETSERVER.LOG
    

    
    RE .40
    
    	Is n't the problem of 'file not found' caused by the fact that
    	sys$login is not defined untill you are actually logged in.
    	Its the same with create/terminal=decterm/detach/input=xxxx
    
    	if xxxx has sys$login in it , it won't work, it needs the whole
    file specification.
    
    
    I have installed dw_net on our system, and have some observations:
    
    	1) at first the only thing I got was:
    
    		invalid device name
    
    	   It took me a long time to find out that it was just caused
    	 by the colons at the node like:
    
    	$DW_NET ATLAST:: "notes/decw"
    
    	without the :: it started to work, maybe a next release wouldn't
    mind the '::'?
    
    
       2) I'm probably not experienced enough with DECwindows, what
    	  is the SERVER 0 and SCREEN 0 (or any other number ) giving me.	
    
    	
    
    

    
    
        Hi,
    
    
    after trying to install Dwnet012_MAX.TARZ without success i copied
    Dwnet010_max.tarz on my ultrix workstation and tried to use
    
    #uncompress dwnet010_max.tar.Z 
    
    i got the following message
    
    dwnet010_max.tar.Z :not in compressed format
    
    
    i then try to use tar directly but i got an error message .
    
    Is someone has an idea of what is wrong in this case ,is the kit is 
    really in compressed format or not ?
    
    Regards
    
    Jean
    
    
    

    This is goofy but, I had the same problem on MAX. I received this
    error when using -i switch on dcp. I then excluded -i and the 
    uncompress and install then worked fine. This isn't the way it is
    supposed to work, but it does. 
    
    I have dw_net installed on RISC and VAX and have been exchanging
    applications back and forth. However, on some X-applications, namely
    third party, DW_NET doesn't funciton properly.
    
    For example  VAX needs to display RISC Xversion of SoftPC.
    
    RISC dw_net get the request, then returns to the VAX netserver.log
    
    connect request for RSF_W_ERROR
    no come file found and all that other stuff.
    The command line is a RISC alias softpc=SoftPC, I have tried SoftPC
    as well but I still get the RSF_W_ERROR message.
    
    I get the same error when trying to run Applicon BRAVO with DW_NET.
    
    Another interesting tidbit, I also have SoftPC for VAX, the RISC
    box, using DW_NET can get the VAX version to display without any
    problems.
    
    It seems that DW_NET, like PCX$SERVER, has problems with certain
    execution command lines.
    
    Anyway, 
    I am still trying to solve this problem.
    
    Regards,
    
    Tony

    If you do DIR/FULL MARX::USER2:[WALSH.PUBLIC]*.TARZ, you'll see a
    difference:
    
    DWNET010_MAX.TARZ;1           File ID:  None
    ...
->  Record format:      Variable length
->  Record attributes:  Carriage return carriage control
    
    DWNET010_VAX.TARZ;1           File ID:  None
    ...
    Record format:      Fixed length 512 byte records
    Record attributes:  None
    
    DWNET012_MAX.TARZ;1           File ID:  None
    ...
    Record format:      Fixed length 512 byte records
    Record attributes:  None
    
    Depending on which one you try to copy, you will or will not have
    success with dcp -i. The format of the first file above is really pilot
    error, I believe.
    
    --Dan

    
    
    
    Re -1,-2 
    
    fine ,that was my problem , i used dcp without -i option and reached to
    uncompress the kit ,and install its , for sure the error message is
    quite misleading ,especially for an ultrix new hire .
    
    
    
    Once more thanks
    
    Jean 

The following are responses to several preceding notes.  I was away on vacation
so sorry for the late responce.

Seems I copied the some of the dwnet010_*.tarz files without dcp -i and this
is causing confusion.  Sorry.

There is an undocumented "error server" in the ultrix kits called
dw_net_error_server.  When you look in the log file it is trying to execute
this file.  You can run dw_net_error_server as a deamon on ultrix machines and
if for some reason dw_net fails to start an X application the error message
will be reported back to the local machine.  I have not gotten this to work on
VMS yet.

As far as DW_NET not handling x applications from VAX out, I don't know.  Try 
executing server command file with the appropriate parameters and see if this
works.  Give me a call if you have not figured this out,  I'm very interested
in this problem.  

Sorry about not taking care of :: I will get that in the next release.

Screen is a way for Xwindows to broadcast to multiheaded workstations.  If you
had two screens on your workstation, you can tell x which screen to broadcast
to.  

Server is the object or daemon that X talks to on the server node.  You could
set up multiple X servers on a single node.  You could build a special server
that redirects X to many different workstations or transfers protocol between
decnet and txp/ip.

Hello Jean,

In DW_NET_012 the server object has changed its name to WAU_SERVER. Execute the
following in ncp.

ncp> define obj WAU_SERVER number 0 file sys$system:wau_server.exe
ncp> set obj WAU_SERVER number 0 file sys$system:wau_server.exe

I have not updated dw_net documentation yet to reflect this change (were
working to hard on RSF :^)

re 41:

DW_NET is two sections a client section and a server section.  The client
section is the DECwindows application that runs on your local workstation in
dw_net 010 the installation procedure link the EXEs and built the uid file. 
This required that you have the DECwindows programming environment to install
it.  In dw_net 012 I have shipped the EXE's and the UID so there should be no
need for a DECwindows programming environment.  

The server section is nothing more the a decnet object that starts up when a
request comes in, figures out who its talking to, accepts a command, screen and
server and then spawns a command file passing the node, command, screen and
server.  This command file sets up the local node to broadcast X applications
to the remote node::server.screen and then runs the command.  There is no
DECwindows stuff on the server side.  If your experiencing a problem it is not
related to the DECwindows programming environment.

re 40:
DW_NET is telling you that when it tries to execute the command file your
executing or something inside of that is getting a RMS error of file not found.
I am pretty sure that sys$login i defined so either it is not finding your file 
or something insid of that file. why are you using this decw_appication com
file instead of entering the command RUN SYS$SYSTEM:DECWRITE.  Send me a copy
of you com file offline and I will see if I can get it to work.

The following should work in dwnet 010
$dw_net "node""user password""" command 
The following should work in dwnet 012  
$dw_net/screen=10/server=2 node"user password" command 
I would advise setting up DEFAULT proxy access though.

DW_NET 012 reads dwnet.dat from decw$user_defaults.  I have not noticed any
problems with the positioning of the DW_NET (I am however using the Ultrix
version)

I will look into getting dw_net to respond to initial state.  (good idea)


Finally DW_NET 012 is not officially released yet, because of documentation and
waiting for ULTRIX 4.0.  I have put new save sets in marx::user2:[walsh.public]
if anyone wants them.  Has anyone tries the multiple screens and server stuff?
Does it work??


    

Hi, I'm still having trouble firing remote DECW commands.  Even though you
normally work on an ULTRIX system, I thought maybe seeing the NETSERVER.LOG
file might help you HELP ME figure out what's wrong.

From my workstation, I'm typing: DW_NET HBO "NOTES/DECWINDOWS"
- a perfectly logical command.  Node STRYKR is my workstation, which has proxy
access to and from HBO.

Thanks,

Stew

p.s. NETSERVER.LOG file follows
-------------------------------------------------------------------------
$!
$!	ico_sys:[sysmgr]SYLOGIN.com	for the ICO sub-cluster
$!
$!	Created:	????
$!
$!	Edited:	10-Nov-1988	PLB	Added L3ISS* symbols for Rick Sherman's LN03R
$!					eliminated ICVAXB printer symbols, moved printer
$!					symbols up into the "all-jobs" area.
$!		18-Feb-1989	PLB	Added VCSLSU & DMTERM symbols
$!		22-Jun-1989	RJJ	Added jpi symbol for convience
$!		28-Aug-1989	RJJ	Rewrite of LPS40 symbols
$!		30-NOV-1989	deb	Upgrade vms from 4.7 to a5.01
$!		>	>	>
$!
$!
$! This command procedure is always run when anybody on the entire system
$! logs in. It is equivalent to LOGIN.COM except that the instructions
$! contained herein are executed everytime anyone on the VMS system
$! logs in to their account.
$!
$! For interactive processes, turn on Control T, and set the terminal type
$!
$ IF (F$MODE() .EQS. "INTERACTIVE") THEN SET CONTROL=T
$ IF (F$MODE() .EQS. "INTERACTIVE") THEN SET TERMINAL/INQUIRE
$!
$! For MicroVAX systems only, use the command INSTALL/COMMAND
$! and MOUNT/NOASSIST.
$!
$ IF (.NOT. F$TRNLNM("SYS$MICROVAX")) THEN GOTO SKIP_MICROVAX_COMMANDS
$SKIP_MICROVAX_COMMANDS:
$!
$! Place your site-specific LOGIN commands below
$!
$SET NOON
$Begin:
$!
$!	if F$EDIT(f$getjpi("username"),"collapse") .eqs. "MORRISSETTE" .AND. -
$!	   F$MODE() .EQS. "NETWORK" THEN SET VERIFY 
$ SET NOVERIFY
Network startup
$ SET DISPLAY/CREATE/NODE=STRYKR 
$ GOTO BATCHENTRY
$BATCHENTRY:
$ !  Copyright (c) 1987 Digital Equipment Corporation.  All rights reserved.
$ IF "" .NES. "" THEN NETSERVER$COMMAND
$ IF ""  .EQS. "" THEN NETSERVER$VERIFY = 0
$ V = F$VERIFY(NETSERVER$VERIFY)

        --------------------------------------------------------

        Connect request received at  2-APR-1990 13:34:05.00
            from remote process STRYKR::"0=STRYKER"
            for object "SYS$COMMON:[SYSEXE]FAL.EXE"

        --------------------------------------------------------


        --------------------------------------------------------

        Connect request received at  2-APR-1990 13:34:46.86
            from remote process STRYKR::"0=STRYKER"
            for object "SYS$SYSTEM:WAU_SERVER.EXE"

        --------------------------------------------------------

read=0,0,NOTES/DECWINDOWS
server=0
screen=0
command=NOTES/DECWINDOWS
HBO::STRYKER will execute NOTES/DECWINDOWS on server 0 screen 0
NOTES/DECWINDOWS failed
%RMS-E-FNF, file not found
network object is unknown at remote node

Hi, I'm still having trouble firing remote DECW commands.  Even though you
normally work on an ULTRIX system, I thought maybe seeing the NETSERVER.LOG
file might help you HELP ME figure out what's wrong.

From my workstation, I'm typing: DW_NET HBO "NOTES/DECWINDOWS"
- a perfectly logical command.  Node STRYKR is my workstation, which has proxy
access to and from HBO.

Thanks,

Stew

p.s. NETSERVER.LOG file follows
-------------------------------------------------------------------------
$!
$!	ico_sys:[sysmgr]SYLOGIN.com	for the ICO sub-cluster
$!
$!	Created:	????
$!
$!	Edited:	10-Nov-1988	PLB	Added L3ISS* symbols for Rick Sherman's LN03R
$!					eliminated ICVAXB printer symbols, moved printer
$!					symbols up into the "all-jobs" area.
$!		18-Feb-1989	PLB	Added VCSLSU & DMTERM symbols
$!		22-Jun-1989	RJJ	Added jpi symbol for convience
$!		28-Aug-1989	RJJ	Rewrite of LPS40 symbols
$!		30-NOV-1989	deb	Upgrade vms from 4.7 to a5.01
$!		>	>	>
$!
$!
$! This command procedure is always run when anybody on the entire system
$! logs in. It is equivalent to LOGIN.COM except that the instructions
$! contained herein are executed everytime anyone on the VMS system
$! logs in to their account.
$!
$! For interactive processes, turn on Control T, and set the terminal type
$!
$ IF (F$MODE() .EQS. "INTERACTIVE") THEN SET CONTROL=T
$ IF (F$MODE() .EQS. "INTERACTIVE") THEN SET TERMINAL/INQUIRE
$!
$! For MicroVAX systems only, use the command INSTALL/COMMAND
$! and MOUNT/NOASSIST.
$!
$ IF (.NOT. F$TRNLNM("SYS$MICROVAX")) THEN GOTO SKIP_MICROVAX_COMMANDS
$SKIP_MICROVAX_COMMANDS:
$!
$! Place your site-specific LOGIN commands below
$!
$SET NOON
$Begin:
$!
$!	if F$EDIT(f$getjpi("username"),"collapse") .eqs. "MORRISSETTE" .AND. -
$!	   F$MODE() .EQS. "NETWORK" THEN SET VERIFY 
$ SET NOVERIFY
Network startup
$ SET DISPLAY/CREATE/NODE=STRYKR 
$ GOTO BATCHENTRY
$BATCHENTRY:
$ !  Copyright (c) 1987 Digital Equipment Corporation.  All rights reserved.
$ IF "" .NES. "" THEN NETSERVER$COMMAND
$ IF ""  .EQS. "" THEN NETSERVER$VERIFY = 0
$ V = F$VERIFY(NETSERVER$VERIFY)

        --------------------------------------------------------

        Connect request received at  2-APR-1990 13:34:05.00
            from remote process STRYKR::"0=STRYKER"
            for object "SYS$COMMON:[SYSEXE]FAL.EXE"

        --------------------------------------------------------


        --------------------------------------------------------

        Connect request received at  2-APR-1990 13:34:46.86
            from remote process STRYKR::"0=STRYKER"
            for object "SYS$SYSTEM:WAU_SERVER.EXE"

        --------------------------------------------------------

read=0,0,NOTES/DECWINDOWS
server=0
screen=0
command=NOTES/DECWINDOWS
HBO::STRYKER will execute NOTES/DECWINDOWS on server 0 screen 0
NOTES/DECWINDOWS failed
%RMS-E-FNF, file not found
network object is unknown at remote node

Hi, I'm still having trouble firing remote DECW commands.  Even though you
normally work on an ULTRIX system, I thought maybe seeing the NETSERVER.LOG
file might help you HELP ME figure out what's wrong.

From my workstation, I'm typing: DW_NET HBO "NOTES/DECWINDOWS"
- a perfectly logical command.  Node STRYKR is my workstation, which has proxy
access to and from HBO.

Thanks,

Stew

p.s. NETSERVER.LOG file follows
-------------------------------------------------------------------------
$!
$!	ico_sys:[sysmgr]SYLOGIN.com	for the ICO sub-cluster
$!
$!	Created:	????
$!
$!	Edited:	10-Nov-1988	PLB	Added L3ISS* symbols for Rick Sherman's LN03R
$!					eliminated ICVAXB printer symbols, moved printer
$!					symbols up into the "all-jobs" area.
$!		18-Feb-1989	PLB	Added VCSLSU & DMTERM symbols
$!		22-Jun-1989	RJJ	Added jpi symbol for convience
$!		28-Aug-1989	RJJ	Rewrite of LPS40 symbols
$!		30-NOV-1989	deb	Upgrade vms from 4.7 to a5.01
$!		>	>	>
$!
$!
$! This command procedure is always run when anybody on the entire system
$! logs in. It is equivalent to LOGIN.COM except that the instructions
$! contained herein are executed everytime anyone on the VMS system
$! logs in to their account.
$!
$! For interactive processes, turn on Control T, and set the terminal type
$!
$ IF (F$MODE() .EQS. "INTERACTIVE") THEN SET CONTROL=T
$ IF (F$MODE() .EQS. "INTERACTIVE") THEN SET TERMINAL/INQUIRE
$!
$! For MicroVAX systems only, use the command INSTALL/COMMAND
$! and MOUNT/NOASSIST.
$!
$ IF (.NOT. F$TRNLNM("SYS$MICROVAX")) THEN GOTO SKIP_MICROVAX_COMMANDS
$SKIP_MICROVAX_COMMANDS:
$!
$! Place your site-specific LOGIN commands below
$!
$SET NOON
$Begin:
$!
$!	if F$EDIT(f$getjpi("username"),"collapse") .eqs. "MORRISSETTE" .AND. -
$!	   F$MODE() .EQS. "NETWORK" THEN SET VERIFY 
$ SET NOVERIFY
Network startup
$ SET DISPLAY/CREATE/NODE=STRYKR 
$ GOTO BATCHENTRY
$BATCHENTRY:
$ !  Copyright (c) 1987 Digital Equipment Corporation.  All rights reserved.
$ IF "" .NES. "" THEN NETSERVER$COMMAND
$ IF ""  .EQS. "" THEN NETSERVER$VERIFY = 0
$ V = F$VERIFY(NETSERVER$VERIFY)

        --------------------------------------------------------

        Connect request received at  2-APR-1990 13:34:05.00
            from remote process STRYKR::"0=STRYKER"
            for object "SYS$COMMON:[SYSEXE]FAL.EXE"

        --------------------------------------------------------


        --------------------------------------------------------

        Connect request received at  2-APR-1990 13:34:46.86
            from remote process STRYKR::"0=STRYKER"
            for object "SYS$SYSTEM:WAU_SERVER.EXE"

        --------------------------------------------------------

read=0,0,NOTES/DECWINDOWS
server=0
screen=0
command=NOTES/DECWINDOWS
HBO::STRYKER will execute NOTES/DECWINDOWS on server 0 screen 0
NOTES/DECWINDOWS failed
%RMS-E-FNF, file not found
network object is unknown at remote node

Dan,

Thanks for you help with this.  To those of you who weren't following it, the
person that installed the server portion of DW_NET missed the WAU_SERVER.COM
file.

When presented with that information, the system manager suggested that, if
time allowed, the installation might be made easier if it prompted the installer
with:
	Client, Server, or Both (C,S, or B):

and allowed the installer to chose one.  This would make installing the
server portion much easier.

Just a suggestion...  8^)

Thanks again to Dan.

Stew

.-1
Any body out there wants to do it.  I'd be glad to incorporate it into the 
installation kit.  

My boss wants me to do real work now :^)

Dan,

I definitely know of where you speak.  I developed a tool for VAX RALLY recently
and finally had to say "I'll get to it sometime" when I was assigned to a new
and important project.

That's the tough part about midnight hacks is you really want to continue
"growing it."

We'll, I've got to get back to my midnight hack.  I've got some new features
I've been wanting to add...

Stew

This utility is great. It is exactly what I need to make distributed
computing really work for one of our clients.

So, can this be sold or giving to a client?

If yes, what needs to be done to do it legitamately?

If no, why not and how/when can this be changed?

Thanks,
	 Dan.

   gak, why don't field people realize that there is more to releasing a
   product, than just getting a piece of software working. Never mind, I seem
   to recall an inference (not commitment) in either this or one of the other
   DECwindows related conferences, that this sort of functionality might be
   available in a later release of DECwindows.
   
   
   IF there is some functionality that you think is important for your
   customers, don't just sit there, tell the product manager about it.
   
   q
   

    Wee-e-e-e-llll,,  
    
    	From the "field"...
    
    	Since a lot of times products appear to be released without the
    software functioning, if we find something that is actually functional,
    we assume it has been a product for awhile 8-).
    
    		Lou "Getting to be an old time field hand now..." Northern

   Excuse  me, but I had over ten years of field experience before I moved
   into an engineering role. I found, even then, theat the most efficient way
   to get a "feature" included in a product was to contact the product manager
   and make sure that it got into the phase review for the next release.
   
   I have noticed a large number of comments lately like "Well this is good,
   let's make it an ASSET and ship it." While this may have benefits that show
   in local revenue, and customer satisfaction, it does nothing for the
   engineering of our products (No reflection is intended on the assets
   program or any of it's contributors.).
   
   Mechanisms exist for field input to product engineering. If these
   mechanisms aren't working then that is a different kettle of fish.
   
   q
   

    >gak, why don't field people realize that there is more to releasing
    >product, than just getting a piece of software working.
    
    You must have been in a very bad mood when you wrote this!
    Be nice.
    
    Kris..
                                     

.56>  gak, why don't field people realize that there is more to releasing a
.56>  product, than just getting a piece of software working.

Please forgive me for being so stupid, but you know how us field people tend
to be so out of touch.

.56>  Never mind, I seem
.56>  to recall an inference (not commitment) in either this or one of the other
.56>  DECwindows related conferences, that this sort of functionality might be
.56>  available in a later release of DECwindows.
   
Gee, maybe I should use some of the time I spend "just sitting here" and read
this entire conference (and all related conferences).  Then I could detect an
_INFERENCE_  that this  _SORT_  of functionality  _MIGHT_  be available in a
_LATER_  release.  Then I can sit here some more and see if it ever
happens (I'm sure our customer will be happy to wait too, 8-) ).

Seriously,  it would be possible to sell some consulting time, and accomplish
this functionality with a bunch of DCL commands.  But it certainly would not be as 
as good or reliable as DW_NET.  I realize that some care would need to be taken 
when implementing this, but there are a few field people that (Mr. q might
not believe this, but,) are smart enough to do just that.

What I'm trying to find out is: How can I have a capable SWS consultant 
implement this utility at a client site, without breaking any rules?

-Dan

Where does DW_NET store the password when you customize a node to include a 
username and password?

Where does DW_NET get the list of nodes presented when you customize a node?

Love it,
Stephen

 I have begun the process of submitting DWNET to assets.

DW_NET does not store the passwords on DISK.  (Security probably would not like
this.  DW_NET has an array of passwords that it uses.  So when you exit DW_NET
all passwords disapear.

DW_NET gets the list of nodes from the .Xdefaults or DECW$SM_GENERAL.dat files.

These files are updated by the SECURITY menu on the Session Manager.  DW_NET 
reads these files when it is invoked so if you change the files you will have 
to restart the application.

By the way there was an effort started to provide DW_NET functionality mentioned
in a DIS magazine.  I investigated it and their financing was pulled.

Dan

    It would be nice if DW_NET allowed the something like the following:
    
    $ dw_net <display node> <remote node>  "blah blah blah"
    
    This would allow this tool to be used on VT1000s, or the ELN DECwindows
    servers. If DW_NET could determine the nodename of the workstation
    automatically, so much the better. Could I temporarily redefine a
    logical to achieve the above? 
    
    Greg	

You could certainly hack up the REMOTE_LOGIN procedure that I posted 
(and which has been subsequently improved upon) in DW_EXAMPLES
to do what you like.


The COM file assumes that it should create the process with display set
to the node from which the connection came, however, you can change it
to do what ever you like.

Be careful though.  If the client doesn't know the nodename string, 
you'll have trouble


-bill

    I think that the DW_NET executable needs to be changed to do what I
    want cleanly. Any chance of making the sources available? (I know
    someone has already made a request for the sources in DW_EXAMPLES.)
    
    Greg.

I co-wrote a hack to start the applications I use remotely.  Having tested and
liked DW_NET, I converted my DECW$LOGIN.COM to use it, as in:

$! DECW$LOGIN.COM
$ Set NoOn
$ DW_NET	CRBOSS       Run Sys$System:Decw$Bookreader
$! DW_NET	CRBOSS       Run Sys$System:Decw$Calc
$! DW_NET	CRBOSS       Inform
$! DW_NET	CRBOSS       Run Sys$System:DECwrite
$ DW_NET	CRBOSS       Run Sys$System:Decw$Calendar
$! DW_NET	CRBOSS       Run Sys$System:Decw$Cardfiler
$! DW_NET	CRBOSS       Run Sys$System:Decw$Clock
$ DW_NET	CRBOSS       Run Sys$System:Decw$Mail
$! DW_NET	CRBOSS       Run Sys$System:Decw$NotePad
$ DW_NET	CRBOSS       Notes/DECwindows
$! DW_NET	CRBOSS       Run Sys$System:Decw$Paint
$! DW_NET	CRBOSS       Run Sys$System:Decw$Puzzle
$! DW_NET	CRBOSS       Run Sys$System:Rags
$ DW_NET	CRBOSS       Vtx/Device_Type=DECwindows
$ DW_NET	CRBOSS       Run Sys$System:Vue$Master

When this DECW$LOGIN executes as part of my session login, I get:

login information invalid at remote node

Yet when I execute the same DECW$LOGIN.COM from a DECterm window AFTER session
login has completed, all is well.  So ($ SET MODE/GUESSING) it seems that
session security information is not available by the time DECW$LOGIN.COM
runs.  This isn't a DW_NET problem, but others that follow may see the same
thing, so I ask the question here:

	why does this occur?

Should I put $WAIT command at the top of DECW$LOGIN.COM, or is there a more
elegant way around this?

I know I've seen this problem discussed before, but � hour of diligant DIR/TITLE
bore no fruit.

Thanks!
tl

I used to do something like that, too.  Adding a WAIT did not help, it just
delayed login.  I guessed that the session manager was waiting for DECW$LOGIN
to finish.  I ended up having decw$login do a SPAWN/NOWAIT @DW_STARTUP, and put
the WAIT in DW_STARTUP before the @DECWNETs.

	:Karl.

Re .67 - right you are, that did the trick.

What's the line I should add to my XDEFAULTS file to have DW_NET iconify on
startup?

tl

    >        <<< Note 2216.63 by AUSSIE::SULLIVAN "Greg Sullivan" >>>
    >                    -< Start DW_NET on boot-node? >-

    >It would be nice if DW_NET allowed the something like the following:
    
    >$ dw_net <display node> <remote node>  "blah blah blah"
    
    >This would allow this tool to be used on VT1000s, or the ELN DECwindows
    >servers. If DW_NET could determine the nodename of the workstation
    >automatically, so much the better. Could I temporarily redefine a
    >logical to achieve the above? 
    
    >Greg	

    DW_NET and X can support what you want now.  There is a an application
    called decw$dwt_decnet.exe on VMS that allows you to redirect X comming
    back to a node from that node to an X terminal.  It is explained in the 
    back of the VT1000 manual.  You use these routines to set up an
    alternative server.  Then set up DW_NET to use the alternate server
    using the nodes screen under the customize menu.  You can do a similar
    thing with Ultrix nodes using the example software gatewayd on
    /usr/examples/decnet/...
    
    From command line you can set up the command 
    
    $dw_net/server=5 node command
    
    Dan