Tivoli/Plus for PSM User’s Guidepublib.boulder.ibm.com/tividd/td/PSM/PSM/en_US/PDF/PSM.pdf · Tivoli/Plus for PSM User’s Guide iii Preface The Tivoli/Plus for PSM User’s Guide

Tivoli/Plus for PSM User’s Guide

Version 1.0

February 1997

Tivoli/Plus for PSM User’s Guide (February 1997)Copyright NoticeCopyright © 1991, 1997 by Tivoli Systems, an IBM Company, including this documentation and allsoftware. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreementor Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication maybe reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computerlanguage, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, orotherwise, without prior written permission of Tivoli Systems. This document was prepared by TivoliSystems and was printed in the United States of America. The document is not intended for productionand is furnished “as is” without warranty of any kind. All warranties on this document are herebydisclaimed including the warranties of merchantability and fitness for a particular purpose.

Restricted Rights NoticeThe Software and its related documentation are provided with "Restricted Rights",unless the Government agrees to other terms. Use, duplication or disclosure by theGovernment is subject to the restrictions set forth in FAR clause 52.227-14 (AlternateIII) or FAR Clause 52.227-19. Unpublished--All Rights Reserved Under the Copy-right Laws of the United States. Manufacturer/Contractor is Tivoli Systems Inc., 9442Capital of Texas Highway, North, Arboretum Plaza One, Suite 500, Austin, Texas78759.

Trademarks

The following product names, denoted by an asterisk (*) at their first occurrence in this publication, aretrademarks of Tivoli Systems or IBM Corporation: AIX, TME 10, TME 10 Distributed Monitoring, TME10 Enterprise Console, TME 10 Framework, TME 10 Software Distribution, Tivoli Plus, and TivoliManagement Environment.

Other company, product, and service names mentioned in this document are trademarks or registeredtrademarks of their respective manufacturers. These company, product, and service names might bedenoted by a double asterisk (** ) at their first occurrence in this publication.

Tivoli/Plus for PSM User’s Guide i

Tivoli/Plus for PSMUser’s Guide

Preface................................................................................................................... iii

Who Should Read This Guide...................................................................... iii

Prerequisite and Related Documents............................................................ iv

What This Guide Contains ........................................................................... iv

Typeface Conventions................................................................................... v

Contacting Customer Support ....................................................................... v

Chapter 1—Getting Started with Tivoli/Plus for PSMInstallation Requirements ...................................................................................1-2

Software Requirements ..............................................................................1-2

Hardware Requirements .............................................................................1-2

Installing from the Desktop ................................................................................1-3

Installing from the Command Line...................................................................1-11

Tivoli/Plus Icons ...............................................................................................1-11

Tivoli/Plus Unique Features .............................................................................1-12

Starting a Tivoli/Plus Module...........................................................................1-13

Launching PSM Applications ...........................................................................1-18

Chapter 2—Software Distribution for PSMConfiguring TME 10 Software Distribution File Packages................................2-2

Installing PSM ..................................................................................................2-10

Installing PSM on All Platforms ..............................................................2-11

Installing PSM on a Single Platform........................................................2-13

Chapter 3—Resource MonitoringUsing Tivoli/Plus for PSM Monitors..................................................................3-2

Viewing the Status of Monitored Resources ......................................................3-5

Monitored Resources ..........................................................................................3-6

ii Version 1.0

Host Status ................................................................................................. 3-7

Spooler Daemon Status .............................................................................. 3-8

Supervisor Daemon Status ......................................................................... 3-9

psmd Daemon Status................................................................................ 3-10

PSM Server Information Directory: Percent Inodes Used....................... 3-11

DCE Directory: Percent of Space Used ................................................... 3-12

PSM Logfile Directory: Percent of Space Used ...................................... 3-13

Chapter 4—Enterprise Event ManagementConfiguration Activity........................................................................................ 4-2

Setting Up the TME 10 Enterprise Console ....................................................... 4-3

Creating a New Rule Base ......................................................................... 4-4

Adding an Existing Rule Base ................................................................... 4-5

Setting Up the Logfile Adapter for PSM............................................................ 4-6

Events and Rules................................................................................................. 4-7

PSM Events................................................................................................ 4-7

TME 10 Distributed Monitoring Events .................................................. 4-23

Event Correlation ..................................................................................... 4-28

Chapter 5—Tasks and Jobs for PSMTivoli/Plus for PSM Jobs.................................................................................... 5-2

Running a PSM Job and Saving the Output ....................................................... 5-6

Modifying a PSM Job......................................................................................... 5-9

Modifying for All Future Executions of the Job........................................ 5-9

Modifying for a Single Execution of the Job ........................................... 5-11

Preface

Tivoli/Plus for PSM User’s Guide iii

PrefaceTheTivoli/Plus for PSM User’s Guide describes specific features andprocedures for using the Tivoli/Plus* for PSM module. This modulewas jointly developed by Tivoli Systems and the IBM Corporation,and provides an integration of the Printing Systems Manager (PSM)print administration and management product with the TME 10*

(Tivoli Management Environment* 10). Through this integration, theTivoli/Plus for PSM module delivers the system managementcapabilities of TME 10 for specific use with PSM. Using Tivoli/Plusfor PSM, the PSM application can be managed across a multi-platformnetwork.

Tivoli/Plus provides different modules for integrating differentproduction control applications with TME 10. Since all Tivoli/Plusmodules have a common interface, a system administrator canimplement the system management capabilities of TME 10 withvarious production control applications while enjoying the simplicityof a common interface. The addition of TME 10 SoftwareDistribution*, TME 10 Distributed Monitoring*, and the TME 10Enterprise Console* provides additional management capabilities inthe areas of client installation, resource monitoring, and eventcorrelation.

Who Should Read This GuideThis guide is for system administrators who use the Tivoli/Plus forPSM module to manage the operation of the PSM print administrationand management product. Readers of this guide should be familiarwith TME 10, the PSM application, and concepts such as directories,

Note: This release of Tivoli/Plus for PSM marks the introductionof this product to the TME 10 product line. As products joinTME 10, the product names are changing. See theTivoli/Plus for PSM Release Notes for a list of old and newproduct names.

All references to “Sentry” in this guide refer to TME 10Distributed Monitoring or its components.

Preface

iv Version 1.0

files, and symbolic links. Readers of this guide should also be familiarwith the operating systems running on the machines on which they willbe using the Tivoli/Plus module, TME 10, and the PSM application.

Prerequisite and Related DocumentsThe information in theTivoli/Plus for PSM User’s Guidecomplementsinformation presented in theTME 10 Framework User’s Guideand theTivoli/Plus User’s Guide. You must be familiar with TME 10Framework* and Tivoli/Plus before you can effectively use a specificTivoli/Plus module. You should be familiar with the documentation forthese products before attempting to use the information in theTivoli/Plus for PSM User’s Guide. Additionally, you should befamiliar with the documentation for the PSM application.

What This Guide ContainsTheTivoli/Plus for PSM User’s Guidecontains the following chapters:

■ Chapter 1, “Getting Started with Tivoli/Plus for PSM”Contains the installation requirements and procedures forinstalling Tivoli/Plus for PSM. This chapter also containsinformation about Tivoli/Plus icons, features unique toTivoli/Plus, and launching the PSM application.

■ Chapter 2, “Software Distribution for PSM”Describes how to set up the prewritten TME 10 SoftwareDistribution file packages to be used with Tivoli/Plus for PSMfor distributing and installing the PSM application across anetwork.

■ Chapter 3, “Resource Monitoring”Describes how TME 10 Distributed Monitoring may be usedwith Tivoli/Plus for PSM to monitor PSM resources in order todetect and prevent system problems.

■ Chapter 4, “Enterprise Event Management”Describes how to set up the TME 10 Enterprise Console to beused with Tivoli/Plus for PSM to provide event management.This chapter also contains a description of the events and rulesspecific to Tivoli/Plus for PSM.

Preface

Tivoli/Plus for PSM User’s Guide v

■ Chapter 5, “Tasks and Jobs for PSM”Describes how to customize and run PSM jobs with Tivoli/Plusfor PSM.

Typeface ConventionsThis guide uses several typeface conventions for special terms andactions. These conventions have the following meaning:

Bold Commands, keywords, file names, or otherinformation that you must use literally appear inbold.Names of windows, dialogs, and other controls alsoappear inbold.

Italics Variables and values that you must provide appear initalics.

Bold Italics New terms appear in bold italics the first time they areused.

Monospace Code examples appear in amonospace font.

This guide may include icons in the left margin. These icons providecontext for the discussion in the text or for performing a step within aprocedure. For example, if you start a procedure by double-clicking ona task icon, that icon appears in the left margin next to the first step. Ifthe fourth step of the procedure instructs you to open another icon, thaticon appears in the left margin next to the fourth step.

Contacting Customer SupportWe are very interested in hearing from you about your experience withthe products in TME 10. We welcome your suggestions forimprovements.

If you encounter difficulties with any TME 10 product, please contactyour customer support representative. To assist you, the TME 10Framework includes thewsupport command. This command promptsyou for problem information, which can be e-mailed to your supportprovider or saved to a text file. You can then print the saved file, andfax the resulting TME 10 Problem Report form to your supportprovider. See theTME 10 Framework Reference Manual for additionalinformation about thewsupport command.

Preface

vi Version 1.0

If you have comments or suggestions about the TME 10documentation, please send e-mail to [email protected].

Tivoli/Plus for PSM User’s Guide 1–1

Getting S

tarted with

Tivoli/P

lus for PS

M

1Getting Started with Tivoli/Plusfor PSM

The Tivoli/Plus for PSM module provides an integration of TME 10(Tivoli Management Environment 10) with the PSM printadministration and management product. This integration allowscentralized distribution and management of the PSM applicationacross a multi-platform network. This module provides the followingfeatures for managing the PSM application:

■ Icons for launching the PSM application

■ Subscription lists for clients, hosts, and servers

■ File packages for TME 10 Software Distribution

■ Monitors for TME 10 Distributed Monitoring

■ TME 10 Enterprise Console events and rule sets customized forPSM

■ PSM-specific tasks and jobs

Note: The TME 10 Software Distribution, TME 10 DistributedMonitoring, and TME 10 Enterprise Console applicationsmust be installed and configured before their correspondingTivoli/Plus feature is operational.

1

Installation Requirements

1–2 Version 1.0

Installation RequirementsBefore attempting to install Tivoli/Plus for PSM on the TME 10Framework, make certain you review the requirements in this section.

The following table provides the context and authorization rolerequired to install Tivoli/Plus for PSM.

■ The Tivoli/Plus for PSM module must be installed on the TMR(Tivoli Managed Region) server first. Then, in order to have fullfunctionality, the Tivoli/Plus for PSM module must be installedon the following machines. These machines must be managednodes.

■ The TME 10 Enterprise Console server (if there is one)

■ The PSM servers

Software RequirementsThe PSM application should be installed before the Tivoli/Plus forPSM module is installed.

Note: For information about current TME 10 Frameworkrequirements, refer to the release notes.

Tivoli/Plus for PSM has features that use TME 10 SoftwareDistribution, TME 10 Distributed Monitoring, and the TME 10Enterprise Console. If these applications are not installed, the specificfeature requiring these applications will not work. However, theTivoli/Plus for PSM installation allows you to incrementally re-installthose features if you buy the missing products at a later date.

Hardware RequirementsThe following table provides the client and server disk spacerequirements for Tivoli/Plus for PSM. This space is in addition to the

Activity Context Required Role

Installing Tivoli/Plus forPSM

TME 10 install_product

Installing from the Desktop


Getting S

tarted with

Tivoli/P

lus for PS

M

space requirements for TME 10, the TME 10 Framework, and the PSMapplication.

Tivoli/Plus for PSM is installed on the TMR server, the TME 10Enterprise Console server (if you have the TME 10 EnterpriseConsole), and the PSM nodes. The space requirements are the same forall of these machines. The Tivoli/Plus for PSM module usesplatform-independent shell and Perl scripts, which is why themodule’s requirements do not differ from platform to platform.

† Not Appreciable

Installing from the DesktopUse the following steps to install Tivoli/Plus for PSM from the TME10 desktop.

Note: The installation windows may contain aLicense Key field.Because Tivoli/Plus modules no longer require a license keyfor installation, you can ignore theLicense Key field.

Platform Libraries Binaries Database Man PagesMessageCatalogs

AIX * 0 MB 500 KB † 0 0 MB 50 KB


1–4 Version 1.0

1. Select theInstall -> Install Product... option from theDesktopmenu

to display theInstall Product window.



Getting S

tarted with

Tivoli/P

lus for PS

M

If the Tivoli/Plus for PSM module is listed in theSelect Productto Install scrolling list, skip to step 3. If it is not listed, proceedto step 2.


1–6 Version 1.0

2. Press theSelect Media... button to display theFile Browserwindow.

TheFile Browser window enables you to identify or specify thepath to the installation media.

If you already know the path to the CD-ROM image

a. Enter the full path in thePath Name field.

b. Press theSet Path button to change to the specified directory.

c. Press theSet Media & Close button to save the new mediapath and return to theInstall Product window. The windownow contains a list of products that are available forinstallation.



Getting S

tarted with

Tivoli/P

lus for PS

M

If you do not know the exact path to the CD-ROM image

a. From theHosts scrolling list, choose the host on which theinstallation media is mounted. Choosing a host updates theDirectories scrolling list to show the directories of the hostyou chose.

b. From theDirectories scrolling list, choose the directorycontaining the installation media.

c. Press theSet Media & Close button to save the new mediapath and return to theInstall Product window. The windownow contains a list of products that are available forinstallation.

3. Select the Tivoli/Plus for PSM module from theSelect Productto Install list.

4. To specify the clients on which the module will be installed, usethe left and right arrow keys to move machine names between the


1–8 Version 1.0

Clients to Install On scrolling list and theAvailable Clientsscrolling list.

By default, all machines in the current TMR (Tivoli ManagedRegion) are listed in theClients to Install On list. To move amachine name to theAvailable Clients list, choose one or moreclients from theClients to Install On list and press the rightarrow button. The chosen clients are moved from theClients toInstall On list to theAvailable Clients list.

5. Press theInstall & Close button to install the module and closethe Install Product window.

— OR —

Press theInstall button to install the module and keep theInstallProduct window open. You can then install Tivoli/Plus for PSMon another set of clients or you can install another product.



Getting S

tarted with

Tivoli/P

lus for PS

M

The installation process prompts you with aProduct Installwindow similar to the following example:

This window provides the list of operations that take place wheninstalling the software. This window also warns you of anyproblems that you may want to correct before you install theTivoli/Plus for PSM module.

6. Press theContinue Install button to begin the installationprocess.

—OR—

Press theCancelbutton to abort the installation process.


1–10 Version 1.0

When the installation is complete, the Product Install windowdisplays a completion message similar to the following example:

7. Press theClosebutton when theProduct Install status windowindicates that the installation is complete.

Completionmessage

Installing from the Command Line


Getting S

tarted with

Tivoli/P

lus for PS

M

Installing from the Command LineUse thewinstall command to install the Tivoli/Plus for PSM module.The following example is the syntax for thewinstall command and itsparameters:

Note: Thewinstall command has a-l license_key option forspecifying a product’s license key. Because Tivoli/Plusmodules no longer require a license key for installation, youdo not need to use the-l license_key option when installing aTivoli/Plus module with thewinstall command.

winstall -c cdrom_path -s installation_server \-i index_file

where:

-c cdrom_path Specifies the path to the CD-ROM image.

-s installation_serverSpecifies the server on which the product is to beinstalled.

-i index_file Specifies the index file from which the product is to beinstalled (PSM.IND).

See thewinstall command in theTME 10 Framework ReferenceManual for more information.

Tivoli/Plus IconsAlthough the Tivoli/Plus icons look like (traditional) TME 10 icons,their functionality has been altered slightly to provide a faster, moreintuitive approach to navigating and deploying the module’s features.In some cases, like a TME 10 Software Distribution file package,menu items have been removed from the icon’s pop-up menu to createa more “point and click” environment.

The Tivoli/Plus icons can be activated in either of two ways:

■ Opening or executing the icon by double-clicking on it with theleft mouse button. In many cases, double-clicking executes anactivity (such as a task) without opening another window.

Tivoli/Plus Unique Features

1–12 Version 1.0

■ Displaying the icon’s pull-down menu by pressing and holdingthe right mouse button.

Generally, either method may be used to access a particular function.There are cases, however, where a particular function can only beaccessed by one of these methods.

The following icon represents the Tivoli/Plus for PSM resources:

To prevent confusion between traditional TME 10 and Tivoli/Plus forPSM functionality, each Tivoli/Plus icon has been overlaid with theTivoli/Plus symbol to highlight its special functionality as shown inthe following example.

Tivoli/Plus Unique FeaturesTivoli/Plus modules use the termprofile manager in a somewhatdifferent way than do the other TME 10 products. In a Tivoli/Plusmodule, a profile manager’s primary function is as asubscription list.A subscription list identifies the machines that tasks and jobs run onwhen executed. Subscription lists can contain machine names or otherprofile managers. Adding a profile manager to a subscription list issimply a way of subscribing several machines at once rather thanadding each one individually.

TheTivoli/Plus User’s Guide describes the function of profilemanagers in the Tivoli/Plus modules in more detail. For moreinformation, see the section on subscribers and targets in theTivoli/Plus User’s Guide.

Starting a Tivoli/Plus Module


Getting S

tarted with

Tivoli/P

lus for PS

M

Starting a Tivoli/Plus ModuleAll Tivoli/Plus modules are kept in a collection under theTivoliPlusicon on the TME 10 desktop.The module’s icon is added to thiscollection after installation. The following icon represents theTivoli/Plus collection:

Use the following steps to see the modules included in your Tivoli/Pluscollection:


1–14 Version 1.0

1. From the main TME 10 desktop, double-click on theTivoliPlusicon or select theOpen... option from theTivoliPlus icon’spop-up menu

to display theTivoliPlus window.



Getting S

tarted with

Tivoli/P

lus for PS

M

TheTivoliPlus window displays an icon for each Tivoli/Plusmodule installed. In the case above, five modules have beeninstalled.


1–16 Version 1.0

