Focal Point Banner


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.



Read-Only Read-Only Topic
Go
Search
Notify
Tools
Load MF Focus DB
 Login/Join
 
dz
Member
posted
I came across a Focus load program that loads a multi segment mainframe Focus DB. At the end of the load there is "table file" that counts all the segments in the new db. When I suggested to remove it, I was told that since this file has aditional "referrence" files it is necessry in "exclusive mode" to parse all the segments in order to populate adresses or pointers of the referrence dbs. If this is not perfromed the performance will be significantly slower. Is it true? If yes it is still valid today? Can someone explain this to me? This query is very cpu costly.
 
Posts: 27 | Registered: April 18, 2008Report This Post
GamP
Virtuoso
posted Hide Post
If the masterfile of the database contains references to segments outside of the database itself and if those references are static, then this method of tabling the file after creation or loading is indeed still valid.
A static join in the master file (segments with segtypes of Kx) will reserve a pointer in the database that will only be resolved using table.
If you do not resolve this pointer then this will be done when the record is referenced for the first time. So only the first usage will pay the performance price, after that the pointer will be used and it will be updated only if needed.
Depending on the size of the databases this can indeed be quite costly.

Hope this helps ...


GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
 
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic


Copyright © 1996-2020 Information Builders