5 Other Functions
5-23
NJ/NX-series Database Connection CPU Units User’s Manual (W527)
5
5-5 Timeout Monitoring Functions
5-5-2 Login Timeout
The login timeout is monitored in the following cases.
ï‚– When connecting to a DB using a DB_Connect (Establish DB Connection) instruction
ï‚– When reconnecting to a DB while a DB Connection is in the Disconnected status
The following table shows the operation to be performed when a login timeout has occurred.
When the timeout occurred DB Connection status
after the timeout occurred
Instruction execution result
When executing a DB_Connect
Closed ErrorID = 3005 hex (DB Connection Failed)
When reconnecting to a DB
5-5-3 Query Execution Timeout
The query execution timeout is monitored in the following cases.
ï‚– When sending an SQL statement to a DB using a DB_Insert (Insert DB Record), DB_Update
(Update DB Record), DB_Select (Retrieve DB Record), or DB_Delete (Delete DB Record)
instruction
ï‚– When resending an SQL statement stored in the Spool memory
The following table shows the operation to be performed when a query execution timeout has
occurred.
When the timeout occurred DB Connection status
after the timeout occurred
Instruction execution result
When executing a DB_Insert or
DB_Update instruction
Connected ErrorID = 300B hex (SQL Execution Error)
SendStatus = _DBC_SEND_COMPLETE
The SQL statement is not stored in the Spool
When executing a DB_Select or
Connected ErrorID = 300B hex (SQL Execution Error)
When resending Spool data Connected The SQL statement is not stored in the Spool
* If an instruction error (SQL Execution Error) occurs, the transmitted SQL statement itself can be the
cause of the SQL Execution Error. Therefore, the SQL statement is not stored in the Spool memory
because the SQL Execution Error may occur again when the SQL statement is resent.
To Next Page
Loading...
Need help?
General
