It's all about the answers!

Ask a question

Buildforge Issues running jobs.

Mark Ireland (26115347) | asked Nov 26 '12, 11:12 a.m.

I have one of the strangest issues, this is the facts :-

On buildforge (Multiple versions!)

step runs :-
"d:\program files\ibm\rational insight\cognos\bin\rundsjob.exe" DB2 DSN=XXXX04R;UID=db2inst4;PWD=~981C5C121BFC824E9D51697A3B2CEDD364;TRUSTED=FALSE Import_OPPTY_Data

If the target machine is older OS, this works.
If run via a CMD window in Older OS or in windows 2008 this works fine.

However, if run on windows 2008, via buildforge the job does NOTHING no logs nothing.
Finally,  If I change the job so that it FAILS, the fail shows as expected in BuildForge.

Has anybody else seen this? Or knows the fix?



One answer

permanent link
Spencer Murata (2.3k115970) | answered Nov 27 '12, 12:38 p.m.
 Hard to know from a first look, but you can take a further look by saving off the temporary batch file and checking it to see what the difference is.  In the bfagent.conf there is a option #leave_tmp_file.  Uncomment that and run the command again.  In the OS temp directory you should see a temporary file like: tmpbf8A87C8E34DC46857EA53F8B49BC93CFA.cmd

Open that to see exactly what the BF agent is actually trying to run.  That will hopefully help highlight what the difference is between running from CLI and from BFA.  Also make sure that you check for any CLI interaction options and make sure its the same user executing the command.

Your answer

Register or to post your answer.