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.
Hi everyone, Im having a weird problem with dates and we recently upgraded WF from 5.2x to 5.3x. I used to have my date field in my .mas file as YYMD and everything seemed to be fine. but the dates started to display some 1901's but when I recreate the synonym or change the usage type to HYYMDs it displays correct info.
For eg:
if myfield datatype is
YYMD then I get 1901/05/03 HHYYMDs then I get 2002/12/19 00:00:00.000
I can't figure out what is the deal with this datatype. Im still thinking its happening after the upgrade.
Please help me if u can. Thanks
Posts: 289 | Location: Houston,TX | Registered: June 11, 2004
hI, I tried to use ur suggestion, I had this line in my edasprof.prf ENGINE SQLMSS SQL SQLMSS SET CONNECTION_ATTRIBUTES(local)/webfocus,5C5B9D17AA33DBBA;GISAddr so i have added this line next to it. ENGINE SQLMSS SET DATETIME OFF (local)/webfocus,5C5B9D17AA33DBBA;GISAddr I tried restarting the engine but it dint seem to make any difference to my date display result.
Help me
Thanks and appreciate it
Posts: 289 | Location: Houston,TX | Registered: June 11, 2004
You needed the line in the edasprof file but you'll also need to make the format in your masters to YYMD usage Date, but then you'll not have access to the time portion of the date. There is a way to generate your masters without the HYYMDs but I don't recall how. I usually do a find and replace on my masters, but I don't have a ton of them either.
Just spoke to FOCUS Wizard and he is confused. In prior releases, we didn't have a DATE-TIME format. So, relational date-time fields were described as having only a DATE portion (YYMD), which we supported, and the interface returned only the date component.
With later releases, we came out with a date-time format (formats with a leading 'H', like HHYYMDs), which handled both date AND time. CREATE SYNONYM was changed, so new MFDs would use this newer format. For compatibility, we provided a SET to the interface (engine SET DATETIME OFF) to restore the old defaults.
What's confusing is that in this case, the interface is returning a DIFFERENT value for the date component, depending on the setting of DATETIME, which shouldn't happen.
Can you provide an example of a single record, and the different dates that are returned, so we can try it here?
It's like this. Date/Time as returned from most DBMSs is a TEXT (human readable) date format.
Date (FOCUS Date) is a BINARY format and is not human readable - it's an SIGNED INTEGER value that represents clock ticks from a start date set at the beginning of computerized time (which is Jan 1 1901 by the way).
So FOCUS is expecting data described as YYMD to be stored as a smart date - an INTEGER. YYMD is really a FOCUS format. It's not going to be comfy being fed a text based date from a relational RDBMS, which will be the numeric representation of an ASCII value and will be converted weirdly.
The answer if you want the date represented as a YYMD is to format it as ACTUAL of HYYMDS and USAGE of HYYMDS and create a DEFINE in the master to represent it as a smart date using the H conversion functions built into FOCUS.