PK08075: CICS TRACE ENTRY AP 0741 MAY INCORRECTLY REPORT BASESPACE / SUBSPACE INDICATOR

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When a CICS transaction produces an SVC dump, there are a number
  of places where basespace/subspace gets reported.  One of those
  is in trace entry AP 0741, as in the following example.
  .
  AP 0741  ABAB ENTRY - FUNCTION(CREATE_ABEND_RECORD)
     GENERAL_REGISTERS(2B89DF84 , 00000010)
     ACCESS_REGISTERS(2B89DFC4 , 00000010)
     FLOATING_POINT_REGISTERS(2B89E0AC , 00000008)
     PSW(079D2000AC762EBA) INTERRUPT_DATA(000000042CF00000)
     SPACE(BASESPACE)
  1-0000  00900000 000000D9 00000000 00000000
    0010  B1E60010 00000000 01000000 00000000
    0020  00000000 00000000 00000000 00000000
    0030  2B89DF84 00000010 2B89DFC4 00000010
    0040  2B89E0AC 00000008 00000000 00000000
    0050  00000000 00000000 079D2000 AC762EBA
    0060  00000004 2CF00000 00000000 00000000
    0070  00000000 00000000 00000000 00000000
    0080  00000000 00000000 00000000 00010000
  .
  In DFHSRP we set the default to BASESPACE at TACBBLD1, then do
  .
    TM     KERNEL_ERROR_SUBSPACE_FLAGS,KERNEL_ERROR_IN_SUBSPACE
  .
  in order to set it to SUBSPACE if necessary. At CICS TS 5.3,
  KERNEL_ERROR_SUBSPACE_FLAGS are at KERRD +1A4.  In the Kernel
  Error Data from the KE domain, at +1A4 we see x'40'.  The '80'
  bit is not on, so we don't get SUBSPACE in the trace entry.
  .
  In the trace entry data above, ABAB_SPACE is at +x'8D'. In the
  above sample, there is a x'01' which means BASESPACE.
  .
  KERNEL_ERROR_SUBSPACE_FLAGS need to be updated when the subspace
  indicator is sourced from the SDWA at abend time.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS Users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: CICS trace entry AP 0741 may            *
  *                      incorrectly report BASESPACE/SUBSPACE.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  After an ABEND the system recovery program DFHSRP passes the
  BASESPACE or SUBSPACE status of the task to DFHABAB which may be
  traced out on entry or exit. DFHSRP only tests flag
  KERNEL_ERROR_IN_SUBSPACE which was set off in the reported
  problem, the AP 0741 DFHABAB entry trace thus reported
  BASESPACE. However the task was running in SUBSPACE as indicated
  by flag KERNEL_ACTIVE_IN_SUBSPACE being set and so the AP 0741
  trace should have shown SUBSPACE.
  When an EXEC CICS ASSIGN ASRASPC is used to inquire on the
  status of this ABEND, BASESPACE is returned instead of SUBSPACE.
  
  Additional keywords: SDWASVLD SDWASSA 0742
  

Problem conclusion

• DFHSRP has been changed to test if either
  KERNEL_ERROR_IN_SUBSPACE or KERNEL_ACTIVE_IN_SUBSPACE is ON when
  setting the BASESPACE/SUBSPACE status to be passed to DFHABAB.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

  PK05002

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

  UK05645

Modules/Macros

•    DFHSRP
  

Fix information

• Fixed component name

  CICSTS 3.1 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R400 PSY UK05645

     UP05/07/28 P F507

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.