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 always receive a different format of date fields read from db2 tables using webfocus for unix. Instead of having this format XXXX-XX-XX-XX.XX.XX.XXXXXX I get this one XXXX-XX-XX XX:XX:XX.XXXXXX. Of course I can always use the EDIT function but it would mean going thru all the affected fexes. Given that, is it possible to just make changes to the config to correct this problem? Thanks in advance.
If you don't care about the time portion, you could just alter your master fileread USAGE=YYMD, ACTUAL=DATE; This seems to work for me using Oracle as well. An alternative is the HDATE function, but you will need to add that as a DEFINE or COMPUTE. Also, I don't think you can use it in a WHERE clause. Dates need a lot of work in WF to eliminate the platform and database differences (IBI take note please!)
Posts: 44 | Location: New York City | Registered: May 23, 2004
I already have my master fileread USAGE=A26, ACTUAL=A26; since I am not going to have date manipulation functions just for viewing. How come I am still getting a different format? It's already alphanumeric.
Based on the messages, I'm assuming that the date-time fields in question are described as A26 USAGE and ACTUAL. This means we just take WHATEVER the engine returns and display it. No modification or formatting is done.
So, if you get two DIFFERENT results, I need to know a few details:
1. Are both UNIX and MVS accessing the SAME engine? There may be engine sets which control HOW a date-time value is returned.
2. HOW are the engines being accessed? If one is direct, versus ODBC, then the ODBC driver may be controlling the format, to make it ODBC compliant.
3. If you issue SQL to display a date-time field, in WHAT format does it get returned. That SHOULD be how we display it.
Posts: 25 | Location: 2 Penn Plaza 28 fl | Registered: March 27, 2003
Read-Only Topic
