Hello Art, I fully agree that proper FOREACH programming is to put a USING clause if there are ? parameters in the query. However, AFAIKR, in first versions of I4GL, the FOREACH instruction did not allow a USING clause, and that's why you can find sequences like: OPEN curs USING ... FOREACH curs...
IBM Bob ハンズオン完全ガイド：初級から中級まで自分のレベルに合わせて学ぼう はじめに IBM Bobは、AI駆動の開発アシスタントとして、開発プロセスを劇的に効率化するツールです。本ブログでは、 GitHubで公開されているハンズオン教材 を、 初級編 、 中級編 、**中級編（外部サービス連携）**の3つのレベルに分類し、それぞれで習得できるスキルを解説します。 🌱 初級編：IBM Bobの基礎を学ぶ 対象者と所要時間 IBM Bobを初めて使う方、プログラミング初級〜中級レベルの方 所要時間 : 45-65分...
Hello Lee , You need to run this before . https://github.com/IBM-Security/verify-access-container-deployment/blob/master/common/create-ivia-pki.sh Thanks
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...