Following is a list of changes to QAnywhere introduced in version 10.0.0.
Client message store ID has changed The client message store ID is now a MobiLink remote ID. Previously it was a MobiLink user name. You do not have to register a remote ID with the consolidated database. However, you still need to register a MobiLink user name with the server message store. If you do not specify a MobiLink user name, it defaults to the client message store ID.
New qaagent options have been provided to manage your MobiLink user names. See:
New ODBC drivers The iAnywhere Solutions ODBC drivers for connecting to Adaptive Server Enterprise and DB2 server message stores have changed.
qaagent -port is removed The -port option specified a port number on which QAnywhere Agent listened for communications from the Listener. This option is no longer required and has been removed. A free port is automatically used.
See -lp option.
See -push option.
See -policy option.
Transaction log is not used or maintained The QAnywhere Agent no longer uses a transaction log or manages its size. As a result, for most applications the client message store should be created using the dbinit -n option, which initializes the database with no transaction log.
See QAMessage class.
In their place, you can use ias_CurrentTimestamp or DATEPART.
See Rule variables.
QAnywhere Central replaced QAnywhere Central has been replaced with the QAnywhere plug-in to Sybase Central. The plug-in provides many enhancements in functionality.
|Discuss this page in DocCommentXchange.
Send feedback about this page using email.
|Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1|