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.
In the first file, I first got a error message saying that &KEY1 is missing:
so, I put a:
I tried here a: -******************** -SET &KEY=' '; -*********************
Then I got:
(FOC731) THE DEFINE-BASED JOIN IS IMPROPERLY DEFINED: FILENAME=KEY1
so, I dont think I need the set key, but not surehow to fix the issue here.
-******************************
The next file result output:
0 ERROR AT OR NEAR LINE 145 IN PROCEDURE queryFOCEXEC * (FOC030) ALL VERB OBJECTS MUST BE IN THE SAME PATH AS THEIR SORT FIELDS
-***********************
The third file just took a long time to get running....I could limit that with a recordlimit
-************************
The last file I got several different error messages in the result output:
0 ERROR AT OR NEAR LINE 358 IN PROCEDURE helpFOCEXEC * (FOC731) THE DEFINE-BASED JOIN IS IMPROPERLY DEFINED: FILENAME= 125 FIELDNAME= BY_KEY 0 ERROR AT OR NEAR LINE 358 IN PROCEDURE helpFOCEXEC *(FOC731) THE DEFINE-BASED JOIN IS IMPROPERLY DEFINED: FILENAME= 125 FIELDNAME= SITE 0 ERROR AT OR NEAR LINE 388 IN PROCEDURE helpFOCEXEC *(FOC003) THE FIELDNAME IS NOT RECOGNIZED: BY_CD BYPASSING TO END OF COMMAND (FOC009) INCOMPLETE REQUEST STATEMENT -*******
(FOC205) THE DESCRIPTION CANNOT BE FOUND FOR FILE NAMED: HOLD1 BYPASSING TO END OF COMMAND (FOC205) THE DESCRIPTION CANNOT BE FOUND FOR FILE NAMED: HOLD1 BYPASSING TO END OF COMMAND -*********
0 ERROR AT OR NEAR LINE 454 IN PROCEDURE helpFOCEXEC * (FOC205) THE DESCRIPTION CANNOT BE FOUND FOR FILE NAMED: HOLD1 (FOC205) THE DESCRIPTION CANNOT BE FOUND FOR FILE NAMED: HOLD1 BYPASSING TO END OF COMMAND (FOC205) THE DESCRIPTION CANNOT BE FOUND FOR FILE NAMED: HOLD1 BYPASSING TO END OF COMMAND
? This will cause the execution to check for most syntax, DM & flow-logic errors without actually reading the files. It will however not catch errors like 'JOIN file records out of sequence', etc. that are encountered only after reading the actual data files.
Saves a lot of time if the error is towards the end of a long running fex. One would typically insert that line at the top of the pgm, but can be used anywhere you want to check for errors. Sandeep Mamidenna
------------------------------------------------------------------------------------------------- Blue Cross & Blue Shield of MS WF.76-10 on (WS2003 + WebSphere) / EDA on z/OS + DB2 + MS-SQL MRE, BID, Dev. Studio, Self-Service apps & a dash of fun !!
Posts: 218 | Location: Jackson, MS | Registered: October 31, 2006
Mayor, Step one should be always work on the first error message.
I would also suggest that you put a -RUN after each and every TABLE FILE, with a -SET &ECHO=ALL;. This will help tp pinpoint which block of code the erroris in.
Step two, understand the error message, do some searches on the error number FOCnnnnn.
For you first two errors, seems that you have coded a defined based join and it is wrong. check the syntax. You also seem to be selecting information from a multipath table or join, the fields should be in a single path to stop this.
Waz is spot on - only deal with the first error and then once that is cleared you will have better understanding of actual errors in the code and not cascaded errors.
The normal reason for the "Error in Define based Join" is missing out the WITH real_field syntax.
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, 2004
In the first file, I first got a error message saying that &KEY1 is missing:
so, I put a:
I tried here a: -******************** -SET &KEY=' ';
error points to &KEY1, you -SET &KEY without the '1'. I would try SET XRETRIEVAL=OFF as suggested by Blue Zone. I'd try a -EXIT after the first table request with a recordlimit of 1. Does it work? Make it a 100. Does it still work? Take off the recordlimit and does it still work? Ok then you now need to move to your -exit down to the next logical breakpoint etc...