Focal Point Banner


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.



Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED] FOC153
 Login/Join
 
User
Member
posted
I've found limited information on the FOC153 verb maximum limitation and understand how/why the error is occurring, but not much in the way of a workaround. Given the procedure definition below, is there a way to consolidate the 15 OVER verb objects into a single VERB object by dynamically setting a DEFINE with each of the CAR attributes and then performing a single OVER verb on that DEFINE field?


TABLE FILE CAR
SUM CAR.CARREC.MODEL
OVER CAR.BODY.BODYTYPE
OVER CAR.BODY.SEATS
OVER CAR.BODY.DEALER_COST
OVER CAR.BODY.RETAIL_COST
OVER CAR.BODY.SALES
OVER CAR.SPECS.LENGTH
OVER CAR.SPECS.WIDTH
OVER CAR.SPECS.HEIGHT
OVER CAR.SPECS.WEIGHT
OVER CAR.SPECS.WHEELBASE
OVER CAR.SPECS.FUEL_CAP
OVER CAR.SPECS.RPM
OVER CAR.SPECS.MPG
OVER CAR.SPECS.ACCEL
OVER CAR.SPECS.BHP
ACROSS CAR.ORIGIN.COUNTRY
ACROSS CAR.COMP.CAR
ON TABLE PCHOLD FORMAT HTML

I found a 'MacGyver' technique ( https://techsupport.informatio...ver/cof_tcn_m07.html ), but am not following where 'counter' is coming from.

Thanks for any help.

This message has been edited. Last edited by: User,


8002
 
Posts: 4 | Registered: November 25, 2013Report This Post
Dan Satchell
Virtuoso
posted Hide Post
COUNTER comes from table FSEQ in the JOIN, which is an IBI sample file that I believe can be generated during the WebFOCUS install process. You can always create your own version. Here is the master description.

FILE=FSEQ, SUFFIX=FOC, $
SEGNAME=SEG1
 FIELD=BLANK , , A1, INDEX=I, $
SEGNAME=SEG2, SEGTYPE=S1, PARENT=SEG1
 FIELD=COUNTER, ORDER, I4, $


WebFOCUS 7.7.05
 
Posts: 1213 | Location: Seattle, Washington - USA | Registered: October 22, 2007Report This Post
User
Member
posted Hide Post
Dan, thanks for the help.


8002
 
Posts: 4 | Registered: November 25, 2013Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic


Copyright © 1996-2020 Information Builders