Specifications

Configuring ODBC Data Exchange Reports
PlantScape Server and Client Configuration Guide 421
Selecting an Alarm Priority in the Event of a Failed SQL Report
If the SQL report fails, an alarm is generated with a message describing the type
of error. Configure the priority of this alarm by selecting an alarm type from the
Alarm priority on error list.
Specifying How Bad Values Are Handled
You can configure how bad or Not a Number (NaN) numeric and string values
are stored in the ODBC database. You use the Replace Bad/NaN numeric values
with dropdown list to specify either a NULL or a zero. You use the Replace Bad
string values with dropdown list to select either a NULL value or an empty string.
Creating the Input Reference File
The tasks performed by an ODBC Data Exchange report are defined in a free
format ASCII file called the Input Reference file. You create this file with a text
editor. The file is restricted to 80 characters per line.
Creating SQL Transactions
The Input Reference file consists of any number of SQL transactions. Each
transaction is made up of:
• Commands
Any SQL command supported by the Open Client interface can be used.
Note that any variables declared in these commands will apply only until the
end of the current transaction and that each transaction may be up to 1000
lines long.
Each SQL command must begin on a new line and must end with an end-of
-command marker (“;”).
• PlantScape Server references
References to the PlantScape server database need to be enclosed in “at”
symbols (that is, in the format “@...@”), and can be embedded anywhere
inside the SQL transaction.
Data is extracted from the PlantScape server database using PlantScape server
references embedded in the SQL command before the end-of-command marker
(“;”). Data can be inserted into the PlantScape server database using PlantScape
server references immediately after the “;”.
plscpcg.book Page 421 Monday, May 28, 2001 10:11 AM