Same module, same code, different results?

Environment

Can anyone think of a reason why the same exact command (the path to the CLT is explicitly used, the arguments are hard-coded) in a shared module, with the same environment information, could work when called by one script and not when called by the other?I realize this is a bit vague because I cannot post all the code - though I'll be happy to answer specific questions of detail if sufficient rationale for why it might have an effect is provided.

Find more posts tagged with

Comments

Nikunj

Hi,
Are both the script in same location....
I am not sure...but i guess i have heard that sometimes script runs one location but not from other...this is mostly when u r in Unix...i Know this is vague...who knows anything can happen...
Or may be there must be some variable...which scriptB is able to access and other not...

I know this is not answering your question but u can always try it out.... Smiley Happy

test.xlsx

Adam Stoller

Hi,
Are both the script in same location....
I am not sure...but i guess i have heard that sometimes script runs one location but not from other...this is mostly when u r in Unix...i Know this is vague...who knows anything can happen...
Or may be there must be some variable...which scriptB is able to access and other not...

I know this is not answering your question but u can always try it out....

Both scripts lived in the same directory.
I ended up moving the setting of $mailserver into a different module (also used by both scripts, and the other module) - and got it working. I still don't know what caused the problem to begin with - but as far as I'm concerned, there isn't much need to keep this thread open ... so I'm closing it.

Thanks anyway.