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 have a big file that I am trying to retrieve records from. The problem is it is so big that it times out on when running on the client and also times out when trying to run remotely. Our Server Poeple say the only thing that can be done is to webcast it. I was thinking of dividing up the read and retreval of of the file in to multiple procedures.
Dan, By coincidence, I'm researching various methods for a colleague on this.
Based on Google searches on "processing large data files", the best recommendation is to use SYNCSORT. If you can get the data on a platform with a current SYNCSORT GUI, it will definately help.
If you have XML data, then other methods are recommended.
I hope this helps. Jim
WebFOCUS 7.6.11, WINDOWS, HTML, PDF, EXCEL
Posts: 77 | Location: Baltimore | Registered: May 31, 2006
If this is Oracle, DB2 or SQL Server I suggest you speak with your DBA about adding indices (indexes ??) on key columns such as dates, categories, etc., that you would use as filters in the retrieval.
Loss of connection timeout problem which is an IIS property can be resolved by using deferred execution under MRE or it can be scheduled using Rcaster. I've had reports that took 9hrs to run produce results this way.
Either this or make it run faster!
Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2 Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006
Remember using VSAM files as feed to GIS system and using wf to transform the data. Eventually ended up using TABLEF and SYNCSORT to retrieve the data. This was prior to wf being able to call syncsort inherently.
You could try building a secondary index in IDCAMS if there is a very selective selection criteria that is currently not indexed. The syntax is a bit cumbersome but it generally worked ok. I think there's a trace so you can see whether its doing the equivalent of a tablescan.
Other thing to check is that your joins are done with all the keys necessary and you are not generating too cartesian a product.
I'm also intrigued about how you were going to webcast a result as I've no experience of this myself.
Hope you get it resolved
John
Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2 Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006
Maybe you should also post the master file description too. It's been a while since I have built a VSAM master but I can recall many cases where a master for a VSAM file was built and was not properly described with an indexed/key field when there is one. The segtyp values for a VSAM (or IMS database for that matter) do not have the same meaning as they do for a FOCUS database. I think all segtypes had to be S0 and the segname for the top segment had to be ROOT or DUMMY depending on the data for VSAM files. The key had to be described with "alias = key" designation, as the alias name. Of course this was over 15+ years ago and the interface has most likely been improved since then. By posting the master maybe someone with more recent experience with the VSAM file interface can make suggestions.
Good luck
FOCUS 7.6 MVS PDF,HTML,EXCEL
Posts: 115 | Location: Chicago, IL | Registered: May 28, 2004