Tweet
Does anyone have any info on passing parameters from OCL to CL? Any help would be much appreciated.
-
-
Passing S/36E Parameters
On Tuesday, September 01, 1998, 06:57 AM, Chris Bennett wrote: Does anyone have any info on passing parameters from OCL to CL? Any help would be much appreciated. ================================================== ============================== ================ You can use the CL CALL command in OCL. (e.g.) // LOAD XXX // FILENAME-XXX // RUN CALL PROGNAME PARM('XYZ') In fact the OCL interpreter will interpret any CL command. David Abramowitz -
Passing S/36E Parameters
Ted, Sorry it has taken me so long to get back to you. We moved our corporate offices this past weekend, and lost our ISDN line for a few days. But I'm back now! Check your email for a copy of B860601. One day, we'll all be heroes.Comment
-
Passing S/36E Parameters
Thanks, guys. My last S/36 job ended in 1988.
color="blue"> On Monday, August 31, 1998, 05:25 PM, Chris Bennett wrote: Ted, Actually David is right. Queries are stored in libraries and the default #QUERY. IDDU data definitions are stored in folders.Comment
-
Passing S/36E Parameters
Dave is, of course, correct. I will add a couple of thoughts. First, you can pass substitution expressions (e.g., ?1?, ?USER?, etc.) as parameters. Second, the called CL program can't modify them. That is, if you pass it ?1?, it won't modify parameter 1 in the OCL procedure. But embedding CL in OCL procs works fine. I have a client that still runs a primarily S/36EE system, but I do all the new stuff in native RPG III, and I have OCL call CL and RPG programs all the time.
On Tuesday, September 01, 1998, 06:57 AM, Chris Bennett wrote: Does anyone have any info on passing parameters from OCL to CL? Any help would be much appreciated.Comment
Comment