Columbia Kermit/kermit.zip/ibm370/ikxker.bwr

Text File | 2020-01-01 | 31KB | 552 lines

CICS Kermit 4.3.x "Beware File" - Known Bugs, Problems, Limitations.

As of: 14:25  Friday, 1997 Jun 13

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 IKXKER.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 <[e-mail]>.

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-CICS 4.2 was released. All
updates prior to 93/9/30 have been removed from IKXKER.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 applied to the source
files in the CICS 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 IKXKER.BWR (the present file), but the updates
themselves are to be found in IKXKER.UPD.

The procedure for updating your copy of CICS Kermit is as described in
IKXKER.INS.  When new updates become available, and you wish to apply
them, the following hints may prove useful.

1) Obtain the latest version of IKXKER.UPD, which contains all the
   updates as a composite file punctuated by comment lines introducing
   each update's name and briefly describing its purpose.  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 IKXKER.UPD has records beginning with "/", then all instances of
   "/" in column 1 should be changed to "./", and all records with "@"
   in column 63 (introducing an update code normally found starting at
   column 64) should be moved over to make room for a "." in column 1.
   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.

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; the last
   line will be labelled with the last-applied update.  At present, the
   generic and CICS-specific code have different effective dates (see
   above).  The generic date is the one of interest.

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 at the beginning of IKXKER.UPD and remove
   the entries for updates already included in (i.e., older than) your
   sources.  Each line of the list begins with "./ *" plus an update
   code in the form xxyyddd (the yyddd is just the date of the update --
   the list is arranged chronologically).  Also, go through and discard
   those updates from the file.  Each update begins with a second copy
   of the line from the list and goes to the next such line.  The
   updates are also in chronological order.  Note that individual update
   control cards generally have time tags, but these are not necessarily
   accurate and should not be taken seriously.

4) Extract any desired optional updates from IKXKER.BWR (this file) and
   group them together with any local modifications specific to your
   site.  NOTE: all updates in this 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.

5) Apply the updates by following the instructions in IKXKER.INS.

------------------------------------------------------------------------
B) Unresolved problems .................................................

---------------- 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.  The others, including CICS
Kermit-370, may send the same file again, and it is left to the user to
prevent filename-collision problems on the receiving end.

---------------- 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/6/11 -----------------------------------------------
Kermit-CICS is a relatively new release, and some of the planned
features have not yet been implemented.  Here is a brief list, ordered
roughly by the importance and likelihood of implementation.  Some of
these features are to be added through separate programs or exit
routines, but others by modification of Kermit itself.  Some, such as
#1 and #4, would be locally developed, but the Kermit distribution
would include one or more samples.

 1. Algorithms for assigning a "userid" other than the OPID, TERMID, or
    USERID.  See IKXKER.INS for details.

 2. I/O for spool files, to be supported by IKXDYNAL.  See IKXDYN.HLP
    for details.

 3. I/O for MVS data sets, to be supported by IKXDYNAL.  ditto.

 4. Data security exits.  See IKXKER.INS for details.

 5. Local option for the action to take in response to BYE.

 6. Local option on limitations of use of TS space, starting with a
    simple test of whether there is enough TS space of the desired type
    for an inbound file.

 7. I/O for data objects on a remote CICS.

 8. Detection of the existence of data in output extra-partition TDQ's.

 9. Interception of terminal I/O from programs invoked by Kermit.

---------------- 91/6/28 -----------------------------------------------
Dynamically defined TD queues apparently do not reside in the DCT along
with hard-coded queues.  Kermit-CICS may not be able to read or write
them.

There may be limits on the size of TS queue records other than the
general CICS maximum of 32767.  If such limits exist, you may need to
reduce the &MAXLR global symbol in Kermit in order to force truncation
or folding at a save level.  However, such a change would preclude
writing such long records to Kermit directory members as well.

As with any multi-user environment, it is possible for a data object
scheduled for downloading via a wildcard filespec to disappear from the
system before its turn comes.  If that should happen, the transfer will
halt with an "I/O error".  On the other hand, if a new object appears
after the transfer has begun, it will not be sent, even if it matches
the wildcard specification.  This problem applies mainly to TS queues.

There is no HOST RENAME function supported by Kermit.  There is also no
APPEND option for the HOST COPY function.

There is a bug (or feature) in the handling of filespecs for the
simulated system commands TYPE, COPY, DELETE, and DIRECTORY.  If the
filetype is omitted, a filetype of TAKE, rather than TS, is assumed.

