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 Operational Integrity automatic function does not work with TSO based department/group
Set SITEADMINS and comment out CTCLASS and CTSITEADMIN in the HPSPARMS member to enable TSO mode. Set AUTOTRACK YES, AUTODEPT 'admin id', AUTOGROUP 'TSO mode group name' Bring started task up
CMS-XML MLS does not honor TSO ID access list (Internal Method).
Command ===> Specify an explicit DSN, and a member name or pattern ending with an *. A member pattern of "*" will protect all the members in the specified DSN.
CMS-XML SSM830: Using RACF groups, in place of TSO UserID's, for Change Tracking Access
2. The revised HPSPARMS member shows how to define the new CTUSERSAFAUTH parameter, and contains some additional text explaining which parameters are used in which circumstances. This member should be copied into your HPSPLIB dataset and updated according to your needs. Set this parameter to YES when you are ready to switch over to the new SAF-based User Authority checking.
CMS-XML SSM823: Error in change tracking batch - recover option
//HPSIN DD * RECOVER=( GROUP =TESTGRP1,FOR=(01), MEMBER =( MEMBER 01), DSN=(STRQA.SSM.TEST.ENV.CT.PDS4),OBJECT=(STRQA.SSM.TEST.ENV.CT.PDS3))
CMS-XML SSM823: Need information regarding implementing MLS w/ACF2
TSO PE dsngrp1 CLASS(classname) ID(tsoid) ACC(UPDATE) TSO PE dsngrp2 CLASS(classname) ID(tsoid) ACC(UPDATE) Note: When defining MLS protected Entities, the MLS Administrator specifies in the Access List the appropriate RACF Group Profile name used to control access to each protected Entity (data set name/ member pattern/ file).
CMS-XML SSM830: Would like to use RACF groups vs TSO UserIDs for change tracking facilities
SSM830: Would like to use RACF groups vs TSO UserIDs for change tracking facilities
CMS-XML Operational Integrity not reflecting updates to datasets in the group
Operational Integrity not reflecting updates to datasets in the group
CMS-XML HPS210W and *Error 021 adding object to group
HPS210W and *Error 021 adding object to group
CMS-XML SSM821: Erroneous message on Group Revoke Authorization panel (HPSCONU2 )
SSM821: Erroneous message on Group Revoke Authorization panel (HPSCONU2 )
CMS-XML Incorrect DSORG set when object is defined to multiple groups
Incorrect DSORG set when object is defined to multiple groups
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs