Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Logging into Request Center and get "Error getting catalog: Forbidden"
Logging into Request Center and get " Error getting catalog : Forbidden"
CMS-XML Error getting catalog: Serena Security Token invalid or expired when logging into Request Center.
Error getting catalog : Serena Security Token invalid or expired when logging into Request Center.
CMS-XML Error getting catalog: Request entity too large OR Error getting Demand and Categories views: Request Entity too large
Error getting catalog : Request entity too large OR Error getting Demand and Categories views: Request Entity too large
CMS-XML Error Getting Catalog: No Service Catalogs Found. Contact your system administrator to make sure applications are promoted and services migrated.
Error Getting Catalog : No Service Catalogs Found. Contact your system administrator to make sure applications are promoted and services migrated.
CMS-XML SSM831 Getting message HPS0100W message with RC=004, and x'0218' error saying, Volume not mounted during Fingerprinting.
Does SSM have any issues with Fingerprinting a PDSE that is not cataloged ? We are running a Fingerprint creating batch job of some datasets on a volser, and then on a different volser of the same dataset names, but not cataloged . When we run against the not-cataloged version all the datasets are ok except the PDS/e?
CMS-XML ENCODE - DECODE gets error FILENAME DDELXXX.AE32B UNABLE TO ALLOCATE
FILENAME DDELXXX.AE32B UNABLE TO ALLOCATE IKJ56228I DATA SET DDELXXX.AE32B NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED RECORDS COPIED:
CMS-XML FDM batch job using PGM=IKJEFT01 issues RC=0 even when job gets error
DATA SET T250963.T250963.JCL.MLS.CNTL.TEST NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
CMS-XML Dim2009R2: Edit request get error: COR0005615E Another user is currently performing an operation on request
In this situation, once the problem is discovered, it may be possible to restore the change requests to a state where they may again be edited by moving the affected change requests from the primary catalog to the secondary catalog and then again back to primary.
CMS-XML DIM10: Upgrade to Dimensions CM 10, now gets error when browsing change requests: SQL-24812(4207) ORA-24812: character set conversion to or from UCS2 failed
Use Dimensions to move the change requests that generate errors into the secondary catalogue and then back to the primary catalogue again. In many cases this will correct the problem.
CMS-XML KM-Dim9: SQL Solution: ora-00001 constraint error on sec_cm_attr_upd_hist1 trying to move change docs to secondary catalogue
Dim 9.1.2 User gets the following error when trying to move change docs to secondary catalogue : 1019-DBIO: Database I/O error occurred.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Updating a work area from a stream (demonstration)
This Dimensions CM demonstration shows you how to update a work area from a stream, restrict the update to specific folders in the stream, and exclude files from the update.
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
Dimensions CM: Working with Items, Part 2 (demonstration)
This Dimensions CM demonstration shows you how to copy item revisions to a work area using the Get and Update commands, deliver a modified file from a work area to a stream using the Deliver command, and action an item revision

Additional Assistance

  • Submit a Case Online
  • FAQs