UPDATES TO DATA COLLECTION TRANSACTION BUILDING TOOL RELEASE 2.0 (aka DCTPB32)
------------------------------------------------------------------------------
This file catalogs updates made to the 32-bit version of the Data Collection
Transaction Building Tool that was released on diskette in September 1997.
This package includes fixes for both OS/2 and NT. The self-extracting zip
file DCTPB2FD.EXE contains the following files:
dctpb2fx.htm
dctpb32.htm
os2\dctpb32.exe
os2\bptcd32.exe
os2\imbedscr.exe
nt\dctpb32.exe
nt\bptcd32.exe
nt\imbedscr.exe
To expand the file, copy it to an empty directory. Then run the following
from that directory:
dctpb2fd -d
The -d parameter causes the subdirectories to be created.
The appropriate files in the .\os2 or .\nt directory can then be copied over
the prior versions.
NOTE: FIX PACK D AND BEYOND CAN ONLY BE APPLIED IF YOU HAVE INSTALLED THE
DCCONNECT TRANSACTION BUILDING TOOL FROM THE 1.4.0 VERSION OF THE CD.
THIS IS BECAUSE THE NEW VERSION FROM THE 1.4.0 CD USES A DIFFERENT
MECHANISM FOR CHECKING WHETHER THE LICENSE FILE HAS BEEN PROPERLY
INSTALLED. FIX PACK D AND LATER WILL USE THIS NEW MECHANISM AND THUS
WILL NOT WORK IF THE LICENSE WAS NOT INSTALLED FROM THE 1.4.0 CD.
The installation of the 1.4.0 CD copied the product executable files into
the directory defined by the environment variable DCTPB. If this is the same
directory that is used for DCConnect, then DCTPB32.HTM should go into the
\dcconn\help directory otherwise it should go in the same directory as the
product executables.
CHRONOLOGICAL SUMMARY OF FIXES/CHANGES
--------------------------------------
9-10-97: DCTPB32.EXE and BPTCD32.EXE no longer require the Visual Age C++
DLLs. The C library functions are now statically linked to these
executables. Executables are a little larger as a result, but they
can now run without any other files required (except the license
file).
9-20-97: Fixed bug generating APND command with new parameters in BPTCD32.EXE.
You'd end up with an APND command containing only the last three
parameters.
9-23-97: Checking for unreferenced labels is now done before checking for
unresolved labels. Unreferenced labels generate warnings while
unresolved labels generate errors.
9-24-97: DCTPB32.EXE and BPTCD32.EXE now will use the environment variable
DCTPB to look for the license file if that license file is not found
in the current directory.
9-26-97: Fixed problem processing ONKEY/ONSUB with maximum of 20 branches.
Increased maximum command length to 1024. Also fixed problem
processing commands that are split across multiple lines. A cause
for a trap was fixed as a result of these changes.
9-29-97: Fixed bug processing CLRP command. In the terminal the CLRP would
work, but it would be followed immediately by a message indicating
the 'Parameter string is invalid'.
9-29-97: Fixed bug generating CLRP command in BPTCD32.EXE. It used to show
up as a CLRS command with the 3 parameters for CLRP.
----------------------------------------------------------------------------
End of changes in version A of fix package (November 1997).
----------------------------------------------------------------------------
12-3-97: SEND command for 7524 terminals now allows RS_232 as a target.
1-28-98: GOSUB, ONSUB and RETURN are now allowed for 7524 programs.
1-28-98: Added optional second parameter to the TERMTYPE command. It is
called ENFORCE_BINDINGS and it requires the use of the KEY command
to start programs instead of using the PROGRAM command. If
ENFORCE_BINDINGS is used, then for 7527/7524 programs, DCTPB
will resolve labels for branches between programs. Of course this
requires that when binding your programs in DCConnect, you do it
exactly as stated in all the KEY commands dictate. (Without the
ENFORCE_BINDINGS parameter, branches to other programs for 7527/7524
must use a step number). See DCTPB32.RME for more details.
2-27-98: KEY and ENDKEY commands are now allowed in imbedded scripts if
the ENFORCE_BINDINGS parameter was specified on the TERMTYPE
command. The TERMTYPE command must still be in the highest level
file; it can't be in an imbedded file.
2-27-98: The KEY command will now accept a number for the key name parameter -
just like ONKEY, ONSUB, GOTO, GOSUB, and BRAUV commands.
3-5-98: Refixed the 9-20-97 fix regarding a bug generating APND command with
new parameters in BPTCD32.EXE. You'd end up with an APND command
containing only the last three parameters. This fix got lost while
making other fixes.
3-9-98: BPTCD32.EXE no longer traps if no command line parameters are given.
----------------------------------------------------------------------------
End of changes in version B of fix package (June 1998).
----------------------------------------------------------------------------
4-7-99: The second parameter for the GOTO command is now optional if the
first parameter is END_OF_PROGRAM.
4-18-99: Due to a typo, the program number TCH12 was flagged as invalid for
the GOTO, GOSUB, ONKEY and ONSUB commands even though all other
TCHxx regions were valid. This was also a problem on the KEY
command when bindings were being enforced.
4-19-99: Documentation (DCTPB32.HTM) enhanced with HTML skeleton so it can
be viewed in browser with links to each section from the table of
contents as well as other references. This updated documentation
is now included in the fix pack.
----------------------------------------------------------------------------
End of changes in version C of fix package (May 1999).
----------------------------------------------------------------------------
NOTE: FIX PACK D AND BEYOND CAN ONLY BE APPLIED IF YOU HAVE INSTALLED FROM
THE 1.4.0 CD FOR THE DCCONNECT TRANSACTION BUILDING TOOL.
9-27-99: Fixed problem ignoring tabs between an ending double quote and
a comma that is the delimiter before the next parameter.
5-11-00: Inline messages and messages from MESSAGE commands can now be
used at the same time. The message numbers in MESSAGE commands
no longer need to be sequential either - although for maintenance
purposes, it is probably a good idea to organize them that way.
5-12-00: Redid WARNING 117 about unreferenced labels so that the individual
references are only written to dctpb.err and not to the screen -
since most of the time these are harmless
5-17-00: The APNDSTR command now accepts 0 for the length, indicating that
the exact length of the text should be used. Always using 0 for the
length is now recommended - so that counting errors are avoided.
10-19-00: Corrected problem with line number referenced in warning/error
messages. In 5-11-00 change, a two pass approach for parsing the
file was implemented. However, the line number for the highest
imbed level was not reset to 1 between the two passes.
Also fixed problem where line number was always 1 more than it
should be.
02-13-01: Added a utility which, given the top level script name, generates
a single listing file containing all imbedded files. The listing
includes the line numbers for all imbedded files as well as
a letter indicating at what level each file is imbedded. The
utility as the following syntax:
imbedscr filename.scr
Where filename.scr is the name of the script file that you would
specify when invoking dctpb32.exe.
The output file name will have the same 'filename' portion as the
input file name but will have the extension .LST.
Having a single listing file is useful when you have lots of
imbedded scripts and you need to search them or analyze them.
Note: This same tool can be used with Transaction Connection scripts!
02-27-01: The maximum number of keys allowed for an ONKEY or ONSUB command
is now 50.
02-27-01: Comments starting with double slash (//) are no longer automatically
included in the .PGM file during compile. If you want double-slash
comments to be included, you must specify a second command line
parameter, INCLUDE_COMMENTS, when running DCTPB32.EXE.
You may want to use the INCLUDE_COMMENTS parameter if you want them
to show up when the program is viewed using, for example, the
DCConnect Toolkit. However, comments that are included in the .PGM
file result in a larger download to 7524/7527 terminals (2 extra
bytes per comment).
----------------------------------------------------------------------------
End of changes in version D of fix package (March 2001).
----------------------------------------------------------------------------