2. Double-click on theTivoliPlus for PSM icon or select theOpen... option from the icon’s pop-up menu

to display the icons representing the tasks and other tools formanaging the PSM product.



Getting S

tarted with

Tivoli/P

lus for PS

M

Launching PSM Applications

1–18 Version 1.0

Launching PSM ApplicationsWhen Tivoli/Plus for PSM is installed on a PSM host, the installationprocess creates an icon for launching the PSM service application fromwithin TME 10.

Each PSM server node has its own PSM icon for launching the PSMapplication from that site. For example, the following icon appears fora server named “adara”:

The PSM application has five logical entry points: thePSM Servers,PSM Spooler, PSM Supervisor, PSM Queue Job, andPSM QueuePrinter windows. The logical entry point is preconfigured and appearson the pop-up menu for each PSM@host icon.

For example, selecting thePSM Servers Windowoption from thepop-up menu displays theService Name window, which then displaysthePSM Serversmain window. Similarly, selecting any of the otheroptions opens their corresponding windows.



Getting S

tarted with

Tivoli/P

lus for PS

M


1–20 Version 1.0


Softw

are Distribution forP

SM

2Software Distribution for PSM

Tivoli/Plus for PSM includes six hierarchical, prewritten TME 10Software Distribution file packages for distributing and installing thePSM applications on hosts. Much of the configuration activitynormally associated with a TME 10 Software Distribution file packagehas been done for you. Using Tivoli/Plus for PSM and TME 10Software Distribution, you can distribute the PSM Spooler Server,PSM Supervisor Server, PSM Client, PSM GUI and PSM PTF’s acrossa multi-platform network.

Installing PSM software is a two-stage process. First, you set up thePSM installation by configuring a TME 10 Software Distribution filepackage for each type of platform on which you are installing PSM.For example, if you are installing PSM on both a Solaris and a Sunplatform, you need to configure a TME 10 Software Distribution filepackage twice, once for each platform.

Second, you distribute the configured file packages by running theappropriatePSM Installation task. This task installs PSM on theselected subscribers for each platform for which you have configureda TME 10 Software Distribution file package. You can distribute PSMto all configured platforms or choose to distribute to only a singleplatform.

2

Configuring TME 10 Software Distribution File Packages

2–2 Version 1.0

Configuring TME 10 Software Distribution FilePackages

When configuring a TME 10 Software Distribution file package to beused with Tivoli/Plus for PSM, you need to establish the location of thePSM installation directory so that TME 10 Software Distribution canlocate the installation binaries and files when installing PSM.

Tivoli/Plus for PSM has a different setup icon for each PSMapplication, which configures a file package for installing the PSMapplication. Once configured, the TME 10 Software Distribution filepackages are installed with a corresponding installation icon (see“Installing PSM” on page 2-10.)

Function Icon

Configures a TME 10 SoftwareDistribution file package fordistributing and installing the PSMSpooler Server, PSM SupervisorServer, and PSM Clientapplications.

Configures a TME 10 SoftwareDistribution file package fordistributing and installing the PTF’sfor the PSM base products.

Configures a TME 10 SoftwareDistribution file package fordistributing and installing the PSMGUI application.

Configures a TME 10 SoftwareDistribution file package fordistributing and installing the PTF’sfor the PSM GUI application.



Softw


SM

Use the following steps to configure a TME 10 Software Distributionfile package. The steps for completing the setup window are similar foreach PSM application. The PSM GUI application has its own setupwindow, therefore you do not need to choose the product to install asyou do in theSetup PSM Installation window. You need to completea setup window for each platform on which you wish to install aparticular PSM application.

Configures a TME 10 SoftwareDistribution file package fordistributing and installing the PSMClient application for OS2.

Configures a TME 10 SoftwareDistribution file package fordistributing and installing the PSMClient application for Windows.

Function Icon


2–4 Version 1.0

1. Select theRun job... option from the setup PSM icon of yourchoice to display the setup window. This window allows you toconfigure the installation parameters.

Note: The following illustration shows theSetup PSMInstallation window.

2. In theDistribution Options block, select the type of operatingsystem on which you will be running PSM from theTarget

The first two blocks ofthis window arecommon to all non-PCsetup windows.

The last block does notappear on the Setup PSMGUI Installation or theSetup PSM GUI PTFInstallation windows.



Softw


SM

Installation Architecture pop-up menu. If the operating systemis not listed, select theDon’t check option.

The architecture type is used during distribution as a validitycheck of the target nodes. For example, if a file package isconfigured for theaix4-r1 platform and an attempt is made todistribute the software to asunos4 target host, this architecturecheck will prevent the mismatched installation from occurring.The distribution will then continue on the remaining valid hosts.

Note: If theDon’t check option is selected, the architecture validitycheck described previously is bypassed. In this case, it isextremely important to manually verify the target subscriptionlist before distributing the file package, as no architecturechecks will be performed to prevent distributing the softwareimage to an incorrect platform. (See page 2-11 for informationabout manually verifying the subscription list.)

3. In theSource Information block, choose whether the PSMinstallation files will be taken from a staging area directory (theStaging Area button) or from a tape device (theTape button).Clicking on either button displays additional fields.

If you are installing from a staging area, continue with step 4 onpage 2-6. If you are installing from a tape device, continue withstep 5 on page 2-7.


2–6 Version 1.0

4. If you are installing from a staging area:

a. In theManaged Node Name field, enter the name of theTMR server or the managed node where the PSM installpimage is located.

b. In theExisting Staging Directory field, enter the name ofthe source directory where the PSM installp image is located.Continue with step 6.

c. In theImage Name (installp)field, enter the name of thepreviously created installp image.



Softw


SM

5. If you are installing from a tape device:

a. In theManaged Node Name field, enter the name of theTMR server or the managed node where the tape device islocated.

b. In theFull Path to Tape Devicefield, enter the full path nameto the tape device.

c. In theImage Name (installp)field, enter the name of theinstallp image you want to create.

d. In the 25 Mb Temp Directory field, enter the path to thedirectory in which the files will be unpacked beforedistribution. The directory will be created on the nodespecified in theManaged Node Name field.

Note: After you have installed PSM from a tape device,you can use the temporary directory as the source ofthe PSM image name for subsequent installations. Todo this, select theStaging Areabutton and then enterthe path to the temporary directory in theExistingStaging Directory field and the image name in theImage Name (installp)field.


2–8 Version 1.0

e. If you are running theSetup PSM Server Installation task,the following information is also needed. This information iscontained in thePSM Target Destination Informationblockof theSetup PSM Server Installation window.

6. In theProduct(s) to Install block, choose the product(s) youwould like to install. You can choose any combination ofproducts from this section.

Note: TheProduct(s) to Install block does not appear on theSetup PSM GUI Installation or the Setup PSM GUIPTF Installation windows.

7. Select theSet And Execute button to set all the information youhave entered.

If you are running theSetup PSM OS2/Windows Installationtask,the installation window is different than the previous installation tasks.



Softw


SM

Use the following steps to complete this window:

1. In theManaged Node Name field, enter the name of the TMRserver or the managed node where the PSM client binary files arelocated.

2. In thePath to PSM Staging Directory field, enter the full pathto the source directory where the PSM client binaries are located.

3. In thePSM Installation Directory on Client field, enter the fullpath of the destination directory. This is the directory where thePSM client binary files will be put on the destination machine.

4. Select theSet And Execute button to set all the information youhave entered.

Installing PSM

2–10 Version 1.0

Installing PSMAfter you have configured a TME 10 Software Distribution filepackage for each platform on which you wish to install PSM, you areready to install PSM on these platforms. You can distribute PSM to allplatforms for which you have configured a TME 10 SoftwareDistribution file package or to a single platform. Tivoli/Plus for PSMperforms pre-installation checks, such as verifying available diskspace and memory. Output for each platform is sent to the sourcemachine in the following files:

/tmp/psm_install_log. platform_name

/tmp/os2_client_install

/tmp/win_client_install

whereplatform_name refers to the operating system on whichPSM was installed. If the installation succeeds or fails, an event is sentto the TME 10 Enterprise Console.

You use an installation icon to distribute and install PSM. If you wishto view the TME 10 Software Distribution file packages that you havecreated, select theOpen... option from the installation icon’s pop-upmenu.

Installing PSM


Softw


SM

Installing PSM on All PlatformsUse the following steps to install PSM on all platforms for which youhave configured a TME 10 Software Distribution file package.

Note: If you selectedDon’t Check in step 2 on page 2-4, then it isimportant to manually verify the target subscription list foreach file package to prevent distributing the software to anincorrect platform. This manual verification procedure isdescribed in steps 1 through 3 on page 2-13. When you havecompleted the verification steps for each file package, closetheDistribute/Install PSM window and continue with step 3on page 2-12 of the following procedure.

1. Select theSubscribers... option from the installation icon’spop-up menu to display the Subscribers window.

Installing PSM

2–12 Version 1.0

2. Specify the subscription lists to which you want to install PSMby using the left and right arrow buttons to move the desired listsinto theCurrent Subscribers field. When finished, press theSetSubscriptions & Close button.

3. Select theDistribute... option from thePSM Installation icon’spop-up menu. Selecting this option installs PSM on the machineslisted on the subscription lists that you chose.

