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.
We have a varchar field in our master that is 7000 bytes. I've been searching on variable and varchar all morning because I know I've seen posts on this issue, but I'm not finding the solution I need. The fields after the varchar field are being ignored. I regenerated the master and it's exactly the same as it was.
The fields on the database (db2) are PROCESS_DATE DATE 4 ALT_DEL_METHOD VARCHAR 7000 TOTALDESTS DECIMAL 1 ALLOCATIONMETH CHAR 1 FREQ CHAR 1
The master is being generated through the console. The ALT_DEL_METHOD is being created as TX50. I've tried changing it to a variety of things, but the webfocus code still says (FOC003) THE FIELDNAME IS NOT RECOGNIZED: ALLOCATIONMETH (I've tried all 3 fields after the varchar field and they all give the same error).
Here is the master for those fields above:
FIELD=PROCESS_DATE ,PROCESS_DATE, YYMD ,DATE ,MISSING=OFF,$ FIELD=ALT_DEL_METHOD ,ALT_DEL_METHOD, TX50 ,TX ,MISSING=ON ,$ FIELD=TOTALDESTS ,TOTALDESTS, P2 ,P8 ,MISSING=ON ,$ FIELD=ALLOCATIONMETH ,ALLOCATIONMETH, A1 ,A1 ,MISSING=ON ,$ FIELD=FREQ ,FREQ, A1 ,A1 ,MISSING=ON ,$ How do I code the ALT_DEL_METHOD so that the fields are recognized after it. I did ask if the varchar field could be moved to the end, but that was not the solution they wanted to go with.
Hi Pam, I don't have a ready solution for you but here is what i would try: 1. Take out the TX field from the master and see if you get the same error. If you do then it is not the TX field which is causing the problem. 2. I see that the TX field is 7K long. There was a time when there was a limitation of 4K. Do you have another DB2 table with a field less than 4K? What happens there?
Daniel In Focus since 1982 wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006
I tried removing the 7000 byte field from the master and I still got the error. I also moved the field to the end of the master trying it as a tx field and other formats and still got the error.
There are 3 fields after the 7000 byte field and it doesn't matter which field I try to display ... each of them will give me an error.
When you create a new field for TX50 field the alias name must be the same as the database name and the actual format must be TX. Ex: FIELDNAME=RELEASE_INFORMATION_COMMENT, ALIAS=RELEASE_INFORMATION_COMMENT, USAGE=TX50, ACTUAL=TX, MISSING=ON,$ FIELDNAME=RELEASE_INFORMATION_COMMENT2, ALIAS=RELEASE_INFORMATION_COMMENT, USAGE=A4000, ACTUAL=TX, MISSING=ON,$
This is the entire master file. As for the db2 create statement ... I have no idea. We have dbas on the db2 mainframe side that do the creation of the tables. I can ask for it, but it will probably take a couple of days to get. This table has been existing for quite a while, we're just starting to use these fields at the end of the master. ALT_DEL_METHOD is my problem field.
Ok. You say that you can display all the fields preceding ALT_DEL_METHOD. Could you create a new MASTER and its ACX using only the last 3 fields and see if that works?
sorry to waste everyone's time. It ended up this application that I'm helping out does not look at the masters on the local machine but on a server for the test environment. The master was not up to date on that server. It was the suggestion to change the master to just display the last 3 fields that found this out. Once I got the master updated on the server, all fields are now being displayed. Thanks for everyone's help.