IBM Support

PH10458: AXMSC0034 CONNECTION TO SERVER FAILED, ALL CONNECTIONS IN USE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CICS region tried to establish an Authorized cross-memory (AXM)
    connection to the Named Counter Server but failed repeatedly
    with error message:
    .
    AXMSC0034 Connection to server DFHNC.name failed because all
     AXM connections are in use.
    .
    The maximum number of AXM connections supported within an MVS
    image, currently 4096, has been reached. There is 1 server per
    LPAR. So it appears that the various CICS regions using the
    server has exceeded the 4096 limit. Note that each TCB issuing
    a named counter server request will perform its own connection
    to the server. If the requests to the NCS are made on open TCBs
    these connections could persist for some time within each CICS
    region.
    .
    Additional Symptom Search Keyword: KIXREVxxx
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Message AXMSC0034 issued when trying    *
    *                      to connect to AXM system services.      *
    ****************************************************************
    The data servers for shared temporary storage, CFDTs
    and named counter services each use the AXM system services
    server connection component to manage connections to AXM, the
    authorised cross-memory server environment. AXM maintains a
    limit of 4096 for the size of the connection index vector.
    This is the maximum number of connections from AXM clients to
    servers per MVS image (LPAR). For shared temporary storage and
    CFDTs, CICS issues the connection from under the QR TCB, so
    this initial connection token can be shared by code running
    under QR or a subtask of QR (i.e. an OTE L8 or L9 TCB). This
    limits the number of shared TS and CFDT connections per CICS
    to one per instance of a particular shared data server. For
    named counter services however, the connection is made under
    the given TCB that is making its first API request to the
    NCS server. This is a requirement to allow batch NCS requests
    to be issued (outside of a CICS environment, where no common
    TCB is available to perform a shared connection). In the
    customer's case, many CICS systems were executing NCS commands
    from within programs executing under open TCBs. The large
    number of concurrent requests to the NCS servers meant that
    all 4096 connections became used, and when subsequent commands
    were issued they resulted in AXMSC0034 messages and the NCS
    commands failing.
    KEYWORDS: SCCSAIXN
    

Problem conclusion

  • SCCSAIXN in AXMSC has been changed to raise the connection index
    vector size to 16384.
    .
    The CICS Messages manual for CICS TS 5.4 and 5.5.will be
    updated as follows. Message AXMSC0034 will be changed to read:
    .
    AXMSC0034 Connection to server prefix.name failed
    because all AXM connections are in use.
    Explanation: The current region tried to establish an
    AXM connection to the AXM server prefix.name but the
    maximum number of AXM connections supported
    within an MVS image (currently 16384) has been
    reached.
    System action: The connection is rejected with return
    code 8, reason code 34.
    User response: If you anticipate a need for more than
    16384 AXM server connections within a single MVS
    image, you will need assistance from IBM. See the
    Approaches to problem determination in
    Troubleshooting for guidance on how to proceed.
    Module: AXMSC
    Destination: Console
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH10458

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-04-01

  • Closed date

    2020-02-19

  • Last modified date

    2020-03-02

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

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

    UI67984 UI67985

Modules/Macros

  • AXMSC
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R100 PSY UI67985

       UP20/02/20 P F002

  • R200 PSY UI67984

       UP20/02/21 P F002

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.4","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"5.4","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 March 2020