Job picking default parameter values and not from script.
Posted: Tue May 11, 2010 8:27 am
Dear All,
There is a job in a sequence which we run using a shell script and also pass the parameters to it using the script.
But, here is the situation, I have been having issues with the sequence aborting and hence did some investigation, upon which it was found that the job whenever it fails is actually picking the DEFAULT parameter values in the job properties as opposed to the one's specified in the script, however this does not happen every time the job runs, only sometimes it picks the DEFAULT values specified within the job properties, isnt this a strange situation?
Any idea what could be the reason behind this?
If it helps, this problem started when the log files hit the max limit of 2GB (Apparently when there was an upgrade the auto purge option was not enabled).
There is a job in a sequence which we run using a shell script and also pass the parameters to it using the script.
But, here is the situation, I have been having issues with the sequence aborting and hence did some investigation, upon which it was found that the job whenever it fails is actually picking the DEFAULT parameter values in the job properties as opposed to the one's specified in the script, however this does not happen every time the job runs, only sometimes it picks the DEFAULT values specified within the job properties, isnt this a strange situation?
Any idea what could be the reason behind this?
If it helps, this problem started when the log files hit the max limit of 2GB (Apparently when there was an upgrade the auto purge option was not enabled).