A fix is available
APAR status
Closed as program error.
Error description
When an IBM WebSphere MQ File Transfer Edition resource monitor invokes any of the four available command calls (preSourceCall, postSourceCall, preDestinationCall, and postDestinationCall) it will evaluate the ${FilePath} variable using the '/' character as the path separator. On some platforms, such as Microsoft Windows, commands may be unable to handle path separators other than the platform default and may fail.
Local fix
Since WMQFTE used Java escaped filepaths for MS Windows, you can work around this issue by tokenizing the ${FilePath} variable substitution in the command call. For example, if your ${FilePath} is substituted with C:/path/to/myfile.txt a preSourceCall argument could be: <argument>${FilePath{token=1}{separator=/}}\${FilePath{token=2}{ separator=/}}\${FilePath{token=3}{separator=/}}\${FilePath{token =4}{separator=/}}</argument> This would result in a correctly formatted filepath for MS Windows: C:\path\to\myfile.txt
Problem summary
When substituting the ${FilePath} variable, the agent would use the '/' character as the path seperator regardless of the platform's convention. In some situations this can result in errors when other applications on that system are invoked which depend on the platform default. USERS AFFECTED: All PLATFORMS AFFECTED: Windows
Problem conclusion
An agent property has been provided to allow the tuning of this behaviour. If you wish to use the platform file seperator as determined by Java instead of the '/' character set the following property in your agent.properties file: monitorFilepathPlatformSeparator=true The default value of this property is 'false'. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.4.2.
Temporary fix
Comments
APAR Information
APAR number
IC79889
Reported component name
WMQ FILE TRANSF
Reported component ID
5724R1000
Reported release
704
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-11-18
Closed date
2012-01-20
Last modified date
2012-07-20
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
WMQ FILE TRANSF
Fixed component ID
5724R1000
Applicable component levels
R704 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEP7X","label":"WebSphere MQ File Transfer Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
20 July 2012