We currently have a job set up which has static names for the hold files. The problem we have is that if someone submits the same report twice with different paramenters at approximately the same time they interefere with each other since they ran from the same session. I was wondering what some of you may have done to insure that the hold file names are unique for this sort of situation. Is there a taskid, or execution id or something that would be unique to a particular run of a report?

This message has been edited. Last edited by: DW Marker,

If you search the forum, there are many posts covering this topic.

You haven't given a lot of information about how you are creating your hold files, but if they're just being created in temporary space, (which is the default),they should not interfere with each other. One job/agent cannot use the temp space of another job/agent while it is still processing, and the temp files are removed after the job completes so subsequent requests won't re-use them.

If you're specifically holding the files to a shared location outside of temp space, then this problem would occur.
Some of the ideas people have used (all referenced in the forum):
appending username/runtime to the hold file name
using user profile to dynamically set up a user's workspace
Moving working files back into the default temp space

and many more -- try the Search function

Lots of posts already on this one and they generally revolve around appending date and time.

You should be able to find them using the search link top right.

T

OR

USERID.whatever.ftm in an APP folder. Just another thought...

So, if I have a MR user logged in. What happens if they run a report, while that same report is still running? Are you saying that it won't even allow that and the second one will fail? Or if they had different names would they be able to run without issue.

B

Ok.. a bit more testing got me my answer.. that it runs fine when they run diretly..so now I just have to deal with report caster which does seem to have a problem.. but with rcaster we do create a physical directory to hold files to, and we can just add the taskid into that name.. so I think I have it under control now. Tahnks!