SybasePhone Number

Release Bulletin Software Developer’s Kit 15.7 for Microsoft Windows

 

Document ID: DC74865-01-1570-01

Last revised: September 20, 2011

 


Accessing current release bulletin information

A more recent version of this release bulletin may be available on the Web. To check for critical product or document information added after the product release, use the Sybase® Product Documentation Web site.

Accessing release bulletins at the Sybase Product Documentation Web site

  1. Go to Product Documentation.

  2. Select a product and language and click Go.

  3. Select a product version from the Document Set list.

  4. Select the Release Bulletins link.

  5. From the list of individual documents, select the link to the release bulletin for your platform. You can either download the PDF version or browse the document online.

 


Product summary

Sybase Software Developer’s Kit (SDK) version 15.7 is compatible with these operating system configurations.

  • Microsoft Windows x86 32-bit

  • Microsoft Windows x86-64 64-bit

For the most current list of supported operating systems, see the Sybase platform certifications page. For a list of platforms, compilers, and third-party products on which SDK is built and tested, see the New Features Bulletin Open Server 15.7 and SDK 15.7 for Windows, Linux, and UNIX.


Product components

For a list of SDK components and the platforms on which these components are supported, see the New Features Bulletin Open Server 15.7 and SDK 15.7 for Windows, Linux, and UNIX.

Sybase has tested and certified these compilers and linkers for use with Open Client™:

  • Microsoft Visual Studio 2005 32-bit and 64-bit C/C++ Compiler, version 14.00.50727.762.

  • Microsoft Visual Studio 2005 32-bit and 64-bit Executable Linker, version 8.00.50727.762.


Availability with 64-bit libraries

SDK version 15.7 is available in 64-bit versions. Use the -DSYB_LP64 flag when compiling applications that use the 64-bit libraries.


Utilities

bcp, isql, defncopy, cobpre, and cpre are available on Microsoft Windows.


IPv6 support

Sybase SDK version 15.7 on Microsoft Windows platforms supports IPv6.

This is a sample sql.ini entry:

[BARNARD_OS]
master=tcp,barnards.sybase.com,18200
query=tcp,barnards.sybase.com,18200
master=tcp,fd77:55d:59d9:165:203:baff:fe68:aa12,18200
query=tcp,fd77:55d:59d9:165:203:baff:fe68:aa12,18200


Sample files

You can find sample files in the SDK installation directory %SYBASE%\%SYBASE_OCS%\sample.

 


Special installation and configuration instructions

See the Software Developer’s Kit and Open Server Installation Guide for your platform for instructions on how to install the software. For guidelines for installing SDK with other Sybase products on the same server, see “Guidelines for installing SDK with other Sybase products”.

WARNING! If you install both SDK and Open Server™ in the same directory, Sybase recommends that you use the same version and ESD levels. Because SDK and Open Server share files, using different version and ESD levels can cause product failures.

For instructions on configuring your environment, see the Open Client and Open Server Configuration Guide for your platform.

For information about compiling and executing Open Client and Open Server applications, including the sample programs, see the Open Client and Open Server Programmers Supplement for your platform.


Installing EBFs

To ensure that your installation is the most current, Sybase strongly recommends that, after you install SDK version 15.7, you download and install the corresponding latest available EBF. You can download product updates from Sybase Downloads.

To verify that you are using the correct version of SDK, enter the following command to check the version string of the SDK library:

isql.exe -v

A sample SDK version string might be Sybase Client-Library/15.7/A-EBFXXXX ESD #X, where XXXX identifies the Client-Library file and the other SDK files.


Installing SDK 15.7 on top of SDK 15.5

SDK version 15.7 is a shelf replacement for version 15.5. When you install SDK 15.7 into an existing SDK 15.5 directory, version 15.7 files overwrite the 15.5 files. Sybase recommends that you back up your SDK 15.5 directory before you install SDK 15.7.


Running InstallAnywhere and InstallShield Multiplatform installers

Some of the files generated by InstallAnywhere and InstallShield Multiplatform share the same file names. This becomes an issue when you use both InstallAnywhere and InstallShield technologies to install or uninstall products in the same installation directory, because files that are used by both installers are overwritten or removed without warning. Sybase recommends that you do not use InstallShield and InstallAnywhere to install to or uninstall from the same installation directory.


Running different versions of SDK on Windows

In a heterogeneous environment that uses applications built for different versions of SDK, you must explicitly set a path for each version at the Command Prompt window.

In the following example, applications using the 12.5.x products are installed in the d:\ocs-1251 directory, and applications using the 15.7 products are installed in the d:\ocs-150 directory:

  1. To use SDK 12.5.x, open a Command Prompt window and set the SYBASE and SYBASE_OCS environment variables to the 12.5.x directory. For example:

    set SYBASE=D:\ocs-1251
    set SYBASE_OCS=OCS-12_5
    
  2. In the same Command Prompt window, set the PATH environment variable to the 12.5.x directory.

    • On Microsoft Windows x86 32-bit:

      set PATH=%SYBASE%\%SYBASE_OCS%\bin;%SYBASE%\%SYBASE_OCS%\dll;
      %SYBASE%\%SYBASE_OCS%\lib3p;%PATH%
      
    • On Microsoft Windows x86-64 64-bit:

      set PATH=%SYBASE%\%SYBASE_OCS%\bin;%SYBASE%\%SYBASE_OCS%\dll;
      %SYBASE%\%SYBASE_OCS%\lib3p64;%SYBASE%\%SYBASE_OCS%\lib3p;%PATH%
      
  3. To use SDK 15.7, open another Command Prompt window and set the SYBASE and SYBASE_OCS environment variables to the 15.7 directory. For example:

    set SYBASE=D:\ocs-150
    set SYBASE_OCS=OCS-15_0
    
  4. In the same Command Prompt window, set the PATH environment variable. For example:

    • On Microsoft Windows x86 32-bit:

      set PATH=%SYBASE%\%SYBASE_OCS%\bin;%SYBASE%\%SYBASE_OCS%\dll;
      %SYBASE%\%SYBASE_OCS%\lib3p;%PATH%
      
    • On Microsoft Windows x86-64 64-bit:

      set PATH=%SYBASE%\%SYBASE_OCS%\bin;%SYBASE%\%SYBASE_OCS%\dll;
      %SYBASE%\%SYBASE_OCS%\lib3p64;%SYBASE%\%SYBASE_OCS%\lib3p;%PATH%
      

Although you must install different versions in separate directories, you can maintain a single sql.ini file by explicitly passing the address file name to each application, for example:

isql -P -Usa -Sconnect50 -ID:\ocs-150\ini\sql.ini

 


Changed functionality in this version

Changed functionality for Sybase SDK 15.7 is described in the New Features Bulletin Open Server 15.7 and SDK 15.7 for Windows, Linux, and UNIX.

 


Known problems

This section describes all of the known issues that exist in this version.


SDK requires components of Microsoft Visual C++ libraries

[CR #555455] SDK requires components of Microsoft Visual C++ libraries.

Workaround: To use SDK on Microsoft Windows, download and install the Microsoft Visual C++ 2005 Redistributable Package:


Client-Library issues

This section describes the known problems and workarounds, if any, for Client-Library.


Row format suppression

[CR #682932] When using Client-Library with an Adaptive Server® that has enabled row format suppression, an error occurs.

Workaround: Do not enable row format suppression in Adaptive Server if the application has prepared statements that return more than a single row.


Adaptive Server Enterprise ODBC Driver issues

This section describes the known problems and workarounds, if any, for Adaptive Server® Enterprise ODBC Driver.


Bulk insert routines cannot support in-row LOB columns in APL tables

[CR #682086] The bulk insert functionality of the ODBC Driver available with SQLBulkOperations has not been tested with large object (LOB) columns marked for in-row storage on allpages-locked (APL) tables. Using this API against such APL tables could result in errors or corrupted data.

Workaround: Do not mark LOB columns for in-row storage on APL tables if you are using SQLBulkOperations to bulk load data into the tables.


Use SQLSetDescField to set decimal or numeric datatypes

You see an error if you do not specify the precision and scale using the ODBC API method – SQLSetDescField – when retrieving data from numeric or decimal columns in a table.

Workaround: Specify the SQLSetDescField with value types SQL_DESC_PRECISION and SQL_DESC_SCALE.

This code illustrates how to retrieve a numeric column from a table specifying a precision and scale.

/*
Insert values
Execute select statement
*/

/*
Fetch Values
*/

#define ROW_SIZE 10
SQLRETURN sr;
SQL_NUMERIC_STRUCT      g[ROW_SIZE];
SQLLEN  gLen[ROW_SIZE];
SQLINTEGER intVal[ROW_SIZE];
SQLLEN intLen[ROW_SIZE];;

sr = SQLBindCol(hStmt, 1, SQL_C_LONG, intVal, sizeof(SQLINTEGER), intLen);
sr = SQLBindCol(hStmt, 2, SQL_C_NUMERIC, g, sizeof(SQL_NUMERIC_STRUCT), gLen);

SQLHDESC hdesc = NULL;
SQLGetStmtAttr(hStmt, SQL_ATTR_APP_ROW_DESC, &hdesc, 0, NULL);
SQLSetDescField(hdesc, 2, SQL_DESC_PRECISION, SQLPOINTER) 5, 0);
SQLSetDescField(hdesc, 2, SQL_DESC_SCALE, (SQLPOINTER) 2, 0);
SQLUSMALLINT rowStatus[ROW_SIZE];

sr = SQLSetStmtAttr(hStmt, SQL_ATTR_ROW_STATUS_PTR, rowStatus, 0);
for (short i = 0; i < ROW_SIZE; i++)
{
	 memset(&g[i], '\0', sizeof(SQL_NUMERIC_STRUCT));
	 memset(g[i].val, 0, 16);
}
sr = SQLFetch(StatementHandle);

See the Microsoft ODBC API Reference.


Unsupported ODBC features

Adaptive Server ODBC Driver version 15.7 does not support the Kerberos network traffic encryption.


Behavior change when datetime parameter is out of range

When you use Adaptive Server ODBC Driver 15.0 or earlier, or connect to Adaptive Server version 15.0.x or earlier, and the application binds a datetime parameter to an invalid datetime range, such as 01-01-0001, the Adaptive Server ODBC Driver returns error 30122, Invalid datetime field. Year is out of range.

For an Adaptive Server ODBC Driver 15.5 that is connected to Adaptive Server 15.7, this behavior has changed. In the 15.7 versions, Adaptive Server ODBC Driver sends the date to Adaptive Server, and Adaptive Server returns an error. The error code returned is 247, Arithmetic overflow during implicit conversion of BIGDATETIME value 'Jan 1 0001 12:00AM' to a DATETIME field, or something similar.


Adaptive Server OLE DB Provider issues

This section describes the known problems and workaround, if any, for Adaptive Server OLE DB Provider.


Unsupported OLE DB features

Adaptive Server OLE DB Provider 15.7 does not support:

  • Returning OLE DB Error objects (ISupportErrorInfo).

  • DBPROP_INIT_PROMPT property; user is not prompted for missing connection information.

  • IPersist objects to read or write data source, and commands to a storage object.

  • Kerberos encryption of network traffic.


Behavior change when datetime parameter is out of range

Previously, when you use Adaptive Server OLE DB Provider 15.0 or earlier, or connect to Adaptive Server version 15.0.x or earlier, and the application binds a datetime parameter to an invalid datetime range, such as 01-01-0001, the Adaptive Server OLE DB Provider returns error 30122, Invalid datetime field. Year is out of range.

For an Adaptive Server OLE DB Provider 15.7 that is connected to Adaptive Server 15.7, this behavior has changed. In the 15.5 versions, Adaptive Server OLE DB Provider sends the date to Adaptive Server, and Adaptive Server returns an error. The error code returned is 247, Arithmetic overflow during implicit conversion of BIGDATETIME value 'Jan 1 0001 12:00AM' to a DATETIME field, or something similar.


Adaptive Server ADO.NET Data Provider issues

This section describes the known problems and workarounds, if any, for Adaptive Server ADO.NET Data Provider versions 2.157 and 4.157.


Limitation on precision for decimal and numeric datatypes

The Adaptive Server ADO.NET Data Provider currently supports a maximum precision of 26 numbers for a decimal type. The underlying .NET structure and the corresponding Adaptive Server datatypes can handle a higher precision, and attempting to use a precision higher than 26 results in an exception. The Adaptive Server datatypes affected by this limitation are decimal and numeric.


Change in behavior when datetime parameter is out of range

Previously, when you use Adaptive Server ADO.NET Data Provider, or connect to Adaptive Server version 15.0.x or earlier, and the application binds a datetime parameter to an invalid datetime range, such as 01-01-0001, the Adaptive Server ADO.NET Data Provider returns error 30122, Invalid datetime field. Year is out of range.

For Adaptive Server ADO.NET Data Provider that is connected to Adaptive Server 15.7, this behavior has changed. In this case, Adaptive Server ADO.NET Data Provider sends the date to Adaptive Server, and Adaptive Server returns an error. The error code returned is 247, Arithmetic overflow during implicit conversion of BIGDATETIME value 'Jan 1 0001 12:00AM' to a DATETIME field, or something similar.


Installer issues

This section describes the known problems you might encounter when installing SDK.


Installer cannot create installer directory on Microsoft Windows 2008

[CR #595614] On Microsoft Windows 2008, the installer can create the SDK installation directory only when you are logged in as an administrator, even if your role has permission to create directories.

Workaround: Create the installation directory before running the installer.


Cannot navigate the Choose Product Features window with a keyboard

[CR #590282] You cannot use the Tab and arrow keys to navigate the Choose Product Features window of the installation or uninstallation program.

Workaround: Use the mouse to click the Choose Product Features window. This sets the focus on the window and you will be able to use your keyboard.


Console mode incorrectly displays western character sets

[CR #588179] When installing in console mode, some western characters display incorrectly.

Workaround: Before you install SDK:

  1. Open a Command Prompt window.

  2. Run chcp 1252 to change the code page to 1252.

  3. Right-click the Command Prompt window title and select Properties. In the Font tab, select “Lucida Console” and click Ok.

  4. Use the same Command Prompt window to run the installer in console mode.


Feature names are not validated when installing in silent mode

[CR #583979] The installer does not validate feature names specified in the response file when you install in silent mode.

Workaround: Ensure that the specified feature names are correct.

 


Product compatibility and interoperability

This section contains information about products that are compatible with SDK 15.7. For a list of platforms, compilers, and third-party products SDK is built and tested on, see the New Features Bulletin Open Server 15.7 and SDK 15.7 for Windows, Linux, and UNIX.


Interoperability matrix

Table 1 shows the interoperability matrix of SDK, Open Server, Adaptive Server, and Replication Server® that are installed on the same machine. For specific platform information, refer to the respective product certification reports.

Although two or more products can be interoperable, remember that new features introduced in a newer version of a product may not be supported with older versions of the same or other products.

Table 1: Interoperability matrix

SDK

Open Server

Adaptive Server

Replication Server

15.7

15.7

15.5

15.0

15.7

15.5

15.0.x

12.5.x

15.5

15.2

15.1

15.0.1

12.6

Apple Mac OS X Intel

n/a

n/a

n/a

n/a

n/a

n/a

x

n/a

n/a

n/a

n/a

x

HP HP-UX PA-RISC 32-bit

n/a

x

x

n/a

n/a

n/a

x

n/a

n/a

x

x

x

HP HP-UX PA-RISC 64-bit

n/a

x

x

x

x

x

x

n/a

n/a

n/a

n/a

n/a

HP HP-UX Itanium 32-bit

x

x

x

n/a

n/a

n/a

n/a

n/a

n/a

n/a

x

x

HP HP-UX Itanium 64-bit

x

x

x

x

x

x

x

x

x

x

n/a

n/a

IBM AIX 32-bit

x

x

x

n/a

n/a

n/a

x

n/a

x

x

x

x

IBM AIX 64-bit

x

x

x

x

x

x

x

x

n/a

n/a

n/a

n/a

Linux x86 32-bit

x

x

x

x

x

x

x

x

x

x

x

x

Linux x86-64 64-bit

x

x

x

x

x

x

x

x

n/a

n/a

n/a

n/a

Linux on POWER 32-bit

x

x

x

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

Linux on POWER 64-bit

x

x

x

x

x

x

x

x

x

x

n/a

n/a

Sun Solaris SPARC32-bit

x

x

x

x

x

x

x

n/a

x

x

x

x

Sun Solaris SPARC 64-bit

x

x

x

x

x

x

x

x

n/a

n/a

n/a

n/a

Sun Solaris x86 32-bit

x

x

x

n/a

n/a

n/a

x

n/a

x

x

n/a

x

Sun Solaris x86-64 64-bit

x

x

x

x

x

x

x

x

n/a

n/a

n/a

n/a

Microsoft Windows x86 32-bit

x

x

x

x

x

x

x

x

x

x

x

x

Microsoft Windows x86-64 64-bit

x

x

x

x

x

x

n/a

x

n/a

n/a

n/a

n/a

LEGEND: x = interoperable; n/a = product not available or does not work with SDK on that platform.

Note:The SDK interoperability information shown in Table 1 is relevant only if the interoperable products are installed in different %SYBASE% directories. See “Running different versions of SDK on Windows”.


Guidelines for installing SDK with other Sybase products

Follow these guidelines if you are installing SDK on the same machine with other Sybase products:

  • On Microsoft Windows, installing SDK 15.7 on the same machine as Adaptive Server 15.0.x could cause Adaptive Server to fail to start. To configure this configuration, either upgrade Adaptive Server to 15.7, or follow the directions in the Software Developers Kit and Open Server Installation Guide for Microsoft Windows.

  • On Microsoft Windows, use .bat files to ensure that each product is started using the correct SDK version and environment variables.

  • Sybase recommends that you do not mix versions of SDK and Open Server in the same directory. For example, do not install SDK 15.7 in a directory containing Open Server 15.5—in this case, upgrade both SDK and Open Server to 15.7.


SDK and Open Server compatibility

For SDK and Open Server compatibility, the header files included in an application must be the same version level as the library with which the application is linked.


DB-Library compatibility with Client-Library

DB-Library™ compatibility issues include:

  • Support for new features in Open Client or Adaptive Server have been made primarily to the Client-Library API. This includes support for LDAP, SSL, high availability failover, bulk-copies into DOL tables, and so on. For this reason, Sybase strongly recommends that you create all new applications using the Client-Library API. You may also need to migrate, to Client-Library, older applications written in DB-Library that can be run against Adaptive Servers that offer newer technology.

  • Support for new features are not added to the DB-Library.

  • Although DB-Library and Client-Library calls can exist in the same application, Sybase does not test or certify combining the two different APIs. If you must use the two APIs together, make sure the libraries are not only at the same major release level but also at the same ESD level.

For help on converting a DB-Library application to a Client-Library application, see the Open Client Client-Library Migration Guide.

 


Programming issues

This section describes programming issues relevant to Open Client and Embedded SQL™.


General issues

This section describes programming issues for all Open Client products.


Upgrading to a new version

For dynamically linked Open Client applications (dblib, ctlib, and esql), recompile and relink with the SDK libraries that now include “syb” in the library names.

Note:If you have made any changes to the application files, you must recompile.

Ensure that the runtime libraries are for the same major release as the version used to build the application.


System path restriction

Do not create a system path larger than 1K.


Client-Library issues

This section describes programming issues of Client-Library.


Asynchronous operations

To properly exit Client-Library, wait until all asynchronous operations are complete, then call ct_exit. If an asynchronous operation is in progress when ct_exit is called, the routine returns CS_FAIL and does not exit Client-Library properly, even when CS_FORCE_EXIT is used.

Client-Library fully supports asynchronous operations on Windows 2000. See “Asynchronous Programming” in the Open Client Client-Library/C Reference Manual.


Registered procedure notifications

The CS_ASYNC_NOTIFS connection property controls how a Client-Library application receives registered procedure notifications from an Open Server application.

Currently, the Open Server application sends a notification to the client as one or more Tabular Data Stream™ (TDS) packets. However, the client application does not learn of the notification until Client-Library reads the notification packets from the connection and invokes the application’s notification callback.

To trigger the application's notification callback on a connection that is otherwise idle, set CS_ASYNC_NOTIFS to CS_TRUE for ct_poll. In other words, unless the application is actively sending commands and reading results on the connection, it does not receive notifications when CS_ASYNC_NOTIFS is CS_FALSE (the default).


Embedded SQL issues

This section describes programming issues specific to:

  • Embedded SQL/C version 15.0 and later.

  • Embedded SQL/COBOL version 15.0 and later.

For a list of platforms on which Embedded SQL/C and Embedded SQL/COBOL are available, see the New Features Bulletin Open Server and SDK for Windows, Linux, and UNIX.


Sharing Embedded SQL/C objects among multiple threads

By default, Embedded SQL/C connections, cursors, and dynamic statements cannot be shared by multiple threads. The namespace for each of these object types is limited to the currently executing thread; one thread cannot refer to objects that were created by another thread. Objects can be shared by setting the macro CONNECTIONS_ARE_SHARED_ACROSS_THREADS to 1 by using the -D compiler option when compiling the sybesql.c module.

WARNING! If Embedded SQL/C objects are shared by multiple threads, the application programmer must add thread serialization code to ensure that objects associated with a single connection are not used simultaneously by multiple threads.

Normally, dynamic descriptors can be shared by multiple threads. To give each thread its own namespace for dynamic descriptors, when compiling the sybesql.c module, use the -D compiler option to set the macro DESCRIPTOR_SCOPE_IS_THREAD to 1.


Precompiler -p option

Applications that rely on inserting empty strings instead of NULL strings when the host string variable is empty does not work if the -p option is turned on. The persistent bind implementation prevents Embedded SQL from circumventing Client-Library protocol (which inserts NULL strings).


Error or warning prevents with select into statements

You can retrieve multiple rows with a single select into statement by using arrays as output host variables. If no errors or warnings occur, all selected rows are returned up to the limit of the length of the arrays. However, if a truncation, conversion warning, or error occurs, rows are returned only up to and including the row where the error or warning occurred. To ensure receiving all rows, use a cursor and continue fetching until there are no more rows.


Embedded SQL/C sample programs

When you enter an incorrect password, sample programs example1.pc and example2.pc generate incorrect error numbers. You can ignore these numbers.


Embedded SQL/COBOL sample programs

The shared library path for compiling the sample programs must include %COBDIR%\lib and %SYBASE%\%SYBASE_OCS%\lib. The path must also include %COBDIR%\bin and %SYBASE%\bin.

 


Documentation clarifications

The New Features Bulletin for Open Server 15.7 and SDK 15.7 GA includes complete feature descriptions. Installation Guides and Release Bulletins are also updated for version 15.7. In addition, new guides for Perl, Python, and PHP scripting languages are available as a part of SDK 15.7.

For all other information about Open Server and SDK, see the Open Server 15.5 and SDK 15.5 documentation.

 


Technical support

Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you have any questions about this installation or if you need assistance during the installation process, ask the designated person to contact Sybase Technical Support or the Sybase subsidiary in your area.

 


Other sources of information

Use the Sybase Getting Started CD and the Sybase Product Documentation Web site to learn more about your product:

  • The Getting Started CD contains release bulletins and installation guides in PDF format. It is included with your software. To read or print documents on the Getting Started CD you need Adobe Acrobat Reader, which you can download at no charge from the Adobe Web site using a link provided on the CD.

  • The Sybase Product Documentation Web site is accessible using a standard Web browser. In addition to product documentation, you will find links to EBFs/Maintenance, Technical Documents, Case Management, Solved Cases, newsgroups, and the Sybase Developer Network.

    To access the Sybase Product Documentation Web site, go to Product Documentation.


Sybase certifications on the Web

Technical documentation at the Sybase Web site is updated frequently.

Finding the latest information on product certifications

  1. Point your Web browser to Technical Documents.

  2. Click Partner Certification Report.

  3. In the Partner Certification Report filter select a product, platform, and timeframe and then click Go.

  4. Click a Partner Certification Report title to display the report.

Finding the latest information on component certifications

  1. Point your Web browser to Availability and Certification Reports.

  2. Either select the product family and product under Search by Base Product; or select the platform and product under Search by Platform.

  3. Select Search to display the availability and certification report for the selection.

Creating a personalized view of the Sybase Web site (including support pages)

Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.

  1. Point your Web browser to Technical Documents.

  2. Click MySybase and create a MySybase profile.


Sybase EBFs and software maintenance

Finding the latest information on EBFs and software maintenance

  1. Point your Web browser to the Sybase Support Page.

  2. Select EBFs/Maintenance. If prompted, enter your MySybase user name and password.

  3. Select a product.

  4. Specify a time frame and click Go. A list of EBF/Maintenance releases is displayed.

    Padlock icons indicate that you do not have download authorization for certain EBF/Maintenance releases because you are not registered as a Technical Support Contact. If you have not registered, but have valid information provided by your Sybase representative or through your support contract, click Edit Roles to add the “Technical Support Contact” role to your MySybase profile.

  5. Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.

 


Accessibility features

This document is available in an HTML version that is specialized for accessibility. You can navigate the HTML with an adaptive technology such as a screen reader, or view it with a screen enlarger.

SDK documentation has been tested for compliance with U.S. government Section 508 Accessibility requirements. Documents that comply with Section 508 generally also meet non-U.S. accessibility guidelines, such as the World Wide Web Consortium (W3C) guidelines for Web sites.

Note:You might need to configure your accessibility tool for optimal use. Some screen readers pronounce text based on its case; for example, they pronounce ALL UPPERCASE TEXT as initials, and MixedCase Text as words. You might find it helpful to configure your tool to announce syntax conventions. Consult the documentation for your tool.

For information about how Sybase supports accessibility, see Sybase Accessibility. The Sybase Accessibility site includes links to information on Section 508 and W3C standards.

© Copyright 2014, Sybase Inc. - v 7.6