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 ChangeMan ZMF ERO Updated DB2 Table Descriptions
The ChangeMan ZMF ERO DB2 Release Audit and Release Management table layouts have changed since they were documented in the "ChangeMan ZMF 5.5 ERO Getting Started Guide".
CMS-XML ERO - Release audit receiving DB2 Insert error SQLCODE -180
ERO - Release audit receiving DB2 Insert error SQLCODE -180
CMS-XML ERO DB2 table CMNRLSHST is not being updated properly when RETRIEVE is done
ERO DB2 table CMNRLSHST is not being updated properly when RETRIEVE is done
CMS-XML ERO autoresolve with DB2 components
When submitting audit with autoresolve a recompile of a DB2 component does not copy the DBR back to the package staging library
CMS-XML Unable to BIND or Recompile CMNRARPT (ERO customers only) under DB2 V8
The following BIND Package BIND works under V7 of DB2 but returns these errors under DB2 V8: //JOBLIB DD DISP=SHR,DSN=DB2Q105.SDSNEXIT // DD DISP=SHR,DSN=CEE.SCEERUN
CMS-XML ERO 21 job not created for DB2 packages when attached to a release
The 21 job is not created for DB2 packages when attached to a release. If the package is detached from the release and frozen, the 21 job is created.
CMS-XML ERO DB2 -803 error at checkin
The customer has relinked components, object code, and LCT cards with the same name in a package. When they attempt to checkin these components, with REPORT FORMAT SHORT, a DB2 ERROR message is displayed during the checkin processing. Some of the components receive a checkin error, and a -803 DB2 error is reported in the task.
CMS-XML ERO: DB2 performance problems since upgrade to 5.6
An ERO customer recently upgraded to CMN ZMF 5.6.0 from 5.5.0. This upgrade coincided with intermittent DB2 performance problems that when encountered, can stop all other work on their development LPAR. The customer has analysed their DB2 environment with their DBAs but no obvious resolution from a DB2 perspective appears to exist.
CMS-XML ERO: CMN21 jobs are not submitted during package install, leading to DB2 timestamp errors.
However the CMN20 jobs were submitted. This caused -805 DB2 errors in the customer's PROD environment. In non ERO packages, the CMN21 and CMN20 jobs are both being submitted in the correct order.
CMS-XML ERO: Rlsmarea Package Retrieve failed DB2 CAF error processing RLSHST/INSERT01
<response> <statusMessage>CMR2591A - DB2 CAF error processing RLSHST/INSERT01 request</statusMessage> <statusReturnCode>08</statusReturnCode>
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs