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.
Getting "Task error: VALUE FOR JOIN FROM FIELD OUT OF SEQUENCE. RETRIEVAL ENDED" in reportcaster job only. When Run directly from DevStudio, no errors. What could cause this?
ReportCaster tasks stop at the first encountered error, WebFOCUS programs just continue unless you trap the error.
There is a setting to exclude certain WebFOCUS error codes from stopping the RC task:
ReportCaster Admin Console > ReportCaster Server Administration > General tab > FOC Message Numbers to Be Processed as Warnings. We have the following FOC Message Numbers coded here: 201, 36359, 757, 837, 95, 96, 1547, 1568 (the first six are the default numbers).
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
The cause of this message is of course that the sequence of the joined files is not exactly the same. At the first record in the referenced file that offends the sequence of the host file, this error is givenand processing stops. You'd best check the process steps to ensure the joined files indeed will have the same sort order for the joined fields.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
@Francis, I'll take that under advisement as I will soon be undertaking a project that will benefit from reporting/reading error levels and that info will be very useful.
@GamP, I've created a side job (so as to be able to make edit w/o messing with Production) and scheduled that through ReportCaster. I have -EXIT'd starting from the top and crawling to the bottom and have isolated the step that throws the error. It is pretty Vanilla. I have commented out the original join and used the GUI to produce it as it should look. The only thing that comes to mind is that I vaguely recall hearing that compound joined fields can give errors and that you should try to concatenate them for the join. I'm not sure if this is that error, but I am off to try that next.
quote:
DEFINE FILE CPM2 PROCTYPE/A10 = IF CABGTYPE2 GT ' ' THEN CABGTYPE2 ELSE IF CABGTYPE GT ' ' THEN CABGTYPE ELSE IF PROCTYPE1 EQ 'CABG' THEN 'CBGB' ELSE PROCTYPE1; END TABLE FILE CPM2 PRINT PROCTYPE CASS_PATSTATUS CASS_CODE CASS_ASASCOREID CASS_CODE CP_SURNUM CP_PROCCODE EMP_LASTNM EMP_FIRSTNM CP_PROCCODE PMF_DESCRP OR_ROOM TIME_CON_SDATE ST_TIME TIME_CON_EDATE SURG_END_DATE END_TIME WC SH_MEDREC PTNAME CABGTYPE -* GNODE_DESCRP BY SH_ACCOUNT BY SURG_START_DATE ON TABLE HOLD AS PROCORM2 END
quote:
TABLE FILE CRINFO PRINT SERVICEDATE INTERNALCASEID HEIGHT WEIGHT ASASTATUS ACCOUNTNUMBER CRSURG_DATE PATIENTNAME MEDICALRECORDNUMBER GENDER DOB ADMISSIONDATE DISCHARGEDATE BY ACCOUNTNUMBER BY CRSURG_DATE ON TABLE HOLD AS CRINFO2 END
quote:
-*JOIN SH_ACCOUNT AND SURG_START_DATE IN PROCORM2 TO -*ACCOUNTNUMBER AND CRSURG_DATE IN CRINFO2 -*END
JOIN CLEAR *
JOIN PROCORM2.PROCORM2.SH_ACCOUNT AND PROCORM2.PROCORM2.SURG_START_DATE IN PROCORM2 TO CRINFO2.CRINFO2.ACCOUNTNUMBER AND CRINFO2.CRINFO2.CRSURG_DATE IN CRINFO2 TAG J2 AS J2 END
Anything else I could be doing wrong? Is it the compound join? This seems very simple, not sure why it's failing.