Find Answers

Filter Search Results
All Products:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
CMS-XML Dim CM 12.1: Inclusion filter generates metadata read error when used to download a baseline
The outcome is that those files which do not meet the inclusion criteria return an error indicating a failure to read the metadata for the item. The steps to recreate the problem are as follows: - a) Create a new filter called Z in Adminconsole that has the inclusion rule COBOL /** b) Create a baseline with the items: - portalprotect-configuration COBOL \hello c) Run the following command to download the Baseline to a ZOS node: - DOWNLOAD /BASELINE="QLARIUS:UCM-TEST" /USER
CMS-XML z/os build : incorrect data format picked up
- create a request R1 - create an item for cobol program P1.srcbat using C1 copybook and relate it to R1 (assume P1.srcbat has the data format COBBAT) - create an item for C1.srccopy copybook and relate it to R1
CMS-XML / Build => impacted targets not found when /TARGETS symbol is not specified int he BLD command
LOAD(*) <<- OBJ(*) <<- SOURCE(*) [FORTRAN] LOAD(*) <<- OBJ(*) <<- SOURCE(*) [ COBOL ] If the two targets (LOAD(*) and LOAD(*) have the same name (for example Target), then when building a particular source entity SOURCE(FOO),

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs