PK35188: USING THE SBDATACONN CONFIGURATION IN CONJUCTION WITH FTP TYPE SUBCOMMAND ALIASES CAUSES UNEXPECTED RESULTS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In FTP, the single-byte SBDATACONN configuration--which can be
  set in the FTP.DATA file or via a SITE/LOCSITE command--has the
  functionality of working in conjuction with an FTP TYPE
  subcommand alias for multi-byte data (such as SJISKANJI or
  BIG5).  However, a problem exists such that using SBDATACONN and
  one of the TYPE commands results in a failed FTP transfer.
  Failure messages such as the following may be issued:
  
      EZA1490I Error writing to data set
      EZA2606W File I/O error 1015
      >>>ABOR
      426 Connection closed; transfer aborted.
      226 ABOR command successful.
      EZA1735I FTP Return Code = 16426, Error Code = 00002
  
  This problem stems from FTP incorrectly believing it has
  encountered untranslatable data.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release 4, 5, 6, 7 and 8  *
  *                 IP: FTP                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Using an SBDATACONN statement for       *
  *                      single byte translation, e.g            *
  *                      SBDATACONN=(IBM-930,IBM-932)            *
  *                      in conjunction with subcommand          *
  *                      SJISKANJI (NOTYPE) for double byte      *
  *                      translation, causes unexpected results. *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In function WrtStreamFastIO() the check for untranslatable
  characters (macro FINDUTC) is being called when the data
  transfer type is DBCS and is should not be.  FINDUTC should
  only be called for single byte data transfers.
  +-------------------------------------------------------------+
  + Please check our Communications Server for OS/390 homepages +
  + for common networking tips and fixes.  The URL for these    +
  + homepages can be found in Informational APAR II11334.       +
  +-------------------------------------------------------------+
  

Problem conclusion

• The function WrtStreamFastIO() has been corrected.
  
  * Cross Reference between External and Internal Names
  PREFTPCX (EZAFTPCX)  PREFTPLS (EZAFTPLS)
  

Temporary fix

Comments

APAR Information

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

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

  UK20596 UK20597 UK20598 UK20599 UK20600

Modules/Macros

• EZAFTPCX EZAFTPLS EZAFTPTI
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R140 PSY UK20596

     UP07/01/10 P F701

• R150 PSY UK20597

     UP07/01/10 P F701

• R160 PSY UK20598

     UP07/01/10 P F701

• R170 PSY UK20599

     UP07/01/10 P F701

• R180 PSY UK20600

     UP07/01/10 P F701

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.