Xref: utzoo comp.sys.dec:4459 comp.dcom.lans:6469
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!aplcen!jhunix!ereiamjh
From: ereiamjh@jhunix.HCF.JHU.EDU (Tom B. O'Toole)
Newsgroups: comp.sys.dec,comp.dcom.lans
Subject: Re: DECnet task-to-task programming
Message-ID: <6810@jhunix.HCF.JHU.EDU>
Date: 8 Nov 90 19:38:25 GMT
References: <873@fred.UUCP> <1990Nov7.231928.20631@freedom.msfc.nasa.gov>
Followup-To: comp.sys.dec
Organization: The Johns Hopkins University - HCF
Lines: 16

You only need sysnam to declare a certain process as a server for an
object, but you might be able to accomplish the same thing by creating
an object in the ncp database. You can specify the username of the account
you want the server process(s) to run under. Then if you fire the process up
with an intial request, you can make it stick around by defining a logical
name of the form NETSERVER$SERVERS_USERNAME to be the number of servers you
want. You can't have a multi-threaded server this way, but if you pre-start
as many processes as the maximum number of links you expect, you will be able
to handle them with your pool of processes. I'm not sure if this is acceptable,
but you didn't really specify exactly what it was you wanted to do...


-- 
Tom O'Toole - ecf_stbo@jhuvms.bitnet - JHUVMS system programmer 
Homewood Computing Facilities, Johns Hopkins University, Balto. Md. 21218 
ease!Trim!eeeaaaassse!trimtrimtrimeeeeeeaaaaassetrimease!trim!ease!trimeaase