Database Information - DB2/400 SQL Gateway (Magic xpa 3.x)
The Database Information parameter in the DBMS Properties, Database Properties, Data Source Properties, Column Properties and Index Properties dialog boxes lets you supply database-dependent information that Magic xpa can pass to the underlying DBMS. The use of this parameter is optional.
Multiple keywords should be delimited by one or more spaces.
Some of the keywords may not require values to be specified. All of the keywords and their values must be specified in uppercase.
|
Keyword
|
Description
|
|
|
|
|
|
|
CHECK_KEY=Y
|
Checks the data table for the existence of a unique index value as the end user attempts to input a data into a record. If a duplicate value is input by the end user into the variables constructing an index defined as Unique in Magic xpa’s Data repository, Magic xpa will issue a Duplicate Index error message and prevent further end-user processing until the input is changed. For some DBMSs, this check takes a toll in performance and it is not recommended. In such a case, the developer may decide not to use this keyword, and then the results of duplicate index value entry will depend on the DBMS behavior.
| |
?
| | | |
|
CNVTSTR=Y
|
Forces the ASCII/EBCDIC conversion for an Alpha field greater than 256 characters.
|
|
|
|
?
|
|
|
CRTSQLSCRPT=<file name>
|
Records SQL CREATE statements in a text file. Specify this keyword in the DB2/400 entry in the DBMS repository to create an SQL scripts file. The scripts file is created in the same platform where Magic xpa is running and can be used by the “Run SQL Statements” (RUNSQLSTM) IBM i command to create SQL tables on IBM i.
|
?
|
|
|
|
|
|
DateTimeGetDefSupport=Y
|
This keyword only works if you are performing a Get Definition action. If you use this keyword as part of your database properties, a time stamp retrieved from IBM i is converted by Magic xpa to Magic xpa’s Datetime format.
|
|
?
|
|
|
|
|
NAMING=*SQL
|
Support for the SQL naming format is for the SQL gateway only.
Specify this keyword in the DB2/400 entry in the DBMS repository to use the SQL naming format (for example, “collection.table”).
|
?
|
|
|
|
|
|
SQL_ISOLATION_LEVEL
|
Support for different SQL isolation levels: UR,CS,NC.
|
?
|
?
|
|
|
|
|
SUPPORT_UNICODE_STMT
|
Several IBM i functions use Unicode internally so that character data integrity is maintained for users across multilingual platforms.
To work with Unicode definitions on DB2 Universal Database (UDB) for IBM i, the SUPPORT_UNICODE_STMT keyword should be specified.
Otherwise, the data is translated from EBCDIC (depending on CCSID) to ASCII.
|
?
|
|
|
|
|
