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.
Using Webfocus 5.3.2 self service; when a user runs a FEX to modify a focus database, and the focus database is in a directory that the user has only read access to; focus creates a new .FOC in the temp directory (edatemp) where the user has write access, and the modify updates this new database.
This seems to me like a big bug, has anyone encountered this problem? do you have a work around, like some type of & message that can be queried? Any suggestions?
I'm not using USE, the .FOC is in a directory in the path. For users with write access to the directory the modify update the .foc in the path; for users with no write access, a new .foc is creating in the temp directory.
sounds to me like its working absolutely perfectly. If by 'temp dir' you mean the agent, then at the end of the update process, query the existence of the .foc in that user's agent dir, (we don't know your platform ), if you're in win then CMD STATE agent\filename.FOC and query the &RETCODE, and branch accordingly. Get the agent name using the TEMPPATH function. If by 'temp dir' you don't mean the agent, then you know where your TEMPDIR is set..so checking the existence of the .foc will be easier. If everyone shares the same explicit TEMPDIR then you do have a problem, but its not a bug. You can reset the TEMPDIR to the users own agent, much safer, i do it all the time for my REMOTE calls, where an explicit TEMPDIR is required. If you're relying on the path to locate the file, then its working exactly as you would want it to. WYCIWYG. Otherwise you need to do what Carol has already suggested, and explictly declare a USE to point to the proper file. and if the user can't update it, then see what kind of error message you get.
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
You are correct the USE statement will fix the problem. What confused me is that when I issue a MODIFY if I have access to write to the file, it used the file in the path, but if I don't have access it creates a new one. I guess we should always use the USE command when modifing. thanks for your help A.