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 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)
CMS-XML SSM832 16D Abend accessing the SSM ISPF facility - avoidance solution.
SSM832 16D Abend accessing the SSM ISPF facility - avoidance solution.
CMS-XML SSM830: Using RACF groups, in place of TSO UserID's, for Change Tracking Access
SSM830: Using RACF groups, in place of TSO UserID's, for Change Tracking Access
CMS-XML compare of PDS members results in CSV026I HPSTRANS NO ACCESSED followed by CSV028I ABEND306-34 JOBNAME=M1GNW00 STEPNAME=
compare of PDS members results in CSV026I HPSTRANS NO ACCESSED followed by CSV028I ABEND306-34 JOBNAME=M1GNW00 STEPNAME=
CMS-XML HPS0578W HPSDSFTP 08:35:53 Open failed. READ access not authorized
HPS0578W HPSDSFTP 08:35:53 Open failed. READ access not authorized
CMS-XML SSM Started Task gets error SER0603E TCP/IP logons will not be allowed due to an error in passticket initialization
SSM Started Task gets error SER0603E TCP/IP logons will not be allowed due to an error in passticket initialization
CMS-XML MLS does not honor TSO ID access list (Internal Method).
MLS does not honor TSO ID access list (Internal Method).
MS-WORD Title
SSM 832 Cumulative Patch Number SSM83222 - Fix Descriptions: Delay accessing Main Menu Wrong message when fingerprinting a volume which is offline
CMS-XML SSM823: MLS not working as designed
MLS not working as designed. With ACCESS =NONE, user can still update (save) a protected member.
CMS-XML Web Browser complains the SSL certificate has expired, even though the expiration date is in the future.
When accessing a URL over https, a browser may complain the certificate date is invalid, even though the current date is within the validity range of the certificate. In the following examples, the clock of the reporting PC had the (correct) date of 11/18/2020: Internet Explorer:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs