You will find the information you need more quickly if you are familiar with:
This book describes:
SCO Doctor includes these Release and Installation Notes (also available online), as well as the following books:
This publication presents commands, filenames, keystrokes, and other special elements in these typefaces:
Exit program?yesb_b.errno
SCO Doctor is an automatic facility that relieves you of routine system management tasks, optimizes system performance, and protects you from unexpected and costly crises. Because accurate diagnosis is important to effective system management, SCO Doctor uses a powerful Inference Engine so SCO Doctor not only recognizes problems, but also diagnoses their causes before notifying you and taking corrective action.
The four principle elements of the SCO Doctor system are:
SCO Doctor for Networks, in addition to providing all of the functionality in SCO Doctor, also allows you to manage multiple remote systems from a centralized location, reducing the system management load of network administrators and support staff. SCO Doctor for Networks features include:
SCO Doctor Lite provides a subset of the functionality
available in SCO Doctor.
It offers system performance monitoring, screen printing,
alerting, and automatic system management for a single
UNIX server. It includes the SCO Doctor System
Management Knowledge Module, with up to 30 alert
routines for proactive management and a fixed set of
automatic action remedies. However, to obtain automatic diagnosis,
tips, and kernel tuning, and to extend
SCO Doctor to meet your requirements,
you need to use the unrestricted SCO Doctor product.
The following table compares the features of SCO Doctor Lite to those of SCO Doctor and SCO Doctor for Networks:
-------------------------------------------------------------- | SCO Doctor | SCO Doctor and | Benefit | | Lite Feature| SCO Doctor for | | | | Networks Feature| | |-------------|------------------|----------------------------| | An efficient| An efficient | Complete information on | | background | background data | the status and performance| | data | collection agent| of the system from a | | collection | | single, network-integrated| | agent | | package. Integrate local | | | | applications into | | | | management regimes with | | | | <1% CPU consumption. | |-------------|------------------|----------------------------| | Standard | Standard View | View any facet of a | | View Library| Library | system's performance as a | | | | table, graph, or time- | | | | line. | |-------------|------------------|----------------------------| | Live | Live and | Allows comparison of your | | monitoring | historical | system's current | | | monitoring | performance with past | | | | performance. | |-------------|------------------|----------------------------| | Print Screen| Print Screen and| Numerous reports available| | | Report Library | for distribution or | | | for live and | archiving. | | | historical data | | | | reporting | | |-------------|------------------|----------------------------| | Standard | Standard Alert | Easily add own alerts for | | Alert | Library with | proactive management of | | Library with| unlimited | any situation, as well as | | limited | expansion | incorporate alerts from | | support for | | other vendors. | | expansion | | | |-------------|------------------|----------------------------| | Standard | Standard Action | Automatic management if | | Action | Program Library | required, or ability to | | Program | with unlimited | add action programs if | | Library | expansion | management requirements | | | | change. | |-------------|------------------|----------------------------| | | Remote Software | Distribute software | | | Distribution | packages or files to | | | | remote systems. (SCO | | | | Doctor for Networks only) | |-------------|------------------|----------------------------| | | Kernel tuning | Intelligent automatic | | | | tuning of kernel | | | | parameters. | | | Pager and email | Whenever an urgent system | | | support for | problem is detected, | | | alerts | receive pager or email | | | | notification. | |-------------|------------------|----------------------------| | | SNMP browsing | Browse system data | | | and traps | collected by SCO Doctor | | | | from an SNMP console and | | | | receive SCO Doctor alerts | | | | as SNMP traps. (SCO | | | | Doctor for Networks only) | |-------------|------------------|----------------------------| | | Intelligent | Interprets management data| | | Diagnosis | and presents easy-to- | | | | understand language | | | | explanations. | |-------------|------------------|----------------------------| | | Intelligent Tips| Provides context-sensitive| | | | management and tuning tips| | | | as you need them. | |-------------|------------------|----------------------------| | | Multiple | Network management is | | | security modes | secure. | | | to control | | | | network- and | | | | user-level | | | | access | | |-------------|------------------|----------------------------| | Fixed | Open | Easily customize or extend| | architecture| architecture | SCO Doctor's data capture,| | | | alerting, views, or | | | | reports. | |-------------|------------------|----------------------------|
The SCO Doctor media provides the following products and patches (also called ``supplements''):
There are several issues of which you should be aware before installing SCO Doctor products and patches, including:
All SCO Doctor products work on the following SCO platforms:
---------------------------------------------------------------------------
Product Hardware requirements
---------------------------------------------------------------------------
SCO Doctor - a minimum of a 486/33Mhz, or a pentium-class computer
for Networks - a minimum of 12MB of RAM; 16MB are recommended
- 15MB of free disk space
- for modem communication, a minimum of 9600 baud
---------------------------------------------------------------------------
SCO Doctor - a 386, 486, or pentium-class computer
Lite or - a minimum of 8MB of RAM; 16MB are recommended
SCO Doctor - 5MB of free disk space
---------------------------------------------------------------------------
SCO Agent - a 386, 486, or pentium-class computer
for SCO - a minimum of 8MB of RAM
Doctor - 5MB of free disk space
- for modem communication, a minimum of 9600 baud
---------------------------------------------------------------------------
Before installing an SCO Doctor product, you may need to:
If you are using SCO OpenServer Release 5.0.0, you must install the enhanced version of the SCOadmin License Manager, (part of the SCO Advanced Server SCOadmin Supplement patch), before you can add client connection licenses for SCO Doctor.
It is recommended that you install this patch before installing any SCO Doctor product.
See also:
If you want to use SCO Doctor's SNMP functionality in a SCO Release 3 environment (SCO Open Desktop/Open Server Release 3.0 or SCO UNIX 3.2v4.2 or later), you must install the Support Level Supplement (SLS) NET382E.
The SLS NET382E is included on the SCO Doctor CD-ROM media as disk images, from which you can create a set of installation floppies. ``Installing the SLS NET382E patch'' describes how to do this, as well as how to install the SLS NET382E.
For complete information on the SLS NET382E,
you can get a copy of the SLS NET382E documentation
(called net382e.ltr.z)
from the SCO World Wide Web site, in the
``Support Level Supplements (SLS)'' area
of the ``Services'' page:
or
ftp://ftp.sco.com/SLS
See also:
If you are using NIS to distribute password, group, hosts, and services files to client systems, you have to manually create some entries for SCO Doctor products on the server system. Once created and propagated to all relevant client systems, you can install the SCO Doctor product on the server and client systems.
The SCO Doctor media contains SCO Doctor Lite, SCO Doctor, SCO Doctor for Networks, SCO Agent for SCO Doctor, and two patches that you may need to install for use with the SCO Doctor products.
Table 2-1 identifies the procedure to use to install the different SCO Doctor products and patches:
Table 2-1 SCO Doctor installation procedures
----------------------------------------------------------------------------
To install: See:
----------------------------------------------------------------------------
SCO Release 5 versions of: ``Installing on SCO OpenServer Release 5''
SCO Doctor Lite
or
SCO Doctor
or
SCO Doctor for Networks
or
SCO Agent
----------------------------------------------------------------------------
SCO Release 3 versions of: ``Installing on SCO Release 3 platforms''
SCO Doctor Lite
or
SCO Doctor
or
SCO Doctor for Networks
or
SCO Agent
----------------------------------------------------------------------------
SCO Advanced Server ``Installing the SCO Advanced Server
SCOadmin Supplement SCOadmin Supplement patch''
----------------------------------------------------------------------------
SLS NET382E ``Installing the SLS NET382E patch''
----------------------------------------------------------------------------
See also:
To install an SCO Doctor product on SCO OpenServer Release 5:
If you are installing SCO Doctor Lite or SCO Doctor, skip this step.
If you are installing SCO Doctor Lite or SCO Agent, skip this step.
An Installation Wizard is invoked when you first run doctor, to help guide you through the SCO Doctor configuration. You can press <Esc> or select cancel at any time if you want to exit the Wizard. You can return to the Wizard at any time to complete the configuration process by selecting Installation Wizard from the Help menu.
See also:
To install an SCO Doctor product on SCO Open Desktop/Open Server Release 3.0 or SCO UNIX 3.2v4.2 or later:
If you are installing SCO Doctor Lite or SCO Doctor, skip this step.
An Installation Wizard is invoked when you first run doctor to guide you through the SCO Doctor configuration. You can press <Esc> or select cancel at any time if you want to exit the Wizard. You can return to the Wizard at any time and complete the configuration process by selecting Installation Wizard from the Help menu.
If you are installing SCO Doctor Lite or SCO Agent, skip this step.
See also:
To create an installable floppy for the Release 3 SCO Agent for SCO Doctor:
Possible mount point values for <mnt_pt> include ``cdFS'' or ``cdrom''.
/dev/install is the default floppy drive on your system. If you want to use a different floppy drive, specify that device instead.
To apply the SCO Advanced Server SCOadmin Supplement patch on an SCO OpenServer Release 5.0.0 system:
See also:
To install SLS NET382E:
Possible mount point values for <mnt_pt> include ``cdFS'' or ``cdrom''.
/dev/install is the default floppy device on your system. If you want to use a different floppy drive, specify that device instead.
See also:
To upgrade from SCO Doctor Lite Release 2.0.0 to either the SCO Doctor or SCO Doctor for Networks Release 2.0.0 product, you must first purchase an SCO Certificate of License and Authenticity (COLA).
After that, simply install the desired SCO Doctor product, following the directions in ``Installing SCO Doctor products and patches''. You do not need to remove the Lite version first; it is automatically removed for you.
This section describes the procedures for adding client connection licenses on SCO Release 5 and Release 3 systems:
To add licenses for connections to SCO Doctor for Networks installed on SCO OpenServer Release 5:
To add licenses for connections to SCO Doctor for Networks installed on SCO Open Desktop/Open Server Release 3.0 or SCO UNIX 3.2v4.2 or later:
This section describes the procedures for removing SCO Doctor products and patches:
To remove an SCO Doctor product from SCO OpenServer Release 5:
If you remove the license after removing the product, you need to know the product's License Number because the product will be displayed as ``Unknown product''.
If you do not remove the license before re-installing an SCO Doctor product, the newly-installed product may fail to function properly until the old license is removed and then recreated on the system using the License Manager.
To remove an SCO Doctor product from SCO Open Desktop/Open Server Release 3.0 or SCO UNIX 3.2v4.2 or later:
To roll back any patch from an SCO OpenServer Release 5 system, including the SCO Advanced Server SCOadmin Supplement:
You must repeat this step for each software component that the patch has changed.
You can start SCO Doctor in one of the following ways:
All SCO Doctor commands are listed in pull-down menus.
The menu names are displayed in the menu bar on the second line
of the screen. One letter within each menu name and each
command is highlighted in red on a color monitor. If
you are using a monochrome monitor, menus and commands
are indicated in bold font.
Menu items not relevant or available to a particular operation are grayed out on the menu display.
There are menu options that are always grayed out if you are using SCO Doctor Lite, SCO Agent, and in some cases, SCO Doctor. Depending on the feature, these options are strictly available from both SCO Doctor and SCO Doctor for Networks, or from SCO Doctor for Networks only.
If you are running SCO Doctor on the system console or on a display running in scanmode, you can select menus using the <Alt> key. Otherwise, you can use <F10>, or <Ctrl>D if the function keys do not work.
or
These function keys provide quick access to some of SCO Doctor's commands and menus:
See the SCO Doctor User Guide for more information on using function keys and other aspects of the SCO Doctor user interface.
After installing an SCO Doctor product, the Installation
Wizard creates the godoctor user, but does not create
a password for the account. You must log in as root
and run the passwd command to create a password
for the godoctor account. A godoctor
password is required for
the Central Management Station (CMS) -- the system
where SCO Doctor for Networks is installed -- to connect to a
remote system over a modem.
The following limitations apply when using SCO Doctor for Networks:
To resolve this problem, use different names for the UUCP and TCP/IP configurations.
To use these options for the remote machine, you must do a remote login to the system (i.e., File --> Open --> Login from SCO Doctor) and run doctor from the command line. You can then use these Config options for the remote system.
You can also enter ``all'' or ``*'' to
specify all managed systems. Or, you can enter:
where <filename> is a file that contains a list of system names, with each system on its own line.
SCO Agent cannot run unless /unix is the booted kernel. If you discover that SCO Agent is not running and have trouble restarting it, check the /usr/spool/doctor/log/agent.log file for the following message:
SCO Agent cannot start as the linked kernel /unix does not appear to be thebooted kernel. As this program extracts data from the running kernel,
you will need to reboot the system before Agent can run.
Agent failed to start.
See the file /usr/spool/doctor/log/agent.log for details.
If you see this message, it is most likely that /unix is not the booted kernel. However, other possible problems may be:
When writing an action program using the
daction SCO Doctor TCL command, make sure that
D_DOCTOR is declared as ``global''
before daction is called.
To access the online documentation, you must run Doctor during an X server session and the DISPLAY environment variable must be set.
As root and using an ascii editor such as vi, open the appropriate file for editing:
or
Locate the </UL> html tag towards the end of the file. Open a line above this tag and enter the following lines, exactly as they are displayed here:
<LI> <A HREF=/drhome.html>SCO Doctor and SCO Doctor for Networks Documentation Set</A>
Save the changes to the file and then restart scohelp(XC). You can now access the English version of the SCO Doctor online documentation from either the French or German Documentation Library.
The SCO Doctor interface has a high graphical content. If
your terminal does not have graphics capability, it is necessary
to replace the graphic line drawing characters with the
following characters: (-), (+), and (|). To do this, type:
The SCO Doctor interface runs in color by default if you
have a color monitor, or in mono if you have a monochrome
monitor. If you need to use monochrome mode on a color
console, type:
If you have a PC scancode terminal and you want
to select menus through the <Alt> + (red letter) sequence,
in addition to the standard menu access options, type:
The SCO Doctor interface uses enhanced versions of the terminal terminfo descriptions. Terminfo descriptions control the display output and include ansi, wyse60, and xterm terminal types.
If you want to disable this option and only use the standard
terminfo descriptions, type:
© 1983 - 1996 The Santa Cruz Operation, Inc. All rights reserved.
No part of this publication may be reproduced, transmitted, stored in a retrieval system, nor translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without the prior written permission of the copyright owner or The Santa Cruz Operation, Inc., 400 Encinal Street, Santa Cruz, California, 95060, USA. Copyright infringement is a serious matter under the United States and foreign Copyright Laws.
Information in this document is subject to change without notice and does not represent a commitment on the part of The Santa Cruz Operation, Inc. or Go Ahead Software Inc.
SCO, the SCO logo, The Santa Cruz Operation, SCO OpenServer, SCO Open Server, UnixWare, Open Desktop, ODT, SCO OK, SCO Doctor, SCO Doctor for Networks, and SCO Doctor Lite are trademarks or registered trademarks of The Santa Cruz Operation, Inc. in the USA and other countries. Go Ahead is a registered trademark and Go Ahead Doctor, Doctor for Networks, and Go Ahead Agent are trademarks of Go Ahead Software Inc. UNIX is a registered trademark in the USA and other countries, licensed exclusively through X/Open Company Limited. All other brand and product names are or may be trademarks of, and are used to identify products or services of, their respective owners.
The SCO software that accompanies this publication is commercial computer software and, together with any related documentation, is subject to the restrictions on US Government use as set forth below. If this procurement is for a DOD agency, the following DFAR Restricted Rights Legend applies:
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of Rights in Technical Data and Computer Software Clause at DFARS 252.227-7013. Contractor/Manufacturer is The Santa Cruz Operation, Inc., 400 Encinal Street, Santa Cruz, CA 95060.
If this procurement is for a civilian government agency, this FAR Restricted Rights Legend applies:
RESTRICTED RIGHTS LEGEND: This computer software is submitted with restricted rights under Government Contract No. _________ (and Subcontract No. ________, if appropriate). It may not be used, reproduced, or disclosed by the Government except as provided in paragraph (g)(3)(i) of FAR Clause 52.227-14 alt III or as otherwise expressly stated in the contract. Contractor/Manufacturer is The Santa Cruz Operation, Inc., 400 Encinal Street, Santa Cruz, CA 95060.
The copyrighted software that accompanies this publication is licensed to the End User only for use in strict accordance with the End User License Agreement, which should be read carefully before commencing use of the software. This SCO software includes software that is protected by these copyrights and trademarks:
© 1994 - 1996 Go Ahead Software Inc. All rights reserved.
SCO, the SCO logo, The Santa Cruz Operation, SCO OpenServer, SCO Open Server, UnixWare, Open Desktop, ODT, SCO OK, SCO Doctor, SCO Doctor for Networks, and SCO Doctor Lite are trademarks or registered trademarks of The Santa Cruz Operation, Inc. in the USA and other countries. Go Ahead is a registered trademark and Go Ahead Doctor, Doctor for Networks, and Go Ahead Agent are trademarks of Go Ahead Software Inc. UNIX is a registered trademark in the USA and other countries, licensed exclusively through X/Open Company Limited. All other brand and product names are or may be trademarks of, and are used to identify products or services of, their respective owners.
Document Version: 2.0.0
29 April 1996