Find Answers

Filter Search Results
All Products:

Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Audit for "same-named" source components sharing the same baseline dataset
***** R000120 Created 2012/08/13 at 14:24:34 by ACHERNA * 2/12/30 Package Status: DEV * cription of member from library directory entry * R:SR2 CHER:SR3 * **************************
CMS-XML Dimensions returns error when user tries to revise a baseline with a directory item.
A baseline exists that contains a directory item.
CMS-XML Folder offset is broken when doing Get (recursive) on sub-project baseline
User then does a recursive Get on the baseline sub-project. The baseline contents are fetched to work area, but folder offset is not included in the path to work area
CMS-XML Baseline library member names containing national characters are not being translated correctly
Component/member names in baseline libraries that contain 'national' characters (i.e. #, @ and $ in US terms) are not being translated in the expected manner for non-US environments. They can be browsed but attempts to execute functions against them are liable to fail with ‘member not found’-type errors. The same member names are displayed and processed correctly in other ZMF4ECL folders (e.g. Data Sets, package library types, etc.).
CMS-XML Checkout and baseline browse of HFS files fails in various manners
And for a wildcarded component that has no spaces in directory name (e.g. nospace/dummymem): COMPONENT NAME ===> nospace/* Member list (panel CMNHMLSS) is presented but after selecting a component and pressing ‘enter’ the following error is returned:
CMS-XML 12.2.0.3 : full filename not updated in baseline view after doing SWF followed by a CRB
/ PART ="PAYROLL:VC.A;1" /WS_FILENAME=" folder 1/ folder 2/ folder 3/item_one.c" /FORMAT="C" /COMMENT="Initial Revision" /CHANGE_DOC=("PAYROLL_CR_28",) /KEEP Create Item - Item PAYROLL:ITEM ONE C-73210370X1200X0.A-SRC;1 has been forwarded to DMSYS Operation completed
CMS-XML S0C7 in CMNRCRCP at offset 0000D32C during recompile from baseline
Customer has a baseline dataset that contains many members with unusual PDS directory entries. Whenever a recompile from baseline is performed against one of these members, the started task abends with a S0C7 in CMNRCRCP at offset D32C.
CMS-XML Dim CM 12.2: Eclipse recommends additions rather than deletions when merging streams and baselines
Using the Eclipse plugin if you merge a Stream and a Baseline that contains files and folders which have been deleted those deletions are not propagated properly. The deleted folder is shown as a conflict and deleted items are shown as additions to the workspace. The following scenario from the demo QLARIUS product illustrates the problem.
CMS-XML CMNSSIDN - synchronize SETSSI in IDRdata and load directory during Relink
This CR is opened to ensure that the SETSSI of a component being relinked is in synch between the IDRdata and the load library directory. Issue: When the relinked load sub-module located in baseline contains the SETSSIs in the IDRdata that is not in synch with the SETSSI in the load library directory , the subsequent package containing the relinked composite load will produce the invalid SYNCH20 flag. One way that the SETSSI goes out of synch between IDRdata and library directory is when the component is relinked using the same load libtype.
CMS-XML Checkout and baseline browse of HFS files continues to fail in certain situations
- a baseline folder contains a file named tmp/pt0065e1.tmp.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Overview (demonstration)
This animation describes what you need to know about Dimensions CM to help you get started with your developement tasks.

Additional Assistance

  • Submit a Case Online
  • FAQs