This document contains important information about the 10.1.3 release of Serena Dimensions CM that is not included in the manuals or online help. For information about defects fixed in this release, see the accompanying Release Notes.
This upgrade can only be applied to Serena Dimensions CM 10.1.1 or later installations. If you do not have this installed, you must install, or upgrade to, Dimensions CM 10.1.1 before installing this patch. The agent and client installers will, however, perform a fresh installation in the case where no existing Dimensions CM agent or client is already installed.
See the Serena Dimensions CM 10.1.1 Readme and Release Notes for information about the Dimensions CM 10.1.1 release. See the Serena Dimensions CM 10.1.2 Readme and Release Notes for information about the Dimensions CM 10.1.2 release.
The Dimensions CM software upgrades (including the server, agent and client components) for AIX, Solaris, HP-UX, Red Hat, SuSE, and Windows are available for download from the Serena Support Web site. These also include a new installation for Windows Vista clients.
A general description of the activities you need to carry out for this release is contained in Upgrading to Dimensions CM 10.1.3. This guide is available in PDF format (dmcm_upgr1013.pdf) from the Serena Support Web site.
A Dimensions CM 10.1.3 upgrade installation can only be run against an existing base Dimensions CM 10.1.1 or later installation. If you do not have such a base installation, you will need to install that first. In this case, consult the Serena Dimensions CM 10.1.1 Readme and Release Notes and the Installation Guide (dmcm_installation.pdf) for version 10.1.1 on the Serena Support Web site.
The Dimensions 10.1.3 client installer performs a fresh installation in the case of Windows Vista. You can also, if you wish, perform a fresh installation of the Dimensions 10.1.3 clients and agents for Windows and UNIX, but only if the 10.1.1.x or 10.1.2.x versions are not already installed (in those cases the installer will automatically adopt upgrade mode).
The Dimensions CM software upgrade for z/OS is also available from the Serena Support Web site. For details on installing Dimensions for z/OS, see the Dimensions for z/OS User's and Administrator's Guide. This guide is available in PDF format (dmcm_for_zos.pdf) in the same location.
The table below displays a high level matrix of the supported platforms. For full details see the following sections:
| Vendor | Operating System Platform | Hardware | Client | Agent | Server | Database* | Oracle Runtime | Comments |
|---|---|---|---|---|---|---|---|---|
| Microsoft | Windows Vista SP1 (32-bit, x86) | x86 IA-32 |
Y |
Business and Ultimate editions | ||||
| Windows XP Professional (32-bit, x86) | x86 IA-32 |
Y |
||||||
| Windows 2000 Professional (32-bit, x86) | x86 IA-32 |
Y |
||||||
| Windows 2003 Server, Windows 2003 Enterprise Server (32-bit, x86) | x86 IA-32 |
Y |
Y |
Y |
O, S, D |
Y |
64-bit supported in 32-bit mode only | |
| Sun | Solaris 9 (64-bit, Sparc) | SPARC | Y |
|||||
| Solaris 10 (64-bit, Sparc) | SPARC | Y |
Y |
Y |
O |
Y |
||
| HP | HP-UX 11.31 (64-bit, IA-64) Itanium | Itanium | Y |
Y |
Y |
O |
Y |
|
| HP-UX 11.23 (64-bit, PA-RISC) | PA-RISC | Y |
Y |
O |
Y |
|||
| IBM | AIX 5.3L (64-bit, PowerPC) - ML 02 or later | PowerPC | Y |
Y |
Y |
O |
Y |
|
| z/OS 1.5-1.9 | Y |
Y |
ISPF client | |||||
| Linux | Red Hat 4.0 (64-bit, x86-64) | x86-64 | Y |
Y |
Y |
O |
Y |
This is a 32-bit application supported on both 32-bit and 64-bit |
| SLES 9 (32-bit, x86) | Pentium (x86) | Y |
Y |
O |
Y |
*Key to
Database Versions |
||
|---|---|---|
| Vendor | Version |
Key |
| Oracle | Oracle 10.2.0.x |
O |
| Microsoft | SQL Server 2000 |
S |
| IBM | DB2 v8.2 |
D |
The server components of this Dimensions CM release are supported on the platform and database combinations listed below.
Note: Dimensions CM is built and tested against Oracle 10.2.0.2 as both a supplied runtime and customer supplied Oracle. For customers using their own Oracle installations Serena will support Oracle 10.2.0.x
| Platform | Version | Database |
|---|---|---|
| Microsoft Windows |
|
|
| Sun SPARC Solaris |
|
|
| IBM AIX |
|
|
| HP-UX |
|
|
| Red Hat |
|
|
* Replicator is not supported
** DBCS is not supported
*** dm_make is not supported on this platform
Optional: Applies if you want to provide access to the Dimensions CM web client or the Administration Console.
The list of supported Web servers includes:
Supported Web application containers:
Optional: Applies if you want to use LDAP for user authentication.
The list of supported directory servers includes:
The client components of this Dimensions CM release are supported on the platforms listed below. To use the web-based clients, you must also have a supported Web browser and Java virtual machine.
Note: You cannot use a Dimensions CM 10.1.3 client with a pre-10.1.3 server, or use a pre-10.1.1 client with a 10.1.3 server.
| Platform | Version | Web browser | Java plug-in |
|---|---|---|---|
| Microsoft Windows |
|
|
|
| Sun SPARC Solaris |
|
|
|
| HP-UX |
|
|
|
| IBM AIX |
|
|
|
| Red Hat |
|
|
|
| SuSE |
|
|
|
| IBM z/OS |
| n/a | n/a |
Notes:
The agent components of this Dimensions CM release are supported on the platforms listed below.
| Platform | Version |
|---|---|
| Microsoft Windows |
|
| Sun SPARC Solaris |
|
| HP-UX |
|
| IBM AIX |
|
| IBM z/OS |
|
| Red Hat |
|
| SuSE |
|
| Vendor |
Application | Integration Method |
|---|---|---|
| Borland |
|
|
| IBM |
|
|
|
|
|
| HP TestDirector for Quality Center |
|
|
| Microsoft |
|
|
|
|
|
| Remedy |
|
|
| Serena |
|
|
| Sybase |
|
|
| TeleLogic |
|
|
This release supports the following versions of Dimensions RM:
This release does not support the use of DB2 or MS SQL Server databases with the RM Integration. Support for DB2 and MS SQL Server database instances will be added in the first patch of Dimensions 10.1.3.
Serena recognizes that virtualization technology provides significant utility and value to our customers. As such, Serena conducts functional testing and certifies our products using virtualization technology in addition to native environments. While Serena expects that our products will function properly when running on supported platforms in a virtualized environment as well as a native environment, there may be functional and performance limitations. Serena will not require that customers recreate and troubleshoot every issue in a non-virtualized environment, however there may be circumstances in which such action may be required. Serena will only make this request when there is reason to believe that the virtualized environment is a contributing factor to the issue. If the issue cannot be reproduced in a supported non-virtualized environment, customers will need to refer their issues to their virtualization vendor.
For general details on installing this upgrade, see Upgrading to Dimensions CM 10.1.3 (dmcm_upgr1013.pdf) on the Serena Support Web site.
The sections below only contain operating system or database specific information essential for upgrades.
Certain Dimensions CM for UNIX installation activities rely on the UNIX uncompress utility and this must be present on the UNIX machine. Most UNIX machines will have this installed as standard, and its presence can be checked with commands such as:
$ which uncompress
$ uncompress -h
If your UNIX machine does not have uncompress installed, your system administrator will need to install it before you can proceed with the installation of Dimensions CM for UNIX.
On Windows, if the password for the PCMS_SYS user has been set in previous installations to any value apart from the default ("PCMS_SYS"), this must be reset to the default prior to attempting an upgrade installation. Upgrade installations do not allow you to specify a different password for the PCMS_SYS user; if the password does not match the default of "PCMS_SYS," the upgrade installation will fail.
If you are upgrading from Dimensions CM 10.1.1, and were using library cache areas,
then to ensure correct functioning of the
10.1.3 version of library
cache areas you need to purge all library cache areas (using the dmcli command plca, see the
Command-Line Reference for details) and remove all sub-directories from each
library cache root directory. Note that there may be a
number of "missing file" error messages when performing the plca
command.
3.4 NIS Configuration Considerations for HP-UX 11.31
On some systems running HP-UX 11.31, using a /etc/nsswitch.conf file based on /etc/nsswitch.hp_defaults can cause the getservbyname library routine to enter an infinite loop.
A linkage of this type affects the Dimensions CM application server processes when they attempt to start Dimensions CM file server processes for user file or item library access. The workaround is to base /etc/nsswitch.conf on /etc/nsswitch.nis. By doing this, the NIS lookup is done last in /etc/nsswitch.nis rather than first. This appears to be a HP-UX operating system issue.
The default sizes for redo logs mentioned in the Dimensions CM 10.1.1 and 10.1.2 documentation (4 MB) is out of date. You should set the default sizes to 100 MB.
Serena Software strongly recommends that the Serena Common Tomcat should be explicitly shut down before commencing any Dimensions software upgrade. Unfortunately, the upgrade installer is not able to automate this, so the person doing the upgrade must do it manually. If this is not done, then the Web archive (.war) files used by the upgraded Dimensions CM Web tools may not expand correctly, causing missing files in these tools.
When you stop the Dimensions Service on windows, the dmschedule process may continue to run for a period after the other processes have exited. You should ensure that this process has actually terminated before performing an upgrade or patch installation.
On Windows platforms, it is recommended that you make sure that the Microsoft Management Console (i.e. Services, Computer Management, etc.) is closed before starting an installation or upgrade. (This is the option accessed from the Windows Control Panel, or on certain versions of Windows is part of the Control Panel Administrative Tools option.)
When running an Agent installation in console mode on UNIX platforms, you may receive the following java exception messages following the "Dimensions 10.1.3 - Installation Location" page:
(Nov 19, 2007 6:36:20 AM), com.installshield.dimensionsunix.event.InstallScript,
err, java.lang.ArrayIndexOutOfBoundsException: 1
java.lang.ArrayIndexOutOfBoundsException: 1
at com.installshield.dimensionsunix.event.InstallScript.onExecutingSetPa
tchVariablesec49d0ef5b1c77db445bea691d08dd70(InstallScript.java:165)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.installshield.event.ActionSequenceEngine$ActionTask.invokeJavaMethod(Unknown Source)
at com.installshield.event.ActionSequenceEngine$ActionTask.executeAction (Unknown Source)
at com.installshield.event.ActionSequenceEngine$ActionTask.run(Unknown Source)
at com.installshield.event.ThreadPool.run(Unknown Source)
at java.lang.Thread.run(Thread.java:534)
These messages can be ignored, as they will have no effect on the installation.
If during the installation, you receive an error message stating that Dimensions CM is unable to connect to the database, but it does not inform you of the reason, check the following:
For more details, see the section “Pre-Installation Tasks and Considerations” for your platform in Upgrading to Dimensions 10.1.3.
The upgrading of existing installations of the IDE integrations is only supported for the standard SCC IDEs and the Rich Eclipse integration. For other integrations, the user must uninstall and reinstall them.
If you are installing this upgrade with SQL Server or DB2 on Windows, and Oracle was installed on the system at the time of the original Dimensions installation, you will need to remove a registry key before running the installation. To do so, run regedit and remove the key:
HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions\10.1\Install\INSTALL_OracleSid
Note: Make sure that you back up your registry before making any changes using regedit via Registry | Export Registry File.
The Dimensions CM Windows installer will fail before loading the first window in the install wizard if there is no C: drive on the machine. To work around this problem use the subst command to create a virtual C: drive.
Some Dimensions CM installation-specific information is retained in the registry for reuse on subsequent installations. If you have removed all Dimensions CM products from your system, you may also wish to remove this registry information. To do so, backup your Windows registry, run regedit, and remove the following key and its contents:
HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions\10.1
The UNIX installer sometimes displays certain letters in passwords. Typically, only one letter is visible. This is a known InstallShield issue. This only affects the on-screen display of passwords during installation. Passwords will not be stored in clear text as a result of the installation.
On Windows platforms there is a small possibility that the installation may not in fact have worked even though the installation has appeared to complete successfully. It is recommended that you check that the expected software (e.g. Serena Dimensions CM Server 10.1.3) is listed in the Control Panel | Add or Remove Programs window following the installation.
When running an agent upgrade, if you click the Back button on the install page it incorrectly takes you to the page that enables you to change the installation directory. You should ignore this page and click the Back or Next button to proceed to another page.
When installing the DOORS integration for DOORS 8.2, an error message:
"1607:Unable to install InstallShield Scripting
Runtime"
is returned. Clicking OK will result in the installation continuing
successfully.
You may receive an Internal Failure message on the AR System Server Connection Information page when installing the Dimensions Integration for Remedy.
To resolve this problem:
Dimensions:Lookup
Dimensions:SampleIntegration
Dimensions:AttributeNames
Dimensions:ProductNames
After installing Serena® Dimensions® CM 10.1.3, please ensure that you visit the Serena support Web site at http://support.serena.com to determine the latest patch updates for Dimensions CM 10.1.3, if any. This site requires first time users to register for a user name and password. Once logged into the support site, under the download tab you will find an option to download patches. Search the list of patches to see if there are any patches appropriate to Dimensions CM 10.1.3. If there are any such patches, it is recommended that you download them together with the associated patch readme and apply them. Each patch download includes the patch binary, an integral patch installer, and the associated patch readme that includes instructions for running the patch installer.
If you have upgraded the Windows Explorer integration, you will need to reboot the client machine after the installation for the plug-in to work correctly.
There is a known issue with the DNN command on installations that use multiple base databases in an Oracle/DB2/MS SQL Server instance. A network node definition referenced by area definition and/or replication configuration definition in a base database could still be deleted when the DNN command is issued from a session connected to another base database that does not reference this network node definition. This is not an issue for installations that have only one base database in the Oracle/DB2/MS SQL Server instance. To avoid this issue, please manually verify that the network node definition being deleted is not referenced in any base databases before issuing the DNN command.
The use of delta libraries is not supported on the following agent platforms:
If you have defined a Deployment area for a project and specified a post-event transfer script, but that script does not exist, you may experience a problem where the client application hangs when you attempt to perform certain operations. It is recommended that you ensure that any scripts you specify for an area exist in the specified location, to avoid this potential issue.
Under certain circumstances, it is possible to have an area defined in Dimensions that subsequently ends up with a blank or missing associated network node, thus causing attempts to populate the area to fail.
The dmcli PLCA command (Purge Library Cache Area) does not currently remove sub-directories from the library cache area root directory. The only way to remove sub-directories is to use the "/purge_all" qualifier and then recursively remove the sub-directories from the library cache area root directory.
There is a known issue on Windows such that if you use the SCWS command with the new /USERS parameter to specify a group, the Windows session may terminate with a crash. To avoid this Windows-specific issue, you must specify the individual users in the group rather than the group itself.
When running the dmdba upgrade command specifying a user name containing DBCS characters, the command may fail with an error. The solution is to set the DM_TMP environment variable to a path containing only ASCII characters before running the command.
If you attempt to deploy an earlier revision of an item to a stage as a result of a name change, and there is a later revision of the same item already deployed to that stage, no action will in fact take place, because the newer (deployed) file has precedence. Currently, Dimensions does not display a message to warn you of this fact.
The Global Stage Lifecycle (GSL) allows for transitions back to earlier stages in the lifecycle. However, this is not recommended as a method of rolling back changes from deployment areas using Baselines, as this will leave the deployment areas in an inconsistent state. Requests can be rolled back as long as the item revisions related as ‘in response to’ are unique to that request.
There are some workarounds for restoring deployment areas back to previously deployed versions described in the knowledgebase article S134447. See the Serena Support Web site for this article.
When a Dimensions CM client gets multiple files from the Dimensions CM server, and a library cache is fully populated. the server sends a single response message to the client detailing which files needed to be gotten from the library cache. This causes the Dimensions CM client to get each file individually from the library cache. When both the Dimensions CM client and the library cache are located on Windows machines, this makes the transfer slow unless delayed ACKs are turned off on all clients and the library cache.
To overcome this problem, set the following variable in the dm.cfg file.
DM_BULKDIRECTCOPYEX_ENABLE y
When this symbol is enabled, the Dimensions CM client sends a single message to the library cache requesting that the cache streams back all files in a single package.
If you have selected the Show User Roles and Privileges option for an object, you may find that when you click on the Privileges tab, the desktop client terminates and the session expires. This is an intermittent problem.
When using the new feature for filtering the rows in a content window grid display, the Action Date is not enabled for requests in the drop down list of available columns.
In the Prime Request dialog, it is necessary to enter the required request in the 'Priming Request' field on the General tab before selecting the Attributes tab. If the Priming Request is entered or changed on the General tab after the Attributes tab has been selected, the Attributes tab will not be updated with the attribute values mapped from the new priming request. This is because the details of a particular tab are saved when another tab is clicked, and then restored when returning to that tab.
The behavior of the Find Requirement dialog in the desktop client has been changed for this release in two significant ways.
The second change above means that it is possible to select the same requirement more than once in the Find Now tab, and open a requirement display. In this case, the resulting display will only contain each specific requirement once regardless of the number of times it was selected in the Find Now list. The specific requirement that is actually displayed is the one selected last in the results list, and any RM container data visible will relate to this selection only. In order to open a requirement from a specific container it is preferable to use the Catalog node in the My Current Project tree and navigate to the required container and requirement(s).
This issue is specific to the use of the Find dialog to open Requirement views, and does not affect other uses of the Find dialog, for example when invoked using the find […] button.
Custom tools in the desktop client now allow you to place an entry for a custom tool anywhere on the pulldown menus by using the Menus/Toolbar tab of the Customize dialog box, instead of having it inserted in the default location in the Tools menu. However, if you use this feature when adding a custom tool, and you subsequently want to delete it, you must first delete all entries for that tool in the pulldown menus by using the Menus/Toolbar tab before deleting the tool using the Tools tab. If you delete the tool on the Tools tab first, blank entries will remain in the Customize Menus/Toolbar dialog box.
If you have used the Windows Explorer integration to both rename a file locally and modify it, and subsequently run the Synchronize wizard, in "upload only" mode, the change will be reported as a conflict in the Synchronize wizard when it is run in "upload only" mode. In this case, the change type is incorrect, as the item has not changed in the repository. This means that you cannot use the Synchronize wizard to synchronize that particular change when in upload mode, forcing you to ignore it. In order for the change to be shown correctly as a non-conflicting local rename and modification, you will need to run the Synchronize wizard in full synchronize mode, and ignore any downloads from the repository that the Synchronize wizard will have selected if you do not want them.
If you are using Internet Explorer on Windows Vista to access Dimensions web client, the enhanced security features of that browser may prevent the web client from reading or writing files to local disks. If this occurs you will probably see a message similar to
java.io.FileNotFoundException:<full pathname>(Access Denied)
This is because Internet Explorer on Windows Vista has Protected Mode enabled by default, and this prevents software running in the web browser from accessing the disk.
Currently, the recommended workaround for this issue is to add the Dimensions CM web server's address to the list of Trusted sites in the Trusted sites security zone. To do this, proceed as follows:
The displaying of the Dimensions CM custom columns in Windows Explorer is not supported under Windows Vista. To obtain this information for a file:
You can still identify the change type from the decorations added to the file icon.
Dimensions CM cannot fetch items to Windows platforms whose resulting file paths would exceed 260 characters.
If you have changed any item types in Dimensions CM, you may receive errors when checking out items of that type. If this occurs, you need to close and restart Eclipse.
Depending on the type of installation, different steps will be necessary, as detailed below, for the IDE to correctly recognize the plugins:
- Open the Update Manager UI (Help | Software Updates | Manage Configuration)
- Locate, and expand, the path where you installed the Dimensions plugins. Select "Serena Dimensions Eclipse Interface X.X.X" where this identifies the version that Eclipse believes to be active.
- Select "Replace With Another Version" on the right side. If there are more recent versions than the one that is currently active, choose the most recent version. Click Finish, and restart the IDE if prompted. If the currently active version is already the most recent, no additional steps are required.
- Open a command shell and change the directory to the location where RAD 7 is installed such as:
C:\Program Files\IBM\SDP70
- From the command line, run the following command where the -to parameter specifies the directory where previous version of the plugins was installed. You may need to specify the full path to the java executable if it is not on the system path:
java -cp startup.jar org.eclipse.core.launcher.Main
-application org.eclipse.update.core.standaloneUpdate
-command removeSite
-to "C:\Program Files\Serena\Dimensions 10.1\CM\Integrations\RichEclipse3.x"
There is a problem when checking in a DOORS baseline with items that have a single-state lifecycle. The process does not complete and relationships are not created. It is necessary to define items with multi-state lifecycles.
When mapping a Serena Business Mashup field against the design part, you must make sure that this field (or it's selection list) always contains the full design part specification, not just the design part ID (for example: CM_QLARIUS:CM_QLARIUS.A;1).
The same version of a requirement may be in multiple RM containers. When a requirement is related to a request, it is the specific version of the requirement in the specific selected collection that has the relationship, not that version of the requirement in each collection that it appears in.
There is a defect such that the relationship for all requirements of the same version are shown in each collection regardless of the collection used to create the relationship. If a requirement/collection combination is selected to create a baseline and that combination doesn't have a related request, the baseline creation will fail.
The solution when creating the above CM baseline is to select the requirement in the container that was used when relating the requirement and request. Identifying that container may be done by inspecting the relationships for the required change request. In the desktop client, configure the Change Request display such that related requirements are visible, and that the requirement attribute "Container Name" is also displayed. Select the change request and open a new display. The RM container used to create the relationship will be displayed in the related requirement's attributes.
This is a defect such that creating baselines from requirements in collections (or RM baselines) containing ‘.’ in their names fails to validate the requirement correctly and thus baseline creation fails.
Remove any "."s from the names of Collections (or RM Baselines)
that are to be associated with Dimensions CM.
To improve performance, Dimensions CM application servers now cache some privilege and role information. In general, this information is refreshed only when an application server is allocated to a session, i.e. on connection or when an idle session is reactivated. If any privilege assignments are updated in the Administration Console, the changes may not take effect during existing client sessions. In this case, the user will need to restart the client session for the new privilege settings to apply.
This behavior can be changed by setting certain variables in the dm.cfg file. For further details, see the Administrator's Guide.
The following changes have been made to the privilege rules that are enabled in a default installation:
If you are the user who defined an area, but when you attempt to update its properties you receive an error stating that the "Update Work Area Properties" privilege is needed, you will need to have that privilege granted to your user.
When using the Build Administration function from the desktop client, and your browser is IE 7.0, you may experience a problem where you are subsequently presented with the Dimensions Build Login page after performing certain actions. This is caused by the cookie handling in IE 7.0. To remedy this, apply the latest hot fixes for IE 7.0 and enable them as described in the article at the following URL:
http://support.microsoft.com/default.aspx/kb/935778
There is an intermittent problem with conflicts between the link list libraries and a tasklib (STEPLIB) in the sBem. This manifests itself as the sBem loading the wrong module in the attached sub-task. For example, if IGY210.SIGYCOMP is in the link list and IGY310.SIGYCOMP is on the TASKLIB for the compile step, then the wrong version of IGYCRCTL gets loaded, and then the COBOL compiler fails (because a subsequent sub-module of the COBOL compiler is not in synch with the main line).
You can restore this behavior by putting the right version of the COBOL compiler into the STEPLIB for the sBem; or the more recommended approach of having the right version of COBOL in the link list and therefore not using TASKLIB at all. This does not occur if you remove the extraneous version of COBOL from the link list.
To turn off many of the mainframe agent’s messages during startup, set the following variable in MDHTDCFG:
DM_MVS_START_QUIET YES
The Dimensions Build User’s and Administrator’s Guide (dmcm_build_users_admin.pdf) was renamed in a previous release to the Dimensions CM Build Tools User's Guide (dmcm_build_tools_users.pdf). Some online help topics may still reference this book by the old title.
Copyright © 1988-2008 Serena Software, Inc. All rights reserved.
This document, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by such license, no part of this publication may be reproduced, photocopied, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Serena. Any reproduction of such software product user documentation, regardless of whether the documentation is reproduced in whole or in part, must be accompanied by this copyright statement in its entirety, without modification.
This document contains proprietary and confidential information, and no reproduction or dissemination of any information contained herein is allowed without the express permission of Serena Software.
The content of this document is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Serena. Serena assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.
Trademarks
Serena, TeamTrack, StarTool, PVCS, Collage, Comparex, Dimensions, RTM, Change Governance, and ChangeMan are registered trademarks of Serena Software, Inc. The Serena logo, Dimensions, Professional, Version Manager, Builder, Meritage, Command Center, Composer, Reviewer, Mariner, and Mover are trademarks of Serena Software, Inc.
All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.
U.S. Government Rights
Any Software product acquired by Licensee under this Agreement for or on behalf of the U.S. Government, its agencies and instrumentalities is "commercial software" as defined by the FAR. Use, duplication, and disclosure by the U.S. Government is subject to the restrictions set forth in the license under which the Software was acquired. The manufacturer is Serena Software, Inc.,
1900 Seaport Boulevard, 2nd Floor, Redwood City, California 94063-5587.
This product includes software developed by The Apache Software Foundation (http://www.apache.org/).
This product includes software developed by Computing Services at Carnegie Mellon University (http://www.cmu.edu/computing/).
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)
CONTAINS IBM(R) 32-bit Runtime Environment for AIX(TM), Java(TM) 2 Technology Edition, Version 1.4 Modules
© Copyright IBM Corporation 1999, 2002. All Rights Reserved
Copyright © 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper
Copyright © 2001, 2002, 2003 Expat maintainers.
Copyright 1998-2006 The OpenLDAP Foundation.
Portions of this Software are derived from IBM Corporation Sample Programs. Copyright © IBM Corp., 2002, 2006. All rights reserved.
Optional Oracle components embedded in Dimensions are also subject to the following Copyright Notices:
Copyright © 2003-2006 Oracle Corporation. All rights reserved.
NOTICE OF RESTRICTED RIGHTS
Programs delivered subject to the DOD FAR supplement are 'commercial computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, programs delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.
End of Readme