 |
| NJE Mainframe Network Links using TCPNJE and DNANJE (NJE over DECnet) on DEC VAX server running VAX/VMS operating system |
---
30-Oct-2023 Update: There is a VMS 4.7 Turnkey Distribution now available for a while from our Discord group. It includes everything and is available here.
---
---
The ancient JNET software for VAX/VMS from now-defunct Wingra Software allows Digital Equipment Corporation DEC VAX servers running VAX/VMS operating system to interact in TCPNJE protocol prevalent in the IBM Mainframe world over DECnet and TCP/IP links. This allows hobbyists running DEC VAX computers to participate on two world-wide hobbyist networks - HECnet the DECnet network and HNET the Mainframe network.
As a working example, JNET version 3.5 works on old VAX/VMS 4.7 operating system. The only trouble during installation is the installer gets confused while creating the POSTMASTER account. The workaround that I learned from Timothy Stark is to repeat the installation but specifying that the POSTMASTER account already exists when asked the second time.
Here is a terminal session from installing JNET 3.5 on VAX/VMS 4.7.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| $! ---------- | |
| $! JNET 3.5 INSTALLATION ON VAX VMS 4.7 (IBM MAINFRAME TCPNJE NETWORKING FROM DIGITAL DEC VAX VMS) | |
| $! See https://supratim-sanyal.blogspot.com/2020/04/vaxvms-47-with-decnet-link-to-hecnet.html | |
| $! ---------- | |
| $ @SYS$UPDATE:VMSINSTAL | |
| VAX/VMS Software Product Installation Procedure V4.7 | |
| It is 8-APR-2020 at 01:14. | |
| Enter a question mark (?) at any time for help. | |
| %VMSINSTAL-W-DECNET, Your DECnet network is up and running. | |
| * Do you want to continue anyway [NO]? YES | |
| * Are you satisfied with the backup of your system disk [YES]? | |
| * Where will the distribution volumes be mounted: MTA0: | |
| Enter the products to be processed from the first distribution volume set. | |
| * Products: JNET035 | |
| Please mount the first volume of the set on MTA0:. | |
| * Are you ready? YES | |
| %MOUNT-I-MOUNTED, JNET mounted on _XLVII$MTA0: | |
| The following products will be processed: | |
| JNET V3.5 | |
| Beginning installation of JNET V3.5 at 01:15 | |
| %VMSINSTAL-I-RESTORE, Restoring product saveset A... | |
| %VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP. | |
| This is Jnet V3.5 Installation Procedure V3.5. | |
| * Do you want to purge files replaced by this installation [YES]? | |
| * Do you want Jnet temporary files on a separate device [NO]? | |
| * Enter the name of the Jnet device [SYS$SYSDEVICE]: DUA1 | |
| * Do you want to install the whole kit [YES]? | |
| * Does the POSTMASTER account already exist [NO]? | |
| * Do you want obsolete Jnet files deleted [YES]? | |
| There will be no more questions... | |
| Setting up logical names... | |
| Creating Jnet node-specific directories... | |
| %CREATE-I-EXISTS, JAN_TMPSPECIFIC:[SYS] already exists | |
| Creating Jnet common directories... | |
| %CREATE-I-EXISTS, JAN_TMPCOMMON:[SYS] already exists | |
| Creating V4 compatibility directories... | |
| Creating POSTMASTER account... | |
| %VMSINSTAL-I-ACCOUNT, This installation creates an account named POSTMASTER. | |
| %UAF-I-ADDMSG, user record successfully added | |
| %DCL-W-NEGATED, entity explicitly negated in command string | |
| %VMSINSTAL-W-BADACC, Unable to CREATE/MODIFY account POSTMASTER. | |
| %VMSINSTAL-E-INSFAIL, The installation of JNET V3.5 has failed. | |
| Enter the products to be processed from the next distribution volume set. | |
| * Products: JNET035 | |
| Please mount the first volume of the set on MTA0:. | |
| * Are you ready? YES | |
| %MOUNT-I-MOUNTED, JNET mounted on _XLVII$MTA0: | |
| The following products will be processed: | |
| JNET V3.5 | |
| Beginning installation of JNET V3.5 at 01:15 | |
| %VMSINSTAL-I-RESTORE, Restoring product saveset A... | |
| %VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP. | |
| This is Jnet V3.5 Installation Procedure V3.5. | |
| * Do you want to purge files replaced by this installation [YES]? | |
| * Do you want Jnet temporary files on a separate device [NO]? | |
| * Enter the name of the Jnet device [DUA1]: | |
| * Do you want to install the whole kit [YES]? | |
| * Does the POSTMASTER account already exist [NO]? YES | |
| * Do you want obsolete Jnet files deleted [YES]? | |
| There will be no more questions... | |
| Setting up logical names... | |
| %DCL-I-SUPERSEDE, previous value of JAN_ROOT has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_SPECIFIC has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_COMMON has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_COMMONV4 has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_SYS has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_LIB has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JANSHR has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JANBSCLIB has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JANNJELIB has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JANB2CTCLIB has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JANTCPLIB has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_ENCASESHR has been superseded | |
| %DCL-I-SUPERSEDE, previous value of MAIL$PROTOCOL_JNET has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_JMAILPROT has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_MFSDISP has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_TMPROOT has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_TMPSPECIFIC has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_TMPCOMMON has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_SPOOL has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_LOG has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_TRACE has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_TMPSYS has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_RECEIVE has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_QUE has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_JOB has been superseded | |
| Creating Jnet node-specific directories... | |
| %CREATE-I-EXISTS, JAN_SPECIFIC:[SYS] already exists | |
| %CREATE-I-EXISTS, JAN_TMPSPECIFIC:[SYS] already exists | |
| Creating Jnet common directories... | |
| %CREATE-I-EXISTS, JAN_COMMON:[SYS] already exists | |
| %CREATE-I-EXISTS, JAN_COMMON:[LIB] already exists | |
| %CREATE-I-EXISTS, JAN_TMPCOMMON:[SYS] already exists | |
| %CREATE-I-EXISTS, JAN_TMPCOMMON:[RECEIVE] already exists | |
| %CREATE-I-EXISTS, JAN_TMPCOMMON:[QUE] already exists | |
| %CREATE-I-EXISTS, JAN_TMPCOMMON:[JOB] already exists | |
| %CREATE-I-EXISTS, JAN_TMPCOMMON:[POSTMASTER] already exists | |
| Creating V4 compatibility directories... | |
| %CREATE-I-EXISTS, JAN_COMMONV4:[SYS] already exists | |
| %CREATE-I-EXISTS, JAN_COMMONV4:[LIB] already exists | |
| Providing DCL command definitions... | |
| Removing obsoleted JMONITOR command definition... | |
| Providing DCL help... | |
| Providing node-specific Jnet files... | |
| Providing Jnet common files... | |
| Providing V4 compatibility images... | |
| Deleting obsolete Jnet files... | |
| Ignore "%VMSINSTAL-W-NOFILE, File does not exist." messages... | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:BF.EXE does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:BITLIB.OLB does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:CLUD.EXE does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:CP.EXE does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:CP.HLB does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:DISKLOAD.EXE does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:GATE.COM does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:GATE.EXE does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_LIB:JANMAKENODE.COM does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_LIB:JANSITE.PLN does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_LIB:JANSITESTOP.PLN does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:JMAIL.COM does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:JMAIL.EXE does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:LMD.EXE does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:NETDATA.DOC does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:NETDATA.EXE does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:NETMON.EXE does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:RTRACE.EXE does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:SEND.COM does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:SENDNETD.EXE does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:TAGREAD.EXE does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_SYS:JMONITOR.EXE does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_LIB:JMONITOR.CLD does not exist. | |
| %VMSINSTAL-W-NOFILE, File JAN_COMMONV4:[SYS]QUE.EXE does not exist. | |
| This installation added or modified the following files: | |
| JAN_LIB:A1.COM | |
| JAN_LIB:BSCLIB.EXE | |
| JAN_LIB:BUILDDAEDISP.COM | |
| JAN_LIB:BUILDENCASE.COM | |
| JAN_LIB:BUILDENQUESPEC.COM | |
| JAN_LIB:BUILDMFSDISP.COM | |
| JAN_LIB:BUILDQUESPEC.COM | |
| JAN_LIB:DAE.HLB | |
| JAN_LIB:DAEDISP.FOR | |
| JAN_LIB:ENCASE.FOR | |
| JAN_LIB:ENCASESHR.EXE | |
| JAN_LIB:ENQUESPEC.FOR | |
| JAN_LIB:JANASK.COM | |
| JAN_LIB:JANCONFIG.COM | |
| JAN_LIB:JANSHR.EXE | |
| JAN_LIB:JANSHR.FOR | |
| JAN_LIB:JANSHR.H | |
| JAN_LIB:JANSHR.MAR | |
| JAN_LIB:JANSHR.PAS | |
| JAN_LIB:JANSHR.PEN | |
| JAN_LIB:JANTABLE.FOR | |
| JAN_LIB:JCP.HLB | |
| JAN_LIB:JNETMSG.MSG | |
| JAN_LIB:KITHELP.COM | |
| JAN_LIB:NJELIB.EXE | |
| JAN_LIB:PROFS.FDL | |
| JAN_LIB:RECHELP.HLB | |
| JAN_SYS:ALI.EXE | |
| JAN_SYS:BCDRIVER.EXE | |
| JAN_SYS:BFDRIVER.EXE | |
| JAN_SYS:BTDRIVER.EXE | |
| JAN_SYS:DAE.EXE | |
| JAN_SYS:DNANJE.EXE | |
| JAN_SYS:DT.EXE | |
| JAN_SYS:FNO.EXE | |
| JAN_SYS:JANSTART.COM | |
| JAN_SYS:JANSTOP.COM | |
| JAN_SYS:JCP.EXE | |
| JAN_SYS:JMAILPROT.EXE | |
| JAN_SYS:JOB.EXE | |
| JAN_SYS:JTRACER.EXE | |
| JAN_SYS:MAIL_PERM_ERRORS.DAT | |
| JAN_SYS:MFS.EXE | |
| JAN_SYS:OSINJE.EXE | |
| JAN_SYS:PROFSIN.EXE | |
| JAN_SYS:PROFSPROT.EXE | |
| JAN_SYS:QUE.EXE | |
| JAN_SYS:RECEIVE.EXE | |
| JAN_SYS:SEND.EXE | |
| JAN_SYS:SENDFILE.EXE | |
| JAN_SYS:ZIPPROT.EXE | |
| JAN_TMPSYS:PROFS.DAT | |
| JAN_COMMONV4:[SYS]BCDRIVER.EXE | |
| JAN_COMMONV4:[SYS]BFDRIVER.EXE | |
| JAN_COMMONV4:[SYS]BTDRIVER.EXE | |
| JAN_COMMONV4:[SYS]DAE.EXE | |
| JAN_COMMONV4:[SYS]JMAILPROT.EXE | |
| JAN_COMMONV4:[SYS]PROFSPROT.EXE | |
| JAN_COMMONV4:[SYS]ZIPPROT.EXE | |
| SYS$HELP:JNET035.RELEASE_NOTES | |
| SYS$LIBRARY:DCLTABLES.EXE | |
| SYS$HELP:HELPLIB.HLB | |
| * JAN_SPECIFIC:[SYS]JANSITE.COM merge customizations! | |
| * JAN_SPECIFIC:[SYS]JANSITESTOP.COM merge customizations! | |
| * JAN_LIB:JNET.CMU move to ALL-IN-1 directory? | |
| * JAN_LIB:JNET.COM move to ALL-IN-1 directory? | |
| * JAN_LIB:JMONITOR.HLP install in alternate HELPLIB? | |
| * JAN_LIB:JTRACER.CLD install in alternate DCLTABLES? | |
| * JAN_LIB:JTRACER.HLP install in alternate HELPLIB? | |
| * JAN_LIB:MFSDISP.FOR merge customizations? | |
| * JAN_LIB:PROFS.CMU move to ALL-IN-1 directory? | |
| * JAN_LIB:PROFS.COM move to ALL-IN-1 directory? | |
| * JAN_LIB:QUESPEC.FOR merge customizations? | |
| * JAN_LIB:RECEIVE.CLD install in alternate DCLTABLES? | |
| * JAN_LIB:RECEIVE.HLP install in alternate HELPLIB? | |
| * JAN_LIB:SEND.CLD install in alternate DCLTABLES? | |
| * JAN_LIB:SEND.HLP install in alternate HELPLIB? | |
| * JAN_LIB:SPECIAL.CMU move to ALL-IN-1 directory? | |
| * JAN_LIB:SPECIAL.COM move to ALL-IN-1 directory? | |
| * JAN_LIB:ZIP.CMU move to ALL-IN-1 directory? | |
| * JAN_LIB:ZIP.COM move to ALL-IN-1 directory? | |
| * JAN_SYS:ENCASE.EXE move to SYS$SYSTEM? | |
| * JAN_SYS:ENQUE.EXE move to SYS$SYSTEM? | |
| * JAN_SYS:JANSITECOMMON.COM merge customizations! | |
| * JAN_SYS:JANSITESTOPCOMMON.COM merge customizations! | |
| * JAN_SYS:JANTIDY.COM merge customizations? | |
| * JAN_SYS:LMD.COM merge customizations! | |
| * JAN_SYS:LOGIN.COM merge customizations? | |
| * - Files marked with "*" may need further attention after the | |
| installation procedure completes. | |
| ******************************************************************** | |
| Remember to do the following to complete the installation: | |
| (1) Perform any post installation tasks described in the Jnet | |
| Installation Guide. | |
| (2) Install any Jnet optional products before (re)configuring. | |
| (3) If you are upgrading an existing Jnet installation, merge your | |
| changes to site-specific configuration files with the new | |
| versions of these files. Also examine the Release Notes for any | |
| new configuration options which you may want to use. See the | |
| Jnet Manager's Guide for instructions on how to reconfigure | |
| Jnet if appropriate. | |
| (4) If this is a new Jnet installation, see the Jnet Manager's | |
| Guide for instructions on how to configure Jnet. | |
| ******************************************************************** | |
| %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... | |
| Installation of JNET V3.5 completed at 01:17 | |
| Enter the products to be processed from the next distribution volume set. | |
| * Products: JNETTCPNJE | |
| Please mount the first volume of the set on MTA0:. | |
| * Are you ready? YES | |
| %MOUNT-I-MOUNTED, JNET mounted on _XLVII$MTA0: | |
| The following products will be processed: | |
| JNETTCP V0.E | |
| Beginning installation of JNETTCP V0.E at 01:17 | |
| %VMSINSTAL-I-RESTORE, Restoring product saveset A... | |
| %VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP. | |
| This is Jnet TCP NJE V1.1 Installation Procedure V1.1. | |
| * Do you want to purge files replaced by this installation [YES]? | |
| Installing TCPNJE link driver... | |
| Installing MultiNet interface... | |
| Installing CMU-TEK IP/TCP interface... | |
| Installing VMS/ULTRIX Connection interface... | |
| Installing WIN/TCP for VMS interface... | |
| Installing FUSION interface... | |
| This installation added or modified the following files: | |
| JAN_LIB:B2CTCLIB.EXE | |
| JAN_LIB:TCPLIB.EXE | |
| JAN_LIB:TCPLIBCMU.EXE | |
| JAN_LIB:TCPLIBFUSION.EXE | |
| JAN_LIB:TCPLIBMNETV20.EXE | |
| JAN_LIB:TCPLIBMULTINET.EXE | |
| JAN_LIB:TCPLIBUCX.EXE | |
| JAN_LIB:TCPLIBWIN.EXE | |
| JAN_SYS:TCPNJE.EXE | |
| SYS$HELP:JNETTCPNJE011.RELEASE_NOTES | |
| %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... | |
| Installation of JNETTCP V0.E completed at 01:17 | |
| Enter the products to be processed from the next distribution volume set. | |
| * Products: | |
| * Products: Exit | |
| VMSINSTAL procedure done at 01:17 | |
| $ |
Once JNET is successfully installed (on DUA1: in this example), JNET is configured by invoking
@JAN_SYS:JANCONFIG
@JAN_SYS:JANCONFIG
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| $! ---------- | |
| $! JNET 3.5 CONFIGURATION ON VAX VMS 4.7 (IBM MAINFRAME TCPNJE NETWORKING FROM DIGITAL DEC VAX VMS) | |
| $! See https://supratim-sanyal.blogspot.com/2020/04/vaxvms-47-with-decnet-link-to-hecnet.html | |
| $! ---------- | |
| $ DIR JAN_LIB: | |
| Directory JAN_COMMON:[LIB] | |
| A1.COM;1 B2CTCLIB.EXE;1 BSCLIB.EXE;1 BUILDDAEDISP.COM;1 | |
| BUILDENCASE.COM;1 BUILDENQUESPEC.COM;1 BUILDMFSDISP.COM;1 | |
| BUILDQUESPEC.COM;1 COPYRIGHT.TXT;2 COPYRIGHT.TXT;1 DAE.HLB;1 | |
| DAEDISP.FOR;1 ENCASE.FOR;1 ENCASESHR.EXE;1 ENQUESPEC.FOR;1 | |
| JANASK.COM;1 JANCONFIG.COM;1 JANSHR.EXE;1 JANSHR.FOR;1 | |
| JANSHR.H;1 JANSHR.MAR;1 JANSHR.PAS;1 JANSHR.PEN;1 | |
| JANTABLE.FOR;1 JCP.HLB;1 JMONITOR.HLP;1 JNET.CMU;1 | |
| JNET.COM;1 JNETMSG.MSG;1 JTRACER.CLD;1 JTRACER.HLP;1 | |
| JTX.CLD_DEBUG;1 KITHELP.COM;1 MFSDISP.FOR;1 NJELIB.EXE;1 | |
| PROFS.CMU;1 PROFS.COM;1 PROFS.FDL;1 QUESPEC.FOR;1 | |
| RECEIVE.CLD;1 RECEIVE.HLP;1 RECHELP.HLB;1 SEND.CLD;1 | |
| SEND.HLP;1 SPECIAL.CMU;1 SPECIAL.COM;1 TCPLIB.EXE;1 | |
| TCPLIBCMU.EXE;1 TCPLIBFUSION.EXE;1 TCPLIBMNETV20.EXE;1 TCPLIBMULTINET.EXE;1 | |
| TCPLIBUCX.EXE;1 TCPLIBWIN.EXE;1 ZIP.CMU;1 ZIP.COM;1 | |
| Total of 55 files. | |
| $ @JAN_LIB:JANCONFIG | |
| This is JANCONFIG V3.11. | |
| Enter the approximate number of nodes in your NJE network [2]: 64 | |
| %JNET-I-SECTIONSIZE, allowing 114 node blocks in the global shared section | |
| Enter the NJE node name of the local host [XLVII]: | |
| Enter your local time zone: GMT | |
| Do you want to configure the batch server [YES]? | |
| Enter the NJE name of the batch server [JOB]: | |
| %JNET-I-SITE, initialize JNET_JOBLOG in JAN_COMMON:[SYS]JANSITECOMMON.COM (cold start) | |
| -JNET-I-CMD, $ INITIALIZE/QUEUE/PROCESSOR=ENQUE/ON="" JNET_JOBLOG | |
| %JNET-I-SITE, start JNET_JOBLOG in JAN_ROOT:[SYS]JANSITE.COM (warm start) | |
| -JNET-I-CMD, $ START/QUEUE JNET_JOBLOG | |
| %JNET-I-SITE, stop JNET_JOBLOG in JAN_ROOT:[SYS]JANSITESTOP.COM (shut down) | |
| -JNET-I-CMD, $ STOP/QUEUE/NEXT JNET_JOBLOG | |
| Will there be any network print servers [YES]? | |
| Enter the NJE name of the printer server [PRT]: | |
| Enter the name of the print queue serving PRT [SYS$PRINT]: | |
| Is there another network print server [NO]? | |
| Will any remote NJE printers be served by local queues [NO]? | |
| Will there be any NJE links over DECnet [YES]? | |
| Enter the NJE node name of the linked system [RED]: QCOCAL | |
| Enter the DECnet node name of the linked system [QCOCAL]: | |
| Enter the DECnet link driver [DNANJE]: | |
| Is there another NJE link over DECnet [NO]? | |
| Will there be any NJE links over TCP/IP [YES]? NO | |
| Should ENQUE and ENCASE be moved to SYS$SYSTEM [YES]? | |
| %PURGE-I-NOFILPURG, no files purged | |
| %BACKUP-S-CREATED, created SYS$COMMON:[SYSEXE]ENQUE.EXE;1 | |
| %BACKUP-I-STARTDELETE, starting file deletion pass | |
| %BACKUP-S-CREATED, created SYS$COMMON:[SYSEXE]ENCASE.EXE;1 | |
| %BACKUP-I-STARTDELETE, starting file deletion pass | |
| %JNET-I-ROUTEFILE, define any routes in JAN_ROOT:[SYS]JANROUTES.JCP | |
| $ | |
| $ | |
| $ ! NEED TO ADD THESE TO SYSTEM STARTUP COMMAND FILE: | |
| $ ! $ DEFINE/SYSTEM/EXEC JAN_DEVICE DUA1: | |
| $ ! $ @JAN_DEVICE:[JANCOMMON.SYS]JANSTART | |
| $ | |
| $ | |
| $ | |
| $ | |
| $ DIR SYS$MANAGER:*STARTUP*.COM | |
| Directory SYS$SYSROOT:[SYSMGR] | |
| IP_STARTUP.COM;1 LPD_STARTUP.COM;1 LPR_STARTUP.COM;1 MAILSMB_STARTUP.COM;1 | |
| SYSTARTUP.COM;16 | |
| Total of 5 files. | |
| Directory SYS$COMMON:[SYSMGR] | |
| SYSTARTUP.COM;1 | |
| Total of 1 file. | |
| Grand total of 2 directories, 6 files. | |
| $ EDIT SYS$MANAGER:SYSTARTUP.COM | |
| 1 $! This is an empty site-specific system startup procedure. | |
| *CHANGE | |
| ! | |
| ! ADD THE TWO LINES ABOVE, SAVE AND EXIT EDITOR | |
| ! | |
| $ @JAN_DEVICE:[JANCOMMON.SYS]JANSTART | |
| %DCL-I-SUPERSEDE, previous value of JAN_JMAILPROT has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_MFSDISP has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_TMPROOT has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_TMPSPECIFIC has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_TMPCOMMON has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_SPOOL has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_LOG has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_TRACE has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_TMPSYS has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_RECEIVE has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_QUE has been superseded | |
| %DCL-I-SUPERSEDE, previous value of JAN_JOB has been superseded | |
| %JCP-I-CREATE, Creating new Jnet database of 155 pages | |
| $ | |
| %%%%%%%%%%% OPCOM 8-APR-2020 03:20:11.97 %%%%%%%%%%% | |
| Message from user SYSTEM on XLVII | |
| (QCOCAL) - Signon of link XLVII complete, buffer size = 1000 | |
| $ lo | |
| Connection closed by foreign host. |
For JNET to automatically start at boot, add the following to the bottom of the system startup command file (SYS$MANAGER:SYCONFIG for VAX/VMS 4.7):
$ DEFINE/SYSTEM/EXEC JAN_DEVICE DUA1:
$ @JAN_DEVICE:[JANCOMMON.SYS]JANSTART
As far as configuring JNET is concerned, a few files in JAN_SYS: need to be edited:
1) JAN_SYS:JANLINKS.JCP
This defines the NJE links. In my case, I set up the local node XLVII and a NJE-over-DECnet (DNANJE) link to the next hop QCOCAL as follows.
create /nodes=114
define XLVII /host /daemon=DAE /timezone="GMT" /line=LOCAL
define JOB /link /daemon=JOB
define PRT /link /daemon=QUE
define QCOCAL /link /daemon=DNANJE /line=QCOCAL
Notes on /DEFAULT_ROUTE qualifier and .PAR files:
From JNET version 3.6 for later versions of OpenVMS, a "/DEFAULT_ROUTE" qualifier is available which causes JNET to use the link configured as default route for routing all nodes that are not explicitly defined in JAN_SYS:JANROUTE.JCP. The DEFAULT_ROUTE feature is absent in JNET 3.5.
Just for the sake of completeness of information in this post, if the link to QCOCAL were TCPNJE instead of DNANJE (as specified in JANLINKS.JCP with "define QCOCAL /link /daemon=TCPNJE /line=UCX"), I would have a JAN_SYS:QCOCAL.PAR file looking like this:
TCP.RMTNODE=10.42.2.5
TCP.RMTPORT=2252
TCP.LCLPORT=2254
OPRMSG=YES
BUFF=4096
and QCOCAL would have a .PAR file with IP address of XLVII and complementary listening and connecting port numbers (TCP.LCLPORT and TCP.RMTPORT respectively):
TCP.RMTNODE=10.42.2.31
TCP.RMTPORT=2254
TCP.LCLPORT=2252
OPRMSG=YES
BUFF=4096
While on the subject of .PAR files, here is my IRLEARN.PAR file from IMPVAX which runs OpenVMS VAX 7.3 and links to HNET via IRLEARN:
BUFF=3976
B2.VMNET_BUFF=8192
B2.TCP_BUFF=1024
TCP.LCLPORT=2253
TCP.RMTNODE=xx.xx.xx.xx
TCP.RMTPORT=175
STREAMS=1
And finally here is a JNET 3.6 PAR file template that I am thankful to Peter Coghlan for:
BUFF=3976
B2.VMNET_BUFF=8192
B2.TCP_BUFF=1024
TCP.LCLPORT=<local port to listen on>
TCP.RMTNODE=<remote ip address>
TCP.RMTPORT=<remote port to connect to>
STREAMS=1
TA=0
TP=THR=500
End of notes.
2) JAN_SYS:JANSTART.JCP
This lists the links that are to be started up at JNET startup. A .PAR is required for TCPNJE links. No .PAR is needed for DNANJE links.
start XLVII
start JOB
start PRT
start QCOCAL
3) JAN_SYS:JANROUTES.JCP
This is the routing table that tells JNET about the next hop to the target node (i.e. a directly linked node that knows how to reach the target node, either directly or via another hop). It consists of one line per route definition, like so:
DEFINE/ROUTE=QCOCAL CLOUDY
DEFINE/ROUTE=QCOCAL FEDACH
DEFINE/ROUTE=QCOCAL IMPVAX
DEFINE/ROUTE=QCOCAL MARIAH
DEFINE/ROUTE=QCOCAL NJEVX1
DEFINE/ROUTE=QCOCAL NJEVX2
DEFINE/ROUTE=QCOCAL TSTVAX
DEFINE/ROUTE=QCOCAL VAXSTN
Finally, once the other end of the TCPNJE link is configured, setup is complete. You can then issues commands and send files from the other node. For example, QCOCAL is the node on the other side for my experiment, and I can do this successfully from QCOCAL:
$ SEND/COMMAND XLVII "CPQ IND"
(XLVII) - VAX 8650 running VAX/VMS V4.7
(XLVII) - Up since 8-APR-2020 01:12
$
$ SEND/COMMAND XLVII "Q SYS"
$
(XLVII) - Link JOB Connect -- JOB Line virtual NOH NOD NOT
$
(XLVII) - Link PRT Connect -- QUE Line virtual NOH NOD NOT
$
(XLVII) - Link QCOCAL Connect -- DNANJE Line QCOCAL NOH NOD NOT
$
No comments:
Post a Comment
"SEO" link builders: move on, your spam link will not get posted.
Note: Only a member of this blog may post a comment.