IT13950: DESTINATION FILENAME GETS TRUNCATED ON WILDCARD COPY STEP

4.7.0.4-SterlingConnectDirectforMicrosoftWindows-x86-fp0004
4.6.0.5-SterlingConnectDirectforMicrosoftWindows-x86-fp0005-if028
4.6.0.6-SterlingConnectDirectforMicrosoftWindows-x86-fp0006
4.7.0.4-SterlingConnectDirectforMicrosoftWindows-x86-fp0004-if007
4.6.0.6-SterlingConnectDirectforMicrosoftWindows-x86-fp0006-if008
4.7.0.4-SterlingConnectDirectforMicrosoftWindows-x86-fp0004-if016
4.6.0.6-SterlingConnectDirectforMicrosoftWindows-x86-fp0006-if009
4.6.0.6-SterlingConnectDirectforMicrosoftWindows-x86-fp0006-if013
4.6.0.6-SterlingConnectDirectforMicrosoftWindows-x86-fp0006-if015
4.7.0.5-SterlingConnectDirectforMicrosoftWindows-x86-fp0005
4.6.0.6-SterlingConnectDirectforMicrosoftWindows-x86-fp0006-if018
4.7.0.4-SterlingConnectDirectforMicrosoftWindows-x86-fp0004-if023
4.7.0.5-SterlingConnectDirectforMicrosoftWindows-x86-fp0005-if006
4.7.0.5-SterlingConnectDirectforMicrosoftWindows-x86-fp0005-if013
4.7.0.5-SterlingConnectDirectforMicrosoftWindows-x86-fp0005-if016
4.7.0.5-SterlingConnectDirectforMicrosoftWindows-x86-fp0005-if025
4.7.0.6-SterlingConnectDirectforMicrosoftWindows-x86-fp0006
4.7.0.6-SterlingConnectDirectforMicrosoftWindows-x86-fp0006-if005
4.7.0.6-SterlingConnectDirectforMicrosoftWindows-x86-fp0006-if006
4.7.0.6-SterlingConnectDirectforMicrosoftWindows-x86-fp0006-if012
4.7.0.7-SterlingConnectDirectforMicrosoftWindows-x86-fp0007
4.7.0.7-SterlingConnectDirectforMicrosoftWindows-x86-fp0007-if001
4.7.0.7-SterlingConnectDirectforMicrosoftWindows-x86-fp0007-if009
4.7.0.7-SterlingConnectDirectforMicrosoftWindows-x86-fp0007-if016
4.7.0.7-SterlingConnectDirectforMicrosoftWindows-x86-fp0007-if018
4.7.0.7-SterlingConnectDirectforMicrosoftWindows-x86-fp0007-if021
4.7.0.7-SterlingConnectDirectforMicrosoftWindows-x86-fp0007-if023
Sterling Connect:Direct for Microsoft Windows 4.6.0 Fix Packs

APAR status

• Closed as program error.

Error description

• A wildcard COPY step is issued to send files matching a pattern
  from a source path to a destination path.
  For each individual file, the destination filename is build
  from the destination path plus the current filename. When this
  combined name gets too long, it will be truncated and the file
  is still send across with this incorrect filename.
  The expected behavior is that the file should fail instead.
  

Local fix

• STRRTC - 490415
  VF / VF
  Circumvention: None
  

Problem summary

• Users Affected:
  Sterling Connect:Direct for Windows 4.5.00
  Sterling Connect:Direct for Windows 4.5.01
  Sterling Connect:Direct for Windows 4.6.0
  Sterling Connect:Direct for Windows 4.7.0
  
  Problem Description:
  When the destination filename gets too long on a wildcard COPY
  step, the file will be sent with a truncated destination
  filename.
  
  Platforms Affected:
  Windows
  

Problem conclusion

• Resolution Summary:
  Enhanced error handling for wildcard COPY steps and let the
  file fail with error LSMG265E instead: File name too long or
  invalid.
  Also fixed an issue where the feedback code (FDBK) was not
  reported properly in the SCPA085I wildcard summary message.
  
  Delivered In:
  Sterling Connect:Direct for Windows 4.6.0.5_iFix026
  Sterling Connect:Direct for Windows 4.7.0.3_iFix025
  

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:

Fix information

• Fixed component name

  STR CD FOR WIND

• Fixed component ID

  5725C9908

Applicable component levels