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 am using datamigrator 7.60 and have written a stored procedure where i set the value of a field in compute i cannot reset the value of that field with another compute as it keeps the value of the first compute IE COMPUTE Dte/A20V=DATECVT(HDATE(EffDate,'YYMD'),'YYMD','A8DMYY') ; NOPRINT COMPUTE ValDte/A20V = EDIT(Dte,'99/99/9999');
Dte =01011900 ValDte = 01/01/1900
and futher on in the same print i try and use the DTE variable again
Dte =23062005 but ValDte1 = 01/01/1900 (This should = 23062005 )
Help Ps there also seems to be a limitation on the length of a line that can be used by datamigrator , that is why i have had to break the date transforms into two lines , any idea about this ?
COMPUTEs are done after all the data is processed. The COMPUTE is performed on the summarized field in the sort group. For any given sort group, the input value will always be the same. Having multiple computes in the same sort group will buy you nothing because the input data is always the same.
Can you do a DEFINE? That is a row-level computation.
And then you should also keep in mind that fieldnames in any given request should be unique. If not, you might end up with unexpected results. Like in this case, what probably happens is that the second compute for valdte will use the first computed dte field. But that is just my guess. What happens if you use really unique compute names, such as dte1/dte2 and valdte1/valdte2?
Hope this helps...
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007