Feature Request – Support for Parameter Substitution in RSEAPI_SQLRequest

Today, RSEAPI_SQLRequest appears to support only static SQL text through the sqlStatement field. What I’m requesting is the ability to use parameter markers (?) with bound parameters for OUT parameters, similar to JDBC/ODBC prepared statements.

This would enable two key scenarios:

1. IN parameter binding (avoid concatenating values into the SQL string)

2. OUT parameter retrieval (capture return codes/status values from stored procedures)

Generic Example: Calling a Stored Procedure with an OUT Return Code

Goal: Call a procedure that performs an operation (e.g., file transformation) and returns a status/return code via an OUT parameter.

SQL statement (with parameter markers):

SQLCALL MYLIB.MYPROC(?, ?, ?)

• Parameter 1: IN (VARCHAR) → input path

• Parameter 2: IN (VARCHAR) → output path

• Parameter 3: OUT (INTEGER) → return/status code

What I’d like to express via RSEAPI_SQLRequest (pseudo-structure)

(This is an illustrative example; the exact field names could vary. The intent is to show the capability needed.)

{
"sqlStatement": "CALL MYLIB.MYPROC(?, ?, ?)",
"parameters": [
{ "index": 1, "direction": "IN", "type": "VARCHAR", "value": "/tmp/input.txt" },
{ "index": 2, "direction": "IN", "type": "VARCHAR", "value": "/tmp/output.bin" },
{ "index": 3, "direction": "OUT", "type": "INTEGER" }
]
}

And then receive the OUT parameter values in the response:

{
"success": true,
"outParameters": [
{ "index": 3, "type": "INTEGER", "value": 0 }
],
"sqlDiagnostics": {
"sqlState": "00000",
"message": "Procedure completed successfully"
}
}

Why this enhancement matters

• Functional: Without OUT parameters, it’s hard (or impossible) to reliably capture procedure results (return code/status) without workarounds.

• Security & robustness: IN parameter binding avoids string concatenation and reduces injection risks.

• Consistency: Aligns RSE API behavior with common SQL execution patterns (prepared statements + bound parameters).

Not sure how this would apply to RSE API. Can you give an example of what you desire to do?