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 HPS210W and *Error 021 adding object to group
SCROLL===> CSR Press END to Exit Tracked Object(s)
CMS-XML SSM830: Using RACF groups, in place of TSO UserID's, for Change Tracking Access
If this user now belongs to our group, he would immediately be authorized to do all work he is supposed to do. Adding the add / delete user to/from the SSM groups is not an option. Enhancement Request:
CMS-XML SSM821: Erroneous message on Group Revoke Authorization panel (HPSCONU2 )
Panel HPSCONU2 informs users that a (D) is a valid command. The only valid line command should be (R) to REVOKE the user.
CMS-XML HPSTRACK utility adds hex '00' to end of history output and LRECL changed to LRECL=134
HISTORY=(DD=HISTFILE, DEPARTMENT=MAINFRAME, GROUP =SYSTEM, FROM=2019/01/07,TO=2019/05/31)
CMS-XML SSM830: Batch Deletes for (new) Groups defined under SSM V8.3.0 failing
ChangeMan SSM, 8.3.0 DETAILS: After installing SSM V8.3.0 we are still having a Group DELETE problem in SSM.
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 SSM823: Message HPS1351W RC=22 GRPDEL function failing
HPS1300I HPSTRACK 19:48:46 EOF HPSIN: Cards read=2 with 2 Commands. HPS1344I HPSTRACK 19:48:46 User T171236 Revoked from group HUGEPDS HPS1351W HPSTRACK 19:50:26 Delete object:
CMS-XML Wrong message HPS1307E issued for HFS Group with no INCLOBJ parm.
HPS0000I HPSTRACK 05:01:27 Job Started: 2011/02/15_05:01:25 Job Ended : 2011/02/15_05:01:27 Warning cnt: 0
CMS-XML RACF and Conversion of SSM V8.2.3 to V8.3.2. Additional Detail
Finally, the customer will want to switch over to using CTUSERSAFAUTH (User Group profiles) rather than tsoid's for Change Tracking User authority. The final step will be to change HPSPARMS (temporarily) back to using the SITEADMINS parameter (presumably, the customer commented it out before starting the RACF conversion), and will comment-out the CTCLASS and CTSITEADMIN parameters (again, temporarily), in order to use the ISPF or batch interfaces to delete all his tsoid-based Groups and Users .
CMS-XML HFS Change tracking report Userid field too small
"TSO LU OMVSUSR1" gives USER =OMVSUSR1 NAME=OE-KERNEL-ID (STC) OWNER=OMVSGRP CREATED=97.315 DEFAULT- GROUP =OMVSGRP PASSDATE=N/A PASS-INTERVAL=N/A PHRASEDATE=N/A ATTRIBUTES=PROTECTED REVOKE DATE=NONE RESUME DATE=NONE LAST-ACCESS=09.330/13:27:54 CLASS AUTHORIZATIONS=NONE NO-INSTALLATION-DATA NO-MODEL-NAME LOGON ALLOWED (DAYS) (TIME)
Pages [Next]

Welcome kb sso

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs