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  
Pages [Next]
CMS-XML How To: - Version Manager and/or System Administrator wants to setup archive directories so that user do not have delete rights on an NT Server
This policy should result in a minimal amount of data loss and/or down-time.
CMS-XML How to modify the subject line of an outgoing item email
The resulting email a user receives when you send one out from an item is composed by two different template files which both construct your email's subject line. ... This line is what pre-populates the subject field that you see when you go to send an email from an item . ... The resulting auto-generated subject line you should see would resemble something like this: ... No matter what templates you change, be sure to backup your existing ones and perform a "Put files into Database" in the System Administrator after saving the changes.
CMS-XML Change the Text Color of Inactive Items
The example below demonstrates how to change the color of inactive items to red. ... 4. From SBM System Administrator , select ... 5. Stop and start your Web server and clear your browser cache for the change to take effect .
CMS-XML Mashup Script may cause unexpected results when using UpdateWithLock() in a Shell.Item context
If you are using Mashup Scripts where you have a Shell.Item, invoking the Ext.UpdateWithLock() function may cause unexpected results to the current item. For example, if you are using Mashp Script to write to a field on the current item in a Pre- or Post-Transition context, in one case, trying to UpdateWithLock causes the PROJECTID field to be set to zero (" 0 "). That makes the item unaccessable by anybody.
CMS-XML PBrowse/PVIEW of VSAM data set results in PDS961E VSAM POINT error at RBA=00000000; Feedback=D708009C
CMS-XML KM-Build6: Evaluation of Builder results in directory listing of files being displayed when trying to connect to Builder
The license must be pasted into the License Manager GUI and the license.ini file, located in the installation directory tomcat\webapps\openmake.ear\openmake.war\license, must be modified to point to the license server.
CMS-XML Dim CM 14.1.x: MDHNCL4501155E Error: Failed to write metadata for file "//DIMADM.PDEV.DIM.DEV2.URTLIB(GL0UNEX)"(rc = 5 msg = Verb DimPutRecord had outcome rc-rea: 5-11;
A problem was reported writing metadata files during a deployment on Mainframe. The same set of items was successfully deployed to two other areas:
CMS-XML Developement Manager 4.0.1: "General error" reported when attempting to update Backlog details
Scroll down until you see the list of "Role Services", and click on "Remove Role Services". In the resulting window under "Web Server -> Common HTTP Features" you will see "WebDAV Publishing". Uncheck this and proceed through the wizard to remove the service.
CMS-XML KM-Dim7: The Effects of Change Management Rules on Items and Change Documents
1) The individuals with the proper roles can extract, edit, update, etc. the Item without PCMS forcing a change document as long as the Item is not in the APPROVAL state. 2) Once the Item is actioned to the APPROVAL state, any attempt to extract, edit, or update the Item will cause PCMS to require a change document be generated and related as 'affected' to the item.
CMS-XML km-dim10 : Z/os : Get item / MDHNCL4501155E Error: Failed to write metadata for file "..." (rc = 8 msg = META010I Verb DimPutRecord had outcome rc-rea: 8-11; decode I/O error writing metadata - WRITE_ERROR)
check permissions on the local metadata for the specified item in the working location. It can be that a different user was used to fetch the item the first time it was fetched. Another useful thing you can try is to fetch the containing directory to a different (clean) USS location.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes

Additional Assistance

  • Submit a Case Online
  • FAQs