I have created a new job that should trigger when files exist. I created the job both from the template and manually. In both cases, i get the same result -the job runs regardless if files exist.

I am using a wildcard for the filename: f:\edi\inbound\*.*

I think this is broken, or there's something wrong with the way i'm specifying things. Note that i do not need "\\" as the escape character has been turned off.

File mask *.* is too generic

If you run DIR *.* from the DOS prompt in an empty directory,
it will return 2 files/directories "." and "..". The same happens with the file mask that you have specified. Please use a more specific mask. In case if incoming files can have different extensions, specify several masks, for example:
f:\edi\inbound\*.txt,f:\edi\inbound\*.dat,f:\edi\inbound\*.xyz

: I have created a new job that should trigger when files exist. I created the
: job both from the template and manually. In both cases, i get the same
: result -the job runs regardless if files exist.

: I am using a wildcard for the filename: f:\edi\inbound\*.*

: I think this is broken, or there's something wrong with the way i'm
: specifying things. Note that i do not need "\\" as the escape
: character has been turned off.

: File mask *.* is too generic

: If you run DIR *.* from the DOS prompt in an empty directory,
: it will return 2 files/directories "." and "..". The same
: happens with the file mask that you have specified. Please use a more
: specific mask. In case if incoming files can have different extensions,
: specify several masks, for example:
: f:\edi\inbound\*.txt,f:\edi\inbound\*.dat,f:\edi\inbound\*.xyz

Thanks for the suggestion.

The files in question have no extension. Will "f:\edi\inbound\*." work?

I think that 24x7 should mask out the "." and ".." entries. They were once useful in DOS, but no more, and from a practical perspective, they're not real files.

-m-

No, it will not work for the same reason (both "." and ".." match this mask). Here is a workaround: create a script job that will run every 10 minutes or so and will use the Dir statement to search for files in f:\edi\inbound directory. If it finds any files, put some code to start the desired process. Note that the Dir "f:\edi\inbound\*.*" statement ignores "." and ".." and so it will produce the desired result.

I think you suggestion makes a lot of sence.

: Thanks for the suggestion.

: The files in question have no extension. Will "f:\edi\inbound\*."
: work?

: I think that 24x7 should mask out the "." and ".."
: entries. They were once useful in DOS, but no more, and from a practical
: perspective, they're not real files.

: -m-

: No, it will not work for the same reason (both "." and
: ".." match this mask). Here is a workaround: create a script job
: that will run every 10 minutes or so and will use the Dir statement to
: search for files in f:\edi\inbound directory. If it finds any files, put
: some code to start the desired process. Note that the Dir
: "f:\edi\inbound\*.*" statement ignores "." and
: ".." and so it will produce the desired result.

: I think you suggestion makes a lot of sence.

Thanks for that idea.

Please also include a global switch in the next build to Disable All Scheduling Activity. This will allow working on a script, or whatever, and not have the scheduling activity produce unwanted interruption. Without this "disable all" feature, one has to individually disable jobs, a painstaking process.

-m-