As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
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
Regards,
Darin
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
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.
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!