Find Answers

Filter Search Results
All Operating Systems:
All Others (9)
All Products:
ChangeMan ZMF (111)
All Solution Types:
Documentation Update (5)
Error Message (2)
Installation & Customization (5)
Product Tips & Advice (15)
Source:
Defects (93)
Solutions (18)
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML audit runs clean if foreign copybook was used
audit runs clean if foreign copybook was used
CMS-XML ERO promotion failing to clean up promotion levels
ERO promotion failing to clean up promotion levels
Similar Answers
CMS-XML Cross Memory does not release or clean the Getmain areas.
Cross Memory does not release or clean the Getmain areas.
CMS-XML Lower level promotion shadow libraries not cleaned up when promoting to a higher level
Lower level promotion shadow libraries not cleaned up when promoting to a higher level
CMS-XML IMS components (FMT and MFR) not cleaned up from promotion shadow libraries when demoted
IMS components (FMT and MFR) not cleaned up from promotion shadow libraries when demoted
CMS-XML **BETA**...SKEL CMNIMPRM at demotion does not clean up promo libs.
**BETA**...SKEL CMNIMPRM at demotion does not clean up promo libs.
CMS-XML OC4 abend in CMNVRARE occurs in the Started Task, when auto clean-up of ERO releases is flagged
OC4 abend in CMNVRARE occurs in the Started Task, when auto clean -up of ERO releases is flagged
Similar Answers
CMS-XML Clean up the overflow characters in 'CMND252I ERROR: COMPONENT RECORDS NOT DELETED.****000000 20160909 20160114 ALL'
Clean up the overflow characters in 'CMND252I ERROR: COMPONENT RECORDS NOT DELETED.****000000 20160909 20160114 ALL'
CMS-XML ERO Test Area automatic cleanup won't detach empty package
CMNTST53 RELEASE PACKAGE COMPONENTS CLEAN -UP ----------------- Invalid Status COMMAND ===> SCROLL ===> PAGE TESTED LIB TESTED PKG USER ORIGINATING USER TEST FAILURE
CMS-XML Manual cleanup of source records in non-source
The fixes for this problem are in 4.1.6 package 40, but these will not clean up the bad records. If you do not want to abandon the package, the manual fix for these records is below. To save frustration, wait until you install package 40 so the invalid records do not recur.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs