TEAMCONNECTION FREQUENTLY ASKED QUESTIONS: HOW TO DO ROUTINE OPERATING SYSTEM TASKS Document Number TR 29.2267 Angel Rivera, Lee R. Perlov, Edna Wong Kyu TeamConnection Development IBM Software Solutions Research Triangle Park, North Carolina Copyright (C) 1997. IBM Corp. ii How to do tasks in OEM platforms ABSTRACT This technical report contains a collection of hints and tips for TeamConnection users and family administrators that must cope with the heterogeneous operating systems environments supported by TeamConnection. This document focuses on several system-related tasks that are different across the diverse platforms available to developers using TeamConnection. Some sample tasks are: o How to start and stop the ObjectStore database o How to query for the free space of a file system ITIRC KEYWORDS o TeamConnection o OEM platforms o Operating systems o AIX o HP-UX o Solaris o OS/2 o ObjectStore o Windows NT o Windows 95 o Windows 3.1 ABSTRACT iii iv How to do tasks in OEM platforms ABOUT THE AUTHORS ANGEL RIVERA Mr. Rivera is a Advisory Software Engineer in the TeamConnection/CMVC development group. He joined IBM in 1989 and since then has worked in the development and support of library systems. Mr. Rivera has an M.S. in Electrical Engineering from The Univer- sity of Texas at Austin, and B.S. in Electronic Systems Engi- neering from the Instituto Tecnologico y de Estudios Superiores de Monterrey, Mexico. LEE R. PERLOV Mr. Perlov is a Staff Software Engineer in the TeamConnection/CMVC development group. He started working for IBM in 1985 in Gaithersburg, Md, working in the Federal Systems Division on various projects for the United States intelligence community. He then moved to RTP to work on library development and support. Mr. Perlov received a B.S.Acc degree in Accounting from the Uni- versity of Florida in 1983. He also completed two years of grad- uate work in the Department of Computer Science at the University of Florida. EDNA WONG KYU Mrs. Kyu is a Staff Software Engineer for the Software Solutions division at Research Triangle Park. She joined IBM in 1987 and has worked in testing, VM systems programming, support of library platforms and support of various UNIX platforms. Mrs. Kyu received a B.A. in Computer Science and a minor in Busi- ness from New York University in 1985. ABOUT THE AUTHORS v vi How to do tasks in OEM platforms CONTENTS ABSTRACT . . . . . . . . . . . . . . . . . . . . . . . . . III ITIRC KEYWORDS . . . . . . . . . . . . . . . . . . . . . iii ABOUT THE AUTHORS . . . . . . . . . . . . . . . . . . . . . . V Angel Rivera . . . . . . . . . . . . . . . . . . . . . . . v Lee R. Perlov . . . . . . . . . . . . . . . . . . . . . . . v Edna Wong Kyu . . . . . . . . . . . . . . . . . . . . . . . v FIGURES . . . . . . . . . . . . . . . . . . . . . . . . . . IX 1.0 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . 1 1.1 Supported Platforms . . . . . . . . . . . . . . . . . 1 1.2 Notes on the terminology used in this document . . . . 1 1.3 Suggestion for Intel Users . . . . . . . . . . . . . . 2 1.4 About this and previous technical reports . . . . . . 2 1.5 Acknowledgements . . . . . . . . . . . . . . . . . . . 3 2.0 END USER TASKS . . . . . . . . . . . . . . . . . . . . . 5 2.1 Where is the TeamConnection code located? . . . . . . 5 2.2 How to find out the version of TeamConnection? . . . . 5 2.2.1 GUI - all platforms . . . . . . . . . . . . . . . . 5 2.2.2 UNIX - Client/Server . . . . . . . . . . . . . . . 5 2.2.3 Intel - Client/Server . . . . . . . . . . . . . . . 6 2.3 How to find out the version of the operating system? 6 2.3.1 UNIX - operating system version . . . . . . . . . . 6 2.3.2 Intel - operating system version . . . . . . . . . 7 2.4 Where are the customization files for the TeamConnection GUI? . . . . . . . . . . . . . . . . . . . . 7 2.4.1 UNIX - Customization files . . . . . . . . . . . . 7 2.4.2 Intel - Customization files . . . . . . . . . . . . 8 2.5 Is there a sample profile for the TeamConnection end user? . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.5.1 UNIX - Sample profiles . . . . . . . . . . . . . . 8 2.5.2 Intel - Profile information . . . . . . . . . . . . 9 2.6 UNIX: How to see the contents of files that are active? 9 2.7 UNIX: How to link files and directories using symbolic links? . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.8 How much space is still available on disk? . . . . . . 9 2.8.1 UNIX - Space in a file system . . . . . . . . . . . 9 2.8.2 Intel - Space on each drive . . . . . . . . . . . 10 2.9 How to find out all the processes that are running? 10 2.9.1 UNIX - processes . . . . . . . . . . . . . . . . 10 2.9.2 Intel - Processes . . . . . . . . . . . . . . . . 10 2.10 How to test the connectivity of a host? . . . . . . 11 2.10.1 Using the ping command . . . . . . . . . . . . . 11 2.10.2 Using the host command (or equivalent) . . . . . 12 2.10.3 Using the nslookup command . . . . . . . . . . . 13 3.0 ADMINISTRATIVE TASKS . . . . . . . . . . . . . . . . . 15 Contents vii 3.1 Which are the main administration tools? . . . . . . 15 3.1.1 UNIX - Administrative GUI tools . . . . . . . . . 15 3.1.2 Intel - Administrative Tools . . . . . . . . . . 15 3.2 Is there a sample profile for a TeamConnection family? 16 3.2.1 UNIX - Family profile . . . . . . . . . . . . . . 16 3.2.2 Intel - Profile information . . . . . . . . . . . 16 3.3 Where are the error messages from the TC daemon and database? . . . . . . . . . . . . . . . . . . . . . . . . 16 3.3.1 UNIX - syslog . . . . . . . . . . . . . . . . . . 17 3.3.2 Intel - syslog . . . . . . . . . . . . . . . . . 19 3.4 Where are the host and services files? . . . . . . . 19 3.5 How to change the owner/group of a file? . . . . . . 20 3.5.1 UNIX - chown . . . . . . . . . . . . . . . . . . 20 3.5.2 Intel - file ownership . . . . . . . . . . . . . 20 3.6 How to export directories to be mounted by other hosts? . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.6.1 UNIX - exporting directories . . . . . . . . . . 21 3.6.2 Intel - Exporting directories or drives . . . . . 22 3.7 How to mount directories exported by a remote host? 23 3.7.1 UNIX - mount command . . . . . . . . . . . . . . 23 3.7.2 Intel - mount command . . . . . . . . . . . . . . 23 3.8 Using CD-ROMs . . . . . . . . . . . . . . . . . . . 24 3.8.1 AIX - CD-ROMS . . . . . . . . . . . . . . . . . . 24 3.8.2 HP-UX - Using CD-ROMs . . . . . . . . . . . . . . 26 3.8.3 Solaris - Using CD-ROMs . . . . . . . . . . . . . 28 3.8.4 Intel - CD-ROMs . . . . . . . . . . . . . . . . . 29 3.9 How to shutdown and reboot the machines? . . . . . . 29 3.9.1 UNIX - shutdown . . . . . . . . . . . . . . . . . 29 3.9.2 Intel - How to shutdown and reboot . . . . . . . 31 3.10 UNIX: How to identify and kill semaphores and free shared memory? . . . . . . . . . . . . . . . . . . . . . 32 3.11 Topics related to printers . . . . . . . . . . . . 32 3.11.1 HP-UX: How to setup a printer? . . . . . . . . . 32 3.11.2 AIX: How to setup printer access? . . . . . . . 33 3.11.3 Solaris: How to setup printer access? . . . . . 33 3.12 Miscellaneous topics, by platform . . . . . . . . . 34 3.12.1 Solaris: How to fix problems with the /etc/vfstab file? . . . . . . . . . . . . . . . . . . . . . . . . . 34 4.0 DATABASE TASKS . . . . . . . . . . . . . . . . . . . . 37 4.1 Environment variables needed by the user root . . . 37 4.1.1 UNIX - database environment . . . . . . . . . . . 37 4.1.2 Intel - database environment . . . . . . . . . . 38 4.2 Where is the ObjectStore code located? . . . . . . . 38 4.3 How to find out the version of ObjectStore? . . . . 38 4.4 How to find out if the ObjectStore server is running and active? . . . . . . . . . . . . . . . . . . . . . . . 39 4.4.1 UNIX - ObjectStore server process status . . . . 39 4.4.2 Intel - ObjectStore server process status . . . . 39 4.4.3 How to determine if the ObjectStore server is running in a host? . . . . . . . . . . . . . . . . . . . 40 4.5 UNIX - How to start the ObjectStore? . . . . . . . . 40 4.5.1 UNIX - How to start the ObjectStore server? . . . 40 4.5.2 UNIX - How to start the ObjectStore cache manager? 40 viii How to do tasks in OEM platforms 4.6 Intel - How to start ObjectStore? . . . . . . . . . 40 4.6.1 OS/2 - Starting ObjectStore . . . . . . . . . . . 41 4.6.2 Windows NT - Starting ObjectStore . . . . . . . . 41 4.7 How to restart the ObjectStore server after a crash? 41 4.8 UNIX - How to stop ObjectStore? . . . . . . . . . . 41 4.8.1 UNIX - How to stop the ObjectStore server? . . . 41 4.8.2 UNIX - How to stop the ObjectStore cache manager? 42 4.9 Intel - How to stop ObjectStore? . . . . . . . . . . 42 4.9.1 OS/2 - Stopping ObjectStore . . . . . . . . . . . 42 4.9.2 Windows NT - Stopping ObjectStore . . . . . . . . 42 4.10 How to display information about the ObjectStore server/client? . . . . . . . . . . . . . . . . . . . . . 43 4.11 How to backup an ObjectStore database? . . . . . . 43 4.12 How to restore a backed up ObjectStore database? . 43 4.13 How to copy an ObjectStore database? . . . . . . . 44 4.14 How to verify the validity of the pointers in an ObjectStore database? . . . . . . . . . . . . . . . . . . 44 APPENDIX A. BIBLIOGRAPHY . . . . . . . . . . . . . . . . . 45 A.1 TeamConnection 2 . . . . . . . . . . . . . . . . . . 45 A.2 TeamConnection 1, useful to TeamConnection 2 users . 45 A.3 Related Technical Reports . . . . . . . . . . . . . 45 APPENDIX B. COPYRIGHTS, TRADEMARKS AND SERVICE MARKS . . . 47 FIGURES 1. Sample shell script to manually mount NFS file systems 31 Contents ix x How to do tasks in OEM platforms 1.0 INTRODUCTION This document contains a collection of tips and hints on how to do several tasks that differ across the diverse operating system platforms in which the TeamConnection (TC) product runs. This document separates tasks into those performed by family administrators and system administrators, and those performed by general users of TeamConnection. Each task is grouped, where appropriate, into "UNIX" (that is, AIX, HP-UX and Solaris) and "Intel" (that is, OS/2, Windows NT, Windows 95 and Windows 3.1) sections, since there are typically significant differences in how tasks are performed for each group. Finally, there are subsections where differences exist between specific operating systems in a group. For example, the adminis- trative tool in AIX is SMIT and the corresponding tool for HP-UX is SAM. 1.1 SUPPORTED PLATFORMS The operating systems that have both server and client code are: AIX Version 4 HP-UX Version 10 Solaris Version 2 (see note) OS/2 Warp Windows NT The operating systems that have only client code are: Windows 95 Windows 3.1 The only database supported by TeamConnection is: ObjectStore 4.x (currently 4.02) 1.2 NOTES ON THE TERMINOLOGY USED IN THIS DOCUMENT o When this document was prepared, the port to the Solaris platform was in progress. o Some tasks are UNIX specific due to the multi-user character- istics of this class of operating system. Introduction 1 o The names of the operating systems will be used without the version numbers, when there is no need to specify it. For example, the term "AIX" means in this document "AIX Version 4". o The term UNIX will be used as a generic term for all the dif- ferent UNIX versions when there is no need to specify one of them. o The term Windows will be used as a generic term for all the different Windows versions when there is no need to specify one of them. o The term Intel will be used as a generic term for the non-UNIX operating systems that run under Intel processors (OS/2 and Windows) when there is no need to specify one of them. 1.3 SUGGESTION FOR INTEL USERS We strongly recommend installing a package of UNIX-like commands for your Intel platform. These packages are generally inexpensive and provide between 30 and 100 useful tools that are common to UNIX operating systems. These tools will allow you to perform most of the UNIX commands described in this document on your Intel operating system. You may try to find such packages from the Internet by using search engines such as "http://www.yahoo.com/" and using keywords such as "OS/2 utilities" or "Windows NT utilities". 1.4 ABOUT THIS AND PREVIOUS TECHNICAL REPORTS This document, as well as other recently released technical reports related to TeamConnection, contains some information that was previously available in other "unofficial" documents. We have endeavored to better organize the information and improve its readability so that you will find it more useful. This technical report is based on the technical report TR 29.2180 HOW TO DO ROUTINE TASKS IN THE OEM PLATFORMS FOR CMVC. 2 How to do tasks in OEM platforms 1.5 ACKNOWLEDGEMENTS Many of the questions and answers that are compiled in this tech- nical report were obtained from the TEAMC and CMVC forums in the IBMPC conferencing disk and from the CMVC6000 forum in the IBMUNIX conferencing disk. We want to thank the main participants in these electronic forums for their support! Also, we want to thank Dodde Stark for editing this technical report. Introduction 3 4 How to do tasks in OEM platforms 2.0 END USER TASKS This section describes some common tasks and useful information for TeamConnection client users. 2.1 WHERE IS THE TEAMCONNECTION CODE LOCATED? The default location for the TeamConnection code is: AIX "/usr/teamc" HP-UX "/opt/teamc" SOLARIS "/opt/teamc" OS/2 "c:\teamc" WINDOWS 3.1 "c:\ProgramF\TeamConn" WINDOWS 95 AND NT "c:\Program Files\TeamConnection" 2.2 HOW TO FIND OUT THE VERSION OF TEAMCONNECTION? 2.2.1 GUI - all platforms __________________________ The version of the TeamConnection GUI for all platforms can be found from the Help pulldown, option "Product Information". 2.2.2 UNIX - Client/Server ___________________________ The version of the TeamConnection server and client for UNIX can be found as follows: 1. Find out the directory where the daemon (teamcd) or the client (teamc) is installed: o For AIX or Solaris, enter: which teamcd o For HP-UX, enter: End User Tasks 5 whence teamcd 2. Change to the directory shown in the step above. 3. Find out the 'what' strings and search for 'teamc': o For the server, do the following: what teamcd | grep teamc o For the client, do the following: what teamc | grep teamc 2.2.3 Intel - Client/Server ____________________________ The client and code for Intel has the same "what" strings and if you have access to a similar "what" and "grep". command, then you can find out the version of the TeamConnection executables. For OS/2 and Windows NT, TeamConnection provides a version of the "what" command: "tcwhat". o Locate the TeamConnection "bin" directory on the path: echo %PATH% or PATH o Change to the directory shown above. o Find the 'what' strings and manually search for 'teamc': tcwhat teamcd | more 2.3 HOW TO FIND OUT THE VERSION OF THE OPERATING SYSTEM? 2.3.1 UNIX - operating system version ______________________________________ You can use the command "uname -a". The output will be similar to: AIX 1 4 operating-system-name release version 6 How to do tasks in OEM platforms 2.3.1.1 AIX level version For AIX, you can then find the level (that is, version.release.level) using the "oslevel" command. 2.3.1.2 X-Windows server version The X-Windows server is the program the manages the graphical display on your system and communicates with the TeamConnection GUI for UNIX. The X-Windows server needs to be running when you run the following command that displays the release number, among other data: xrdb -symbols 2.3.2 Intel - operating system version _______________________________________ You can use the command "ver". 2.4 WHERE ARE THE CUSTOMIZATION FILES FOR THE TEAMCONNECTION GUI? 2.4.1 UNIX - Customization files _________________________________ There are two customization files for the GUI: o Teamcgui This is the X Resource File where the user can specify the font size, the colors for the windows, etc. If this file does not exist, then the GUI will NOT create it in the $HOME directory; instead, the GUI will rely on the system-wide Teamcgui resource file which is located in /usr/lib/X11/$LANG/app-defaults/Teamcgui. The user could copy the sample /usr/teamc/samples/Teamcgui into the $HOME directory and customize it. End User Tasks 7 For advanced users: to guarantee that your new Teamcgui changes are loaded, do the following: 1. Exit teamcgui 2. xrdb -remove 3. xrdb -load Teamcgui o teamc20.ini This is the file that contains the tasks shown in the TeamConnection GUI Tasks window and contains values used by functions in the GUI. This file is created if it does not exist (such as when using the GUI for the first time) and resides in the $HOME direc- tory for the user account. NOTE: It is strongly recommended that the users should not attempt to edit this file. 2.4.2 Intel - Customization files __________________________________ In OS/2 and Windows, the teamc20.ini file is stored where the operating system code is stored, such as C:\OS2 or C:\WINDOWS. These files are updated through the settings page of the teamcgui. It is strongly recommended that the users should not attempt to edit this file. 2.5 IS THERE A SAMPLE PROFILE FOR THE TEAMCONNECTION END USER? 2.5.1 UNIX - Sample profiles _____________________________ The following sample profile can be used as the basis for the profile of a UNIX user account that will use TeamConnection (end- user). The user will have to read the entire profile and delete the comment character of those lines that are appropriate for the operating system to be used. /usr/teamc/samples/profile.user 8 How to do tasks in OEM platforms 2.5.2 Intel - Profile information __________________________________ Since Intel operating systems are single user systems, the TeamConnection installation script addresses all environmental configuration needs. 2.6 UNIX: HOW TO SEE THE CONTENTS OF FILES THAT ARE ACTIVE? To see the up-to-date contents of the files that are active, such as nohup.out and the audit/database logs, do the following: 1. Enter the following command: tail -f filename 2. Observe that the output is scrolling when the file is being updated. 3. If it is no longer scrolling, then the file is not being updated anymore. 4. Press Ctrl+C to exit from the tail command. 2.7 UNIX: HOW TO LINK FILES AND DIRECTORIES USING SYMBOLIC LINKS? To establish a symbolic link between a 'real' file/directory and a 'shadow' file/directory do: ln -s real-entity shadow-entity Use the following command in order to see the real file/directory of a linked file/directory: ls -l 2.8 HOW MUCH SPACE IS STILL AVAILABLE ON DISK? 2.8.1 UNIX - Space in a file system ____________________________________ To show, in kilobytes, the space left in the file system, use: End User Tasks 9 AIX df -k Without "-k" the default is 512 byte blocks. HP-UX bdf SOLARIS df -k 2.8.2 Intel - Space on each drive __________________________________ To show the space available on any logical disk drive, use: dir /w µDRIVE-LETTERº or chkdsk µDRIVE-LETTERº 2.9 HOW TO FIND OUT ALL THE PROCESSES THAT ARE RUNNING? 2.9.1 UNIX - processes _______________________ To see the processes related to TeamConnection that are running, do the following: o To find out how many TeamConnection family server daemons are running on the entire system: ps -ef | grep teamcd o To find out all of the processes running in a family account: ps -fu FAMILY_ACCOUNT NOTE: In TeamConnection, there are four different processes that are typically running: teamcd, teamagnt, teamproc and teamcgui. You will also intermittently see teamc and any miscellaneous tools being run in the family account. 2.9.2 Intel - Processes ________________________ 2.9.2.1 OS/2 and Windows NT - process status 10 How to do tasks in OEM platforms pstat | more 2.9.2.2 Windows 3.1 and Windows 95 You can use the Task Manager to find out which processes are running. 2.10 HOW TO TEST THE CONNECTIVITY OF A HOST? Sometimes it is important to test the connectivity of a host in order to proper diagnose a problem. 2.10.1 Using the ping command ______________________________ The "ping" command is the first tool that the user should use to diagnose possible network problems. The TCP/IP "ping" command can be used to test if a given host specified by a host name or host IP address is registered as a valid host and actively connected to the network. If the host name or IP address is not registered as a valid iden- tifier, then the ping command will fail. If the host is active but not connected to the network then the "ping" command will not be able to receive the expected message. For example: 1. At a prompt, type "ping testfam". If you receive information that is similar to the following, you can successfully connect to your TeamConnection family: PING testfam.company.com: 56 data bytes 64 bytes from 1.23.457.78: icmp_seg:0. time=0. ms 64 bytes from 1.23.456.78: icmp_seg:1. time=0. ms 64 bytes from 1.23.456.78: icmp_seg:2. time=0. ms 2. Press Ctrl+C to end the command. 3. If you receive the message "unknown host testfam", you cannot connect to the family. Verify that the data in the hosts and services files is correct, and then try the command again. End User Tasks 11 If you still do not get the correct response, contact your TCP/IP administrator to solve the problem. 2.10.2 Using the host command (or equivalent) ______________________________________________ In AIX and in OS/2 there is a command called "host" which gets the IP address given a host name or vice versa. This command uses the local /etc/hosts file first, and if the host name or the IP address is not found there, then the network name server is contacted next. In some networks, there could be a mismatch between the host name and the IP address. Do the following to verify that the hosts file is specified correctly: 1. Type "host family_name", where family_name is the name of your TeamConnection family. The information returned should match the number and name specified in your hosts file. For example, the system response might be as follows: testfam.company.com = 9.12.345.67 2. Type "host ip_address", where ip_address is the IP address of your machine. The information returned should match the number and name specified in your hosts file. For example, the system response might be as follows: testfam.company.com = 9.12.345.67 If you do not receive the expected response, contact your TCP/IP administrator to solve the problem. In some networks the second step gives a different host name and this will cause problems with TeamConnection. In other platforms we provide the "tchost" or "tchostw" command which provides the basic functionality of the "host" command pro- vided in AIX and OS/2. 12 How to do tasks in OEM platforms 2.10.3 Using the nslookup command __________________________________ The TCP/IP "nslookup" command skips the local hosts file and queries directly the network name server, thus its name: Name Server Look Up. It provides the host name and IP address of the name server, followed by the target host name and IP address. End User Tasks 13 14 How to do tasks in OEM platforms 3.0 ADMINISTRATIVE TASKS This section describes some common tasks that the administrator user of TeamConnection is likely to do with the operating system, in general. 3.1 WHICH ARE THE MAIN ADMINISTRATION TOOLS? 3.1.1 UNIX - Administrative GUI tools ______________________________________ AIX The main tool is "smit" for GUI or "smitty" for a character-based interface. for command line inter- face. HP-UX The main tool is "sam" for GUI. This tool is very hard to use when using the command line. SOLARIS The main tool is "admintool" for GUI. 3.1.2 Intel - Administrative Tools ___________________________________ 3.1.2.1 OS/2 The vast majority of administrative actions can be found by opening the System Icon. However, TeamConnection has its own folder and an icon for an Administration Tool, "tcadmin", that is used for administration tasks related to TeamConnection. 3.1.2.2 Windows NT and Windows 95 Generally performed administrative tasks are split between several icons. Here are the most commonly used for TeamConnection administration: In Windows NT 4 and Windows 95 The system administration facilities in Windows 95 are in the "Start" -> "Control Panel" program selection. In Windows NT 3.51: Administrative Tasks 15 o "Main Icon"->"System Icon" o "Main Icon"->"Services Icon" o "Administration Tools Icon"->"Event Viewer Icon" o "TeamConnection"->"TeamConnection Administration" 3.1.2.3 Windows 3.1 The limited system administration facilities are in: o "Main Icon"->"System Icon" 3.2 IS THERE A SAMPLE PROFILE FOR A TEAMCONNECTION FAMILY? 3.2.1 UNIX - Family profile ____________________________ The following sample profile can be used as the basis for the profile of a UNIX user account that will serve as a TeamConnection family: /usr/teamc/install/profile.family The TeamConnection family administrator will have to read the entire profile and revome the comment character of those lines that are appropriate for the operating system in question. 3.2.2 Intel - Profile information __________________________________ Since Intel operating systems are single user systems, the TeamConnection installation script addresses all environmental configuration needs. 3.3 WHERE ARE THE ERROR MESSAGES FROM THE TC DAEMON AND DATABASE? 16 How to do tasks in OEM platforms 3.3.1 UNIX - syslog ____________________ Errors encountered by TeamConnection are recorded in the system log file (syslog) when the syslog daemon (syslogd) is activated. If syslogd is not active, then the error messages are sent to the console of the TeamConnection server workstation; however, these messages eventually will scroll off the screen. Because multiple families may be supported by a single TeamConnection server, the messages logged in syslog may pertain to multiple families. It is important to activate the syslog daemon so that TeamConnection errors and database errors can be logged for sub- sequent problem resolution. To activate the syslog daemon do the following: 1. Login as root. 2. Use the touch command to create the syslog file if it does not exist already in the appropriate directory: AIX "touch /var/spool/syslog" HP-UX "touch /var/adm/syslog/syslog.log" SOLARIS "touch /var/adm/messages" 3. When creating the syslog file, set the file permissions according to the directions for the operating system. o AIX: chmod 666 /var/spool/syslog chown root:system /var/spool/syslog o HP-UX: chmod 666 /usr/adm/syslog/syslog.log chown root:system /usr/adm/syslog/syslog.log o Solaris: chmod 666 /var/adm/messages chown root:system /var/adm/messages NOTES: a. If you do not want to use "chmod 666", you can use any of the following: chmod a=rw /var/adm/syslog or chmod ugo=rw /var/adm/syslog Administrative Tasks 17 b. The command "chown root:system" is a short way to do the following: chown root /var/spool/syslog chgrp system /var/spool/syslog 4. Edit the /etc/syslog.conf file and add the following line: NOTE: You must use a tab character to separate the values. AIX "*.warning /var/spool/syslog" HP-UX "*.warning /var/adm/syslog/syslog.log" SOLARIS "*.warning /var/adm/messages" 5. Stop and restart syslogd after modifying syslog.conf and cre- ating the log file. a. AIX: stopsrc -s syslogd startsrc -s syslogd b. HP-UX: kill -HUP `cat /var/run/syslog.pid` c. Solaris ps -ef | grep syslog # Find the process id for syslogd kill -9 ******************** => use the process id /usr/sbin/syslogd 6. Verify that the syslog daemon is running: ps -ef | grep syslog You should see an entry for syslogd. 7. Verify that the syslog daemon is able to write into the syslog file. The following test case can help you to deter- mine if the syslog has been configured properly: a. Login with a TeamConnection family id. b. Use 'su root' and give a wrong password. This action will fail and will add a warning message at the bottom of the syslog. c. To quickly view the last 10 lines of the syslog, do: 18 How to do tasks in OEM platforms tail ****************** => use the appropriate name d. If the syslog is properly set and running, then a message similar to this one will be added to the syslog: Apr 19 hostname su: BAD SU from userid to root at /dev/pts/3 or May 1 oem-hp03 syslog: su : - ttyp1 cmhp3ora-root 8. If you want to cleanup the syslog, you can use the following command: cp /dev/null **************** => use the appropriate name 9. Monitor the syslog file at regular intervals so that any required maintenance or problem resolution can be performed. 3.3.2 Intel - syslog _____________________ The syslog facility is not a native application for OS/2 and Windows, TeamConnection provides an application specific syslog. The syslog file resides in the sample location where the TeamConnection Family Server (teamcd.exe) resides, and it is called "syslog.log". 3.4 WHERE ARE THE HOST AND SERVICES FILES? The "hosts" file is used to indicate the IP address of a host and aliases for that host. The "services" file is used to indicate the port number of the service (TeamConnection family). UNIX "/etc/hosts" and "/etc/services" It is recommended that the system administration utilities should be used to update these files, such as smit in AIX and sam in HP-UX. OS/2 They are located in the directory described in the environment variable "SET ETC" WINDOWS 3.1 They are located in the appropriate directory that differ in each TCP/IP product. In IBM TCP/IP for DOS, the directory is TCPDOS\ETC. Administrative Tasks 19 WINDOWS 95 They are located where the operating system is located, such as C:\WINDOWS. The "hosts" file by default does not exist, but it can be constructed from the sample "Host.sam" which, by default, resides in C:\WINDOWS. WINDOWS NT They are located in the subdirectory SYSTEM32\DRIVERS\ETC, where the operating system is located. The default is C:\WINNT. 3.5 HOW TO CHANGE THE OWNER/GROUP OF A FILE? 3.5.1 UNIX - chown ___________________ AIX 4 chown user:group file HP-UX chown user:group file SOLARIS chown user; chgrp group NOTES: 1. Using the command 'ls -l' will show both the owner and the group. 2. The command "chown user:group" is a short way to do the fol- lowing: chown user file chgrp group file 3.5.2 Intel - file ownership _____________________________ Intel operating systems do not have the concept of ownership for ordinary files. Windows 95 and NT do maintain separate config- uration files for each user login, but this is not a general purpose feature. 3.6 HOW TO EXPORT DIRECTORIES TO BE MOUNTED BY OTHER HOSTS? This section assumes that you are using TCP/IP and the NFS daemon to export your filesystems. For Intel platforms and AIX there is support for IBM OS/2 Warp Server and other traditional Intel "net use" facilities. 20 How to do tasks in OEM platforms 3.6.1 UNIX - exporting directories ___________________________________ 3.6.1.1 AIX - /etc/exports You can use the smit tool to specify the directories to be exported; this information is stored in /etc/exports: 1. Login as root. 2. Enter "smit" (GUI) or "smitty" (ASCII) 3. Select "Communications Applications and Services" 4. Select "NFS" 5. Select "Network File System" 6. Select "Add a Directory to exports lists" AIX also allows client access to IBM OS/2 Warp Server drivers through "net use", starting with AIX 4.1.4. 3.6.1.2 HP-UX You can use the sam tool to specify the directories to be exported; this information is stored in /etc/exports: 1. Login as root. 2. At the command prompt, enter "sam". 3. Double click on the Networking and Communications icon. 4. Double click on the Networked File Systems icon. 5. Double click on the Exported Local Filesystems icon. 6. From the menu bar, select Actions. Then select Add Exported File System. 7. In the Local Directory Name field, enter the absolute path name of the directory to export. Also select other options on the same screen as appropriate for your system. 8. Then click on the OK box. This will export your directory to the specified machines immediately. Administrative Tasks 21 3.6.1.3 Solaris The Solaris admintool does NOT provide a convenient method of updating /etc/dfs, so we have provided the manual process below: 1. Login as root. 2. Change directory to /etc/dfs. 3. Edit the file dfstab which is a file containing commands for sharing resources across a network. Append a share command to the end of this file. Use the man command to find out more information about the share command. Add a share command in the dfstab file. For example: share -F nfs -o rw=host -d "teamc client" /export/home/dir 4. Save and exit the file. 5. For the export to take effect immediately, execute the same share command on the command line. 3.6.2 Intel - Exporting directories or drives ______________________________________________ 3.6.2.1 OS/2 IBM TCP/IP provides an NFS daemon. Since this is a separate product from the operating system we will only cover this facility briefly. 1. Add export directories by updating the "exports" file in the directory pointed to by the ETC environment variable. 2. Restart TCP/IP with the "tcpstart" command. 3. Verify the new export with the "showexp SYSTEM_NAME" command. NOTE: We have found the "showexp" command to be unique to OS/2. It is very useful for checking NFS exports in a heterogeneous environment. 22 How to do tasks in OEM platforms 3.6.2.2 Windows NT, Windows 95 and Windows 3.1 The operating system does NOT support an NFS daemon (the process that manages an NFS export) in the operating system. The NFS server for this platform is provided by third-party vendors. Follow the instructions provided by the vendor. 3.7 HOW TO MOUNT DIRECTORIES EXPORTED BY A REMOTE HOST? 3.7.1 UNIX - mount command ___________________________ The best way to mount directories that are exported by a remote host is to use the system administration tool. If you have mounted directories as part of your normal system configuration, you can use the system administration tool and have the operating system mount the directories during bootup and initialization. Note that if your network is experiencing problems, your system may hang or take a long time to complete the bootup process. 3.7.1.1 Mounting directories using manual commands 1. Login as root. 2. Enter the following command: mount carcps21:/home/build /home/build | | | host remote directory local directory to be mounted 3.7.1.2 AIX mount AIX supports administering mounts through smit. AIX also supports "net use" for drives exported by OS/2 Warp Server. 3.7.2 Intel - mount command ____________________________ Administrative Tasks 23 3.7.2.1 OS/2: OS/2 mount syntax: mount carcps21:c&colon\home\build x: | | | | host remote remote directory local drive drive if to be mounted an Intel Server 3.7.2.2 Windows NT, Windows 95 and Windows 3.1 The operating system does NOT support an NFS client (the process that mounts an exported file system from a remote host) in the operating system. The NFS client for this platform is provided by third-party vendors. Follow the instructions provided by the vendor. 3.8 USING CD-ROMS CD-ROM is the only medium IBM provides for installing the com- plete TeamConnection package. The use of CD-ROM is well docu- mented in the TeamConnection Administration Guide. 3.8.1 AIX - CD-ROMS ____________________ Before you can use a CD-ROM in AIX, you have to mount the CD-ROM. Once the CD-ROM is mounted, then you can access it. 3.8.1.1 Mounting a CD-ROM in AIX 1. Insert the CD-ROM into the CD-ROM drive. 2. Log in as user root or do "su - root" to login as root and use the profile. 3. Create a directory for the CD-ROM /cdrom by entering "mkdir /cdrom". 4. Enter "smit" to add a CD-ROM file system. 24 How to do tasks in OEM platforms 5. Select "System Storage Management (Physical & Logical Storage)" 6. Select "File Systems" 7. Select "Add / Change / Show / Delete File Systems." 8. Select "CDROM File Systems" 9. Select "Add a CDROM File System" 10. Select a "Device name", such as "cd0". The CD-ROM file system device names must be unique. You may need to delete a previously defined CD-ROM file system if there is a conflict. 11. Type "/cdrom" for "Mount Point". 12. Select "OK" (or press enter if using the smit ASCII inter- face). 13. Return to the previous smit level, "System Storage Management (Physical & Logical Storage)" 14. Select "File Systems". 15. Select "Mount a File System". 16. Select "/dev/cd0" for "File System name". 17. Select "/cdrom" for "Directory over which to mount". 18. Select "cdrfs" for "Type of file system". 19. Select "yes" for "Mount as a READ-ONLY system.". 20. Select "OK" (or press enter if using the smit ASCII inter- face). 21. Exit smit. Now you are ready to install the appropriate TeamConnection com- ponents. Administrative Tasks 25 3.8.1.2 AIX - Installing TeamConnection from a CD-ROM using tar files To install the TeamConnection code from tar files using the CD-ROM in AIX, do the following: 1. You must have added and mounted a CD-ROM. 2. Log in with root authority. 3. Change the directory to /cdrom. 4. Run the installation script by typing: ./tcinst.ksh NOTE: The tcinst.ksh script can be copied to a directory not on the CD-ROM, then edited to customize your installation. 5. Follow the instructions in the installation script to install the TeamConnection components. 6. After the installation is complete, type the following com- mands to unmount the CD-ROM: cd .. umount /cdrom 7. Eject the CD. 3.8.2 HP-UX - Using CD-ROMs ____________________________ Before you can use a CD-ROM in HP-UX, you have to mount the CD-ROM. Once the CD-ROM is mounted, then you can access it. 3.8.2.1 HP-UX - Mounting a CD-ROM Do the following to add and mount a CD-ROM file system: 1. Insert the installation CD into the CD-ROM drive. 2. Log in as user ROOT or type su - root. 3. Issue the mount command to determine if the CD-ROM file system is mounted and operational. Verify that /CDROM is listed; if, not, then do the following: a. To create a directory for the CD-ROM, type mkdir /CDROM. 26 How to do tasks in OEM platforms b. Type: sam & c. Select Disks and File Systems. d. Select Disk Devices. e. Select the entry CDFS (for CD-ROM File System), then from the menu bar select "Actions" and choose the option "View more information". f. Click on the Show Device Files. Do not select raw devices such as /dev/rdsk/c0t2d0. g. Write down the value for Device File, such as /dev/dsk/c0t2d0 h. Close the View More Information window. i. Close the Disks and File Systems window. j. Exit sam. k. To mount the CD-ROM device file identified above, type: mount /dev/dsk/c0t2d0 /CDROM l. Issue the mount command again and verify that /CDROM is listed. 3.8.2.2 HP-UX - Installing TeamConnection code from CD-ROM To install the TeamConnection code from tar files from CD-ROM in HP-UX, do the following: 1. You must have added and mounted a CD-ROM. 2. Log in with root authority. 3. Change the directory to /CDROM. 4. Run the installation script by typing "./TCCDUTIL.KSH;1" (in uppercase and inside double quotes). This shell script will map the file names to lowercase and remove the ISO 9660 file name extensions in the temporary directory /tmp/tccdrom; then it will invoke the actual installation shell script (tcinst.ksh). NOTE: The tcinst.ksh script can be copied to a directory not on the CD-ROM, then edited to customize your installation. In HP-UX, the files on a CD are always shown in uppercase. Administrative Tasks 27 5. Follow the instructions in the installation script to install the TeamConnection components. 6. After the installation is complete, type the following com- mands: cd .. umount /CDROM 7. Eject the CD. 8. To cleanup the temporary directory "/tmp/tccdrom", type the following commands: cd / rm -fr /tmp/tccdrom 3.8.3 Solaris - Using CD-ROMs ______________________________ There is no need to mount the CD-ROM if Volume Management is running. Once you insert the CD-ROM into the drive, the oper- ating system mounts it for you. If Volume Management is not running, do the following to mount the CD-ROM: 1. Login as root. 2. Start the Volume Management daemon by executing the following command: /etc/init.d/volmgt start 3. Execute "ps -ef | grep vold". You should see the process "/usr/sbin/vold" started. 3.8.3.1 Solaris - Installing TeamConnection code from CD-ROM To install the TeamConnection code from tar files from CD-ROM in Solaris, do the following: 1. Insert the CD-ROM into the CD-ROM drive. The Solaris volume management automatically mounts the CD-ROM as /cdrom/teamc_20 (or similar) 2. Log in as root and type the following commands: cd /cdrom/teamc_20 ./tcinst.ksh 28 How to do tasks in OEM platforms NOTE: The tcinst.ksh script can be copied to a directory not on the CD-ROM, then edited to customize your installation. 3. Follow the instructions in the installation script to install the appropriate TeamConnection component. 4. After the installation is completed, type the following command: cd eject cdrom 3.8.4 Intel - CD-ROMs ______________________ In Intel operating systems, the CD-ROM drive is recognized by the operating system during boot and is treated as a read-only drive. 3.9 HOW TO SHUTDOWN AND REBOOT THE MACHINES? 3.9.1 UNIX - shutdown ______________________ 3.9.1.1 Miscellaneous notes before shutdown In order to efficiently shutdown a system, it is recommended that you follow these suggestions before you actually shutdown the system: 1. It is recommended to shutdown your system from a local session that does not use a windowing system (otherwise, the shutdown time will be longer because the windowing system has to be shutdown too). 2. If possible, unmount all the mounted NFS file systems. 3.9.1.2 Miscellaneous notes after reboot After the system has been rebooted, it is suggested that you should manually remount the necessary NFS file systems and if desired, start specific processes that may not be started auto- matically after reboot, such as the database server. Sometimes it is not convenient to automatically mount NFS file systems. For example, Host A and Host B are being rebooted at Administrative Tasks 29 the same time. If Host B NFS mounts directories from Host A, Host B will hang during bootup until Host A is completely ini- tialized and has its nfsd and mountd daemons running. Then Host B can NFS mount directories from Host A and complete its bootup. It is also convenient to startup processes only when they are needed, such as databases. This is advantageous when you know that the system is heavily used and when there is no need for some databases to be running all the time. In order to facilitate these tasks, you can, as root, create a shell script that will mount the necessary NFS file systems and start the desired processes. In our site we have the convention that this shell script is located in the root directory, it has file permissions for execute, it is named after the hostname and it has a suffix of ".mounts"; for example, in the host "oem-hp01", the shell script is called "/oem-hp01.mounts" and its contents is: 3.9.1.3 AIX - shutdown 1. Login as root. 2. Enter the following command to shutdown and reboot (quick restart): shutdown -Fr 3.9.1.4 HP-UX - shutdown 1. Login as root. 2. Enter the following command to shutdown and reboot: shutdown -r 3.9.1.5 Solaris - shutdown 1. Login as root. 2. Enter the following command to shutdown and reboot: shutdown -i6 30 How to do tasks in OEM platforms +--- ADD IT AND COPY IT INTO THE OTHER TR --------------------+ | | +-------------------------------------------------------------+ Figure 1. Sample shell script to manually mount NFS file systems 3.9.2 Intel - How to shutdown and reboot _________________________________________ 3.9.2.1 OS/2 - setboot The OS/2 "setboot /b" command will cause OS/2 to shutdown and reboot. You can also manually specify Shut Down from the desktop menu (point to the desktop and click right button). 3.9.2.2 Windows NT o You can manually select "Start" then "Shut Down" and then specify the desired level for shutdown and reboot. o You can use the utility "reboot" from the Windows NT Resource Kit. 3.9.2.3 Windows 95 You can manually select "Start" then "Shut Down" and then specify the desired level for shutdown and reboot. 3.9.2.4 Windows 3.1 You need to manually exit Windows and then reboot by doing a Ctrl-Alt-Del or power off then power on the system Administrative Tasks 31 3.10 UNIX: HOW TO IDENTIFY AND KILL SEMAPHORES AND FREE SHARED MEMORY? To cleanup the semaphores and shared memory used by one TeamConnection family, you can do one of the following: o Use the TeamConnection utility /usr/teamc/bin/stopteamc which also stops the TeamConnection daemons. o Perform the following manual procedure: 1. Login as root. 2. Enter the following command to show the semaphores: ipcs -s 3. Enter the following command to kill a semaphore: ipcrm -s xxx Where xxx is the semaphore id identified in the previous step. 4. Enter the following command to show the shared memory: ipcs -m 5. Enter the following command to kill the shared memory: ipcrm -m xxx Where xxx is the shared memory id identified in the pre- vious step. 3.11 TOPICS RELATED TO PRINTERS 3.11.1 HP-UX: How to setup a printer? ______________________________________ You can set up local or remote printer access using "sam". 1. At the command line prompt, enter 'sam'. 2. Select the 'Printers and Plotter' icon. 3. Select the 'Printers and Plotter' icon again. 4. From the 'Actions' pull down, select local, remote or network based printer access. 32 How to do tasks in OEM platforms 5. Complete and/or answer the screens that appear. Please also refer to your system documentation for further infor- mation on local, remote or network printer setup. 3.11.2 AIX: How to setup printer access? _________________________________________ You can use the "smit" or "smitty" tool to set up local or remote printer access. The steps below show how to set up remote printer access. Please refer to system documentation for local set up. 1. Type 'smitty' at a command line prompt. 2. At the System Management screen select 'Print Spooling'. 3. At the Print Spooling screen select 'Add a Print Queue'. 4. At the Add a Print Queue screen select 'remote'. 5. At the Type of Remote Printing screen select 'Standard Proc- essing'. 6. At this final screen, you will be asked to enter the fol- lowing information: o Name of QUEUE to a add o HOSTNAME of remote server o Name of QUEUE on remote server o TYPE of print spooler 7. Press enter and the new print queue will be added. 8. Exit smitty and verify the setup by attempting to print a small ascii text file using the lp command. Please also refer to your system documentation for further infor- mation on printer setup. 3.11.3 Solaris: How to setup printer access? _____________________________________________ There are 2 options: o You can set up local or remote printer access using the "admintool" in Solaris. 1. At the command line prompt, enter 'admintool'. Administrative Tasks 33 2. Select 'Browse', then 'printer' from the pull down menu. 3. On the 'Admintool: Printers' pull down menu, select 'Edit', then 'add' and then one of the following: - 'Access to Printer' for remote printer set up, or - 'Local Printer' for local printer setup. 4. Complete the information on the screen and select 'OK'. Please also refer to your system documentation for further information. o You can use the line commands below to setup a printer. 1. Ensure that the client is allowed to print on the host. 2. Do the following: lpsystem -t bsd server_name lpadmin -p new_name -s hostname!printer_name lpadmin -p new_name -T unkonwn # unless PS (PostScript) lpadmin -p new_name -I simple # unless above is PS 3. Change directory to /etc/lp/fd 4. Do the following: sh for f in download dpost postio postior postprint postreverse do lpfilter -f $f -F $f.fd done 5. Do the following: accept new_name enable new_name 3.12 MISCELLANEOUS TOPICS, BY PLATFORM 3.12.1 Solaris: How to fix problems with the /etc/vfstab file? _______________________________________________________________ If this file is corrupted, such as wrong parameters were used, then the system could hang when trying to mount or to perform fchk. To solve this problem, boot from the Solaris install disk. When the GUI is shown, mount the /etc file system; you must use the device name, such as: 34 How to do tasks in OEM platforms mount /dev/dsk/c0t1d0s0 /mnt Then you can correct the invalid entry. Administrative Tasks 35 36 How to do tasks in OEM platforms 4.0 DATABASE TASKS This section describes some common tasks that the administrator user of TeamConnection is likely to do with the database system. 4.1 ENVIRONMENT VARIABLES NEEDED BY THE USER ROOT 4.1.1 UNIX - database environment __________________________________ In UNIX, the ObjectStore database is started by root. The default installation process enables the operating system to start ObjectStore during startup. However, you need to make sure the root environment is set correctly. 4.1.1.1 AIX - root environment Log in as root and type the following statements in .profile: OS_ROOTDIR=/usr/lpp/ODI/OS4.0/cset export OS_ROOTDIR PATH=$PATH:$OS_ROOTDIR/bin:$OS_ROOTDIR/lib export PATH LIBPATH=$OS_ROOTDIR/lib export LIBPATH 4.1.1.2 HP-UX - root environment Log in as root and type the following statements in .profile: LANG=C export LANG OS_ROOTDIR=/usr/local/ODI/OS4.0 export OS_ROOTDIR PATH=$PATH:$OS_ROOTDIR/bin:$OS_ROOTDIR/lib export PATH SHLIB_PATH=$OS_ROOTDIR/lib export SHLIB_PATH Database Tasks 37 4.1.1.3 Solaris - root environment Log in as root and type the following statements in .profile: OS_ROOTDIR=/opt/ODI/OS4.0/sunpro export OS_ROOTDIR PATH=$PATH:$OS_ROOTDIR/bin:$OS_ROOTDIR/lib export PATH SHLIB_PATH=$OS_ROOTDIR/lib export SHLIB_PATH LD_LIBRARY_PATH=$OS_ROOTDIR/lib export LD_LIBRARY_PATH 4.1.2 Intel - database environment ___________________________________ For OS/2 and Windows NT, the environment settings needed by the database are set by the installation program. 4.2 WHERE IS THE OBJECTSTORE CODE LOCATED? The default location for the ObjectStore code is: AIX "/usr/lpp/ODI/OS4.0" HP-UX "/usr/local/ODI/OS4.0" SOLARIS "/opt/ODI/OS4.0" OS/2 "c:\teamc" WINDOWS 3.1 "c:\ProgramF\TeamConn" WINDOWS 95 AND NT ""c:\Program Files\TeamConnection"" 4.3 HOW TO FIND OUT THE VERSION OF OBJECTSTORE? To display the version of ObjectStore that is in use on the machine, type: osversion FAT name: osversio 38 How to do tasks in OEM platforms 4.4 HOW TO FIND OUT IF THE OBJECTSTORE SERVER IS RUNNING AND ACTIVE? 4.4.1 UNIX - ObjectStore server process status _______________________________________________ To verify if the ObjectStore server is active (osserver), do the following: 1. From a prompt, type: ps -ef | grep ' os' 2. Verify that there is a process for osserver. If you have a family already created, then it might be pos- sible that you see the process oscmgr4 (for the ObjectStore cache manager). 4.4.2 Intel - ObjectStore server process status ________________________________________________ The ObjectStore server only runs on the OS/2 and Windows NT Intel operating systems. 4.4.2.1 OS/2 - ObjectStore processes Unless you have "grep" for OS/2 you need to use the following: pstat | more 4.4.2.2 Windows NT - ObjectStore processes 1. Open Main Icon 2. Open Control Panel Icon 3. Open Services Icon 4. Scroll down to ObjectStore processes, then note if the status is "started" or "stopped". Database Tasks 39 4.4.3 How to determine if the ObjectStore server is running in a _________________________________________________________________ host? _____ To find out if the ObjectStore server is running on the specified host do: ossvrping µ-vº µhostNameº Where -v indicates that you want more information (Verbose mode). FAT name: ossvrpin 4.5 UNIX - HOW TO START THE OBJECTSTORE? 4.5.1 UNIX - How to start the ObjectStore server? __________________________________________________ You must have the proper ObjectStore environment variables defined in the .profile for root: 1. Login as root. 2. Enter the following command: osserver 4.5.2 UNIX - How to start the ObjectStore cache manager? _________________________________________________________ There is no need to explicitly start the ObjectStore cache manager, because it is started when the first TeamConnection daemon is activated. 4.6 INTEL - HOW TO START OBJECTSTORE? The ObjectStore server only runs in OS/2 and Windows NT. 40 How to do tasks in OEM platforms 4.6.1 OS/2 - Starting ObjectStore __________________________________ 1. Open "ObjectStore for OS/2" Icon 2. Select "ObjectStore Server" Icon or, use the "osserver" command. NOTE: The default installation copies the "ObjectStore Server" icon to the "Startup" folder. 4.6.2 Windows NT - Starting ObjectStore ________________________________________ 1. Open Control Panel Icon 2. Open Services Icon 3. Select and make active the ObjectStore processes or, use "net start osserver" NOTE: The default installation configures NT to autostart ObjectStore 4.7 HOW TO RESTART THE OBJECTSTORE SERVER AFTER A CRASH? It is recommended that after a crash of the ObjectStore server, it should be started and force the cleanup of the Server log file. Use with caution, though: osserver -i 4.8 UNIX - HOW TO STOP OBJECTSTORE? 4.8.1 UNIX - How to stop the ObjectStore server? _________________________________________________ You must have the proper ObjectStore environment variables defined in the .profile for root: 1. Login as root. 2. Enter the following command to shutdown the server: Database Tasks 41 ossvrshtd µ-fº hostName Where -f is to force an immediate shutdown. FAT name: ossvrsht 4.8.2 UNIX - How to stop the ObjectStore cache manager? ________________________________________________________ You must have the proper ObjectStore environment variables defined in the .profile for root: 1. Login as root. 2. Enter the following command to shutdown the cache manager: oscmshtd 4.9 INTEL - HOW TO STOP OBJECTSTORE? The ObjectStore server only runs in OS/2 and Windows NT. 4.9.1 OS/2 - Stopping ObjectStore __________________________________ 1. Open "ObjectStore Server" window 2. Enter -C to stop server process 3. Type "exit" to close window or, 1. Press Ctrl-Esc to show the window list, then select the entry for the ObjectStore server (osserver). Then with the right button, select the option to close it. 4.9.2 Windows NT - Stopping ObjectStore ________________________________________ 1. Open Control Panel Icon 2. Open Services Icon 3. Select and make inactive the ObjectStore processes or, use "net stop osserver" 42 How to do tasks in OEM platforms 4.10 HOW TO DISPLAY INFORMATION ABOUT THE OBJECTSTORE SERVER/CLIENT? The following utility displays settings for ObjectStore: o Server parameters o Server use meters o Information for each client connected to the Server running on the specified host. ossvrstat hostName µ-metersº µ-clientsº µ-parametersº µ-rusageº Where some options are: -meters Displays performance meters -clients Displays the state of each client connect to the server -parameters Displays server parameter values -rusage UNIX only: displays server process information FAT name: ossvrsta For more information, see the section "Maintaining the TeamConnection database", found in chapter 15 "Maintaining your TeamConnection environment", from the manual "TeamConnection Administrator's Guide". 4.11 HOW TO BACKUP AN OBJECTSTORE DATABASE? You can use the following utility to perform an online backup of the database: osbackup For more information, see the section "Maintaining the TeamConnection database", found in chapter 15 "Maintaining your TeamConnection environment", from the manual "TeamConnection Administrator's Guide". NOTE: If the TeamConnection family is not running, you can use the "oscp" command to copy the family database to another direc- tory. This can be part of a complete family backup using the oscp and cp commands. 4.12 HOW TO RESTORE A BACKED UP OBJECTSTORE DATABASE? You can use the following utility to restore a database that was backed up by using osbackup: Database Tasks 43 osrestore FAT name: osrestor For more information, see the section "Maintaining the TeamConnection database", found in chapter 15 "Maintaining your TeamConnection environment", from the manual "TeamConnection Administrator's Guide". 4.13 HOW TO COPY AN OBJECTSTORE DATABASE? You can use the following utility to create a copy of a database: oscp For more information, see the section "Maintaining the TeamConnection database", found in chapter 15 "Maintaining your TeamConnection environment", from the manual "TeamConnection Administrator's Guide". 4.14 HOW TO VERIFY THE VALIDITY OF THE POINTERS IN AN OBJECTSTORE DATABASE? You can use the following utility to validate that the pointers within a database are valid: osverifydb µoptionsº pathName FAT name: osverify For more information, see the section "Maintaining the TeamConnection database", chapter 15 "Maintaining your TeamConnection environment", from the manual "TeamConnection Administrator's Guide". 44 How to do tasks in OEM platforms APPENDIX A. BIBLIOGRAPHY A.1 TEAMCONNECTION 2 For more information on how to use TeamConnection, you can consult the following manuals and publications: SC34-4551 TeamConnection, Administrator's Guide SC34-4552 Getting Started with the TeamConnection Clients SC34-4499 TeamConnection, User's Guide SC34-4501 TeamConnection, Commands Reference SC34-4500 TeamConnection, Quick Commands Reference A.2 TEAMCONNECTION 1, USEFUL TO TEAMCONNECTION 2 USERS A few publications that have not been updated for TeamConnection 2.0 are still useful. SG24-4648 Introduction to the IBM Application Development Team Suite 83H9677 Staying on Track with TeamConnection Processes (Poster) A.3 RELATED TECHNICAL REPORTS The following technical reports describe in detail useful hints on using TeamConnection: 29.2147 SCLM Guide to TeamConnection Terminology 29.2196 Using REXX command files with TeamConnection MVS Build Scripts 29.2231 TeamConnection Interoperability with MVS and SCLM 29.2235 Using REXX command files with TeamConnection MVS Build Scripts for PL/I programs 29.2253 Comparison between CMVC 2.3 and TeamConnection 2 29.2254 Migrating from CMVC 2.3 to TeamConnection 2 29.2266 TeamConnection frequently asked questions: National Language Support (NLS) and Double-Byte Character Sets (DBCS) Appendix A. Bibliography 45 46 How to do tasks in OEM platforms APPENDIX B. COPYRIGHTS, TRADEMARKS AND SERVICE MARKS The following terms used in this technical report, are trademarks or service marks of the indicated companies: +---------------------+-------------------------------------------+ | TRADEMARK, | COMPANY | | REGISTERED | | | TRADEMARK OR | | | SERVICE MARK | | +---------------------+-------------------------------------------+ | IBM, AIX, | IBM Corporation | | OS/2, OS/2 Warp, | | | CMVC, TeamConnection| | | MVS. SCLM | | +---------------------+-------------------------------------------+ | UNIX | X/Open Co. Ltd. | +---------------------+-------------------------------------------+ | Sun, Solaris | Sun Microsystems Inc. | +---------------------+-------------------------------------------+ | HP, HP-UX | Hewlett-Packard Company | +---------------------+-------------------------------------------+ | Microsoft, Windows, | Microsoft Corporation | | Windows 95, | | | Windows NT | | +---------------------+-------------------------------------------+ | ObjectStore | Object Design, Inc. | +---------------------+-------------------------------------------+ | Intel | Intel Corporation | +---------------------+-------------------------------------------+ | Yahoo | Yahoo! Inc. | +---------------------+-------------------------------------------+ END OF DOCUMENT Appendix B. Copyrights, Trademarks and Service marks 47