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.
That has got to be one of the strangest things I've seen in a while. Definitely a bug.
This works
TABLE FILE TEST1
PRINT
COMPUTE XSTARTTIME/HHI= STARTTIME;
COUNTRY
DATETIME
BY STARTDATE NOPRINT
ON STARTDATE SUBHEAD
" "
"<STARTDATE1"
BY STARTTIME NOPRINT
END
-RUN
This is strange indeed. It only works as expected when you remove the NOPRINT from the by-field. I'd make this a case for IBI, since this can not be correct behaviour.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
There is no difference in the Master in your solution, you simply have a different way of determining the Time portion of the Date/Time column in the DEFINE statements.
I can't see anything wrong with the way I am doing it. I'm sorting on the Date/Time column that has been reformatted to display only the Hours:Minutes, the result sure looks like a bug to me.
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
DEFINE FILE TEST1
STARTDAG/YYMD = HDATE(DATETIME, 'YYMD');
STARTDATE1/wMtDYY = STARTDAG;
STARTTIME/HHI = DATETIME;
DUMMY/A1='';
END
-RUN
TABLE FILE TEST1
SUM
COUNTRY
DATETIME
BY STARTDAG NOPRINT
BY DUMMY AS ''
BY STARTTIME
ON STARTDAG SUBHEAD
" "
"<STARTDATE1"
END
I created an extra dummy field as BY field and then is works, but strange it is!!!!
Frank
prod: WF 7.6.10 platform Windows, databases: msSQL2000, msSQL2005, RMS, Oracle, Sybase,IE7 test: WF 7.6.10 on the same platform and databases,IE7
Posts: 2387 | Location: Amsterdam, the Netherlands | Registered: December 03, 2006
I think STARTDATE, STARTDATE1, STARTTIME are all the same internally which pointing to the value of DATETIME. But why NOPRINT before STARTTIME triggers this behavior?!
Developer Studio 7.6.11 AS400 - V5R4 HTML,PDF,XLS
Posts: 305 | Location: Winnipeg,MB | Registered: May 12, 2008
That is an acceptable temporary fix to the problem. I may still open a case so that someone at IBI can explain the issue, something to do with the internal matrix not doubt.
TABLE FILE TEST1
PRINT STARTTIME/HYYMDS
BY STARTTIME
END
it will be apparent that (a) the series of Defines in the original post copies the full date-and-time value from DATETIME into STARTTIME; and (b) BY STARTTIME sorts on the [invisible] date and [visible] time value in the natural manner.
The use of HHI format just hides the other components (year, month, date, second) at print time.
So WF is sorting correctly by STARTTIME -- the bug is in suppressing the repeated display of the sort field within sort break groups: WF is testing for a change in just the date components in the STARTTIME column, rather than change in the overall date-time value.
- Jack Gross WF through 8.1.05
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
We agree there's a bug: There is some set of circumstances (such as the original posted code) where WF misbehaves in handling an H-time-formatted sort field, and I characterized what it seems to do wrong, but made no assertion as to where the borderline of the bug-domain lies. -- Is it my fault when WF behaves correctly?
But there's another issue people should be aware of -- Htime formats can violate WYSIWYG expectations: If you use a HYYMDS-to-HH cast to get the Hour, and sum a statistic sorted on that HH field to obtain distribution by hour-of-day using a month's data, you'll be disappointed.
- Jack Gross WF through 8.1.05
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
I didn't redo your master file definitions, I only redid the define. I guess I should have made that clear in my previous post. I was looking for a quick solution to give you the results you wanted.
Pat WF 7.6.8, AIX, AS400, NT AS400 FOCUS, AIX FOCUS, Oracle, DB2, JDE, Lotus Notes
Posts: 755 | Location: TX | Registered: September 25, 2007