Michael Corbett wrote:
>
> Jeremy Begg wrote:
>
> >
> > Another option would be to carefully manage the MULTINET:SERVICES.MASTER_SERVER
> > file so that MultiNet starts up with TELNET disabled. But it would be
> > rather messy to get consistently right.
> >
>
> Another thing you could try is to pass "NOSERVER" as p1
> to start_multinet.com. The code does the following -
>
> $ If P1 .Nes. "NOSERVER" .And. F$Search("MultiNet:Server.Exe") .Nes. "" Then -
> $ @MultiNet:Start_Server
>
> Then you could execute multinet:start_server.com later in the
> system startup.

What kind of fall-out could I expect from that? That is, what other
inbound connections will fail besides Telnet? How 'bout print queues?

....and how (in)compatible would that be with Oracle, MQ Series and
Cerner Millennium?

--
David J Dachtera
dba DJE Systems
http://www.djesys.com/

Unofficial OpenVMS Hobbyist Support Page:
http://www.djesys.com/vms/support/

Unofficial Affordable OpenVMS Home Page:
http://www.djesys.com/vms/soho/

Unofficial OpenVMS-IA32 Home Page:
http://www.djesys.com/vms/ia32/

Coming soon:
Unofficial OpenVMS Marketing Home Page