FTP 451 Data Transfer Aborted: CMS File Error (When PQ29794 is Applied)
APAR Identifier ...... PQ34272 Last Changed ........ 00/09/26
FTP 451 DATA TRANSFER ABORTED: CMS FILE ERROR (WHEN PQ29794 IS
APPLIED)
Symptom ...... IN INCORROUT Status ........... CLOSED PER
Severity ................... 3 Date Closed ......... 00/02/04
Component .......... 5735FAL00 Duplicate of ........
Reported Release ......... 310 Fixed Release ............ 999
Component Name TCP/IP V2 FOR V Special Notice PE
Current Target Date .. Flags
SCP ...................
Platform ............
Status Detail: SHIPMENT - Packaged solution is available for
shipment.
PE PTF List: UQ37979 UQ37981 UQ37980
PTF List:
Release 240 : UQ40561 available 00/03/21 (1000 )
Release 310 : UQ40562 available 00/03/21 (0001 )
Release 320 : UQ40563 available 00/03/21 (0001 )
Parent APAR:
Child APAR list:
ERROR DESCRIPTION:
An FTP transfer of a fixed-record format file is performed from
an MVS client to a VM host; the transferred file is to be
stored within an SFS directory on the VM host and consists of
records with a record length that exceeds 80 bytes. However,
the file transfer fails and the data connection is aborted; the
FTP client receives the following message:
451 Data transfer aborted: CMS file error
The file transfer works fine as long as the record length
attribute of the file being transferred is 80 bytes or less.
Problem occurs only when files are directed to an SFS directory
via the PUT, PUT with SUNIQUE, or APPEND FTP subcommands.
File transfers to minidisks and BFS directories not affected.
LOCAL FIX:
None.
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: All VM TCP/IP FTP Server Users *
****************************************************************
* PROBLEM DESCRIPTION: PQ29794 shipped a bad FTSVMSUB text *
* deck for each release of VM TCP/IP. *
****************************************************************
* RECOMMENDATION: APPLY PTF *
****************************************************************
PQ29794 shipped a bad fix for part FTSVMSUB for each supported
release of VM TCP/IP.
The associated PTF numbers are: UQ37979, UQ37980, UQ37981
****************************************************************
SYMPTOMS EXHIBITED BY VM FTP SERVER WITH APAR PQ29794 SERVICE
APPLIED, AND WHICH ARE ADDRESSED VIA THIS APAR:
****************************************************************
1) MVS or VM FTP client receives "451 data transfer aborted:
CMS file error" message, attempting a file transfer to an
SFS directory on a VM host. The FTP data connection is
subsequently aborted.
The problem appears ONLY if the file being transferred
has a fixed length record format whose record length exceeds
80 bytes, and ONLY when a PUT, PUT with SUNIQUE, or APPEND
FTP subcommand has been issued by the FTP client.
2) FTP PUT of same file previously created by the FTP server
on an earlier PUT to the same SFS directory, which is under
ESM (External Security Manager) control, fails. FTP client
receives the following message:
"550 Unable to store '<fn.ft>', SFS create file error"
From the FTP server trace, the server is erroneously trying
to create the same file again because the ESTATE call issued
just prior to creating the file fails with RC=28.
An investigation of the SFS server trace revealed that ESM
is denying the FTP server access to the file it had just
created on behalf of the FTP client, because the access
attempt is being done NOT on behalf of the FTP client but
RATHER on behalf of the FTP server which is not authorized
by ESM to do so.
PROBLEM CONCLUSION:
The corrected FTSVMSUB text deck, along with the rest of the
text decks originally shipped with PQ29794, are shipped with
this fix.
A re-built FTP server module is shipped as well.
***************************************************************
Here is a description of the changes included with this fix:
***************************************************************
1) The call parameter list for new function SFSCreateFile(),
added via apar PQ29794, failed to include a parameter for
the file record length. This resulted in DMSCSL routine
"DMSCRFIL" using a default record length value of 80 bytes
for fixed length records when creating the new SFS file.
The code has been modified to include the record length
specification for the new file on all calls to the new
SFSCreateFile() routine.
2) In FTSVMSUB routines SOpenUniqueFscb()and SOpenFscb(), added
a call to PushWU() just prior to, and call to PopWU() just
after, the call to ESTATE.
TEMPORARY FIX:
COMMENTS:
MODULES/MACROS: FTSVMSUB MSFTP SRVRFTP
SRLS: NONE
RTN CODES:
CIRCUMVENTION:
MESSAGE TO SUBMITTER: