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.
Hi ________________________________________________ Attempt to update the numeric fields on a oracle table, is always are left me to zero. On the contrary the alphanumeric fields work to me correctly.
I assume that this TABLE has one key, NUMCOMERC and the access file has WRITE=YES. When using a REPOSITION statement, you should use the name of the KEY field, not the segment name. Also, depending on your enviornment, Maintain doesn't always recognize Amper Variables.
A good simple test would be just to update the MAXOPER for the first record with a hardcoded value, like this:
MAINTAIN FILE COMIMPM
INFER COMIMPM.NUMCOMERC INTO PILA STACK CLEAR PILA REPOSITION COMIMPM.NUMCOMERC NEXT COMIMPM.NUMCOMERC INTO PILA
PILA.NOMCOMERC ='ABC'; PILA.MAXOPER= 123;
UPDATE NOMCOMERC MAXOPER FROM PILA END
And see if the first record updates. If it does, then you will have to make sure that the incoming amper variables have the values you are expecting (You can TYPE them out). If not, let me know and we can try something else.
Mark
Posts: 663 | Location: New York | Registered: May 08, 2003
The test continues updating single field NOMCOMERC, and leaving MAXOPER to zero
what follows is the view source off the original process
SET MSG=ON -SET &ECHO=ALL; SET TRACEOFF = ALL SET TRACEON = STMTRACE//CLIENT SET TRACEON = STMTRACE/2/CLIENT SET TRACEUSER = ON SET XRETRIEVAL = ON SET PAGE-NUM = OFF MAINTAIN FILE COMIMPM
INFER COMIMPM INTO PILA STACK CLEAR PILA REPOSITION COMIMPM
You are sure that PILA.NOMCOMERC is updating? If you table the file, you see the new NOMCOMERC, and MAXOPER is 0? Please make sure that the data in that field IS changing. I would say put in a COMMIT after the UPDATE statement, but that would make sense if none of the fields were updating.
Please open a case with Support. Maybe we can dial in and see the problem.
Thanks Mark
Posts: 663 | Location: New York | Registered: May 08, 2003