All of a sudden, scheduled tasks that update the Cognos Cubes are getting failed. When I try to run it manually from the CMD it is getting executed successfully. But, when I try to create a bat file and run the below script nothing is happening. Could someone look into this and let me know if anything is wrong.
#echo on
C:
cd "C:\Program Files (x86)\ibm\cognos\c10\bin"
Cogtr.exe -n2 -m "C:\Cognos\cube models\test.mdl"
Guess your formatting got awry when posting to the forum, but in general it looks ok.
When you say “nothing happens” — there might be a cogtr process in background you don't see.
You're running with n2 command line syntax, making Transformer run “background”
http://pic.dhe.ibm.com/infocenter/cbi/v10r1m0/index.jsp?topic=%2Fcom.ibm.swg.im.cognos.ug_cogtr.10.1.0.doc%2Fug_cogtr_id13215n_option.html
Check Task Manager to see if that's the case. You can change the line to just -n to see a bit more action )
Related
I am getting this error when running "behave -f" command, I have init.py file in steps,feature folder. Please let me know if there is any solution.
I tried running the feature for generating reports.
this question is not clearly formuled, there are details missing here. You must add something like a capture or similar to show us the directory tree you have in your project or so.
The init.py file doesn't matter to run behave. I'll show you an Hello-World project that works with the proper output of running the command behave in the command line.
If you need some other help, please, add more information about your question.
I'm following a tutorial to install a program on an RHEL environment and I've overcome some errors up until this point. I'm at the end of the installation process, attempting to confirm the validity through "make test", which returns the following error:
[user#localhost verilator-4.018]$ make test
Can't open perl script "/bin/verilator": No such file or directory
...
[Makefile:228: smoke-test] Error 10
I first checked to see if there was a verilator-4.018/bin/verilator file, which there was.
I then tried researching the error online and got a single result, where a user stated the issue could be solved by "Setting VERILATOR_ROOT to the root of your checkout", but I'm not too sure how to interpret this since I'm a beginner.
I tried setting as root:
[root#localhost verilator-4.018]# make test
But got the same error messages.
Also, please let me know how I can rephrase the title to make it more specific. I thought it was difficult to be specific about a question where I need interpretation help.
There is no /bin/verilator ... there is bin/verilator. But it's more tricky than that : The tests are done with test_regress/driver.pl, so "bin/verilator" is one level up.
Edit test_regress/driver.pl, line 782 to
my #cmdargs = ("perl", "$ENV{VERILATOR_ROOT}../bin/verilator",
... and the firsts tests can be run.
More bugs : "smoke-test" fails : Will use a file from the install destination. Please do # make install ... and the next tests can also be run.
Test result → make-test__result.txt https://www.dropbox.com/s/tebcqj7bl5dkzx8/make-test__result.txt?dl=0
Please notice the SYSTEMC settings. verilator was built with $ export SYSTEMC_INCLUDE=/usr/local/include/ && export SYSTEMC_LIBDIR=/usr/local/lib-linux64 && ./configure && make
SYSTEMC is required for the tests to pass. See verilator/README
By default, all scripts in PyCharm seem to execute in a separate python interpreter called "Run", which, as far as I can make out, is pretty much independent of the IPython console running alongside. Now, to execute any snippet of the script after the whole thing has been run, I can copy-paste into the Run pane, but this is not ideal as it is not an actual python/ipython console. If I want to execute in the console, I will need to run the whole thing again inside the console (and not just a snippet) because the console doesn't seem to recognize/store any of the variables when it was run, which is tedious.
I've searched for a solution, but the closest I got was to enable "show command line afterwords" in the Run Configurations. This just seems to throw up an error on the lines of "file not found", which makes no sense. I'm running my script through SSH into a remote server, if that helps.
Go to run --> edit configurations...
towards the button you'll see a checkbox that says "run with python console"
make sure its checked
try to edit the run config, via run -> edit configuration.
And check the path of the working directory or the script directory.
Description
Trying to install pilfs (the LFS for raspberry) on my raspberry pi 3. I'm following the guide as posted here: http://www.intestinate.com/pilfs/guide.html
I'm currently following their "chapter 8"
8 Building Chapter 5 [5.4. Binutils - Pass 1]
Alright, this is the moment of truth. Will you make your way through
chapter 5 slow and steady, or just execute the build script and go do
something else for 30 hours? This is for you to decide ... I've done
both :)
Also, here is where you might want to start a tmux or screen session.
Because if you break your ssh connection or your router has a hickup,
your build will just stop.
So you've made up your mind? Okey, script runners, start your engines:
cd $LFS/sources
chmod +x
ch5-build.sh
./ch5-build.sh
The script will report your SBU time after the first binutils build has finished, mine
is usually around 1 hour.
For those brave souls who are working through the chapter by hand,
check out the about page and read the build scripts to figure out
what's going on.
Error
When I do ./ch5-build.sh, it's causing the following mesage:
Not running as user lfs, you should be!
Question:
What step did I miss for this to happen? How do I run myself as a "lfs user"?
You need to enter su - lfs in the command line and then enter your password. This is assuming you have created the lfs user earlier in the book. From there, you can run the shell script.
I am following this tutorial that is like the hello world for post-commit
I am using Ubuntu 10.04. I installed svnnotify and ran $ which svnnotify which output:
/usr/bin/svnnotify
so I changed the path in the turorial from /usr/local/bin/svnnotify to /usr/bin/svnnotify
I also tried changing the line: #!/bin/sh to #!/bin/bash since bash is the login shell in ubuntu 10.04.
I tried to run it the way the tutorial originally had it, with my changes, and combinations of the two.
Every time the commit is successful but I get
Warning: post-commit hook failed (exit code 1) with no output.
The original way had output not found
I am very new to linux and shell scripting and have exhausted everything I can think of. What am I doing wrong?
Get the script working and tested before trying to run as a commit hook. I expect that your problem is something to do with the script, maybe not being marked as executable, environment wrong, etc.. i.e. if you can't get it to run successfully from the command line, this is more of a unix/shell question and doesn't really have anything to do with SVN (yet).
I'm not sure whether this applies in the Linux world, but in the Windows versions of SVN I've used, the code which runs the hook scripts only captures STDERR. If your hook script is only writing messages to STDOUT, that would likely explain the "No Output" warning.