Installing PSM


Softw


SM

Installing PSM on a Single PlatformIf you want to install PSM on only one type of platform, you candistribute only the TME 10 Software Distribution file package thatapplies to that platform.

Use the following steps to install PSM on a single platform:

1. Select theOpen... option from the installation icon’s pop-upmenu to display the Distribute/Install PSM window.

2. Select theSubscribers... option from the pop-up menu of theicon representing the file package for the platform on which youwish to install PSM.

3. In the Subscribers window, specify the subscription lists to whichyou want to install PSM on a single platform by using the left andright arrow buttons to move the desired lists into theCurrent

Installing PSM

2–14 Version 1.0

Subscribers field. When finished, press theSet Subscriptions &Close button.

4. Select theDistribute... option from the file package icon’spop-up menu. Selecting this option installs PSM onto the clientmachines listed on the subscription lists that you chose.


Resource M

onitoring

3Resource Monitoring

Tivoli/Plus for PSM provides the ability to monitor critical resourceswith TME 10 Distributed Monitoring. The monitors for TME 10Distributed Monitoring are predefined to enable you to managedifferent aspects of the operating system, such as processes, availableinodes, directory free space, or the PSM hosts, that are crucial to thecontinued availability of the PSM application. These monitors allowyou to quickly identify and respond to potential problems so thatsystem downtime is avoided.

3

Using Tivoli/Plus for PSM Monitors

3–2 Version 1.0

Using Tivoli/Plus for PSM MonitorsTivoli/Plus for PSM comes with five types of monitors:PSM SpoolerServer, PSM Supervisor Server, PSM Server, PSM Host, andPSMNode Connectivity.

Function Icon

This monitor checks the status of the PSMSpooler Server daemon.

This monitor checks the status of the PSMSupervisor Server daemon.

These monitors check the status of several PSMserver-related file systems, such as percent ofinodes used and percent of disk space used.

This monitor checks the status of the PSMdaemon, psmd, that runs on all of the PSM hostmachines.

These monitors check the status of the hosts onwhich the PSM servers are running. Thesemonitors run on the TME 10 ALI.



Resource M

onitoring

Before the Tivoli/Plus for PSM monitors are operational, they must bedistributed to their subscription lists. To distribute a monitor, simplyselect theDistribute... option from the monitor’s pop-up menu andthen click on theDistribute Now button.

The exception is thePSM Node Connectivity Monitors, which youdo not need to distribute. Every time you install Tivoli/Plus for PSMon a new machine, the new host receives a node connectivity monitor.These monitors, which check to see if the host is up or down, run onthe TMR server.

The other monitors are distributed to their default subscription lists.ThePSM Spooler Server Monitors are distributed to thePSMSpooler Server List. ThePSM Supervisor Server Monitors aredistributed to thePSM Supervisor Server List. ThePSM Server


3–4 Version 1.0

Monitors are distributed to thePSM Server List. ThePSM HostMonitors are distributed to thePSM Host List.

To modify the default subscription list of a particular monitor, selecttheSubscribers... option from the monitor’s pop-up menu.

Although the Tivoli/Plus for PSM server monitors come alreadydefined to monitor resources specific to PSM, you can add monitorsfrom the TME 10 Distributed Monitoring collection or delete monitorsas you wish. You can also edit existing monitors to perform differentactions under different conditions.

Selecting the options on a PSM monitor’s pop-up menu displays theusual TME 10 Distributed Monitoring windows. Refer to the TME 10Distributed Monitoring documentation for more detailed informationon using these windows.

Displays functions for adding, deleting,and editing monitors.

Displays the function for distributingmonitors to those managed nodes(machines) and profiles included on themonitor’s subscription list.

Displays the subscription list thatspecifies to which machine the monitoris distributed. You can modify this list.

Viewing the Status of Monitored Resources


Resource M

onitoring

Viewing the Status of Monitored ResourcesUse thePSM Sentry Indicators icon to view the status of themonitored resources

.

The thermometer on thePSM Sentry Indicators icon rises as thestatus of a monitored resource becomes more urgent. In the example,thePSM Host Monitors has received a “critical” status from one of itsmonitored resources.

Open thePSM Host Monitors icon to view the status of the PSMresources on remote machines. For each monitored resource, themonitor only reports the most urgent status received within a recenttime frame. The monitor reports are organized so that the most urgentstatus level appears at the top of the report.

For more information on viewing the status of a monitored resource,refer to the TME 10 Distributed Monitoring documentation.

Monitored Resources

3–6 Version 1.0

Monitored ResourcesThe following table indicates the network resources that Tivoli/Plusfor PSM monitors.

Monitored ResourceDescribedon Page

Monitor Icon

Host status page 3-7

spooler daemon page 3-8

supervisor daemon page 3-9

psmd daemon page 3-10

Percent of inodes used in thePSM information directory(/var/psm).

page 3-11

Percent of space used in theDCE directory.

page 3-12

Percent of space used in thePSM logfile directory.

page 3-13

Monitored Resources


Resource M

onitoring

Host StatusThe host status monitor checks whether the status of a host is up ordown. This monitor checks the status of any host or other resource onthe network that can respond to aping request. This monitor checksspecifically to see whether the targeted hosts are up or down.

This monitor checks the host status every 15 minutes.

The following table lists the preconfigured actions for this monitor:

Monitors that are defined with this monitor use status operators toevaluate data. To display a list of the available operators, refer to theTME 10 Distributed Monitoring documentation for more informationon displaying the available operators.

For information on viewing a monitor’s status report, see “Viewing theStatus of Monitored Resources” on page 3-5.

Severity Trigger When Default Actions

Critical Becomes unavailable Send event to the TME 10Enterprise Console.Change icon.

Severe Never N/A

Warning Never N/A

Reset Becomes available Send event to the TME 10Enterprise Console.

Normal N/A N/A

Always N/A N/A

Monitored Resources

3–8 Version 1.0

Spooler Daemon StatusThespooler daemon status monitor checks whether all instances of thespoolerserver daemon are up and running.

This monitor runs every minute.





Severe N/A N/A

Warning N/A N/A

Reset Becomes available Send event.

Normal N/A N/A

Always N/A N/A

Monitored Resources


Resource M

onitoring

Supervisor Daemon StatusThesupervisor daemon status monitor checks whether all instances ofthesupervisorserver daemon are up and running.






Severe N/A N/A

Warning N/A N/A


Normal N/A N/A

Always N/A N/A

Monitored Resources

3–10 Version 1.0

psmd Daemon StatusThepsmddaemon status monitor checks whether thepsmd serverdaemon is up and running.






Severe N/A N/A

Warning N/A N/A


Normal N/A N/A

Always N/A N/A

Monitored Resources


Resource M

onitoring

PSM Server Information Directory: Percent Inodes UsedThe PSM information directory (/var/psm) monitor checks thepercentage of used inodes in the PSM server information directory.

This monitor runs every 30 minutes.




Critical Increases beyond 95%. Send event to the TME 10Enterprise Console.Change icon.

Severe Increases beyond 90%. Send Event.Change Icon.

Warning Increases beyond 80%. Send Event.Change Icon.

Reset Decreases below 80% Send Event.

Normal N/A N/A

Always N/A N/A

Monitored Resources

3–12 Version 1.0

DCE Directory: Percent of Space UsedThe DCE directory monitor checks the percentage of disk space usedin the DCE directory.






Severe Increases beyond 85%. Send event.Change icon.

Warning Increases beyond 75%. Send event.Change icon.

Reset Decreases below 75%. Send event.

Normal N/A N/A

Always N/A N/A

Monitored Resources


Resource M

onitoring

PSM Logfile Directory: Percent of Space UsedThe PSM logfile directory monitor checks the percentage of disk spaceused in the PSM logfile directory.






Severe Increases beyond 90%. Send event.Change icon.

Warning Increases beyond 80%. Send event.Change icon.

Reset Decreases below 80%. Send event.

Normal N/A N/A

Always N/A N/A

Monitored Resources

3–14 Version 1.0


Enterprise E

ventM

anagement

4Enterprise Event Management

With the TME 10 Enterprise Console, Tivoli/Plus for PSM provides aset of filters for identifying events and a set of predefined correlationrules to automate the task of responding to specific events. An event isany significant change in the state of system resources or anapplication. In the case of Tivoli/Plus for PSM, an event is a change ina monitored resource that affects PSM or the system on which PSM isrunning. Examples of events are the starting and stopping of a process,or a host becoming unavailable. Event management provides apredefined or automated response to specific events, so that potentialproblems are identified and responded to before causing system downtime. For example, if a process fails, the TME 10 Enterprise Consolecan automatically rerun the process. The TME 10 Enterprise Consolecan also notify the system administrator of repeated process failuresthat may indicate a more severe problem with an application or thenetwork. For some events, there is no automated response except to bedisplayed in the TME 10 Enterprise Console.

4

Configuration Activity

4–2 Version 1.0

Configuration ActivityThe following section describes the configuration activity that occurswhen setting up the TME 10 Enterprise Console to be used withTivoli/Plus for PSM. This activity takes place on the TME 10Enterprise Console and PSM servers. Tivoli/Plus for PSM performsmost of the setup activity automatically.

