IBM Support

IT44451: PCOMM BATCH FILE STOPPING AFTER HAVING STARTED 31 PRINT SESSIONS

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

  • There is an issue for running batch file in PCOMM 14.0.5 and
    14.0.6 32bit. With the configuration of Max EmulatorSession=52
    in USERPFM, when tried to run a batch file (with 52 WS file
    sessions), the program just stopped and did not open the 52
    sessions. See results below:
    
    14.0.5 - Open A-Z a-i sessions
    14.0.6 - Open A-Z a-e sessions
    

Local fix

  • Test fix was created for PCOMM 1406x64
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All IBM Personal Communications users                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When a PCOM batch file containing 52 printer session RUN     *
    * entries is launched, not all of the 52 sessions are          *
    * launching.                                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1) Launch User Preference Manager USERPM.EXE
    2) Switch to Advanced tab
    3) Set the Maximum number of emulator sessions dropdown to 52
    4) Close User Preference Manager
    5) Launch a batch file *.BCH that contains 52 session entries
    6) Less than 52 sessions are launching
    

Problem conclusion

  • USERPM.EXE and PCSBAT.EXE have been changed so the Loop
    condition break is dependent on the valid session launch count
    as set in User Preference Manager utility.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT44451

  • 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

    2023-08-30

  • Closed date

    2023-10-03

  • Last modified date

    2023-10-03

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

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

Modules/Macros

  • PCSBAT   USERPM
    

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:
04 October 2023