IBM Support

IT22714: PCOM: PCOMMSESSION API FAILS TO START MULTIPLE SESSIONS FROM A USER APPLICATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Personal Communications 12.0.2 on Windows 7
    Please find the steps to recreate the issue:
    a. Create  Go.Bat  in directory of your PCOMMSession.exe folder
    b. Add the following text to the batch file (simulate 4
    sessions being launched at the same time):
    Start PCOMMSession.exe
    Start PCOMMSession.exe
    Start PCOMMSession.exe
    Start PCOMMSession.exe
    Exit
    c. Run that batch file.
    You will get one connection and 3 failed connections, because
    Session A is in use.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Personal Communications users of API "pcsStartSession()" *
    * of PCSAPI interface.                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When multiple emulator sessions are started at the same time *
    * using the pcsStartSession() API, only the first session is   *
    * successfully started.                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem occurs when two different applications try to start
    sessions with the same session ID using the API
    "pcsStartSession()" simultaneously. The first application that
    calls the API will start the session. The second application
    will fail to create the session; however, it returns a success
    return code of '0'Í, which is not correct. The API should have
    returned '2' instead, indicating "PCS_USED_ID".
    

Problem conclusion

  • PCSAPI code changes have been made to ensure that the API
    returns '2'Í (PCS_USED_ID) in the above documented scenario.
    Fix is scheduled for Personal Communications 12.0.3.0 and
    13.0.1.0 Refresh Pack.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT22714

  • Reported component name

    PCOMM COMBO-ENG

  • Reported component ID

    5639I7000

  • Reported release

    C00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-10-09

  • Closed date

    2017-10-31

  • Last modified date

    2018-03-16

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

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

Modules/Macros

  • PCSAPI
    

Fix information

  • Fixed component name

    PCOMM COMBO-ENG

  • Fixed component ID

    5639I7000

Applicable component levels

  • RC00 PSY

       UP

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

Document Information

Modified date:
28 September 2021