■ TME 10 Enterprise Console Server

The TME 10 Enterprise Console server is set up to

• Recognize and accept PSM events.

• Respond to PSM events according to the predefined rules.

• Notify the system administrator of the events received andthe action taken.

■ PSM Servers

On the nodes where PSM servers will be running

• PSM is configured to send events to the TME 10 EnterpriseConsole.

• The logfile adapter is configured to recognize and forwardPSM events to the TME 10 Enterprise Console.

Setting Up the TME 10 Enterprise Console


Enterprise E

ventM

anagement

Setting Up the TME 10 Enterprise ConsoleUse the procedures in this section to set up the TME 10 EnterpriseConsole to receive Tivoli/Plus for PSM events.

To set up the TME 10 Enterprise Console, select theRun job... optionof theSetup EventServer for PSM icon’s pop-up menu. This actiondisplays theSetup EventServer for PSM window.

Once you have displayed theSetup EventServer for PSM window,there are two options for setting up the TME 10 Enterprise Console:creating a new rule base or adding the Tivoli/Plus for PSM specificrules to an existing rule base.


4–4 Version 1.0

Creating a New Rule BaseUse the following steps to set up the TME 10 Enterprise Console bycreating a new rule base.

1. Select theCreate New Rule Basebutton. This action displaysadditional fields.

2. Enter the name of the rule base you want to create in theNewRule Base Name field.

Note: It is not advisable to modify theDefault rule base, so donot enterDefault in theNew Rule Base Name field.

3. New rule bases are created by copying (cloning) and modifyingan existing rule. Enter the name of the rule base to be copied intheRule Base to Clonefield.

4. Specify the path name to the directory on the TME 10 EnterpriseConsole server in which you want to create the new rule base inthePath For New Rule Basefield.

Note: The current user for the TME 10 administrator must havewrite access to the directory that you specify in this field.

5. (Optional) Use theName For Event Console to Configurefieldto display PSM related events on a particular systemadministrator’s event console. To make this assignment, enter the



Enterprise E

ventM

anagement

name that appears under the desired system administrator’s eventconsole icon.

6. Press theSet And Executebutton when finished.

Adding an Existing Rule BaseUse the following steps to set up the TME 10 Enterprise Console byadding the Tivoli/Plus for PSM specific rules to an existing rule base.

1. Select theAdd To Existing Rule Base button. This actiondisplays theExisting Rule Base Name field.

2. Enter the name of an existing rule base that you want to modifyto contain the PSM event classes and rules in theExisting RuleBase Name field.

3. (Optional) Use theName For Event Console to Configurefieldto display PSM related events on a particular systemadministrator’s event console. To make this assignment, enter thename that appears under the desired system administrator’s eventconsole icon.

4. Press theSet And Executebutton when finished.

Setting Up the Logfile Adapter for PSM

4–6 Version 1.0

Setting Up the Logfile Adapter for PSMSetting up the TME 10 Enterprise Console logfile adapter for PSMrequires configuring the TME 10 Enterprise Console logfile adapter toread the PSM log files and send events to the TME 10 EnterpriseConsole.

Note: The logfile adapter must be restarted after completing thisprocedure in order for the logfile adapter to send PSM eventsto the TME 10 Enterprise Console. This happensautomatically.

To set up the TME 10 Enterprise Console logfile adapter for PSM:

Select theRun Job... option from theConfigure PSM LogFileAdapter icon’s pop-up menu. The logfile adapter will beautomatically configured to monitor all of the PSM log files located inthe PSM logfile directory (this directory is determined by looking atthe PDBASE variable in the/etc/environment file).

Events and Rules


Enterprise E

ventM

anagement

Events and RulesTivoli/Plus for PSM configures the TME 10 Enterprise Console toreceive events from PSM logfiles and TME 10 Distributed Monitoring.The TME 10 Enterprise Console classifies the events and then matchesthem against the rule base to see if the event has a predefined rule(automated response).

The following tables describe the Tivoli/Plus for PSM events andrules. The tables are organized according to the message that the TME10 Enterprise Console sends to the system administrator for each PSMevent. The percent sign (%s) in the messages indicate a variable. Thedefinition for each variable follows the message.

Note: The automated action checks if a deliverable address called“Psmadmin” exists and sends e-mail to that address. If theaddress is not deliverable, the default action sends e-mail to“root”.

PSM EventsThe following table contains the PSM events sent to the TME 10Enterprise Console.

PSM Events

5010-234 Job %s(%s:%s) is close to being discarded.

Event Description:

Event Class:

Event Severity:

Job about to be deleted.

Psm_close_to_discard_time

WARNING

5010-292 Document %s (%s) in job %s (%s:%s) was aborted by theprinter.

Event Description:

Event Class:

Event Severity:

Printer deleted document.

Psm_doc_aborted_by_printer

MINOR

Events and Rules

4–8 Version 1.0

5010-206 Document %s (%s) in print job %s (%s:%s) was aborted bythe server.

Event Description:

Event Class:

Event Severity:

Server aborted document.

Psm_doc_aborted_by_server

MINOR

5010-204 Job %s (%s:%s) stopped printing due to job or printererrors.

Event Description:

Event Class:

Event Severity:

Server aborted job because printer errorsoccurred.

Psm_ job_aborted_by_server

MINOR

5010-196 Job %s (%s:%s) was cancelled by the operator oradministrator.

Event Description:

Event Class:

Event Severity:

Operator or administrator deleted job.

Psm_ job_cancelled_by_operator

WARNING

5010-303 The job %s (%s:%s) cannot be scheduled to a printer.

Event Description:

Event Class:

Event Severity:

Printer not available to support this job.

Psm_job_cannot_be_scheduled

MINOR

5010-209 The final document indication for job %s (%s:%s) was notreceived by the server within the server’s job-submission-timerinterval. Job processing will continue.

Event Description:

Event Class:

Event Severity:

Server timed out waiting for documents.

Psm_job_submission_not_complete

MINOR

PSM Events

Events and Rules


Enterprise E

ventM

anagement

5010-321 Job %s (%s:%s) is now in the timed-out state.

Event Description:

Event Class:

Event Severity:

Spooler can’t obtain information about job.

Psm_job_timed_out

CRITICAL.

5010-570 The job submitted to logical printer %s in server %s containsno print file documents. Submit a job with at least one print filedocument.

Event Description:

Event Class:

Event Severity:

Job contained no documents.

Psm_no_document

CRITICAL

5010-213 Job %s (%s:%s) was discarded before it printed.

Event Description:

Event Class:

Event Severity:

Job discarded due to time out.

Psm_job_discarded

WARNING

5010-107 Printer %s needs operator attention.

Event Description:

Event Class:

Event Severity:

Automated Action:

Printer needs operator attention.

Psm_printer_needs_operator

CRITICAL

E-mail user Psmadmin (or root).

5010-304 The queue %s:%s is backlogged.

Event Description:

Event Class:

Event Severity:

Automated Action:

Queue has too many jobs.

Psm_queue_backlogged.

CRITICAL


PSM Events

Events and Rules

4–10 Version 1.0

5010-299 The queue %s:%s is no longer backlogged.

Event Description:

Event Class:

Event Severity:

Queue is no longer backlogged.

Psm_queue_no_longer_backlogged

HARMLESS

5010-306 The printer %s:%s needs administrator attention.

Event Description:

Event Class:

Event Severity:

Automated Action:

Printer needs attention from the administrator.

Psm_printer_needs_attention

MINOR


5010-294 Successfully started %s:%s.

Event Description:

Event Class:

Event Severity:

This server is started.

Psm_server_startup

HARMLESS

5010-337 Starting the shutdown request for server %s.

Event Description:

Event Class:

Event Severity:

Server processing the request.

Psm_server_shutdown_started

HARMLESS

5010-338 The shutdown request for server %s is complete.

Event Description:

Event Class:

Event Severity:

Server completed processing request.

Psm_server_shutdown_complete

HARMLESS

5010-215 An internal error was detected in server %s.

Event Description:

Event Class:

Event Severity:

Automated Action:

A server error occurred.

Psm_internal_server_error

FATAL


PSM Events

Events and Rules


Enterprise E

ventM

anagement

5010-224 Successfully created object %s %s:%s.

Event Description:

Event Class:

Event Severity:

The object was created.

Psm_created_object

HARMLESS

5010-225 Successfully deleted object %s %s:%s.

Event Description:

Event Class:

Event Severity:

The object was deleted.

Psm_deleted_object

HARMLESS

5010-241 Successfully modified object %s %s:%s.

Event Description:

Event Class:

Event Severity:

The object was modified.

Psm_modified_object

HARMLESS

5010-242 Successfully paused %s %s:%s.

Event Description:

Event Class:

Event Severity:

Printer or queue is paused

Psm_paused_object

WARNING

5010-227 Successfully resumed %s %s:%s.

Event Description:

Event Class:

Event Severity:

Printer or queue was resumed.

Psm_resume_object

WARNING

5010-240 Successfully disabled printer %s:%s.

Event Description:

Event Class:

Event Severity:

Logical or physical printer disabled.

Psm_disable_printer

WARNING

PSM Events

Events and Rules

4–12 Version 1.0

