FTP PUT/GET Processing Fails When File is on SFS - ESM Protected

 
 APAR Identifier ...... PQ24662      Last Changed ........ 00/04/17
 FTP PUT/GET PROCESSING FAILS WHEN FILE IS ON SFS - ESM PROTECTED
 
 Symptom ...... IN INCORROUT         Status ........... CLOSED  PER
 Severity ................... 3      Date Closed ......... 99/04/19
 Component .......... 5735FAL00      Duplicate of ........
 Reported Release ......... 240      Fixed Release ............ 999
 Component Name TCP/IP V2 FOR V      Special Notice
 Current Target Date ..              Flags
 SCP ...................
 Platform ............
 
 Status Detail: SHIPMENT - Packaged solution is available for
                           shipment.
 
 PE PTF List:
 
 PTF List:
 Release 230   : UQ29245 available 99/04/20 (1000 )
 Release 240   : UQ29246 available 99/04/20 (0001 )
 Release 310   : UQ29247 available 99/04/20 (9903 )
 
 Parent APAR:
 Child APAR list:
 
 ERROR DESCRIPTION:
 The user did a PUT from VM of a file located on an SFS directory
 and the file arrived corrupted. The problem appeared to be ESM
 related because if the SFS directory did not have ESM on, the
 problem did not occur. Tracing the problem showed that an
 FST Lookup call in FTSREAD received a error return code.  The
 return code was ignored, and the data area that was assumed to
 be filled in was used to obtain various file attributes.  These
 erroneous file attributes led to the file being incorrectly
 transferred.
 
 LOCAL FIX:
 
 PROBLEM SUMMARY:
 ****************************************************************
 * USERS AFFECTED: Users of the VM TCP/IP FTP client            *
 ****************************************************************
 * PROBLEM DESCRIPTION: Error transferring SFS file when SFS    *
 *                      CRR server is not running.              *
 ****************************************************************
 * RECOMMENDATION: APPLY PTF                                    *
 ****************************************************************
 The  user did  a  PUT from  VM  of  a file  located  on an  SFS
 directory and the file  arrived corrupted. The problem appeared
 to be  ESM related because if  the SFS directory does  not have
 ESM on, the problem does  not occur. Tracing the problem showed
 that  an FST  Lookup call  in FTSREAD  received an error return
 code. The return  code was ignored, and the data  area that was
 assumed  to  be filled  in  was  used  to obtain  various  file
 attributes.  These erroneous  file attributes  led to  the file
 being incorrectly transferred.
 
 FST  lookup routine  DMSLFP  was giving FTP a  RC  1 on  return
 because  its call  to DMS2SC  was getting  a RC  8. DMS2SC  was
 informing the  SyncPoint Manager that  a commit was  done. That
 call produced an error because  the CRR server was not running.
 Although the  configuration was invalid  and the bad  RC should
 not have been reflected back to  the FST  Lookup caller,  since
 it can happen,  the situation must be  accounted for in the FTP
 client.
 
 PROBLEM CONCLUSION:
 FTSREAD was modified to examine the return code from FST Lookup
 and exit in an error mode if it is non-zero.  The routines that
 call FTSREAD have been modified to identify  this situation and
 issue a message  indicating that the transfer was aborted since
 we could not access the file attributes that we need to be able
 to transfer the file.
 
 A new FTP client message will be included in any future updates
 to the following publication:
 
  GC24-5850-00 -- TCP/IP Function Level 310 Messages and Codes
 
 Cannot read file, file attributes not available
 
 Explanation:  While attempting to transfer a file, the file
 attributes are obtained via an internal CMS system call.  This
 system call failed, so we were unable to transfer the file.
 One situation that causes this problem is when the file is in
 an SFS file pool, the file is ESM protected, and the SFS CRR
 server is not running.  A possibility in the case of minidisk
 files is that the minidisk is corrupted.
 
 User or Operator Response:  Contact your system programmer
 or support desk.  You may be able to get around the problem
 if the file is in an SFS filepool by copying the file to a
 minidisk and transferring the file from the minidisk.
 
 System Programmer Response:  Investigate the characteristics
 of the file to determine why the file attributes may not be
 available to the user attempting the file transfer.
 
 System Action:  Error messages are issued and the transfer is
 aborted.
 
 TEMPORARY FIX:
 
 COMMENTS:
 
 MODULES/MACROS:   FTP      FTPROCS  FTSREAD  MSFTPC   SRVRFTP
 
 SRLS:      GC24585000
 
 RTN CODES:
 
 CIRCUMVENTION:
 
 MESSAGE TO SUBMITTER: