IBM Support

IT19373: PCOM: JAPANESE DBCS LETTERS ARE INCORRECT AFTER 6.0.17 REFRESH

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer reported that all DBCS letters are garbage after 3270
    file transfer on Pcomm 6.0.17 and Pcomm 6.0.18.
    
    HCP : 939 or 1399
    File transfer CP : 1041
    File transfer option : JISCII CRLF
    
    We found that the issue began to occur from Pcomm 6.0.17 and
    does not occur on Pcomm 6.0.16. If apply pcsxlt.dll of Pcomm
    6.0.16 on Pcomm 6.0.17, the issue was gone.
    
    It occurs both upload and download.
    
    Customer also reported that STRPCCMD with DBCS letters in the
    command string fail.
    
    Test1sd
    STRPCO
    MONMSG     MSGID(IWS4010)
    STRPCCMD   PCCMD('NOTEPAD C:\TEST.TXT') PAUSE(*YES)
    ->Succeeded
    
    Test2
    STRPCO
    MONMSG     MSGID(IWS4010)
    STRPCCMD   PCCMD('NOTEPAD C:\"dbcs".TXT') PAUSE(*YES)
    ->failed
    
    Previously using dbcs characters did not fail.
    This phenomenon occurs in the following version.
    6.0.17
    6.0.18
    12.0.1
    

Local fix

  • Use PCSXLT.DLL from 6.0.16 level.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All IBM Personal communication users with DBCS characters    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * STRPCCMD command which has DBCS characters fails to execute. *
    * Also, file transfer using APVUFILE utility contains garbage  *
    * data for all DBCS characters.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Scenario 1:
    In local machine create a file C:\<DBCS_char>.TXT
    Using PCOMM, Login to HOST which has STRPCCMD configured.
    Perform STRPCO
    STRPCCMD  PCCMD('NOTEPAD C:\<DBCS_char>.TXT') PAUSE(*YES)
    We get warning message asking to create new file,<DBCS_char>
    .TXT' where as it already exists under C: drive and thus it
    fails to open the existing file when file name/path have DBCS
    characters in it.
    Scenario 2:
    IBM Personal Communications users downloading a file from the
    Japanese host using APVUFILE transfer facility see that the
    received file contains garbage data for all DBCS characters.
    

Problem conclusion

  • PCSXLT.DLL code changes have been made to handle the DBCS
    characters used to Execute STRPCCMD and while downloading a host
    file having DBCS characters using APVUFILE.
    
    Fix scheduled for PCOM 6.0.19 and 12.0.2 Refresh Pack
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT19373

  • Reported component name

    PCOMM COMBO-ENG

  • Reported component ID

    5639I7000

  • Reported release

    601

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-22

  • Closed date

    2017-03-24

  • Last modified date

    2017-03-24

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

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

Modules/Macros

  • PCSXLT
    

Fix information

  • Fixed component name

    PCOMM COMBO-ENG

  • Fixed component ID

    5639I7000

Applicable component levels

  • R60G PSN

       UP

  • RC00 PSN

       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":"6.0.1"}]

Document Information

Modified date:
26 September 2021