PN90438: C-FTP SERVER ERRORS DURING BLOCK MODE TRANSFERS.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When PUT/GET is done w/the C-FTP server in block mode the
  transfer fails.  Block mode transfers with attributes of
  RECFM=VBS, RECFM=VS, LRECL=X, or LRECL=nnnn can fail.  PUTs
  can fail with OPEN error 550, or VMCF error as follows:
    EZA1678I Abnormal condition during inter-addr communication
    (VMCF Rc=0 User=TCPIP)(8521)
  The C-FTP server trace may reflect the following:
    RS2655 write_block: entered
    RS2843 write_block: bad block at 034E8C25
    RS2845 write_block: last recv- 00004933 bytes at 034E8000
    MV0496 seq_close_file: file closed
    MV1249 seq_release_file: release dsname - xxxxxx.xxx.xxx
    RS2395 store_data: receive error (-1001)
   Error message 1001 indicates:
   'Block descriptor has none of the defined indicators.'
  GETs and PUTs can truncate or loss data when long records
  must be segmented.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: FTP users of the C server who transfer data  *
  *                 in block mode (mode b) that has records that *
  *                 are larger than 64K in length. This is the   *
  *                 normal case for users who process data sets  *
  *                 with lrecl=X.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: The external symptoms are truncated or  *
  *                      lost data on PUTs and GETs that fail    *
  *                      and may possibly hang the FTP session.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The C server does not recognize a block header that does not
  have the end of record (EOR) or end of file (EOF) indicator set.
  
  Additional Keywords: FTP116 PN84587
  

Problem conclusion

• Processing has been added to handle records larger that 64K that
  do not have either the EOR or EOF indicators set.
  
  The fix does not support the checkpoint/restart feature for
  variable spanning format data sets where the lrecl is larger
  than the blocksize. It also pre-reqs the LE runtime PTF that
  removes the restriction that the user specify SITE BUFNO=1
  before issuing a file transfer command for a data set with
  LRECL=X.
  
  Depending on the runtime being used with TCP/IP, this PTF has a
  dependency on LE/370 APAR PN86790, or it's equivalent C/370 APAR
  PN90167, that removes the restriction that the user specify SITE
  BUFNO=1 before issuing a file transfer command for a data set
  with LRECL=X.
  
  The TCP/IP for MVS Version 3 Release 2 User's Guide
  (SC31-7136-02) should have the following note added to the
  CHKPTint parameter of the LOCSITE command on page 133:
  
    The Checkpoint/Restart feature for variable spanning format
    data sets where the LRECL is larger than the blocksize is not
    supported.
  
  The same note should be added to the Usage Notes section of the
  RESTART Subcommand on page 163 of the same manual.
  
  Replace the following sections in the Site Command to read:
  
  LRecl
    Used to specify the logical record length of a newly allocated
    data set.
  
    Specify LRECL with no value when you are also specifying
    DATACLASS=data_class and you want the SMS dataclass to provide
    the LRECL value, or when you are specifying
    DCBDSN=data_set_name and you want to use the LRECL from the
    dcbdsn data set.  If LRECL=length is specified with either
    DATACLASS or DCBDSN, the length specified by the LOCSITE LRECL
    parameter will override the DATACLASS or DCBDSN LRECL.
  
  length
    Specifies the logical record length of a newly allocated data
    set.  The valid range is 0 through 32760 or X.
  
    Specifying LRecl=0 has the same effect as specifying LRecl
    with no parameters.
  
    Specifying LRecl=X allows the server the ability to create
    records in excess of 32760 bytes long.
  
    When using LRecl=X (with a transfer mode of BLOCK mode and a
    data type of EBCDIC) the following restrictions are in effect:
  
        The output dataset can not be an "ASA" (VBSA or VSA)
        dataset with ASAtrans specified.
  
        The datasets may not be members of Partitioned datasets
  
        Can not append to a dataset.
  
        Storing data on tape is not supported.
  
        Checkpoint/Restart is not supported.
  
        Specifying RETPD=nnn will cause the server to prompt the
        operator for permission to write the dataset.
  
        Using WRAPWRECORD is not applicable when LRECL=X is
        specified.
  
  
  * Cross Reference between External and Internal Names
  

Temporary fix

Comments

• ×**** PE97/08/13 FIX IN ERROR. SEE APAR PQ07423  FOR DESCRIPTION
  

APAR Information

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

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

  PQ05236 UQ06472

Modules/Macros

• EZAFTSME EZAFTSMV EZAFTSRI EZAFTSRR EZAFTSRS
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R320 PSY UQ06472

     UP97/07/14 P F707

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.