accuncg@ecsvax.UUCP (Ted Hildebrandt) (04/29/85)
We have the following minor problem with KERMIT-32 operating under VAX/VMS 4.1: For the present we have one VAX operating under VMS 4.1 and another under VMS 3.7 and we are using Kermit to transmit files between the two systems. The Kermit operating under VMS 3.7 in VAX-1 communicates perfectly with the Kermit operating under VMS 4.1 in VAX-2. However, when VAX-2 initi- ates the connection it reports error messages. For example: From VAX-2 (4.1) we command Kermit in VAX-1 (3.7) to act as SERVER, then command GET filename. The transfer is carried out cor- rectly and the report [OK] is displayed. Next the following message: %KERMIT32-F-BADPARAM, bad parameter value We then command FINISH, and the same report is displayed. We CONNECT to VAX-1 and receive the following partial message: iguous verb [sic] \L\ E%KERMIT32-F-BADPARAM, bad parameter valueQ [sic] We then logout of VAX-1 and return to Kermit in VAX-2. Following the message [SYS$NODEReturning to VAX/VMS KERMIT-32] the "BADPARAM" message is displayed twice, and then the "KERMIT-32>" prompt reappears. The problem is not serious, since the file transfer itself and the behavior of the Kermit on VAX-1 under VMS 3.7 is perfect. However, the frequent appearance of the BADPARAM message is annoying to the experienced user and disconcerting to the novice. Has anyone else observed this behavior? Does anyone have a fix? T. W. Hildebrandt Academic Computer Center UNC-Greensboro Greensboro, NC 27412 919-379-5350