🚀 go-pugleaf

>
> We upgraded to Jnet V3.6 using 3 DNANJE links and 1 BSC/370 link last Friday.
> As Jack Pernice said, the new install does not replace your lmd.com.  Along with
> other user-configurable procedures, they give you a template file and tell you
> to merge your local modifications into it.
>
> For LMD.COM, I just left the Jnet template alone and used the LMD.COM from PMDF
> V4.1.  We've had no problems since then (related to Jnet, that is - but that's
> another story :-).
>
> Dan
>
>    Daniel A. Dinkin
>    Network Services Manager                   BITNET: dan@towsonvx.bitnet
>    IR Academic Computing                    Internet: dan@toe.towson.edu
>    Towson State University                            dan@midget.towson.edu
>    Towson, Maryland 21204                UMSA DECnet: toe::e7opdan
>    (410)830-3320
>
>      Any thoughts in this message are purely random and my employer had
>            nothing to do with them... especially if I was right.
>
What release of JNET did you upgrade from?  We are running JNET V3.4 and
PMDF V4.1-10.  Do I have to switch to the LMD.COM (V3.5) from PMDF 4.1 or
stick with LMD.V34 after upgrading to Jnet V3.6?

------------------------------------------------------------------------------
 Eliza Lau
 Virginia Tech Computing Center                Internet : LAUE@VTCC1.CC.VT.EDU
 1700 Pratt Drive                               Bitnet  : LAUE@VTCC1
 Blacksburg VA 24060                            Voice   : (703) 231-9399
------------------------------------------------------------------------------