IBM Tivoli Storage Manager Server 6.2.3 is out

IBM Tivoli Storage Manager Server is finally at the 6.2.3 release. For awhile now, it’s been stuck at 6.2.1 and that if you wanted 6.2.2, you had to install the interim fix which I wasn’t comfortable with.

My favorite APAR you ask?

IC69003 IC69003 5698ISMSV 62W LACK OF DOCUMENTATION REGARDING SERVER UPGRADE TO 6.X IN A CLUSTERED ENVIRONMENT.

I would say that it’s just hard to find and read the documentation in general.

Nonetheless, hopefully I will get it installed this week and check out if I notice anything different.

Posted in software | Tagged , , | Leave a comment

Remote desktop into Windows 7 and Server 2008 from XP

remote desktop 7.0 client

I’m not sure how I missed this, but Microsfoft released an update to the remote desktop client called Remote Desktop Connection 7.0 for Windows XP, Windows Vista SP1, and Windows Vista SP2. It basically allows for these clients to remote desktop  into Windows 7 and Window Server 2008.

This is great because I’ve lowered the security settings on Windows 7 in order to allow for my old XP boxes to remote in. Now I can just update this client and I’m good to go with the higher security settings that come default in Windows 7.

Also keyboard ninjas, just type ‘mstsc’ to load up the remote desktop client from Run or the Search Box.

Posted in software | Tagged , , , , | Leave a comment

Adding identi.ca support on seesmic android app

Proof of identi.ca on android seesmic. A bit fuzzy though 🙂

I did some searches and found that I can add my identi.ca account to my seesmic android app. Here are two blog posts I found about it:

http://status.net/2010/03/25/using-seesmic-for-android-with-statusnet

http://blog.seesmic.com/using-seesmic-for-android-to-add-other-web-applications-like-tumblr-identica-wordpress.html#more-197

On version of Seesmic 1.7 for android, I did the following

  1. Add account.
  2. Twitter proxy
  3. Filled out my username and password.
  4. Use secure connection
  5. REST API server: https://identi.ca/api/
  6. Unchecked “Use XAuth”.
Posted in software | Tagged , , | 1 Comment

Greening through IT inspired post

Greening Through IT book cover

I’ve been reading Greening Through IT by Bill Tomlinson and has been a pretty good read so far. I’m halfway through so I can’t give a big review, but I can say that I found it very interesting and gives me new outlook on nature in life in general.

Although I haven’t reached specific ways of greening in my situation via the book, I’d thought I would at least list some ways that we do it at work.

  1. Lab computers are turned off soon after the lab closes and automatically turn back on in the morning before labs start.
  2. Servers are set in the BIOS to have power settings controlled by the O/S so when there’s no load on the server, the cpu’s are running at a slower clock speed. The newer r610s that we have I haven’t played with comparing it with O/S mode and some other mode that I’ve forgotten what’s it’s called.
  3. A/C aren’t set to be super cold: we’ve raised them to be in the 70s so they don’t need to be wasting a ton of energy trying to cool everything down a lot.
  4. Warm and cold aisles of racks. We have raised floors with air vents that are only in the cold aisles and then have the backs of other racks face each other for the warm aisles with cool vents in the floor. This keeps our cooling more efficient and “should” be more “green.”
  5. Monthly maintenance of the A/C units. I try to make sure the A/C units are running with solid belts so that they are running optimally all the time. Broken belts cause some low air flow wastes much energy.
  6. Virtualization. Everyone always talks about consolidation, but it’s really easy to dump a few vm’s on newer servers and just assign a core to each of them. We removed an old sun server recently and replaced it with a vm and it barely takes any load on the server. We use xen on centos as our vm technology of choice.

So there’s a few that I can think of at the top of my head. Stay green!

Posted in tips | Tagged , , | Leave a comment

compile amber 11 cuda on centos linux

Here are the steps that allowed me to actually compile amber, amber mpi, amber cuda, and some other cuda variations on Centos 5.6.

