When the app, the cfdp engine, assigned the new machine to a File which is requested,
the engine didn't initialize the "temp_file_name" in the machine(MACHINE.TRANS_STATUS.temp_file_name) in the function,
"aaa__initialize".
This caused that when the new file is assigned to a new machine, it had the obsolete temp_file_name which had been assigned to
the previous File.
This obsolete temp_file_name is shown in the Trans Diag Packet for the new file,
when received the command, CF_SEND_TRANS_DIAG_DATA_CC.
Test case : Test_CF_AppPipe_SendTransDiagCmdPbTransId
When the app, the cfdp engine, assigned the new machine to a File which is requested, the engine didn't initialize the "temp_file_name" in the machine(MACHINE.TRANS_STATUS.temp_file_name) in the function, "aaa__initialize". This caused that when the new file is assigned to a new machine, it had the obsolete temp_file_name which had been assigned to the previous File. This obsolete temp_file_name is shown in the Trans Diag Packet for the new file, when received the command, CF_SEND_TRANS_DIAG_DATA_CC.