PI91691: ABENDATSC OR TSSHARED SUSPENDS FOR CERTAIN SHARED TS QUEUES. THIS HAPPENS FOLLOWING A PRIOR RUN OF CICS ABEND 40D OR 90D .

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A run of CICS abended End Of Memory which is Abend40D or
  Abend90D .  A dump from that abend shows that there were
  Dispatchable tasks that had been in a TSSHARED wait on a
  certain queue.
  .
  From that point on, attempts to access those Shared TS queues
  hang in a TSSHARED wait, or get ATSC when the TSSHARED suspend
  timesout. This is because there is a stranded buffer lock in
  Shared TS Server address space.  The lock became stranded
  during the Memterm ( End Of Memory abend).
  .
  Additional Symptom(s) Search Keyword(s): KIXREVDWZ
  

Local fix

• MVS Cancel , then restart , the Shared TS Server .
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: ABENDATSC (or TSSHARED suspends) for    *
  *                      certain shared TS queues, following a   *
  *                      prior run of CICS that abended 40D or   *
  *                      90D.                                    *
  ****************************************************************
  If CICS address space encounters a problem which causes an
  immediate end-of-memory (EOM), bypassing normal end-of-task
  clean-up, such as an abend during recovery with system
  completion code 40D, then the AXM end-of-task resource manager
  does not get control, and the AXM end-of-memory resource manager
  runs instead.  This marks the connection as no longer valid, but
  it does not have access to the server so it cannot purge any
  active or waiting requests.  This means that any resource owned
  by the request may be unavailable until the server is restarted.
  For shared TS, an active request usually holds a lock on the
  buffer for the required queue index entry, so any further
  requests which attempt to access that specific queue will hang
  or time out until the server has been restarted.
  KEYWORDS: ATSC end of memory memterm abend40d abend90d
  

Problem conclusion

• The AXM server disconnect processing will be driven during CICS
  client EOM processing. The master scheduler will invoke
  disconnect via an SRB, scheduled synchronously using IEAMSCHD
  SYNCH=YES. This calls a new SRB routine within AXMSC,
  passing it the address of the SCDET area being disconnected.
  The disconnect routine will then be able to run as if it were
  being called by the client region for EOT processing.
    Note - the change to AXM applies to the shared temporary
  storage data server, the named counter server and the CFDT
  shared data server.
    The following new message will be added to the CICS Messages
  and Codes (Volume 1) for CICS TS 5.2, CICS TS 5.3 and CICS TS
  5.4:
  
  AXMSC0043I Server disconnect SRB was scheduled, IEAMSCHD RC=xx
  COMP=xx CODE=xx RSN=xx
  
  Explanation
  A client region connected to a CICS cross-memory server region
  was terminated at end of memory, so the AXM interface in the
  client region was unable to complete normal server disconnect
  processing.  The AXM end of memory resource manager has
  therefore scheduled a synchronous SRB to the server region to
  notify it that the client region has now disconnected, using the
  IEAMSCHD macro.  This message indicates the result values
  returned by that macro, in hexadecimal, consisting of the return
  code, completion type, completion code and reason code as
  documented for the IEAMSCHD macro.  If the server region is
  still running and the disconnection process was successful, the
  return code is zero.  In this case, the completion type and
  completion code are also zero, and any non-zero reason code may
  be ignored. If the return code is non-zero, server disconnect
  processing could not be completed, in which case it is possible
  that some server resources being used by the disconnected client
  region may not have been released.
  
  System action
  Processing continues.
  
  User response
  If the return code is zero, no action is required.  If the
  return code is non-zero, it is possible that subsequent requests
  to the same server region may fail or hang.  If this occurs, the
  only solution is to cancel and restart the server region.
  
  Module
  AXMSC
  
  Destination
  Console
  

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:

  UI54059 UI54060 UI54061

Modules/Macros

• AXMEV    AXMSC    AXMXM    AXMXM1
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R000 PSY UI54059

     UP18/02/27 P F802

• R100 PSY UI54061

     UP18/02/28 P F802

• R900 PSY UI54060

     UP18/02/28 P F802

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.