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
Join Efficiency
 Login/Join
 
Glenda
Guru
posted
We have reached the point where just a couple of minutes or even 30 seconds will be adding up and costing us valueable production time.

My co-worker (Brian) asks the following question.

When Joining a specific subset of records from an unindexed flat file to an indexed MFCISAM file on a 1 to 1 situation - No matter which way you go, the limited number of records in the undexed flat file will limit the data from the MFCISAM file but is there a speed difference concerning which is the FROM and which is the TO?

The unindexed flat file contains close to 2,000,000 records with a recordlength of 128 chars. and the mfcisam file,...... a LOT more with a recordlength of 312 chars.

Any ideas or comments?


Glenda

In FOCUS Since 1990
Production 8.2 Windows
 
Posts: 301 | Location: Galveston, Texas | Registered: July 07, 2004Report This Post
GinnyJakes
Expert
posted Hide Post
Can you use the WHERE IN FILE syntax? You would select the keys from the non-indexed file and hold them in a SAVE file and then use that to extract from the indexed file then hold that output as FORMAT FOCUS INDEX keyfield. Then do the join.


Ginny
---------------------------------
Prod: WF 7.7.01 Dev: WF 7.6.9-11
Admin, MRE,self-service; adapters: Teradata, DB2, Oracle, SQL Server, Essbase, ESRI, FlexEnable, Google
 
Posts: 2723 | Location: Ann Arbor, MI | Registered: April 05, 2006Report This Post
Darin Lee
Virtuoso
posted Hide Post
I would definitely join from the smaller flat file to the larger mfcisam file. A lot fewer attempts to join would occur this way whereas the other way around it would try to attempt a join for many more records but would be less successful. I don't know exactly how that data source works for indices/pointers, but it may also help to have your unindexed flat file sorted in the same order as your JOIN TO field. seems like it would be more efficient.


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, 2007Report This Post
Darin Lee
Virtuoso
posted Hide Post
Seems like if there are 2M records, that would exceed the size limit invoked by using WHERE IN FILE functionality.


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, 2007Report This Post
Glenda
Guru
posted Hide Post
Thanks for the input Darin. And you are right, the size limit prohibits the use of WHERE IN FILE.


Glenda

In FOCUS Since 1990
Production 8.2 Windows
 
Posts: 301 | Location: Galveston, Texas | Registered: July 07, 2004Report This Post
Danny-SRL
Virtuoso
posted Hide Post
Glenda,

Since ISAM and C-ISAM use hash tables for their indices, I doubt whether it is advantageous to presort you 2M records.

You said that you were going to join a subset of your flat file to the CISAM file. Maybe you can extract the subset faster if you use some utility and then use the subset for your JOIN.


Daniel
In Focus since 1982
wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF

 
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006Report This Post
PBrightwell
Master
posted Hide Post
When you limit the smaller file, how many records are you extracting? Have you considered using a UNIX script to extract the data (I think it can be done with sed and awk).


Pat
WF 7.6.8, AIX, AS400, NT
AS400 FOCUS, AIX FOCUS,
Oracle, DB2, JDE, Lotus Notes
 
Posts: 755 | Location: TX | Registered: September 25, 2007Report This Post
Glenda
Guru
posted Hide Post
Hey Pat,

Funny you should ask. We have been using a lot of UNIX scripts lately. I'll have to look into the ones you mentioned.

How's everything on your end of town?


Glenda

In FOCUS Since 1990
Production 8.2 Windows
 
Posts: 301 | Location: Galveston, Texas | Registered: July 07, 2004Report This Post
PBrightwell
Master
posted Hide Post
Typical Texas - Hot and Humid


Pat
WF 7.6.8, AIX, AS400, NT
AS400 FOCUS, AIX FOCUS,
Oracle, DB2, JDE, Lotus Notes
 
Posts: 755 | Location: TX | Registered: September 25, 2007Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic


Copyright © 1996-2020 Information Builders