Note:
BITNET channels were relegated to obsolete status as of PMDF V5.2. Completely untested and unsupported BITNET channel images have been built for PMDF V6.0 and included in the V6.0 distribution. Sites that wish may try using them, but Innosoft does not warrant that they will work or work correctly.
Jnet and ANJE channels are used to link PMDF to either Jnet or ANJE.¹ Both of these software packages implement NJE compliant networking under OpenVMS. NJE networking is used to link OpenVMS systems to the national BITNET network as well as its sister networks internationally. The documentation presented here is intentionally biased towards sites on BITNET; sites on NJE networks disjoint from BITNET will have to ignore all the BITNET-specific information contained in this chapter and devise their own procedures for configuring their networks.
Jnet and ANJE channels use a single unidirectional master program and a single unidirectional slave program. The master program can only send while the slave program can only receive. There is also a third channel program for use with Jnet and ANJE; this channel is used to implement mailer processing and is not itself directly attached to Jnet or ANJE.
The slave program runs either as Jnet's Local Mail Delivery (LMD) agent or as the ANJE delivery daemon and is only associated with one channel (the "local NJE" channel). The master program is invoked by MASTER.COM for all Jnet and ANJE channels.
Jnet and ANJE channels are generated by the automatic configuration generator if any are needed.
Note:
PMDF is compatible with versions 3.2, 3.3, 3.4, 3.5, 3.6, and 3.7 of Jnet and version 5 of ANJE. Other versions of these packages may require alterations to the PMDF interface.
Note:
The command filelmd.commay need to be adapted to different versions of Jnet, and the username changing routine USERNAME used by ANJE master channels may need to be relinked since it is linked against the system symbol table SYS.STB. Use the command procedurePMDF_COM:link_username.comto relink this image.