5010-226 Successfully enabled printer %s:%s.

Event Description:

Event Class:

Event Severity:

Logical or physical printer enabled.

Psm_enable_printer

WARNING

5010-525 Physical printer %s successfully registered with the spooler.

Event Description:

Event Class:

Event Severity:

Printer registered with spooler.

Psm_registered_printer

HARMLESS

5010-237 Printer %s:%s was shut down after job %s (%s:%s) startedprocessing.

Event Description:

Event Class:

Event Severity:

Printer shutdown after job started processing.

Psm_printer_shutdown

HARMLESS

5010-243 Printer %s:%s is no longer registered with %s:%s.

Event Description:

Event Class:

Event Severity:

Printer no longer registered with spooler.

Psm_unregistered_printer

HARMLESS

5010-013 Cannot restore object %s in the print database.

Event Description:

Event Class:

Event Severity:

Error occurred while restoring object.

Psm_cannot_restore_object

CRITICAL

5010-014 Cannot save an object.

Event Description:

Event Class:

Event Severity:

Error occurred while trying to save object.

Psm_cannot_save_object

CRITICAL

PSM Events

Events and Rules


Enterprise E

ventM

anagement

5010-017 Cannot free an exclusive lock in %s at line %s.

Event Description:

Event Class:

Event Severity:

Error occurred while trying to free lock.

Psm_cannot_free_lock

CRITICAL

5010-019 Cannot save directory entry in %s.

Event Description:

Event Class:

Event Severity:

Error occurred while trying to save directoryentry.

Psm_cannot_save_directory

CRITICAL

5010-026 Cannot obtain a usage lock in %s at line %s. Use your localproblem-reporting procedure to report this message.

Event Description:

Event Class:

Event Severity:

Error occurred while trying to use object.

Psm_cannot_obtain_lock

CRITICAL

5010-029 The object check out usage value is not valid in file %s atline %s.

Event Description:

Event Class:

Event Severity:

Object usage value not valid.

Psm_check_out_value_not_valid

CRITICAL

5010-030 Not enough memory to create a new object. Performingmemory clean-up.

Event Description:

Event Class:

Event Severity:

Insufficient memory to create new object.

Psm_not_enough_memory

MINOR

PSM Events

Events and Rules

4–14 Version 1.0

5010-041 Memory failure. Return code = %s.

Event Description:

Event Class:

Event Severity:

Server has run out of memory.

Psm_memory_failure

CRITICAL

5010-069 An internal error occurred in module %s at line %s.

Event Description:

Event Class:

Event Severity:

A severe error has occurred.

Psm_internal_error

CRITICAL

5010-070 An out-of-memory error occurred in module %s at line %s.

Event Description:

Event Class:

Event Severity:

A severe error has occurred.

Psm_out_of_memory

CRITICAL

5010-083 A system error occurred while trying to process this request.Use your local problem-reporting procedure to report this message.

Event Description:

Event Class:

Event Severity:

System error prevented server from processingthis request.

Psm_system_error_occured

CRITICAL

5010-119 The server %s exceeded its resource allocations. Use yourlocal problem-reporting procedure to report this message.

Event Description:

Event Class:

Event Severity:

Server has exceeded it’s resource allocations.

Psm_server_exceeded_resource

CRITICAL

PSM Events

Events and Rules


Enterprise E

ventM

anagement

5010-120 A server error occurred.

Event Description:

Event Class:

Event Severity:

Error occurred during server processing.

Psm_server_error

CRITICAL

5010-137 A DCE error occurred during %s. Use your localproblem-reporting procedure to report this message.

Event Description:

Event Class:

Event Severity:

Error occurred in DCE.

Psm_dce_error

MINOR

5010-156 Cannot obtain an exclusive lock. Use your localproblem-reporting procedure to report this message.

Event Description:

Event Class:

Event Severity:

A severe system error has occurred.

Psm_cannot_obtain_excl_lock

CRITICAL

5010-157 Cannot free an exclusive lock. Use your localproblem-reporting procedure to report this message.

Event Description:

Event Class:

Event Severity:

A severe system error has occurred.

Psm_cannot_free_excl_lock

CRITICAL

5010-169 Cannot create a new process at this time. Fork returnvalue = %s.

Event Description:

Event Class:

Event Severity:

Error occurred while trying to fork new process.

Psm_cannot_create_new_process

MINOR

PSM Events

Events and Rules

4–16 Version 1.0

5010-289 The supervisor timed out waiting to receive document %s ofjob %s. The job is added to the queue to be scheduled again.

Event Description:

Event Class:

Event Severity:

Supervisor timed out waiting for job.

Psm_supervisor_timed_out

MINOR

5010-309 A server thread cannot register with the logging service.

Event Description:

Event Class:

Event Severity:

Server thread can’t register with logging.

Psm_server_thread_cannot_register

MINOR

5010-312 Cannot restore local job IDs.

Event Description:

Event Class:

Event Severity:

PSM daemon can’t open job id file.

Psm_cannot_restore_job_ids

MINOR

5010-313 The PSM daemon shut down due to signal %s.

Event Description:

Event Class:

Event Severity:

Daemon shutdown in response to signal.

Psm_daemon_shut_down

MINOR

5010-317 Cannot initialize device support system registration table.

Event Description:

Event Class:

Event Severity:

Cannot initial device support registration table.

Psm_cannot_initialize_support_syst

CRITICAL

5010-395 The program %s has been interrupted by the signal %s (%s).

Event Description:

Event Class:

Event Severity:

Program received signal.

Psm_program_interrupted

MINOR

PSM Events

Events and Rules


Enterprise E

ventM

anagement

5010-414 Cannot communicate with a DCE server.

Event Description:

Event Class:

Event Severity:

Can’t communicate with DCE server.

Psm_cannot_communicate_dce_server

MINOR

5010-420 Cannot open a status file for the PSF backend.

Event Description:

Event Class:

Event Severity:

Can not open status file.

Psm_cannot_open_status_file

MINOR

5010-433 The server has been interrupted by the signal %s (%s).

Event Description:

Event Class:

Event Severity:

Server has received a signal.

Psm_server_intr_by_signal

MINOR

5010-506 Cannot shut down %s within the allotted time.

Event Description:

Event Class:

Event Severity:

Server did not shut down in allotted time.

Psm_cannot_shutdown_object

MINOR

5010-511 Memory error %s occurred while processing a previousmemory error.

Event Description:

Event Class:

Event Severity:

Memory error occurred.

Psm_mem_error_occured

CRITICAL

5010-513 Deadlock error. %s is trying to wait on %s which is waitingon %s. The server stopped processing.

Event Description:

Event Class:

Event Severity:

Deadlock condition detected.

Psm_deadlock_error

CRITICAL

PSM Events

Events and Rules

4–18 Version 1.0

5010-514 Deadlock error. %s is trying to wait on %s which is waiting on%s which is waiting on %s. The server stopped processing.

Event Description:

Event Class:

Event Severity:

Deadlock condition detected.

Psm_deadlock_error_bigger

CRITICAL

5010-517 PSM detected a memory problem. Returned report code %s.

Event Description:

Event Class:

Event Severity:

PSM detected a memory problem.

Psm_memory_problem_detected

CRITICAL

5010-518 Memory error. PSM attempted to delete storage with invalidmemory mark.

Event Description:

Event Class:

Event Severity:

PSM detected an internal memory error.

Psm_memory_error_del_storage

CRITICAL

5010-519 Memory error. PSM attempted to delete storage with a sizeless than 0.

Event Description:

Event Class:

Event Severity:

PSM detected an internal memory error.

Psm_memory_error_del_storage_lt_zero

CRITICAL

5010-526 Physical printer %s cannot register with the spooler.

Event Description:

Event Class:

Event Severity:

Printer could not register with spooler.

Psm_printer_cannot_register

MINOR

PSM Events

Events and Rules


Enterprise E

ventM

anagement

5010-610 The error log file is full. New log information will be written tothe display.

Event Description:

Event Class:

Event Severity:

Log file has seeded it’s specified size.

Psm_log_file_full

MINOR

5010-631 System function returned error number %s.

Event Description:

Event Class:

Event Severity:

Call made to system function returned error.

Psm_syst_function_ret_error

MINOR

5010-636 The return code %s from a system command is not valid.

Event Description:

Event Class:

Event Severity:

Server could not read return code.

Psm_syst_command_ret_code_invalid

MINOR

5010-637 Cannot communicate with the PSM daemon at %s to removethe temporary document file %s.

Event Description:

Event Class:

Event Severity:

Spooler could not communicate with psmd.

Psm_cannot_communicate_with_daemon

MINOR

5010-642 PSM detected a memory shortage.

Event Description:

Event Class:

Event Severity:

PSM detected memory shortage.

Psm_memory_shortage_detected

MINOR

PSM Events

Events and Rules

4–20 Version 1.0

5010-649 The process is unable to renew its DCE login identity.ThePSM process is shutting down.

Event Description:

Event Class:

Event Severity:

Error occurred trying to renew DCE identity.

Psm_proc_unable_renew_dce_identity

MINOR

5010-657 Previous ACL information not found. PSM re-creating ACLsfor server %s.

Event Description:

Event Class:

Event Severity:

ACL information being recreated.

