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.
The branch is in the header line of the source data, in reality the branch number is normally 4 digit integer. In the example I've just given Branch 1, Branch 2 etc....
Posts: 42 | Location: UK | Registered: October 23, 2005
Picky is good, apologies for not being detailed enough initially.
In theory yes, the branch will always exist in the same position even with no data, but the variable element comes if a new branch is added. We could always ask the business to ensure the 'new' branch is added at the righ-hand-most column.
But we're looking the most low-maintenance solution, changng the MFD is unaccepatble if a new branch is added.
P
Posts: 42 | Location: UK | Registered: October 23, 2005
I played around with COMT and OCCURS. Didn't work. If I used plain, old COMT and specified a field for each of the branch values, it handled the missing data properly. It did not use the headings in row 1.
Since you are on Windows, you might be able to do an ODBC-type master to a spreadsheet. However, it appears that you might have to regen the master every time you add a new branch.
One other thought comes to mind that is a very old technique and that is using MODIFY FIXFORM to decode your input file and load the data into a Focus data base that you could then report against. I don't know how big your file is but this would be fairly easy to do.
I would want to take a step back and ask if I could get the data in the format I need it. Someone has raw data that they are summarizing for you and choosing to present it in a particular format. Why couldn't they provide it as "SUM VALUE, BY Date, BY Branch"?
You can work with the data in the format they are giving it to you, but is it a good use of resources to do it that way?
ttfn, kp
Access to most releases from R52x, on multiple platforms.
Posts: 346 | Location: Melbourne Australia | Registered: April 15, 2003
OCCURS was orginally created for VSAM files and hierachial databases (IMS, IDMS). You ask if it could work in this instance, probably. However, you say that changing the MFD is unacceptable. Your answer then becomes NO because you would have to change the OCCURS ## TIMES everytime a new brach is added. I would discourage you from trying this. Maintenance on the MFD for a comma delimited file is a nightmare even without an occurs clause.
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