Hi everybody,

today I found a very strange behaviour of WF concerning Where-based joins + Web Services. Actually, they do not get along very well - even if they are completely unrelated.

In my case, I was doing some hold-file stuff using a Where-Based join on some FOCUS holds + a Web Service call afterwards. For me (7.7.03 HF6) this does not work. The WS call fails and I am getting an error message:
(FOC42202) XML INTERFACE UNABLE TO FIND DDNAME/FILEDEF : @0000041

If I add a

JOIN CLEAR *

before the WS call, everything runs fine - eventhough the Join is completely unrelated to the WS call.

The call works if I am doing a Standard-Join instead of a Where-based Join (in my special case where is necessary though).

I could reproduce this problem also just using a Where-join on two TABLE FILE CAR - foc. holds + a different Web Service - so I guess it is generally not working on 7.7.03.

 TABLE FILE CAR
BY CAR
BY MODEL
ON TABLE HOLD AS H_TMP1 FORMAT FOCUS INDEX CAR
END
-RUN

TABLE FILE CAR
SUM
  FST.COUNTRY
BY CAR
WHERE CAR GE 'B';
ON TABLE HOLD AS H_TMP2 FORMAT FOCUS INDEX CAR
END
-RUN

JOIN CLEAR *
JOIN
 LEFT_OUTER
 FILE H_TMP1 AT CAR TO ALL
 FILE H_TMP2 AT CAR TAG J0 AS J0
 WHERE CAR EQ J0.CAR;
END

-*JOIN
-*  LEFT_OUTER
-*   CAR IN H_TMP1 TO ALL
-*   CAR IN H_TMP2 TAG J0 AS J0
-*END

TABLE FILE H_TMP1
PRINT *
BY CAR
BY J0.CAR
PRINT 
END


-*JOIN CLEAR *

-* call a Web Service here - with or w/o JOIN CLEAR - for me w/o did not work

If you have the time & motivation + a Web Service ready for easy checking - you could try this one on different WF versions (esp. 8.x would be interesting.)

Please keep in mind: as it is very often the case with WF: the error message FOC42202 does not say at all what went wrong.

I will also open a Case with IBI but regarding my past experiences I am not too optimistic - at least there is an easy work-around

Cheers Linne

This message has been edited. Last edited by: linnex,

Hi linnex,

Thank you for opening a case for this issue. Per the current comments, we have reproduced this in release 7.7.03, but it doesn't occur in release 8.0.05. Please keep us posted as to the outcome of your case.

Thanks and regards,

Kathryn

Hi Kathryn,

IBI Support has given me the same results on the case as you mentioned:
* reproducible in 7.7.03
* not occuring in 8.x+

As with JOIN CLEAR * there is a workaround possible, I believe IBI is probably not going to fix this back in the 7.7 line. The case was closed now as I had no further questions.
I merely wanted to inform about this behaviour in 7.7. as it is not easy to trace when it happens (error message is misleading)

Cheers
Linne