Article 128448 of comp.os.vms:
Path: nntpd.lkg.dec.com!pa.dec.com!decuac.dec.com!haven.umd.edu!purdue!lerc.nasa.gov!magnus.acs.ohio-state.edu!math.ohio-state.edu!howland.reston.ans.net!swrinde!ihnp4.ucsd.edu!mvb.saic.com!info-vax
From: "GWDGV1::MOELLER" <moeller@gwdgv1.dnet.gwdg.de>
Newsgroups: comp.os.vms
Subject: RE: How do I create a network process
Message-ID: <58379819@MVB.SAIC.COM>
Date: Sat, 2 Sep 1995 05:03:25 +0200
Organization: Info-Vax<==>Comp.Os.Vms Gateway
X-Gateway-Source-Info: Mailing List
Lines: 61

Simon Howden <howdens@WCG.CO.UK> asks:
> Does any one know how DECnet creates its network server
> processes. What parameters does it pass to CREPRC to get it to
> create the process as another user, or does it use some other
> underhanded mechanism ?
>[...]

Last year, I wrote up the following ...

How to create a NETWORK process
-------------------------------

Create a _detached_ process via $CREPRC, with SYS$SYSTEM:LOGINOUT.EXE 
as the 'image' to be run, and set the PRC$M_NETWORK bit in the 'stsflg'
argument (DCL $RUN doesn't support this flag, so you need a program
to do this). 

Specify the command procedure to be run as 'input' (traditionally,
the network process can find this string in the "TT" logical name).

As 'output', LOGINOUT expects an (undocumented) binary variable-length
data structure, which in assember notation is either

	.word	0		; normal login (w/ password check)
	.ascic  username
	.ascic  password
	.byte	0

or (VMS V5 and up only)

	.word   1		; proxy login based on ...
	.ascic  proxyuser	; ... this username (w/o password)
	.ascic  username2	; use these in case 'proxyuser' is invalid
	.ascic  password2
	.byte	0

In C notation,
	.word = 'short int'
	.byte = 'char'
	.ascic = <an 'unsigned char' holding the string length, 
	          followed by that many 'char's>.

Whatever you specify as the 'error' argument to $CREPRC,
will be assigned to the logical name SYS$NET; if this string
contains a slash ('/'), as is always the case with DECnet, 
LOGINOUT will also [attempt to] define SYS$REM_NODE and SYS$REM_ID.

The network process's SYS$OUTPUT and SYS$ERROR will always be 
directed to a .LOG file in the target user's default directory, 
with the file name matching the ('input') command procedure's name.

The remaining arguments to $CREPRC have no bearing on the network process,
but don't forget to set 'baspri' to at least 4 (DEFPRI), or else the 
process creation itself will be very slow (lately, UCX V2.0 suffered 
from this oversight).

-----

Wolfgang J. Moeller, Tel. +49 551 2011516 or -510, moeller@gwdgv1.dnet.gwdg.de
GWDG, D-37077 Goettingen, F.R.Germany           PSI%(0262)45050859008::MOELLER
Disclaimer: No claim intended!  |  moeller@decus.decus.de   w.moeller@ieee.org