Psm_prev_acel_info_not_found

MINOR

5010-293 Document %s (%s) in job %s (%s:%s) was cancelled at theprinter.

Event Description:

Event Class:

Event Severity:

The document was cancelled at the printer.

Psm_doc_cancelled_at_printer

MINOR

5010-217 %s %s encountered an error.

Event Description:

Event Class:

Event Severity:

Error occurred that can not be described.

Psm_encountered_error

MINOR

5010-236 %s %s has encountered a warning condition.

Event Description:

Event Class:

Event Severity:

Warning occurred that can not be described.

Psm_encountered_warning

WARNING

PSM Events

Events and Rules


Enterprise E

ventM

anagement

5010-307 The printer %s:%s requires a function that is not available.

Event Description:

Event Class:

Event Severity:

Printer requires function that is unavailable.

Psm_printer_function_unavailable

MINOR

5010-223 Printer %s:%s registered with %s:%s.

Event Description:

Event Class:

Event Severity:

Physical printer registered with spooler.

Psm_printer_registered

HARMLESS

5010-247 Physical printer %s:%s has timed out.

Event Description:

Event Class:

Event Severity:

Printer did not connect with printer device.

Psm_printer_timed_out

MINOR

5010-238 Resource %s on printer %s:%s needs attention.

Event Description:

Event Class:

Event Severity:

Resource needs attention from a person.

Psm_resource_needs_attention

MINOR

5010-239 Resource %s on printer %s:%s needs operator attention.

Event Description:

Event Class:

Event Severity:

This resource needs attention from an operator.

Psm_resource_needs_operator

MINOR

5010-437 The printer %s:%s cannot register with the queue %s.

Event Description:

Event Class:

Event Severity:

Printer could not register with the queue

Psm_unable_to_register

WARNING

PSM Events

Events and Rules

4–22 Version 1.0

5010-214 Resource %s that is required for job %s (%s:%s) is notknown to the server.

Event Description:

Event Class:

Event Severity:

Resource required for job not known.

Psm_unrecognized_resource

MINOR

PSM Events

Events and Rules


Enterprise E

ventM

anagement

TME 10 Distributed Monitoring EventsThe following table describes the events and rules that TME 10Distributed Monitoring may use when monitoring PSM resources. Thetable is organized according to the monitor that sends the event to theTME 10 Enterprise Console.

TME 10 Distributed Monitoring Events

Daemon Status

“PSM daemon psmd has failed.”

Event Description:

Event Class:

Event Severity:

Correlation Activity

psmd becomes unavailable.

Sentry2_0_daemon

CRITICAL

If twice in 8 hours send e-mail to userPsmadmin (or root).

“PSM daemon spooler has failed”

Event Description:

Event Class:

Event Severity:

Correlation Activity:

spooler becomes available.

Sentry2_0_daemon

CRITICAL


“PSM daemon supervisor has failed.”

Event Description:

Event Class:

Event Severity:


supervisor becomes unavailable.

Sentry2_0_daemon

CRITICAL


Events and Rules

4–24 Version 1.0

PSM Server Information Directory: Percent of Inodes Used

PSM %s File System has used %s percent of the available inodes.(filesystem name, percent of inodes used)

Event Description:

Event Class:

Event Severity:


The percentage of inodes used in the PSMServer Information directory (/var/psm)increases beyond 95%.

Sentry2_0_inodesusedpct

CRITICAL



Event Description:

Event Class:

Event Severity:



SEVERE

