Switch to standard view 
  Sybase logo
 
 
 



Release Bulletin InfoMaker® 11.1

Release Bulletin InfoMaker® 11.1

 

Document ID: DC33824-01-1110-01

Last revised: November 15, 2007



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 Manuals Web site.

Accessing release bulletins at the Sybase Product Manuals Web site
  1. Go to Product Manuals.

  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. Select the link to the release bulletin. You can either download the PDF version or browse the document online.



Product summary

Enclosed is Sybase InfoMaker® version 11.1, which is compatible with the following platform and operating system configurations:

InfoMaker 11.1 builds 32-bit applications, but supports deployed applications in both 32-bit and 64-bit environments on the Vista operating system. For more information about using InfoMaker on the Vista operating system, see “Vista support”.

The Microsoft Windows 2000 operating system with Service Pack 4 is supported for deployment.


DataDirect database drivers

The PB DataDirect ODBC drivers and OLE DB data providers from DataDirect Technologies have been removed from InfoMaker 11.0 and later releases. If you want to continue to use these drivers and data providers, you must obtain them from DataDirect Technologies.



Special installation instructions

InfoMaker 11.1 is available as a full install and as an update for InfoMaker 11.0 users.


Before you install

Before you install this release, shut down any applications running on your system. Restart your system after all the installations are complete.

The executable files in this release extract setup files to the folder specified by your TMP environment variable, or the folder specified by your TEMP environment variable if TMP is not defined or specifies a directory that does not exist. Make sure you have enough disk space on the drive containing this folder before beginning the installation.

To specify an alternative location, open the System Properties dialog box from the Windows control panel, select the TMP user variable (or TEMP if TMP does not exist) on the Environment or Advanced tab page, and specify a location that has sufficient space.


Installing InfoMaker 11.1 using the full install

If you are installing InfoMaker 11.1 using the full install, the Installation Guide for InfoMaker 11.0 on the Sybase Product Manuals Web site describes how to install the software.


Updating InfoMaker 11.0 to InfoMaker 11.1

You can download the InfoMaker 11.1 update from the InfoMaker page of the Sybase EBFs/Maintenance site (select “in all months” and click the GO button if you do not see the 11.1 release). Download the zip file and extract its contents to a temporary directory on your computer using the “Use folder names” option.

To install the InfoMaker 11.1 update, you must have already installed version 11.0 of InfoMaker on your computer.

To update InfoMaker:
  1. Create a backup by copying the contents of your Sybase\Shared\PowerBuilder directory to another directory.

  2. If you use the Internet plug-ins, back up the Internet Tools directory in the Sybase\InfoMaker 11.0 directory. Also, back up other files that contain information you do not want to lose, such as PBLs, database files, and .INI files.

  3. Run the setup.exe file in the InfoMaker directory extracted from the zip file.



Changed functionality in this version

This section lists new features and changed functionality in this version of InfoMaker. The New Features section of the InfoMaker Help file also describes features added in this release. To view this Help, from the InfoMaker menu, select Help>Welcome to InfoMaker 11.1.


Vista support

The InfoMaker 11.1 development environment has been tested on the Microsoft Vista operating system using both the 32-bit and 64-bit versions of the Vista Business Edition. Application deployment has been tested using the same Vista editions. The InfoMaker development environment and applications created using InfoMaker run as 32-bit applications on both platforms.

Microsoft has established two separate levels of its Windows Vista Logo Program for Software: Certified for Windows Vista and Works with Windows Vista. InfoMaker 11.1 satisfies the Works with Windows Vista requirements. Applications built with InfoMaker can be designed to meet the Certified for Windows Vista requirements. For more information about these requirements, see the Microsoft Web site.


User accounts and administrative privileges

One of the most significant changes in Windows Vista is the introduction of User Account Control (UAC). UAC is the mechanism Vista uses to limit the default privileges users run with on Vista. Limiting these privileges is intended to make it less likely that a user’s actions affect the configuration of the system or other users’ state and settings.

Standard users (members of the Users group) have restricted privileges. They cannot install most applications, change system settings, or perform most other administrative tasks.

