Hey guys, quick question here and probably fairly easy. I haven’t had any luck looking this one up. we have some scripts that use action script along with dos commands in them and I’m not sure what is actually going on behind the scenes here. We have an issue where I am using the “wait” command followed by a long 7Zip command, which I am having no luck redirecting the output to a log file with the normal " > log.txt". When I put this in, it will not run at all, no zip action, but shows “complete”. I can get it to work by starting the line with “dos start /wait”, but I am unsure of what that does to the remainder of the script.
I’m not sure if another cmd.exe window is opened that has no knowledge of the action script or what. I have used “dos copy” many times and never even thought about this issue, just curious. It appears as if you cannot redirect the output on the “wait” command in action script, so will the “dos start /wait” command work and ensure that the actionscript below waits until the 7zip command finishes until it proceeds to the next line of code? Any help would be appreciated, thank you.
Example is below.
dos echo {now} : Finished task {parameter “taskname”} >> {parameter “command_debug_log”}
dos echo {now} : {parameter “taskname”}: Unzipping … >> {parameter “command_debug_log”}
wait {parameter “7ZipPath”}\7za.exe x -y {parameter “Client_File_Destination”}{parameter “destination_file_name2”} -o"{parameter “Unzipped_Folder_Destination”}"
// If I replace the “wait” from above with a “dos start /wait” command, will the below “dos echo” wait until the 7zip command finishes until it runs.
dos echo {now} : {parameter “taskname”}: Done. >> {parameter “command_debug_log”}
-Jesse