Is port re-entrant. State driven Xmodem and Ymodem on multiple ports simultaneously. Is fully thread safe. Supports Windows XP through Windows 10. Works with all 32-bit versions of Borland, Codegear and Embarcadero Delphi. Works with 32- bit and 64-bit verisons of Embarcadero Delta XE through Delphi XE8, and Delphi 10 Seattle and Berlin. Erik Salaj from Winsoft has a com port component for Delphi XE6 Firemonkey on OSX available. This is the latest com port component in a series of com port components that he has available for Windows, Android, and IOS.
ZylSerialPort - Serial port communication Delphi & CBuilder Component Zyl Soft See also: ZylSerialPort 1.73 Delphi & CBuilder Component ZylSerialPort is a Delphi & CBuilder thread based serial port component. Use ZylSerialPort component to easily communicate with external devices on serial port connection, such as modems, bar code readers, GSM modules and others. It works in synchronous and asynchronous mode. You can use it also with USB, IrDA and Bluetooth devices, because these devices have a driver that redirects the input from the USB, IrDA or Bluetooth port to a virtual serial port (you can check it in System/Device Manager/Ports).
![Delphi xe com port component Delphi xe com port component](http://lmd.de/products/vcl/lmdtools/shots/lmdnhint0.png)
If your USB device is not provided with such a driver, then use a USB controller whose vendor provides a virtual serial port driver, such as or use a USB/RS-232 adapter. The demo version is fully functional in Delphi and CBuilder IDE, but it displays a nag dialog (the licensed version will, of course, not have a nag dialog and will not be limited to the IDE).
The package includes demo programs for Delphi and CBuilder and a help file with the description of the component.
Overview This document describes troubleshooting and common ERRORCODE and SQLCODE errors during masking. Sections in this document are:.
DB2 Connector Troubleshooting:. DB2 Error Code formats.
![Port Port](http://www.delphiarea.com/wp-content/uploads/preview2.png)
Troubleshooting Steps. DB2 ERRORCODE Summary:. ERRORCODE=-4214 - JDBC failed to connect to the database. ERRORCODE=-4229 - The executed SQL statement had an error. ERRORCODE=-4470 - Connection already closed. ERRORCODE=-4499 - Connection refused.
DB2 SQLCODE Summary:. SQLCODE=-104 - Illegal symbol/token. SQLCODE=-204 - Object is unspecified. SQLCODE=-206 - Object is not valid in this context. SQLCODE=-302 - Input too large or invalid for target column. SQLCODE=-471 - The SQL Code failed.
SQLCODE=-551 - No privilege to perform operation. SQLCODE=-805 - DB2 DBRM or package not found. SQLCODE=-913 - Execution failed due to Deadlock or Timeout. Additional Information.
External Links. Troubleshooting Steps The first step in troubleshooting is to look at the logs:. Open the masking logs. Get the ERRORCODE or SQLCODE.
Get the SQLSTATE. Get the Step returning the error. Check additional information such as executed SQL and additional errors.
Check if the ERRORCODE or SQLCODE is detailed below. If additional information is needed or the error is not detailed below, search IBM DB2 documentation on the Web. If further information is needed, set the diagnostics level to 4, rerun and check db2diag.log. Example 1 -Update (Commit) Failure Committing the updates to the table failed with a violation or error. ERROR 01-02 10:59:23,481 - Update - Unable to commit Update connection ISAP - TSO35ISAP - DSNB - ST35 CONNECTOR:org Error updating batch jcct4102100404.18.60 Batch failure.
The batch was submitted, but at least one exception occurred on an individual member of the batch. Use getNextException to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null.
Masking Example On the masking engine, this error has been seen in the TableOutput step. The error usually presents the SQL which is failing and the SQL statement can be tested on the database. The SQLERRMC details the TOKEN. Here: ' ISAPDBX' INFO 01-02 15:06:51,651 - TableOutput - Connected to database ISAP - TSO35ISAP - DSNB - ST35 CONNECTOR (commit=10000) Couldn't execute SQL: TRUNCATE TABLE ISAPDBX.' PARECOR' DROP STORAGE IGNORE DELETE TRIGGERS IMMEDIATE DB2 SQL Error: SQLCODE=-104, SQLSTATE=42601, SQLERRMC=ISAPDBX;IS, DRIVER=4.18.60. Masking Example On the masking engine, we will usually see SQLCODE=-204 after a Table input step. It can also be after other steps.
The error usually presents the SQL which is failing and this SQL can be tested on the database. The SQLERRMC details the Object. Here: ' SELECT. FROM DBX.' TABLE' ' In this case, it is likely that the schema or the table name is incorrect. ERROR 19-01 13:19:28,834 - Table input - Unexpected error An error occurred executing SQL: SELECT. FROM DBX.'
TABLE' DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=DBX.' Masking Example On the masking engine, we will see SQLCODE=-206 at a Table input step. The error usually presents the SQL which is failing and this SQL can be tested on the database.
The SQLERRMC details the Object: ' DMSROWID' In this case, the manually added column is ' DMSROWID' and it has been specified as ' DMSROWID' in the Rule Set and Logical Key, which is incorrect and cannot be found. ERROR 19-01 13:19:28,834 - Table input - Unexpected error An error occurred executing SQL: SELECT 'DMSROWID', 'DATA1', 'DATA2', 'DATA3' FROM DBX.' TABLE' SQLCODE=-206, SQLSTATE=42703, SQLERRMC=DMSROWID. Masking Example This error is usually returned early in the masking process, even during Connector and Rule Set creation. The error example below is thrown at the transformation job, at the Table input step.
ERROR 09-11 14:42:03,619 - Table input - Unexpected error An error occurred executing SQL: SELECT 'CODEFSLCLI', 'NOMECGNCLI', 'NOMENOMECLI', 'CODECLI' FROM C8DBA16.' DELPHIXTABLE' DB2 SQL Error: SQLCODE=-551, SQLSTATE=42501, SQLERRMC=C8DBAR2;SELECT;C8DBA16.DELPHIXTABLE, DRIVER=4.18.60.