PSM %s File System has used %s percent of the available inodes.(filesystem name, percent of inodes used

Event Description:

Event Class:

Event Severity:



WARNING


Events and Rules


Enterprise E

ventM

anagement


Event Description:

Event Class:

Event Severity:


The percentage of inodes used in the PSMServer Information directory (/var/psm)decreases below 80%.


HARMLESS

Close related PSM_LogFilesystemSize eventsand auto-acknowledge this event.

DCE Directory: Percent of Space Used

PSM %s File System has used %s percent of the available space.(filesystem name, percent of space used)

Event Description:

Event Class:

Event Severity:


The percentage of space used in the DCEincreases beyond 92%.

Sentry2_0_diskusedpct

CRITICAL



Event Description:

Event Class:

Event Severity:



SEVERE


Events and Rules

4–26 Version 1.0


Event Description:

Event Class:

Event Severity:



WARNING


Event Description:

Event Class:

Event Severity:


The percentage of space used in the DCEdecreases below 75%.


HARMLESS


PSM Logfile Directory: Percent of Space Used


Event Description:

Event Class:

Event Severity:


The percentage of space used in the PSMlogfile directory increases beyond 95%.


CRITICAL



Events and Rules


Enterprise E

ventM

anagement


Event Description:

Event Class:

Event Severity:



SEVERE


Event Description:

Event Class:

Event Severity:



WARNING


Event Description:

Event Class:

Event Severity:


The percentage of space used in the PSMlogfile directory decreases below 80%.


HARMLESS



Events and Rules

4–28 Version 1.0

Event CorrelationThe TME 10 Enterprise Console also provides event correlation formultiple events. If a number of separate events are related to eachother, a predefined rule correlates the events and triggers a response.

The following table describes the event correlation rules and relatedactions provided by Tivoli/Plus for PSM. For example, if thepsmddaemon fails twice in 8 hours, a “Repeated psmd failure” e-mail is sentto Psmadmin.

Note: The automated action checks if a deliverable address called“Psmadmin” exists and sends e-mail to that address. If theaddress is not deliverable, the default action sends e-mail to“root”.

Tivoli/Plus for PSM Event Correlation Rules

Job timed out

Condition 1: Job timed out.

Condition 2: There have been no failed supervisors; job hastimed out 10 times in the last 8 hours.

Automated Action(s): Send “Repeated job timeout” e-mail toPsmadmin (or root).

No document condition

Condition 1: No document logfile message.

Condition 2: The number of events in the last 1 hour is equalto 5.

Automated Action(s): Send “Repeated No Document” e-mail toPsmadmin (or root).

Events and Rules


Enterprise E

ventM

anagement

Printer needs operator

Condition 1: Printer ‘printername’ needs operator.

Condition 2: The number of events in the last 24 hours isequal to 5.

Automated Action(s): Send “Repeated operator attention needed onprinter” e-mail to Psmadmin (or root).

Queue is backlogged

Condition 1: Queue ‘servername:queuname’ backloggedlogfile message.

Condition 2: The number of events in the last 8 hours is equalto 4.

Automated Action(s): Send “Queue backlogged repeatedly” e-mail toPsmadmin (or root).

Internal server error

Condition 1: Internal server error logfile message.


Automated Action(s): Send “Repeated Internal Server Error” e-mail toPsmadmin (or root).

psmd daemon failure

Condition 1: psmd daemon fails.


Automated Action(s): Send “Repeated psmd failure” e-mail toPsmadmin (or root).


Events and Rules

4–30 Version 1.0

spooler daemon failure

Condition 1: spooler daemon fails.


Automated Action(s): Send “Repeated spooler failure” e-mail toPsmadmin (or root).

supervisor daemon failure

Condition 1: supervisor daemon fails.


Automated Action(s): Send “Repeated supervisor failure” e-mail toPsmadmin (or root).

PSM server information directory runs out of inodes

Condition 1: Server information directory goes critical withregard to running out of inodes.


Automated Action(s): Send “Repeated Out of Inodes” e-mail toPsmadmin (or root).

DCE directory runs out of space

Condition 1: DCE directory goes critical with regard torunning out of space.


Automated Action(s): Send “Repeated out of space” e-mail toPsmadmin (or root).


Events and Rules


Enterprise E

ventM

anagement

PSM logfile directory runs out of space

Condition 1: PSM logfile directory goes critical with regardto running out of space.


Automated Action(s): Send “Repeated out of space” e-mail toPsmadmin (or root)


Events and Rules

4–32 Version 1.0


Tasks and Jobs for PS

M

5Tasks and Jobs for PSM

Tivoli/Plus for PSM provides tasks that allow you to run PSM jobs onmultiple machines and operating systems. These tasks are ready to beexecuted as soon as you have installed your Tivoli/Plus for PSMmodule. Simply double-click on the task icon to execute the PSM job.You can modify the default execution characteristics of a particularjob, such as where the output of a job is displayed and on whichmachines the job will run. You may also specify whether a job runsserially on each machine, in parallel on all machines, or staged ingroups of machines.

5

Tivoli/Plus for PSM Jobs

5–2 Version 1.0

Tivoli/Plus for PSM JobsThe following table lists the PSM jobs that can be customized andexecuted with Tivoli/Plus for PSM. Double-click on the task icon torun the PSM job.


Job Function Job Name and Icon

Runs the supervisor daemon on a node.

Stops the supervisor daemon on a node.

Runs the psmd daemon on a node.

Stops the psmd daemon on a node.

Runs the spooler daemon on a node.




M


Stops the spooler daemon on a node.

Enables physical or logical printers toaccept jobs.

Stops physical or logical printers fromaccepting jobs.

Enables all associated logical printer toaccept jobs.

Stops all associated logical printer fromaccepting jobs.

Enables all printers residing in the serverto accept jobs.

Stops all printers residing in the serverfrom accepting jobs.



5–4 Version 1.0


Enables all printers residing in the serverto accept jobs.

Stops all printers residing in the serverfrom accepting jobs.

Stops a physical printer from printingjobs.

Enables a paused printer to resumeoperation.

Stops a queue from dispatching any jobs.

Enables a paused queue to resumeoperation.

Pauses all queues residing in the spooler.





M


Enables all paused queues residing in thespooler to resume operation.

Pauses all printers residing in thesupervisor.

Enables all paused printers residing in thesupervisor to resume operation.


Running a PSM Job and Saving the Output

5–6 Version 1.0

Running a PSM Job and Saving the OutputAll Tivoli/Plus for PSM jobs can be run immediately after installation.You can run these jobs from the desktop only.

To run a PSM job with the default execution characteristics:

If Tivoli/Plus for PSM requires further information to execute the job,a pop-up window appears prompting you for the information. Onlinehelp is available to assist you in completing these windows.

—OR—D-ouble-clickon the icon.

SelectRun job... from theicon’s pop-up menu.




M

For example:

Where appropriate, apop-up window assists youin supplying additionalinformation.

Output is displayedin an output window.


5–8 Version 1.0

The job’s output is displayed in an output window. To save the job’soutput to a file:

1. Select theSave to File... button to display theSave Job Outputdialog box.

2. Enter the name of the machine on which to save the output file intheOn Host field.

3. Enter the name of the output file that will contain the job’s output.

4. Select theSave & Close button to save the output of the job tothe file you specified.

You can also use theModify job... option of the job icon’s pop-upmenu to specify that the output be sent to a file.

Modifying a PSM Job



M

Modifying a PSM JobYou can modify the execution characteristics of a job for each time thejob is run or for only a single execution of the job.

Modifying for All Future Executions of the JobUse the following steps to modify a job for each time it is run.

Modifying a PSM Job

5–10 Version 1.0

1. Select theModify job... option from the job icon’s pop-up menuto display theEdit Job window.

2. Make the necessary changes in theEdit Job window. Online helpis available to assist you.

Note: Be sure to specify on which managed nodes and profilemanagers the job will run.

3. Click on theChange & Close button when finished.

Be sure to specifyon which man-aged nodes andprofile managersthe job will run.

Modifying a PSM Job



M

Modifying for a Single Execution of the JobUse the following steps to modify a job for only a single execution ofthe job. The next time you run the same job, it will return to the defaultexecution characteristics.

Modifying a PSM Job

5–12 Version 1.0

1. Select theRun on selected subscribers... option from the jobicon’s pop-up menu to display theExecute Task window.

1. Make the necessary changes in theExecute Task window. Onlinehelp is available to assist you.

Note: Be sure to specify on which managed nodes and profilemanagers the job will run.

2. Click on theExecute button when finished.

Be sure to spec-ify on whichmanaged nodesand profilemanagers thejob will be runthis time.

Tivoli/Plus for PSM User’s Guide Index–1

Index

Aactivating Tivoli/Plus icons 1-11

Ccommand line installation 1-11commands

winstall 1-11wsupport v

configuringfile packages 2-2logfile adapters 4-6

conventions, typeface vcorrelating event rules 4-28customer support, contacting v

Ddaemons, monitored 3-6DCE directory, percent of space used 3-12desktop installation 1-3Distribute Profiles window 3-3Distribute/Install PSM window 2-13distributing

monitors 3-3PSM 2-10software 2-1– 2-14

documentsprerequisite ivrelated iv

EEnterprise Console.See TME 10 Enterprise

Consoleevent management 4-1– 4-31events

correlation rules 4-28– 4-31description 4-7PSM 4-7– 4-22TME 10 Distributed Monitoring 4-23–

4-27

FFile Browser window 1-6file packages

configuring for PSM installation 2-2viewing 2-10

Ggetting started 1-1– 1-19

Hhardware requirements 1-2host status 3-7

Iicons

for activating Tivoli/Plus 1-11for configuring file packages 2-2for configuring the logfile adapter 4-6for installing PSM 2-10for launching PSM 1-18for monitors 3-2, 3-6for PSM jobs 5-2– 5-5

Index–2 Version 1.0

for setting up the TME 10 EnterpriseConsole 4-2

for subscription lists 3-4Sentry Indicators 3-5Tivoli/Plus 1-11, 1-13Tivoli/Plus for PSM 1-12Tivoli/Plus symbol 1-12

Install Product window 1-5, 1-7installing PSM

all platforms 2-11description 2-1, 2-10single platform 2-13

installing Tivoli/Plus for PSMfrom the command line 1-11from the desktop 1-3requirements for

hardware 1-2machines 1-2software 1-2

Jjobs

icons for 5-2list of 5-2modifying

all future executions 5-9– 5-10single execution 5-11– 5-12

running 5-6saving output 5-8

Llaunching PSM 1-18library, task 5-1logfile adapter for PSM, setting up 4-6

Mmachine requirements 1-2modifying PSM jobs

all future executions 5-9– 5-10single execution 5-11– 5-12

modulesstarting 1-13viewing 1-15

monitored resourcesdaemons

psmd 3-10spooler 3-8supervisor 3-9

directoriesDCE 3-12PSM logfile 3-13PSM server information 3-11

host status 3-7list of 3-6viewing 3-5

monitoring resources 3-1– 3-13monitors

customizing 3-4distributing 3-3icons for 3-2, 3-6subscription lists 3-3using 3-2

Pprerequisite documents, to this guide ivprocedures

configuring file packages 2-2customizing monitors 3-4distributing monitors 3-3installing PSM

all platforms 2-11single platform 2-13

installing Tivoli/Plus for PSM


from the command line 1-11from the desktop 1-3

launching a PSM application 1-18managing PSM jobs

modifying 5-9– 5-12running 5-6saving ouput 5-8

setting up the TME 10 EnterpriseConsole 4-3– 4-6

startinga Tivoli/Plus module 1-13PSM 1-18

using monitors 3-2viewing monitored resources 3-5

Product Install window 1-9, 1-10profile manager 1-12PSM

distributing 2-10events 4-7– 4-22icon 1-18installing

all platforms 2-11single platform 2-13

jobsicons 5-2– 5-5modifying 5-9– 5-12running 5-6saving output 5-8

launching an application 1-18monitored resources

DCE directory 3-12host status 3-7PSM logfile directory 3-13PSM server information directory

3-11psmd daemon status 3-10spooler daemon status 3-8supervisor daemon status 3-9

PSM Servers window 1-19psmd daemon status 3-10

Rrelated documents, to this guide ivrequirements

hardware 1-2installation 1-2machine 1-2software 1-2

resource monitoring 3-1– 3-13rules

for event correlation 4-28– 4-31for PSM events 4-7– 4-22for TME 10 Distributed Monitoring

events 4-23– 4-27running PSM jobs 5-6

Ssaving job output 5-8Sentry Indicator Collection window 3-5Sentry.See TME 10 Distributed MonitoringService Name window 1-19setting up

PSM installation 2-1Tivoli/Plus for PSM 1-1TME 10 Enterprise Console

adding an existing rule base 4-5configuring logfile adapter 4-6creating a new rule base 4-4opening the setup window 4-3

TME 10 Software Distribution filepackages 2-1

Setup EventServer for PSM window 4-3Setup PSM Installation window 2-4Setup PSM OS2 Client Installation window

2-8software

distribution 2-1– 2-14requirements 1-2

Software Distribution.See TME 10 Software

Index–4 Version 1.0

Distributionspooler daemon status 3-8starting

PSM 1-18Tivoli/Plus modules 1-13

Subscribers window 2-11, 2-14subscription list

definition 1-12for monitors 3-3icons 3-4

supervior daemon status 3-9

Ttasks.See jobsTivoli/Plus

icons 1-11modules

starting 1-13viewing 1-15

plus symbol 1-12unique features 1-12window 1-15, 1-16

Tivoli/Plus for PSMinstalling

See installing Tivoli/Plus for PSMprofile manager 1-12subscription list 1-12window 1-17, 3-3

TMEDesktop window 1-4, 1-14problem report v

TME 10 Distributed Monitoringevents 4-23– 4-27list of monitored resources 3-6resource monitoring 3-1using monitors 3-2viewing monitored resources 3-5

TME 10 Enterprise Consoledescription 4-1

setting upadding an existing rule base 4-5configuring logfile adapter 4-6creating a new rule base 4-4opening the setup window 4-3

setup icons 4-2TME 10 Software Distribution

configuring file packages 2-2description 2-1

typeface conventions v

Uusing monitors 3-2

Vviewing

file packages 2-10monitored resources 3-5Tivoli/Plus modules 1-15

Wwindows

Distribute Profiles 3-3Distribute/Install PSM 2-13File Browser 1-6Install Product 1-5, 1-7Product Install 1-9, 1-10PSM Servers 1-19Sentry Indicator Collection 3-5Service Name 1-19Setup EventServer for PSM 4-3Setup PSM Installation 2-4Setup PSM OS2 Client Installation 2-8Subscribers 2-11, 2-14Tivoli/Plus 1-15, 1-16


Tivoli/Plus for PSM 1-17, 3-3TME Desktop 1-4, 1-14

winstall command 1-11wsupport command v