PH20099: SSFTPEPLOY AGAINST A BUILD AND TRANSFER (NO GENERATION OF .MSL FILE) SHOWS INVALID TARGET FILE PATH FORMAT

APAR status

• Closed as program error.

Error description

• ssftpeploy using a script with only Build and Transfer Maps
  selected (Generate and Transfer Launcher Control File not
  selected) reports: Invalid target file path format, target file
  system does not support the windows path syntax: <fullpath>.msl
  

Local fix

• ITXCQ - ITX00060053
  LV / LV
  Circumvention: Ignore warning message as runmap files will be
  built and transferred.
  

Problem summary

• Users Affected:
  Users attempting to deploy a file
  
  Problem Description:
  Secure system deploy utility ssftpdeploy reports invalid error
  message for msl file generation "Invalid target file path
  format, target file system does not support the windows path
  syntax". This error is reported if deploy script setting:
  "Generate and Transfer Launcher Control File" setting is not
  selected, and the msl file path does not conform the file path
  syntax of the target system. (i.e. If the target server supports
  Unix file system, and the msl file name has Windows file path
  format, and vice versa).
  
  Platforms Affected:
  Windows
  

Problem conclusion

• The ssftpdeploy utility code is changed to account for
  deployment script setting "Generate and Transfer Launcher
  Control File", if generation of .msl files is not selected, the
  utility will not check the file path syntax of the msl files,
  and will not report invalid errors, and will not report invalid
  error on the system deployment time.
  
  Applies to:
  9.0.0.4 10.0.0.0 10.0.2.0
  
  Fixed in the next service packs and releases.
  
  To obtain the fix for this APAR:
  
  To see if the next service pack or product release is available,
  check the IBM Transformation Extender Release Notes page:
  https://www.ibm.com/support/docview.wss?uid=swg27008337
  
  If the service pack or product release is available, download it
  from Fix Central:
  http://www.ibm.com/support/fixcentral/
  
  If the service pack or product release is not available and you
  require the APAR fix immediately, request a Limited Availability
  Interim Fix (LAIF) by opening a case:
  https://www.ibm.com/mysupport/
  
  Prior to version 9.0.0, IBM Transformation Extender was called
  IBM WebSphere Transformation Extender.
  

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

  TX DESIGN STUDI

• Fixed component ID

  5724M4008

Applicable component levels