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 10.x / 2009Rx / 12.x : z/os batch interface MDFLCMD => how to protect the file defined in //LOGIN in order to nobody can see its contents ?
... your RACF administration group . ... the command : AD 'dataset. ... ... GENERIC on the AD command. ... : on each member of your sysplex ... You can then extend this access to specific individuals (foo, bar) or groups (grpfoo) using permit 'dataset.**' ... or if your technical user has a default group for which a user has Group SPECIAL then those users can alter the protecting profile to allow themselves access - but this activity will be auditable via SMF logging.
CMS-XML Dim9: Error: User authenitcation failed... trying to authenticate on remote node
If remote node is UNIX, make sure all directories in the hierarchy from root to $DM_ROOT have x bit on owner, group and other. Make sure user account exists on the remote node, and authentication is not through LDAP
CMS-XML Dim12: Is there a way to list the users or members within a group?
The command of LGRP will provide a list of groups and the users within. The formatting of this command can provide undesired results by placing the group name and description on different lines.
CMS-XML Dim10: Last Updated By showing Last User Added for Groups in Admin Console
Under groups , when adding a new member to a group , the last updated field shows who was the last user to be added, rather then then who added them. To replicate Open Admin Console, select Groups
CMS-XML Dim10: A user who is in the admin group cannot update an item attribute
Under certain circumstances it can happen that a user who is a member of the admin group can not update item attributes using the Desktop Client (they appear in italics which means they are read-only). The same action works fine from the Desktop Client console or command line.
CMS-XML Dim CM 12.2: Role Assignments not updated correctly when removing a user from a group
When removing a user from a group they are no longer able to browse an item even though they hold a valid role via another group membership . For example:
CMS-XML KM-Dim10: Reported Defect DEF112645: Duplicate User Interface Profiles in Desktop Client Popup When Profile Assigned to Group and User
Duplicate user interface profiles appear in the popup menu used to switch user interface profiles in the desktop client. This happens when the interface profile is assigned to a user as well as one or more user groups that the user is a member of.
CMS-XML KM-Dim10: Multi column attributes sometimes fail to populate from validation groups
Unless those attributes in the validation group are are in adjacent positions in the block only the first one can be populated with values from the valid set. The other members of the validation cannot be populated. (Note that this is not an auto population issue as manual selection of the values fails).
CMS-XML Reserving Concurrent Licenses for Groups of Users
To ensure that each user group has an equal number of available licenses, reserve 5 for each group. Then, none of the functional areas can use up all 20 available licenses. For example, if 5 members of the Development group are logged in, no more may log in.
CMS-XML KM-Dim10: Reported Defect DEF106227: Browse Privileges
To reproduce in Qlarius 1. Deassign the group membership for DP 2. Modify the existinfg browse privileges for requests and items so that the only general grant rule selected is
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs