IV31159: cicsas crashes with signal 11 while cancelling and Asynchronous request

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

  • Closed as program error.

Error description

  • A cicsas receives a signal 11 and hangs. Further processing of
    region is halted. CICS may abend with a U5655 after a signal
    11.
    The condition is triggered by the use of the EXEC CICS CANCEL
    call for the transaction.
    

Local fix

Problem summary

  • When an CICS application uses EXEC CICS START API with REQID and
    PROTECT options, as well as EXEC CICS CANCEL API with same
    REQID, sometimes a signal 11 is observed in the cicsas.
    
    Message in console will look similar to-
    
    26590/0001 CICS Signal Handler entered with signal: 11
    26590/0001 Traceback file
    /var/cics_regions/testregion/dumps/dir1/cicsas26590.traceback
    for transaction 'TEST' is generated.
    ERZ014022I/0075 10/30/12 10:50:12.356137742 testregion
    26590/0001      : Exception 'exc_e_illaddr' caught during
    termination of transaction 'TEST' at '????'.
    
    The traceback file generated for the cicas, will look similar
    to-
    
    0xd03c8260  waitpid(??, ??, ??) + 0x170
    0xd04679c8  system(??) + 0x1e8
    0xd3d224c4  SupOS_StackWalk(??, ??, ??, ??, ??, ??) + 0x178
    0xd3d328bc  SupOS_TurnSignalToException(??, ??, ??) + 0x6e0
    <signal>
    0xd3e578fc  ConTI_ExtractICE(??) + 0x208
    0xd3e59004  ConTI_DeleteICE(??) + 0x340
    0xd3fbdd30  ConTI_CommitRetCan(??, ??) + 0x1f8
    0xd3e533d0  TasLU_InternalAfterResolution(??, ??) + 0x524
    0xd3e5396c  TasLU_AfterResolution(??, ??) + 0x3f4
    0xd1eb3ee4  event_AfterResolutionWork(??) + 0x174
    0xd1eb3c78  LoggedLocalCommit(??) + 0x2a0
    0xd1eb4ec8  event_DeliverLocalCommit(??) + 0x690
    0xd1ec2f4c  PrepareCompleted(??) + 0x378
    
    The above mentioned cicsas which recieved SEGV could lead to-
       1) The cicsas which received the signal will be hung,
    eventually leading to a hung region.
       2) The region crashes with U5655 abend.
    
    This is caused due to synchronization issue between the cicsas
    issuing the START and the cicsas performing the CANCEl
    operation.
    

Problem conclusion

  • The problem has been fixed, and an Interim fix was provided to
    the customer. The fix will be included in all future releases of
    TXSeries and FixPacks.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV31159

  • Reported component name

    CICS S/C AIX

  • Reported component ID

    5724A5620

  • Reported release

    510

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-30

  • Closed date

    2012-12-31

  • Last modified date

    2012-12-31

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

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

    IV36442 IV36443

Fix information

  • Fixed component name

    CICS S/C AIX

  • Fixed component ID

    5724A5620

Applicable component levels

  • R500 PSY

       UP

  • R510 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

TXSeries
CICS

Software version:

5.1

Reference #:

IV31159

Modified date:

2012-12-31

Translate my page

Machine Translation

Content navigation