After each make clean I had to rerun the python patch script, that was something wasn’t so clear and made my compiling not fun when figuring it out.

  1. amber 11 with bugfix13 and ambertools bugfix 4
  2. Installing it at /pkg/amber/11-1.5.0
  3. Get Amber11.tar.gz and get bugfix all for amber 11 at http://ambermd.org/bugfixes11.html
  4. get ambertools 1.5 at http://ambermd.org/AmberTools-get.html
  5. Get bugfix for ambertools at http://ambermd.org/bugfixesat.html
  6. cd /pkg/amber
  7. tar -xvpf Amber11.tar.gz which puts it in amber11 folder
  8. tar -xvpf AmberTools.1.5.tar.bz2 which puts it in amber11 folder
  9. mv amber11 11-1.5.0
  10. export AMBERHOME=/pkg/amber/11-1.5.0
  11. cd /pkg/amber/11-1.5.0
  12. patch -p0 -N < bugfix.all
  13. mv bugfix.all bugfix.all.ambertools.up.to.4 so we know how many bugfixes it does
  14. download bugfix.all for amber
  15. download apply_bugfix.x
  16. chmod 700 apply_bugfix.x
  17. ./apply_bugfix.x bugfix.all
  18. mv bugfix.all bugfix.all.amber.up.to.13

# now that all the bugfixes done let’s compile ambertools

  1. cd /pkg/amber/11-1.5.0/AmberTools/src
  2. ./configure gnu
  3. NOTE: after installing AmberTools, if you want to compile       Amber11 using AmberTools 1.5, you must run the        AT15_Amber11.py script first, e.g.:       cd /pkg/amber/11-1.5.0; ./AT15_Amber11.py; make serial       (See the Amber11 Users’ Manual for full instructions,       and be sure to have a backup, since the AT15_Amber11.py       script will modify your Amber11 files.)
  4. make install
  5. cd /pkg/amber/11-1.5.0
  6. ./AT15_Amber11.py
  7. cd src
  8. make serial
  9. cd ../test
  10. make test

359 file comparisons passed

21 file comparisons failed

0 tests experienced errors

== mpi time parallel ==

  1. yum install mpich2.x86_64 mpich2-devel.x86_64
  2. cd /pkg/amber/11-1.5.0/AmberTools/src
  3. make clean
  4. ./configure -mpi gnu
  5. cd ../../src
  6. make clean
  7. cd /pkg/amber/11-1.5.0./AT15_Amber11.py
  8. cd src
  9. make parallel
  10. cd ../testexport
  11. DO_PARALLEL=’mpirun -np 2′
  12. Create a ~/.mpdconf
  13. mpd &
  14. make test.parallel

Some tests require 4 threads to run, while some will notrun with more than 2.  Please run further parallel tests with theappropriate number of processors. See README for details.
make[1]: Leaving directory `/pkg/amber/11-1.5.0/test’

361 file comparisons passed

9 file comparisons failed

0 tests experienced errors

  1. export DO_PARALLEL=’mpirun -np 4′
  2. make test.parallel

make[1]: Leaving directory `/pkg/amber/11-1.5.0/test’

282 file comparisons passed

16 file comparisons failed

0 tests experienced errors

== let’s try cuda now ==

  1. install the cuda developer nvidia driver
  2. install cuda stuff into /usr/local/cuda-3.2
  3. run deviceQueryDrv as root once after compiling it from the sdk toolkit
  4. export CUDA_HOME=/usr/local/cuda-3.2/cuda
  5. export PATH=/usr/local/cuda-3.2/cuda/bin:$PATH
  6. unset DO_PARALLEL
  7. cd /pkg/amber/11-1.5.0/AmberTools/src
  8. make clean
  9. ./configure -cuda gnu
  10. cd ../../
  11. ./AT15_Amber11.py
  12. cd src
  13. make clean
  14. make cuda
  15. cd ../test
  16. export LD_LIBRARY_PATH=/usr/local/cuda-3.2/cuda/lib64:/usr/local/cuda-3.2/cuda/lib
  17. ./test_amber_cuda.sh

56 file comparisons passed

0 file comparisons failed