Administrators have elevated privileges. When a user who is a member of the Administrators group (or another group with elevated privileges) logs on to a Vista computer, the interactive login process creates a restricted token in addition to the token that describes the administrator’s elevated privileges. The restricted token has the privileges of a standard user and is used to create the interactive desktop and Windows Explorer session.

The elevated privileges for the user are still available when needed. If the user attempts to perform an operation that requires administrative privileges, the user is prompted to authorize the operation.

When the user double-clicks an icon or selects it from the Start menu, the process inherits the restricted token. If the application is marked as requiring elevated privileges in a manifest file, UAC prompts the user for authorization to run with those privileges. For more about manifest files, see “Manifest files”.

You can start an application with administrative privileges by right-clicking it in the Start menu or Explorer and selecting Run As Administrator from its pop-up menu.


Installing InfoMaker

You must have administrative privileges to install InfoMaker on Windows Vista. To ensure that the installation completes successfully, right-click the setup.exe or autorun.exe file and select Run as administrator.


Running InfoMaker

InfoMaker typically writes to multiple files in the Program Files directory, including im.ini, IM110_sysam.properties, and code examples, tutorial, and demo database files. If an application is run without administrative privileges, Vista restricts it from writing to the HKEY_LOCAL_MACHINE subtree in the registry, the Program Files directory, and the Windows directory. Instead, changes are written to a writable area in the registry and to the user’s local directory. This is referred to as virtualization.

For example, if you start InfoMaker without administrative privileges, the im.ini file is written to Program Files\Sybase\InfoMaker 11.0\im.ini in the C:\Users\<your_name>\AppData\VirtualStore directory.

To avoid the issues that would result from this behavior, on Vista, you must start InfoMaker 11.1 with administrative privileges by right clicking im110.exe in the Start menu or Explorer and selecting Run as administrator from its pop-up menu.


Manifest files

If you want to deploy an application to the Windows Vista operating system that meets the certification requirements of the Windows Vista Logo program, you must follow User Account Control (UAC) guidelines. The executable file must have an embedded manifest that defines the execution level and specifies whether access to the user interface of another window is required. The Vista Application Information Service (AIS) checks the manifest file to determine the privileges with which to launch the process. For more information about creating manifest files, see the Microsoft Web site.


Signed DLLs

When you run an application on Vista, Vista warns you if the application uses any DLLs that have not been signed with an Authenticode certificate. If you want to deploy your application with Windows Vista Logo certification, all the DLLs that you distribute with it must be signed. InfoMaker runtime DLLs, and all other InfoMaker DLLs, are signed.


Windows Help files

Windows Vista does not distribute the WinHlp32.exe file required to open Windows Help files such as the imhlp110.hlp file used in InfoMaker. To use .hlp files, you need to download a special Vista version of WinHlp32.exe from the Microsoft Web site.

Compiled HTML Help (.chm) files are supported, but you need to edit the Windows registry to enable a Help macro that supports links from the imhlp110.hlp file to the imman110.chm file. If you do not edit the registry, the “For your information” links at the bottom of many topics in the Windows Help display an error.

You also need to edit the registry if you need to run Windows Help files at a remote location on an intranet.

Registry reflection on 64-bit Windows 64-bit versions of Windows use registry reflection to maintain a 32-bit registry view and a 64-bit registry view. On 64-bit Windows, configuration information related to 32-bit applications is stored in the HKEY_LOCAL_MACHINE\Software\WOW6432node registry hive.

To enable Windows Help macros and remote access on Vista:
  1. Create the following registry key.

    On 32-bit Windows:

    		HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WinHelp
    	

    On 64-bit Windows:

    		HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432node\Microsoft\
    	WinHelp
    	
  2. Add a new DWORD value with the name AllowProgrammaticMacros and the value 1.

  3. Add a new DWORD value with the name AllowIntranetAccess and the value 1.

You can also add this support by saving the following lines in Notepad to a file with the extension .reg and importing it into the registry.

On 32-bit Windows:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WinHelp]
"AllowProgrammaticMacros"=dword:00000001
"AllowIntranetAccess"=dword:00000001

