FORGET WHAT I SAID. I just realized what the issue is. The 4GL code it bad. You have: LET p1 = 102 OPEN c1 USING p1 FOREACH c1 INTO rec.* # Fail: Reuses p1=101 when OPTOFC=1 ! DISPLAY "FOREACH rec: ", rec.pkey, " ", rec.name END FOREACH END MAIN But the FOREACH does its own OPEN. That is the 3rd...
Sebastien: I have to disagree, the generated ESQL/C is producing the same result but that is because the generated code is faulty. Just look at and test the version that I sent you. The generated code never fetches after the second OPEN but only after the third one. It works when you do not set...
Hi Art, Glad that you could reproduce with OPTOFC=1 !!! Since the problem exist also with ESQL/C, I believe it's rather an ESQL/C bug. We should now register a defect. Seb
Background: I needed to build a small QA test system that mimics a traditional z/OS batch application — one that opens data sets at regularly scheduled intervals, holds them open to simulate real workload activity, then closes them and waits for the next scheduled cycle. I already had a program...
Every now and then I come across something I started documenting long ago, but never got around to finishing. This is one of those documents. I decided to post it here as well, you never know, it might help someone out. How to set up the IBM ACE vault from scratch The IBM ACE vault...