I think we are going round in circles and digging ourselves in deeper, somehow.
You are, not US, refusing any attempt to understand the REXX interface logic
Cobol can build the parameter block like that. On the Call, the RETURNING phrase could be used to receive the function value into a data-item defined in the Cobol programl.
show how please, note that the <even> token is not the length address but the length itself
This sounds promising.
no it does not...
REXX external functions
interact with the calling environment ( REXX on behalf of the calling script )
using the <structures>
000367 IRXEFPL REXX External Function
000368 IRXEVALB REXX Evaluation Block
000369 IRXSHVB REXX Shared Variable Block
IRXEFPL for the mapping of the input parameter list
( the addresses of the variables are on a second <jump> )
IRXEVALB to return the result
IRXSHVB to <read> and <write> the variable content
( the external function is supposed to know if a parameter is <data> or the name of a variable
and in this case You are out of luckgiven also the note in the source
*| This is the name (NOT value) of a variable where the
*| MD5 context is maintained.
so .... nooooo way
trying to interface a third party tool by tweaking the calling conventions of any HLL language is the safest road to unmantainable code