IBM Support

IT41497: ADDING OF AUTO RECONNECT KEYWORD IN WS FILE FOR THE NEXT RELEASE VERSION OF PCOMM

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

  • To avoid multiple connect try we have a keyword (no UI option)
    to use in session file, we can set "N" as number to try this
    many time. if Backup 1 and Backup 2 hosts is not configure, it
    will stop connecting.
    
    The following WS keywords have been provided to enable an IBM
    Personal Communications emulator session to fail over from the
    Primay host to the Backup 1 and Backup 2 hosts, when
    Auto-reconnect is configured. Both keywords are part of the
    Session section, and are valid for the TN3270, TN5250, and VT
    connections.
    
    [Session]
    SwitchToNextHostOnAutoReconnect=Y
    The SwitchToNextHostOnAutoReconnect keyword is effective only
    when Auto-reconnect is enabled. The default value is N.
    
    [Session]
    AutoReconnectRetries=10
    The AutoReconnectRetries keyword is effective only when the
    SwitchToNextHostOnAutoReconnect keyword is set to Y.
    
    The default value is 0. Valid range for this keyword is 0 to 99.
    If the keyword is set to 0, it indicates that the retry attempt
    is unlimited, and fail over does not take place.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All IBM Personal Communications (PCOMM)users.                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * PCOMM failed to stop connection retries though the below     *
    * keywords are configured.                                     *
    *                                                              *
    * [Session]                                                    *
    * SwitchToNextHostOnAutoReconnect=Y                            *
    * AutoReconnectRetries=2                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    While user runs the PComm with auto-reconnect enabled,
    "AutoReconnectRetries" keyword can be used to avoid the infinite
    connection retries.
    
    Affected Module
    PCSTLNET.dll
    

Problem conclusion

  • The problem occurred as the "AutoReconnectRetries" counter is
    not reset properly.
    
    Code logic is corrected such that the application acts as per
    the document in the link given below, under the section
    "Keywords to fail over to the next configured host with Auto
    Reconnect configured".
    
    https://www.ibm.com/docs/en/personal-communications/14.0?topic=f
    iles-version-120#keywords
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT41497

  • Reported component name

    PCOMM COMBO-ENG

  • Reported component ID

    5639I7000

  • Reported release

    E00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-07-12

  • Closed date

    2023-06-21

  • Last modified date

    2023-06-21

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

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

Fix information

  • Fixed component name

    PCOMM COMBO-ENG

  • Fixed component ID

    5639I7000

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEQ5Y","label":"Personal Communications"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"E00","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
22 June 2023