| |
Home |
![[Table of Contents]](/dwicons/b_toc.gif)
|
Access Service User's Guide DirectConnect for AS/400 |
![[-]](/dwicons/i_colpse.gif)
| Appendix A Backward compatibility with MDI database gateways |
|
| Configuration considerations |
Following are configuration differences between the access service and the MDI Database Gateway.
The access service continues to support application validation via the ApplicationValidationFile property. We recommend using the Service Name Redirection capability instead of application validation. If you choose to use both Service Name Redirection and application validation, Service Name Redirection takes precedence.
For information about Service Name Redirection, see the DirectConnect Server Administration Guide.
All MDI Database Gateway code set alphanumeric characters and most punctuation characters map correctly to access service code sets. We recommend using the access service code sets whenever possible.
The MDI Database Gateway EBCDIC code set contains some nonstandard extended character mappings. If you have applications and data that depend on one or more of the unusual gateway control codes or extended character mappings, set the access service client and target code set properties as follows:
DefaultClientCodeset=819
DefaultTargetCodeset=gwebcdic
For detailed information about code set properties, see "DefaultClientCodeset" and "DefaultTargetCodeset" .
The access service BinaryResults and GraphicResults datatype conversion properties replace the MDI Database Gateway Disable Binary Support parameter.
To use MDI Database Gateway-compatible settings, set the access service GatewayCompatible property value to yes. After you change your client applications to access service settings, set the GatewayCompatible property to no to improve performance.
The access service does not support the MDI Database Gateway Summary Messages configuration parameter, which sends a result set summarizing SQL processing results to the client application.
The access service SendWarningMessages client interaction property replaces the MDI Database Gateway Verbose error messages parameter.
To customize an MDI Database Gateway-compatible version string for use by your client applications, configure the access service Version property. (For more information, see "Version" .)
|
|