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 CMNEX027 not overiding Promotion rule for selective demote.
CMNEX027 not overiding Promotion rule for selective demote .
CMS-XML ZMF4ECL: Selective demote lists all promote-able package components
ZMF4ECL: Selective demote lists all promote-able package components
CMS-XML ‘CMN3285A - Not authorized to promote / demote this package’ when doing selective promote.
User has authority to promote to first promotion level, but not the higher promotion levels. When the package is promoted beyond the first promotion level, then one of the component s is selectively demoted back to staging, the user modifies the component and attempts to selectively promote back to the first promotion level where they have authority to promote. User receives the message CMN3285A - Not authorized to promote / demote this package.
CMS-XML ERO: Selective demotion submits promote request
Attempts to submit a selective area demote from the ERO Package option (7.P line command DM) results in the submission of a promotion request.
CMS-XML Demote requests always display custom user options panel CMNUSV1
Demoting a package (full or selective ) always displays the custom user options panel CMNUSV1. This is regardless of whether or not the ‘User variables’ option is selected on panel CMNRPM04.
CMS-XML Memo Delete and Demote inconsistency between ZMF4ECL and ZMF.
If a Selective demote for a package that has one component in it has been performed you cannot then do a FULL Demote as in ZMF to memo delete the package
CMS-XML Unable to promote after demoting to STAGING
Promote to the first promotion level Do a selective demote from that level Then try a selective promote of the same components back to that level
CMS-XML DB2 vars REBPKG and REBIND blank during DEMOTE with XML
If you use the XML service to DEMOTE a package containing DB2 components, the skeleton variables &REBPKG and &REBIND are blank, causing incorrect processing in CMNDB2PL. Problem seen on both full and selective demote . ISPF driven demotion works fine at this level.
CMS-XML Invalid ‘CMN3067I’ messages when attempting to unfreeze selectively demoted source component
When two or more source (SRC) components are in a package that has been promoted, if you selectively demote one source (SRC) component and its associated components (LOD/LST), when you attempt to unfreeze the selectively demoted source (SRC) component you get the invalid message ‘CMN3067I - Promotion rule 2 requires selective demotion prior to unfreeze.’ If there is only one source (SRC) component in the package the unfreeze works.
CMS-XML Selective promote requests failing with invalid CMN3297I (Mixed promotion level prohibited)
When this problem occurs it appears that executing a selective demote of all other package components from the level at which the components being promoted currently exist resolves the issue. For example, if the components being promoted currently exist at level 2 and are being promoted to level 3, then demoting all package components currently promoted to level 2 will circumvent the issue. Obviously this is very inconvenient.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs