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 Approvers getting project notification and email for each file in the project
********* INSTRUCTION FOR APPLYING PATCH ********** 1. Shut down DS server. 2. Exit from Change Man DS clients or development IDEs
CMS-XML Approver.Pkg.List XML Service does not sort the returned approver entities correctly
The XML Services interface will only retrieve the data as it is physically stored within the appropriate master file record. Any data manipulation or sorting that is required is the responsibility of the client code that invokes the service. This is true for all services and not just the Approver.Pkg.List service.
CMS-XML CMNEX009 additional dynamic approvers not being added for same libtype
Customer reported same issue in CR 16511 ( CMNEX009 is adding duplicate entity names), and added the additional code in the solution: CMNEX009 to be updated as follows (add 4 lines marked <<<<<): X09$1000 DS 0H
CMS-XML ERO: Associated install approver not added for scratch components
A customer adds one or more release install approvers to each release based on library types affected in the release. This works fine for new or existing components that have been changed in the release. However, if there are only scratch requests for components of the relevant type in the release then the associated install approver is not being added to the release.
CMS-XML INFO approval process no longer checking approver RACF entity
A customer is reporting this as a security loophole in the approval process. Prior to defect DEF175989 the customer states that the loophole did not exist.
CMS-XML CMNEX009 is not adding approvers.
When attempting to add dynamic approvers based on libtypes contained in the package (via CMNEX009), the approvers are not being added. Customers may also see the following error message being issued in the SERVER started task output at package freeze time when this problem occurs: 10:31:20 IKJ56231I UTILITY DATA SET NOT ALLOCATED, SYSTEM OR INSTALLATION ERROR+
CMS-XML POA - Package stuck in APR state after all approvers
Customer indicated that they had to delete the users who were part of the approval process and recreate them due to other licensing issues.
CMS-XML POA: Cannot Remove Approver Group
Using the web client , if you setup an approval group and add users and groups to this approval group and add then add this approval group to an application and you create a package and then move the package through the various stages of the approval process and then it finally gets installed, you are not allowed to remove an approver user/group from the approval group as a message comes up and says, "Approver Has Approval Assignment".
CMS-XML Mail Client Advanced Features
Mail Client Advanced Features
CMS-XML Silent Installation of Client Components
Silent Installation of Client Components
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs