IBM Support

II14486: ABEND1FC ABEND0C4 ECSA OVERLAY LSQA RB RBXSB FIELD OVERLAID WITH X'16'

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • INTRAN

Error description

  • Customer experienced overlay of X'16' ( HEX16 16 ) to the
    RBXSB field, resulting in eventual ABEND1FC in the SVC FLIH
    IEAVESVC ( aka IEAV9SVC ).  Additionally, this overlay of the
    RB often caused secondary overlays to ECSA in the address range
    of X'16Fxxxxx'.  These overlays to the RB and CSA are performed
    while running KEY0.
       In addition to the RBXSB field in the RB-X'20' being
    corrupted with a one byte overlay of X'16' to the first byte,
    there were also other fields in the RB that were damaged.  The
    SVRA or SVRB eyecatcher which should exist at RB-X'28' was
    typically damaged, as was the first byte of each of the words
    in the RB immediately following the RBXSB field.
       This problem has been seen to occur during CICS startup, as
    well as when a jobstep terminates and a new one is in the
    process of being started.  A logrec of the ABEND1FC or ABEND0C4
    shows the overlaid RB in reg2.  The ABEND0C4 logrec shows the
    corrupted RBXSB field content in register 1.
       This overlay is caused by an OEM product passing an incorrect
    RB address to a FESTAE macro.  The code that does the overlay
    only gets control under an error-relate circumstance (not
    visible in the system trace table), thus the overlay may be
    experienced infrequently.  However, due to impact, this problem
    is HIPER in nature.  The code lives within loadmod IGX00206
    which can be found in the IPCS LPAMAP output.  Presence of
    this load module in conjunction with these other symptoms
    offers further verification.
       The product causing the overlay is Smarttest by Allen Systems
    Group.  According to customer feedback, the fixing vendor PTF is
    STM 74083.
    
    Additional Symptoms:
    
    Abend602 in VTAM when ISTINCCO issues POST with an ASCB address
    that is actually a pointer to the system CVT, which was loaded
    from PSA location x'10'.  The bad address was loaded from field
    MPSASCB in a VTAM MPST, but the pointer to the MPST was zero.
    This zero address was loaded from PST field PSTMPSTP.  The PST
    at offset 8 was overlaid for 8 bytes and the second word, which
    is PSTMPSTP, was zeroes.
    
    Abend0c4 in ISTAPCPS or other abends related to an overlay of
    the PST for 8 bytes. The MPST pointer at +8 is overlaid for a
    length of 8 bytes. 61 is the VTAM PST Control block ID and +8
    should point to an MPST but is overlaid.
    
    14CB2D90   610000A0   00000000   00008CF7   00000000
    14CB2DA0.:14CB2DBF.--All bytes contain X'00'
    14CB2DC0   00000000   00000000   00C16654   00000000
    14CB2DD0   01011000   07F00030   00000000   00000000
    ..
    S1FC
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II14486

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-05-08

  • Closed date

  • Last modified date

    2009-07-09

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
09 July 2009