On 64-bit Windows:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432node\Microsoft\WinHelp]
"AllowProgrammaticMacros"=dword:00000001
"AllowIntranetAccess"=dword:00000001

Microsoft prohibits the distribution of WinHlp32.exe with deployed applications. If your application uses .hlp files, you should provide your users with instructions on how to download WinHlp32.exe. For more information, see the Microsoft support site.


Drop-down calendar properties

The Vista operating system does not support several properties for the drop-down calendar in a column. The following properties are not supported on Vista: Calendar BackColor, Calendar TextColor, Calendar TitleBackColor, Calendar TitleTextColor, and Calendar TrailingTextColor.


Saving as PDF

To save as PDF in the Report painter, environment, you must be running InfoMaker as an administrator (see “Running InfoMaker”) and the correct versions of Microsoft PostScript printer driver files must be available in the drivers directory when a file is saved as PDF using the Distill method.

If you (and your users) have installed a PostScript printer, the PostScript driver files required to create PDF files are already installed. Typical locations are C:\WINDOWS\system32\spool\drivers\w32x86 on Windows XP, C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_xxxxxxxx\, where xxxxxxxx is a system-specific identifier, in the I386 subdirectory on 32-bit Vista and the Amd64 subdirectory on 64-bit Vista. You must use the version of these files that is appropriate to the system where the PDF file is created. Copy the files to the Shared\PowerBuilder\drivers directory.

If you have never installed a PostScript printer, you can use the Printers and Faxes option in the Windows control panel to install a generic PostScript printer. If the Microsoft PSCRIPT5.DLL has never been installed, you may be prompted to insert the Windows Vista install CD.


Informix 10 support

InfoMaker 11.1 introduces a new database interface for Informix databases. The I10 interface in PBI10110.DLL requires the Informix Client SDK 2.9 or later for Informix application development and Informix Connect 2.9 or later for runtime deployment. The new interface supports access to Unicode databases and several features that are available in recent versions of IBM Informix Dynamic Server (IDS).

Restriction You cannot use the IN9 interface and the I10 interface in a single InfoMaker session.


Accessing Unicode data

InfoMaker can connect, save, and retrieve data in ANSI/DBCS databases using the IN9 interface, but the IN9 interface does not support Unicode databases. The Informix I10 interface supports ANSI/DBCS and Unicode databases.

The I10 native interface uses the Informix GLS (Global Language Support) API for global language support. The native interface uses three DBParms to help you set up the locale used in the current connection:

These parameters are available on the Regional Settings tab page in the Database Profile Setup dialog box.

Client_Locale

Client_Locale specifies the value of the Informix environment variable CLIENT_LOCALE. The format is language_territory.codeset. For example:

Client_Locale='en_us.1252'
Client_Locale='en_us.utf8'

The I10 interface uses this setting to access string data in an Informix database and to process SQL statements. If you do not set the DBParm, the default locale value is based on the OS locale.

DB_Locale

DB_Locale specifies the value of the Informix environment variable DB_LOCALE. The format is language_territory.codeset. For example:

DB_Locale='en_us.1252'
DB_Locale='en_us.utf8'

DB_LOCALE specifies the language, territory, and code set that the database server needs to correctly interpret locale-sensitive datatypes such as NChar and NVarChar in a specific database. The code set specified in DB_LOCALE determines which characters are valid in any character column, as well as in the names of database objects such as databases, tables, columns, and views. If you do not set the DBParm, the I10 interface assumes that the DB_LOCALE value is the same as the CLIENT_LOCALE value.

You can set the CLIENT_LOCALE and DB_LOCALE environment variables directly using the Informix Setnet32 utility, available in the Utilities folder for the Informix database interfaces in the Objects view in the Database painter or the Database Profiles dialog box.

For more information about the Informix CLIENT_LOCALE and DB_LOCALE environment variables, see the IBM Informix GLS User's Guide, currently available at the Informix library Web site.

StrByCharset

The StrByCharset DBParm specifies how to convert string data between InfoMaker Unicode strings and Informix client multibyte strings. By default, string conversion for UTF-8 code sets is based on the UTF-8 code set, and string conversion for non-UTF-8 code sets is based on the current OS code page. If StrByCharset is set to 1 (true), string conversion is based on the code set specified in the DBParm Client_Locale.


Assigning an owner to the PowerBuilder catalog tables

When you use the I10 interface, you can use the PBCatalogOwner DBParm on the System tab page to assign a nondefault owner to the extended attribute system tables. For ANSI-compliant databases, the owner name that you specify must be unique but the table name does not have to be unique. You can create multiple sets of catalog tables prefaced with different user names. However, if the database is not ANSI-compliant, the table name must be unique, so that only one set of catalog tables can be created with an assigned owner name.


Support for long object names

The I10 interface supports Informix long object names with up to 128 characters.


Renaming an index

With IDS 9.2.1 and later, you can change the name of an index in the Database painter when you are connected using the I10 interface. The I10 interface uses the IDS RENAME INDEX statement to change the name of the index. You need only drop and recreate the index if you want to make other changes.


SQL statement caching

In IDS 9.2.1 and later, the database server uses the SQL statement cache (SSC) to store SQL statements across user sessions. When any user executes a statement already stored in the SQL statement cache, the database server does not parse and optimize the statement again, resulting in improved performance. The statement must be a SELECT, UPDATE, DELETE, or INSERT statement, and it cannot contain user-defined routines.

There are several ways to configure caching on the server. The SET STATEMENT CACHE statement takes precedence over the STMT_CACHE environment variable and the STMT_CACHE configuration parameter. You must enable the SQL statement cache, either by setting the STMT_CACHE configuration parameter or by using the Informix onmode utility, before the SET STATEMENT CACHE statement can execute successfully.

You can set the StmtCache DBParm on the System tab page in the Database Profile Setup dialog box for I10 connections to turn SQL statement caching on or off on the client. However, the server must be configured to support SQL statement caching before you can access the cache from the client.

For more information about Informix SQL statement caching, see the IBM Informix Dynamic Server Performance Guide.


Creating and dropping indexes without locking

In IDS 10.0 and later, the SQL syntax of CREATE INDEX and DROP INDEX supports the ONLINE keyword to create or drop an index in an online environment where the database and its tables are continuously available. When you use the ONLINE keyword to create or drop an index, data definition language (DDL) operations execute without applying an exclusive lock on the table on which the specified index is defined.

If you use CREATE INDEX ONLINE to create an index on a table that other users are accessing, the index is not available until no users are updating the table. If you issue DROP INDEX ONLINE to drop an index, no users can reference the index, but concurrent data manipulation language (DML) operations can use the index until the operations terminate. Dropping the index is deferred until no users are using the index.

You can set the OnlineIndex static DBParm on the System tab page in the Database Profile Setup dialog box for I10 connections to specify that the Database painter should use the ONLINE keyword when you create or drop an index.

Clustered index not supported You cannot create a clustered index using online mode because it is not supported by IDS.


Column-level encryption

In IDS 10.0 and later, the SQL statement SET ENCRYPTION PASSWORD can improve the confidentiality of data and support data integrity by defining or resetting a password for encryption and decryption of data at the column level.

You can set the EncryptionPass and Hint static DBParms on the System tab page in the Database Profile Setup dialog box for I10 connections to specify a password and a hint to help you remember the password. The application uses built-in Informix functions to encrypt and decrypt character data.


Using multiple OUT parameters in user-defined routines

In a user-defined routine (UDR), an OUT parameter corresponds to a value returned through a pointer. Before IDS version 9.4, IDS supported no more than one OUT parameter in a UDR, and any OUT parameter was required to appear as the last item in the parameter list. IDS version 9.4 drops these restrictions, supporting multiple OUT parameters anywhere in the parameter list of the UDR. This feature is available when you use the I10 interface. It provides greater flexibility in defining UDRs, and removes the need to return collection variables in contexts where multiple returned values are required.

To return OUT parameters from a UDR, you must use statement local variables (SLVs). In the following statement, the OUT parameter in the UDR myfunc is defined using the SLV syntax slvname#out_param_type.

