PM41914: ATTEMPTS TO TRANSFER A ZERO-SIZE LOAD MODULE VIA FTP FAILS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When attempting to MGET or MPUT a PDS containing load modules,
  if one of the modules has a zero length the FTP will output the
  following error:
  
  MD1254 selectListXLMT: strtol() failed on 000000 - EDC5000I
  No error occurred. (errno2=0x00000000)
  

Local fix

• Transfer the load modules one at a time, or remove the
  zero-length module prior to the MPUT or MGET.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release(s) 11, 12 and 13  *
  *                 IP: FTP                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: When customer wants to transfer load    *
  *                      modules with mget or mput subcommand    *
  *                      and there exists members with size 0 or *
  *                      undefined size, FTP fails on transfer   *
  *                      of the load module library with 'Could  *
  *                      not build a file list' error message.   *
  *                      The load module transfer processing     *
  *                      cannot continue and regular processing  *
  *                      is to be used.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When customer wants to transfer load modules with mget or mput
  subcommand, function strtol() is used to change member size
  from 'char *' to 'int'. If there exists members with size 0 or
  undefined size, the return value of strtol() is 0. In the code
  0 is regarded as a wrong return value indicating a conversion
  error.
  +-------------------------------------------------------------+
  + 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

• Code has been modified to accept a return value of 0 of strtol()
  so members with size 0 or undefined size can be transferred.
  
  The following documentation updates will be made.
  
  * FUNCTION AFFECTED: Communications Server TCP/IP (PM41914)    *
  *                     FTP                                      *
  * DESCRIPTION      : Documentation updates                     *
  * TIMING           : None                                      *
  IBM Communications Server:
  IP User's Guide and Commands
  SC318780
  
  Add new restriction to list of current restrictions documented
  in section 4.2.5 Load module transfer with FTP starting with
  paragraph:
  
  Because of the special requirements of MVS load modules,
  there are some additional restrictions:
  
  . Do not transfer nonexecutable load modules, or load modules
  of size 0 or undefined size. Unpredictable results will occur.
  
  ================================================================
  IBM Communications Server:
  IP Diagnosis Guide
  GC318782
  
  Add new item 3 to current list for load module failures in
  section 3.8.1.9.6 Data transfer problems starting with
  paragraph:
  
  If the MVS load module fails to transfer, check the following:
  
  3. If ABEND X'B3700000' occurs, this can indicate that a DASD
     storage shortage happened when FTP used IEBCOPY to copy the
     data from the original load module to a temporary data set.
     Ensure that all the members in the original load module PDS
     or library have correct size information in the directory.
     Do not transfer nonexecutable load modules, or load modules
     of size 0 or undefined size.
  
  
  * Cross Reference between External and Internal Names
  

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:

  UK71513 UK71514 UK71515

Modules/Macros

• EZAFTPMD
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R1B0 PSY UK71513

     UP11/10/06 P F110

• R1C0 PSY UK71514

     UP11/10/06 P F110

• R1D0 PSY UK71515

     UP11/10/06 P F110

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.