<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr">Problem solved.</div><div dir="ltr"><br></div><div dir="ltr">I found a missing driver executable.</div><div dir="ltr"><br></div><div dir="ltr">Cheers, John</div><div dir="ltr"><br><blockquote type="cite">On 27/08/2020, at 16:07, JY@xtra.co.nz wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta charset="UTF-8">
<p>Hi all,</p><p>I'm working on a connection from an OpenVMS 7.3 emulation currently running DECnet and MultiNet, to the HNET using JNET 3.6.</p><p>I'm stuck with the following after starting JNET:</p><p>$ @JAN_DEVICE:[JANCOMMON.SYS]JANSTART<br>%JCP-I-CREATE, Creating new Jnet database of 159 pages<br>$<br>%%%%%%%%%%% OPCOM 27-AUG-2020 15:52:14.00 %%%%%%%%%%%<br>Message from user SYSTEM on GLOVER<br>Jnet status message from link NZVAX001<br>Unexpected Jnet daemon termination for link: Unknown:<br>%RMS-E-FNF, file not found</p><p>And JNET isn't attempting to open a TCP connect to the HNET peer. The JENT install went OK and I've carefully cross checked my config files with Supratim who has been very helpful.</p><p>I appreciate this is a bit off topic for this reflector so if anyone has experience with JNET and time to help, I'd appreciate a contact off list. My email is <a href="mailto:jy@xtra.co.nz">jy@xtra.co.nz</a></p><p>Thanks, John</p>
</div></blockquote></body></html>