#AREXX & MFF
3 messages in this thread
I'm puzzled that your external function couldn't be found — REXX: is
searched. What is the actual name of the function file? Keep in mind that
when function names are resolved in file-name space that the file extension
used is that specified by the host. If your file is named foo.rexx and MFF
uses .mffm, then calling it as
call foo args,args,etc.
would search for REXX:foo and REXX:foo.mffm and thereby miss the file.
I'm also puzzled about the quotes — all commands issued from REXX are
evaluated as expressions first, so this would normally strip away the
quotes. You might want to run the macro with TRACE C in effect to see
exactly the command being issued.
In this case I wrote a boolean function called OpenRexxArpLib() that
returns zero if it fails. It has a .rexx extension but I could have sworn
I tried a fully qualified path name when I was trying to find the problem.
Let me try that again.
With quotes… could the command
'PUT' RecordVar
have a different interpetation than
'PUT RecordVar'
A command like
'PUT' RecordVar
would be evaluated as an expression, quite possible with a value for the
RecordVar variable being retrieved (whether this is what you want or not).
However, issuing the command as
'PUT RecordVar'
would issue the string as a literal (without the quotes of course) to the
external host, so no value would be retrieved for the variable.
Again, turning on TRACE C should illuminate the situation.