Add a shell-command to a job:

I tried to add a command like: "mv". As argument I entered something like: "/mydir/*.* /nextdir"!

I found that this generates an error, if I test the script with "Testscript". If I replace the wildcards with a real file name, everything works fine.

Is this a bug or a feature, that ttaad5205m000 doesn't except wildcards as arguments?

Think command or shell script without arguments only can be scheduled in the Job .

It should work if you add just a script file which contains your mv statements. (mv /mydir/* /nextdir should do, *.* should dos-isch ;-) )