---------------- 91/10/31 ----------------------------------------------
Kermit-CICS has conditional assembly code for access to extra-partition
TD's under CICS 1.6 and earlier, but it works only for CICS/OS/VS (MVS);
there is no provision for DOS/VSE.

------------------------------------------------------------------------
C) Problems with workarounds or optional fixes .........................

---------------- 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 wish to run Kermit on an IBM 3270-type
terminal.  Normally, Kermit can recover from these error conditions, but
some configurations and/or versions of VTAM may hang the terminal
session instead or have other undesirable side effects.  For example,
there may be an error message IKT00405I SCREEN ERASURE CAUSED BY ERROR
RECOVERY from VTAM that never goes away.  In that case, there are
several possible cures.  First is the simple expedient of pressing PA1
to clear the error condition.  If that doesn't help at your site, you
may find that logging onto the host via Netview's TAF component makes
the error message appear only once.  If you cannot start Kermit
reliably, 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

Because there is apparently no way to determine from within a program
whether WSF Query is allowed for a particular terminal and because CICS
does not provide for Read Modified commands without waiting for an
Attention interrupt, the standard flag value on CICS is STCNORD+STCQBIT;
if you wish to force the code to select SERIES1, you should change that
to STCNORD+STCS1, as in the following:

 ./ * SC9131X - Customize controller type selection
 ./ R 01205200          $ 1205200 100                  11/21/91 00:16:50
 &CONOPTS SETC  'STCNORD+STCS1' SETCON options                  @SC9131X

Alternatively, if you have *only* GRAPHICS-type controllers, you could
change it to STCNORD+STCNOS1 (or STCNORD+STCNOS1+STCQBIT if you have
3174 AEA controllers).

---------------- 90/7/5 ------------------------------------------------
Kermit-370 honors the file type specification (binary or text) given by
a sending Kermit in an Attribute packet.  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 before sending it, e.g., by using HOST COPY to move it to a TS queue.

---------------- 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/5/30 -----------------------------------------------
The "factory" settings for several of the Kermit options may be unsuited
to the operation at a given site.  Here are updates to change some of
the most likely parameters to need changing.

 ./ R 01208000          $ 1208000 500
 LIMDSK   EQU   65536         Reduce user directory space quota @SC91150

 ./ R 01209000          $ 1209000 500
 CUTDSK   EQU   300000        Increase directory space cutoff   @SC91150

 ./ R 01226000          $ 1226000 500
 &USER    SETC  'TERM'        Use TERMID for user id            @SC91150

 ./ R 01226000          $ 1226000 500
 &USER    SETC  'UID'         Use USERID for user id            @SC91150

 ./ R 01226000          $ 1226000 500
 &USER    SETC  'OTHER'       Use exit routine to get user id   @SC91150

 ./ R 01415800          $ 1415800 10                            ->4.3<-
 &KTRACE  SETC  'YES'         Enable tracing                    @SC91150

---------------- 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/7/8 ------------------------------------------------
Running Kermit under CICS in a BTAM environment with a Yale-type
protocol converter may require the application of APAR PN00282 to avoid
continually getting out of transparent mode during a file transfer.  The
specific CICS component affected is DFHTCP.

---------------- 92/7/13 -----------------------------------------------
Under DOS/VSE, a small change can be made in the installation to avoid a
harmless error message from the assembly of IKXTRN -- remove the END
statement from the source file and insert a " PUNCH ' END'" into the JCL
after the " PUNCH ' COPY IKXTRN'".

---------------- 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

---------------- 93/1/21 -----------------------------------------------
Kermit-370 in FULLSCREEN mode can be at the mercy of clever efforts
toward screen "optimization" by the protocol converter.  One possible
symptom is the suppression of the last outbound packet in a transfer if
the screen is cleared just afterwards.  This may happen after an upload
or upon leaving server mode.  To avoid this possibility, Kermit-370 can
simply wait a few seconds to give the protocol converter less excuse for
suppressing the last packet.  The following update uses four seconds,
but the optimum time may be more or less, depending on the system.

 ./ * SC93021 - Try to prevent end effect in FULLSCREEN mode
 ./ I 08780000          $ 8780000 80                   01/22/93 ->4.3<-
          CLI   TRMTP,C'F'                                      @SC93021
          BNE   INTINICN      Go if not FULLSCREEN              @SC93021
          LA    0,4           Wait four seconds to synchronize  @SC93021
          KCALL SUPFNC,9                                        @SC93021
 INTINICN DS    0H                                              @SC93021

---------------- 93/5/21 -----------------------------------------------
Kermit-CICS sometimes has trouble synchronizing read and write commands
on GRAPHICS-type protocol converters.  The symptom is a lost packet when
the micro sends before the mainframe is ready.  There is a cure, but it
can't be applied generally because it may kill transfers on terminals
defined with the automatic up-casing option.  For some reason, the ASIS
option is not permitted for the CICS CONVERSE command, which is the
centerpiece of the update below.  Users are invited to experiment with
this update by moving the comma from before to after the word "ASIS" on
the line marked with "???" and/or to try the update with terminals set
for automatic upcasing.  If results are favorable, this update may be
added permanently to Kermit.

 ./ * SC93110 - Ensure line turnaround (CICS)
 ./ I 01131000          $ 1132000 1000                 04/21/93 22:14:44
 SCRCTLCH DS    X             WCC for next output op            @SC93110
 ./ R 05540400          $ 5540400 40                   04/21/93 22:14:44
          BE    SCRNEXWS      Expecting a reply - save ptrs     @SC93110
 ./ R 05542500 05543500 $ 5542500 300                  05/20/93 17:36:43
          CLI   WRRD,5                                          @SC93110
          BNE   *+12          Not expecting a reply - just send @SC93110
            CLI CONSOPR,6       Write message?                  @SC93110
            BNE SCRNEXWS        No, save ptrs                   @SC93110
 *        MVI   SCRCTLCH,X'C1'  Yes, lock it to prevent clash   @SC93110
 ./ I 05545000          $ 5545200 200                  04/21/93 22:14:44
          MVI   SCRLSTIO,0    Clear I/O code                    @SC93110
 ./ I 05545500          $ 5545600 100                  04/21/93 22:14:44
 SCRNEXWS MVC   SCRLSTIO,0(8) Save code of last I/O             @SC93110
          B     SCRNEXZ                                         @SC93110
 ./ I 05549000          $ 5549200 200                  04/21/93 22:14:44
          L     3,SCRLSTIO                                      @SC93110
 ./ D 05550150                                         04/21/93 22:14:44
 ./ R 05550250          $ 5550250 10                   04/21/93 22:14:44
                FROM(0(,3)) FROMLENGTH(SCRLSTIO+6),             @SC93110+
 ./ I 05551000          $ 5551060 60                   04/21/93 22:14:44
          CLI   SCRLSTIO,0    Saved WRITE operation?            @SC93110
          BE    SCRNEXRR      No, fine                          @SC93110
          EXEC CICS CONVERSE CTLCHAR(SCRCTLCH),                 @SC93110+
                FROM(0(,3)) FROMLENGTH(SCRLSTIO+6),             @SC93110+
                INTO(0(,7)) TOLENGTH(GTMLEN), ASIS   ???        @SC93110
          B     SCRNEXR2                                        @SC93110
 SCRNEXRR DS    0H                                              @SC93110
 ./ D 05559000                                         04/21/93 22:14:44
 ./ D 05569000                                         04/21/93 22:14:44

---------------- 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.

------------------------------------------------------------------------
D) Resolved problems ...................................................

---------------- 90/5/8 ------------------------------------------------
A commonly reported "problem" is that Kermit-370 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-CICS 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-CICS 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.

---------------- 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 IKXKER.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
IKXKER.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 IKXKER.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 IKXKER.UPD.

---------------- 94/12/10 ----------------------------------------------
Kermit-CICS now runs under CICS version 3.3.  CICS has introduced new
command-level facilities for obtaining the information in control blocks
formerly available only through the CSA, and the CSA has been removed.
The new facilities are automatically used by Kermit when installed with
the appropriate "SYSPARM" (always set to the current CICS version).
The fix: BM94344 in IKXKER.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 IKXKER.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 IKXKER.UPD.

---------------- 95/2/2 ------------------------------------------------
Kermit-370 is now at level 4.3.1.

---------------- 95/2/10 -----------------------------------------------
Kermit-CICS now avoids an error message during assembly under CICS 3.3
and higher.  The "error" in question had no effect on the executable
code, but should be avoided anyway.  The fix: SC95041 in IKXKER.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 IKXKER.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 IKXKER.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
IKXKER.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 IKXKER.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 IKXKER.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 IKXKER.UPD.

---------------- 96/6/13 -----------------------------------------------
Kermit-CICS has been updated to comply with the conventions for time
tags beyond 1999.  These are used only for files in the Kermit-managed
user directories.  TD and TS queues do not have time tags associated
with them.  The fix: SC96165 in IKXKER.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 IKXKER.UPD.

---------------- 97/6/13 -----------------------------------------------
Kermit-370 is now at level 4.3.2.

------------------------------------------------------------------------