Does the usage have to be a "rexx external function"?
if the <function> has been written as a rexx external function
that' s it
Can't the rexx just use a module which is OK for the Cobol program to call?
if the <thing> has already been written, it must be REwritten as a <standard> callable <object>
REXX variables are variable-length strings and REXX takes care of everything,
as seen here http://publibz.boulder.ibm.com/cgi-bin/ ... 0253&CASE=
where rexx takes care of all the length issues
values can be passed back to the calling REXX
1 - using rexx SHV interface for REXX under TSO or IRXJCL
2 - using IKJCT441 ( TSO generic variable access routine ) for REXX under TSO
- both methods have pros/cons
1 - valid only for REXX scripts
2 - allows to share variables with CLISTS
using the Address <environment> facility any assembler subroutine can be called from REXX ( see IGGCSI00 )
but then all the variable handling is less than automated ( the user must provide for fixed/variable length issues )
Maybe not "cool" enough.
coolness does not make any difference, it is just impractical
Could one call the function from a rexx snippet called from the cobol program?
but then there would be the issue of passing back to COBOL the results
COBOL/REXX is kind of unidirectional, things can be passed to REXX, not back