List of known bugs or problems with C-Kermit under VAX/VMS: Version: 4D(067) As of: 9:19am Tuesday, 27 October 1987 See CKUKER.BWR which lists problems with Unix Kermit. Many of these problems may also apply to VMS C-Kermit. This file lists only those that are unique to VMS C-Kermit. Recent checkout of 4D(067) on a VAX/VMS 4.3 system gives the following results: - The commands mostly seem to work -- help, log, set, show, etc etc. - The basic file transfer and server commands seem to work OK with a couple exceptions: "remote cwd" makes the VMS C-Kermit server respond with a wierd message. Text and binary files transfer OK with regular and long packets, with CRC's, etc etc, except that when VMS sends a foreign binary file back to you, it's padded out to the nearest block with nulls. - Caution is needed with the "!" command. If it requires a response, the program will hang silently. E.g. if you say "! delete foo.x;*" instead of "! delete/noconfirm foo.x;*". - C-Kermit on VMS doesn't accept command line arguments (maybe there's a way to tell DCL to pass them?). - The program doesn't seem to work when parity is involved, even if you "set term/parity=odd" or whatever. The command parser goes catatonic, and files don't seem to transfer either. - The command parser is totally screwy if you enter the VMS system via CTERM (DECnet terminal service from a DEC-20) -- characters echo twice, editing characters don't work, etc. All this works fine if you enter via a regular terminal line. Don't know what happens over LAT, or SET HOST between VMS systems, etc. - ^C^C during file transfer doesn't interrupt the program. Is VMS swallowing them? General problems: - The fact that VMS C-Kermit is built with CKU* files as well as CKC* and CKV* files is confusing. Well... It's that way because VAX-11 C does its best to provide a Unix programming environment -- to the extent it succeeds, VMX C-Kermit can use certain Unix-specific modules. - VMS C-Kermit, unlike Bliss Kermit, is NOT interruptible, either with ^C or ^Y. The latter can be interrupted by two (?) ^Ys. This is a serious shortcoming. (There is code whose intention is make the program interruptible, but it apparently does not work.) - VMS C-Kermit is less efficient than Bliss Kermit, and may require the use of lower baud rates when sending TO it. - If using LAT (Local Area Transport) terminal connections, you may need to use a lower baud rate when transferring from your "terminal" to the host, or a smaller send-packet length. Some LAT software doesn't expect "fast typing" from the terminal direction (applies mainly to old F11-based LAT boxes; newer DECserver-100s and -200s reportedly work fine with Kermit, if set up with the right parameters). - VMS VAX-11 C V2 allows DEFINEs by a command line qualifer, and CKVKER.COM makes use of this to include debugging and transaction logging code if it believes that VAX-C V2 is being used. VAX-C V1 had no such feature. If you want the DEBUG and TLOG symbols defined for use with VAX-C V1, modify the CKCDEB.H file. - The local "directory" command defaults to * rather than *.*. - Execution of local commands (C-Kermit>! ): The problem with "! XXX" in VMS is related to the BYTLM in user authorization file. For VMS to create a subprocess, the BYTLM must exceed 4096 (which is our previous setting), and of course, PRCLM must be at least 1. 6144 seems to work for BYTLM. Here's some material dealing with older releases, which may still apply: ------------------------------ Date: Fri, 16 Jan 87 14:34:01 pst From: ames!styx!elxsi!gumby.ARPA!valid!carolf@cad.Berkeley.EDU To: CU20B.COLUMBIA.EDU!SY.FDC I've begun to test c-kermit 4D(061) between the S-320 and the MicroVAX, running VAX version 2.1, and the VAX-11/780 running VMS 4.4. I compiled c-kermit on VMS using the CKVKER.COM DCL procedure. I've found the following problems: ----------------------------------------------------------------------------- S-320 -> MicroVAX and VAX-11/780 ----------------------------------------------------------------------------- * Bye doesn't work When running kermit from VMS in server mode, type bye, then connect. Kermit will connect to the VMS command interpreter rather than logging out of the server. At this point, type logout (which doesn't echo on the screen) * Exit doesn't always work (MicroVAX only) Sometimes no action will be taken in response to exit. Quit always works however. ----------------------------------------------------------------------------- MicroVAX and VAX-11/780 -> S-320 ----------------------------------------------------------------------------- * Directory doesn't work on VMS Directory listed only some of the files in a directory containing several files. Problem is that "dir" defaults to "." rather than "*.*". This can be fixed in ckuusr.c. * On the VAX, kermit's output overwrites the prompt and command on the previous line. * Remote directory on the VAX could not list UNIX files whose format was not correct VMS format. c-kermit(VAX-11/780)> remote directory c-kermit(VAX-11/780)> - ttini: ttiosb.status: %SYSTEM-W-DATAOVERUN, data overrun (for all filenames too long) UUCP address: ucbvax!hplabs!pesnta!valid!carolf Carol Fernihough ------------------------------ Date: 17 Sep 87 12:23:00 MST From: Subject: 4E C_Kermit on VAX/VMS I've just downloaded the newest XK* versions to VAX VMS 4.5. It compiled without a hitch, using the XKVKER.COM. It even transferred a file OK. However, there are a couple of problems: - The show command produces a lot of unprintable characters in the header lines of the table ("send" and "receive"), after which several of the lines contain gibberish. After the SHOW, things go back to normal (except see below) - After many commands are executed, and the C_Kermit> prompt shows, typing another command responds with ?invalid - xxx. Typing an erase-line character (CTRL-U on VMS) before doing anything else will erase 3 characters of the prompt, indicating that three charac- ters must have been received by VMS from the terminal(?) I can easily get around this problem by habitually typing command...but who wants to? Is it possible that I need to SET TERMINAL to something different before executing Kermit? Or are there indeed spurious characters being sent by C_Kermit? At any rate, this version works OK, but the BLISS version is the system standard here. Declan A. Rieb, Division 2614 DARIEB@SANDIA-2.ARPA Sandia National Laboratories (505) 844-6338 Albuquerque, NM 87185-5800 ------------------------------ Date: Thu 17 Sep 87 15:48:24-EDT From: Frank da Cruz Subject: Re: 4E C_Kermit on VAX/VMS To: darieb@SANDIA-2.ARPA How are you connected to the VMS system? Normal TTY line? Or some kind of terminal server or SET HOST, etc? I tried both ways (on a VMS 4.3 system) and found that the screen looked fine with a regular TTY line, and there were all kinds of garble, character doubling, prompt-erasing, etc, when I came in thru a network. Can you give more details about your connection, the VMS version, and maybe do a SHOW TERM? Thanks! - Frank ------------------------------ Date: 17 Sep 87 15:17:00 MST From: Subject: Re: 4E C_Kermit on VAX/VMS Boy, was that a quick reply!!!! We're running VMS 4.5. I'm running an IBM PC/XT at 9600 Baud using the VTERM 4010 Version 2.0 software from Coefficient Systems Corporation, which supplies a pretty good VT102 emulation. Connection is through COM1: to a Gandalf LDS120 line driver, into a Gandalf (I think) port contender device, thence to a VAX 8600. No other DECNET. The BLISS version of KERMIT works OK. (My connection to the CDC VX/VE which runs this KERMIT OK was through identically the same topology, except for the final step...) Using the PC, I was able to copy what happened onto disk. I am forwarding it to you below. The funny characters, which show in VMS EDT as <+->, showed on my PC screen as pillows. Kermit's normal output seems to be interspersed between these. The gibberish starts after the packet length data. After executing the SHOW, I immediately tried two STAT's. The first worked, the second didn't. It's the second which I can cure by prepending the line- cancel character . None of this happens, using the same terminal/ parameters, when using the BLISS Kermit, nor, I believe, the previous version of C_Kermit. The following is what I saw and did using KERMIT: C-Kermit>show C-Kermit, 4E(066) 4 Aug 87, Vax/VMS, Communications Parameters: 1 1L1i1n1e1:1 1T1T1:1,1 1s1p1e1e1d1:1 1-111,1 1m1o1d1e1:1 1r1e1m1o1t1e1,1 1m1o1d 1e1m1-1d1i1a1l1e1r1:1 1d1i1r1e1c1t1 1 1B1i1t1s1:1 181,1 1p1a1r1i1t1y1:1 none, duplex: full, flow: xon/xoff, handsha ke: none Terminal emulation: 7 bits Protocol Parameters: Send Receive Timeout: 10 7 Padding: 0 0 Block Check: 1 Pad Character: 0 0 Delay: 5 Packet Start: 1 1 Max Retries: 10 Packet End: 13 13 Packet Length: 90 90 Krti l riii akLg sa:n astoLg o ?Invalid - C-Kermit>stat Most recent transaction -- files: 0 total file characters : 0 communication line in : 0 communication line out : 0 elapsed time : 0 sec C-Kermit>stat ?Invalid - stat C-Kermit>exit $ show terminal Terminal: _VTA665: Device_Type: VT102 Owner: Declan Rieb Physical terminal: _TXB1: Username: DARIEB Input: 9600 LFfill: 0 Width: 80 Parity: None Output: 9600 CRfill: 5 Page: 24 Terminal Characteristics: Interactive Echo Type_ahead No Escape Hostsync TTsync Lowercase Tab Wrap Scope Remote No Eightbit Broadcast No Readsync No Form Fulldup Modem No Local_echo Autobaud Hangup No Brdcstmbx DMA Altypeahd Set_speed Line Editing Overstrike editing No Fallback Dialup No Secure server Disconnect No Pasthru No Syspassword No SIXEL Graphics No Soft Characters Printer port Numeric Keypad ANSI_CRT No Regis No Block_mode Advanced_video Edit_mode DEC_CRT No DEC_CRT2 Declan A. Rieb DARIEB@SANDIA-2.ARPA Division 2614 (505) 844-6338 Sandia National Laboratories Albuquerque NM 87185-5800 ------------------------------ Date: 17 SEP 1987 15:57 EDT From: Steve Roseman Subject: C-Kermit 4E(067) on VAX/VMS Running C-Kermit 4E(067) under VMS V4.5 seems to work so far, with 3 problems. 1. The user needs a BYTLM quota of at least 5000 to execute a "! xxx" command, "DIR", or "SPACE". Otherwise the job just hangs up. 2. With a sufficient BYTLM, the above work, but if any are done, C-Kermit leaves behind a subprocess when it exits. Re-entering C-Kermit and executing any of the above starts up (and then leaves behind again) another subprocess. Repeat until your job hangs up. 3. A "! LOGOUT" command kills the subprocess in which it executes; another "! xxx" command just hangs, since C-Kermit doesn't seem to know it's gone. Fairly minor problems, but file transfers run well with 1000 char packets. Steve Roseman Lehigh Univ. ------------------------------ Date: 19 Oct 87 10:49:00 EDT From: "ETD1::LABOVITZ" Subject: VMS 4.6 Bug Report with C-Kermit 4E(067) Keywords: VAX/VMS Kermit, C-Kermit I have just compiled the source modules for C-Kermit 4E(067) under VAX/VMS 4.6 on our VAX 11/785, using the supplied XMVKER.COM file. During the final link of the KERMIT executable, the following warning message is produced by the linker: %LINK-W-MULDEF, symbol SYSTEM multiply defined in module C$UNIX file SYS$COMMON:[SYSLIB]VAXCRTL.OLB;1 While I have not had a chance to confirm this with our DEC Software Analyst (he's on vacation until next week), this seems to be directly attributable to the new VMS 4.6 C Run Time Library. Other than producing a warning message, however, our new version of KERMIT seems to be running well thus far. If any other problems arise, I will forward them to Info-Kermit, otherwise it will soon replace our current version of KERMIT-32. LT Stuart Labovitz arpa: LabovitzSL@Afwal-aaa.ARPA arpa: Labovitz%Etd1.DECNET@Afwal-aaa.ARPA ------------------------------ From: schullman%aqua.DEC@decwrl.dec.com (Dan Schullman * {617-46,29}7-4576 * MRO1-2/E47) Date: 27 Oct 87 09:43 Subject: VMS Kermit Frank, How you been? I recently had need for KERMIT (after not using it for over a year), then I end up helping somebody else in my group with it, and then I get some internet mail about it! When it rains it pours [frogs]! Anything going on with the C version of KERMIT? I haven't checked, but believe it does not support the "new" VMS V4 file names and types which may be much longer and also contain hyphens and dollar- signs and underscores. Also thinking it might make more sense to use a VMS logical for the init file. If you "speak" DCL, it would be something like: IF F$TRNLNM("KERMRC") .EQS. " " THEN GOTO IGNORE_INIT_FILE I_SPEC = F$PARSE("KERMRC","SYS$DISK:[].INI",,,"SYNTAX_ONLY") IF I_SPEC .EQS. "" THEN GOTO IGNORE_BAD_INIT_SPEC I_FILE = F$SEARCH(I_SPEC) IF I_FILE .NES. "" THEN GOTO FOUND_INIT_FILE I_SPEC = F$PARSE("KERMRC","SYS$LOGIN:.INI",,,"SYNTAX_ONLY") IF I_SPEC .EQS. "" THEN GOTO IGNORE_BAD_INIT_SPEC I_FILE = F$SEARCH(I_SPEC) IF I_FILE .NES. "" THEN GOTO FOUND_INIT_FILE GOTO INIT_FILE_NOT_FOUND This would allow: KERMRC to be a VMS logical that pointed at an init file: DEFINE KERMRC SYS$LOGIN:TTA3_AT_2400_BAUD.KINIT System (or group) defaults for init files (with user-defined logical having precedence): DEFINE/SYSTEM KERMRC ... DEFINE/GROUP KERMRC ... Ability to ignore system/group/job/process predefined logicals: DEFINE KERMRC " " !a single space In the absence of KERMRC logical, look first for KERMRC.INI in current directory and if that doesn't exist look for it in SYS$LOGIN. If KERMRC is not a full file spec, supply defaults of SYS$DISK:[]KERMRC.INI (first try) SYS$LOGIN:KERMRC.INI (second try) For example: DEFINE KERMRC COLUMBIA would try: SYS$DISK:[]COLUMBIA.INI (first attempt) SYS$LOGIN:COLUMBIA.INI (second attempt) but DEFINE KERMRC KERMIT$DIR:.2400 would only try (because directory was specified): KERMIT$DIR:KERMRC.2400 You sufficiently confused now? Unfortunately it would NOT be backwards compatible with the old name of KERMIT.INI, but I feel it would be more more useful. The current code also looks first in SYS$LOGIN rather than the current directory. The "new" approach could allow directory-specific init (e.g., file-type). You could take the DCL code above, add the necessary labels and have them display the spec and resulting file, and try it. For example: $TRY_ANOTHER: $ READ SYS$COMMAND VALUE /PROMPT="Value for KERMRC: " $ DEFINE/NOLOG KERMRC "''VALUE'" $ IF VALUE .EQS. "-" THEN DEASSIGN KERMRC $! $! put code from above in here, prefixed with "$" $! $IGNORE_INIT_FILE: $ WRITE SYS$OUTPUT "No init file will be used." $ GOTO TRY_ANOTHER $IGNORE_BAD_INIT_SPEC: $ WRITE SYS$OUTPUT "Bad spec (",I_SPEC,") ignored." $ GOTO TRY_ANOTHER $FOUND_INIT_FILE: $ WRITE SYS$OUTPUT "Spec: ",I_SPEC," File: ",I_FILE $ GOTO TRY_ANOTHER $etc... Comments? Suggestions? I don't know how soon I'd get these changes made. Between family, house, and work I'm pretty busy! Be well, Dan S. ------------------------------ Date: Tue, 10 Nov 87 14:44 CST From: Subject: RE: VMS 4.6 Bug Report with C-Kermit 4E(067) Keywords: C-Kermit, VMS Kermit > Date: 19 Oct 87 10:49:00 EDT > From: "ETD1::LABOVITZ" > Subject: VMS 4.6 Bug Report with C-Kermit 4E(067) > > I have just compiled the source modules for C-Kermit 4E(067) under VAX/VMS > 4.6 on our VAX 11/785, using the supplied XMVKER.COM file. During the > final link of the KERMIT executable, the following warning message is > produced by the linker: > > %LINK-W-MULDEF, symbol SYSTEM multiply defined > in module C$UNIX file SYS$COMMON:[SYSLIB]VAXCRTL.OLB;1 > > While I have not had a chance to confirm this with our DEC Software Analyst > (he's on vacation until next week), this seems to be directly attributable > to the new VMS 4.6 C Run Time Library. > > [Ed. - Thanks for the report. It's been forwarded to the new C-Kermit/VMS > developer and added to the XKVKER.BWR file. Since compilation and linking > were tested with VAX-11 C 2.3 on VMS 4.6, and this problem didn't arise, > the culprit is indeed most likely the runtime system.] Was C-Kermit/VMS really tested under VMS V4.6? Before VMS V4.6, there was no `system' function in the VAX C runtime library. Starting with VMS V4.6, Digital provides a `system' function. The error message basically indicates that the linker was provided with two routines named `system'. It sounds like the developer of C-Kermit/VMS implemented `system' in the code, and that it now conflicts with the new V4.6 standard `system'. It should be straightforward for VMS V4.6 users to remove the definition of `system' from the C-Kermit/VMS code and recompile/relink. Perhaps the developer can find some nifty way to define `system' conditionally depending upon which VMS version is being used. Ed ------------------------------