Xref: utzoo comp.databases:1932 comp.dcom.lans:2334 comp.lsi:629 comp.protocols.tcp-ip:6089 comp.software-eng:1020 comp.std.internat:460 comp.std.misc:72
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!sm.unisys.com!csun!srhqla!ncs
From: ncs@srhqla.UUCP (Sekar)
Newsgroups: comp.databases,comp.dcom.lans,comp.lsi,comp.protocols.tcp-ip,comp.software-eng,comp.std.internat,comp.std.misc
Subject: Re: Network Definition Language
Keywords: Network Design, Languages, Expert Systems, Databases, Soft. Engineering
Message-ID: <509@srhqla.UUCP>
Date: 2 Feb 89 00:18:43 GMT
References: <153@qusunb.queensu.CA>
Reply-To: ncs@srhqla.UUCP (Sekar)
Followup-To: comp.databases
Organization: Silent Radio, Los Angeles
Lines: 15

In article <153@qusunb.queensu.CA> fokas@qucis.queensu.CA (Elias Fokas) writes:
>
>                                  Abstract
>
>                         Network Definition Language (NDL)
>

Unisys (Detroit,MI) has had this language ( called NDL ! - same expansion )
on all its (Burroughs) mainframes with proprietary OS ( MCP - master control
program) for many,many years.
I know it handles some ( not all ) of your conceptual requirements.

Hope this helps.

- sekar