IBM Support

PM30400: ABENDS0C3 IN KO2STORB+EFA - DPSYEXC ROUTINE RETURNED OUTPUT AREAS NOT BEING RELEASED CAUSING A STORAGE CREEP.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • KO2I0170U 0195 ABEND IN MODULE KO2OCNTB PERCOLATED TO D5API
    MODULE KO2ACONB
    KO2S0550E SDMP SDUMPX Failure. RC: 00000208
    KO2S0509E SDMP LMOD: KO2OCNTB, CSECT: KO2OCNTB, OFFSET: 01CC6A
    
    DUMP TITLE=STORAGE MANAGER COMPID=5655OPE00, JOB=OMXD20A , LMOD
    =KO2OCNTB#L, OFFSET=01D4EE, OWNER=TRANSRES
    
    DUMPID=002 REQUESTED BY JOB (OMXD20A )
    DUMP TITLE=OMEGAMON II FOR DB2 DUMP: TASK=COMMCOLL,ID=V420
    ,MOD=KO2OCNTB,OFFSET=01CC6A,CODE=0195/00000000
    
    ABENDS0C3  in KO2STORB+EFA at PM12876 level.
    ABENDU0195 in KO2STORB+6C0 at PM12876 level
    
    Symptoms for KO2STORB at PM23480 level
    
    S0C3 abend
    
    DUMP TITLE=STORAGE MANAGER COMPID=5655OPE00, JOB=CANSO2,
    LMOD=KO2OCNTB#L, OFFSET=01835E, OWNER=CALLCNTL
    
    U0195 abend
    
    DUMP TITLE=OMEGAMON II FOR DB2 DUMP: TASK=COMMCOLL, ID=V420,
    MOD=KO2OCNTB, OFFSET=017AE6, CODE=0195/00000000
    
    DPSYEXC routine returned output areas not being released causing
    a storage creep.  Maximum token value exceeded.
    
    Other symptoms:
    DUMP TITLE=STORAGE MANAGER COMPID=5655OPE00, JOB=Z342D2  , LMOD
               =KO2OCNTB#L, OFFSET=01DEC6, OWNER=COLLSTAT
    VARIABLE RECORDING AREA (SDWAVRA)
    
      +000    Key: 02     Length: 0F
      +002    E2E3D6D9    C1C7C540    D4C1D5C1    C7C5D9
    |STORAGE
    MANAGER |
      +011    Key: 04     Length: 08
      +013    F1F261F3    F061F1F0
    |12/30/10
      +01B    Key: 05     Length: 08
      +01D    D7D4F2F3    F4F8F040
    |PM23480
      +025    Key: 09     Length: 04
      +027    F4F2F040                                        |420
      +02B    Key: 37     Length: 09
      +02D    C481A381    A2978183    85
    |Dataspace
      +036    Key: 39     Length: 08
      +038    F0F0F0F0    F0D2D6F2
    |00000KO2
      +040    Key: 37     Length: 04
      +042    C1A28984                                        |Asid
      +046    Key: 3A     Length: 02
      +048    0155                                            |..
      +04A    Key: 37     Length: 06
      +04C    D98581A2    9695
    |Reason
      +052    Key: 39     Length: 33
      +054    C1C4C45B    F0F0F0F0    7A40C184    8440D985
    |ADD$0000:
    Add Re|
      +064    98A485A2    A34B40D4    81A78994    A49440E3
    |quest.
    Maximum T|
      +074    96928595    40A58193    A4854085    A7838585    |oken
    value
    excee|
      +084    848584                                          |ded
      +087    Key: 37     Length: 0A
      +089    C3819393    859940D9    F1F4
    |Caller R14
      +093    Key: 38     Length: 04
      +095    A9872E38                                        |zg..
      +099    Key: 27     Length: 0B
      +09B    E3C1D440    C1848499    85A2A2                  |TAM
    Address
      +0A6    Key: 28     Length: 04
      +0A8    00170480                                        |....
      +0AC    Key: 27     Length: 0F
      +0AE    E2A39699    81878540    C1848499    85A2A2
    |Storage
    Address |
      +0BD    Key: 28     Length: 04
      +0BF    2ABD7518                                        |....
      +0C3    Key: 37     Length: 0D
      +0C5    E2A39699    81878540    D6A69585    99
    |Storage Owner
      +0D2    Key: 39     Length: 08
      +0D4    C3D6D3D3    E2E3C1E3
    |COLLSTAT
    
    PSW for the S0C3 points to offset X'F52' in O2STOR (V420210
    12/30/10
    00:37.- PM23480 DB2COM).  At this offset in KO2STORB we see:
    AL    R1,TAMREGHI        increment last token added
    CL    R1,TAMREGMX        maximum reached?
    BNH   ADD$4000           no, branch...
    DS    0H
    #S0C3 RETRY=NO,          yes, error...
          RSN='&ENAME: Add Request. Maximum Token value exceeded'
    Below is the #TAM I believe is the cause of this problem,
    preceeded by
    the #SAM:
    *---------------------------*
    
    
    * #SAM at address : 00003200*
    * in Dataspace : 00000KO2   *
    *---------------------------*
    
     #SAM: 00003200
        +0000  NAME..... #SAM          SUBP..... 00000064
    USAGE....
    00416040      INKEY.... 00000000      FTAM@.... 00008000
        +0014  LTAM@.... 00170480      1FLG..... C0
    FWRD.....
    00000000      DWRD..... 00000000  00000000
        +0028  AVAIL.... 00000000  00000000  00000000  00000000
    00000000
    00000000  00000000  00000000  00000000  00000000  00000000
        +0054            00000000  00000000  00000000  00000000
    00000000
    00000000  00000000  00000000  00000000  00000000  00000000
    *---------------------------* * #TAM at address : 00170480*
    * in Dataspace : 00000KO2   *
    *---------------------------*
    
     #TAM: 00170480
        +0000  NAME..... #TAM          NEXT..... 00000000
    SUBP.....
    00000064      ASCB@.... 00F0BE80      TCB@..... 007B99C8
        +0014  REGHI.... 00009FFF      REGMX.... 00009FFF
    EOTHI....
    00000046      EOTMX.... 000000C8      USAGE.... 001563B3
        +0028  TKSTR.... 00170500      TKEND.... 00198500
    1FLG..... 80
    FWRD..... 00000000      DWRD..... 00000000
        +003C            00000000      AVAL1.... 00000000
    AVAL2....
    00000000  00000000  00000000  00000000  00000000  00000000
        +0068            00000000  00000000  00000000  00000000
    00000000
    00000000
    Note REGHI is 9FFF and REGMX is 9FFF
    Looking at the SHDRs under this #TAM, near the end we see:
    *  Regular Index Entry : 40958     *
    
    *    SHDR at address : 2A463A00    *
    
     : 2A463A00
        +0000  ADDR..... 2A463A20      LEN...... 00000038
    SUBP..... 64
    KEY...... 70            STAT..... 00
        +000B  1FLAG.... 80            TOKEN.... 00009FFD
    REQST....
    DPSYEXC       TCB...... 007B99C8      ASCB..... 00F0BE80
        +0020   1st 16 Bytes of Data :           00000014  C4C2E2E3
    E2D6E4E3  00000258
    
    *  Regular Index Entry : 40959     *
    *    SHDR at address : 2ABC61D0    *
    
     : 2ABC61D0
        +0000  ADDR..... 2ABC61F0      LEN...... 00000204
    SUBP..... 64
    KEY...... 70            STAT..... 00
        +000B  1FLAG.... 88            TOKEN.... 00009FFE
    REQST....
    CALLCNTL      TCB...... 007B99C8      ASCB..... 00F0BE80
        +0020   1st 16 Bytes of Data :           00000000  2A5678C8
    2A885F88  A9872D02
    
    The REQSTs indicate DPSYEXC (16), O2NCTCPU (1100), O2NCNTA
    (1290),
    O2NCTRAC (1070), DPSYSUB (1540).
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component:                          *
    *                 -   The component that transfers DB2         *
    *                     monitoring data collected by the         *
    *                     OMEGAMON collector to the TEMA           *
    ****************************************************************
    * PROBLEM DESCRIPTION: STORAGE MANAGER COMPID=5655OPE00,       *
    *                      ,JOB=jjjjjjjj,LMOD=KO2OCNTB#L,          *
    *                      OFFSET=01785E, OWNER=STATCTHD           *
    *                                                              *
    *                      STORAGE MANAGER COMPID=5655OPE00,       *
    *                      ,JOB=jjjjjjjj,LMOD=KO2OCNTB#L,          *
    *                      OFFSET=01785E, OWNER=ACE2AGNT           *
    *                                                              *
    *                      STORAGE MANAGER COMPID=5655OPE00,       *
    *                      ,JOB=jjjjjjjj, LMOD=KO2OCNTB#L,         *
    *                      OFFSET=01D4EE, OWNER=TRANSRES           *
    *                                                              *
    *                      STORAGE MANAGER COMPID=5655OPE00,       *
    *                      ,JOB=jjjjjjjj, LMOD=KO2OCNTB#L,         *
    *                      OFFSET=01D4EE, OWNER=FINDXLOK           *
    *                                                              *
    *                      OMEGAMON II FOR DB2 DUMP:               *
    *                      TASK=COMMCOLL,ID=V420,MOD=KO2OCNTB,     *
    *                      OFFSET=01CC6A,CODE=0195/00000000"       *
    *                                                              *
    *                      Intermittent High CPU Symptoms in       *
    *                      background exceptions.                  *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    *                                                              *
    ****************************************************************
    PROBLEM SUMMARY:
    Residual storage (storage creep) found in several routines
    causing Storage Manager ABEND0C3's and tasks ending with
    completion code U0195.
    
    $XMWORK CSA / ECSA control blocks not being released during
    abnormal task termination.
    
    Intermittent High CPU symptoms caused by #storage requests in
    background processing.
    
    PROBLEM CONCLUSION:
    Ensure residual storage and $XMWORK is released.
    Improve return code check for #storage requests in background
    processing.
    

Problem conclusion

  • Ensure residual storage and $XMWORK is released.
    Improve return code check for #storage requests in background
    processing.
    
    KEYWORDS :  $XMWORK CSA ECSA ABEND0C3
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PM30400

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    420

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-01-12

  • Closed date

    2011-03-23

  • Last modified date

    2017-02-04

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

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

    PM35293 UK66065

Modules/Macros

  •    KO2APCBA KO2APCBS KO2APCB2 KO2CCINB KO2CNASB
    KO2CSTSB KO2CTHBA KO2CTHBS KO2CTHB2 KO2CTHSA KO2CTHSS KO2CTHS2
    KO2DDSBA KO2DDSBS KO2DDSB2 KO2HDTPB KO2HPRCB KO2HSQPB KO2HSVPB
    KO2ICOLA KO2ICOLS KO2ICOL2 KO2IINTB KO2NCSTB KO2NDRVB KO2OCINB
    KO2ODCNB KO2ODINB KO2OMSGB KO2ONTAB KO2OPCNB KO2OXTRB KO2STOBB
    KO2STORB KO2XCINB
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R420 PSY UK66065

       UP11/03/25 P F103 Ž

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"420","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"420","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 February 2017