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.
I am doing a drill down report. When I drill down I am pulling back data that fits within a certain date range. However, I am having trouble handling NULL date fields. When I view the source I see the NULL field being returned as
DT( )
I tried using
SET NODATA = ' '
and then doing
CHECKEXPIRDATE = IF &PLUSCNEXTDATE EQ ' ' THEN &DATEMDYY ELSE &PLUSCNEXTDATE;
This is what is returned when I view the source
CHECKEXPIRDATE = IF DT( ) EQ ' ' THEN 05/13/2008 ELSE DT( );
I then tried the IF statement to say
CHECKEXPIRDATE = IF DT( ) EQ DT( ) THEN 05/13/2008 ELSE DT( );
The NODATA setting is for display only. It has no impact on values being tested in your (assumed) DEFINE. Also, I don't know what your &PLUSNEXTDATE variable is doing so it's hard to give an exact answer.
If MISSING=ON for that field in your Master File AND the actual field in your RDBMS can be NULL , you can test it by using 'EQ MISSING'.
If the database field cannot be null, the MFD should have MISSING=OFF (the default) or no MISSING attribute at all. The value will be blank for alpha or 0 for numeric and you can test those values.
One other tip - you will want to assign a format to your defined field like MDYY. You will frequently get erros doing this sort of calculation when the field has no assigned format.
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
Thanks for your response. I ended up resolving this issue by doing a compute in the print stmt and changing it to a MDYY. This seemed to give me the results I was looking for instead of a DT( ). Thanks for your help
Kymber, not sure what release you were experiencing this issue on, but we had a similar 'null value' issue in aix 5.3.3 - we ended up getting a 5.3.8 patch and all was resolved. As Ginny and others have aptly put it - inserting your environment/release would be time saving for all of us that are trying to assist. Glad your problem was fixed just the same.
Ira aix - wf 5.3.8 (dev) 5.3.3 (dev), windows (7.6.1-test)