Fixes are available
Closed as program error.
If your application has a FileSink operator with both the moveFileToDirectory and closeMode parameters, and closeMode is set to a value of ?dynamic?, it might fail with the following errors: CDISR5160E: The system failed to rename the <file name> file to be the <file name> file. The error is: No such file or directory. CDISR5179E: An error occurred when a file was moved. The error is: The system failed to rename the <file name> file to be the <file name> file. The error is: No such file or directory. This situation occurs when the operator decides it needs to close the current output file, move it to another directory, and open a new file. The errors indicate that the operator is actually trying to move the new file rather than the old file.
To work around the problem, remove the moveFileToDirectory parameter.
Users Affected: Users with applications that use the FileSink operator with moveFileToDirectory and closeMode parameters. Problem Description: See Error Description.
This problem is fixed in Version 3.0 Fix Pack 1 and later fix packs.
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels