| Telelogic Synergy 6.6a Readme |
IBM Corporation 5 December, 2008 |
© Copyright IBM Corporation 1992, 2008
U.S. Government
Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
This file contains last-minute product information for and updates to Telelogic® Synergy™ 6.6a.
It is divided into the following sections:
For the latest news and information
on Telelogic Synergy, visit the Web site at http://www.ibm.com/software/rational/support/.
To run Telelogic Synergy 6.6a, you need one of the following operating systems installed on your computer, running on a supported locale:
CPU, OS and version |
Locales |
Server |
User Interfaces |
|---|---|---|---|
Sun SPARC |
China zh_CN.GB18030 |
Informix |
Synergy GUI |
Pentium or equivalent |
China zh_CN.UTF-8 |
Informix |
Synergy GUI |
Pentium or equivalent |
Chinese (PRC) |
Informix |
Synergy GUI |
Pentium or equivalent |
Chinese (PRC) |
Not supported |
Synergy GUI |
Pentium or equivalent |
Chinese (PRC) |
Not supported |
Synergy GUI |
This release provides support for Asian language characters,
with the restrictions noted in this document.
Windows clients (Synergy GUI, Synergy Classic GUI, and Synergy Classic CLI) may connect to a Telelogic Synergy server in the same Windows locale, or in a UNIX® locale for the same country. UNIX clients (Synergy GUI and Synergy Classic CLI) may connect only to Telelogic Synergy servers in the same UNIX locale. For example, a Solaris server in Japan (the ‘ja’ locale) may be accessed from a ‘ja’ Solaris client, from a ‘ja_JP.UTF-8’ Linux client, and from Windows Japanese clients.
Cross-locale working, for example, a client in a Chinese locale connecting to a Japanese server, is not supported.
The minimum hardware requirements for the server are:
The minimum hardware requirements for the client are:
Telelogic® License Server™ 1.5 must be installed and operational
Telelogic Synergy release 6.6a has the following restrictions.
The Synergy Classic GUI is not supported on UNIX or Linux.
The HP-UX operating system is not supported.
Windows FAT-16 file systems are not supported. Telelogic Synergy Windows servers must be installed on NTFS file systems. Windows work areas may be placed on NTFS or FAT-32 file systems.
Oracle databases are not supported.
For additional information on system requirements, including recommended configurations, visit the Telelogic Synergy Support Web site.
For the latest information about third party products that are supported with Telelogic Synergy, visit the Telelogic Synergy Support Web site.
See System requirements for information about locales by platform.
Telelogic Synergy does not adapt numeric formats or sorting orders according to the locale.
Telelogic Synergy 6.6a is compatible with the following products:
Telelogic Synergy Release 6.6a supports upgrade from releases Telelogic Synergy Releases 6.5 and 6.5a. The upgrade process from 6.5 supports only 7-bit ASCII CM and UTF-8 Synergy Change characters during the upgrade. If the 6.5 database contains any non-ASCII data, the result will not be correct.
Telelogic Synergy 6.6a is DCM-compatible with the following versions:
DCM and DCS transfers between two Synergy Asian-release databases, i.e., Release 6.5a and 6.6a, are supported, even when those two databases are in different locales. DCM automatic receive across different locales is not supported. Also note that that operating system settings and fonts might not permit simultaneous display of characters from multiple locales.
Patches may be required in order to support Telelogic Change 5.1 with Telelogic 6.6a, or to support DCM-compatibility between versions. Check the Telelogic Synergy Support Web site for the latest information on patches.
For a list of supported product integrations, visit the Telelogic Synergy Support Web site.
Telelogic Synergy 6.6a is available in the following formats:
See the Telelogic Synergy Installation Guide for detailed directions about installing Telelogic Synergy.
A new license is required for Telelogic Synergy 6.6a.
Telelogic Synergy 6.6a uses the Telelogic License Server. The Telelogic License Server is a FLEXlm-based license server that manages licenses for Telelogic products. You must upgrade or install the Telelogic License Server to use Telelogic Synergy 6.6a. See Telelogic Lifecycle Solutions Licensing Guide for detailed information.
The following sections provide brief descriptions of product features available in the 6.Xa releases:
This release provides support for characters from the Unicode 3.0 standard. Characters outside the Basic Multi-Lingual Plane, characters represented by surrogate pairs, and characters from private use areas are not supported. The ability to display characters in the supported Unicode 3.0 set depends upon your operating system settings and fonts. Telelogic Synergy itself does not provide any fonts.
Telelogic Synergy supports Asian language characters in most attributes, including:
Filenames for objects under CM control (i.e., object names).
Work area paths.
An object’s version, comment, release, purpose, etc.
Input method editors (IMEs) are enabled in Telelogic Synergy dialogs, so you can enter the range of characters supported by the IMEs. Telelogic has verified Telelogic Synergy with the standard IMEs supplied by the operating system vendors; third-party IMEs have not been tested.
In some contexts, Telelogic Synergy allows use of external viewers and editors to display or edit the contents of string and text attributes. For example, the Task Browsing dialog in Telelogic Synergy Classic has an Edit button to edit the Task Description. The command line also provides this facility - for example, the ccm attr -m command allows users to edit any text attribute value (subject to the usual permissions checks). In all cases, the text sent to the external viewers and editors is in the default system encoding, and the text returned from the editor is assumed to be in that same encoding. In many locales, this means that characters from other locales will be lost or modified. For example, an attribute containing both Chinese and Japanese characters cannot be edited using ccm attr -m on a Japanese system with the Shift JIS encoding - the Chinese characters would be lost or be substituted by incorrect Japanese characters.
For more general information about encodings for Telelogic Synergy files and attributes, see File Encodings.
Telelogic Asian releases extend support for Asian language character in source files.
The bundled Telelogic Synergy compare and merge tool (Telelogic Synergy Compare/Merge) is supported for source files that contain Asian language characters. For more information, see Compare/Merge.
A wide range of encodings are supported for source files, but see below for information on UTF-16 and UTF-32, and see the restrictions on Keyword Expansion. Files in encodings incompatible with ASCII (such as EBCDIC) should be defined as binary types. For more general information about encodings for Telelogic Synergy files and attributes, see File Encodings.
It is the user’s responsibility to ensure that the editors used with Telelogic Synergy can handle the encodings used. Some editors allow the encoding to be selected when opening or saving files; others assume files are in the default system encoding.
For some files in some encodings (and for almost all files in UTF-16 or UTF-32 encodings), source files are treated as binary even if they have a subtype of ascii. This means that the Telelogic Synergy type of the object may be ascii or a subtype of ascii, but internally, Telelogic Synergy treats the file as binary. A file is treated as binary due to the appearance of null bytes, Control-Z, or too many other non-printable characters. UTF-16 or UTF-32 files may contain a large number of null bytes. This has the following implications for files that are treated as binary:
Newline translation is not performed. This means that if the CM server is on UNIX or if the database contains data that was received in a DCM package from a UNIX database (which is supported), and the CM client is on Windows, source files in the Windows work area might contain UNIX-style newline characters. Unicode-aware editors and IDEs are likely to handle both types of newline characters (because the Unicode standard recommends that). It is not necessarily true that other Windows-based, non-Unicode Asian language tools can handle UNIX newline conventions.
The binary compare and merge tools are used. This means that compare and merge do not work unless a tool that understands the specific encodings used is configured for the binary type . Note that the bundled Telelogic Synergy Compare/Merge tool does handle UTF-16 and UTF-32.
Source file keyword expansion is not performed.
Telelogic Synergy Compare/Merge supports a large number of file encodings. When you first run the tool, it asks permission to create a list of encodings in a file .ccm_merge.enc in your home profile directory. When you start a merge or compare, you may choose the encoding for the files from this list. If you wish to make the list shorter, you can remove encodings from the menu selection by editing the .ccm_merge.enc file, and restarting the Compare/Merge tool. If you wish to restore the full list, delete the .ccm_merge.enc file.
If you select an encoding that is not appropriate for the files being merged or compared, the tool may detect that and prompt you to select a different encoding. If the tool does not detect the incorrect encoding automatically, and you see the wrong characters displayed on screen, you should restart the merge or compare and select the right file encoding explicitly.
Telelogic Synergy Compare/Merge does not support merging or comparing files with different encodings.
The tool also creates a .ccm_merge.dat file in your home profile directory. This file holds your default settings, including the encoding most recently used. You can edit the .ccm_merge.dat file to change the default Compare/Merge settings.
Text written by Telelogic Synergy to the standard output and standard error streams is in the system default encoding. Text read by Telelogic Synergy from the standard input stream is assumed to be in the same system default encoding. This means that scripts using the CLI might not be able to handle attribute values from multiple locales, since many encodings cannot represent (for example) both Chinese and Japanese characters at the same time.
On Windows, programs may read their command line parameters in the default system encoding, or in Unicode. Programs that read the parameter values in Unicode can handle strings from multiple locales. Programs that use the default system encoding probably support only one locale.
On UNIX, the command line parameters are only available in the encoding for the current locale. If that encoding is Unicode (for example, UTF-8), characters from multiple locales can be handled correctly. If the locale encoding is not Unicode (for example, EUC), programs can only support command line characters from that one locale.
Source files are sent to and read from editors, viewers, merge tools, etc., as an uninterpreted stream of bytes. It is up to the user to select tools, and/or tool options, that match the actual source file encodings.
Telelogic Synergy expects its own files to be in specific encodings - either UTF-8 or the system encoding. Note that files containing only 7-bit ASCII characters are compatible with both UTF-8 and system encodings such as Shift-JIS.
The following frequently edited Telelogic Synergy files must be in UTF-8 (or ASCII) encoding:
ccm_home/etc/ccm.properties
ccm_home/etc/ccm.help.file.properties
ccm_home/etc/ccm.server.properties
ccm_home/etc/ccm.ini
ccm_home/etc/om_hosts.cfg
ccm_home/etc/ignored_file_patterns
database/db/MDL_INFO
database/etc/dcm*.txt
database/lib/Unix/migrate.rul
database/lib/Windows/migrate.rul
database/lib/notify/*.tpl
database/pt/attrange.dft
The following frequently edited files must be in the system default (or ASCII) encoding:
All files in and below ccm_home/bin
All files in and below database/bin
database/db/DBINFO
database/etc/NTftp.in
database/etc/Unixftp.in
Scripts in database/lib/notify/Unix
Batch files in database/lib/notify/Windows
The following frequently edited Telelogic Synergy files must be limited to 7-bit ASCII characters only:
ccm_home/etc/remexec.cfg
ccm_home/etc/ccminit
ccm_home/etc/ccm_locales.map
database/lib/ccminit
database/lib/notify/Unix/*.def
database/lib/notify/Windows/*.def
Telelogic Synergy supports having multiple names, or aliases, for locales and encodings. For example, in Japan, the user might log in using the shorter and more convenient locale name ja instead of the more complete name ja_JP.eucJP. Similarly, HP-UX only recognizes lower cases encodings, but the user might want to use an upper case encoding name. Telelogic Synergy has a built-in table of the common forms of these aliases, but provides a way to extend the list if necessary.
The valid synergy_encodings are UTF8, BIG5, eucJP, EUC-KR, SJIS, and GB18030. If you need more information on encodings, refer to the technical note "Encoding Translations" on the Support website.
Telelogic Synergy supports different encodings for the same source file. This allows source files to have encodings that correspond to where they are stored. Three different encodings may be specified for each object: one encoding for the server, one encoding for the Windows work area, and another encoding for a UNIX work area. This ensures that the appropriate encoding conversions are made when a file is copied from one location to another. To accomplish this, two attributes must be set.
The attribute encoding_conversions is set on the model object. When this attribute is set to TRUE, the multiple-encoding feature is enabled for the database. If this attribute does not exist or is set to FALSE, this feature is not enabled for the database.
The attribute encoding_rules is set on the object type. This attribute specifies that encoding translations occur when the files are copied between the client and server, and vice versa. The encoding_rules attribute is of the following form:
Server-encoding:encoding
Unix-wa-encoding:encoding
Windows-wa-encoding:encoding
Specifying the UNIX or Windows work area encoding is optional. An encoding must be the name of a character encoding that is recognized by standard encoding conversion programs, such as iconv. If you need more information on encodings, refer to the technical note "Encoding Translations" on the Support website.
This section covers areas where Asian characters are not supported, where Telelogic Synergy 6.6a does not offer the full functionality of the underlying release 6.5, and other issues in product usage.
Strings Restricted to ASCII
Some string or text fields and values are restricted to 7-bit ASCII characters, excluding control characters, but including white space characters. The restricted fields and values are:
Machine names and host names
Windows domain names
INFORMIX database server names
Telelogic Synergy installation paths
Database paths and names
OS and Telelogic Synergy user names
OS and Telelogic Synergy group names
Role names
State names
DCM database IDs
DCM generate and receive paths, for all transfer modes
SOADF offline storage paths
Type names
Version, release, and DCM delimiters
Attribute and relationship names
Names of third-party tools invoked by Telelogic Synergy (for example, editors and merge tools)
Naming Conventions and Limitations
Some characters are reserved for use as delimiters by the operating systems, INFORMIX, or Telelogic Synergy, and may not be used in object names. For example, the colon (:), slash (/), and backslash (\) characters (amongst others) may not be used in object names. Project names must not contain tabs. See Telelogic Synergy Help and the Telelogic Synergy Administration Guide for more information.
Telelogic Synergy places limits on the lengths of various names and other strings. These limits are in terms of bytes, not characters. Some error messages might describe limits in terms of characters; such messages are incorrect, and should be taken as referring to byte length limits. All strings are held internally in Telelogic Synergy as UTF-8, so the length limits in Asian characters would normally be one third of the byte limit. For example, the length of an object name is limited to 155 bytes; this would imply a limit of 51 Asian characters. Version strings are limited to 32 bytes, or 10 Asian characters.
Asian Characters in Passwords
Due to operating system restrictions, you must use only ASCII characters in passwords when starting a remote session from Windows to UNIX using rexec. If you have non-ASCII characters in your password, you must use ESD to start a Windows session on a UNIX database. This limitation on starting remote sessions also applies to DCM automatic receive; for this reason, Telelogic recommends that the password for ccm_root be limited to ASCII characters if DCM automatic receive is used.
Date Handling
In the CLI and Telelogic Synergy Classic, only the following date formats are supported for date input, such as entering dates in queries or in task estimated completion dialogs:
Telelogic Synergy supports a locale-appropriate calendar widget for date selection, but only for Gregorian calendars.
For date output, the default date display format is YYYY/MM/DD. You can select other date formats using the environment variable CCM_DATETIME_FMT. However, non-numeric date formats might not always work, and certainly cannot be copied to a date input field.
Migrate Limitations
Migration of source (in any encoding) from plain files is supported. Migration of archives from SCCS, RCS, CVS, and PVCS is not supported.
Keyword Expansion
Keyword expansion in source files is disabled by default in Telelogic Synergy 6.6a, using a new model attribute keyword_expansion.
Keyword expansion can be enabled by setting this model attribute to TRUE:
ccm attr -c keyword_expansion -f -t boolean -v TRUE base-1:model:base
Keyword expansion can be disabled by deleting this attribute, or setting it to FALSE:
ccm attr -c keyword_expansion -f -t boolean -v FALSE base-1:model:base
or:
ccm attr -d keyword_expansion base-1:model:base
Note that the strings inserted by keyword expansion are always in UTF-8, regardless of the encoding of the source files in question. If your source files do use UTF-8, or if the strings generated by keyword expansion are always 7-bit ASCII, then the result works as expected.
However, if your source files use any encoding other than UTF-8, and the values substituted for the keywords include Asian or other non-ASCII characters, then keyword expansion would generate incorrect results.
Keyword expansion in source files whose names include spaces may contain syntax errors when compiled. Avoid using spaces in source code file names, or comment out (or remove) the keyword.
Task Report Generator
Telelogic Synergy 6.6a does not provide the problem tracking (PT) task report feature. This functionality is now available using the Telelogic Change product.
Import and Export Commands
The ccm import and ccm export commands are not supported in this release.
DCM Export 4.5SP2 Format
Telelogic Synergy 6.6a does not support the Telelogic Synergy 4.5SP2 DCM export format. This format was used to transfer data between previous releases up to, and including, CM Synergy 6.1 databases.
INFORMIX Archive and Restore
The commands ccmsrv archive and ccmsrv restore are not supported in this release.
ObjectMake
ObjectMake is not supported in this release.
ACcent and GUILD Customizations
ACcent and GUILD customizations are not supported in this release. The custom database pack file is not provided. GUILD files may contain only 7-bit ASCII characters, so may not be used for localization.
6.6a includes the following changes:
Telelogic Synergy release 6.6a was updated to comply with IBM technical, legal, and marketing requirements, in order to ensure quality of the products and protection of intellectual rights.
In the process of updating Telelogic Synergy 6.6a to comply with IBM standards, the following changes were made:
Telelogic Synergy release 6.6a does not look significantly different from release 6.5a, but it contains many underlying changes. Before upgrading, it is a good idea to test carefully and thoroughly, as described in the Telelogic Synergy Upgrade Instructions. Telelogic Synergy 6.6a provides some new utilities for use during the upgrade process.
Before you decide to upgrade, consider the following points:
Important! Before you upgrade, be sure to carefully read Appendix B of the Telelogic Synergy Upgrade Instructions.
For details about known problems in Telelogic Synergy 6.6a and how to work around them, visit the support center on the Telelogic Synergy Support Web site.
For details about problems that have been resolved in Telelogic Synergy 6.6a, visit the support center on the Telelogic Synergy Support Web site.
Support and information for Telelogic products is currently being transitioned from the Telelogic Support site to the IBM Rational Software Support site. During this transition phase, your product support location depends on your customer history.
If you are a heritage customer, meaning you were a Telelogic customer prior
to November 1, 2008, visit the Telelogic Synergy
Support site.
Telelogic customers will be redirected automatically to the IBM Rational
Software Support site after the product information has been migrated.
If you are a new Rational customer, meaning you did not have Telelogic-licensed products prior to November 1, 2008, visit the IBM Rational Software Support site.
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send written license inquiries to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send written inquiries to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions. Therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
Intellectual Property Dept. for Rational Software
IBM Corporation
1 Rogers Street
Cambridge, Massachusetts 02142
U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Trademarks
IBM, the IBM logo, ibm.com, AIX, Telelogic, Telelogic Synergy, Telelogic Change, Telelogic License Server, and Telelogic Directory Server are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.html.Adobe, the Adobe logo, PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
Citrix, the Citrix logo, Citrix Presentation Server, MetaFrame, and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. and/or one of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries.
Firefox is a trademark of the Mozilla Foundation.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Internet Explorer, Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Java, Solaris, Sun, and Sun Microsystems are registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
Red Hat, Red Hat Linux, and the products listed are trademarks or registered trademarks of Red Hat, Inc. in the US and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
VMware and ESX Server are trademarks or registered trademarks of VMware, Inc. in the United States and/or other jurisdictions.
WinZip is a registered trademark of WinZip International LLC.
Other company, product or service names mentioned may be trademarks or service marks of others.