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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED] Modify File Question

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED] Modify File Question
 Login/Join
 
dz
Member
posted
I have the MODIFY FILE below. Recently we had a new index added (KEY4), however in one of the loading programs we don't have the data for KEY4, so the value defaults to blanks on the fixform. When running it the way it is, Focus adds KEY4 to Match as default and extra segments are produced which is not what I need. I used NEXT instead of MATCH. I worked, but I'm skeptical it works the same way. Can someone advise the best way to handle this?

MODIFY FILE FILEA
FIXFORM FROM WORKA
MATCH KEY...
.
MATCH KEY...
.
.
MATCH KEY1 KEY2 KEY3
ON MATCH CONTINUE
ON NOMATCH INCLUDE
.
.
DATA ON WORKA
END

This message has been edited. Last edited by: Kerry,
 
Posts: 27 | Registered: April 18, 2008Report This Post
Tony A
Expert
posted Hide Post
dz,

When you say added as an indexed field do you mean FIELDTYPE=I alone or do you also mean that it has been included into the SEGTYPE to give SEGTYPE=S4 and thereby make it a KEY field?

If it is only an index (FIELDTYPE=I) then it should function no different to the previous MODIFY process.

However, if you added it as a KEY then, yes, you will have so opportunities to address.

Don't mistake INDEX and KEY fields as an INDEX is not necessarily a KEY!!

From your post I guess that it has been added as a key but, do you need it as a key?

If the answer is yes, then you really need to change your pre extract to give you ALL key fields so that the modify functions properly as you will not be able to change a key field value later.

If you don't really need it as a key then take it out of the equation and use a SEGTYPE=S3 (or as per your MFD) and use your existing extract and modify.

T


In FOCUS
since 1986		WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2  
WebFOCUS App Studio 8.2.06 standalone on Windows 10 
 
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED] Modify File Question

Copyright © 1996-2020 Information Builders