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 have a table with only 1 field of length 300 characters. It technically consists of multiple data columns separated by a space. I am using EDIT, GETTOK functions but at some point it's breaking. Below data is an example. I need to split each record into 4 different fields.
ATLANTA 1 GEORGIA GA
CUPERTINO 2 CALIFORNIA CA
AUSTIN 333 TEXAS TX
BILLINGS 1232 MONTANA MT
Please suggest.
ThanksThis message has been edited. Last edited by: FP Mod Chuck,
ATLANTA 1 GEORGIA GA
********************
VAL 1= ATLANTA
VAL 2= 1
VAL 3= GEORGIA
VAL 4= GA
********************
CUPERTINO 2 CALIFORNIA CA
********************
VAL 1= CUPERTINO
VAL 2= 2
VAL 3= CALIFORNIA
VAL 4= CA
********************
AUSTIN 333 TEXAS TX
********************
VAL 1= AUSTIN
VAL 2= 333
VAL 3= TEXAS
VAL 4= TX
********************
BILLINGS 1232 MONTANA MT
********************
VAL 1= BILLINGS
VAL 2= 1232
VAL 3= MONTANA
VAL 4= MT
********************
I personally would try to clean this up at the data table level so you don't have the issue of trying to break it apart with WF. A space is a terrible delimiter, all it takes is one string within that field to have an inadvertent space and your logic to break it apart is hosed. Any reason why you have one delimited field rather than a table with the fields broken out into separate data columns?
JC WebFOCUS Dev Studio / App Studio 8.2.01 Windows 7
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
Originally posted by jcannavo: I personally would try to clean this up at the data table level so you don't have the issue of trying to break it apart with WF. A space is a terrible delimiter, all it takes is one string within that field to have an inadvertent space and your logic to break it apart is hosed. Any reason why you have one delimited field rather than a table with the fields broken out into separate data columns?
It's a file that is coming from mainframe. FTP to webfocus server.
!/bin/mfftp toud t 'filename' /WF/ibi/wf8/apps/baseapp/filename.txt 80 FB DIRMIXCASE
Well, it is a mainframe extract file... if you ask the jurassic park staff nicely they might tweak the JCL to make it comma-delimited, though they will lament endlessly how much it costs to store a comma. Unless it is stored that way originally, when it might be actually position-stored... but the extract should be able to handle that.
Cheers, H. WebFOCUS 8.1.05M Oracle 11g - DB2 RedHat
Posts: 115 | Location: Brighton UK | Registered: February 19, 2005
But seriously I think, if possible, somehow getting the pieces broken apart differently before getting to WF is going to minimize the pulling of your hair out.
JC WebFOCUS Dev Studio / App Studio 8.2.01 Windows 7