@ From:	CSBVAX::MRGATE!GRANROTH@IOWASP.SPAN@SMTP 14-MAY-1988 03:36 To:	ARISIA::EVERHART Subj:	DECnet "master" server    R Received: from STAR.STANFORD.EDU by KL.SRI.COM with TCP; Fri 6 May 88 13:59:17-PDTC Received: from IOWASP by STAR.STANFORD.EDU via MAIL-11 with DECnet;  	  Fri, 6 May 88 13:58:12-PDT  Date: Fri 6 May 88 13:58:11-PDT < From: GRANROTH%IOWASP.SPAN@STAR.STANFORD.EDU (Larry Granroth       319/335-1960)  Subject: DECnet "master" server  To: info-vax@[128.18.10.6]  > Our local system manager recently disabled the "0=" or "TASK="B option in DECnet on our 11/780.  Previous to this, I had developedB a number of network client/server systems which used this feature.@ For example, I could distribute a client executable program to aC number of users on remote nodes which would handle a user interface @ and produce data plots at the user's local node while requestingC reduced data from a central server.  In the client FORTRAN program, , I used an open statement like the following:   	open (	unit	= net, 3 	1	file	= 'NODE"USER PASSWORD"::"TASK=SERVER.COM"',  	1	status	= 'OLD', 	1	form	= 'UNFORMATTED', 	1	access	= 'SEQUENTIAL')   F Which would initiate the execution of the command file indicated afterF the "TASK=".  The "USER" account allowed only network access much likeF the DECNET default account.  The server command file would execute theA server FORTRAN program which would immediately open a file called E "SYS$NET" similar to the above open statement.  As long as the client G and server conformed to some protocol, they could very effectively pass G information back and forth by writing to and reading from these network F "files".  Unfortunately, now that the "TASK=" feature is disabled, theG only network servers allowed must be assigned a network task number and F be installed by the system manager.  Having to have the system managerE install every server would be a pain in the proverbial to start with, E but the killer is that there is only a limited small number (255?) of E network task numbers available and the system manager doesn't want to F give me more than one or two.  An acceptable solution would be to haveC a single network task number point to a "master" command file which D could accept a keyword from the client software and then fire-up theD appropriate server.  Unfortunately, nobody here seems to know how toD implement this.  I can open SYS$NET in the DCL master and accept theE keyword and start a second command file, but I get an access conflict G when the server FORTRAN program tries also to open SYS$NET.  I've tried I opening the network "file" with shared access in both places, but I still E get the same error.  Closing the file in DCL doesn't work because the C network connection is then lost.  I guess the problem is similar to E trying to open a file during the execution of one program then trying 0 to use the file in a spawned subprocess. (maybe)   C So here's the question:  Does anyone out there know of a simple way I to implement a "master" network server which would accept key information B from a remote client task and then start up an appropriate server?  O (In case it isn't obvious by this point, I'm working with VMS, DCL, DECnet/VMS,  and VAX FORTRAN.)   E Please respond directly to me, since I don't usually have the time to  read all of INFO-VAX.    Larry Granroth Programmer/Analyst Dept. of Physics and Astronomy University of Iowa Iowa City, IA  52242  & GRANROTH%IOWASP.SPAN@STAR.STANFORD.EDU