	  Sybase Adaptive Server Anywhere Version 6.0.4 Release Notes
   Copyright (c) 2000 Sybase, Inc. and its subsidiaries. All rights reserved.

  The following components have been updated in this version of SQL Anywhere 
  Studio:
    Adaptive Server Anywhere	Version 6.0.4

				    Contents
				    --------
  Release Notes are added to the top of this file with every maintenance 
  release. For that reason, section numbering starts with 1 at the end
  of the file and works up to the most recent additions at the top of the file.
  6.  Version 6.0.4 Update
  5.  Known Limitations and Problems in Version 6.0.3
  4.  New Features in Version 6.0.3
  3.  New Features in Version 6.0.2
  2.  New Features in Version 6.0.1
  1.  Documentation Corrections

			    6. Version 6.0.4 Update
			    -----------------------

  Version 6.0.4 is a regularly scheduled maintenance release. It contains
  bug fixes to Version 6.0.3, including all big fixes included in Emergency
  Bug Fix releases to 6.0.3 software.

  There are no new features in version 6.0.4.

  The documentation is not updated with this release. It therefore says
  Version 6.0.3.

	       5. Known Limitations and Problems in Version 6.0.3
	       --------------------------------------------------

  5.1  UltraLite: Application recompile necessary for serial-port 
       synchronization

       The UltraLite Developer's Guide states that 6.0.2 UltraLite 
       applications can synchronize with a 6.0.3 MobiLink server. This is not
       true for applications using direct serial-port communication on the Palm
       Computing Platform. If you are using this communication protocol for
       synchronization, you must recompile your applications with the 6.0.3
       libraries.

  5.2  ASA Windows CE: occasional connection failures from SH4 device 
       to network server

       Connection attempts may intermittently fail from a Windows CE client
       application running on a device using the SH4 chip to a network
       server running on another machine. It is recommended that in the TCP/IP
       network communication parameters (CommLinks TCPIP arguments) you specify
       UseUDP=NO, provide a HOST parameter to locate the server, and specify a
       long TIMEOUT parameter. For example:

         CommLinks=tcpip{Host=192.168.55.100;UseUDP=no;Timeout=100}

  5.3  Windows CE: intermittent dropping of serial link

       The serial link between Windows CE and a Windows NT machine
       may be dropped intermittently under some circumstances. In this
       case, any ASA connections across that link are also dropped.
       The Windows CE serial link appears to be prone to failure when 
       the CE device is very busy processing, or when there is a lot of 
       TCP/IP traffic on the link.

  5.4  UltraLite: Windows CE MIPS compiler symbols not found

       If the linker fails to find the symbols __ltd, __eqd, and __ned,
       use the compiler option -QMOC to prevent the compiler from
       referencing these symbols.

  5.5  UltraLite: Windows CE compiler optimization error

       The Windows CE 2.11 version of the SHx compiler has an optimization
       error that affects UltraLite code when multiple aggregate functions are
       used in a select list.  The list() aggregate is the most common source
       of this problem.  The optimization error manifests itself as an
       incorrect field access that can often trigger a data alignment
       exception.  The error is in the peephole optimizer. This optimizer can
       be disabled with the undocumented option -Qdnopipmo.  You can also use
       -Od to disable all optimizations.  You can remove these options when a
       subsequent version of the compiler is released, provided the new
       optimizer correctly compiles the code.  The undocumented option
       -Qdnopipmo may be changed in the future and may not be valid in
       subsequent releases of the SHx compiler.

  5.6  MobiLink: Synchronizing CustDB from Adaptive Server Enterprise

       When using Adaptive Server Enterprise as the consolidated database,
       the MobiLink server does not run the CustDB begin_connection script
       unless the "DDL in transaction" option is set in the database
       used to store the temporary tables.  This database is usually
       called tempdb.  By default, the "DDL in transaction" option is off.
       You must set it explicitly before synchronizing CustDB.

  5.7  Failed ALTER statements may not be completely rolled back

       An ALTER statement that fails may not completely roll back changes
       to CHECK, DEFAULT, or COMPUTE properties made before the failure.

       For example, if the following statement fails on the second CHECK
       condition; the change to column c1 is not rolled back.

         ALTER TABLE A1
         MODIFY c1 CHECK ( <expression-1> )
         MODIFY c2 CHECK ( <expression-2> )

  5.8  Windows CE: Repeated installations
       
       If you install the software over a previous copy of the software on
       Windows CE, you may need to delete the transaction log of the sample
       database (asademo.log). This file is not removed by uninstalling the
       software, and if a new database file (asademo.db) is installed without
       deleting the log file, the new database cannot be used.

  5.9  Windows 3.x and Java

       The Windows 3.x database server supports Java in the database. However,
       the Windows 8.3 file name limitation makes .java and .class file names 
       invalid on this operating system, and so only the asademo.jar file
       is installed for Windows 3.x machines.

       In order to install the demo examples, you shold run jdemow.sql rather 
       than jdemo.sql.

  5.10 SQL Remote and Java objects

       To extract a database that contains Java objects for SQL Remote,
       use the dbxtract command line utility instead of Sybase Central.

       You should use the internal reload option (the default) when carrying
       out this extraction.

  5.11 Windows CE: Example code requires Visual C++ 6.0
   
       The Windows CE example code installed into the cxmp directory contains
       the odbcdemo.dsp and dcur.dsp project files. In order to support the
       new version of the Windows CE operating system, these files require
       Visual C++ 6.0.

  5.12 Installing InfoMaker 7.0

	      System Requirements
	      -------------------
	      - 486 PC or higher
	      - 16 MB RAM (24 recommended)
	      - 45 MB hard drive space, depending on configuration
	      - CD ROM drive
	      - VGA monitor
	      - Windows 95 or Windows NT 3.51 or higher for development
	      - Windows 95, Windows NT, or Window 3.x  for deployment

	      Installing on NT 4.0
	      --------------------
	      You must have Administrator privileges to fully install this 
	      product on NT 4.0.

		  4.  New Features in Version 6.0.3
		  ---------------------------------
  
  For a more complete description of any of the new features in this release,
  see Chapter 1 of the New Features and Upgrading Guide.

  To look up new features in the online documentation, enter the topic title 
  in the index. Topics are indicated by =>.

  New Adaptive Server Anywhere features
  =====================================

  o   Combined stored procedure and Java debugger -- The Java debugger that was 
      provided in previous releases has been upgraded. The new version of the
      debugger is able to debug not only Java classes within the database, but
      also SQL stored procedures and triggers.

      => Debugging Logic in the Database.  

  o   Cache size changes -- The default initial cache size for the database 
      server is now computed from the database file sizes and the machine
      physical memory. A specific initial cache size can be specified as a
      percentage of the physical memory of the machine rather than as an
      absolute amount, for easier deployment to a variety of environments. On
      Windows NT, and Windows 95/98, the cache grows if it is exhausted or if
      Java requires more memory, or if an internal algorithm suggests a
      performance benefit. Previously, the server would give a "Fatal Error:
      dynamic memory exhausted" error if cache was exhausted.
      
      => Cache size.

  o   Read-only databases -- You can designate a database as read only when
      you start a database server. This feature makes deployment of databases
      on read-only media, such as CD-ROMs, more straightforward.

      The ReadOnly database property returns ON for read-only databases, and
      OFF for databases that are not being run in read-only mode.

      => -r command-line option.

  o   Computed column extensions -- New flexibility has been added to computed 
      columns.  You can now add computed columns to non-empty tables, and
      change the expression associated with a computed column. Computed columns
      are recalculated in a number of circumstances to ensure that the values
      are reliable.

      => Defining computed columns, and When computed columns are recalculated.

  o   Support for the euro -- Collations have been added that include the euro 
      currency symbol. These collations are the 1252LATIN1 and ISO9LATIN1
      collations.

      => The 1252LATIN1 collation, and The ISO9LATIN1 collation.
   
  o   Additional collations -- Other collations have been added to the list of
      supplied collations, including 852POL (OEM Code Page 852 (Latin 2), with
      Polish ordering), 1250POL (Windows Latin2 code page 1250 with Polish
      ordering), 1250Latin2 (Windows Latin2 Code page 1250). 932JPN (Japanese),
      936ZHO (similar to EUC_CHINA), and 950TAI (similar to EUC_TAIWAN).

      => Supplied collations.

  o   New Windows CE platforms -- The SH4 and ARM processors are now supported 
      under Windows CE 2.1x.

      => System requirements.

  o   ALTER TABLE extensions -- The ALTER TABLE statement has been extended to 
      provide SQL/92-compliant clauses to set and drop defaults on columns.
      These clauses are an alternative to the existing MODIFY clause.

          ALTER column-name SET DEFAULT default-value
          | ALTER column-name DROP DEFAULT

      => ALTER TABLE statement.

  o   LOAD TABLE extensions -- You can now load specific columns of a table using 
      the LOAD TABLE statement. A new CHECK CONSTRAINTS option has been
      introduced to address rebuild issues.

      => LOAD TABLE statement.

  o   Easier connections across firewalls -- A set of communications parameters 
      has been introduced to allow easier connections across firewalls.

      => Connecting across a firewall.

  o   BACKUP statement extended -- The MATCH keyword has been introduced to allow
      renaming of the backup copy of the transaction log to a filename of the
      form YYMMDDnn.log. If you use this keyword, you can execute the same
      statement multiple times without writing over data.

      => BACKUP statement.

  o   Fast table truncation -- A faster form of the TRUNCATE TABLE statement is 
      provided for tables that meet certain criteria. As this fast truncation 
      carries out a COMMIT as a side effect, a new option has been introduced 
      to disable it. By default, the option is set to ON; it should be set to 
      OFF for maximum compatibility with older versions of the software.

      => TRUNCATE_WITH_AUTOCOMMIT option, and TRUNCATE TABLE statement.

  o   Easier unload and reload -- The dbunload utility has been enhanced (-ar
      command-line option) to allow a single-step unload and reload of a
      database that can be used whether or not your database is involved in
      replication.

      => Unload utility options, and Unloading and reloading a database.

  o   Temporary file location -- The database server checks for a new environment
      variable, ASTMP, when deciding on the location of the temporary file.
      This allows you to use directories other than system temporary
      directories for the temporary file.

      => ASTMP environment variable.

  o   New system procedures -- New system procedures allow DBA users to override some
      database server command-line options (sa_server_option), and to flush the
      database server cache (sa_flush_cache).

      => System and catalog stored procedures.

  o   Character set translation tuning -- You can control the application locale 
      used in character set translation for an individual connection using the
      new Charset connection parameter.

      => CharSet connection parameter.

  o   Re-organized Performance Monitor statistics -- The statistics made available 
      to the Windows NT Performance Monitor have been organized into areas.
      Some statistics have been added, and ones of little use have been
      removed.

      =>  Monitoring database statistics from the Windows NT 4.0 Performance
      Monitor.

  o   Database properties from the utility database -- You can now execute SELECT
      statements, with no tables, against the utility database. This is
      primarily of use for retrieving database and connection properties.

      => Using the utility database.

  o   New database properties -- The following properties are available using the
      property function.  IsNetworkServer Returns YES if connected to a network
      database server, and NO if connected to a personal database server.

      => Server-level properties.
    
      o   DefaultCollation -- You can use the new DefaultCollation property to
          find the default collation to be used when creating a database.

          => Finding the default collation, and Server-level properties.

  o   Support for some JDBC 2.0 functions in internal JDBC -- The internal 
      server-side JDBC driver now supports functions from the JDBC 2.0
      interface.  Server-side Java applications can now use features such as
      such as scrollable, updatable result sets and batch updates. A side
      effect is that you can now access result sets from Java methods from
      Interactive SQL.

      => Server-side JDBC features.

  o   Updating Java columns -- The restriction that set methods in UPDATE 
      statements must return a non-void data type has now been removed. For
      example, the following statement now works, even if the method setName()
      returns void.

          UPDATE Product
          SET JProd.setName( 'Tank Top' )
          WHERE ID = 302

      => Updating Java objects.

  o   Using Java methods that return void as SQL expressions -- You can use Java 
      methods that return void as SQL expressions. These methods return this,
      that is, the object itself, to the SQL calling environment.

      => Return value of methods returning void.

  o   Using the main method in Java classes -- You can now execute a main
      method of a Java class from SQL.

      => The main method.

  o   User-defined functions using Java classes -- You can wrap a Java method
      in a SQL user-defined function.

      => CREATE FUNCTION statement.

  o   Extensions to stored procedures using Java methods -- You can use OUT and
      INOUT parameters in stored procedures that are wrappers for Java methods.

      => Returning values from Java via stored procedures.

  o   Multi-threaded Java classes in the database -- Support has been added for
      the package java.lang.Thread.

      => Using threads in Java applications.

      => Supported Java packages.

  o   File access from Java -- Support has been added for all the classes in the 
      package java.io, including those that enable file access from classes in
      the database.  For security reasons, a new option has been introduced,
      which must be set by the DBA to enable this feature.

      This feature is supported on Windows NT only.

      => JAVA_INPUT_OUTPUT option.

  o   CONVERT function extensions -- The date and time styles supported by the 
      CONVERT function have been extended.

      => CONVERT function.

  o   Database server startup dialog -- On 32-bit Windows operating systems, if you
      start a database server with no arguments, a window appears where you can
      specify a database file and additional command-line parameters.

      => Starting the server.

  o   Console utility enhancements -- The Console utility has been enhanced to 
      provide more information concerning connections and server performance.

      => The Console utility.

  o   dbtran utility enhancements -- The dbtran command-line utility permits 
      filtering of the transaction log operations to isolate subsets of
      operations.

      => The DBTRAN command-line utility.

  o   dblog utility enhancements -- The dblog utility now displays additional 
      summary information, including offset information.

      => The DBLOG command-line utility.

  o   dbspawn utility enhancements -- The dbspawn utility has a -f command-line 
      switch to force a server to start even if one is already running. This
      switch uses a ForceStart connection parameter, used only by the
      db_start_engine Embedded SQL function.

      => The Spawn utility, and db_start_engine function.

  o   Replication Agent runs as a daemon -- On UNIX operating systems, you can run 
      the Replication Agent as a daemon by supplying the -ud command-line
      option.

      => The Log Transfer Manager.

  o   TCP/IP local machine connections -- You can now use TCP/IP to connect from a
      client application to a database server running on the same machine.
      This is of most use for Windows 3.x applications connecting to a Windows
      95/98 database server on the local machine, where TCP/IP connections are
      faster than the DDE protocol, which has been the recommended method until
      now.

      => Windows 3.x applications on Windows 95/98 or Windows NT.

  o   HTML Help format -- Online documentation for Windows NT and Windows 95/98 
      is now available in HTML Help format. HTML Help is the standard online
      documentation format with new versions of Windows. Sybase Central
      documentation remains in Windows Help (WinHelp) format. You must
      have administrator privileges to install HTML Help.

      By default, the HTML Help version of the online documentation is
      installed if you have Internet Explorer version 4.0 or later installed,
      or if you have HTML Help already installed. Otherwise, WinHelp format is
      installed. The content of the online documentation is the same in each
      format.

      If you prefer to use WinHelp, you can select the option to do so from the
      Adaptive Server Anywhere setup program.

  New UltraLite and MobiLink features
  ===================================

  o   Windows CE 2.11 and Visual C++ 6.0 -- The development tools now use 
      Microsoft Visual C++ 6.0 to target Windows CE version 2.11. Previous
      releases of Windows CE are no longer supported. You may be able to
      develop applications for older versions of Windows CE, but this
      application of the UltraLite technology is not supported. The initial
      release of UltraLite used Microsoft Visual C++ 5.0 to target Windows CE
      version 2.0.  File-based persistent stores UltraLite applications under
      Windows CE and Windows NT, 95, and 98 now use a file-based persistent
      storage mechanism.  Under Windows CE, the use of a file improves
      performance of the UltraLite database by improving the access times for
      row data. The Windows NT, 95, and 98 version uses a read-write memory
      mapped file as its file caching mechanism.

  o   New data types -- Real and double data types are now fully supported by 
      both UltraLite and MobiLink technologies.  ODBC 3.51 The MobiLink Server
      now uses ODBC 3.51, in common with the rest of Adaptive Server Anywhere.
      Version 6.0.2 of the MobiLink server used ODBC 2.0.

  o   User settable BAUD rate -- You can now specify the baud rate for 
      communication via serial streams with Palm devices. Previously, the only
      available speed was 19200 BAUD. This value remains the default.

      => Adding serial synchronization to your Palm application.

  o   Optional user column -- The new_row_cursor and old_row_cursor scripts allow 
      you to optionally include an extra column in your SELECT statement to
      hold the user name. If your SELECT statement contains one extra column,
      the first column is automatically filled with the user name.

      => new_row_cursor cursor script, and old_row_cursor cursor script.

  o   Character set translation -- The MobiLink synchronization server now translates 
      all uploaded characters to Unicode and passes them to the consolidated
      database using the Unicode ODBC API. Conversely, it translates all
      downloaded characters from Unicode to the character set of your UltraLite
      application. Character set translation within the consolidated database
      server can influence the results, but the new system allows more
      consistent behavior across multiple platforms.  Free technical advice
      Technical advice and limited support is available for free on the
      newsgroup sybase.public.sqlanywhere.ultralite. The host for this
      newsgroup is forums.sybase.com.

  o   MobiLink server runs as a Windows NT service When you run the MobiLink 
      server as a service, you can configure it to continue running when you
      log off the Windows NT workstation.
      
      => Running the MobiLink server as a Windows NT service.

  o   DB2 setup scripts provided To make it easier to use IBM DB2 as a 
      consolidated database, a DB2 setup script has been added to the available
      set scripts.  
      
      => Creating a consolidated database.

  New SQL Remote features
  =======================

  o   FTP and SMTP/POP support on UNIX -- The range of message systems supported 
      on UNIX operating systems has been expanded to include FTP and SMTP/POP.
      
      For a listing of supported operating and message systems, see Supported
      Platforms and Message Links.

  o   Message link options stored in the database The message link parameters that
      control SQL Remote behavior over each message system can now be stored in
      the database as opposed to the registry. This simplifies deployment and
      management issues related to message link parameters.  
      
      => Setting message type control parameters, SET REMOTE
      OPTION statement, and sp_link_option procedure.

  o   Date and time replication formats You can now specify database options
      that instruct SQL Remote what format to use when replicating dates and
      times.  These options are SR_time_format, SR_date_format, and
      SR_timestamp_format.  

      => Replication of dates and times, and SQL Remote options.

  o   Message Agent and SQL Remote Open Server run as a daemon -- On UNIX 
      operating systems you can run these applications as a daemon using the
      -ud command-line option.  
      
      => The Message Agent, and The SQL Remote Open Server.

  o   Easier unload and reload of Adaptive Server Anywhere databases -- The 
      dbunload utility has been enhanced (-ar command-line option) to allow a
      single-step unload and reload of a database that can be used whether or
      not your database is involved in replication.

      => Unload utility options, and Unloading and reloading a database.

  o   Enhanced dblog output -- The dblog utility now displays additional 
      summary information, including offset information.

      => The DBLOG command-line utility.

  o   dbtran utility enhancements -- The dbtran command-line utility permits 
      filtering of the transaction log operations to isolate subsets of
      operations. This is of particular use to SQL Remote administrators.

      => The DBTRAN command-line utility.

  Behavior changes
  ================
   
  The following are behavior changes from previous versions of the software.

  o   SQL Remote behavior changes -- For a list of SQL Remote behavior changes, see
      Behavior changes.

  o   UltraLite behavior changes -- For a list of UltraLite behavior changes, see
      Behavior changes.

  o   Debugger replaced -- The Java debugger included in previous versions of this
      software has been replaced with a more comprehensive and powerful stored
      procedure and Java debugger.

  o   Adding columns with default values -- When an added column has a default 
      value, the entire column is populated with the default. In previous
      releases, the column was populated with NULL.  Permissions of referential
      integrity actions When changes are made to a primary table, referential
      integrity actions such as cascading deletes or updates can take place on
      a secondary table. These actions are implemented using system triggers.
      The triggers now execute with the permissions of the owner of the
      secondary table. Previously, they executed with permissions of the owner
      of the primary table. The new behavior means that cascaded operations can
      take place between tables with different owners, without additional
      permissions having to be granted.

  o   datediff, MONTHS, and YEARS functions -- The number of months between two 
      dates is now calculated as the number of first-of-the-months between the
      dates.  For example, the difference between January 25 and February 2 is
      1; the difference between January 1 and January 31 is 0. The number of
      years is now calculated as the number of first-of-the-years between the
      dates.

      This changes the results of these functions by one number, in some cases.
      The change was made for compatibility with Adaptive Server Enterprise.
      For the smaller time units there are overflow values to the DATEDIFF
      function that are now imposed. Previous versions of the software gave
      incorrect answers if the limit was exceeded.

      => DATEDIFF function.

  o   Starting the database server with no arguments -- In previous releases, 
      a command such as the following:
          dbeng6
      would display the usage text for the database server. On 32-bit Windows
      operating systems, it now displays a window where you can specify a
      database file and additional command-line parameters.

  o   Default page size -- The default page size for databases is now 2048 bytes. 
      This choice is a better choice for many users.

  o   Default database collation -- The default collation used when creating 
      databases has changed. The default depends on your operating system
      settings.

      => Finding the default collation.
   
  o   SQL Preprocessor default collation -- If no collation is explicitly specified, 
      the Embedded SQL Preprocessor now uses locale information to choose a
      default collation. If the locale information is unavailable, then
      850LATIN1 will be used. The collation used is reported following the
      banner. Previous behavior was to use 850.

      =>  The SQL preprocessor.

  o   Enforced server name length -- The server name is checked on startup, and is
      truncated to a maximum value of 40 characters. On NetBIOS, it is
      truncated to 16 characters. From the client side, the value of the
      EngineName parameter is also truncated to 40 characters.

      => EngineName connection parameter.

  o   Agent connection parameter -- The Agent connection parameter behavior has 
      been changed. The meaning of this parameter changed from version 5 to
      version 6, as the need for the dbclient executable was removed. The
      parameter meaning has changed to be more useful in a Version 6
      environment.

      => Agent connection parameter.

  Upgrade issues
  ==============

  Version 6.0.3 software works with older databases. There is no need to
  upgrade your database in order to continue working with existing
  applications. There is no need to upgrade your database in order to use
  many of the new features, including new SQL statements and statement
  extensions.

  If you wish to use new database options, you must upgrade your database.
  You can upgrade a database using the Upgrade utility or the ALTER DATABASE
  statement.

  Version 6.0.3 database servers support connections from Version 6.0.0, 
  6.0.1, or 6.0.2 client applications.
  Version 6.0.0, 6.0.1, and 6.0.2 database servers support connections from
  version 6.0.3 clients, as long as the clients do not set the new UseUDP 
  communication parameter to OFF (ON is the default).

  => The Upgrade utility, and ALTER DATABASE statement.

  For information on SQL Remote upgrade issues, see New features in version
  6.0.3. For information on UltraLite upgrade issues, see Upgrade issues.
  Behavior changes


		  3.  New Features in Version 6.0.2
		  ---------------------------------

  For a more complete description of any of the new features in this release,
  see Chapter 2 of the New Features and Upgrading Guide.

  To look up new features in the online documentation, enter the topic title 
  in the index. Topics are indicated by =>.

  New features include:

  o  UltraLite deployment option -- With this new technology you can
     build and use relational databases and database applications on the 
     PalmPilot and Windows CE operating systems. The UltraLite database
     engine takes as little as 30K of memory.

     => UltraLite Developer's Guide

  o  Performance enhancements -- Many aspects of Adaptive Server Anywhere
     performance are improved in this version of the software.  
     
  o  SQL Remote performance enhancements -- A major enhancement 
     improves replication turnaround times.

     => Tuning Message Agent performance.

  o  Backup and Restore SQL statements -- Adding BACKUP and RESTORE as SQL
     statements provides server side backup and automation of backups using 
     SQL scripts and backup to tape.

     => BACKUP statement.

  o  Security features -- New security features have been added.

     o Database administrators can keep track of activity
     performed on a database by turning on the AUDITING option.

     => Auditing database activity.

     o Database administrators can specify a minimum password length, 
     to discourage easily discovered passwords. 

     => MIN_PASSWORD_LENGTH option.

  o  DBPing command-line utility for locating servers.

     => The DBPing utility.

  o  Database connections over TDS, including connections from 
     Java applications over jConnect, can start a database on a 
     server.

     => Supplying a URL for the server.

  o  From Java applications, you can now retrieve objects from a table 
     and insert objects into a table without the explicit serialization 
     and deserialization required in previous releases.

     => Inserting and retrieving objects.

  o  The ODBC driver has been updated to ODBC 3.51. This
     version of ODBC includes support for Unicode applications.

     => ODBC conformance.

  o  Previous releases have permitted some multi-table queries with 
     ambiguous join clauses. In the present release, you can set an 
     option to disallow such queries.

     => EXTENDED_JOIN_SYNTAX option.

  o  Options have been added to the administration utilities.

     o  dbtran -- If you use the new -d switch, dbtran puts each operation as
     it occurs in the transaction log file. This makes transaction log output
     easier to read. This has been added primarily for auditing purposes.

     => The DBTRAN command-line utility.

     o  dbtran -- You can run dbtran against a running database server instead
     of against a log file. This feature has been added to increase the
     security of the transaction log--there is now no need to access the
     transaction log directly.

     => The DBTRAN command-line utility.

     o LTM and SQL Remote Message Agents -- New command-line options allow you
     to tune message logging from these utilities.

     => The Log Transfer Manager, and The Message Agent.

     o  New LTM options -- New command line options enable you to replicate
     only backed up transactions (backup_only), and to shut down as soon as all
     data is replicated (continuous).

     => The LTM configuration file.

  o  Network or Personal Server -- To detect whether you are connected to
     a network server or a personal server, use
        select property('IsNetworkServer')
     This returns YES if connected to a network server, and NO if connected
     to a personal server.
     


		  2.  New Features in Version 6.0.1
		  ---------------------------------

  For a more complete description of any of the new features in this release,
  see Chapter 3 of the New Features and Upgrading Guide.

  New features include:

  o   Windows CE Edition -- You can now use Adaptive Server Anywhere databases 
      on Windows CE. Also, you can use existing applications such as 
      Sybase Central to manage your Windows CE database from a desktop 
      computer. 
      This is a complete database server for small devices that use the 
      Windows CE operating system, and includes SQL Remote replication using
      ActiveSync synchronization.

  o   Remote data access --  You can access data from external data sources, 
      including Adaptive Server Anywhere databases and other databases,
      from a single connection.

  o   Sybase Central Java Edition -- Management of remote data access, and
      database management from platforms other than Windows, is made possible
      using the Java Edition of Sybase Central. This feature is not included 
      in the package.
      
      To obtain Sybase Central (Java Edition), go to the following location
      at the Sybase Technical Library:
	 http://techinfo.sybase.com/css/techinfo.nsf/DocID/ID=47872 

      When connecting to databases from Sybase Central Java Edition, it 
      is recommended that you use the JDBC (jConnect) connection option,
      rather than the ODBC (JDBC/ODBC bridge) option.

  o   Character set translation -- Character set translation has been added 
      to translate strings automatically between different character sets as 
      data is passed between client applications and the database server.
      This enables more flexibility in mixed character-set environments.

  o   New Java features

      o	  You can use standard UPDATE statements to update a field in a 
	  Java column.
      o	  You can install compressed JAR and ZIP files into a database.
      o	  You can wrap a Java method in a stored procedure to return
	  result sets from a Java method to the calling environment.
      o   New standard internal connection -- The new method of obtaining
          a connection from internal Java classes corresponds to 
	  proposed Java standards.

  o   New SQL Remote features

      o	  The SQL Remote Message Agent can be made to run in a minimized
	  window using the -q command-line switch.
      o	  New flexibility has been built into the methods for polling
	  for incoming messages and requesting that lost messages be
	  resent.
      o	  The Message Agent for Adaptive Server Enterprise has a new method 
	  for keeping the size of the stable queue small.

  o   Additional Features

      o   Extended Message statement and message callbacks -- These allow 
	  applications to receive and process messages from the database server
	  during query processing.
      o   More control over operating system threads -- The -gx command-line
	  switch allows you to alter the number of operating system threads
	  in use.
      o	  Connection property system procedures -- These allow you to obtain
	  more information about connection information and database settings.


		     1. Documentation corrections
		     ----------------------------

  The printed documentation is not updated with each maintenance release.
  The online documentation is updated with each maintenance release, and
  is more current and more reliable than the printed documentation.  In
  addition to documenting the new features, several changes have been made to
  the documentation to improve it, or to provide information that was
  previously missing.

  o   The MultiByteCharSet new feature, described in the New Features section
      of the online documentation is not present in the software.

  o   The UltraLite Developer's Guide states that 6.0.2 UltraLite applications
      can synchronize with a 6.0.3 MobiLink server. This is not true for
      applications using direct serial-port communication on the Palm Computing
      Platform. If you are using this communication protocol for 
      synchronization, you must recompile your applications with the 6.0.3
      libraries.
      
  o   Corrections -- A major review of the documentation for technical
      correctness has led to many small changes throughout the online manuals.  

  o   Backup and Recovery rewrite -- The Backup and Recovery chapter in the
      online User's Guide has been rewritten.

      => Backup and Data Recovery.

  o   International Languages and Character Sets rewrite -- Over recent
      releases, many features have been added for better national language
      support. The online version of this chapter has been rewritten with 
      a focus on using locales to manage language and character set issues.

      => International Languages and Character Sets.

  o   Additional deployment information -- Material describing how to create
      and use a silent install of Adaptive Server Anywhere has been added
      to the online chapter on deployment.

      => Using a silent installation for deployment.
