Changing interface language in DB2 Control Center

Created:
Last Update:
Author: Christoph Stoettner
Read in about 1 min · 44 words
DB2

Fountain pen and a notebook

Photo by Aaron Burden | Unsplash

I often install IBM Connections on localised operating systems, so normally DB2 control center get started with a non-english language.

Interface language in DB2 control center can be changed through environment variable DB2LANG. After setting DB2LANG=EN and restart db2cc i get a english interface.

Author

Christoph Stoettner

I work at Vegard IT GmbH as a senior consultant with a focus on collaboration software, Kubernetes, security and automation. I mainly deal with HCL Connections, WebSphere Application Server, Kubernetes, Ansible, Terraform and Linux.

Sometimes my daily work results in technical talks and blog articles, which you can follow here more or less regularly. You can find the presentations in the main menu under public speaking .

I created a list of tools I use regularly, most of which have been released under an open source license.

In my spare time I read a lot, test all kinds of technical software and gadgets and try to follow about 200 RSS feeds.
Here you can find a collection of them.

This is my private blog, all opinions are my own.

           

Add a comment
Error
There was an error sending your comment, please try again.
Thank you!
Your comment has been submitted and will be published once it has been approved.

Your email address will not be published. Required fields are marked with *

Suggested Reading
Aaron Burden: Fountain pen and a notebook

Adding EMPLOYEE\_EXTENDED to all users

Today i read a question in the IBM Connections Forum about setting the EMPLOYEE_EXTENDED role to all users in a Connections deployment.

Created:
Last Update: Read in about 1 min
Aaron Burden: Fountain pen and a notebook

Command history wsadmin on Linux

Missing command history on Linux is a little problem when using command line utilities like wsadmin, db2, sqlplus and so on. I found a solution for this today. You can use rlwrap to get command history for all applications on the console and it is possible to recall and edit the commands. Rlwrap uses readline. Installation on CentOS: yum install readline-static gcc make tar -xvzf rlwrap-0.41.tar.gz cd rlwrap-0.41 ./configure make make install Call rlwrap with wsadmin: rlwrap -r /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/wsadmin.sh -lang jython -username wasadmin -password password rlwrap and db2 rlwrap -r db2 Use rlwrap everytime with alias vim ~/.bash_profile export WAS_HOME=/opt/IBM/WebSphere/AppServer export DMGR=Dmgr01 alias db2='rlwrap -r db2' alias wsadmin='cd $WAS_HOME/profiles/$DMGR/bin;rlwrap -r .
Created:
Last Update: Read in about 1 min
Aaron Burden: Fountain pen and a notebook

Skripting DB2 Automatic Maintenance

After skripting jdbc and j2ee on WebSphere i was interested to fasten the DB2 configuration after a Connections installation. There are two ways to get valid source xml-Files for automatic maintenance in DB2. I use automatic maintenance, because i can set a maximum backup time and how many dumps of one database should be stored. DB2 deletes old backups (which i have in a filebackup each night) automatically. You can’t script this settings directly, IBM provides two system calls for this: sysproc.automaint_set_policyfile and sysproc.automaint_set_policy. I use the file variant here, because i think it easier to handle files than blob content.
Created:
Last Update: Read in about 3 min