![]() | ![]() |
Home |
|
|
Access Service User's Guide DirectConnect for AS/400 |
|
| Appendix B Quick Reference |
Chapter 16
This appendix contains quick reference tables for the following topics:
For detailed explanations of configuration properties, see Chapter 2, "Configuring the DirectConnect Access Service Library"
The following table lists access service library and access service properties in alphabetical order. The property category represents the subsection heading in the service library configuration file.
Property Name | Property Values | Property Category {Subsection Name} | Global Variable (GV) or set Statement (SS) |
Allocate | [ connect | request ] | {Target Interaction} | GV and SS |
APPCSecurity | [ pgm | none | same ] | {Target Interaction} | none |
ApplicationValidationFile | pathfilename | {Client Interaction} | none |
ASCIICodeset | char | {ACS Required} | none |
BinaryResults | [ binary | char ] | {Datatype Conversion} | GV and SS |
CharConvertError | [ reject | truncate ] | {Data Conversion Errors} | GV and SS |
ClientDecimalSeparator | char | {Client Interaction} | GV and SS |
ClientIdleTimeout | integer | {Client Interaction} | none |
ConnectionProtocol | lu62 | {ACS Required} | none |
ConnectionSpec1 | char | {ACS Required} | none |
ConnectionSpec2 | char | {ACS Required} | none |
ConnectionSpec3 | char | {ACS Required} | none |
CSPCatalogQualifier | qualifier | {Catalog Stored Procedures} | GV and SS |
CSPDBName | dbname | {Catalog Stored Procedures} | GV and SS |
CSPIncludeSystem | [ no | yes ] | {Catalog Stored Procedures} | GV and SS |
CSPIncludeTable | [ yes | no ] | {Catalog Stored Procedures} | GV and SS |
CSPIncludeView | [ yes | no ] | {Catalog Stored Procedures} | GV and SS |
CSPQualByDBName | [ no | yes ] | {Catalog Stored Procedures} | GV and SS |
DatabaseName | databasename | {ACS Required} | none |
DatatypeInfo | [ transact | target ] | {Catalog Stored Procedures} | GV and SS |
DateResults | [ datetime | datetime4 | char_iso | char_usa | char_eur | char_jis ] | {Datatype Conversion} | GV and SS |
DateTimeConvertError | [ reject | null | default ] | {Data Conversion Errors} | GV and SS |
DateTimeResults | [ datetime | datetime4 | char_iso | char_usa | char_eur | char_jis ] | {Datatype Conversion} | GV and SS |
DecimalResults | [ autoconvert | int | float | real | char | money | money4 | bcd ] | {Datatype Conversion} | GV and SS |
DefaultClientCodeset | clientcodeset | {ACS Required} | GV and SS |
DefaultDate | yyyy-mm-dd | {Data Conversion Errors} | none |
DefaultNum | integer | {Data Conversion Errors} | none |
DefaultTargetCodeset | targetcodeset | {ACS Required} | GV |
DefaultTime | hh.mm.ss | {Data Conversion Errors} | none |
EBCDICCodeset | char | {ACS Required} | none |
EnableAtStartup | [ no | yes ] | {Client Interaction} | none |
FloatResults | [ float | real | char ] | {Datatype Conversion} | GV and SS |
GatewayCompatible | [ no | yes ] | {Client Interaction} | GV |
GraphicResults | [ binary | char ] | {Datatype Conversion} | GV and SS |
Int2Results | [ smallint | char ] | {Datatype Conversion} | GV and SS |
Int4Results | [ int | char ] | {Datatype Conversion} | GV and SS |
IsolationLevel | [ cs | ur | no ] | {Target Interaction} | none |
LogConnectionStatistics | [ no | yes ] | {Logging} | none |
LogReceivedSQL | [ no | yes ] | {Logging} | none |
LogRequestStatistics | [ no | yes ] | {Logging} | none |
LogServiceStatistics | integer | {Logging} | none |
LogSvclibStatistics | integer | {Logging} | none |
LogTargetActivity | [ no | yes ] | {Logging} | none |
LogTransferStatistics | [ no | yes ] | {Logging} | none |
LogTransformedSQL | [ no | yes ] | {Logging} | none |
MaxResultSize | integer | {Client Interaction} | GV and SS |
MaxRowsReturned | integer | {Client Interaction} | GV and SS |
MaxSvcConnections | integer | {Client Interaction} | GV |
NumConvertError | [ reject | null | default ] | {Data Conversion Errors} | GV and SS |
PasswordRequired | [ no | yes ] | {Target Interaction} | none |
QuotedStringDelimiter | char | {Target Interaction} | none |
QCCSIDRemap | [ ccsid| alt_ccsid ] | (Target Interaction) | GV and SS |
RealResults | [ float | real | char ] | {Datatype Conversion} | GV and SS |
SendWarningMessages | [ no | yes ] | {Client Interaction} | GV and SS |
ServiceDescription | char | {Client Interaction} | GV |
SvclibDescription | char | {Client Interaction} | GV |
SQLInformationFile | filename | {Catalog Stored Procedures} | none |
SQLTransformation | [ passthrough | sybase | tsql0 | tsql1 | tsql2 ] | {Target Interaction} | GV and SS |
StopCondition | [ error | none | warning ] | {Target Interaction} | GV and SS |
TargetDecimalSeparator | char (default is a period) | {Target Interaction} | GV |
TextSize | integer | {Client Interaction} | GV and SS |
TimeResults | [ datetime | datetime4 | char_iso | char_usa | char_eur | char_jis ] | {Datatype Conversion} | GV and SS |
TPName | tpname | {ACS Required} | none |
TraceDRDATrans | [ no | yes ] | {Tracing} | none |
TraceEvents | [ no | yes ] | {Tracing} | none |
TraceHostCom | [ no | yes ] | {Tracing} | none |
TraceInterface | [ no | yes ] | {Tracing} | none |
TraceTarget | [ no | yes ] | {Tracing} | none |
TransactionMode | [ short | long ] | {Client Interaction} | GV and SS |
TransferBatch | integer | {Transfer} | GV and SS |
TransferErrorCount | integer | {Transfer} | GV and SS |
Version | versionstring | {Client Interaction} | GV |
This section contains tables showing the relationship between the combination of TransactionMode, Allocate, and StopCondition property settings and transaction behavior.
The following four tables show the effects of combined StopCondition and Allocate properties, based on a TransactionMode setting of short.
Condition/Status | Effects of Settings on Processing |
Does a rollback occur on an error? | The transaction rolls back immediately. |
What is the status of connection after an error occurs? | The connection ends. |
What happens if a begin transaction occurs? | A commit occurs and uses begin transaction behavior described in Table 5-9. |
When the client application issues a commit or rollback, what happens? | A commit or rollback occurs. |
If the request is a cursor or dynamic request, how does it behave? | The request behaves the same as TransactionMode=long. |
In batch mode, what happens if an error occurs? | The batch ends and a rollback occurs. |
When completed, is a batch job committed? | The batch commits if no errors occur. |
After the batch commits, what is the status of the connection? | The connection ends. |
The following table shows the effects of combined StopCondition and Allocate properties, based on a TransactionMode setting of short.
Condition/Status | Effects of Settings on Processing |
Does a rollback occur on an error? | A rollback does not occur. |
What is the status of the connection after an error occurs? | The connection continues. |
What happens if a begin transaction occurs? | A commit occurs and uses begin transaction behavior described in Table 5-9. |
When the client application issues a commit or rollback, what happens? | A commit or rollback occurs. |
If the request is a cursor or dynamic request, how does it behave? | The request behaves the same as TransactionMode=long. |
In batch mode, what happens if an error occurs? | The batch continues executing. |
When completed, is a batch job committed? | The batch is always committed. |
After the batch commits, what is the status of the connection? | The connection ends. |
The following table shows the effects of combined StopCondition and Allocate properties, based on a TransactionMode setting of short.
Condition/Status | Effects of Settings on Processing |
Does a rollback occur on an error? | The transaction rolls back immediately. |
What is the status of the connection after an error occurs? | The connection continues. |
What happens if a begin transaction occurs? | A commit occurs and uses begin transaction behavior described in Table 5-9. |
When the client application issues a commit or rollback, what happens? | A commit or rollback occurs. |
If the request is a cursor or dynamic request, how does it behave? | The request behaves the same as TransactionMode=long. |
In batch mode, what happens if an error occurs? | The batch request ends. |
When completed, is a batch job committed? | The batch commits if no errors occur. |
After the batch commits, what is the status of the connection? | The connection continues. |
The following table shows the effects of combined StopCondition and Allocate properties, based on a TransactionMode setting of short.
Condition/Status | Effects of Settings on Processing |
Does a rollback occur on an error? | A rollback does not occur. |
What is the status of the connection after an error occurs? | The connection continues. |
What happens if a begin transaction occurs? | A commit occurs and uses begin transaction behavior described in Table 5-9. |
When the client application issues a commit or rollback, what happens? | A commit or rollback occurs. |
If the request is a cursor or dynamic request, how does it behave? | The request behaves the same as TransactionMode=long. |
In batch mode, what happens if an error occurs? | The batch continues. |
When completed, is a batch job committed? | The batch commit occurs, if no errors occur. |
After the batch commits, what is the status of the connection? | The connection continues. |
The following four tables show the effects of StopCondition and Allocate properties, based on a TransactionMode setting of long.
Condition/Status | Effect of Settings on Processing |
Does a rollback occur on an error? | A rollback does not occur. |
What is the status of the connection after an error occurs? | The connection continues. |
What happens if a begin transaction occurs? | The begin transaction is ignored. Also, an informational message appears. |
When the client application issues a commit or rollback, what happens? | If TransactionMode was originally short, and cursors and dynamics were all freed, the commit or rollback occurs and TransactionMode changes back to short. If TransactionMode was originally long, then a commit or rollback occurs. |
If the request is a cursor or dynamic request, how does it behave? | If TransactionMode was originally short, and cursors and dynamics were all freed, a commit occurs and TransactionMode changes back to short. If TransactionMode was originally long, then the connection behaves the same as Allocate=request until all cursors and dynamics are freed |
In batch mode, what happens if an error occurs? | The batch transaction ends. |
When completed, is a batch job committed? | The batch does not commit. |
After the batch commits, what is the status of the connection? | The connection ends if the commit or rollback occurs at the end of batch. Otherwise, the connection continues. |
The following table shows the effects of combined StopCondition and Allocate properties, based on a TransactionMode setting of long.
Condition/Status | Effects of Settings on Processing |
Does a rollback occur on an error? | A rollback does not occur. |
What is the status of the connection after an error occurs? | The connection continues. |
What happens if a begin transaction occurs? | The access service ignores the begin transaction command. |
When the client application issues a commit or rollback, what happens? | If TransactionMode was originally short, and cursors and dynamics were all freed, the commit or rollback occurs and TransactionMode changes back to short. If TransactionMode was originally long, then a commit or rollback occurs. |
If the request is a cursor or dynamic request, how does it behave? | If TransactionMode was originally short, and cursors and dynamics were all freed, a commit occurs and TransactionMode changes back to short. If TransactionMode was originally long, then the connection behaves the same as Allocate=request until all cursors and dynamics are freed. |
In batch mode, what happens if an error occurs? | The batch continues. |
When completed, is a batch job committed? | The batch does not commit. |
After the batch commits, what is the status of the connection? | The connection ends if the commit or rollback occurs at the end of the batch. Otherwise, the connection continues. |
The following table shows the effects of combined StopCondition and Allocate properties, based on a TransactionMode setting of long.
Condition/Status | Effects of Settings on Processing |
Does a rollback occur on an error? | A rollback does not occur. |
What is the status of the connection after an error occurs? | The connection continues. |
What happens if a begin transaction occurs? | The access service ignores the begin transaction command. |
When the client application issues a commit or rollback, what happens? | If TransactionMode was originally short, and cursors and dynamics were all freed, the commit or rollback occurs and TransactionMode changes back to short. If TransactionMode was originally long, then a commit or rollback occurs. |
If the request is a cursor or dynamic request, how does it behave? | If TransactionMode was originally short, and cursors and dynamics were all freed, the commit occurs and TransactionMode changes back to short. If TransactionMode was originally long, then the connection behaves the same as Allocate=request until all cursors and dynamics are freed. |
In batch mode, what happens if an error occurs? | The batch request ends. |
When completed, is a batch job committed? | The batch does not commit. |
After the batch commits, what is the status of the connection? | The connection continues. |
The following table shows the effects of combined StopCondition and Allocate properties, based on a TransactionMode setting of long.
Condition/Status | Effects of Settings on Processing |
Does a rollback occur on an error? | A rollback does not occur. |
What is the status of the connection after an error occurs? | The connection continues. |
What happens if a begin transaction occurs? | The access service ignores the begin transaction command. |
When the client application issues a commit or rollback, what happens? | If TransactionMode was originally short, and cursors and dynamics were all freed, the commit or rollback occurs and TransactionMode changes back to short. If TransactionMode was originally long, then a commit or rollback occurs. |
If the request is a cursor or dynamic request, how does it behave? | If TransactionMode was originally short, and cursors and dynamics were all freed, a commit occurs and TransactionMode changes back to short. If TransactionMode was originally long, then the connection behaves the same as Allocate=request until all cursors and dynamics are freed. |
In batch mode, what happens if an error occurs? | The batch continues. |
When completed, is a batch job committed? | The batch does not commit. |
After the batch commits, what is the status of the connection? | The connection continues. |
The following table shows the effect on processing when a begin transaction command occurs in a request.
Condition/Status | When begin transaction occurs... |
Does a rollback occur on an error? | A rollback does not occur. |
What is the status of the connection after an error occurs? | The connection continues. |
What happens if another begin transaction occurs? | The access service ignores the begin transaction command. |
When the client application issues a commit or rollback, what happens? | If TransactionMode was originally short, it changes back to short. If TransactionMode was originally long, then a commit or rollback occurs. |
If the request is a cursor or dynamic request, how does it behave? | The request continues behaving as a short setting. |
In batch mode, what happens if an error occurs? | The batch continues. |
When completed, is a batch job committed? | The batch does not commit. |
After the batch commits, what is the status of the connection? | The connection continues. |
This section contains code set tables for two configuration properties:
DefaultClientCodeset
DefaultTargetCodeset
For current information on certified code sets, check the Sybase Web site or contact your local Sybase office. To request certification for a new code set, contact your local Sybase office.
The following table shows all values for the DefaultClientCodeset configuration property.
Code Set Identifier | Description | Certified |
9 | EUC-CNS encoding | |
10 | EUC-GB encoding | |
11 | Microsoft CP932 | |
12 | ISO 8859-2 Latin-2 Eastern Europe | |
13 | ISO-885905 Latin/Cyrillic | |
14 | ISO 8859-6 Latin/Arabic | |
15 | ISO 8859-7 Latin/Greek | |
16 | ISO 8859-8 Latin/Hebrew | |
17 | ISO 8859-9 Latin-5 Turkish | |
26 | Macintosh Cyrillic | |
27 | Macintosh Eastern Europe | |
28 | Macintosh Greek | |
29 | Macintosh Turkish | |
30 | HP Greek | |
31 | HP Turkish | |
32 | KOI8 - Cyrillic | |
33 | Thai Standard | |
420 | Arabic Bilingual | |
437 | U. S. code page | yes |
819 | ISO 8859-1 Latin | yes |
850 | European code page | yes |
852 | PC Eastern European | |
855 | PC Cyrillic | |
857 | PC Turkish | |
860 | PC Portuguese | |
861 | Icelandic | |
863 | PC Canadian French code page | yes |
864 | PC Arabic | |
866 | PC Russian | |
869 | PC Greek | |
874 | Microsoft Thai SB code page | |
932 | Japanese IBM J-DBCS | yes |
949 | PC MS Korean | |
950 | PC MS Traditional Chinese | |
954 | EUCJIS | yes |
1250 | MS Windows East Europe | |
1251 | MS Windows Cyrillic | |
1252 | MS Windows US | |
1253 | MS Windows Greek | |
1254 | MS Windows Turkish | |
1255 | MS Windows Hebrew | |
1256 | MS Windows Arabic | |
deckanji | Digital UNIX JIS encoding | yes |
eucjis | EUC-JIS encoding | yes |
mac | Standard Macintosh Roman | yes |
roman8 | HP Roman8 | yes |
sjis | Shift-JIS proper | yes |
The following table shows all values that the DefaultTargetCodeset configuration property can use.
Coded Character Set Identifier | Description | Certified |
37 | IBM EBCDIC code page | yes |
273 | IBM EBCDIC Germany/Austria code page | yes |
277 | IBM EBCDIC Denmark/Norway code page | yes |
278 | IBM EBCDIC Finland/Sweden code page | yes |
280 | IBM EBCDIC Italian code | yes |
284 | IBM EBCDIC Spain/Latin America code page | yes |
285 | IBM EBCDIC U.K. code page | |
297 | IBM EBCDIC France code page | |
420 | Arabic Bilingual | |
437 | US Standard code set | |
500 | Western Europe code page | yes |
850 | European code page | |
852 | PC Eastern Europe | |
855 | IBM PC Cyrillic | |
857 | IBM PC Turkish | |
860 | PC Portuguese | |
863 | IBM PC Canadian French code page | |
864 | PC Arabic | |
866 | PC Russian | |
869 | IBM PC Greek | |
870 | Eastern Europe | |
874 | Microsoft Thai SB code page | |
875 | Greek code page | |
930 - 290 -300 | Japan Katakana - SBCS - MBCS | |
933- 833 - 834 | MBCS Korean - SBCS - DBCS | |
935 - 836 - 837 | MBCS Simplified Chinese - SBCS - DBCS | |
937 - 37 - 835 | MBCS Traditional Chinese - SBCS - DBCS | |
939 - 1027 - 300 | Japan English - SBCS - MBCS | |
1047 | MVS Open Edition | |
5026 - 290 - 4396 | MBCS IBM Kanji (Katakana) - SBCS - DBCS | yes |
5035 - 1027 - 4396 | MBCS IBM Kanji (Latin) - SBCS - DBCS | yes |
cxgwebc | MDI Gateway-compatible | yes |
cxpsebc | PeopleSoft Custom |
The following table shows the current CCSIDs that can be remapped.
Code Set Identifier | Alternate Code Set Identifier | Purpose of Remapping |
930 | 3000 | With CCSID 3000, the access service maps the yen sign sent from the client to a yen sign stored on the host. Otherwise, CCSID 930 would map the yen sign to a backslash. |
939 | 3001 | With CCSID 3001, the access service maps the yen sign sent from the client to a yen sign stored on the host. Otherwise, CCSID 939 would map the yen sign to a backslash. |
5026 | 3002 | With CCSID 3002, the access service maps the yen sign sent from the client to a yen sign stored on the host. Otherwise, CCSID 5026 would map the yen sign to a backslash. |
5035 | 3003 | With CCSID 3003, the access service maps the yen sign sent from the client to a yen sign stored on the host. Otherwise, CCSID 5035 would map the yen sign to a backslash. |
|
|