Documente Academic
Documente Profesional
Documente Cultură
Copyright
Copyright 2008 Cognos ULC (formerly Cognos Incorporated). Cognos ULC
is an IBM Company. While every attempt has been made to ensure that the
information in this document is accurate and complete, some typographical
errors or technical inaccuracies may exist. Cognos does not accept
responsibility for any kind of loss resulting from the use of information
contained in this document. This document shows the publication date. The
information contained in this document is subject to change without notice.
Any improvements or changes to the information contained in this document
will be documented in subsequent editions. This document contains
proprietary information of Cognos. All rights are reserved. No part of this
document may be copied, photocopied, reproduced, stored in a retrieval
system, transmitted in any form or by any means, or translated into another
language without the prior written consent of Cognos. Cognos and the
Cognos logo are trademarks of Cognos ULC (formerly Cognos Incorporated)
in the United States and/or other countries. IBM and the IBM logo are
trademarks of International Business Machines Corporation in the United
States, or other countries, or both. All other names are trademarks or
registered trademarks of their respective companies. Information about
Cognos products can be found at www.cognos.com
This document is maintained by the Best Practices, Product and Technology
team. You can send comments, suggestions, and additions to
cscogpp@ca.ibm.com .
Contents
1 INTRODUCTION ............................................................................................ 4
1.1 PURPOSE .............................................................................................................. 4
1.2 APPLICABILITY ....................................................................................................... 4
1.3 EXCLUSIONS AND EXCEPTIONS .................................................................................... 4
2 USEFUL UNIX COMMANDS FOR TM1 ............................................................ 4
3 SIMPLE COMMANDS ..................................................................................... 4
3.1 PWD - RETURN WORKING DIRECTORY NAME .................................................................... 4
3.2 LS- LIST CONTENTS OF DIRECTORY .............................................................................. 4
3.3 HOW TO SET BACKSPACE KEY TO DELETE ....................................................................... 5
3.4 CAT - CONCATENATE AND DISPLAY FILES ........................................................................ 5
3.5 DF - DISPLAY STATUS OF DISK SPACE ON FILE SYSTEMS ...................................................... 6
3.6 CD - CHANGE WORKING DIRECTORY.............................................................................. 7
1 Introduction
1.1 Purpose
This document provides some information on using basic UNIX commands to
help with the administration of TM1 when running in a UNIX environment.
1.2 Applicability
TM1 version 9.1 and prior running on UNIX operating system
These commands are based off of a Solaris 2.8 server. However, most of these
commands are universal across the 3 platforms that IBM Cognos supports (AIX, Sun,
and HP)
3 Simple Commands
3.1 pwd - return working directory name
#pwd
# ls
ls Options
# ls la
Gives more information on the files in the directory (ie. permissions, size, date last
used)
#cat Tm1s.cfg
df Options
#df -k
Displays in Kilobytes
4 Detailed Commands
4.1 ps - report process status
This command will search all the processes that are running on the UNIX server that
have TM1 in the name. This is a great command to find out how many TM1 servers
are running and who started them.
4.2 top - a utility that provides a rolling display of top cpu using
processes
# top
CPU usage
Physical RAM
What RAM is being used
#vmstat
vmstat Options
#vmstat 1
# vmstat 1 >vmstatlog
#vmstat -S
Report on swapping rather than paging activity. This option will change two
fields in vmstat's ``paging'' display: rather than the ``re'' and ``mf'' fields,
vmstat will report ``si'' (swap-ins) and ``so'' (swap-outs).
#mpstat
A command that may help gain some more detail on the CPU usage. This command
is similar to mpstat on Solaris.
The sar command with -M will segregate CPU usage per CPU. If you type in
sar -M 1 10
this will give a CPU response every second for 10 seconds. What I would do is the
following
What this will do is every 5 second report CPU usage 100 times and output the stats
to a log file. Run this command when you kick off 7 TI processes again
#psrinfo
Without the processor_id operand, psrinfo displays one line for each
configured processor, displaying whether it is on-line, non-interruptible
(designated by no-intr), off-line, or powered off, and when that status last
changed. Use the processor_id operand to display information about a
specific processor.
psrinfo Options
# psrinfo v
Note:
Best to output this to a log file because a lot of information is returned
#sysdef >syslog
4.8 TOP
Top is scripted command that needs to placed in the /usr/local directory. This
command gives valuable details on processes running and how much CPU and
physical RAM is being used
If the user does not get this correct one gets a pstack output full of question marks like:
Examples:
1) User is in the directory /appl/Applix and start the server with the command
bin/tm1s.exe z
In the core file is the executable path bin/tm1s.exe so
user must be in the directory /appl/Applix when pstack is run so that bin/tm1s.exe find
the executable.
Core file can be anywhere.
We should, as part of the standard instructions for Solaris and HP, have customers:
1) Do a sum on the core file and submit the produced values with any inquiry report.
Run sum path-to-core-file
This produces something like:
34216 7584 core.13307