info-vax@ucbvax.ARPA (02/09/85)
From: engvax!KVC@cit-vax Unfortunately, Mark is right about DECnet remote terminals not working with CONNECT/DISCONNECT. Uner VAX PSI V3, however (which is the version you will need to run PSI under VMS V4), the X.29 network terminals are implemented as a terminal port driver, and use TTDRIVER as the class driver. Thus, CONNECT/DISCONNECT works just fine. The only problem is that you will find it difficult setting /DISCONNECT on terminals that are created on the fly (like the PSI terminals). What I did was set the DISCONNECT bit in the SYSGEN parameter TTY_DEFCHAR2 (I think) that determines default terminal characteristics. My PSI terminals (_NVxx) now allow full CONNECT and DISCONNECT. It would be nice if the DECnet RT devices could use TTDRIVER, but I believe that the QIO to such devices is handled quite differently from what TTDRIVER does. I think some QIO's are decoded and then sent over the network to be handled by the driver on the other side. (PSI terminals handle the QIO locally, and then produce X.29 packets that go out through the PSI device). For this reason, I suspect DECnet terminals are always going to lag behind TTDRIVER. bummer drag.... /Kevin Carosso engvax!kvc @ CIT-VAX.ARPA Hughes Aircraft Co.