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.
Here's a new one, at least for me: I have a field in the source file (1010data) which has a value of "09/03/13_21:30:00" which displays as "09/03/13_21:29:59" in my WebFOCUS report. It's in the synonym as "FIELDNAME=STARTTIME, ALIAS=STARTTIME, USAGE=HYYMDS, ACTUAL=HYYMDS, MISSING=ON, $".
What I want is for it to display as "09/03/13 21:30:00" or "2012/09/03_21:30:00"... Not ...29:59
I appreciate your thoughts on this.
~ DougThis message has been edited. Last edited by: <Kathryn Henning>,
In FOCUS Since 1983 ~ from FOCUS to WebFOCUS. Current: WebFOCUS Administrator at FIS Worldpay | 8204, 8206
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005
ERROR AT OR NEAR LINE 10 IN PROCEDURE ADHOCRQ FOCEXEC *
(FOC36346) INCORRECT USE OF DATE-TIME FIELD OR CONSTANT
(FOC009) INCOMPLETE REQUEST STATEMENT
BYPASSING TO END OF COMMAND
When I do a
COMPUTE HYYMDa17/A17 = ADJSTARTN ;
OR
COMPUTE HYYMDa17/A17 = EDIT(ADJSTARTN) ;
This message has been edited. Last edited by: Doug,
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005
Would you see a difference if you change the definition of STARTN in your master to ACTUAL=HYYMDm, USAGE=HYYMDm so the adapter reads the value with the highest precision possible?
Being as it is right now, STARTN is only getting data down to the SECOND, and I guess that any further COMPUTE to try to get more granular information (s, m) may not work as that information is already "lost" in virtue of the source value being read as HYYMDS.
Yeah, but the issue is that it doesn't seem consistent, as to when the second is lost. It's lost on some values and not on others. It may be time for a Case
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005
I hope not and I have faith in 1010data. I did open a case with IB and we'er working on it. But, this may be a byproduct of the way that the datetime is stored in the DB. I'll keep you posted. Not sure if I should be or .
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005
Sorry for the alarmist comment - this happens when retrieving data from Oracle. Case number 92732542.
This occurs when the column is defined as a NUMBER in Oracle, without scale or precision. WebFOCUS metadata default for these columns: USAGE=D20.2, ACTUAL=D8
"It makes no sense that x.415 becomes 0.42 while x.715 becomes x.71. It's just plain inconsistent."
The rounding seemed to have changed in the data adapter. Unfortunately the database modeller was perhaps lazy when designating the size of the numeric columns.
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
Read-Only Topic
or 
.