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.
Can anyone tell me what's meant with @0000013 in below error?
quote:
(FOC236) LINKED FILE DOES NOT HAVE A MATCHING KEY FIELD OR SEGMENT: @0000013
How am I supposed to know what that refers to?This message has been edited. Last edited by: Kerry,
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
What I'm joining or what's wrong with the join, doesn't really matter to my question. I'm looking at the @000013 code that's giving me a rather unhelpful hint of where the problem is.
I think I found the issue with the joins. Apparently, even though according to the documentation XFOCUS format supports multi-column joins, it can't actually do them. I solved that by creating an artificial key from the combined fields, but I had hoped not to have to resort to kludges like that.
It would have been a major help if the error would be a little more indicative of where the problem was. I think the @000013 code is actually a relative line number counted from the first line in the first JOIN. If I go 12 (=13-1) lines down from there, I end up in the middle of above-mentioned multi-column join.
Unfortunately, with the built-in editor in combination with large amounts of joined TABLE FILEs, that does require some math to end up at the actual line number. Why do I have to do math to understand a message from a computer? It's much better at that than I am. Of course I can calculate an absolute line number based on an offset, but I shouldn't have to! It's silly.
It's a bit like you're at the cashier in a super market and she just blots out the prices of all articles and expects you to add them up yourself.
Computers are for convenience!
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :