CMS Kermit 4.3.x "Beware File" - Known Bugs, Problems, Limitations. As of: 15:25 Tuesday, 1997 Nov 4 This file contains (A) instructions for applying Kermit updates, (B) a list of unresolved problems, (C) a list of problems with work-arounds or optional fixes, and (D) a list of resolved problems. NOTE: entries will sometimes be entered under (D) even though the needed updates have not been released in IKCKER.UPD. Please check the date of the UPD and NUP files to see if they have been changed before requesting new copies. Bug reports may be sent to John Chandler . Kermit-370 carries an "edit" number in addition to the version and release numbers. The three numbers together are printed out in the assembly listing and displayed by Kermit at startup time. Be sure to include all three numbers (e.g., 4.3.0) along with any error reports. A) Update instructions ................................................. Many updates have been received since Kermit-370 4.2 was released. All updates prior to 93/9/30 have been removed from IKCKER.UPD and applied to the sources in the process of creating 4.3. If your source does not include the line defining &KVRSN to be 4.3, you should obtain an all-new source distribution from Columbia. Any updates created later than your source should be applied before you make the executable module. In general, updates received at Columbia will not be included in the source files in the CMS Kermit distribution until and unless "major" bugs are uncovered, and then all accumulated updates will be applied at once. The description of each problem and a pointer to its solution will always be included in IKCKER.BWR (the present file), but the updates themselves are to be found in IKCKER.UPD or IKCXA.UPD. The latter file contains the updates related to VM/XA or VM/ESA. The procedure to update your copy of CMS Kermit is as follows: 1) Obtain the latest version of IKCKER.UPD, which contains all the updates, each preceded by a separator beginning ":READ" and giving the update's name. Please note that some modes of file transport have a side effect of either doubling or removing any periods in the first column -- if your copy of IKCKER.UPD has records beginning with "/", then all instances of "/" in column 1 should be changed to "./". Similarly, any instances of ".." in columns 1-2 should be changed to just ".". A related problem can affect the sources by leaving a blank in column 80. That can happen via the loss of a "." in column 1 (in which case the sequence number will be shifted into columns 72-79) or via automated efforts to preserve the "." (in which case the sequence number will be truncated). The repair consists of inserting the missing "." in column 1 or "0" in column 80. Also, obtain IKCXA.UPD if you wish the VM/XA or VM/ESA version. 2) Determine the date of your sources. If you obtained the source from Columbia, the date is the value of the &KDATE variable symbol in the source itself, i.e., the release date of the current base version. If you received the source distribution from a secondary supplier, you will need to examine the code to determine the most recent update applied. Just sort the combined source by columns 67-71, e.g., using :1 SORT * A 67 71 in XEDIT; the last line will be labeled with the last-applied update. 3) If your sources are "pure" Columbia 4.3, go on to step 4. Otherwise, you must take care to avoid applying updates that are already in the source. If it is inconvenient to obtain "pure" sources, you must go through the list of updates (the "AUX" file) at the beginning of IKCKER.UPD (arranged in reverse chronological order) and note which ones are already included in (i.e., are older than) your sources. Disable each such redundant update by inserting an asterisk in column one of the relevant line in the AUX file. If you wish, you may also discard the update itself by deleting the lines from the corresponding :READ up to (but not including) the next :READ. 4) Separate the updates into individual files. This operation is done automatically when you run IKCINS EXEC (included in IKCKER INS). 5) Extract any desired optional updates from IKCKER.BWR (this file) and insert their names into KERMIT AUXOPT, which is reserved for such optional, local updates. The first line of each update, if stripped of the leading "./ * ", will serve as a useful entry in an AUX file. If you have local modifications specific to your site, these should also be listed in KERMIT AUXOPT. NOTE: all updates in this BWR file are indented one column to avoid all the transmission problems mentioned above in step 1. Be sure to shift everything over when you extract the updates. You may bundle the updates together with the AUXOPT into a single file called KERMIT LOCAL (for ease of keeping track) in the same format as IKCKER UPD. When you run IKCINS EXEC, it will automatically split the local updates into the individual files and apply them. 6) Apply the updates to your composite source. This is automatically done by IKCINS EXEC. You may, instead, do it by hand via one of: a) UPDATE KERMIT (CTL b) UPDATE KERMIT ASSEMBLE A KERMCMS6 (CTL c) UPDATE KERMIT ASSEMBLE A KERMXA (CTL d) UPDATE KERMIT ASSEMBLE A KERMXA21 (CTL e) UPDATE KERMIT ASSEMBLE A KERMESA (CTL The resulting file, $KERMIT ASSEMBLE A, represents the latest source, but you should archive the original components IK*.ASM until a new release comes from Columbia. ------------------------------------------------------------------------ B) Unresolved problems/warnings ........................................ ---------------- 89/1/20 ----------------------------------------------- Now that Kermit-370 supports multiple-filespec SEND, it is possible for a single SEND subcommand to specify overlapping wildcard filespecs. Only the CMS variant keeps track and makes sure that it doesn't send the same file twice within one SEND invocation. Indeed, with CMS Kermit-370 it is possible to get a mysterious "file not found" message simply because all the files matching the filespec in question had already been sent in the same invocation. A related limitation applies to the new send-by-line-range option -- you cannot send several different pieces of the same file by one SEND subcommand, since the duplicate-suppression logic pays no attention to line ranges actually sent. ---------------- 90/5/8 ------------------------------------------------ With a few exceptions, CONTROLLER will be set automatically when Kermit is invoked. See file IK0AAA.HLP in the Kermit distribution for a list of front ends that have been reported to allow Kermit file transfers and another list of reported failures. ---------------- 91/8/16 ----------------------------------------------- The type-out interception mechanism for server mode works only for "normal" line-oriented output, not for fullscreen applications. Indeed, since there is no mechanism provided for feeding subcommands to a program on the mainframe through the Kermit server, only one-shot, non- interactive commands should be issued via REMOTE HOST. ---------------- 92/10/13 ---------------------------------------------- Like all variants of Kermit-370, Kermit-CMS does not support mixed-case file ids. Starting at CMS Rel 4, there has been partial support in CMS for mixed-case ids via the CMS SET INPUT command, but Kermit ignores the SET INPUT translations, if any. ------------------------------------------------------------------------ C) Problems with workarounds or optional fixes ......................... ---------------- 87/7/2 ------------------------------------------------ Subject: Using KERMIT with an IBM 3708 and VCNA In protocol conversion mode on the 3708, you can use Kermit FULLSCREEN mode for file transfer (see below). However, in protocol enveloping mode, you must go through 6 separate steps to get things working. Briefly, they are as follows: 1) Apply IBM APAR DY30352 to bypass VCNA translation tables. 2) Apply IBM APAR II01192 to increase the length of a 'line' for a TWX- type terminal to 80 bytes instead of 72 bytes. 3) Set the packet length on both sides of KERMIT to 80 bytes. 4) Change DTIPDODR source code for VCNA to skip the addition of a 'CRLF' on the front of any line beginning with 02 (CNTRL B). 5) Require that both sides of the link use 02 (CNTRL B) as the start- of-packet character. This is because the 3708 interprets the normal start-of-packet character (CNTRL A) as an attention signal. 6) Use the alternate translate table provided on the 3708, which allows for more accurate transmission of some control characters. ---------------- 87/8/9 ------------------------------------------------ CMS Kermit issues its default prompt by means of the PROMPT option of the CMS TYPLIN function. In so doing, it subjects the prompt buffer to translation via the user's current CMS SET OUTPUT tables such that the changes persist. It is wise to avoid using characters subject to OUTPUT translation in the Kermit prompt. ---------------- 89/2/27 ----------------------------------------------- The code for detecting the difference between SERIES1- and GRAPHICS-type terminal controllers may cause peculiar error messages at session startup, particularly if you try to run Kermit on an IBM 3270-type terminal. Typically, you would see a PROG470 error, but PROG755 is also possible on SDLC/DFT connections. Normally, Kermit can recover from these error conditions, but some configurations and/or versions of VTAM may hang the terminal session instead. For example, there may be an error message IKT00405I SCREEN ERASURE CAUSED BY ERROR RECOVERY from VTAM that never goes away. If you cannot persuade VTAM to be more sensible, you might want to bypass the code (especially if you don't have any GRAPHICS-type terminals). The code is governed by a set of switches which can be tailored to your needs: STCQBIT EQU X'01' WSF Query is always allowed STCQNS1 EQU X'02' WSF Q implies *not* SERIES1 STCS1 EQU X'04' Always assume SERIES1 STCNOS1 EQU X'08' Always assume *not* SERIES1 STCNORD EQU X'10' Asynch READ MOD is forbidden The standard flag value on CMS is STCQNS1; if you wish to force the code to select SERIES1, you should change that to STCS1, as in the following: ./ * SC9131X - Customize controller type selection ./ R 01085200 $ 1085200 100 11/21/91 00:16:50 &CONOPTS SETC 'STCS1' SETCON options @SC9131X Alternatively, if you have *only* GRAPHICS-type controllers, you could change it to STCNOS1. ---------------- 89/7/15 ----------------------------------------------- The CMS/XA Kermit source can't be assembled with the F or VS assemblers, which lack the new XA-mode machine instructions. The H assembler will do. ---------------- 90/6/12 ----------------------------------------------- Speaking of assemblers... Under VM/SP 6 (or thereabout), the STAX macro was imported from MVS to VM's OSMACRO MACLIB with the purely nuisance changes that are incompatible with the VS assembler, and IBM has refused to fix the problem. Moreover, the version of STAX in TSOMAC MACLIB is incompatible with the H assembler. Thus, if you switch assemblers, you must also switch the order of MACLIB's. ---------------- 90/7/5 ------------------------------------------------ Kermit-370 now honors the file type specification (binary or text) given by a sending Kermit in an Attribute packet. Old procedures for sending binary files may therefore not work properly anymore. To return to the old mode of operation, issue the subcommand SET ATTR TYPE OFF. To live with the new mode, be sure to issue the SET FILE TYPE to both sending and receiving Kermits (to be safe). ---------------- 90/7/30 ----------------------------------------------- When the file type is TEXT and the recfm is F, Kermit-370 strips off trailing blanks from each record before sending a file. In order to keep trailing blanks in a downloaded file, you can convert it to RECFM V in CMS before sending it, e.g., by using COPYFILE with the RECFM V option. This is true of versions from 4.1 onward. ---------------- 90/8/22 ----------------------------------------------- If, for some reason, the other Kermit insists on pretending ASCII bytes all have the 8th bit set, Kermit-370 will not detect the intended CRLF separators between lines. The result of uploading from such a Kermit is a (text) file with only one record. If the other Kermit cannot be fixed, the following update will make Kermit-370 treat ASCII 8D and 8A the same as 0D and 0A, as long as the ATOE table does so. ./ * SC90151 - Forgive 7-bit ASCII files with 8th bit on ./ I 02490500 $ 2490700 200 08/03/90 16:06:46 ISW78 DC X'7F' Start with 7-bit ASCII @SC90151 ./ I 02713500 $ 2713700 200 08/03/90 16:06:46 SW78 DS X'7F' Switch for 7-bit/8-bit ASCII @SC90151 ./ I 03347500 $ 3347700 200 08/03/90 ->4.3<- KCALL TBLCRLF Note current treatment @SC90151 ./ I 03350500 $ 3350700 200 08/03/90 ->4.3<- KCALL TBLCRLF Note current treatment @SC90151 ./ I 04016000 $ 4016200 200 08/03/90 ->4.3<- KCALL TBLCRLF Reset 7-bit/8-bit mask for CRLF @SC90151 ./ I 04063000 $ 4063040 40 08/03/90 ->4.3<- * * Entry: nothing special @SC90151 * Exit: SW78 set up correctly @SC90151 TBLCRLF ENTER ALT @SC90151 MVI SW78,255 Assume 8-bit codes @SC90151 CLC ATOE+ALF(1),ATOE+ALF+128 @SC90151 BNE RTRN0 @SC90151 CLC ATOE+CR(1),ATOE+CR+128 @SC90151 BNE RTRN0 @SC90151 MVI SW78,127 No, 7-bit codes @SC90151 B RTRN0 @SC90151 ./ I 08391000 $ 8391200 200 08/03/90 ->4.3<- NC CUR,SW78 If 7-bit ASCII, ignore 8th bit @SC90151 ---------------- 91/11/21 ---------------------------------------------- In order to change the default Kanji encoding from IBM-style to another, add one of the following updates. ./ * SC9132X - Change Kanji default ./ R 01416000 $ 1416000 10 11/21/91 ->4.3<- &KNJDEF SETC 'HITACHI' Default Kanji @SC9132X ./ * SC9132X - Change Kanji default ./ R 01416000 $ 1416000 10 11/21/91 ->4.3<- &KNJDEF SETC 'FUJITSU' Default Kanji @SC9132X ---------------- 92/4/10 ----------------------------------------------- The minimum size of strings to be subjected to run-length encoding may need to be changed to two to make the new FULLSCREEN mode work on certain protocol converters, such as the MICOM 7400, which convert three successive blanks into cursor motion commands (or even two!). The following update accomplishes that. ./ * SC92101 - Encode multiple blanks ./ I 08296500 $ 8296550 50 04/10/92 ->4.3<- CLI 0(8),ABL Is it a blank? @SC92101 BNE ENCRP1 No, use normal criterion @SC92101 C 14,F2 @SC92101 BNL ENCRP2 Always encode multiple blanks @SC92101 ENCRP1 DS 0H @SC92101 ./ I 08297500 $ 8297700 200 04/10/92 ->4.3<- ENCRP2 DS 0H @SC92101 ---------------- 92/3/10 ----------------------------------------------- Under VM/XA (and presumably under VM/ESA), a CP SLEEP no longer ends if the user enters data and then presses ENTER. Instead, CP treats the string as a command and issues an error message if the string is not a valid CP command (e.g., is a Kermit packet). For TTY and FULLSCREEN modes, then, the DELAY should be set to a small value to ensure that the micro Kermit never times out before Kermit-CMS can send the first packet. ---------------- 92/3/16 ----------------------------------------------- CMS Kermit includes conditional-assembly code that is necessary for working with the Shared File System that comes with CMS Releases 6 and higher. The code is normally suppressed because it cannot be assembled properly under pre-6 CMS. To enable the code, use KERMCMS6, KERMESA, or KERME370 CNTRL file for applying the updates, whichever is appropriate. This is done automatically using IKCINS EXEC. ---------------- 92/10/13 ---------------------------------------------- There is a bug in CMS Rel 7 and 8 affecting the CMS ERASE command when issued by typing the command at Kermit-CMS. The symptom is that the file id is taken by ERASE exactly "as is", with neither the normal up- casing done by Kermit nor the translation, if any, according to the CMS SET INPUT commands. The bug is listed by IBM as APAR VM48775, and the fix (to CMS) has been available since June of 1992. Alternatively, the following update may be applied to Kermit-CMS to avoid the problem. ./ * SC92244 - Bypass ERASE bug in VM/ESA (CMS) ./ R 05286000 $ 5286000 100 09/02/92 ->4.3<- ICPCMSX DS 0H @SC92244 AIF ('&KTAG' NE 'XA').CMSXA1B @SC92244 L 6,ASVCSECT Since we searched... @SC92244 DMSEXS OI,SVCCMDRS-SVCSECT(6),SVCCSRCH set search bit @SC92244 .CMSXA1B HOST 0(3),E=*+4,EPL=YES Accept errors, use ext.PL. @SC92244 ---------------- 92/10/18 ---------------------------------------------- When Kanji characters are first selected, the default for the single- byte character set is CP290 (hard-coded in Kermit-370). That can be changed, however: ./ * SC92252 - Make CP281 the default SBCS with KANJI ./ R 04118000 $ 4118000 100 10/18/91 ->4.3<- TBVJP DC CL(LALF)'CP281',CL(LALF)'CP500',CL(LALF)'CP290' @SC92252 ---------------- 92/11/10 ---------------------------------------------- In the IOCP gen on the ES9000, there is a SHARED option on the CNTLUNIT macro in the IOCP gen. It must be set to SHARED=YB for a 7171. ---------------- 93/9/20 ----------------------------------------------- When issuing the STOP command to get out of Kermit protocol mode, it may be necessary to hit the CLEAR EOL (not the CLEAR) key so that Kermit-370 will recognize the command. In general, if the word "stop" is echoed to the screen as you type it, and if there is already stuff on that same line, that previous stuff will be sent to the host when you hit ENTER. To prevent that, you must clear it without causing an interrupt, i.e., without using the CLEAR key. ---------------- 95/5/10 ----------------------------------------------- The automatic diagnosis of controller type may cause the session to hang on Sim3278, even when the latter nominally supports this feature. The following update avoids this problem. Better yet, SimWare now has a four-line fix for Sim3278/TCPIP to correct the problem once and for all. ./ * SC95130 - Avoid hangup on Sim3278 ./ R 04330000 $ 4330000 200 05/10/95 13:55:04 STCS1ORD DC &S1CMD1 @SC95130 ---------------- 97/1/17 ----------------------------------------------- Installing Kermit-CMS under CMS 7 with the 370 feature can be a problem because the old assembler cannot handle all the macros needed by Kermit. The simplest fix is to suppress support for SFS in this case. The following should replace KERME370 CNTRL TEXT MACS DMSOM DMSGPI OSMACRO TEXT AUXE370 TEXT AUXOPT TEXT AUXLCL ---------------- 97/11/4 ----------------------------------------------- One site has reported a problem with Kermit dying when closing a newly uploaded file, though the same module works fine at other sites. It is not known what causes this problem, but it appears to occur either all the time or never. If it occurs, it can be avoided by issuing the subcommand SET ATTR DATE OFF. ------------------------------------------------------------------------ D) Resolved problems ................................................... ---------------- 89/9/3 ------------------------------------------------ CMS Kermit works under VM/XA and VM/ESA. The set of updates to allow XA-mode or ESA-mode operation is available as a separate file called IKCXA.UPD (as a supplement to IKCKER.UPD). The XA-tolerant Kermit will still work correctly in 370 mode of CMS 5.5, 5.6, 7, or later, but will not work with earlier releases of CMS (because CMS did not then support SVC 204). ---------------- 90/5/8 ------------------------------------------------ A commonly reported "problem" is that Kermit-CMS objects to a send packet size greater than 94, and users wonder how to turn on long-packet protocol for downloads. The answer is that the the maximum packet size in Kermit protocol is always dictated by the receiving Kermit -- ALWAYS. NOTHING YOU CAN SAY TO A SENDING KERMIT WILL EVER MAKE IT SEND PACKETS LONGER THAN THE RECEIVING KERMIT ASKS FOR. Conversely, Kermit-CMS will always use packets as long as possible unless frequent transmission errors indicate a noisy communication line. The only purpose for the send packet-size parameter in Kermit-CMS is to set the default, in case the receiving Kermit is badly crippled (in which case, long packets are entirely out of the question anyway), or to control "raw" downloads (those without Kermit protocol and parameter negotiation). ---------------- 90/6/22 ----------------------------------------------- Kermit-370 supports file transfers through the IBM 3174 AEA with level 2 microcode in configuration B. The support is restricted to terminal types defined in the 3174 to have ASCII Graphics capability. That capability is available by default only for VT241 and Tektronix 4205 terminals, but user-defined terminal types are also possible. Also, the Graphics capability is allowed only for lines defined without associated Host Addressible Printers. Kermit-370 now automatically detects the B2 AEA and sets CONTROLLER accordingly (to AEA if Graphics is allowed, to NONE if not). However, if the 3174 is owned by VTAM, and the connection is made with a logmode that forbids the Read Partition Query (such as M2SDLCNQ), Kermit cannot detect the AEA and will default to CONTROLLER GRAPHICS (and, incidentally, cannot transfer files even with CONTROLLER set to AEA by hand). M2SDLCQ is known to allow correct operation, but other logmodes have not been tested. Since the 3174 supports full 8-bit communication, it may be useful to configure the ports for 8-bit data and to set both SEND and RECEIVE PARITY to NONE in Kermit-370. The fix: SC90173. Note: B2 microcode became available from IBM in May 1990. B3 followed soon afterward, and it supports file transfer the same way as B2. ---------------- 93/12/3 ----------------------------------------------- Kermit-CMS now uses the date/time stamp, if any, received along with a file (in preference for the date/time of reception). This new behavior can be suppressed by issuing a SET ATTRIB DATE OFF to either Kermit. Note that time stamps will not be passed in either direction with that setting. The fix: SC93342 in IKCKER UPD. ---------------- 93/12/16 ---------------------------------------------- Kermit-CMS would sometimes incorrectly identify the terminal controller type for sessions established using VM/Passthru (PVM) from a remote system, i.e., decide that a fullscreen session is linemode, depending on the I/O gen of both the local and remote hosts and PVM configuration. Now, however, Kermit can distinguish "disguised" fullscreen sessions from linemode (TTY) sessions. The fix: SC93355 in IKCKER UPD. See also the optional update SC9131X for dealing with VTAM (documented above). ---------------- 94/3/15 ----------------------------------------------- Kermit-370 now sends an explicit NAK packet when it receives a bad data packet, instead of resending the previous ACK (which is nominally the same thing in Kermit protocol). This way, there are no needless timeouts when dealing with a zealous sliding-windows Kermit. The fix: SC94074 in IKCKER UPD. ---------------- 94/6/23 ----------------------------------------------- Kermit-370 honors a new protocol feature known as "WHATAMI". Thus, when Kermit-370 is in server mode, the user can issue a SET FILE TYPE to the local Kermit and have it take effect in the server as well. The local Kermit obviously must also support WHATAMI. The fix: SC94174 in IKCKER UPD. See also the note in section (C) dated 90/7/5. ---------------- 94/6/30 ----------------------------------------------- Kermit-370 honors the new level-1 restart/recovery mode. When a similarly equipped Kermit is at the other end, an interrupted binary transfer can be resumed where it left off by issuing a RESEND instead of a SEND (same syntax). Attributes must be enabled at both ends of the transfer, and the sender must be set to binary (V-BINARY and D-BINARY are also acceptable). If the file in question is already fully received at the other end, RESEND does nothing; if the file is not even partially received, RESEND behaves just like SEND. In order to insure that the partial file is not erased when a transfer aborts, it is helpful to issue a SET INCOMPLETE KEEP to the receiving Kermit. Kermit-370 now also supports the UPDATE option of FILE COLLISION. With that option, a received file is rejected (on grounds of "date") if the transmitted time stamp is no later than that of an existing file of the same name. The fix: SC94181 in IKCKER UPD. ---------------- 94/9/3 ------------------------------------------------ Kermit-370 gives more accurate transfer statistics after uploads in server mode. Formerly, the time used in figuring transfer rates included any waiting time after the transfer completed but before the next inter-Kermit communication (result: understimated efficiency). The fix: SC94245 in IKCKER UPD. ---------------- 95/1/23 ----------------------------------------------- Kermit-370 misbehaved when doing a RESEND of a file that was already entirely received on the target system. If the length matched exactly that of the file to be sent, the whole thing would be sent again and appended. That is now corrected. Also, Kermit-370 now has the APC subcommand for sending Kermit commands to the micro while in connect mode. The fix: SC95023 in IKCKER UPD. ---------------- 95/2/1 ------------------------------------------------ Kermit-370 objected to receiving a RESEND of a file too large to fit on disk without removing the portion already received. It now takes into account the fact that that portion will not be duplicated. The fix: SC95032 in IKCKER UPD. ---------------- 95/2/2 ------------------------------------------------ Kermit-370 is now at level 4.3.1. ---------------- 95/2/17 ----------------------------------------------- Kermit-CMS now avoids an obscure bug for uploaded SFS files. If DEBUG is turned on, and mode "A" is SFS, a newly-uploaded A-disk file requires special effort to be visible to Kermit. Without that effort, an aborted upload followed immediately by a RESEND would append the entire file to whatever was received in the first attempt. Kermit now closes all files properly. The fix: SC95048 in IKCKER UPD. ---------------- 95/2/28 ----------------------------------------------- Kermit-370 now uses the newly-transmitted time tag for a file that is resumed after an abortive transfer. The fix: SC95059 in IKCKER UPD. ---------------- 95/4/18 ----------------------------------------------- Kermit-370 no longer treats an error-free file transfer as an "error" for the purpose of deciding whether to halt execution of a TAKE file. The fix: SC95108 in IKCKER UPD. ---------------- 95/6/23 ----------------------------------------------- Kermit-370 now supports the REGET subcommand, which works like GET, but makes the server do a RESEND of the requested file. The fix: SC95174 in IKCKER UPD. ---------------- 96/5/1 ------------------------------------------------ Kermit-370 now suppresses the "doubled" transmission of a file that can sometimes occur on a flaky connection. (This was a problem introduced in the process of avoiding unnecessary time-outs on flaky lines.) The fix: SC96122 in IKCKER UPD. ---------------- 96/5/30 ----------------------------------------------- Kermit-370 now announces its system type to the other Kermit before a transfer. This meshes with new versions of the various micro Kermits that expect that information and will display it to the transfer screen. The fix: SC96151 in IKCKER UPD. ---------------- 96/6/6 ------------------------------------------------ Kermit-370 has been modified to take advantage of another recent upgrade to micro Kermits -- it will be possible to issue a SEND or GET to the mainframe Kermit, and the micro will automatically pop from terminal emulation into transfer mode and then revert to emulation as soon as the transfer is done. The fix: SC96158 in IKCKER UPD. ---------------- 96/12/3 ----------------------------------------------- Kermit-CMS has been updated to take action on the recently announced changes to CMS for supporting file dates after 1999. There are two parts: Kermit-CMS (a) recognizes when a file to be sent needs a leading "20" and sends the correct time tag to the other Kermit (actually, this part was already in place for dates up through 2049), and (b) sets the correct time tag for a received file as well. Part (b) is meaningful only when CMS 13 or higher is running, but it actually works even for earlier versions of CMS as long as Kermit is installed *without* SFS support. The fix: SC96165 and SC96338 in IKCKER UPD. ---------------- 97/1/28 ----------------------------------------------- Kermit-370 was failing to clear the "Kermit command error" status upon execution of the VERSION and ECHO subcommands. It now clears that status condition to "No errors" after all subcommands, as described in the documentation. The fix: SC97028 in IKCKER UPD. ---------------- 97/6/13 ----------------------------------------------- Kermit-370 is now at level 4.3.2. ------------------------------------------------------------------------