OA57889: RUCSA USE DETECTION AND THE SLIP RECOMMENDATION TO TRACE OFFENDERS IS FLAWED WHEN RUNNING UNDER A FLIH.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• See APAR Abstract.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of HBB7790 and above with IEASYSxx                     *
  * RUCSA defined wishing to identify software                   *
  * that faults on user key CSA storage.                         *
  *                                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * GTF trace records are not collected                          *
  * for RUCSA faults as described in                             *
  * the z/OS Migration publication.                              *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The 'Removal of user key common areas' section of
  the Migration publication documents steps that can
  be taken to capture GTF trace records to assist in
  identifying software that faults on user key CSA
  storage when IEASYSxx RUCSA is defined.  These
  steps do not work as documented for RUCSA faults.
  
  Note: 'RUCSA faults' refer to faults on user key
        CSA storage when IEASYSxx RUCSA is defined.
  

Problem conclusion

• A new RSM trace event (RUCSAFLT) is introduced to
  trace RUCSA fault events and is documented in the
  z/OS MVS Diagnosis: Tools and Service Aids publication.
  
  In addition, new DIAGxx TRAPS NAME(IARRUCSAFLT) can
  be set to issue a retry-able C0D abend whenever a
  RUCSA fault occurs.  Note: Unlike the RSM trace
  event (RUCSAFLT) that will be captured for all
  RUCSA (resolved and unresolved) faults, the
  retry-able C0D abend will only be issued when
  the faulter does not have SAF read authority
  to CLASS(FACILITY) PROFILE(IARRSM.RUCSA).  The new
  IARRUCSAFLT trap is documented in the z/OS MVS
  Initialization and Tuning Reference.
  
  The new retry-able C0D abend will have a reason
  code of 05005C00 and is documented in the z/OS
  MVS System Codes publication.
  
  The following migration actions are documented in
  either the z/OS Migration or z/OS Upgrade Workflow
  publication to assist in identifying software that
  faults on user key CSA storage when IEASYSxx
  RUCSA is defined:
  
    Request a SYSRSM component trace with OPTIONS('RUCSAFLT')
    specified to request tracing of user key CSA storage
    faults when a RUCSA is defined.  For more information on
    requesting and viewing component trace, see the
    'Component trace' section of z/OS MVS Diagnosis: Tools
    and Service Aids.  Each RUCSAFLT trace record will include
    the faulting virtual storage address (VSA) in RUCSA and
    the faulter's PSWE (16-byte PSW).  For example:
  
      SYSNAME   MNEMONIC  ENTRY ID    TIME STAMP     DESCRIPTION
      -------   --------  --------  ---------------  -----------
      S7A0      RUCSAFLT  0000001B  20:21:24.568179  RUCSA Fault
  
        FUNC1... FLTAESEG          Addr Space Seg Faults
        JOBN1... RSJRUE9B ASID1... 0022     PLOCKS.. 08004000
        JOBN2... RSJRUE9B ASID2... 0022     RLOCKS.. 08004000
        KEY..... 0036     ADDR.... 02782808 ALET.... 00000000
        0500
        KEY..... 002F     ADDR.... 09F00801 ALET.... 00000000
        KEY..... 0086     ADDR.... 0276A390 ALET.... 00000000
        07047001 80000000 00000000 091D577A
  
    In the above example, key 002F contains the faulting
    VSA in RUCSA and key 0086 contains the faulter's PSWE.
    The last half of the faulter's PSWE can be used to
    identify the software that faulted on user key CSA
    storage when a RUCSA is defined.
  
    There may be cases when the above RUCSAFLT trace
    record may not be enough to identify the faulting
    software.  For example, when the software is no
    longer loaded in the address identified by key 0086.
    For those cases, you can perform the following steps:
  
    - Run with TRAPS NAME(IARRUCSAFLT) specified on
      an active DIAGxx parmlib member.  Any software
      attempting to fault on user key CSA storage
      when a RUCSA is defined and does not have SAF READ
      authority to CLASS(FACILITY) PROFILE(IARRSM.RUCSA)
      will result in a C0D-05005C00 abend.  For more
      information on the IARRSM.RUCSA profile, see the
      documentation updates for APAR OA56180 located at
      http://publibz.boulder.ibm.com/zoslib/pdf/OA56180.pdf
  
    - Set the following example SLIP trap to produce
      an SVC dump when the C0D-05005C00 abend occurs.
        SLIP SET,ID=C0DA,C=C0D,A=SVCD,RE=05005C00,
             SDATA=(ALLNUC,LPA,LSQA,PSA,RGN,SQA,
                    ALLPSA,NUC,TRT,CSA,SUM,SWA),
             END
  
      Note: Register 2 is preloaded with the faulter's
            VSA and register 3 is preloaded with the
            faulting VSA in RUCSA prior to taking the
            COD-05005C00 abend.  Register 2 can be used
            to identify the faulting software.
  
      Consider adding the MATCHLIM parameter if you want
      the above SLIP trap to hit more than once before
      becoming disabled.
  
  Additional Search Keywords:  ZOS0204C/K ZOS0205C/K
                               ZOS0301C/K
                               ABENDC0D
                               RSN05005C00
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UJ00221 UJ00222 UJ00224 UJ00225

Modules/Macros

• IAXZIFTE IAXZITBL IGVDGNB  IGVDGNTM IAXFS    IAXMJ
  

Fix information

• Fixed component name

  RSM - REAL STOR

• Fixed component ID

  5752SC1CR

Applicable component levels

• R790 PSY UJ00225

     UP19/08/14 P F908

• R7A0 PSY UJ00224

     UP19/08/14 P F908

• R7C0 PSY UJ00222

     UP19/08/14 P F908

• R7B0 PSY UJ00221

     UP19/08/14 P F908

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.