FIXES TO DCConnect 1.01 AND OTHER PRODUCTS ON THE DCCONNECT CD
--------------------------------------------------------------
This file catalogs fixes made to the DCConnect products since we
shipped version 1.01 in October 1996.
This file also explains how to install the fixes from the DCN101FX.EXE
self-extracting zip file.
See the bottom of the file for the date of the last change.
If you have the file DCN101FX.EXE you can either create a diskette from
which to install the fixes or you can expand the self-extracting zip file
on the hard drive in any subdirectory and run the installation from that
subdirectory.
IMPORTANT NOTE 1:
These fixes can only be installed if your PC has been rebooted since you
installed DCConnect 1.01. The installation makes use of some
environment variables that are defined by CONFIG.SYS.
EXPANDING AND INSTALLING FROM THE HARD DRIVE
--------------------------------------------
To expand and install DCN101FX.EXE from somewhere on your hard drive,
perform the following steps:
1) Create or choose an empty directory anywhere on your harddrive. For
example: C:\TEMP
2) Copy or download DCN101FX.EXE to that directory
3) Make sure that directory is the current directory and then run the
executable by typing:
DCN101FX
This will expand all the files into the current directory.
4) To install the fixes, first make sure none of the DCConnect products are
running and that the current directory is the one containing the expanded
contents of the DCN101FX executable. Issue the following command:
INSTALL
5) Continue with the section below marked: CHRONOLOGICAL SUMMARY OF
FIXES/CHANGES
EXPANDING AND INSTALLING FROM A DISKETTE
----------------------------------------
To create a diskette from the DCN101FX.EXE self-extracting executable,
perform the following steps:
1) Get a completely blank, formatted 1.44 3.5 in. diskette
2) Make sure the DCN101FX.EXE is somewhere on your hard drive, for example
C:\TEMP\DCN101FX.EXE. But DO NOT copy this file to the diskette. If
you do, there will not be enough room to expand all the files contained
in the self-extracting executable.
3) Make A: the current drive
4) If your executable is in C:\TEMP\DCN101FX.EXE then run the following
command:
C:\TEMP\DCN101FX
This will extract the files from the executable and put them on the
diskette because A: is the current drive.
5) To install the fixes contained on the fix diskette, first make sure none
of the DCConnect products are running and then put the fix diskette
in drive A: Issue the following command:
A:\INSTALL
CHRONOLOGICAL SUMMARY OF FIXES/CHANGES
--------------------------------------
2-13-97: Changed the server so that it ignores an incorrect COMM_LINE_NUM
for a terminal or line definition for the RF_SERIAL_PORT. The GUI should
be putting a 0 in for that value, but instead it puts a 1-4 in. It was
easier to make the runtime more forgiving than to change the GUI.
Changed file: \DCCONN\BIN\DCXCPOS2.EXE
2-14-97: Fixed problem where a failed validation file download to a 7526
(via a submit or load->validation files) would not automatically be retried
as a complete download by DCConnect.
Changed file: \DCCONN\BIN\DCXCPOS2.EXE
2-14-97: Fixed problem where Submit from validation editor did not cause
the file to be downloaded. The .VAL file was created but not terminals
were downloaded with the new file. The GUI now makes the API call properly.
There is another part to this problem which lies in the runtime. See
the 2-17-97 problem that was fixed in the runtime.
Changed file: \DCCONN\DLL\DCCONFIG.DLL
2-14-97: Fixed two bugs in the TCP/IP code which resulted in more
communications errors than there should have been. One bug resulted
in too quick timeouts and the other resulted in DCConnect thinking a message
came from an invalid IP address. Also increased the retry count for
each command to 3 from 2.
Changed file: \DCCONN\BIN\DCXIPOS2.EXE
2-14-97: Changed code to get a terminal out of the not-responding state if a
transaction or download request comes from the terminal when in this state.
This shouldn't be necessary if the port timeout is sufficient. Mechanisms
are already in place for DCConnect to reestablish communications with a
terminal that has been powered on or comes back into range after being out
of range of the nearest base.
However, we have seen cases where it takes more than a minute for a terminal
to respond to an Are-you-there poll and there was no indication that the
terminal went out of range or was powered off and on. In this situation,
DCConnect put the terminal in the not-responding state. Later when a
transaction came in, the terminal would be told not to send any more.
With the new change, the terminal may still be told this initially - but
right after that DCConnect will go through its initialization steps with the
terminal which should cause the terminal to be put back into the in-service
state - provided the terminal responds properly to these steps.
This change is needed mostly for the RF environment - however, since there
is a lot of common code for RF and TCP/IP networks, the change has also
works in the TCP/IP environment.
Changed files: \DCCONN\BIN\DCXRFOS2.EXE
\DCCONN\BIN\DCXIPOS2.EXE
2-14-97: Fixed problem for 7527 terminal where the transaction buffer was
not properly allocated if it exceeded 99999 bytes. We were trying to
squeeze 6 bytes into 5.
This changes fixes APAR PQ00922 (actually an APAR against DCC/2r).
Changed file: \DCCONN\BIN\DCXCPOS2.EXE
2-14-97: Fixed problem where callers of the API DcxRequestData were not
getting responses of (DCX_NO_DATA) when the runtime shutdown. Instead,
they were left hanging.
Changed file: \DCCONN\BIN\DCXCPOS2.EXE
2-14-97: The file DFTMSGS.BIN for the DCConnect Toolkit was corrupted as
shipped. This is only a problem if you try to use DCTPB.EXE outside of
DCConnect. When trying to compile with DCTPB.EXE and the corrupted file
you get an error saying the message file is incorrect.
Changed file: \DCCONN\BIN\DFTMSGS.BIN
2-14-97: Fixed trap that resulted when you tried to modify more than one
transaction program at the same time.
Changed file: \DCCONN\BIN\EDITPGM.EXE
2-14-97: Fixed problem with CMPUV and BRAUV where these commands would not
take UVx as a valid value for either user variable parameter. Only a number
worked before.
Changed file: \DCCONN\BIN\DCTPB.EXE
2-14-97: Fixed PM hang problem while deleting or adding adapters on systems
without ARTIC support installed.
This changes fixes APAR PQ01439
Changed file: \DCCONN\DLL\DCCONFIG.DLL
2-17-97: Fixed two problems with submitting validation files. One problem
affected 7526 terminals and the other affected 7527 and 7524 terminals.
Before the problems were fixed, a submit initialized the file to size 0 or
2 and did not load anything to it.
Changed file: \DCCONN\BIN\DCXCPOS2.EXE
2-24-97: Fixed problem starting DCConnect Run-Time after installing OS/2
fix pack26 on Warp 3.0 or while running on Warp 4.0. DCConnect Run-Time
will fail to start and OS/2 displays a SYS3175 (Trap-D) error in modual
CS2232tnk.dll.
Changed file: \DCCONN\DLL\DCXUTILS.DLL