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.
JOIN
FIELD1 AND FIELD2 IN FILE1 TO ALL FIELDA AND FIELDB IN FILE2 AS J1
END
-*
SET ALL = ON
-*
TABLE FILE FILE1
PRINT
FIELD1
FIELD2
FIELDA
FIELDB
END
-*
SET ALL = OFF
-******************************************
SET ALL = ON
Will result in a record set that contains all data in file1 and any data in file2 where FIELD1 AND FIELD2 IN FILE1 equal FIELDA AND FIELDB IN FILE2.
Two things to remember:
Follow up with
SET ALL = OFF
If you want to input logic such as
WHERE FIELDA EQ ''
you must hold the initial answer set and then do a
I may be mistaken (someone please correct me if I am) but i don't think you can join from a field that is null. The attempt would eliminate the host record, which is what you are seeing.
If you think about it, you are saying get record in file B where field value in file A matches field value in file B. Well, there is no field value in A if it is null, so that would preclude any join from being performed for that record. Null is NOT a value in itself.This message has been edited. Last edited by: Darin Lee,
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, 2007
Guess the set all=pass fixed the problem. No join would not work for a null value but at least it won't eliminate the host record.
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, 2007
My question is based on previous responses to akilayko's original question re : NULL
Is this correct :
NULL and MISSING are synonymous, and mean "the absence of a value" such as JOINing fields in HOST and X-REF tables, when there is no matching record/row in the X-REF table ?
JOIN A1 IN T1 TO B1 in T2 AS J0
... some values of A1 may not have a corresponding value in B1, and so there are no values for any field in T2 ?
And so this example would not work if, say, A2, were NULL/MISSING even if B2 were also MISSING (and A1 matched B1) ?
I would have to do a couple tests to verify, but I believe that is correct. Even if both values are null, it will not work because something in file A cannot equal (JOIN TO) something in file B if the something in A is nothing. Now that made a lot of sense.
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, 2007