0 tests experienced errors
== cuda mpi ==

  1. cd ../AmberTools/src
  2. make clean
  3. ./configure -cuda -mpi gnu
  4. cd ../..
  5. ./AT15_Amber11.py
  6. cd src
  7. make clean
  8. export C_INCLUDE_PATH=/usr/include/mpich2-x86_64:/usr/include/mpich2-i386
  9. export CPLUS_INCLUDE_PATH=/usr/include/mpich2-x86_64:/usr/include/mpich2-i386
  10. make cuda_parallel
  11. cd ../test
  12. export DO_PARALLEL=’mpirun -np 2′
  13. ./test_amber_cuda_parallel.sh

29 file comparisons passed

0 file comparisons failed

0 tests experienced errors

== now cuda dpdp ==

(Still using above environmental settings)

  1. cd /pkg/amber/11-1.5.0/AmberTools/src
  2. make clean
  3. ./configure -cuda_DPDP gnu
  4. cd ../..
  5. ./AT15_Amber11.py
  6. cd src
  7. make clean
  8. make cuda
  9. cd ../test
  10. ./test_amber_cuda.sh -1 DPDP

55 file comparisons passed

1 file comparison failed

0 tests experienced errors

=== now cuda dpdp mpi ===

  1. cd /pkg/amber/11-1.5.0/AmberTools/src
  2. make clean
  3. ./configure -cuda_DPDP -mpi gnu
  4. cd ../…/AT15_Amber11.py
  5. cd src
  6. make clean
  7. make cuda_parallel
  8. cd ../test
  9. ./test_amber_cuda_parallel.sh -1 DPDP

 

 

Posted in software | Tagged , , , | 4 Comments

Perl day 3: unless statement

Going off our if statement yesterday, I found that there’s something called the unless clause. According to the ifelseifelse website, the unless clause is the opposite of an if statement. I like their example of the following two statements being equivalent:
if (!$flag) { do_something();}
unless ($flag) { do_something();}

I’m used to using the ! for doing the opposite of a boolean statement, and probably will be doing that instead of using the unless statement. It is possible that some situations are better to use the unless statement that would provide better readability, like:
#!/usr/bin/perl
$a = 'taco';

unless ('$a' eq 'burrito') {
print "unless $a is a burrito, don't print this \n";
} else {
print "else it's a $a \n";
}

Posted in software | Tagged , | Leave a comment

Perl day 2: if statements

The if statements that I’ve seen in perl seem to be pretty much the standard. It looks like the standard kind that I’ve used in java. Today’s link is the perl – if statement syntax webpage.

We got our basic if then a boolean expression in parenthesis and then the statements that will run that satisfy it.

$a = 2;

if ($a == 2) {
print "true\n";
}

Posted in software | Tagged , | Leave a comment

Perl day 1: arguments

So here’s day one of my journey to learning perl. The reason I’m learning it is because there’s a lot of perl used at my work place. I can sort of read it, but I think it’s good to actually be able to code it as well.

The first lesson I thought would be good is how to accept arguments. I always feel like this is a good way to start because I can mess around and toss different kinds of strings and numbers into the program easily. The link for today’s code is from How to read command-line arguments with Perl

The website is pretty good about explaining that the arguments are stored in an array called ARGV and can reference the elements by using $ARGV[numberStartingFromZero]

From the sample I’ve noticed that the path for perl is at the top just like in python and shell scripts I’ve written before.

Another thing to notice is that $ is used when creating and accessing variables, even arrays.

Comments look like the common in most other dynamic languages and uses the # symbol.

Lastly, $#ARGV will get you what the last number of the array is. So if there’s only one element in the array, it will be in the 0th place.

Posted in software | Tagged , | Leave a comment

IBM TSM 6.2

I’m switching over from EMC Legato Networker to the IBM TSM 6.2 this year and I’m still in the phase of reading the documentation. I will say that it is a ton of things to read and the concepts of things are much different than in networker. The bummer right now is that I can’t get my tape library to work and so I haven’t been able to work with those yet.

Posted in software | Tagged , , , | Leave a comment

DeskPins – windows software

http://users.forthnet.gr/pat/efotinis/programs/deskpins.html

This is pretty sweet for Windows when you want to pin a window on top of all other ones. This works like on my linux desktop where you can just keep a window on top of all other ones.

Posted in software | Tagged , | Leave a comment