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 reading a dataset that is created and being update by a SAS program. Unfortunately the Date is stored as SAS Date format and it's not possible to change the source format as lot of other SAS programs are reading this data. As a Webfocus fan I am trying to create some reports in WF. Is there a way to convert the SAS date in Webfocus?
Example of the data I am getting...
SASDATE 17,695.00 17,696.00 17,695.00 17,696.00This message has been edited. Last edited by: CRICKETMIND,
-SET &BASE_DATE = '19600101';
DEFINE FILE CAR
BASE_DT/YYMD WITH COUNTRY = '&BASE_DATE.EVAL';
CUR_DATE/YYMD WITH COUNTRY = DATEADD(BASE_DT,'D',17695);
END
TABLE FILE CAR
SUM
DEALER_COST
RETAIL_COST
FST.CUR_DATE
BY COUNTRY
BY CAR
END
-EXIT
You could also use just a single function to calculate the SAS date, by using the fact that the SAS base date difference to the WF base date is 21550 days.
However, using either method, I would suggest that you trap the SQL created to ensure that the method that you use can be passed through the adapter - especially if you have large amounts of data!