Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
PDF Serena Builder for Professional User’s Guide
Here are some commonly-experienced problems, along with suggestions for what to do. * Compiler complains of no input files This may be because the directory containing the source files are not specified in the Search Path. * Project was not found on the KB (Knowledge Base) server This may mean that your target definition file makes reference to a project that has changed or was deleted .
CMS-XML Builder Web Client appears to "hang" when accessing the KB Server.
For machines that do not have a connection to the World Wide Web or Internet, references from metadata on the KB server will not be resolved. This will manifest in the browser appearing to hang when loading the Builder Web Client connecting to the KB server.
CMS-XML KM-Build8: ZOS Does Openmake ZOS Build supports ++INC as dependencies?
Does ZOS Openmake Build support COBOL programs using CA-Librarian ++INC (INCLUDE) statements and COPYDD statements by the Scanner (build of materials) and as dependencies? These are used by the customer instead of the IBM COBOL COPYBOOK statement.
PDF Getting Started
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.
CMS-XML KM-Build8 How to use OMERRORRC variable in Builder 6.3.1
$OMERRORRC variable is not used in any of the Builder build scripts that are associated with specific build tasks within a Builder build. In order to use $OMERRORRC, you just call a Perl script as part of a pre- or post-build activity (run with either the -bp <script name> or -ap <script name> flags), and reference the $OMERRORRC variable as part of a routine you want to execute, based on the success or failure of a build.
CMS-XML SLM: How to consolidate multiple license keys for one Host ID into a single license file
If there is an existing serena.lic, rename that file to something else as a backup first before renaming the consolidated license file to prevent conflict .
CMS-XML SLM: Certain clients sometimes/consistently cannot connect to the License Server, especially from remote locations
(eg. vmreg -m "" Existing Linux/UNIX users execute the following command to update their SLM server reference with the one from the license.ini template file:
CMS-XML Serena License Manager 2.1.4 (SLM 2.1.4)
If multiple product releases are installed on a single system that all have their own client library, consider replacing all copies at the same time. This avoids potential conflicts when libraries are found through a search path.
HTML Serena Builder Readme
3.3 In Standalone Web Client: Click on Build Task to Enable Delete Button for Custom Options

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Delivering changes from a work area to a stream (demonstration)
This demonstration shows you how to deliver changes from a work area to a stream in Dimensions CM, restrict the deliver to specific folders in the work area, and relate a new item to the correct design part.
Dimensions CM: Resolving conflicts (demonstration)
This demonstration shows you how to resolve conflicts between your work area files and the item tip revisions in a stream in Dimensions CM

Additional Assistance

  • Submit a Case Online
  • FAQs