A while ago I answered a question of yours where the root cause of the
problem was that some variable didn't contain what you thought it did, and
suggested use of say statements like
say "thingy is >"thingy"<"
and yet here, where your description of the problem makes it near certain
that the problem is that some var doesn't contain quite what you think,
you're still doing things like:
which will not, for example, show you if there are trailing blanks on the
YOU say you are certain that the two programs are equivalent. I can say
without looking at the code that they won't be. YOU can be sure too, by
altering the non-hardcoded version to have just one test in it. After
Arg directory outputFile
if outputFile \== "yourexpectedhardcodedvalue" then...
and you'll find it isn't the same. Or perhaps you'd need, after you create
the Path var:
Path = sQuote||directory ||'*.*'||sQuote
if Path \== 'C:\SNA\*.*' then say "path mismatch"
From where I sit, this isn't so much a rexx issue, as you not seeming to
have any idea how to check that your code does what you think it does. Nor,
when there's a problem, do you seem to havce any idea how to diagnose where
the problem might lie. And yet I'm sure you said that while rexx is new to
you you had somne expertise in some other language... Surely you know how
to do fault finding in that? So apply the same principles here.
TBH I think you're trying to run before you can walk. You don't seem to
have got the hang of basic rexx principles.
You sign yourself "IBM Intern"; if that means what I think it might, then
why on earth haven't you read the (TSO) Rexx language manual cover to cover?
Jeremy C B Nicoll - my opinions are my own.