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 have a data source that returns the date time as a date serial number, I can substring the value returned which is a D20.2 to an A10 or D10 but I need to convert this value to some date format that WF understands. For example serial date 42611 is Aug 29, 2016.
Thanks TrudyThis message has been edited. Last edited by: Tamra,
-SET &MYDATE = 18991230 ; -SET &NEWDATE = AYMD( &MYDATE, 42611 , 'I8YYMD'); -TYPE &NEWDATE and lo and behold &NEWDATE is 20160829
figure out the base date, sometimes called epoch date, for your system. I'm in windows, I tried 19000101, which I thought was the epoch date, but that gave me august 31. so I just dropped back my base date.
you can do this in a define of course, once you nail down what your epoch date really is. UNIX's epoch date is something like 1970/1/1. I guess they figured nothing before 1970 mattered;
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
By the way, for those curious as to why the starting (epoch) date is "12/30/1899" instead of "12/31/1899"...
Lotus 123 was a popular spreadsheet way back when.
An extra day (leap day) is added to February every 4 years starting at the beginning of a new century... except... a leap year is not observed at the start of a new century if that century is not evenly divisible by the number 400.
What does that mean in simple terms? We did not have a leap year in 1700, 1800 or 1900. But we did in the year 2000, because that is evenly divisible by the number 400.
The Lotus 123 programmers used the starting year of 01/01/1900 as the number one day of their date calculations. So 12/31/1899 plus 1 day equals 01/01/1900.
But... because the Lotus 123 programmers thought the year 1900 had one extra day in February, future software programs such as Microsoft Excel -- in order to maintain compatibility with old Lotus 123 spreadsheets -- deleted this extra year 1900 day by moving the base (epoch) date back one day, from 12/31/1899 to 12/30/1899.
Apparently WebFOCUS does so as well.
App Studio WebFOCUS 8.1.05M Windows, All Outputs
Posts: 594 | Location: Michigan | Registered: September 04, 2015