SELECT sales FROM mytable WHERE myfunc(10, sales#money) < 1000

Statement caching for Oracle 10g

Statement caching in Oracle 10g provides and manages a cache of statements for each session. On the server, cursors are ready to be used without the need to parse the statement again before execution. Statement caching can be used with connection pooling and improves performance and scalability.

To set the maximum size of the statement cache, set the StatementCache DBParm to the number of statements you want to cache. The default value is 0, which means that statement caching is disabled in the current session. This DBParm is available only in the O10 database interface.


Identity columns in Adaptive Server 15

In Adaptive Server® Enterprise 15.0 and later, you can use the following datatypes as identity columns: bigint, int, numeric, smallint, tinyint, unsigned bigint, unsigned int, and unsigned smallint. This support has been added to the ASE and SYC database interfaces for InfoMaker 11.1.


New DLL required for pipeline deployment

If you deploy an application that includes data pipelines, you need to deploy a new DLL, pbdpl110.dll, with your application.


Specifying null values as retrieval arguments

When you preview a report that takes retrieval arguments in the Report painter, you may want to specify that one or more arguments has a null value. The Retrieval Arguments dialog box now has a check box next to each retrieval argument that you can select to specify that the argument has a null value. Typing a value in the Value box clears the check box.



Known problems


Database connectivity issues


Value of bit column displays as -1 with SNC interface

To communicate with SQL Server, the SNC interface uses the Microsoft OLE DB API, which returns VARIANT_BOOL for a bit datatype. If the value of the StaticBind DBParm is 1, the SNC interface does not describe the columns and does not do any data conversion. As a result, a bit column with the value 1 displays as -1 in a report. To work around this issue, set the StaticBind DBParm to 0, which enables the SNC interface to convert the datatype correctly. [CR 463142]


Pipeline execution with JDBC driver fails

Executing a pipeline with the destination Adaptive Server Enterprise 12.5 when using the JDBC driver fails with the database error 2762. [CR 338371]


IN9 Informix interface does not work with UTF-8

The IN9 Informix database interface cannot update and retrieve data when the Informix server uses the UTF-8 character set. The interface works correctly with ANSI and DBCS. [CR 349535]


Alter table limitations with OLE DB and Microsoft SQL Server

When you connect using OLE DB and change the name or width of a column in a Microsoft SQL Server 2000 database using Alter Table in the Database painter, the column is moved to the end of the table and all its data is lost. To prevent this from occurring, InfoMaker does not allow you to alter a table's column name and column size. [CR 348581]


Connection issues with CnnPool

In the Database painter, attempting to connect to an Oracle9i or Oracle 10g database from an Oracle9i client fails after a connect and disconnect if the CnnPool database parameter is set to ‘Yes’. The Oracle9i client software does not support connection pooling with InfoMaker 10.0 or later. [CR 355639]


ASE version 15 with ODBC driver

When you connect to an ASE version 15 server using the Sybase ASE ODBC driver, NChar(10) and NVarChar(10) columns are saved as Char(10) and VarChar(10). [CR 408710]


Report painter issues


AutoSize Height issues with header band

When two reports are included one above the other in the header band of a report and the AutoSize.Height property is set to true for the header band and false for the detail band, the report displays incorrectly in preview. The lower report overlaps the upper report. The report displays correctly if the Autosize.Height property is set to true in both the header and detail bands. [CR 405033]


Save As PDF fails on Windows 2003 Server

Saving a report as PDF using the Distill method fails at runtime on Windows 2003 Server. This is caused by a Group Policy that by default disallows installation of printers that use kernel-mode drivers. (Kernel-mode drivers have access to system-wide memory, and poorly written drivers can cause system failures.)

To allow installation of kernel-mode drivers, follow these steps:

  1. Select Run from the Windows Start menu.

  2. In the Open box, type gpedit.msc and click OK.

  3. In the Group Policy console, expand Computer Configuration, Administrative Templates, and Printers.

  4. Disable “Disallow Installation of Printers Using Kernel-Mode Drivers.”

[CR 349868]


XSL-FOP save as PDF does not support graphic controls

Use the distill method to export the data in reports that contain graphic controls, such as lines and rectangles, to PDF. The XSL-FOP method does not work correctly for graphic controls. [CR 303829]


Other issues


Truncated string in saved EMF file

Sometimes a string in a text control in a report is longer than can be displayed in the control in the Design view in the Report painter. If this occurs, an EMF file saved in the painter or at runtime displays with the string truncated. [CR 342797]


Web ActiveX download fails on Windows XP

The DataWindow® Web Control for ActiveX fails to download its CAB file to a client browser running on Windows XP if the Microsoft Active Template Library (ATL) module, atl71.dll, is not present in the Windows\System32 directory. The CAB file downloads successfully if the ATL DLL is present.


Some PSR files must be regenerated

PSR files created in builds of InfoMaker 10.0 or 10.0.1 prior to EBF build 6044 cannot be opened in InfoMaker 11.1. You must regenerate the PSR file in a later build. [CR 386984]



Product compatibilities


SQL Anywhere

InfoMaker 11.1 has been tested with SQL Anywhere® 10.0.1 and the SQL Anywhere 10.0.1 Runtime Edition.


Ghostscript

The report Save as PDF feature has been tested with AFPL Ghostscript version 8.53.



Third-party components and deployment

InfoMaker applications have some dependencies on third-party components that are installed with InfoMaker. You may redistribute some of these components with your application, but others must be obtained from the vendor.

For information about components that can be freely downloaded, see the free download terms document. A copy of this document is located in the Support directory on the CD and on the Sybase Web site.


Apache files

You may redistribute Apache files included with InfoMaker to your users. Any use or distribution of the Apache code included with InfoMaker 11 must comply with the terms of the Apache License which is located in the free download terms document for InfoMaker 11.

Version 0.20.4 of the Apache Formatting Objects Processor (FOP) is required if your application uses XSL-FO to save files as PDF. For more information about FOP, see the Apache FOP Web site.

The Apache Xerces files xerces-c_2_6.dll and xerces-depdom_2_6.dll are required for XML support for reports. For more information about Xerces, see the Xerces C++ Parser Web site.


Microsoft files

When you deploy the core InfoMaker runtime files, you must ensure that the msvcr71.dll and msvcp71.dll Microsoft Visual C++ runtime libraries and the Microsoft .NET Active Template Library (ATL) module, atl71.dll, are present on the user’s computer. The InfoMaker runtime files have a runtime dependency on these files and they are required for all applications. For more information about obtaining and using these files, see the Microsoft Web site.

Microsoft.Ink, Microsoft.Ink.dll, and Microsoft.Resources.dll are required if your application uses the InkEdit EditMask style or InkPicture controls. These files are part of the Microsoft Windows XP Tablet PC Edition Software Development Kit 1.7, which is available on the Microsoft Web site.


Sun Microsystems files

The Java Runtime Environment (JRE) is required for JDBC connections and saving as PDF using XSL-FO. For a copy of third-party terms and conditions for the JRE, see the free download terms document.The JRE can be downloaded from the Sun Developer Network.



Documentation updates and clarifications

The following books have been updated on the Sybase Product Manuals Web site for InfoMaker 11.1:

For other books in the documentation set, refer to the InfoMaker 11.0 collection on the Sybase Product Manuals Web site or the online Help.



Migration information

You can migrate an InfoMaker application from any version of InfoMaker directly to any later version. Before you migrate to a later version, read the following Technical Document to learn about changes in InfoMaker that might affect your application: Migrating PowerBuilder Applications. Topics with IM in parentheses after their titles apply to InfoMaker.


OLE DB performance with Microsoft SQL Server

In InfoMaker 10.5.2 and later, when you use the OLE DB database interface with a Microsoft SQL Server database and retrieve data into a report or use an embedded SQL cursor in a SELECT statement, server-side cursors are used to support multiple command execution. If this has a negative impact on performance, try increasing the size of the Block database parameter to 500 or more, or adding the following line to the [Microsoft SQL Server] section in the PBODB initialization file to turn off server-side cursors:

ServerCursor = 'NO'


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, the SyBooks CD, and the Sybase Product Manuals Web site to learn more about your product:


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 Certification Report.

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

  4. Click a 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.

InfoMaker 11.1 HTML 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.



Back to Top
© Copyright 2010, Sybase Inc.