Xref: utzoo comp.sys.dec:4418 comp.dcom.lans:6430
Path: utzoo!attcan!uunet!mcsun!cernvax!chx400!urz.unibas.ch!doelz
From: doelz@urz.unibas.ch
Newsgroups: comp.sys.dec,comp.dcom.lans
Subject: Re: DECnet task-to-task programming
Message-ID: <1990Nov5.131642.1124@urz.unibas.ch>
Date: 5 Nov 90 12:16:42 GMT
References: <873@fred.UUCP>
Organization: University of Basel, Switzerland
Lines: 24

In article <873@fred.UUCP>, rbraun@polygen.uucp (Richard Braun) writes:
> I'm developing a DECnet task-to-task interface for a distributed
> Unix application being ported to VMS.
> 
> The code I've written uses DECnet nontransparent operations, and
> declares a server as a named object.

You can avoid this if you use a PROXY account, then 0= ... will 
start a com file in the user's directory. In the DECnet implementation
of UNIX boxes, mostly the uid serves as username.  

..
> 
> Question:  under DECnet, how to I initiate a task-to-task
> connection *between two existing processes* (a la Berkeley sockets)
> without having to resort to named objects?  If I have to use named
> objects, can I get around the security problem some other way?

Forgive me, but why don't you use sockets on VMS? Even UCX 1.2 supports 
sockets, and they work. Code is portable in between systems in you ifdef
the include libraries. 

Regards 
Reinhard