Tivoli System Automation Application Manager V4.1.0.1: … · 2018. 7. 30. · Edition Notices...

System Automation Application ManagerVersion 4.1

Reference and Problem DeterminationGuide

SC34-2703-01

IBM

System Automation Application ManagerVersion 4.1

Reference and Problem DeterminationGuide

SC34-2703-01

IBM

Edition Notices

Before using this information and the product it supports, read the information in “Notices” on page 355

This edition of IBM Tivoli System Automation Application Manager, Reference and Problem Determination Guide applies toVersion 4, Release 1, Modification 0 of IBM Tivoli System Automation Application Manager, program number5724–S92, and to all subsequent releases and modifications of this product until otherwise indicated in new editions.IBM Tivoli System Automation Application Manager is the successor to the end-to-end automation managementcomponent of IBM Tivoli System Automation for Multiplatforms V2.3.

This edition replaces SC34-2589-03.

IBM welcomes your comments. A form for readers' comments may be provided at the back of this publication, oryou may address your comments to the following address:

IBM Deutschland Research and Development GmbH

Department 3248

Schoenaicher Str. 220

D-71032 Boeblingen

Federal Republic of Germany

FAX (Germany): 07031+16-3456

FAX (Other Countries): (+49)+7031-16-3456

Internet e-mail: [email protected]

If you would like a reply, be sure to include your name, address, telephone number, or FAX number.

Make sure to include the following in your comment or note:v Title and order number of this book

v Page number or topic related to your comment

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in anyway it believes appropriate without incurring any obligation to you.

© Copyright IBM Corporation 2006, 2015.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . ix

Tables . . . . . . . . . . . . . . . xi

About this book . . . . . . . . . . xiiiWho should read this guide . . . . . . . . xiiiWhere to find more information . . . . . . . xiiiConventions used in this guide . . . . . . . xivISO 9000 . . . . . . . . . . . . . . . xivRelated information . . . . . . . . . . . xivHow to obtain publications . . . . . . . . . xvHow to reach us by email . . . . . . . . . xv

What's new in this release . . . . . . xvii

Chapter 1. Troubleshooting and support 1Administration . . . . . . . . . . . . . 1

Log and trace file location . . . . . . . . . 1Log files in a multilingual environment . . . . 3Restart workflow fails . . . . . . . . . . 4OutOfMemory exception when trying to view thedomain log . . . . . . . . . . . . . . 4Using the operations console in a multilingualenvironment . . . . . . . . . . . . . 5Problems occur when multiple browser windowsare used to connect to the same IBM DashboardApplication Services Hub from the same clientsystem . . . . . . . . . . . . . . . 5The end-to-end automation domain is notdisplayed on the operations console . . . . . 6A first-level automation domain is not displayedin the topology tree after an outage. . . . . . 6A System Automation for Multiplatforms domainis not displayed in the topology tree . . . . . 6Security exception when trying to subscribe toresources that are hosted on a first-levelautomation domain . . . . . . . . . . . 9Automation Java EE framework (EEZEAR) doesnot support Java 2 security . . . . . . . . 9Resolving timeout problems . . . . . . . . 10Modifying the time zone settings for theoperations console . . . . . . . . . . . 14WebSphere Application Server cannot connect toDB2 . . . . . . . . . . . . . . . . 14Critical exceptions in the WebSphere ApplicationServer log file . . . . . . . . . . . . 15OutOfMemoryError in the WebSphereApplication Server log file . . . . . . . . 15"Unable to set up the event path..." error messageis displayed in the IBM Dashboard ApplicationServices Hub . . . . . . . . . . . . . 16EEZBus is not started . . . . . . . . . . 16No System Automation events received in theOMNIbus event console . . . . . . . . . 18

The end-to-end automation manager fails toinitialize . . . . . . . . . . . . . . 18Troubleshooting EEZIMEAR . . . . . . . . 20Creating IdML books . . . . . . . . . . 20Troubleshooting command shell problems . . . 21Troubleshooting automation engine problems . . 21Troubleshooting Distributed Disaster Recoveryproblems . . . . . . . . . . . . . . 22Troubleshooting PowerHA adapter problems . . 24Troubleshooting FOC adapter problems . . . . 26Troubleshooting VCS adapter problems . . . . 29Troubleshooting the policy editor . . . . . . 29Troubleshooting the agentless adapter . . . . 30

Installation . . . . . . . . . . . . . . 33Silent installation or uninstallation fails due tobroken X connection . . . . . . . . . . 33Installation wizard cannot find WebSphereApplication Server on the system . . . . . . 33Installer cannot detect non-default SOAP port . . 33Determining the correct DB2 port number . . . 34DB2 access test hangs . . . . . . . . . . 34DB2 message SQL1035N The database iscurrently in use. SQLSTATE=57019 . . . . . 34Using the Configuration problem analysis dialog 35Procedures for troubleshooting an installation . . 35Exceptions appear in file eezinstall.log . . . . 36Cleaning up from a failed installation . . . . 36Using the log file collector utility . . . . . . 37Gathering information for IBM Support . . . . 37Troubleshooting the installation of the FOCadapter . . . . . . . . . . . . . . . 37

Configuration . . . . . . . . . . . . . 39SSL configuration problems . . . . . . . . 39

Chapter 2. Reference . . . . . . . . 43Command line interface . . . . . . . . . . 43Commands reference . . . . . . . . . . . 43

Command shell commands . . . . . . . . 43Configuration commands . . . . . . . . . 81Controlling adapters commands . . . . . . 91Controlling the GDPS agent . . . . . . . . 96Command-line interface commands . . . . . 97Data model mapping . . . . . . . . . . 101

Policy XML reference . . . . . . . . . . . 102End-to-end automation policy XML reference 102Automation policy rule reference . . . . . . 124Sample automation policy . . . . . . . . 125Agentless adapter policy XML reference . . . 129Disaster recovery policy reference . . . . . 151Tivoli Monitoring Resource Templates Reference 165

User roles . . . . . . . . . . . . . . 178

Chapter 3. Messages . . . . . . . . 181Policy editor messages . . . . . . . . . . 181

© Copyright IBM Corp. 2006, 2015 iii

SAMP0001E: An 'IOException' was caught inmethod methodName of class className. Thereceived message was message. . . . . . . 181SAMP0002E: The specified policy policyLocationis not valid. . . . . . . . . . . . . . 181SAMP0003E: Not able to create an object of typeObject-type. The name of the tree-node isnode-name. . . . . . . . . . . . . . 181SAMP0004E: Not able to retrieve the policyinformation. . . . . . . . . . . . . 182SAMP0005E: Received errors when trying toactivate the policy. . . . . . . . . . . 182SAMP0006E: The specified policy file " policyFile" cannot be found. . . . . . . . . . . 182SAMP0007E: Original Parser Exception:exceptionMessage . . . . . . . . . . . 182SAMP0008E: Received errors when trying todeactivate the current policy. . . . . . . . 183SAMP0009E: Received errors when trying tocheck the policy. . . . . . . . . . . . 183SAMP0010E: Received errors when trying tosave the current policy. . . . . . . . . . 183SAMP0011E: The resource with nameresourceName and class className was found asmember of multiple groups. . . . . . . . 184SAMP0012E: The resource with nameresourceName and class className was found asmember of an equivalency and of a group. . . 184SAMP0013E: The specified member "memberName " was found multiple times in thesame <groupForm> " groupName ". . . . . . 184SAMP0014E: The specified <groupForm> "groupName " was found as member of itself. . . 184SAMP0015E: The resource group with nameresourceGroupName has a nesting level of morethan 50. . . . . . . . . . . . . . . 185SAMP0016E: An 'Exception' was caught inmethod methodName of class className. Thereceived message was message. . . . . . . 185SAMP0017E: The relationship with the sourcewith name sourceName and type type has atarget with the same key. . . . . . . . . 185SAMP0018E: The relationship source with namesourceName and class sourceClass is not aresource group nor member of a resource group. 186SAMP0019E: An error occurred in methodmethodName of class className. Error detailsdetails. . . . . . . . . . . . . . . . 186SAMP0020E: The specified <Relationship> withthe <Type> " relationType ", the <Source> withthe name " source " and the <Target> with thename " target " was found multiple times in thepolicy document. . . . . . . . . . . . 186SAMP0021E: An 'UTFDataFormatException' wascaught in method methodName of classclassName. The received message was message. . 187SAMP0022E: A <Element> can only containeither a <subElement1> or a <subElement2>. . . 187SAMP0023E: A <Element> that contains a<subElement1> must also contain a<subElement2>. . . . . . . . . . . . . 187

SAMP0024E: A <Element> that contains a<subElement1> must also contain a<subElement2> or a <subElement3>. . . . . . 187SAMP0025E: The <Element> with the name "referenceName " refers to a resource that does notexist on the cluster. . . . . . . . . . . 188SAMP0026E: The node with the name "nodeName " does not exist on the cluster. . . . 188SAMP0027E: The node with the name "nodeName " is not online in the cluster. . . . . 188SAMP0028E: The value " domainName " of theelement <elementName> does not conform to thereal name of the cluster " actualDomainName ". . 189SAMP0029E: The specified element <element>with the name " groupName " contains a memberwith a different name " memberName " . . . . 189SAMP0030E: The specified element <element>was found more than once. . . . . . . . 189SAMP0031E: The specified element<childElement> was found more than once aschild element of <parentElement>. . . . . . 189SAMP0032E: The specified element<childElement> was found more than once aschild element of <parentElement> with the name" parentName ". . . . . . . . . . . . . 190SAMP0033E: The value " value " of the element<allowedNode> does not exist as a node, nor isan equivalency with this name defined. . . . 190SAMP0034E: The element <element> with thename " equivalencyName " cannot be target of alocation relationship. . . . . . . . . . . 190SAMP0035E: The element <element> with thevalue " elementValue " can only be used with alocation relationship except the relationship ofthe type " isStartableType ". . . . . . . . . 191SAMP0036E: The element <element> with thename " elementValue " has got members that arenot from the same resource class. . . . . . 191SAMP0037E: The connection to the backendfailed because the following exception occurredexception. . . . . . . . . . . . . . . 191SAMP0038E: The element <tie-breaker> with thename " name " is set to active although at leastone other element of this kind is set to active,too. . . . . . . . . . . . . . . . 191SAMP0039E: The specified element <element>with the value " value " of the subelement<subelement1> cannot contain a subelement<subelement2> as well. . . . . . . . . . 192SAMP0040E: An IOException was caught whentrying to write the policy to the file " filename ".The exception message was: exception-message. . 192SAMP0041E: Exception occurred when trying tovalidate the selection string " selectString ".Either the selection string is not valid or theconnection to the backend failed. Exceptionmessage was: exception. . . . . . . . . . 192SAMP0042E: The <Element> with the name "referenceName " has an invalid value for thesubelement <Sub-Element>. . . . . . . . 193

iv Tivoli System Automation Application Manager V4.1.0.1: Reference and Problem Determination Guide

SAMP0043E: The <Element> with the type "value " is not allowed on a " value " system. . . 193SAMP0044E: A <Element> must either contain a<Subelement> or a <Subelement>. . . . . . . 193SAMP0045E: An IOException was caught whentrying to read from the included policy file "filename ". The exception message was:exception-message. . . . . . . . . . . . 194SAMP0046E: The syntax of the input policy file" filename " is invalid. The line in error is: invalidline. . . . . . . . . . . . . . . . 194SAMP0047E: Variable referenced within line "invalid line " not found in top-level XML file.Variable is referenced within file: " inputfilename". . . . . . . . . . . . . . . . . 194SAMP0048E: The policy created from thetop-level file policyLocation is not valid. Theresulting policy can be found in the temporaryfile temp-filename. . . . . . . . . . . . 194SAMP0049E: An error occurred in class:className method: methodName. The resourceresourceName could not be defined. There wasno exception, but the define call did not returnany object either. . . . . . . . . . . . 195SAMP0050E: An error occurred in class:className method: methodName. The resourceresourceName could not be defined. The receivedexception was exception . . . . . . . . . 195SAMP0051E: An error occurred in class:className method: methodName. The resourceresourceName could not be added to the resourcegroup groupName. The received exception wasexception . . . . . . . . . . . . . . 195SAMP0052E: An error occurred in class:className method: methodName. The resourcegroup groupName could not be set to the desiredstate state. The received exception was exception . 196SAMP0053E: An error occurred in class:className method: methodName. The resourceresourceName could not be undefined. Thereceived exception was exception . . . . . . 196SAMP0054E: An error occurred in class:className method: methodName. The resourceresourceName could not be identified andlocated. This can be caused by an exception orthe resource could not be found. Therefore theresource resourceName cannot be added to theresource group groupName. The receivedexception was exception . . . . . . . . . 197SAMP0055E: An error occurred in class:className method: methodName. The resourcegroup groupName could not be identified andlocated. This can be caused by an exception orthe resource could not be found. Therefore theresource group groupName cannot be set to thestate state. The received exception was exception . 197

SAMP0056E: An error occurred in class:className method: methodName. The resourceresourceName could not be identified andlocated. This can be caused by an exception orthe resource could not be found. Therefore theresource resourceName cannot be created,because it requires resource resourceName. Thereceived exception was exception . . . . . . 197SAMP0057E: An error occurred in class:className method: methodName. The resourceresourceName could not be identified andlocated. This can be caused by an exception orthe resource could not be found. Therefore theresource resourceName cannot be deleted. Thereceived exception was exception . . . . . . 198SAMP0058E: An error occurred in class:className method: methodName. The resourceresourceName could not be identified andlocated. This can be caused by an exception orthe resource could not be found. Therefore theresource resourceName cannot be modified. Thereceived exception was exception . . . . . . 198SAMP0059E: An error occurred in class:className method: methodName. The resourceresourceName could not be modified. There wasno exception, but the define call did not returnany object either. . . . . . . . . . . . 199SAMP0060E: An error occurred in class:className method: methodName. The resourceresourceName could not be modified. Thereceived exception was exception . . . . . . 199SAMP0061E: An error occurred in class:className method: methodName. TheIBM.TieBreaker resource resourceName could notbe identified and located. The receivedexception was exception . . . . . . . . . 199SAMP0062E: An error occurred in class:className method: methodName. The activeIBM.TieBreaker resource could not be identifiedand located. Therefore the IBM.TieBreakerresource resourceName could not be modified orcreated. The received exception was exception . 200SAMP0063E: An error occurred in class:className method: methodName. TheIBM.TieBreaker resource resourceName could notbe set to active. The received exception wasexception . . . . . . . . . . . . . . 200SAMP0064E: An error occurred in class:className method: methodName. Thesubscription from consumer consumer toresource resourceName has failed. The receivedexception was exception . . . . . . . . . 200SAMP0065E: The attempt to update the currentautomation policy failed because errors weredetected. . . . . . . . . . . . . . . 201SAMP0066E: The <element> with the nameelementName contains a member that has aninvalid value className for its attribute class. . 201

Contents v

SAMP0067E: An error occurred in class:className method: methodName. The resourceresourceName could not be removed from theresource group groupName. The receivedexception was exception . . . . . . . . . 201SAMP0068E: The specified resource group withthe name " name " contains a member that is a<subelement>. This is only allowed for resourcegroups that have a value of " value " for thesubelement <subelement1>. . . . . . . . . 202SAMP0070E: An error occurred in class:className method: methodName. . . . . . . 202SAMP0071E: An error occurred in class:className method: methodName. . . . . . . 202SAMP0072E: Failed to set information about theactivated policy file name: fileName, the errormessage is: error-message. . . . . . . . . 203SAMP0073E: Failed to set information aboutdeactivating a policy. The error message is:error-message. . . . . . . . . . . . . 203SAMP0074E: The <Element> element with thename elementName must contain a <Subelement>subelement, because it describes an IPv6address. . . . . . . . . . . . . . . 203SAMP0075E: The <Element> element with thename elementName contains both a <Subelement>subelement and a <Subelement> subelement. . . 204SAMP0076E: The <Element> element with thename elementName contains a <Subelement>subelement that is too large. . . . . . . . 204SAMP0077E: The <Element> element with thename elementName contains a link local address. 204SAMP0078E: The <Element> element with thename elementName contains a multicast address. 204SAMP0079E: The <Element> element is notsupported with the current Active Version avn. . 205SAMP0080E: The activation task was not able todelete all existing resources. The reason for thisis shown in the previous messages. . . . . . 205SAMP0081E: The deactivation task was not ableto delete all existing resources. The reason forthis is shown in the previous messages. . . . 205SAMP0082E: The update task was not able todelete all existing resources. The reason for thisis shown in the previous messages. . . . . . 206SAMP0083E: The value element of the varelement with name element is not valid for thespecified type " . . . . . . . . . . . . 206SAMP0084E: The value attribute of the varelement with name element must not be empty. . 206SAMP0085E: The element attribute value of theinclude element that points to file element mustnot be empty. . . . . . . . . . . . . 207SAMP0086E: At least on of the value attributesof the nested var elements of varoption elementwith name element is not valid for the specifiedtype. . . . . . . . . . . . . . . . 207SAMP0087E: The element attribute value of thevar element with name element must not beempty. . . . . . . . . . . . . . . 207

SAMP0088E: The dynSelString attribute of thevar element with name element must not containonly one var name. . . . . . . . . . . 207SAMP0089E: At least one var that is referencedin the dynSelString attribute of the var elementwith name element does not exist. . . . . . 208SAMP0090E: The var element referenced in themulti attribute of the include element thatpoints to file element does not exist. . . . . . 208SAMP0091E: Two include elements must notpoint to the same file: element. . . . . . . 208SAMP0092E: If the enumeration attribute is setto value="choice", the attribute validValues mustalso be specified and vice versa. The varelement with name element does contain eitheronly enumeration=choice or validValue. . . . 209SAMP0093E: At least one of the entries of thevalidValues attribute value does not match thespecified type attribute value and/or themin/max attribute values of the var elementwith name element. . . . . . . . . . . 209SAMP0094E: At least one var that is referencedin the multi attribute of the include element thatpoints to the xml file element does not exist. . . 209SAMP0095E: The value attribute of thevaroption element with name element must notbe empty. . . . . . . . . . . . . . 210SAMP0096E: There is no valid license availablefor the policy you are trying to activate. . . . 210SAMP0097E: The value of the max attribute issmaller than the value of the min attribute forthe var element with name element. . . . . . 210SAMP0500W: The specified policy policyLocationcontains no resource group. . . . . . . . 210SAMP0501W: An 'Exception' was caught inmethod methodName of class className. Thereceived message was message. . . . . . . 211SAMP0502W: The two <Relationship> elementswith <Type> "StartAfter" and <Type>"StopAfter" were found with the same <Source>with the name " source " and <Target> with thename " target ". . . . . . . . . . . . . 211SAMP0503W: All members of the group withthe name " groupName " should be collocated,because the group is part of a locationrelationship or of a relationship of the type "dependsOnType ". Set the value of the groups tag<memberLocation> to " collocatedValue ". . . . . 212SAMP0504W: The specified <Relationship> with<Type> " relationType " and <Source> with thename " Sourcename " and <Target> with thename " Target " was found in a loop. . . . . 212SAMP0505W: A <Relationship> with the<Type> " relationType " was found that haslinked more than 100 resources. . . . . . . 212SAMP0506W: The specified element <element>with the value " value " of the subelement<subelement1> should not contain a subelement<subelement2> as well. This subelement isignored. . . . . . . . . . . . . . . 213

vi Tivoli System Automation Application Manager V4.1.0.1: Reference and Problem Determination Guide

SAMP0507W: The resource group with nameresourceGroupName has linked more than 100resources. . . . . . . . . . . . . . 213SAMP0508W: An error occurred in methodmethodName of class className. Error detailsdetails. . . . . . . . . . . . . . . . 213SAMP0509W: A non-critical error occurred inmethod methodName of class className duringactivation of a new policy. Error details details. . 213SAMP0510W: A non-critical error occurred inmethod methodName of class className duringdeactivation of the current policy. Error detailsdetails. . . . . . . . . . . . . . . 214SAMP0511W: A non-critical error occurred inmethod methodName of class className duringsaving of the current policy. Error details details.. 214SAMP0512W: The resource group member nameis specified with the invalid attributecombination of non-mandatory and " value ". . 214SAMP1000I: Usage: sampolicy -h sampolicy [-T][-V] [-q] [-f] -a filename sampolicy [-T] [-V] [-q]-u filename sampolicy [-T] [-V] [-q] [-f] -rfilename sampolicy [-T] [-V] [-q] [-f] -dsampolicy [-T] [-V] -s [filename] sampolicy [-T][-V] [-u] -c filename sampolicy [-T] [-V] -ifilename sampolicy [-T] [-V] [-q] [-f] -a -ttemplatefilename sampolicy [-T] [-V] [-q] -u -ttemplatefilename sampolicy [-T] [-V] [-q] [-f] -r-t templatefilename sampolicy [-T] [-V] [-u] -c -ttemplatefilename sampolicy [-T] [-V] -i -ttemplatefilename sampolicy [-T] [-V] -wtemplatefilename . . . . . . . . . . . 215SAMP1001I: The specified policy policyLocationis valid. . . . . . . . . . . . . . . 215SAMP1002I: The policy has the following policyinformation: policyInfo. . . . . . . . . . 215SAMP1003I: The policy has been activatedsuccessfully. . . . . . . . . . . . . 216SAMP1004I: The activation task ends. . . . . 216SAMP1005I: The activation task ends. . . . . 216SAMP1006I: The current policy was saved to filefilename. . . . . . . . . . . . . . . 216SAMP1007I: The automation policy wasdeactivated successfully. . . . . . . . . 216SAMP1008I: Template processing failed. Theactive task ends. . . . . . . . . . . . 217

SAMP1009I: The automation policy wasupdated successfully. . . . . . . . . . 217SAMP1010I: The update task ends because youdid not confirm the action. . . . . . . . 217SAMP1011I: The attempt to update the currentautomation policy failed. . . . . . . . . 218SAMP1100I: Starting to check policypolicyLocation. . . . . . . . . . . . . 218SAMP1101I: Starting to load policy. . . . . . 218SAMP1102I: Retrieving policy info ofpolicyLocation. . . . . . . . . . . . . 218SAMP1103I: Are you sure you want to activate anew automation policy? Yes (y) or No (n) ? . . 218SAMP1104I: Deactivation will remove allresources which can be created via policyactivation. Deactivation will not change anyresources of the class IBM.TieBreaker Are yousure you want to deactivate the currentautomation policy? Yes (y) or No (n) ? . . . . 218SAMP1105I: Please enter the root password: . . 218SAMP1106I: Now calling the backend in orderto retrieve all data needed. . . . . . . . 219SAMP1107I: Now calling the backend in orderto activate the policy. . . . . . . . . . 219SAMP1108I: Now calling the backend in orderto deactivate the policy. . . . . . . . . . 219SAMP1109I: Removed resources successfully. 219SAMP1110I: Created and changed resourcessuccessfully. . . . . . . . . . . . . 219SAMP1111I: Are you sure you want to updatethe current automation policy? Yes (y) or No (n)? . . . . . . . . . . . . . . . . 219

EEZ message code. . . . . . . . . . . . 219EEZ message catalog . . . . . . . . . . . 220VCS Solaris adapter messages . . . . . . . . 340PowerHA and automation adapter messages . . . 344

Using IBM Support Assistant . . . . 353Installing IBM Support Assistant and the TivoliSystem Automation for Multiplatforms plug-in . . 353

Notices . . . . . . . . . . . . . . 355Trademarks . . . . . . . . . . . . . . 356

Index . . . . . . . . . . . . . . . 357

Contents vii

viii Tivoli System Automation Application Manager V4.1.0.1: Reference and Problem Determination Guide

Figures

1. Dr. Watson for Windows settings . . . . . 28

© Copyright IBM Corp. 2006, 2015 ix

x Tivoli System Automation Application Manager V4.1.0.1: Reference and Problem Determination Guide

Tables

1. Environment variables of the automation JEEframework . . . . . . . . . . . . . 10

2. Sub-components implicated by messageEEZJ0030E . . . . . . . . . . . . . 19

3. Issues when creating IdML books . . . . . 204. GPDS agent return codes . . . . . . . . 225. Resource states that are affected by the state of

the target node . . . . . . . . . . . 316. Observed states that are affected by the state

of the target node . . . . . . . . . . 327. Corrupt or empty SSL truststore file - Adapter

messages . . . . . . . . . . . . . 408. Corrupt or empty SSL truststore file -

Application Manager messages . . . . . . 409. Corrupt or empty SSL keystore file - Adapter

messages . . . . . . . . . . . . . 4010. Corrupt or empty SSL keystore file -

Application Manager messages . . . . . . 4011. Wrong SSL keystore password specified -

Adapter messages . . . . . . . . . . 4112. Wrong SSL keystore password specified -

Application Manager messages . . . . . . 4113. Wrong SSL certificate alias specified - Adapter

messages . . . . . . . . . . . . . 4114. Wrong SSL certificate alias specified -

Application Manager messages . . . . . . 4115. Missing SSL configuration on one side -

Adapter messages . . . . . . . . . . 42

16. Missing SSL configuration on one side -Application Manager messages . . . . . . 42

17. Command shell commands . . . . . . . 4418. Operators that can be used in selection strings 8019. Selection strings: Data types . . . . . . . 8120. Configuration commands . . . . . . . . 8121. Data model mapping . . . . . . . . . 10122. XML special characters . . . . . . . . 10323. Classes of nodes in the various system

automation products . . . . . . . . . 15324. Worksheet to define disaster recovery

topology . . . . . . . . . . . . . 16225. Worksheet to define disaster recovery

hardware . . . . . . . . . . . . . 16326. Worksheet to define disaster recovery

workload . . . . . . . . . . . . . 16527. DB2 agent resource attribute mappings 16628. Tivoli Monitoring WebSphere Application

Server agent resource attribute mappings . . 16729. Apache agent resource attribute mappings 16930. Tivoli Monitoring custom agent resource

attribute mappings. . . . . . . . . . 17131. Linux OS agent resource attribute mappings 17432. UNIX OS agent resource attribute mappings 17633. Access roles for System Automation

Application Manager . . . . . . . . . 178

© Copyright IBM Corp. 2006, 2015 xi

xii Tivoli System Automation Application Manager V4.1.0.1: Reference and Problem Determination Guide

About this book

This guide contains reference information such as commands, messages, andtroubleshooting guidelines pertaining to System Automation Application Manager(from here on referred to as System Automation Application Manager.

Who should read this guideThis guide is for all users who are responsible for administering SystemAutomation Application Manager, and for diagnosing problems related to it.

Where to find more informationThe System Automation library contains the following books, including this one,describing System Automation Application Manager:v System Automation Application Manager Administrator's and User's Guide,

SC34-2701-00v System Automation Application Manager Installation and Configuration Guide,

SC34-2702-00v System Automation Application Manager Reference and Problem Determination Guide,

SC34-2703-00

You can download the books at:http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.saam.doc_4.1/welcome.html

More information about System Automation for Multiplatforms can be found inthe following books:v System Automation for Multiplatforms Administrator's and User's Guide,

SC34-2698-00v System Automation for Multiplatforms Installation and Configuration Guide,

SC34-2699-00v System Automation for Multiplatforms Reference, SC34-2700-00v System Automation for Multiplatforms High Availability Policies Guide, SC34-2660-00

You can download the books at:http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.samp.doc_4.1/welcome.html

The System Automation home page contains useful up-to-date information,including support links and downloads for maintenance packages.

The System Automation Application Manager home page is:

http://www.ibm.com/software/tivoli/products/sys-auto-app-mgr

The System Automation for Multiplatforms home page is:

http://www.ibm.com/software/tivoli/products/sys-auto-multi

The System Automation for z/OS® home page is:

http://www.ibm.com/software/tivoli/products/system-automation-zos

© Copyright IBM Corp. 2006, 2015 xiii

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.saam.doc_4.1/welcome.html

http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=%2Fcom.ibm.samp.doc_4.1%2FSAMP-homepage.html

http://www.ibm.com/software/tivoli/products/sys-auto-app-mgr

http://www.ibm.com/software/tivoli/products/sys-auto-multi

http://www.ibm.com/software/tivoli/products/system-automation-zos

Conventions used in this guideThis guide uses several conventions for special terms and actions and operatingsystem commands and paths.

Typeface conventions

This guide uses the following conventions:v Typically, file names, directories, and commands appear in a different font. For

example:– File name: setup.jar– Directory: /etc/hosts– Command: eezdmn -start

v Variables are either italicized, enclosed in brackets, or both. For example:– http://<hostname.yourco.com>/index.html

v Frequently, variables are used to indicate a root installation directory:– Root installation directory of System Automation Application Manager:

<EEZ_INSTALL_ROOT> or EEZ_INSTALL_ROOT– WebSphere® Application Server root installation directory: <was_root> or

was_root– Runtime root directory of Integrated Solutions Console: <isc_runtime_root> or

isc_runtime_rootv Directories are shown with forward slashes (/), unless operating-system specific

information is provided. On Windows systems, you should use backwardslashes (\) when typing at a command line, unless otherwise noted.

v Operating-system specific information is provided. For example:– AIX®, Linux: /opt/IBM/tsamp/eez– Windows: C:\Program Files\IBM\tsamp\eez

ISO 9000ISO 9000 registered quality systems were used in the development andmanufacturing of this product.

Related informationFind out where to find more information about products related to SystemAutomation Application Manager.

Knowledge Centers:

WebSphere Application Server publications:

The latest versions of all WebSphere Application Server publications can befound in the WebSphere Application Server Knowledge Center.

IBM® DB2® publications:The latest versions of all DB2 publications can be found in the DB2 forLinux UNIX and Windows Knowledge Center.

IBM GDPS® publications:The latest versions of all GDPS publications can be found in the TivoliNetView Monitoring for GDPS Knowledge Center.

xiv Tivoli System Automation Application Manager V4.1.0.1: Reference and Problem Determination Guide

http://www.ibm.com/support/knowledgecenter/SSEQTP/mapfiles/product_welcome_was.html?lang=en

http://www.ibm.com/support/knowledgecenter/SSEPGG/welcome?lang=en

http://www.ibm.com/support/knowledgecenter/SSEPGG/welcome?lang=en

http://www.ibm.com/support/knowledgecenter/SSDG28/welcome?lang=en

http://www.ibm.com/support/knowledgecenter/SSDG28/welcome?lang=en

IBM Redbooks® publications:The following publications are available at:http://www.redbooks.ibm.com/

v GDPS Family: An Introduction to Concepts and Capabilities

IBM Tivoli® Common Reporting (TCR) publications:The latest versions of all publications can be found in the Tivoli CommonReporting Knowledge Center.

IBM Tivoli Storage Productivity Center for Replication (TPC-R) publications:The latest versions of all publications can be found in the Tivoli StorageProductivity Center for Replication Knowledge Center.

IBM Support Assistant (ISA):ISA Publications are available on the IBM Support Assistant web site at:http://www.ibm.com/software/support/isa

How to obtain publicationsThe System Automation publications are also available (valid at the time of release)at these Web sites:www.ibm.com/servers/eserver/clusters/library/www.ibm.com/servers/eserver/zseries/software/sa/www.ibm.com/software/sysmgmt/products/support/

How to reach us by emailIf you would like to contact us by email, send your comments [email protected]

About this book xv

http://www.redbooks.ibm.com/

http://www.redbooks.ibm.com/redbooks/pdfs/sg246374.pdf

http://www.ibm.com/support/knowledgecenter/SSH2DF/welcome?lang=en

http://www.ibm.com/support/knowledgecenter/SSH2DF/welcome?lang=en

http://www.ibm.com/support/knowledgecenter/SSMN28/welcome?lang=en

http://www.ibm.com/support/knowledgecenter/SSMN28/welcome?lang=en

http://www.ibm.com/software/support/isa

xvi Tivoli System Automation Application Manager V4.1.0.1: Reference and Problem Determination Guide

What's new in this release

Get a quick overview about the new features of System Automation ApplicationManager version 4.1.

New DASH user interface for the operations consoleThe System Automation operations console is completely redesigned, basedon Jazz for Service Management and Dashboard Application Services Hub.

Key enhancements are:v More flexible and dynamic views

– Create your own dashboards based on Dashboard ApplicationServices Hub capabilities.

– Customize predefined dashboards, for example change widget layoutor configure displayed columns.

v The predefined dashboard Domain and Automation Health provides agraphical status overview and drill down capabilities for more details.

v Use the predefined dashboard Explore Automation Nodes to explore alldomains and nodes that are connected to System AutomationApplication Manager and drill down to the hosted resources.

v The predefined dashboard Operate End-to-End Resources displaysautomated resources and a graphical view of resource relationships.

v You can now allow user requests against multiple resources at a timev You can allow priorities on requests.v The visualization of different group types is improved.v Performance of System Automation operations console is improved.

Server groupThe server group is a new policy element, designed to group resourcestogether, which have to react to dynamic load requirements by addingmembers if needed. The server group introduces automatic failovercapabilities for its members and allows to dynamically start and stop sparemember by modifying the availability target of the server group.

Policy editor provided in the DASH operations console (V 4.1.0.1)The policy editor, which is available in System Automation ApplicationManager, is now integrated into the DASH operations console.

New versions of the middleware software (V 4.1.0.1)Starting with fix pack 4.1.0.1, System Automation Application Managerexploits new features of the middleware software. Therefore, upgrade themiddleware software, in particular the version of Jazz for ServiceManagement, if you upgrade System Automation Application Manager toservice level 4.1.0.1 or higher.

© Copyright IBM Corp. 2006, 2015 xvii

xviii Tivoli System Automation Application Manager V4.1.0.1: Reference and Problem Determination Guide

Chapter 1. Troubleshooting and support

Troubleshooting and support information for System Automation ApplicationManager helps you understand, isolate, and resolve problems. Troubleshooting andsupport information contains instructions for using the problem-determinationresources that are provided with your IBM products. To resolve a problem on yourown, you can find out how to identify the source of a problem, how to gatherdiagnostic information, where to get fixes, and which knowledge bases to search. Ifyou need to contact IBM Support, you can find out what diagnostic informationthe service technicians need to help you address a problem.

For more information, see System Automation Application Manager 4.1.0 SupportPortal.

AdministrationFind out all the help that is offered if you require support or want to solve anissue while administering System Automation Application Manager.

Log and trace file locationLocate the log and trace files that are relevant for end-to-end automationmanagement.

About this task

Tivoli Common Directory locationAbout this task

Message and trace logs for Tivoli products are located under a common parentcalled the Tivoli Common Directory. The log and trace files of all components ofSystem Automation Application Manager that are not running within WebSphereApplication Server, for example, the log and trace files of the end-to-endautomation engine and of the automation adapters, are written to theproduct-specific subdirectory of the Tivoli Common Directory.

The path to the Tivoli Common Directory is specified in the properties filelog.properties. The file log.properties is located in the /etc/ibm/tivoli/common/cfg directory.

In the log.properties file, the path to the Tivoli Common Directory is defined inthe property tivoli_common_dir=<path_to_Tivoli_Common_Directory>.

/var/ibm/tivoli/common is the default value.

These are the relevant subdirectories for end-to-end automation management:

Subdirectory Description

<Tivoli_Common_Directory>/eez/logs message log files, trace files

<Tivoli_Common_Directory>/eez/ffdc FFDC files

© Copyright IBM Corp. 2006, 2015 1

http://www.ibm.com/support/entry/portal/product/tivoli/tivoli_system_automation_application_manager?productContext=-57776453

http://www.ibm.com/support/entry/portal/product/tivoli/tivoli_system_automation_application_manager?productContext=-57776453

For additional information on where to find the log and trace files of theautomation engine, see below. For information about the log and trace files of theautomation adapters, refer to the adapter-specific documentation.

Log and trace files of the automation engineAbout this task

The log files and trace files of the automation engine are available in the directory<Tivoli_Common_Directory>/eez/logs.

Message log file: <Tivoli_Common_Directory>/eez/logs/msgEngine.log

This is the domain log file of the end-to-end automation domain that can bedisplayed from the operations console.

Trace log file: <Tivoli_Common_Directory>/eez/logs/traceEngine.log

Use the Logger tab of the end-to-end automation manager configuration tool tospecify which messages and traces are written to the log files. For informationabout the configuration tool, see Tivoli System Automation Application Manager,Installation and Configuration Guide. For a detailed description of the properties thatcan be configured on the page, refer to the configuration tool help.

The log files are written in XML format. Use the operations console and select theview log menu item for a specific automation domain to inspect the related logfile.

Traces and logs are also created in a flat file format. They are namedtraceFlatEngine.log and msgFlatEngine.log and can be found in the samedirectory. The contents of these files are not written as XML structures, so they areeasy to read with any editor.

Log and trace files of the operations console and the automationJEE frameworkThe operations console and the automation JEE framework of System AutomationApplication Manager use the log files and the tracing function of WebSphereApplication Server.

About this task

By default, the information is written to these log and trace files:v SystemOut.logv SystemErr.logv trace.log

The files are located in the following directory:<jazzsm_root>/profile/logs/<server_name>

Use the WebSphere administrative console to set the parameters for logging andtracing:v To specify log file parameters, for example, the log file names, the maximum

size, and the number of history log files to be preserved, open the WebSphereadministrative console and navigate to Troubleshooting > Logs and Trace ><server_name> > Diagnostic Trace

v To set the parameters for tracing, for example, to switch tracing on or off or todefine for which components traces should be recorded, open the WebSphere

2 Tivoli System Automation Application Manager V4.1.0.1: Reference and Problem Determination Guide

administrative console and navigate to Troubleshooting > Logs and Trace ><server_name> > Change Log Detail Levels .

For more information, see the WebSphere Application Server knowledge center.

Traceable componentsAbout this task

For the components of System Automation Application Manager that run inWebSphere Application Server, it is possible to enable logging and tracing withdifferent scopes, varying from all component groups (com.ibm.eez.*) to veryfine-grained individual components.

You change the logging and tracing levels for the components of SystemAutomation Application Manager on the Change Log Detail Levels page in theWebSphere administrative console. The names of the components start with thestring com.ibm.eez. To change the log detail levels for all traceable user interfacecomponents, change the settings for the component group com.ibm.eez.ui.*.

Log files used for Distributed Disaster RecoveryAbout this task

The following log files are used by Distributed Disaster Recovery functions:

GPDS agent (eezgdpsagent)Writes messages to the system logger (/var/log/messages) if you have setthe levels "debug" and "err" in the file /etc/syslog.conf:v To log verbose messages, the GPDS agent calls the system logger using

the facility "user" and the level "debug" (logger –puser.debug).v To log error messages, it uses the facility "user" and the level "err"

(logger –puser.err).

Processed commands are written to the log file of the end-to-endautomation engine in the Tivoli Common Directory.

Hardware adapter (eezhwadapter)

Writes messages and traces to the log and trace files of the automationengine.

As soon as the command has been passed to the JEE Framework, standardlogging and tracing of the JEE Framework and the automation engine isused.

Log files in a multilingual environmentAbout this task

In general, messages are generated according to the locale that best fits thelanguage preference specified in the browser in which the operations console isdisplayed. Messages are presented on the console and written to one or more logfiles, depending on the System Automation Application Manager component thatgenerates the message.

If multiple browsers with different language preferences are used, the log files maycontain messages in multiple languages. Additionally, some messages are writtento the log files independent of any operator interaction. For example, when a

Chapter 1. Troubleshooting and support 3

http://www.ibm.com/support/knowledgecenter/SSEQTP/mapfiles/product_welcome_was.html

System Automation Application Manager component is started or stopped, itwrites a message to its log file according to the locale in which it was started orstopped.

If you need to understand the content of a message in the log file that is written ina language you do not know, refer to the message catalog provided in the IBMTivoli System Automation Application Manager Reference to find the message bymessage ID.

The log files that are stored in the Tivoli common directory, for example the logfiles of the end-to-end automation engine and of the agentless adapter are encodedin the UTF-8 format. Make sure to open the log files using an editor that supportsUTF-8 in order to properly view the file content.

Restart workflow failsAbout this task

If the restart workflow fails, it can have one of the following three reasons. If youwant to find out how the restart workflow works, refer to Tivoli System AutomationApplication Manager, Administrator’s and User’s Guide.1. The restart workflow is rejected. The workflow does not start or terminates

immediately. The following reasons apply:v The observed state of the resource is not Online.v The desired state of the resource is NoChange.v The restart of the resource is already running.v The resource is an end-to-end automation replication reference. A restart does

not apply to this kind of resources.v The automation domain throws an exception while processing the initial

offline request.2. The restart workflow is interrupted. The following reasons apply:v Another request with a higher priority changes the observed state of the

resource.v The restart workflow timed out. The offline or online request does not

complete within a given timeframe. The default timeout range is 48 hours.For more information, see Resolving timeout problems.

3. All restart workflows are interrupted for the whole domain or node. Thefollowing reasons apply:v Activate an automation policy.v Start or stop the end-to-end automation engine.v Start or stop the first-level automation adapter.v Exclude the first-level cluster node.v Stop the WebSphere Application Server which affects all ongoing restart

workflows.

OutOfMemory exception when trying to view the domain logAbout this task

The size of log files of your automation domain grows up to a specified limit.When this limit is reached, the current log file is automatically saved as a differentfile name. Logging continues with a new empty file with the same name. Whenyou experience OutOfMemory problems when trying to view the log file this


http://www-03preprod.ibm.com/support/knowledgecenter/SSPQ7D_4.1.0.1/com.ibm.saam.doc_4.1/tatune_trouble_resolvetimeouts.html

problem can be circumvented by reducing the maximum size of the file using theautomation manager configuration tool (Logger tab of the common configurationdialog). You may consider to copy your current log file on a regular base to adifferent location, for example once a week into a folder named OldLogFiles. Youachieve a well structured log file history as you start each week with an empty logfile.

Using the operations console in a multilingual environmentAbout this task

If you need multiple-language encoding support in the administrative console, forexample, because some of your automation domains are running in locales withencoding other than those specified in the client browser, you can use the JVMargument client.encoding.override=UTF-8 to configure an application server forUCS Transformation Format. This format enables an application server to handlemost character encodings correctly.

Example:

If you use the operations console to view the log file of a first-level automationdomain running in a German locale and the default language of your browser isset to Japanese, German special characters that appear in the log may not bedisplayed correctly in the Japanese browser. To avoid this problem, set the clientencoding override to UTF-8.

To configure an application server for UCS Transformation Format, perform thesesteps:1. In the administrative console, click Servers > Server Types > WebSphere

application servers and select the server you want to enable for UCSTransformation Format.

2. Then, under Server Infrastructure, click Java™ and Process Management >Process Definition > Java Virtual Machine.

3. Specify -Dclient.encoding.override=UTF-8 for Generic JVM Arguments andclick OK. When this argument is specified, UCS Transformation Format is usedinstead of the character encoding that would be used if theautoRequestEncoding option was in effect.

4. Click Save to save your changes.5. Restart the application server.

Problems occur when multiple browser windows are used toconnect to the same IBM Dashboard Application Services Hubfrom the same client system

About this task

If you are using a browser other than Microsoft Internet Explorer, opening multiplebrowser windows on the same client machine to connect to the same IBMDashboard Application Services Hub will cause unexpected results. This is becauseonly Microsoft Internet Explorer establishes a separate HTTP session for eachbrowser instance. Other browser types will share a single session between multiplebrowser instances on the same system if these instances connect to the same IBMDashboard Application Services Hub.


The same situation occurs if you open multiple Microsoft Internet Explorerbrowser windows using File —> New Window (or Ctrl + N) from an existing IBMDashboard Application Services Hub session, because in this case the new browserwindow and the one from which it was opened will also share the same session.

The end-to-end automation domain is not displayed on theoperations console

About this task

If the end-to-end automation domain is not displayed on the operations consolealthough the automation JEE framework is running and the automation engine isstarted, perform the following steps:1. In the end-to-end automation manager configuration dialog, verify that all

parameters are set correctly.2. Restart the automation engine.

For information about the configuration dialog, refer to Tivoli System AutomationApplication Manager, Installation and Configuration Guide. For information on startingthe automation engine, refer to Tivoli System Automation Application Manager,Administrator’s and User’s Guide.

A first-level automation domain is not displayed in thetopology tree after an outage

About this task

After a planned or unplanned outage of the end-to-end automation manager JEEframework, it may happen that first-level automation domains that werepreviously visible on the topology tree in the operations console do not appearagain. This may occur if the end-to-end automation database was cleared for somereason, or if the timeout defined by the environment variablecom.ibm.eez.aab.domain-removal-hours was exceeded. For more information, see“Resolving timeout problems” on page 10.

To resolve the problem, stop and restart the first-level automation adapter. If thefirst-level automation domain is still not displayed in topology tree, check theinstructions in “A System Automation for Multiplatforms domain is not displayedin the topology tree.”

A System Automation for Multiplatforms domain is notdisplayed in the topology tree

About this task

If a first-level automation domain does not appear in the topology tree on theoperations console, perform the following steps to analyze and resolve theproblem:1. Check if the adapter is running by issuing the following command on one of

the nodes of the domain:samadapter status

If the adapter is running, a message like in the following example comes up:samadapter is running on sapb13


Make a note of the name of the node on which the adapter runs (in theexample this is sapb13) and proceed with step 4.

2. If the adapter is not running, issue the following command to check if thedomain is online:lsrpdomain

A message like in the following example comes up:Name OpState RSCTActiveVersion MixedVersions TSPort GSPortdomain1 Online 2.4.4.2 No 12347 12348

If OpState is not Online, start the domain.3. If the domain is online, start the adapter with the following command:

samadapter start

After the start message has appeared, reissue the following command:samadapter status

4. If the adapter is running, check again on the operations console if the domainnow appears in the topology tree. Note that it may take time until the contactto the end-to-end automation manager is established after the adapter isstarted.

5. If the domain still does not appear in the topology tree, you need theconnection information that you specified in the adapter configuration dialogto resolve the problem.Perform the following steps:a. Launch the adapter configuration dialog of System Automation by issuing

the following command on a node in the domain:cfgsamadapter

b. On the entry window of the configuration dialog, click Configure.c. Open the Adapter page on the Configure window and write down the

values that appear in the following fields:v Host name or IP Addressv Request port number

This is the connection information the end-to-end automation managementhost uses to reach the adapter on any of the nodes in the domain.

d. Open the page Host using adapter and write down the values that appearin the following fields:v Host name or IP Addressv Event port number

This is the connection information the adapter on any of the nodes in thedomain uses to reach the end-to-end automation management host.

6. Check if end-to-end automation management can be reached from each nodein the domain. A simple test is ping <end-to-end management host>.If there is a firewall between the nodes of the domain and the end-to-endautomation management host, check with the network administrator if thefirewall permits a connection between the node (page Adapter: Host name orIP Address) and the end-to-end management host (page Host using adapter:Host name or IP Address and Event port number).

7. The adapter determines whether SSL must be used for the communicationwith the end-to-end automation manager. To check the SSL settings of theadapter, launch the adapter configuration dialog using the commandcfgsamadapter. On the Security page, verify that the SSL settings are correct.


Note: If the end-to-end automation manager is configured for using SSL, theadapter must be configured for SSL as well. The SSL configuration of theend-to-end automation manager is performed using the cfgeezdmnconfiguration utility.

8. On the end-to-end automation management host, use netstat to find out if it islistening for events on the event port defined in Event port number.When the event port number is set to 2002 host, netstat -an displays amessage like in the following example:Active Internet connections (servers and established)Proto Recv-Q Send-Q Local Address Foreign Address Statetcp 0 0 :::2002 :::* LISTENtcp 0 0 10.0.0.1:2002 10.0.0.2:59261 ESTABLISHED

If netstat does not display any information about the event port defined inEvent port number, open the file /etc/hosts and verify that the loopbackaddress (127.0.0.1) is not related to the actual host name. The loopbackaddress should be related to localhost only. For example, the entry in/etc/hosts may look like the following:127.0.0.1 localhost.localdomain localhost

9. Check if each node in the domain can be reached from end-to-end automationmanagement. A simple test is ping <host name or IP Address>.If there is a firewall between the end-to-end automation management host andthe nodes of the domain, check with the network administrator if the firewallpermits a connection between the end-to-end automation management host(page Host using adapter: Host name or IP Address and Request portnumber) and the node (page Adapter: Host name or IP Address).

10. On the node on which the adapter is running, use netstat to find out if it islistening on the port defined in Request port number.For example, when the request port number is set to 2001, netstat displays amessage like the following:sapb13:~ # netstat -atn |grep 2001tcp 0 0 9.152.20.113:2001 :::* LISTEN

11. When the communication between all ports has been established correctly(see the descriptions above), check whether the EEZ Publisher is running. TheEEZ Publisher must be running on the master node of the System Automationfor Multiplatforms domain.To check if the publisher is running, perform the following steps:a. Issue the following command on one of the nodes of the first-level

automation domain:lssamctrl

If the publisher is enabled, you will receive output like in the followingexample:safli03:~ # lssamctrl | grep PublisherEnablePublisher = EEZ

b. Issue the following command on the master node of the SystemAutomation for Multiplatforms domain:ps axw | grep SAMAdapter

You should receive output like in the following example:32739 ? Sl 0:01 /usr/sbin/rsct/bin/SAMAdapter/etc/opt/IBM/tsamp/sam/cfg/sam.adapter.properties EEZ false 1

12. If the domain still does not appear on the operations console contact IBMsupport and provide diagnostic information:


a. On each node in the domain, find out where the trace files are located. Thetrace files can be found in the /eez/logs subdirectory of the TivoliCommon Directory. To find the path to the Tivoli Common Directory, issuethe following command:cat /etc/ibm/tivoli/common/cfg/log.properties

The command returns the path to the Tivoli Common Directory, forexample:tivoli_common_dir=/var/ibm/tivoli/common

This means that the trace files can be found in the following directory:/var/ibm/tivoli/common/eez/logs

b. Use tar to package all files in the directory and provide the archive toIBM support.

Security exception when trying to subscribe to resources thatare hosted on a first-level automation domain

About this task

If you see the following error messages in the domain log file of the end-to-endautomation domain, verify that the credentials for the first-level automationdomain have been specified:

EEZD0069E A Security Exception was caught trying to subscribe to resourceshosted on automation domain with name first-level domain. Following is a listof resources the automation engine tried to subscribe to: (resource_group/IBM.ResourceGroup/).

EEZD0072E An EEZUserSecurityException was caught trying to contact anotherautomation domain. Original message text is: EEZA0009E Invocation of adapterplug-in failed: plug-in=com.ibm.sam.eezplugin.SAMFLA,method=SUBSCRIBE_RESOURCE, internalRetcode=41, taskRetcode=0.

To check that the user credentials for the first level automation domain have beenspecified correctly, check the settings on the User credentials page of theconfiguration dialog.

For more information about the configuration dialog, refer to Tivoli SystemAutomation Application Manager, Installation and Configuration Guide. For detailedinformation about the User credentials page, refer to the online help of theconfiguration dialog.

Automation Java EE framework (EEZEAR) does not supportJava 2 security

About this task

Java 2 security is not supported by the EEZEAR application. If Java 2 security isenabled, EEZEAR will no longer start.

Note that Java 2 security will be automatically enabled when you enableWebSphere security in the WebSphere administrative console. In this case, youmust disable Java 2 security in the WebSphere administrative console.


Resolving timeout problemsAbout this task

If you experience timeout problems when accessing first-level automation domains,this may mean that the default values of some optional JEE frameworkenvironment variables are not appropriate for your environment.

The following table lists the environment variables that you may need to change toresolve the problems.

More information about the environment variables is provided in the followingtopics. topic “Modifying the environment variables for the automation Java EEframework” on page 13 describes how you change the environment variables inthe WebSphere administrative console.

Table 1. Environment variables of the automation JEE framework

Variable nameMinimum

valueDefaultvalue

Maximumvalue

com.ibm.eez.aab.watchdog-interval-seconds 60 300 86400

com.ibm.eez.aab.watchdog-timeout-seconds 2 10 60

com.ibm.eez.aab.domain-removal-hours 1 48 1000

com.ibm.eez.aab.resource-restart-timeout-hours

1 1 3600

com.ibm.eez.aab.invocation-timeout-seconds 30 60 3600

Rules:

v If the value of an environment variable is below the minimum value for thatvariable, the minimum value is used.

v If the value of an environment variable is above the maximum value for thatvariable, the maximum value is used.

v Cross-dependency: To ensure that domains are removed only after the healthstate has moved to some timeout or failed state, the value of the variable:com.ibm.eez.aab.domain-removal-hours

must be greater than the value of:com.ibm.eez.aab.watchdog-interval-seconds/3600

If you specify values that violate this rule, the user-specified value for:com.ibm.eez.aab.domain-removal-hours

is ignored and the value of:com.ibm.eez.aab.domain-removal-hours

is set tocom.ibm.eez.aab.watchdog-interval-seconds/3600 +1

Working with hardware adapter for zEnterprise® HMC access: It is recommendedto set the following variables with the values shown:v com.ibm.eez.aab.watchdog-timeout-seconds - set to 30 seconds.v com.ibm.eez.aab.invocation-timeout-seconds - set to 90 seconds.


Watchdog - A mechanism for monitoring the domaincommunication statesAbout this task

The automation JEE framework includes a watchdog mechanism to determine thehealth state of the communication with each domain (either the end-to-endautomation domain or a first-level domain). If the automation JEE framework andthe domain in question have not communicated successfully during the timeinterval defined by the environment variable:com.ibm.eez.aab.watchdog-interval-seconds

(default value: 300), the automation JEE framework invokes a test operation on thedomain. This test operation may only take a limited amount of time, as defined bythe environment variable:com.ibm.eez.aab.watchdog-timeout-seconds

Depending on the outcome of this test operation, the domain communicationhealth state is updated and reflected in the operations console accordingly.

If a very large number of domains is to be monitored or the domain contains avery large number of resources and the value of:com.ibm.eez.aab.watchdog-interval-seconds

is not sufficiently large, the watchdog may not be able to contact all domains andreceive their reply events within the given time. This results in incorrectcommunication state changes for the affected domains:v In the WebSphere Application Server message log, pairs of messages EEZJ1003I

can be found for each of these domains, indicating that the domain'scommunication state changed from "OK" to "AsyncTimeout" and back to "OK"within a short period of time.

v In addition, the operations console icons for the affected domains changeaccordingly for a short period of time from "The domain is online" to "Resourceevents cannot be received" and back to "The domain is online".

To resolve the problem, increase:com.ibm.eez.aab.watchdog-interval-seconds

to a value that is approximately double that of the number of domains. Forexample, if there are 200 domains, the value of:com.ibm.eez.aab.watchdog-interval-seconds

should be set to 400.

If the number of resources to be monitored on the operations console is very large,increase the value of:com.ibm.eez.aab.watchdog-interval-seconds

in steps of 200 seconds until the result is satisfactory.


Database cleanup timeout for automation domainsAbout this task

The automation JEE framework contains a mechanism for removing automationdomains from the database after a period of inactivity. The domains themselves arenot removed, just the representation of the domains in the automation JEEframework is removed.

When the automation JEE framework detects that no communication with aparticular domain has occurred for a time interval that is longer than the clean-uptimeout interval defined in the environment variable:com.ibm.eez.aab.domain-removal-hours

it removes the related domain information from the database.

If the automation JEE framework had been stopped for a time, such domains willbe removed only after attempts to contact them have failed.

Whenever the automation JEE framework removes a domain, the operationsconsole is notified about the change and refreshed accordingly.

Restart request timeoutAbout this task

The JEE framework observes resource restart requests until they are completed.After the restart, the resource is online. In some other situations, the restart doesnot finish. For example, a restart request is send to resource A. Resource A has adependency relationship to resource B. This dependency relationship inhibits tostop resource A. In this case, the restart request waits until B changes its state.Pending restart requests are removed after they timed out. You can find thetimeout value in the environment variable:com.ibm.eez.aab.resource-restart-timeout-hours

Method invocation timeout between the automation Java EEframework and the automation adaptersAbout this task

A timeout value can be set in order to control how long an operation between theautomation JEE framework and the automation adapters may take. Theenvironment variable com.ibm.eez.aab.invocation-timeout-seconds is used todefine this timeout value.

The value of this environment variable should be at least 15 seconds less than thevalue of the WebSphere ORB request timeout property. Otherwise,"CORBA.NO_RESPONSE: Request timed out" errors may be encountered by theoperations console or the automation engine if an operation takes longer than thetime interval specified by the ORB request timeout. The default value for theWebSphere ORB request timeout is 180 seconds. The ORB request timeout propertycan be changed from the WebSphere administrative console. To view or change theproperty, open the WebSphere administrative console and navigate to Servers >Server Types > WebSphere Application Servers > server1 > Container Services >ORB service. See the WebSphere documentation for more information about theORB request timeout property.


The com.ibm.eez.aab.invocation-timeout-seconds variable is used for thecommunication with all automation adapters. There is no individual timeout valueper automation adapter.

Note: The communication with the end-to-end automation engine does notsupport method invocation timeout. This means that either the connection cannotbe established, in which case the operation returns with an exception immediately,or the operation will continue until a connection is established.

Modifying the environment variables for the automation Java EEframeworkAbout this task

The current value of each variable is displayed when the application EEZEAR isstarted. Look for messages EEZJ1004I, EEZJ1005I, EEZJ1006I in the WebSphereApplication Server log (SystemOut.log).

If the default values of the environment variables are not appropriate for yourenvironment, you can change them by performing these steps in the WebSphereadministrative console:1. Log on to the WebSphere administrative console.2. Click Servers —> Server Types —> WebSphere application servers --> server1

—>

Server Infrastructure —> Java and Process Management —> ProcessDefinition —>

Additional Properties —> Java Virtual Machine

Additional Properties —> Custom Properties

3.

Click New to create a new variable, or select an existing variable to change itsvalue.

4. Enter values for Name (com.ibm.eez.aab.<variable_name>) and Value(<new_value>). You can also enter a description.

5. Save your changes.

WebSphere Application Server must be restarted for the changes to take effect.

Watchdog for infrastructure - A mechanism for testingconnectivity to OMNIbus and GDPSAbout this task

If an attempt to deliver an automation event to one of the event consumersOMNIbus, GDPS, or the GDPS backup fails, then event forwarding to that failingconsumer is disabled. Instead, the automation JEE framework regularly attempts todeliver an event to the failing consumer. This procedure ensures that the (typicallyvery time-consuming) failing event delivery attempts are not blocking the regularwork of the automation manager. The retry interval for this event delivery is up to10 minutes, and it is not configurable.

Whenever the System Automation manager attempts to deliver an event to adisabled event consumer one of these messages is logged:v EEZJ0039E: "Sending events to OMNIbus is currently disabled since an earlier

attempt to deliver an event to OMNIbus failed. The end-to-end JEE frameworkregularly tries to send an event and enables sending events to OMNIbus againas soon as the retry operation succeeds."


v EEZJ0040E: "Sending events to GDPS is currently disabled since an earlierattempt to deliver an event to GDPS failed. The end-to-end JEE frameworkregularly tries to send an event and enables sending events to GDPS again assoon as the retry operation succeeds."

Modifying the time zone settings for the operations consoleAbout this task

The times stamps that are displayed on the operations console are derived fromthe time zone settings of the operating system on the system on which the IBMDashboard Application Services Hub server is installed. If the times in the timestamps differ from the local time at your location, check the time zone settings onyour IBM Dashboard Application Services Hub server.

The time settings can usually be set with the configuration tools that are providedwith the operating system:v On AIX, you can configure time settings with the smit or smitty system

configuration tool. Use the menu entries System environments —>Change/Show Date and Time to adjust the time settings.

v On SuSE Linux, you can use the yast2 or yast system configuration tools. Usethe menu entries System > Date and Time.

v On Red Hat Linux distributions, you can use the configuration toolsredhat-config-time or system-config-time.

You may have to restart your operating system for the changes to take effect.

Note:

If you have modified the time zone settings as described above but the timesdisplayed in the time stamps on the operations console are still inappropriate, youcan set the environment variable TZ to resolve the problem.

Examples:

v To set the time zone for Berlin, Germany, use the following command:export TZ="Europe/Berlin"

v To set the time zone to US Eastern Standard Time, use the following command:export TZ="US/Eastern"

WebSphere Application Server cannot connect to DB2About this task

When you receive an error message indicating that WebSphere Application Servercould not establish a connection to the automation manager database, check first ifthe database server is started. If it was not started, start the database server. If theSystem Automation operations console does not recover within two minutes,restart WebSphere® Application Server.

If the DB2 database server was started already this may indicate that the DB2 portnumber is not specified correctly in the WebSphere administrative console.

To verify if the DB2 port number is specified correctly, run the following steps:1. On the DB2 server system, check which port number DB2 is using. On Linux,

for example, use the netstat command to obtain the following information:


sys1:~ #netstat -atnp | grep db2tcp 0 0 0.0.0.0:50001 0.0.0.0:* LISTEN 8714/db2sysctcp 0 0 x.x.x.x:50001 y.y.y.y:38306 ESTABLISHED 8714/db2sysctcp 0 0 x.x.x.x:50001 z.z.z.z:42614 ESTABLISHED 8714/db2sysc

In the example, the correct DB2 port number is 50001.2. In the WebSphere administrative console, navigate to Resources>JDBC>Data

sources >EAUTODBDS and check whether the port number is specifiedcorrectly in the field Port number.

Critical exceptions in the WebSphere Application Server logfile

About this task

If the automation domain topology does not look as expected in the SystemAutomation operations console, check the WebSphere Application Server log filefor one or multiple of the following exceptions or stack trace fragments:

java.lang.IllegalMonitorStateException: JVMLK002: current thread not owner

CNTR0019E: EJB threw an unexpected (non-declared) exception during invocationof method "findByPrimaryKey". Exception data: java.lang.NullPointerException

atcom.ibm.ejs.container.activator.UncachedActivationStrategy.atActivate(

UncachedActivationStrategy.java(Compiled Code))[...]at com.ibm.eez.aab.subscription.EJSLocalCMPEEZDomainSubscriptionHome_25634d48.findByPrimaryKey(

EJSLocalCMPEEZDomainSubscriptionHome_25634d48.java(Compiled Code))at com.ibm.eez.aab.EEZDomainSessionBean.unsubscribeAll(EEZDomainSessionBean.java(Compiled Code))

CNTR0019E: EJB threw an unexpected (non-declared) exception during invocationof method "findByPrimaryKey". Exception data:

com.ibm.websphere.cpi.CPIException: ; nested exception is:java.lang.ClassCastException: com.ibm.eez.aab.EEZDomainSessionBean[...]at com.ibm.eez.aab.subscription.EJSCMPEEZDomainSubscriptionHomeBean_25634d48.findByPrimaryKey_Local(

EJSCMPEEZDomainSubscriptionHomeBean_25634d48.java(Inlined Compiled Code))[...]at com.ibm.eez.aab.EEZDomainSessionBean.unsubscribeAll(EEZDomainSessionBean.java(Compiled Code))

To resolve the problem, run the following steps:1. Disable the just-in-time compiler (JIT) of the WebSphere Java Virtual Machine

(JVM)2. Restart WebSphere Application Server

If the domain topology still does not look like expected, deactivate the end-to-endautomation policy and activate it again.

OutOfMemoryError in the WebSphere Application Server logfile

About this task

An OutOfMemoryError may occur if a large amount of data is returned from afirst-level automation domain. Depending on the situation, the error may becomevisible on the operations console or in the WebSphere Application Server messagelog file.


Perform the following steps to increase the JVM heap size:1. Log on to the WebSphere administrative console.2. Navigate to Servers > Server Types > WebSphere Application Servers >

server1 > Server Infrastructure > Java and Process Management > Processdefinition > Additional Properties > Java Virtual Machine.

3. Set the value to at least 768 MB. Refer to the WebSphere Application Serveronline documentation for more information about how to determine theoptimum value for the maximum heap size, depending on the availablephysical memory.

4. Save your changes. WebSphere Application Server must be restarted for thechanges to take effect.

"Unable to set up the event path..." error message isdisplayed in the IBM Dashboard Application Services Hub

About this task

When you try to connect the operations console the following error message isdisplayed in the IBM Dashboard Application Services Hub:Unable to set up the event path between the operations console

and the management server:CWSIA024E: An exception was received during the call to the method

JmsManagedConnectionFactoryImpl.createConnection:com.ibm.websphere.sib exception SIRexourceException:

CWSIT0006E: It is not possible to contact a messaging engine in bus EEZBus

This may indicate a problem with the DB2 instance account for the end-to-endautomation management databases. To check if this is the case, check whether thepassword for the DB2 instance account has expired or is incorrect.

EEZBus is not startedAbout this task

The EEZBus is a sub-component of the automation JEE framework that runs withinWebSphere Application Server. There are several potential reasons why the EEZBuscannot be started. The reasons and proposed actions are described in the followingtopics.

EEZBus is not started due to a security problemAbout this task

If the EEUBus cannot be started, this may indicate a problem with the DB2instance account for the end-to-end automation management databases, regardlessof whether you are using DB2 or LDAP as the user registry.

In such a case, one or more of the following symptoms may occur:

v On the messaging engine panel of the WebSphere administrative console Serviceintegration > Buses > EEZBus > Messaging engines, you can see that theEEZBus is not started. When you try to start the bus, the following errormessage is displayed:The message engine <node_name.server_name> EEZBus cannot be started.

v Message "EEZD0010E" appears in the automation engine log file msgengine.log.v If you are using DB2 as the user registry, the following exception appears in the

WebSphere Application Server log file:


00000f1d FreePool E J2CA0046E:Method createManagedConnectionWithMCWrapper caught an exceptionduring creation of the ManagedConnection for resource jms/

EEZTopicConnectionFactory,throwing ResourceAllocationException.Original exception: javax.resource.ResourceException:CWSJR1028E: An internal error has occurred.The exception com.ibm.websphere.sib.exception.SIResourceException:CWSIT0006E: It is not possible to contact a messaging engine in bus EEZBus.was received in method createManagedConnection.

v If you are using LDAP as the user registry, the following exception appears inthe WebSphere Application Server log file:000000a2 FreePool E J2CA0046E:Method createManagedConnectionWithMCWrapper caught an exceptionduring creation of the ManagedConnection for resource jdbc/EAUTODBDS,throwing ResourceAllocationException.Original exception: com.ibm.ws.exception.WsException:DSRA8100E: Unable to get a XAConnection from the DataSource.with SQL State : null SQL Code : -99999

To eliminate a problem with the DB2 instance account as the cause, check thedatabase connection from the WebSphere administrative console:1. Select the data source.2. Click Test connection.

If the DB2 instance account for the end-to-end automation management databasescauses the problem, you receive the following message:Test connection failed for data source EAUTODBDSon server <serverName> at node <nodeName> with the following exception:java.lang.Exception: java.sql.SQLException:

Connection authorization failure occurred.Reason: password invalid. DSRA0010E: SQL State = null, Error Code = -99,999.

EEZBus is not started because an internal database is in aninconsistent stateAbout this task

Check if the message log file of WebSphere Application Server contains thefollowing message (where sapb11Node01.server1-EEZBus must be replaced with themessaging engine name based on the node name of your WebSphere ApplicationServer installation) :[3/1/06 11:52:37:847 CET] 00000019 SibMessageE [EEZBus:sapb11Node01.server1-EEZBus]CWSIS0002E:The messaging engine encountered an exception while starting.Exception: com.ibm.ws.sib.msgstore.PersistenceException:CWSIS1501E:The data source has produced an unexpected exception:java.sql.SQLException: Failed to create database’/opt/IBM/WebSphere/AppServer/profiles/default/databases/com.ibm.ws.sib/sapb11Node01.server1-EEZBus’,see the next exception for details.DSRA0010E: SQL State = XJ041, Error Code = 40,000DSRA0010E: SQL State = XJ041, Error Code = 40,000

If this message exists, check if the directory described in the message exists in thefile system. If it does, complete the following steps:v Stop the WebSphere Application Server.v Rename (or remove) the directory described in the message.v Start the WebSphere Application Server.


v Verify in the WebSphere Application Server message log that the error messageshown above does no longer appear and that the EEZBus was startedsuccessfully:CWSID0016I: Messaging engine sapb11Node01.server1-EEZBus is in state Started.

No System Automation events received in the OMNIbus eventconsole

About this task

If no events from System Automation Application Manager are received in theevent console then perform the following steps:v Verify that WebSphere Application Server is runningv Verify that the event server is running.v If you are using OMNIbus as event server, verify that OMNIbus has been

configured to accept Application Manager events as described in SystemAutomation Application ManagerInstallation and Configuration Guide.

v If you are using Tivoli Enterprise Console as event server:Ensure that the SystemAutomation.baroc file is known to Tivoli EnterpriseConsole. For information on how to import, compile, load, and activate theBAROC file on the Tivoli Enterprise Console server, refer to Chapter " Rule basemanipulation procedures using the rule builder" in the IBM Tivoli EnterpriseConsole® Rule Developer’s Guide Version 3.9, SC32-1234 at http://publib.boulder.ibm.com/tividd/td/tec/SC32-1234-00/en_US/PDF/ecodmst.pdf.

v Start the end-to-end automation configuration tool and verify that the check boxEnable OMNIbus EIF event publishing is selected on the Event Publishing taband that the event server host name and port number are specified correctly.

v Restart the WebSphere Application Server.v Verify that an event related to the start of System Automation Application

Manager is displayed in the event console.

The end-to-end automation manager fails to initializeAbout this task

The message EEZJ0030E The end-to-end automation manager is not fullyinitialized and refuses to accept requests. The followingsubcomponents are not yet initialized: [EventHandlerBean] may appearwhen logging in on the operations console. It may also appear in the message logof the end-to-end engine. This message indicates that the initialization phase of theend-to-end automation manager JEE framework has not yet completed after arestart. Normally, this message will not show up again if you login again after ashort period of time. Internally, the automation JEE framework regularly tries toinitialize the missing components.

However, there are situations when this initialization step never completes. Forexample, this may occur when OMNIbus event forwarding for System AutomationApplication Manager is enabled but the OMNIbus event server cannot be reached.In this case, the communication layer does not raise an exception by itself butwaits for a timeout. In addition, a transaction timeout may occur before thecommunication timeout is reached.

Similarly, if Distributed Disaster Recovery with GDPS is used, this situation mightoccur if GDPS cannot be reached.


http://publib.boulder.ibm.com/tividd/td/tec/SC32-1234-00/en_US/PDF/ecodmst.pdf

http://publib.boulder.ibm.com/tividd/td/tec/SC32-1234-00/en_US/PDF/ecodmst.pdf

In addition, the WebSphere Application Server process may be restartedautomatically.

Solution:

If OMNIbus event forwarding is required, validate the firewall setup and ensurethat the OMNIbus event server port can be reached from the system where theSystem Automation end-to-end automation manager is installed.

If GDPS event forwarding is required, validate the firewall setup and ensure thatthe primary and backup GDPS server ports can be reached from the system wherethe System Automation end-to-end automation manager is installed.

The following table shows the sub-components that may be listed within messageEEZJ0030E, and the respective troubleshooting actions:

Table 2. Sub-components implicated by message EEZJ0030E

Subcomponent name Solution

AutomationProperties Ensure that the automation JEE framework has read accessto the properties file eez.automation.engine.propertiesthat is located in the EEZ_CONFIG_ROOT directory. For moreinformation, refer to Tivoli System Automation ApplicationManager, Installation and Configuration Guide.

DB2 Ensure that the DB2 instance to be used by theautomation JEE framework is started. See “WebSphereApplication Server cannot connect to DB2” on page 14 fordetails. If you just upgraded from an earlier release ofSystem Automation Application Manager, and if you areusing a remote DB2 server, then refer to Tivoli SystemAutomation Application Manager, Installation andConfiguration Guide for instructions regarding any requiredupgrades of the automation database. After you haveresolved the problem, restart WebSphere ApplicationServer.

EventHandlerBean See “EEZBus is not started” on page 16.

FLAEventReceiver Transient state only. Indicates that the subcomponent thatreceives events from first-level automation domains hasnot been initialized yet. If the problem persists, restartWebSphere Application Server. If this does not solve theproblem, check the WebSphere Application Server logsand the System Automation Application Manager installerlogs for more details related to the first-level automationresource adapter.

ManagedDomainsRegistry Transient state only, or accompanied by subcomponent"DB2". Check the solution for that subcomponent first.

ServerConfigCache Transient state only. Indicates that the automation JEEframework has not yet read the WebSphere ApplicationServer configuration properties that the end-to-endautomation manager needs to know.

StartupBean Transient state only. If it persists, restart WebSphereApplication Server.


Table 2. Sub-components implicated by message EEZJ0030E (continued)

Subcomponent name Solution

WatchdogBean Transient state only. The WatchdogBean is the lastcomponent that gets started. After all other componentsare started successfully, then this component refreshes thestates of the automation domains and verifies if thepreviously known nodes still exist and if they are stillmapped correctly to the hardware (optional). This processcan take up to minute. If it persists, restart WebSphereApplication Server.

RestartRegistry Transient state only. Indicates that the in-memory registryof pending restart requests has not yet been initialized.

Troubleshooting EEZIMEARAbout this task

System Automation Application Manager deploys several enterprise applications inWebSphere Application Server. One of these applications is called EEZIMEAR. Itprovides a web service interface to a subset of the functionality provided by theautomation JEE framework. This web service interface is intended to be usedprimarily by IBM Service Management applications. As long as you do not usesuch web service client applications, you may ignore any errors that may beproduced by the EEZIMEAR application.

Creating IdML booksAbout this task

There are only a few situations that result in no IdML book being created. Thesecan be grouped into configuration issues and runtime issues. The following tablelists the configuration issues (first two lines), runtime issues (next 3 lines), and theregular scenario without errors (last two lines).

Table 3. Issues when creating IdML books

Condition IdML Book

IdML book directory does not exist, or userhas no write access to it

No book created

Remote book creation:

v Remote system unavailable

v Userid or password incorrect

No book created

WebSphere Application Server unavailable No book created

EEZEAR application not started No book created

end-to-end automation engine not started No book created

No end-to-end automation policy active Book created that only contains MSS andend-to-end domain objects

end-to-end automation policy active Book created that contains MSS, end-to-enddomain objects, all resources andrelationships

Note: If the end-to-end automation engine is running with no automation policyactive, the resulting discovery book is almost empty. If this is loaded into TADDM,previously existing configuration items may be deleted.


Troubleshooting command shell problemsAbout this task

Command shell hangs in shell mode - no input is possibleAbout this task

The command shell supports a command history function which can be exploitedby using the scroll-up and scroll-down keys. This functionality is implemented byparticular native input libraries. On some systems (depending on the distributionand version, and the shell used), this native code may lead to problems, forexample:v EEZCS fails with a javacorev No input is possible (not even CTRL-C)

In order to circumvent this problem, you can disable the command historyfunction by setting the HISTORY value to "false" in the file <EEZ_INSTALL_ROOT>/bin/eezcs.sh. This is the default setting in eezcs.sh which you need to change:# Set HISTORY to false if you experience input problemsHISTORY=true

Handling multibyte characters in the command shellAbout this task

Problem:

The command shell does not accept commands that contain multibyte characters,for example resource names that contain Chinese characters. If you enter acommand that contains multibyte characters, the command shell indicates that theresource does not exist.

Solution:

Disable the command history. Set the history value to HISTORY=false in the file<EEZ_INSTALL_ROOT>/bin/eezcs.sh.

Troubleshooting automation engine problemsAbout this task

eezdmn command hangs during start up or shut downAbout this task

If the eezdmn command is hung during start up or shut down of the automationengine, for example, because of an extreme load on the automation manager, youreceive a timeout message after 60 seconds.

You can adjust the timeout value by adding the parameter EEZDMNCLIREADTIMEOUTto the script file eezdmn.sh and setting it to an appropriate value. The timeoutvalue must be specified in milliseconds. For example, to receive a timeout messageafter 30 seconds, set the value of the parameter to 30000.

End-to-end resource state temporarily Starting or Unknown

If the end-to-end automation policy XML file contains dynamic resource referencesthen the automation manager re-activates an automatically modified version of theend-to-end automation policy. This applies each time when one or multiple


matching first-level automation resources are added or removed. During theprocess of end-to-end policy re-activation, the end-to-end automation resources canshow the state Starting or Unknown temporarily.

No operator action is needed. The operations console refreshes automatically andshows the actual states of the resources.

Troubleshooting Distributed Disaster Recovery problemsAbout this task

GDPS agent problemsAbout this task

Use the following information to troubleshoot problems with the GDPS agent:v Logs and traces are written to the system log by the eezgdpsagent script itself.v Logs and traces are written to msgFlatEngine.log and traceFlatEngine.log in

the Tivoli Common Directory by the automation engine command shell (eezcs)part of the GDPS agent.

v Review the output file <EEZ_CONFIG_ROOT>/eezgdpsagent.out (the default is/etc/opt/IBM/tsamp/eez/eezgdpsagent.out) for error messages if initializationwith the eezgdpsagent -start command fails.

v Use the information in Table 4, which lists the GPDS agent return codes.

Note: This table does not apply to the eezgdpsagent status command. For thespecific return codes of this command, see “Controlling the GDPS agent” onpage 96.

Table 4. GPDS agent return codes

Return code Command used Description Comment

0 All Successful Command finished successfully.

1 Health check Failed The health check command failed.Ensure that the automationengine, WAS, and the JEEFramework are started.

2 All except -shutd Timeout Timeout when waiting for signalfrom command shell. Check thelogs.

3 – Commandunknown

Invalid command specified.

4 -start mkfifo commandfailed

Not able to create fifo pipe. Checkpermissions of directory<EEZ_CONFIG_ROOT> andensure that the corresponding useris allowed to write to thisdirectory.

5 -shutd rm commandfailed

Not able to remove file. Checkpermissions of directory<EEZ_CONFIG_ROOT> andensure that the corresponding useris allowed to write to thisdirectory.


Table 4. GPDS agent return codes (continued)


6 -start Write failure Not able to write to outputdirectory. Check permissions ofdirectory <EEZ_CONFIG_ROOT>and ensure that the correspondinguser is allowed to write to thisdirectory.

7 All except -shutd Initialization notperformed

Initialization has not beenperformed or failed. Execute thecommand eezgdpsagent -start,or use the end-to-end HA policy.

13 All except -startand -shutd

Incorrect flag Incorrect flag specified.

16 Start/stopworkload, poweron/off systems

Error handling arequest

Error occurred when processing arequest. Check /var/log/messages.

17 All except -startand -shutd

Automationmanager failed

Not able to obtain data from theautomation manager or engine.Check the WAS log and the log ofthe end-to-end automationdomain.


Cluster set isunknown

The specified cluster set does notexist.


Site is unknown The specified site does not exist.


Domain is notaccessible

For starting or stoppingworkloads this means that thecorresponding domain is shutdown, the FLA adapter is stoppedor the network is down.

For powering on or off systems,this means that the hardwareadapter is not running.

24 1 Start/stopworkload, poweron/off systems

Disaster recoverychoice grouperror

The compound state of the groupof business-critical or discretionaryworkload is in error or fatal. Usethe operations console to checkthe failed resources.

25 Start workload Startingworkload onmultiple sites

The business-critical workload isalready started on the other site.

26 – – Reserved.


Receivedapplicationexception

Check the log file of theend-to-end automation domain.


Table 4. GPDS agent return codes (continued)


28 1 Start/stopworkload, poweron/off systems

Disaster recoverychoice hassuspendedmembers

One or more resources in thegroup of business-critical ordiscretionary workload aresuspended from automation.Resume automation for theseresources first.

1. Note that these return codes can be overruled by promotion.

v Ensure that the user ID for using the automation engine command shell isspecified in the Command shell tab of the configuration dialog and that it hassufficient rights (that is, it has the EEZOperator role).

v Ensure that the WebSphere Application Server is up and running.v Verify that the command shell is working using the command eezcs, for

example:~ # eezcsEEZCS[eezadmin@FriendlyE2E]>lsclustersetsDisplaying Clustersets:

Clusterset GblFEClusterSAP:

SiteIndex = 1WorkloadType = bcDesiredState = OnlineCompoundState = WarningActionStatus = NotApplicable

WorkloadType = discDesiredState = OnlineCompoundState = WarningActionStatus = NotApplicable



EEZCS[eezadmin@FriendlyE2E]>quitGoodbye.

Troubleshooting PowerHA adapter problemsAbout this task

Use this topic for troubleshooting problems you experience when working with theHACMP™ adapter.

PowerHA adapter log filesAbout this task

Increasing the trace logging level:About this task

If your trace is not detailed enough to analyze a problem and the problem can berecreated, it may be useful to increase the trace logging level:


1. Invoke the adapter configuration dialog using cfghacadapter.2. On the main window of the configuration dialog, click Configure.3. Select the Logger tab.4. Set the Trace logging level to Maximum.5. Click Apply. The new setting takes effect immediately.

For more information about the PowerHA adapter configuration dialog, see theInstallation and Configuration Guide.

Log file locations:About this task

The PowerHA adapter log files are located in the Tivoli Common Directory:v Default location: /var/ibm/tivoli/commonv PowerHA adapter-specific subdirectory structure in the Tivoli Common

Directory:– eez/ffdc – Contains the First Failure Data Capture files (if the FFDC

recording level is not set to Off in the adapter configuration dialog)– eez/logs – Contains the PowerHA adapter trace file:

- traceFlatAdapter.log

PowerHA adapter does not startAbout this task

Possible causes:v PowerHA level is lower than 5.3.0.5

To check, use: lslpp –l cluster.es.server.utilsv Cluster services have not been started

Start the services using smitty: hacmp —> C-SPOC —> Manage...

PowerHA adapter terminatesAbout this task

Cluster services terminated while the PowerHA adapter was runningIf the adapter is automated, it should restart automatically on next prioritynode where cluster services run.

Adapter attempts to start but terminates againThis may indicate that the adapter is not configured correctly. Forinformation about configuring the adapter, see System AutomationApplication Manager Installation and Configuration Guide.

PowerHA adapter fails to connect to the end-to-end automationmanager hostAbout this task

Make sure the firewall allows connections in both directions.

Check with netstat if tcp sessions are established:v whether the adapter listens on the request port (default port is 2001)v whether the end-to-end automation manager listens on the event port (default

port is 2002)

If no sessions are establish try to set up TCP sessions, for example using telnet:


v telnet <e2e-host> 2002 from the system running the PowerHA adapter, orv telnet <hacmp adapter address> 2001 from the system running the System

Automation Application Manager installation.

where <e2e-host> is the IP address or fully qualified domain name of the systemhosting the System Automation Application Manager installation and <hacmpadapter address> is the IP address or fully qualified domain name of the PowerHAadapter. If a session setup is not possible using telnet check again that the firewallallows this.

PowerHA resource groups cannot be started or stoppedAbout this task

To bring PowerHA resource groups online or offline, the PowerHACluster-SubState must be STABLE. If the Cluster-SubState is UNSTABLE, which istypically the case during resource state transitions, Bring online and Bringoffline actions against resource groups are not accepted. You can view theCluster-Substate on the Additional tab of the domain properties page for thePowerHA cluster. The information on the page is not updated automatically. To seeif the Cluster-SubState has changed, open the context menu of the PowerHAdomain in the operations console and select Advanced > Release cachedresources. When the Cluster-Substate has changed to STABLE, Bring online andBring offline actions can run again against resource groups.

Troubleshooting FOC adapter problemsUse this topic for troubleshooting problems you experience when working with theMicrosoft Failover Cluster (FOC) adapter.

FOC adapter log filesThis is where the adapter log files are located:v Tivoli Common Directory

Default location: C:\Program Files\IBM\tivoli\commonFOC adapter-specific subdirectory structure in Tivoli Common Directory:– eez\ffdc – Contains the First Failure Data Capture files (if the FFDC

recording level is not set to Off in the adapter configuration dialog)– eez\logs – Contains the FOC adapter log files:

- msgMSCSAdapter.log

- traceMSCSAdapter.log (if trace logging level is not set to Off)- eventMSCSAdapter.log (if trace logging level is not set to Off)

v The default adapter installation directory is C:\Program Files\IBM\tsamp\eez\mscs.Subdirectories and files used for troubleshooting:– The file data\eez.release.information.txt is created in the adapter

installation directory when the FOC adapter is started. It contains informationabout service applied to the FOC adapter and about the configuration settingsused.

– The installation log files are located in the subdirectory \install\logs.

FOC adapter does not startFOC adapter does not start

Problem determination:


v The application event log should contain the message "The service SAAM FOC Adapter has been started."

v In the configuration file cfg\mscs.service.properties, uncomment theproperty service-log-file, restart the service, and investigate theresulting file.Ensure to comment the property again before returning to normaloperation.

The SA AM FOC Adapter Service reports the status 'Started' for some secondsand then stops again

v Startup should be completed within 60 seconds.v Refresh the view to see the actual status.

Problem determination:v Investigate the FOC adapter log file msgMSCSAdapter.log.v If no error messages can be found, increase the trace logging level to

Maximum and provide all logs to IBM support.

The file msgMSCSAdapter.log contains the message EEZA0061E indicating thatthe adapter failed to bind to a socket

Possible reason if the FOC adapter service is made highly available usingFOC:v The network name or virtual IP address used for the "Automation

adapter host" is not available during adapter startup

Possible solution:v Check the spelling of the network name or virtual IP address in the

adapter configuration dialog.v Check that there are appropriate "Network Name" / "IP Address"

resources defined in FOC and that they are working properly.v Check that the FOC adapter service resource has a dependency on the

"Network Name" / "IP Address" resources in FOC.

FOC adapter terminatesThe FOC adapter services stops and the log files contain no related error messages.In particular, message "EEZA0104I" does not appear in the FOC adapter log filemsgMSCSAdapter.log. The message indicates that the FOC adapter was successfullystopped.

Problem determination:1. Search for javacore.*.txt files in the subdirectory lib.2. Use Windows tool drwtsn32 to configure dump capturing. Use the following

settings:


3. Try to recreate the FOC adapter termination.4. Provide the data to IBM support.

FOC domain does not joinThe FOC domain does not join within two minutes and the FOC adapter serviceis no longer running

Problem determination:v Investigate the FOC adapter log file msgMSCSAdapter.log.v If no problems can be found, increase the trace logging level to

"Maximum" and provide all logs to IBM support.

The FOC domain does not join within two minutes but the FOC adapter serviceis running

Problem determination and possible causes:v An invalid host name or IP address is specified for the end-to-end

automation management server.v The end-to-end automation management server cannot be reached from

the system running the FOC adapter. To check, use ping, telnet, andtracert commands.

v Determine the network name / IP address the FOC adapter sends to theend-to-end automation management server:– Increase the trace logging level at least to "Minimum", restart the FOC

adapter, investigate the log file eventMSCSAdapter.log.– Locate the latest adapter join event ("EVT_RSN=domainAdapterJoin").

The event contains the required information.v The system running the FOC adapter cannot be reached from the

end-to-end server. To check, use ping, telnet, and tracert commands.

Figure 1. Dr. Watson for Windows settings


Troubleshooting VCS adapter problemsUse this topic for troubleshooting problems you experience when you are workingwith the Veritas Cluster Server (VCS) adapter.

VCS adapter log filesThis is where the adapter log files are located:v Tivoli Common Directory

Default location: /var/ibm/tivoli/common/The log files are written to the following subdirectories of the Tivoli CommonDirectory:– eez/ffdc – Contains the First Failure Data Capture files (if the FFDC

recording level is not set to Off in the adapter configuration dialog)– eez/logs – Contains the VCS adapter log files:

- msgVCSAdapter.log

- traceVCSAdapter.log (if the trace logging level is not set to Off)v The default adapter installation directory is /opt/IBM/tsamp/eez/vcs

Troubleshooting the policy editor

Previously specified domain name not usedIf a policy file is loaded from a policy pool and the policy file contains errors, thedomain name of the domain hosting the policy pool is automatically used for thatpolicy, regardless of what automation domain was specified before.

Mozilla Firefox browser displays special characters incorrectlyIf special characters are incorrectly displayed in the policy editor, select View >Character Encoding > Auto Detect > Universal in the browser menu.

Policy editor does not print out the complete policy on someprintersIf you have a printer driver installed that prints out only a subset of the policywhich fits on the first page instead of printing the policy on multiple pages whichcan be combined to a poster, proceed as follows:

Generate an image of the policy using policy editor functionality. Open this imagein an image editing application. Print the image. Most image editing applicationsare capable to print out large images on multiple pages.

Delay until the list with available policies is displayed.If you want to activate a new policy for an agentless adapter domain and clickedthe Activate New Policy button in the operations console, then it can take longerthan 10 seconds until the policy is activated. The duration time is triggered by:v If the trace level is set to maximum in the Application Manager Common

Configuration dialog, reduce the trace level or turn it off.v If your agentless adapter policy pool contains a large number of policies, or very

large policies, for example greater than 1000 resources, the loading and parsingof these policies is very time intensive. Reduce the number of files, for exampleby removing outdated policies.


Troubleshooting the agentless adapter

Agentless adapter does not startIf there is no agentless adapter domain already defined, the Agentless Adapter willnot start successfully. Define at least one agentless domain using the configurationutility and retry to start the Agentless Adapter.

Agentless adapter log files

Location of the adapter log files:

Tivoli Common Directory The log files are written to the following sub-directories of the TivoliCommon Directory:v

eez/ffdc – Contains the First Failure Data Capture files (if the FFDCrecording level is not set to Off in the adapter configuration dialog)

veez/logs – Contains the agentless adapter log files:–

msgEEZALAdapter.log

–eventEEZALAdapter.log and traceFlatEEZALAdapter.log (if the tracelogging level is not set to Off)

Default adapter installation directory/opt/IBM/tsamp/eez/bin

Agentless adapter fails to connect to the end-to-end automationmanager host

For a local agentless adapter installation check if ports are configured as expected,and TCP sessions are established.

For a remote agentless adapter, perform the same checks as for the local agentlessadapter, and make sure the firewall allows connections in both directions.

Check with netstat if TCP sessions are established:v Whether the agentless adapter listens on the request port (default port is 2001).v Whether the end-to-end automation manager listens on the event port (default

port is 2002) .

For both the local and remote agentless adapter, if no sessions are established tryto set up TCP sessions, for example using telnet:v telnet <e2e-host> 2002 from the system running the agentless adapter.v telnet <agentless adapter address> 2001 from the system running the System

Automation Application Manager installation.

Where <e2e-host> is the IP address or fully qualified domain name of the systemhosting the System Automation Application Manager installation. <agentlessadapter address> is the IP address or fully qualified domain name of the agentlessadapter. If a session setup is not possible using telnet check again that the firewallallows this.


Agentless adapter domain and resource states are not refreshedas expected

If the states of remote resources that are managed by the agentless adapter do notreflect the actual state of the resources within a reasonable time frame thenconsider to tune the agentless adapter domain topology. For more information, seeSystem Automation Application Manager Installation and Configuration Guide.

Analyzing the states of remote resources

If the states of remote resources that are managed via the agentless adapterindicate some issue, see System Automation Application Manager Administrator's andUser's Guide for hints about the potential root cause of the issue based on thecombination of the monitor command return codes and the resource states.

Resource states that are affected by the state of the target node

The following table lists resource states caused by communication problems withthe target node.

Table 5. Resource states that are affected by the state of the target node

Scenario Root cause Resource Observed State

Monitoring consequencesfor resources and targetnode states

Waiting for stateinformation

v after eezaladapter started(last policy activated)

v after new policyactivated

v after subscription isdeleted (unsubscribed)

Observed State

Unknown

Operational State

NoContact

Compound State

Warning

Next resource monitor isstarted with nextsubscription or after nextresource query. Target nodeis also not being monitoreduntil next resource monitoris started.

Communication has beeninterrupted or timed out.

v network problem

v monitor commandtimeout

Observed State

Unknown

Operational State

LostCommunication

Compound State

Error1

Next resource monitor isstarted afterMonitorCommandPeriod.Same for target nodemonitor.

Hosting node is notavailable.

v target node offline

v wrong hostname inpolicy

v no IP address found forhostname

v firewall prevents accessto host

v sshd stopped

Observed State

Unknown

Operational State

SupportingEntityInError

Compound State

Error

Next resource monitor isstarted afterMonitorCommandPeriod.Same for target nodemonitor.


Table 5. Resource states that are affected by the state of the target node (continued)

Scenario Root cause Resource Observed State

Monitoring consequencesfor resources and targetnode states

User credentials areincorrect

v wrong userid orpassword inconfiguration

v password expired

v userid does not exist

v wrong ssh public keys inconfiguration

Observed State

Unknown

Operational State

BrokenResource

Compound State

Fatal

Next resource monitor isstarted after next resetaction. Target node will nolonger be monitored toavoid user ids to berevoked.

Unable to run a commanddefined for the resource.

v command not found

v userid has nopermissions to executecommand

Observed State

Unknown

Operational State

InvalidResource

Compound State

Fatal

Next resource monitor isstarted after next resetaction. Target node willcontinue to be monitored.

Non recoverable error v MP monitor command rc= 3 or 4

v start/stop commandtimeout

v start/stop command rc!= 0 (Failed)

Observed State

see table 40. and 41.

Operational State

NonRecoverableError

Compound State

Fatal

Next resource monitor isstarted after next resetaction. Target node willcontinue to be monitored.

Note:

1. Changed to Error with 4.1.0.0 (Warning until 3.2.2.x).

Observed states that are affected by the state of the target node

The following table lists all observed states for a target node.

Table 6. Observed states that are affected by the state of the target node

Resource Observed StateMonitoring consequences for resources andtarget node states

Unknown If all resources on that node have theoperational state NoContact orBrokenResource.

Offline If at least one resource on that node has theoperational state SupportingEntityInError.

Online All other cases.


For more information about resource states of remote applications, see SystemAutomation Application Manager Administrator's and User's Guide.

InstallationUse this topic for troubleshooting problems you experience when you installSystem Automation Application Manager.

About this task

Silent installation or uninstallation fails due to broken Xconnection

About this task

The creation of a response file for silent installation is done via a graphicalinterface, which requires an X-server on UNIX systems. If you are performing asilent installation on a UNIX system that has console profiles configured thatcontain X-server references, the silent installation may fail with a correspondingerror message:X connection to localhost:10.0 broken (explicit kill or server shutdown).

If this message occurs, open a new session on the system using a profile that doesnot contain any X-server references, and restart the installation.

Installation wizard cannot find WebSphere Application Serveron the system

About this task

WebSphere Application Server must be installed on the system before SystemAutomation Application Manager can be installed. If the installation wizard doesnot detect WebSphere Application Server on the system, or if you installedmultiple instances of WebSphere Application Server on the same system, you canspecify the WebSphere Application Server installation location manually.

Installer cannot detect non-default SOAP portAbout this task

If the default SOAP port settings are changed in the WebSphere AdministratorConsole, the installer cannot detect these. This causes an error window to bedisplayed with the message that the cell could not be retrieved.

Changing the SOAP port via the WebSphere Administrator Console does notupdate the value used by the wsadmin.sh command. This will cause all commandswhich use wsadmin.sh and a SOAP connection to fail.

A quick workaround for this problem is to manually edit the file/opt/IBM/JazzSM/profile/properties/wsadmin.properties and adjust the value ofthe variable com.ibm.ws.scripting.port.

You can change the default ports of WebSphere using an Ant script. For moreinformation, see http://www-01.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.base.doc/ae/tins_updatePorts.html. Using theAnt script avoids the problem as it correctly updates the SOAP port for wsadmin.sh.


http://www-01.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.base.doc/ae/tins_updatePorts.html

http://www-01.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.base.doc/ae/tins_updatePorts.html

Determining the correct DB2 port numberAbout this task

The installation wizard provides a function to retrieve the valid DB2® instance portnumber automatically. If you choose not to use this function, the port number50001 will be displayed in the entry field on the corresponding installation wizardwindow, which is the default port number that is assigned to DB2 during theinstallation of DB2. However, if the port is not free, a different port number isassigned automatically, which is why you need to check if the default port numberis correct.

This is how you can determine the correct DB2 port number:v All operating systems:

– The port number is displayed in the summary window that appears when theDB2 installation is complete.

v You can also determine the port number in this way:1. Log on as the instance user (for example, db2inst1)2. Issue the command db2 get dbm cfg3. Go to the following line:

TCP/IP Service name (SVCENAME) = db2c_DB2

the string after (SCVENAME) = is the DB2 instance port.If the string is numeric, for example, 50000, it is the instance port number. Ifthe string is not numeric, for example, db2c_DB2, look for a string similar todb2c_DB2 50000/tcp in this file:AIX/Linux:/etc/services

DB2 access test hangsAbout this task

If the attempt to access the database does not return (an indeterminate dialog isshown for a very long time), the test may be hung. The DB2 password may beexpired. To resolve the problem, perform these steps:1. End the installer. Because Cancel is not enabled at this point, end the installer

using the kill command. If the installer is killed, files in the system temporarydirectory remain on the system. If desired, you can manually delete the files inthe following way:Delete the directories dirs /tmp/<xxxxxx>.tmp and /tmp/install.dir.<xxxxxx>> (where <xxxxxx> is an arbitrary number)

2. Check if the DB2 password is expired.3. Renew the DB2 password.4. Restart the installation.

DB2 message SQL1035N The database is currently in use.SQLSTATE=57019

About this task

This message may be received after an error during installation. To correct it yourestart DB2 and drop database EAUTODB manually before resuming theinstallation. It may be necessary to use the force option to close DB2.


Using the Configuration problem analysis dialogAbout this task

The Configuration problem analysis dialog assists in handling post-installationconfiguration issues. The Configuration problem analysis dialog is displayed if apost-installation step fails. The dialog is divided into two panels. The panel at thetop displays an introductory explanation and points to the directory that containsthe detailed installation log. The panel at the bottom provides information thatassists to identify the root cause of the problem on the following tabs:v The Step details tab shows the step number, the technical step ID, the return

code of the step, and the step description.v The Executed command tab shows details of the executed command.

After you resolved the issue, you can then click the Retry button to re-execute thestep.

Click the Retry button to re-execute the most recent step. Click the Exit button toquit the installation. If you restart the installation at a later time, the installationresumes at the step that previously failed.

Installing on machines with system resources at or below the minimum requiredlevel can lead to timeouts. For details on the minimum required system resources,see System Automation Application ManagerInstallation and Configuration Guide.Normally, a timeout is not a problem in the configuration phase. A pop-upwindow is displayed with a detailed explanation of why the timeout occurred.Click Retry to perform the step again which timed out previously.

Procedures for troubleshooting an installationAbout this task

If the installation fails, the installation wizard displays an error message.

When an error occurs, immediately archive the installation log files (see “Using thelog file collector utility” on page 37). This ensures that the original log files areretained, which is important should you need to contact IBM Support, and you canuse the archive for your own troubleshooting activities.

An error occurred in the pre-installation phaseIf an error occurs in the pre-installation phase, that is, before the Installbutton was clicked, click the button Save installation log files to collect allinstallation log files. The zip file will be created at the location specified.

An error occurred in the installation phaseTypically, errors only occur in the installation phase if insufficient diskspace is available.

An error occurred in the configuration phaseClick Finish to finish the installation, then change to <EEZ_INSTALL_ROOT>/install and run the log file collector utility. The log zip will be created inthe same directory. For details see “Using the log file collector utility” onpage 37.


Exceptions appear in file eezinstall.logAbout this task

Any NoClassDefFoundError exceptions that appear in the eezinstall.log filebefore the file EEZEAR was deployed can be ignored.

Note: In the last step of the install process the intermediate log is copied to thesubfolder install in the user install directory. This copy omits the messages fromthe installer finish process ( 3 or 4 lines). If these lines are required the originalinstall log should be read. This log file can be found in the tmp directory with aname of the form: install.dir.xxxxxxxx.

Cleaning up from a failed installationAbout this task

Installation can be canceled at any time. Clean up depending on the installationphase when the installation was canceled or when the installation failed:v Installation was canceled or failed before the installation was started: no cleanup

is necessaryv Installation was canceled or failed during the installation phase: Run the

uninstaller to clean up files that were installed on disk.v Installation was canceled during the configuration phase: Installation can be

resumed.If the system has to be cleaned up again, rerun the installer, and then run theuninstaller to undo all configuration steps and to remove all installed files fromdisk.

v Installation failed during the configuration phase: Corrective actions may beneeded before installation can be resumed.To just recover the files if the product was uninstalled but the unconfigurationwas not successful and the files are needed to manually perform the remainingunconfiguration steps: Run the installer with the option -Dfilesonly=true in thiscase, only the files are installed; no configuration is performedBe sure to undo the configuration changes that were made during theinstallation before uninstalling. Otherwise, the configuration changes will beretained and the scripts to remove them are already uninstalled.

v If the uninstallation fails to remove the System Automation Application Managerrelated configuration items in the WebSphere Application Server (WAS) profile,then remove the WAS profile, remove all System Automation ApplicationManager related files, create a new WAS profile, and use the new WAS profilefor a new installation.

Recovering from a lock out situation during installation:

If the installation fails try to uninstall the product and reinstall again. If there-installation fails showing a message like "product is already installed at samelevel", delete the file /var/.com.zerog.registry.xml.

Note: .com.zerog.registry.xml is a hidden file.Make sure that no other product needs this file. Browse the file and verify if youhave no other entries that point to different products. Otherwise contact supportfor further recommendations.


Using the log file collector utilityAbout this task

When an error occurs, use the log file collector utility to collect the log files thatwere written during the installation. The utility generates an archive that you canuse for your own troubleshooting activities and send to IBM Support if you cannotresolve the error.

Perform these steps to run the log file collector utility:1. Change the directory to <EEZ_INSTALL_ROOT>/install.2.

Issue the command collectinstallerlogs.sh.The command can be invoked with the option -D to copy all logs (in case Javais not available). The directory tree created can then be packed manually.The name of the file that is created by the utility iseezinstallerlogs_<timestamp>.zip.On AIX and Linux you can invoke the command with the option tar to use tarrather than jar for packing.The resulting archive has the following directory structure:- EEZ_logs- cfg: configuration files (for the automation engine, etc.)- logs: eezinstall.log, etc.- sh: scripts used by installer- WAS_logs- logs: general WAS server logs- <server name>: logs for the selected WebSphere Application Server

Gathering information for IBM SupportAbout this task

If you cannot resolve an installation problem, send the installation log file archiveto IBM support (see “Using the log file collector utility”).

Troubleshooting the installation of the FOC adapterAbout this task

Use this topic for troubleshooting problems you experience when installing orconfiguring the FOC adapter.

FOC adapter installation failsAbout this task

If the installation wizard indicates a problem, check the installer output and thefollowing files for error messages:v The log files in the subdirectory \install\logs.v IBM Tivoli System Automation Application Manager MSCS

Adapter_install_log.log.v mscsinstall_<date_time>.log


FOC Adapter configuration dialog problems occurAbout this task

A problem occurs using the adapter configuration dialogProblem determination:v The file cfgmscsadapter.bat contains a command for launching the

configuration dialogv The file contains a duplicate of this command with additional option

-DEBUG which enables diagnostic output. Enable this version of thecommand and launch the configuration dialog again.

The Apply button on the Logger tab cannot be clickedPossible cause: The FOC adapter is not running.

Configuration files cannot be replicatedPossible causes:v The FOC cluster is not available.v The cluster contains only a single node.

Replication fails with the message "Login on target node failed"Possible cause: The domain user ID was not specified in the correct format,which is <user_ID>@<domain_name>.

FOC adapter uninstallation failsAbout this task

Uninstaller indicates an uninstallation problemThis may occur if the FOC adapter service is still running duringuninstallation.

Note: If the FOC adapter service is made highly available using FOC, FOCmay restart or fail over the service.

Uninstalling the FOC adapter manuallyAbout this task

Perform the following steps in sequence:1. Stop the FOC adapter service and ensure that it is not restarted by FOC on the

system where the manual uninstallation is performed.2. Manually remove the service by issuing the command:

sc.exe delete "SA AM MSCS Adapter"

3. Manually remove the service JaasLogon by issuing the following commands:cd <adapter_installation_directory>\jre\binJaasLogon.exe –remove

4. Delete the adapter installation directory.5. If no other Tivoli System Automation product is installed on the system you

can delete the eez subdirectories of the Tivoli Common Directory.6. If no other products installed with InstallAnywhere remain on the system, go

to C:\Program Files\Zero G Registry and delete the complete directory. Ifother InstallAnywhere installer products are installed you must remove allentries related to FOC Adapter from the file .com.zerog.registry.xml.For the following example, all sub-elements of <products> and <components>must be deletedExample:


<?xml version="1.0" encoding="UTF-8"?><registry install_date="2012-09-27 13:13:59" version="1.1"

last_modified="2012-09-29 16:26:20"><products>

<product name="System Automation MSCS Adapter"id="655d44e8-1ee4-11b2-9a39-e02fa5b28587"version="3.2.2.0" copyright="2012" info_url="" support_url=""location="C:\Program Files\IBM\tsamp\eez\mscs"last_modified="2012-09-29 16:26:20">

<vendor name="IBM" id="4b89a1a0-1ee0-11b2-8c02-f523645d652c"home_page="" email=""/>

<feature name="Application" last_modified="2010-09-29 16:26:20"><![CDATA[This installs the application feature.]]><component ref_id="655d44e8-1ee4-11b2-9a39-e02fa5b28587"

version="3.2.2.0"location="C:\Program Files\IBM\tsamp\eez\mscs\.version"/>

<component ref_id="0df5155e-1ee4-11b2-9b2c-e02fa5b28587"version="1.0.0.0"location="C:\Program Files\IBM\tsamp\eez\mscs\.jre"/>

</feature></product>

</products><components>

<component id="655d44e8-1ee4-11b2-9a39-e02fa5b28587"version="3.2.2.0" name="Common"location="C:\Program Files\IBM\tsamp\eez\mscs\.version"vendor="IBM"/>

<component id="0df5155e-1ee4-11b2-9b2c-e02fa5b28587"version="1.0.0.0"name="InstallAnywhere VM Component"location="C:\Program Files\IBM\tsamp\eez\mscs\.jre"vendor="IBM"/>

</components></registry>

ConfigurationUse this topic for troubleshooting problems you experience when you configureSystem Automation Application Manager.

About this task

SSL configuration problemsAbout this task

If problems occur with the SSL setup, you can use the information in this topic forroot cause analysis.

SSL configuration error messages are stored in the following paths:v On the Application Manager side, the messages are stored in the WebSphere

Application Server log file:<WAS_PROFILE>/logs/server1/SystemOut.log

v On the Adapter side in the log file:/var/ibm/tivoli/common/eez/logs/msg<ADAPTER_TYPE>Adapter.log

The following list describes the most common SSL errors with their correspondingerror messages.1. Corrupt or empty SSL truststore file specified

a. Messages in the Adapter log:


Table 7. Corrupt or empty SSL truststore file - Adapter messages

Message Identifier Exception Text

EEZA0038E Unrecognized keystore entry

EEZA0038E Received fatal alert: certificate_unknown

EEZA0022E No trusted certificate found

EEZA0038E Certificate chain is null

b. Messages in the Application Manager WebSphere log:

Table 8. Corrupt or empty SSL truststore file - Application Manager messages


EEZA0038E Invalid keystore format

EEZA0022E Received fatal alert: handshake_failure

EEZJ0101E Embedded message EEZI0015E: Unable toconnect to the adapter

User response: Check SSL truststore files on Adapter and Application Managerside.

2. Corrupt or empty SSL keystore file specified


Table 9. Corrupt or empty SSL keystore file - Adapter messages


EEZA0038E No trusted certificate found



EEZA0032E Embedded message EEZA0033E: Unable tocreate socket factory object

EEZA0105I Embedded return code rc=20: Adapter hasbeen stopped due to initialization failure


Table 10. Corrupt or empty SSL keystore file - Application Manager messages




EEZJ0101E Embedded message EEZI0046E: SSLconnection could not be established


User response: Check SSL keystore files on Adapter and Application Managerside.

3. Wrong SSL keystore password specified



Table 11. Wrong SSL keystore password specified - Adapter messages


EEZA0038E Keystore was tampered with, or passwordwas incorrect

EEZA0032E Embedded message EEZA0033E: Unable tocreate socket factory object

EEZA0105I Embedded return code rc=20: Adapter hasbeen stopped due to initialization failure


Table 12. Wrong SSL keystore password specified - Application Manager messages


EEZA0038E Keystore was tampered with, or passwordwas incorrect

EEZA0033E Unable to create socket factory object


User response: Check SSL keystore password on Adapter and ApplicationManager side.

4. Wrong SSL certificate alias specified


Table 13. Wrong SSL certificate alias specified - Adapter messages


EEZA0038E Certificate chain is null

EEZA0047E No available certificate corresponds to theSSL cipher suites which are enabled

EEZA0047E No cipher suites in common

EEZA0105I Embedded return code rc=12: Adapter hasbeen stopped because initial contact failed


Table 14. Wrong SSL certificate alias specified - Application Manager messages


EEZA0022E Received fatal alert: handshake_failure


User response: Check SSL certificate alias on Adapter and Application Managerside.

5. Missing SSL configuration on one side



Table 15. Missing SSL configuration on one side - Adapter messages


EEZJ0101E Embedded message EEZI0021E: Using SSL isrequired for all first-level automationadapters but not enabled for this particularadapter

Reason: SSL was configured only at the Application Manager side andenforce use of SSL was enabled, or the adapter was not restarted after SSLwas configured.User response: Check the SSL configuration on the adapter side and restartthe adapter.


Table 16. Missing SSL configuration on one side - Application Manager messages


EEZA0038E No such file or directory


Reason: SSL was only configured at the adapter side, or WebSphere was notrestarted after SSL was configured.User response: Check the SSL configuration at the Application Manager sideand restart WebSphere.


Chapter 2. Reference

Learn more about how to use System Automation Application Manager commandsand exploit their full functionality used. You can find a full XML reference and allmessages used throughout the product.

Command line interfaceThis topic describes all commands provided by the System AutomationApplication Manager. Most commands are used to control the various functionalcomponents of the System Automation Application Manager. Some commands areprovided to facilitate your work with automation policies. Other commands helpyou to extract information of currently defined resources. One special commandoffers to open a Command Shell, which is an interactive subshell with thecapabilities to work with resources and domains on the same level like theweb-based operations console.

All these commands can be found after installation in the<EEZ_INSTALL_ROOT>/bin

directory. To issue the commands, log on to the System Automation ApplicationManager. Use the “root” user account.

For more detailed information about the commands (like the command’s optionsand return codes), refer to Tivoli System Automation Application Manager, Referenceand Problem Determination Guide.

Commands referenceFind the full description of all commands used throughout System AutomationApplication Manager.

Command shell commands

Command overviewThe System Automation Application Manager command shell allows you tointeract with resources and relationships hosted by all automation domains thatcan also be controlled using the web-based operations console.

All command shell commands are targeted against the domain you have specifiedwhen starting the command shell.

Table 17 on page 44 lists the commands that can be issued with the SystemAutomation Application Manager command shell. The command eezcs, which youuse to issue a single command to the Application Manager or to open a commandsubshell that accepts multiple commands, is described in “eezcs” on page 48.

The type of the currently connected automation domain determines whichcommand shell commands are supported.


Table 17. Command shell commands

Command

Domain Types

Description

End-to-EndLevel

Automation

First LevelAutomation

“chprefmbr” X Changes the preferred member of a choice group.

“chtarget” onpage 46

X Changes the availability target of a server group.

“connect” onpage 47

X X Connect-to and work with another known domain.

“eezctrl” onpage 52

X Provides additional control functions for the connected automationdomain.

“eezdiag” onpage 54

X Provides diagnostic utilities for the connected automation domain.

“eezpolicy”on page 57

X Activates or deactivates an end-to-end automation policy or listsinformation about the automation policies in the policy pool.

“help” onpage 59

X X Displays a command's usage statement or a list of all commandspossible on the current connected automation domain.

“lsclustersets”on page 61

X Lists information about cluster sets defined in the end-to-endautomation policy

“lseezdom”on page 62

X X Lists information about the automation domains that are currentlyknown to the end-to-end automation manager.

“lsnode” onpage 64

X Lists information about nodes defined in the currently-connecteddomain.

“lsrel” onpage 66

X X Lists information about the managed relationships that are definedbetween resources on the currently connected automation domain.

“lsres” onpage 68

X X Lists information about the resources that are hosted by the currentlyconnected automation domain.

“lsresreq” onpage 71

X X Lists requests and orders that were issued against resources. Oncommand-driven domains, this command might return empty.Optionally (if supported by the domain) it returns the details of thelast command.

“nodereq” onpage 73

X Issues commands against nodes of an automation domain.

“quit” onpage 75

X X Closes the command shell in shell mode.

“resetres” onpage 75

X X Resets the operational state of end-to-end automation resources from"Unrecoverable error" to "Unknown".

“resreq” onpage 76

X X Issues requests and commands against resources to change theircurrent desired state or active role, or to suspend them fromautomation. On domains that are not request-driven, the request hasthe same effect as the "Bring Online" command in the OperationsConsole.

chprefmbrPurpose

chprefmbr — changes the preferred member of a choice group.


Format

chprefmbr -h

chprefmbr -g choice_group -m new_preferred_member [-T] [-V]

Usage

End-to-end domain X

First level automation domain

Comments

The command changes the preferred member of a choice group. When the choicegroup has the observed state “Online”, the command triggers the followingactions: the end-to-end automation manager brings the currently preferred memberoffline, changes the preferred member, and tries to bring it online.

Flags

–g choice_groupSpecifies the name of the choice group whose preferred member is to bechanged.

–m new_preferred_memberSpecifies the name of the choice group member that is to become the newpreferred member.

-T Writes the command's trace messages to standard output. For yoursoftware-service organization's use only.

-V Writes the command's verbose messages to standard output.

-h Writes the command's usage statement to standard output.

Parameters

None.

Return codes0 The command ran successfully.11 The command was unable to contact the end-to-end automation manager.12 The user is not authorized to execute the command.13 An incorrect flag was specified on the command line.14 An incorrect attribute was specified on the command line.16

The specified choice group member was not found.17 The specified choice group was not found.

Authorization

EEZOperator and EEZEndToEndAccess roles

Examples1. To list all members of a choice group and to find out which is currently the

preferred member, you can use the lsres command:

Chapter 2. Reference 45

EEZCS[eezadmin@FECluster]>lsres -m -r "HTTP Server" –ApResource HTTP Server:

DisplayName = HTTP ServerClass = ChoiceOwner = Jenny ParkerDescription = This is the choice-Group for choosing one HTTP ServerInfoLink = http://www.example.com/choiceDefaultDesiredState = OfflinePreferredMember = HTTP Server Prim

Resource HTTP Server Backup:DisplayName = HTTP Server BackupClass = ResourceReferenceOwner = Harry O’NeillDescription = This is the reference with the name HTTP ServerInfoLink = --- No help ---DefaultDesiredState = OfflineReference-to:Name = HTTP Server BackClass = IBM.ResourceGroupDomain = FEClusterNode =

Resource HTTP Server Prim:DisplayName = HTTP Server PrimClass = ResourceReferenceOwner = Owens, BobDescription = This is the reference with the name HTTP ServerInfoLink = http://www.example.com/help/policy/HTTPServer.htmlDefaultDesiredState = OfflineReference-to:Name = HTTP ServerClass = IBM.ResourceGroupDomain = FEClusterSAPNode =

2. To change the preferred member of the choice group “HTTP Server” to itsbackup member “HTTP Server Backup”, issue:EEZCS[eezadmin@FECluster]>chprefmbr -V -g "HTTP Server" -m "HTTP Server Backup"EEZS0140I The resource HTTP Server Backup has been set as new

preferred member of choice group HTTP Server.

3. To verify the new preferred member of "HTTP Server", issue:lsres -r "HTTP Server" -ApResource HTTP Server:

DisplayName = HTTP ServerClass = ChoiceOwner = Jenny ParkerDescription = This is the choice-Group for choosing one HTTP ServerInfoLink = http://www.example.com/choiceDefaultDesiredState = OfflinePreferredMember = HTTP Server Backup

chtargetPurpose

chtarget — changes the availability target of an end-to-end server group.

Format

chtarget -h

chtarget -a new_availability_target [-c comment ] server_group [-T] [-V]

Usage

End-to-end domain X



Comments

The command changes the availability target of an end-to-end server group.

Flags

-a new_availability_targetSpecifies the value of the new availability target. This must be an integer value1 ≤ new_availablity_target ≤ members_of_server_group

–c commentA string representing a remark that might be related to this change. If thestring contains blanks, it must be enclosed in quotation marks. Someautomation domains only write the specified comment to their domain log,which can be browsed using the operations console.




Parameters

server_groupThe name of the server group whose availability target is to be changed.

Return codes0 The command ran successfully.11 The command was unable to contact the end-to-end automation manager.12 The user is not authorized to execute the command.13 An incorrect flag was specified on the command line.16

The specified server group was not found.17 An invalid target value has been specified.

Authorization


Example

To change the availability target of the server group SG_WebServers to 5, enter:EEZCS[eezadmin@FECluster]>chtarget -a 5 SG_WebServersEEZS0133I The request to set availability target "5" has been issued against resource SG_WebServers.

connectPurpose

connect - connect-to and work with another known domain.

Format

connect domain_name [-T] [-V] [-h]


Usage

End-to-end domain X

First level automation domain X

Comments

connect command connects to another known first-level automation or end-to-enddomain, changing the scope of the current interactive session.

If no credentials are specified in the configuration utility, connect will prompt foruser id and password. While in interactive mode, there is always exactly oneconnection active to one domain. Therefore, if a user is connected to domain DomA,and then connects to DomB, the connection to DomA is closed. If the domain is’Offline’ during the connect attempt, the credential will be verified as soon as thedomain comes online while the command shell is still connected.

Flags

-T Writes trace command’s trace messages to standard output. For yoursoftware-service organization’s use only.

-V Writes the command’s verbose messages to standard output.

-h Writes the command’s usage statement to standard output.

Parameters

domain_nameThe name of the domain to connect-to.

Return codes0 The command ran successfully.11 The command was unable to contact the end-to-end automation manager.12 The user is not authorized to execute the command.13 An incorrect flag was specified on the command line.14 An incorrect attribute was specified on the command line.

Authorization

EEZMonitor roles

Examplesv To connect to domain DomB, enter:

EEZCS [UserA@DomA] >connect DomBUsername: UserBPassword:EEZCS [UserB@DomB] >

eezcsPurpose

eezcs — opens the Application Manager command shell in line or in shell mode.


Format

eezcs [-h] [–S server_name[:port]] [–D domain_name] [-T] [-V] [-c command [-uWAS_username -p WAS_password] [-du domain_username -dp domain_password]]

Comments

Use this command to run one or more commands against resources, groups, andrelationships that are hosted on any automation domain that is currently connectedto the Application Manager:v If you use the -c option, you open the command shell in line mode. In this

mode, the shell connects to the automation manager, run the command (againstresources of the selected domain), display the results, and quit with the relevantexit status.

v When you omit the -c option, you open the command shell in shell mode. Inthis mode, a subshell opens in which you can enter an arbitrary number ofcommands against the selected automation domain until you close the subshellwith the quit command. The subshell is indicated with the prompt EEZCS[username@domainame] >. To display a list of all commands that can be enteredwithin the currently selected domain, use the help command.

To display a command's usage statement, enter the command with the -h option,for example:v In line mode, enter:

eezcs -c "lsres -h"

v In shell mode, enter:EEZCS [username@domainame] > lsres -h

Flags

–S server_name [:port]Specifies the information that is needed to connect to the server that hosts theApplication Manager. For the server_name, specify either a host name, an IPv4address, or an IPv6 address that is enclosed by brackets (for example, [::1]). Ifthe option is not specified, the default host name of the local host with theconfigured port number is used.

Note: This parameter is required when eezcs is started on a system other thanthe one on which the Application Manager is running. This is especially true inthe case when the Application Manager is kept highly available and mightmove. To find the appropriate <server_name> value in this scenario, issue thecommand eezdmn status. You can either use the host name where theautomation engine is located or the System Automation Application Managerservice IP address.

Note: If this parameter is used for the first time to connect to WebSphereApplication Server, which is running on another system, you might be asked toaccept an SSL signer from the target host to the local truststore. Review thesigner information. If the signer information is correct, then add it to thetruststore. A signer must be added to the local truststore before the eezcscommand can connect to the target host.

-D domain_nameSpecifies the domain name for which the command is run. This parameter isoptional. The default is the first online end-to-end domain that is found.


Note: Depending on the type of the connected automation domain, only asubset of command shell commands is available. See also System AutomationApplication Manager Reference and Problem Determination Guide for a list ofsupported commands per domain type.

-c commandSpecifies an automation manager command in line mode. The command shellconnects to the automation manager, runs the command, writes the output tostandard output, and quits with the relevant exit status. When the option isomitted, the command shell is opened in shell mode.

-u WAS_usernameSpecifies the user ID to be used for authentication to the end-to-endautomation manager. Here you must specify the user ID, which you also use inthe login window of the Dashboard Application Services Hub when you openthe web-based operations console. The option can be used only together withthe -c option. This ensures that user ID and password specification is onlyused in line mode.

-p WAS_passwordSpecifies the password for the user ID specified with the option -u. The optioncan be used only together with the -c option. This ensures that user ID andpassword specification is only used in line mode.

-du domain_username

Specifies the optional user ID to be used for authentication to the contactedfirst-level automation domain. Here you must specify the user ID you also usewhen you select the specific automation domain in the web-based operationsconsole. This user ID is verified by the selected automation domain.

If you choose to contact the first available end-to-end automation domain (bynot specifying the –D option), you do not have to specify the –du option. Inthis case, authentication with –u is sufficient.

This option can be used only together with the -c option. This ensures thatuser ID and password specification is only used in line mode.

If the specified FLA domain has no security that is enabled, a specification of–du and –dp is not required.

If you specified to use the user credentials that are specified in cfgeezdmn forthe end-to-end automation engine also for the command shell, –du and –dp isalso not required.

Note: Even if you authenticate earlier to the specific FLA domain, it is stillrequired to specify these user credentials. For example, with the graphicaloperations console or with an earlier invocation of the eezcs command. Theeezcs command does not use the credential vault feature, which can be usedwith the graphical operations console.

-dp domain_passwordSpecifies the password for the domain_username value that is specified with theoption -du. The option can be used only together with the -c option. Thisensures that user ID and password specification is only used in line mode.

-V Writes the verbose messages of the command to standard output.

-T Writes the trace messages of the command to standard output. For yoursoftware-service organization's use only.

-h Writes the usage statement of the command to standard output.


Parameters

None.

Return codes0 The command ran successfully.1 The command was unable to contact the end-to-end automation manager.2 An unknown flag was specified on the command line or a required parameter

was not specified.4 The command encountered a security problem.11 11 or higher. A problem occurred when the specified automation manager

command run.

Authorization

To use the command shell, the user ID used to log in must have the right to runthe eezcs command. After the installation of the System Automation ApplicationManager on UNIX and Linux systems, you need root authority.

The user name must have at least the EEZMonitor and EEZEndToEndAccess rolesto contact an end-to-end automation domain. If the command shell is used tocontact another automation domain, EEZMonitor role is sufficient – with the samerestrictions that this user name has when the web-based operations console isused.

Examples1. To open a command shell in shell mode, contacting the end-to-end automation

domain that runs on the local host by using the verbose option, enter:eezcs -V

2. To list all top-level resources that are defined in the currently active policy ofthe end-to-end automation domain that is running on server saamsrv1 on port2810, enter:eezcs -S saamsrv1:2810 -c "lsres -m -Adt" -u eezadmin -p eezadmin

Sample output:Research ResourceGroup false Online Online Ok OkAppServerResearch_ref ResourceReference false Online Online Ok OkWebServerResearch_ref ResourceReference false Online Online Ok OkDatabaseResearch_ref ResourceReference false Online Online Ok OkDevelopment ResourceGroup false Online Online Ok OkAppServerDevelopment_ref ResourceReference false Online Online Ok OkWebServerDevelopment_ref ResourceReference false Online Online Ok OkDatabaseDevelopment_ref ResourceReference false Online Online Ok Ok

3. To display all relationships that are defined on domain FECluster, which isconnected to the local System Automation Application Manager in line mode,enter:eezcs -D FECluster -c "lsrel" -u eezadmin -p eezadmin -du root -dp eezadmin

Sample output:Connecting to System Automation Application Manager on Server localhost using domain FECluster.EEZS0120I Using domain FECluster.IBM.Application:samadapterDependsOn IBM.ServiceIP:samadapter-ip

IBM.ServiceIP:samadapter-ipDependsOn IBM.Equivalency:samadapter-nieq

4. Enter the following command to apply the following behavior: Open acommand shell in shell mode, which connects to the local System Automation


Application Manager. Use the domain FECluster. List all available commandsthat are supported on the domain type. Close the command shell.eezcs -D FECluster

Sample input and output:Connecting to System Automation Application Manager on Server localhost using domain FECluster.Realm/Cell Name: defaultWIMFileBasedRealmUser Identity: eezadminUser Password:Specify user name and password to access domain: FEClusterUsername: rootPassword:EEZS0120I Using domain FECluster.EEZCS[username@domainame]>helpPossible Commands:

lseezdom - List information about automation domains.resreq - issues requests against resources or cancels previously entered requests.nodereq - issues commands against nodes of an automation domain.resetres - resets the operational state of end-to-end automation resources.lsrel - lists information about managed relationships.lsres - lists information about resources.lsnode - lists information about one ore many nodes.lsresreq - lists requests and orders that were issued against resources.help - displays a command’s usage statement or a list of all possible commands.quit - closes the command shell.

EEZCS[eezadmin@FECluster]>quitGoodbye.

5. After you configured the command shell to use specified user credentials foraccessing the System Automation Application Manager and to use FLA domainaccess credentials as defined under the tab "User credentials" with thecommand cfgeezdmn, it is not required to specify any user and passwordanymore. For more information, see Tivoli System Automation ApplicationManager, Installation and Configuration Guide. To open a command shell in linemode (connecting to the domain FECluster connected to the local SystemAutomation Application Manager) and show all relationships, enter:# eezcs -D FECluster -c "lsrel"

Sample output:IBM.Application:samadapter

DependsOn IBM.ServiceIP:samadapter-ipIBM.ServiceIP:samadapter-ip

DependsOn IBM.Equivalency:samadapter-nieq

eezctrlPurpose

eezctrl — provides additional control functions for the connected automationdomain.

Format

eezctrl -h

eezctrl -r "*" | domain_name [-T] [-V]

Usage

End-to-end domain X



Comments

The eezctrl command offers additional functions to control (resources of)automation domains. Currently, this command offers one option specialized to theautomation behavior of end-to-end domains.

Flags

-r "*" | domain_name

Specify one domain_name which hosts at least one of the referenced resources ofthe current active end-to-end automation policy. You can also specify "*" toaddress all domains hosting at least one referenced resource.

This option has the following effects:v If domain_name is currently on the list of temporarily excluded domains, it is

removed from this list. For more information about temporary excludeddomains, see Tivoli System Automation Application Manager, Administrator’s andUser’s Guide.

v All resource references in the current active end-to-end policy referring tothe specified domain_name will be set into the initial (unknown) state – whichis the same state as if the end-to-end policy gets activated again. This causesthe end-to-end automation manager to contact the referenced first levelautomation domain to request initial events for the referenced resources. Inthis way, you can enforce the synchronization of the current observed statesof resource references with the states of the referenced resources.

v If domain_name specifies a replication domain, then this replication domainrefreshes its configuration and its resource cache.

This option is useful especially after you found all or more than one resourcereference referring to resources running on domain_name in a "fatal" compoundstate. Call this option after you have solved the problem causing this fatal error(for example, after you have corrected the domain access credentials).




Parameters

None.


The specified domain was not found.

Authorization

EEZConfigurator and EEZEndToEndAccess roles


Examples1. To reset all resource references in the current active policy in verbose mode,

enter:eezctrl –r “*” -V

eezdiagPurpose

eezdiag — provides diagnostic utilities for the connected automation domain.

Format

eezdiag [-h] [-T] [-V]

eezdiag [-e (domain_name | all)] | [-a (adapter_host | all)]

eezdiag [-d fully qualified file_name] | [-t (all | exc | hist] | [-l] [-T] [-V]

Usage

End-to-end domain X


Comments

The eezdiag command provides diagnostic functions for the currently selectedautomation domain. If no option is specified, the command will provide detailedstatus and configuration information.

Flags

-e Use the option -e to query the event history from the automation engine. Itshows a statistics record of events per FLA domain which have been receivedby the automation engine. The statistics ignore heartbeat events. The statisticsare helpful in answering the question "Why is a domain not showing up in theoperations console?" or "Why is a resource reference still waiting for stateinformation?" The statistics only show the events received since last startuptime of the Application Manager.

You can display the event statistics for one FLA domain by specifying a domainname. For example:eezdiag -e "domain_xyz"

Or, you can display the event statistics for all FLA domains by specifying theparameter “all”. For example:eezdiag -e all

DomainThe domain name for this specific statistics record.

Adapter_IPThe IP address from which the first level automation adapter sendsevents to the System Automation Application Manager. The SystemAutomation Application Manager uses this address whenever it has tocontact this domain; for example, to query the current status ofresources.


CurrentEventLag

The current event lag is calculated by the System AutomationApplication Manager by comparing the system time of the SystemAutomation Application Manager at the moment the event is receivedagainst the time specified in the event when it was created on the firstlevel automation domain. The current event lag is updated each timean event is received from that domain.

The current event lag can be positive or negative. It is influenced bytwo factors: unsynchronized system times on different machines, andthe actual event delivery time span.

Note: When using the deep history view of the resource reference tabin the Operations Console and the current event lag is too big, thedeep history might result in incorrect correlation of past events,because events from different domains can only be correlated by timestamp.

LastEventSequenceNumberThe sequence number of the last event received from that domain.

ReceivedInitialEventA boolean value which indicates that an event of type "initial event"was ever received from that domain. If this value is false, it mightexplain why an end-to-end resource reference pointing to a resource onthis domain is stuck in the state "waiting for event". In this case, theproblem probably has to be solved by checking the adapter log writtenby the adapter of the specific first level automation domain.

ReceivedAdapterJoinEventA boolean value which indicates that an adapter from this domain hastried to contact the System Automation Application Manager.

ReceivedDomainJoinEventA boolean value which indicates that the initial handshake between theadapter and the System Automation Application Manager has beensuccessful.

ReceivedDomainLeaveEventA boolean value which indicates that an adapter has been terminatedand therefore stopped the connection to the System AutomationApplication Manager.

LastEventTimeStampThe time stamp of the last-received event.

LastResourceEventTimeStampThe time stamp of the last-received resource event indicating, forexample, a state change of a resource.

LastAdapterJoinEventTimeStampThe time stamp of the last-received adapter join event. See explanationfor ReceivedAdapterJoinEvent

LastDomainJoinEventTimeStampThe time stamp of the last-received domain join event. See explanationfor ReceivedDomainJoinEvent

LastDomainLeaveEventTimeStampThe time stamp of the last-received domain leave event. Seeexplanation for ReceivedDomainLeaveEvent


-a adapter_host | all

Use the option -a adapter_host to display the event statistics of a specificadapter.

Use the option -a all to display the event statistics of all known adapters.

-t (all | exc | hist)

Use the option -t all to retrieve the formatted trace file from the automationengine. This feature will format the traceEngine.log to a readable format andprint it page-by-page to STDOUT.

Use the option –t hist to query history information from the automationengine. It shows a (large) table describing events of the following types in theend-to-end automation engine:v All events sent by the end-to-end automation engine (resource events of

resources defined in the end-to-end policy and domain events).v All requests issued against resources of the end-to-end domain by an

operator or by GDPS.v All events received from referenced FLA resources (initial events and state

change events).v All requests sent by the end-to-end automation engine to FLA domain

resources.v All policy activations.

You will not get any history about FLA resources if you have not definedreferences in the current active policy. The shown table contents only reflectthose happenings which could currently be found in the trace filetraceEngine.log. This trace file has a configured maximum size and onlycontains the most current trace statements. If the automation engine is runningfor a long time, it is likely that you will see neither a table header nor the veryfirst events issued since start-up.

If you have disabled tracing for the end-to-end automation domain, the –toption will not present any information.

Use the option -t exc to list all exceptions found in the trace of the automationengine.

-l Use the -l option to retrieve the formatted log file from the automation engine.This is similar to the function “View log...” which you can select on theweb-based operations console whenever the end-to-end automation domain isonline. Notice – only with this command you can explore trace and log fileswritten by the automation engine even if the end-to-end domain is offline.

-d file_name

Use this command option only when IBM requests debugging information forall resources currently hosted by the end-to-end automation manager. Thiscommand will dump the debugging information to the specified fully qualifiedfile_name.





Parameters

file_nameFully-qualified file name of the file to hold the data dumped with the –doption.

Return codes0 The command ran successfully.11 The trace or log file could not be read.12 The trace file does not contain the requested data.13 An incorrect flag was specified on the command line.14 An incorrect attribute was specified on the command line.16 The specified domain cannot be found in the event statistics.17 The file cannot be created.

Authorization


Examples1. To get general information about the current automation domain, enter:

eezdiag

2. To retrieve the event history of the automation engine, enter:eezdiag –t hist

3. To retrieve the formatted trace file of the automation engine, enter:eezdiag –t all

4. To dump debugging information for all resources hosted by the end-to-endautomation manager to a file, enter:eezdiag -d "/tmp/ae_dump.dmp"

5. To list the domain-specific events for all domains, enter:eezdiag -e all

6. To list the adapter-specific events for all adapters, enter:eezdiag -a all

eezpolicyPurpose

eezpolicy — activates or deactivates an automation policy or displays informationabout the automation policies in the policy pool. This command is only availablefor domains supporting policy handling as indicated by the domain capabilities.

Format

eezpolicy [-h] [-T] [-V]

eezpolicy –a policy_file_name [-T] [-V]

eezpolicy –d [-T] [-V]

eezpolicy -A [policy_file_name] [-T] [-V]

Usage

End-to-end domain X



Comments

The eezpolicy command is used for the following tasks:v Activate an automation policyv Deactivate the currently active automation policyv Display the list of automation policies from the policy poolv Display information about a specific or all automation policies in the policy pool

Flags

–a policy_file_nameActivates the specified automation policy (after deactivating the currentlyactive policy, if applicable).

To obtain the correct policy_file_name of the automation policy, use eezpolicy-A.

Before activating a policy, it is checked for syntactical and semantic errors. Thisincludes a check of the policy rules described in “Automation policy rulereference” on page 124. If the specified automation policy cannot be activatedbecause of errors, the currently active automation policy is not deactivated andan error message is displayed.

-d Deactivates the active automation policy.

-A [policy_file_name]Lists detailed information about the specified automation policy or allautomation policies in the policy pool.




Parameters

None.


The specified policy was not found.17 The specified policy cannot be activated or deactivated.

Authorization



Examples1. To list all policies in the policy pool, enter:

eezpolicy -V

Sample output:Policies in pool 'C:\Program Files\IBM\tivoli\eez\policyPool'

FEClusterDemo.xmlFEClusterLinux.xmlsample.xml

done.

2. To list detailed information about all automation policies in the policy pool,enter:eezpolicy –A

Sample output:Policy 1:

PolicyFileName = FEClusterDemo.xmlPolicyName = FECluster PolicyPolicyToken = 1.0.1PolicyAuthor = Michael AtkinsPolicyCheck = Error

Policy 2:PolicyFileName = FEClusterLinux.xmlPolicyName = FECluster PolicyPolicyToken = 1.0.1PolicyAuthor = Michael AtkinsPolicyCheck = Warnings

Policy 3 (active) :PolicyFileName = sample.xmlPolicyName = Sample E2E PolicyPolicyToken = 1.0.1PolicyAuthor = Michael AtkinsPolicyCheck = ok

EEZCS[eezadmin@FECluster]>

3. To activate an automation policy, use the -a option and specify the name of thepolicy. To retrieve the name, issue the eezpolicy command with the -A option(see the sample output in usage scenario “eezpolicy” on page 57). When the filename sample.xml is used to activate the policy, the output looks like this:eezpolicy -a sample.xmlEEZS0100I The policy /etc/opt/IBM/tsamp/eez/policyPool/sample.xml

has been activated.

4. To deactivate the active automation policy, enter:eezpolicy –d

Sample output:eezpolicy –dEEZS0101I The policy /etc/opt/IBM/tsamp/eez/policyPool/josi.xml

has been deactivated.

helpPurpose

help — displays a command's usage statement or a list of all possible commands.


Comments

The help command lists all possible commands, each with a short usage statement,or prints the usage statement for a specific command, similar to displaying manpages on UNIX systems. Usage statements that do not fit on a single page are splitinto multiple pages. One page is displayed at a time. To jump to the next page,press Enter. This behavior is comparable to that of the “ | more” command onUNIX systems. Scrolling back to previous pages is not possible.

Format

help [-h] help command

Usage

End-to-end domain X


Flags


Parameters

commandSpecifies the command for which detailed help information is requested.

Return codes0 The command ran successfully.11 The command was unable to contact the end-to-end automation manager.13 An incorrect flag was specified on the command line.16 The specified command was not found.

Examples1. To list all commands that are supported by the end-to-end automation

command shell, enter:help

Output:Possible Commands:

lseezdom - List information about automation domains.eezpolicy - activates or deactivates an end-to-end automation policy.resreq - issues requests against resources or cancels previously entered requests.resetres - resets the operational state of end-to-end automation resources.chprefmbr - changes the preferred member of a choice group.lsrel - lists information about managed relationships.lsres - lists information about resources.lsresreq - lists requests and orders that were issued against resources.help - displays a command’s usage statement or a list of all possible commands.quit - closes the command shell.lsclustersets - lists information about clustersets.

2. To list detailed usage information for the lsrel command, enter:help lsrel


lsclustersetsPurpose

lsclustersets - returns all cluster sets on the sites defined in the automation policy.It shows the desired state, the compound state and the status of a requested actionfor the business-critical and discretionary workload.

Note: This command only returns results when using Distributed DisasterRecovery for GDPS.

Format

lsclustersets [-h] [-T] [-V]

lsclustersets [-c clusterset_name] [-b] [-D delimiter] [-T] [-V]

Usage

End-to-end domain X


Comments

lsclustersets always returns a complete table, even if no resources are defined in aspecific cluster set and site scope. In this case the compound state is 'OK' and theobserved state is 'NotApplicable'.

DR requests can also be issued on cluster set and site scopes that have noresources specified. In these cases the requests will immediately return successfullybecause there is nothing to do.

Flags

-c clusterset_namePrints information for the named cluster set only.

-b Prints information about business-critical workload only.

-D delimiterLists the output in delimited format.

-T Writes trace messages to standard output.

Note: Only for use by your software-service organization.

-V Writes verbose messages to standard output.


Parameters

None.

Return codes0 The command ran successfully.17 The command was not able to obtain data from the automation engine.


Authorization


Examplesv To list all data about the clusterset GblFEClusterSAP, enter:

EEZCS[eezadmin@FECluster]>lsclustersets -c GblFEClusterSAP

Sample output:Displaying Clustersets:

Clusterset GblFEClusterSAP:





lseezdomPurpose

lseezdom — lists information about the automation domains that are currentlyknown to the end-to-end automation manager.

Format

lseezdom [-h] [-T ] [-V]

lseezdom [-n domain_name] [-A p | d | b] [-D delimiter] [-T ] [-V] [Attr]

Usage

End-to-end domain X


Comments

The lseezdom command retrieves information about a specific or all automationdomains that are currently known to the end-to-end automation manager. To usethe command, it is not necessary to be connected to the automation domain.

The command contacts the Automation Manager JEE Framework and gathersinformation about all currently known domains, which can be one or morefirst-level automation domains and zero or one end-to-end automation domain.


If hidden automation domains are defined in your personal operator preferencesthen the lseezdom command does not include information about the hiddendomains. Use the option -V to get a list of the defined hidden domains. You canconfigure the list of hidden domains in the Preferences window of the SystemAutomation operations console.

To retrieve the maximum of information about a specific or all domains, use the–A option with the b parameter. The list contains the following information abouta domain:v Namev States The listed states are identical to those that are displayed on the operations

console when the domain is selected.v Dynamic and persistent attributes Depending on the type of automation domain,

some of the domain attributes listed may always be empty.v When a first-level domain hosts one or more resources that are referenced in the

active end-to-end automation policy, and if the -A option is not used, then thedomains are displayed in a tree-like structure.

Flags

–n domain_nameLists information about the specified domain.

–A p | d | bLists all domain attributes or the attributes of the specified type. Possibletypes:

p Lists the persistent attributes of a domain.

d Lists the dynamic attributes of a domain.

b Lists both the persistent and dynamic attributes of a domain.


-T Writes the trace messages of the command to standard output. For yoursoftware-service organization's use only.

-V Writes the verbose messages of the command to standard output.

-h Writes the usage statement of the command to standard output.

Parameters

AttrSpecifies the name of one or more attributes whose values are to be listed.Attribute names must be separated by spaces.

Return codes0 The command ran successfully.11 The command was unable to contact the end-to-end automation manager.12 The user is not authorized to execute the command.13 An incorrect flag was specified on the command line.14 An incorrect attribute was specified on the command line.16 The specified domain does not exist.

Authorization

EEZMonitor role


Examples1. To list all currently known domains and find out to which domain the

command shell is currently connected, you can use the following command.Notice that the string "(Connected)" is shown alongside the domain name towhich the command shell is currently connected. All commands used in thiscommand shell session are targeted against this domain.lseezdom

Sample output:FriendlyE2EFECluster (Connected)

2. To list the dynamic attributes of all domains that are currently known to theend-to-end automation manager, enter:lseezdom –Ad

Sample output:Domain FriendlyE2E (Connected):

DomainState = OnlineCommunicationState = OkDomain Log has new Error = trueActivePolicyName = Sample E2E PolicyPolicyActivationTime = Tue Feb 03 17:47:46 CET 2011AutomationStartupTime = Tue Feb 03 17:17:31 CET 2011

Domain FECluster:DomainState = OnlineCommunicationState = OkDomain Log has new Error = falseActivePolicyName =PolicyActivationTime = Thu Feb 05 14:22:03 CET 2011AutomationStartupTime = Wed Jan 21 13:35:50 CET 2011

3. To list the persistent attributes of the domain, enter:lseezdom -Ap -n "FECluster”

Sample output:Domain FECluster:

AutomationProductname = IBM Tivoli System Automation for MultiplatformsAutomationVersion = 3.1.0.1 - IVN/AVN/CVN: 3.2.1.0 / 3.2.1.0 /

1233840464148 (0x94498ae950)DomainType = FLAAutomationLocation = node1Properties:

Domain-Health-State = OnlineTimestamp-Adapter = 2010-02-10 16:12:22 +0100Timestamp-Last-Event = 2010-02-10 14:28:01 +0100Sequence-Number-Last-Event = 5EIF-Sender-Location = saamsrv1EIF-Sender-Port = 2002

lsnodePurpose

lsnode - lists information about nodes defined in the currently connected domain.

Format

lsnode -h

lsnode [-A p | d | b] [-f] [-t | -D delimiter] [-n node_name] [-T] [-V] [Attr]

Usage

End-to-end domain



Comments

lsnode command is used to retrieve information about all nodes in the scope ofthe currently connected domain.

Additional properties can be displayed with the -A option.

The full information option (-f) allows you to display virtual server information (ifavailable). Additional credentials might be necessary if this option is specified.

Output can be restricted by specifying one or more columns via the Attrparameter.

Flags

-A p | d | bDisplay additional attributes by type. Possible types:

p Lists the persistent attributes of a node.

d Lists the dynamic attributes of a node.

b Lists both the persistent and dynamic attributes of a node.

-f Enhance existing output with information for a virtual server.


-t Lists the output in tabular format. Each attribute is displayed in a separatecolumn, one node per line.

-T Writes trace command’s trace messages to standard output.

Note: Only for use by your software-service organization.



Parameters

AttrThe name of one or more attributes. Attribute names must be separated byspaces. The specified Attr parameters must be valid node attributes.

Whether a node attribute is listed depends on the specified value for the -Aoption.

Return codes0 The command ran successfully.11 The command was unable to contact the end-to-end automation manager.12 The user is not authorized to execute the command.13 An incorrect flag was specified on the command line.

Authorization

EEZMonitor roles


Examplesv 1. To list all currently defined nodes, enter:

lsnode

Sample output:EEZCS>lsnodesOnline p6sa11 (v)Online lnxcm4 (v)Online p550sa14 (v)

v 2. To list dynamic and persistent attributes for all nodes of an automationdomain in tabular format, enter:Press Enter to continue...lsnode -Abft

Sample output:EEZCS>lsnode -AbftName Operating Observed Excluded Node Virtual VirtualServer VirtualizationHost Virtualization

System State Startable Server State Type Host-----------------------------------------------------------------------------------------------------p6sa11 IBM AIX Online no yes virtServer09 operating Blade blade04lnxcm4 RedHat Linux Offline no yes virtServer03 not-operating LPAR lpar01p550sa14 IBM AIX Online no yes virtServer01 operating LPAR lpar04

lsrelPurpose

lsrel — lists information about the managed relationships that are defined in thecurrently active automation policy.

Format

lsrel [-h] [-T ] [-V]

lsrel [-S [resource_class:]source_resource_name[:resource_node]] [-G[resource_class:]target_resource_name[:resource_node]] [-P relationship_type] [-A] [-t|-Ddelimiter] [-T] [-V] [Attr ... ]

Usage

End-to-end domain X


Comments

The lsrel command lists information about the managed relationships that aredefined in the currently active automation policy. The command generates outputonly if a policy is active and contains managed relationships. The command cannotbe used to list group memberships or referenced resources.

If the relationship_type is specified, all relationships of this type will be listed. If aresource name is specified as source_resource_name or target_resource_name, the nameof the resource and the managed relationships in which it is the source or target,respectively, are listed. If both a source_resource_name and a target_resource_name arespecified, only the corresponding managed relationships between the sourceresource and the target resource are listed.

If one or more attribute names are specified with the Attr parameter, the exactvalues of the specified attributes are listed. The Attr parameter must be a validrelationship attribute.


Flags

–A Specifies that all attributes of a relationship are to be listed.

–D delimiterLists the output in delimited format.

–t Lists the output in tabular format. Each attribute is displayed in a separatecolumn, one resource per line.

–S [resource_class:]source_resource_name[:resource_node]]Use this option to specify the name of the resource which is the source of allrelationships that are to be listed.

–G [resource_class:]target_resource_name[:resource_node]]Use this option to specify the name of the resource which is the target of therelationships that are to be listed.

–P relationship_typeSpecifies the type of relationship for which the relationships are to be listed.The value can be one of the following (not case-sensitive):StartAfterStopAfterForcedDownBy




Parameters

AttrSpecifies the name of one or more attributes whose values are to be displayed.Attribute names must be separated by spaces.

Return codes0 The command ran successfully.11 The command was unable to contact the end-to-end automation manager.12 The user is not authorized to execute the command.13 An incorrect flag was specified.14 An incorrect attribute was specified.16

No managed relationships were found.17 The specified source or target resource could not be found.

Authorization

EEZMonitor and EEZEndToEndAccess roles

Examples1. To list all relationships from the currently active policy, enter:

lsrel -V

Sample output:Displaying relationship informationResourceReference:WebSphere EE

StartAfter ResourceReference:DNS ServerResourceReference:SAP AppServer

StartAfter ResourceReference:SAP ENQ Server


ForcedDownBy ResourceReference:SAP ENQ ServerResourceGroup:mySAP Solutions

StartAfter ChoiceGroup:DB2ResourceReference:SAP ENQ Server

StopAfter ResourceReference:SAP AppServerResourceReference:NFS Client

StartAfter ResourceReference:SAP AppServerForcedDownBy ResourceReference:NFS Server

done.

2. To list all relationships in tabular format, enter:lsrel -t

Sample output:EEZCS[eezadmin@FECluster]>lsrel –tSource Relationship TargetIBM.ServiceIP:samadapter-ip DependsOn IBM.Equivalency:samadapter-nieqIBM.Application:samadapter DependsOn IBM.ServiceIP:samadapter-ip

lsresPurpose

lsres — lists information about the resources that are defined in the currentlyconnected automation domain.

Format

lsres [-h] [-T] [-V]

lsres [-m] [-s selection_string] [-A p|d|b][-f] [-t|-D delimiter] [-r[resource_class:]resource_name[:resource_node]] [-T] [-V] [Attr ...]

Usage

End-to-end domain X


Comments

The lsres command lists top-level resources that are defined in the currentlyconnected automation domain. The command only generates output if a policy isactive and contains resources.

When the command is issued with the –m option, group members are also listed.A specific resource can be shown using the –r option.

When the attribute option (–A b) is specified, the values of all possible attributesare listed.

When specified, the Attr parameter must be a valid resource attribute whenresource information is listed. Whether a resource attribute is listed depends onwhich value was specified for the -A option. In all cases, the exact values of theattributes are listed.

Flags

–A p | d | bSpecifies an attribute type. Possible types:


p Lists the persistent attributes of a resource.

d Lists the dynamic attributes of a resource.

b Lists both the persistent and dynamic attributes of a resource.

-f Follow any resource reference or replication reference and list additionalinformation about the referenced object.


-m When -m is specified, the command lists also the members of groups. Whenthe –A option is set as well, the attributes of the displayed resource are shown.

-r [resource_class:]resource_name[:resource_node]Specifies the name of the resource for which information is to be listed.

-s selection_stringSpecifies a selection string. If specified without the –m option, this option isapplied to the resource attribute fields; when the –m option is specified, theselection string is applied to the member-resource attribute fields. All selectionstrings must be enclosed in either double or single quotation marks. If theselection string contains double quotation marks, enclose the entire selectionstring in single quotation marks, for example:-s 'Name == “testing”'-s 'Name ?= “test”'

All attributes may be listed in a selection string. For information on how tospecify selection strings, see “Using selection strings” on page 79.

-t Lists the output in tabular format. Each attribute is displayed in a separatecolumn, one resource per line.




Parameters

AttrSpecifies the name of one or more attributes whose values are to be listed.Attribute names must be separated by spaces. The exact values of theattributes will be listed.

The specified Attr parameter must be a valid resource attribute. Whether aresource attribute is listed depends on which value was specified for the -Aoption. In all cases, the exact values of the attributes are listed.


The specified resource is not a group or the group has no members.17 The specified selection string does not match any resource attribute.


Authorization


Examples1. To list all currently defined resources with their observed state, enter:

lsres -m

Sample output:Online IBM.Equivalency:samadapter-nieq

Online IBM.NetworkInterface:eth0:saxb14Online IBM.NetworkInterface:eth0:saxb42Online IBM.NetworkInterface:eth0:saxb43

Online IBM.ResourceGroup:A-ND-001Online IBM.Application:A-ND-001-1:saxb14Online IBM.Application:A-ND-001-2:saxb42Online IBM.Application:A-ND-001-3:saxb43

Online IBM.ResourceGroup:samadapter-rgOnline IBM.Application:samadapter

Online IBM.Application:samadapter:saxb14Offline IBM.Application:samadapter:saxb42Offline IBM.Application:samadapter:saxb43

Online IBM.ServiceIP:samadapter-ipOnline IBM.ServiceIP:samadapter-ip:saxb14Offline IBM.ServiceIP:samadapter-ip:saxb42Offline IBM.ServiceIP:samadapter-ip:saxb43

2. To list all members and sub-members of the group “Friendly Computer Shop”and their dynamic attributes in tabular format, enter:lsres -tAd -m -r "Friendly Computer Shop" -V

Sample output:

Displaying resource information

Name Class Domain Sus-pended

DesiredState

ObservedState

OperationalState

CompoundState

--------------------------------------------------------------------------------------------------------

FriendlyComputer Shop

ResourceGroup false Offline Unknown NoContact Warning

WebSphere AE ResourceReference FECluster false Offline Unknown NoContact Warning

mySAP Solutions ResourceGroup false Offline Unknown NoContact Warning

DNS Server ResourceReference FECluster false Offline Unknown NoContact Warning

SAP ENQ Server ResourceReference FEPLEX1 false Offline Unknown NoContact Warning

3. To list all attributes of the group “DNS Server”, enter:lsres -Ab -f -r "DNS Server"

Sample output:Resource DNS Server:

DisplayName = DNS ServerClass = ResourceReferenceOwner = Jenny McDowellDescription = This is the reference with the name DNS ServerInfoLink = http://www.example.com/help/DNS ServerDefaultDesiredState = OfflineDesiredState = OfflineObservedState = UnknownOperationalState = NoContactCompoundState = WarningSuspended = falseReference-to:

Name = DNS ServerClass = IBM.ResourceGroupDomain = FEClusterNode =

Properties:sa_status_compound = Inhibited


sa_status_desired = Offlinesa_status_observed = Unknownsa_status_binding = Not Applicablesa_status_automation = Idlesa_status_control = StartInhibitedsa_status_health = Not Applicable

4. To list all table columns as comma-separated list, specify the comma (,) asdelimiter character for the option –D. The first line of the output always showsthe names of the listed attributes. Each line ends with a duplicated delimitercharacter (in this example: ",,").lsres -D, -Ad

Sample output:Name,Class,Domain,Suspended,DesiredState,ObservedState,OperationalState,CompoundState,,eMail Hosting,ResourceReference,FECluster,false,Online,Unknown,NoContact,Warning,,WebSphere E2E,ResourceGroup,,false,Offline,Unknown,NoContact,Warning,,Enterprise DB2,ResourceReference,FEPLEX2,false,Offline,Unknown,NoContact,Warning,,WebSphere EE,ResourceReference,FEPLEX2,false,Offline,Unknown,NoContact,Warning,,DNS Server,ResourceReference,FECluster,false,Offline,Unknown,NoContact,Warning,,NFS Client,ResourceReference,cm1cm2,false,Offline,Unknown,NoContact,Warning,,NFS Server,ResourceReference,FEPLEX1,false,Offline,Unknown,NoContact,Warning,,WebSphere AE,ResourceReference,FECluster,false,Offline,Unknown,NoContact,Warning,,Friendly Computer Shop,ResourceGroup,,false,Offline,Unknown,NoContact,Warning,,WebSphere AE,ResourceReference,FECluster,false,Offline,Unknown,NoContact,Warning,,mySAP Solutions,ResourceGroup,,false,Offline,Unknown,NoContact,Warning,,DNS Server,ResourceReference,FECluster,false,Offline,Unknown,NoContact,Warning,,SAP ENQ Server,ResourceReference,FEPLEX1,false,Offline,Unknown,NoContact,Warning,,SAP AppServer,ResourceReference,FEClusterSAP,false,Offline,Unknown,NoContact,Warning,,HTTP Server,ChoiceGroup,,false,Online,Unknown,NoContact,Warning,,HTTP Server Prim,ResourceReference,FEClusterSAP,false,Online,Unknown,NoContact,Warning,,HTTP Server Backup,ResourceReference,FECluster,false,Offline,Unknown,NoContact,Warning,,DB2,ChoiceGroup,,false,Offline,Unknown,NoContact,Warning,,DB2 Connect Client,ResourceReference,FECluster,false,Offline,Unknown,NoContact,Warning,,DB2 Connect Client Backup,ResourceReference,FEPLEX2,false,Offline,Unknown,NoContact,Warning,,

lsresreqPurpose

lsresreq — lists requests and orders that were issued against resources. Suspendactions are not listed.

Format

lsresreq [-h] [-T] [-V]

lsresreq [-L] [-t|-D delimiter] [-s selection_string] [-T] [-V][resource_class:]resource_name[:resource_node]

Usage

End-to-end domain X


Comments

The lsresreq lists all requests and orders that were issued against specificresources, or only the winning request, or all outstanding requests and orders.

Flags

–L Lists all requests and orders that were issued against a specified resourcegroup or resource reference. If the option is not specified, only the winningrequest is listed.


–s selection_stringSpecifies a selection string. The selection string is evaluated against all requeststhat were submitted against resources. Requests whose attribute values matchthe selection string are listed. For example, to list all requests that were issuedby operators use the following selection string:–s “Source == OPERATOR"

To list all requests that where submitted against resources whose name startswith SERVER*, specify:-s “Resource like 'SERVER%'”

For information on how to specify selection strings, see “Using selectionstrings” on page 79.

–t Lists the output in tabular format. Each attribute is displayed in a separatecolumn, one resource per line.

–D DelimiterLists the output in delimited format.




Parameters

resource_nameSpecifies the name of one or more resources whose requests are to bedisplayed. The resource names must be separated by spaces.


The specified resource was not found.17 No request with an attribute value that matches the specified selection string

was found.

Authorization


Examplesv To list all requests against the resource "DNS Server", enter:

EEZCS[eezadmin@FECluster]>lsresreq -V "DNS Server"

Sample output:Requests against Resource DNS Server:Request 1:

Action = OnlinePriority = HighSource = OPERATORUserId = unknownComment = none


Additional Info = ENTRY: DNS ServerTimestamp = Thu Jun 22 10:28:26 CEST 2006is winning = yes

done.

nodereqPurpose

nodereq - issues commands against nodes of an automation domain.

Format

nodereq -h

nodereq -o action [-t timeout] [-c comment] [-T] [-V] node_name

Usage

End-to-end domain


Comments

nodereq command is used to submit start and stop commands to nodes and toexclude and include nodes.

Depending on the currently connected automation domain, options and actionsmight show different effects or might not be supported. Only nodes that areassociated with a virtual server can be started or stopped.

Flags

-o actionSpecifies the type of request. Possible types:

startStart the virtual server associated with the node.

startWaitStart the virtual server associated with the node. Waits for a node to be inobserved state online. Note: Can only be used with the timeout option.

stopStop the virtual server associated with the node.

excludeSpecifies that the node is to be excluded (if this is supported by theconnected automation domain).

includeSpecifies that the node is to be included (if this is supported by theconnected automation domain).

-t timeoutA positive integer with a maximum value of 2147483647 representing thenumber of seconds before this synchronous command will be terminated.When this timeout option is specified, it implies that the command is waitingfor the specified timeout period to reach a certain state of a node.


v For the start option, the state to be achieved is a virtual server state ofactivated.

v For the startWait option the state to be achieved is a node observed state ofonline.

v For the stop option, the state to be achieved is a virtual server state ofnot-operating.

If the state to be achieved still does not match the expected state as indicatedabove when the timeout period has expired, the command will exit with thestatus indicating that the timeout has been reached.

When this option is not specified, the default is to send the commandasynchronously.

-c commentA string representing a remark that might be related to the request. If thestring contains blanks, it must be enclosed in quotation marks. Someautomation domains only write the specified comment to their domain log,which can be browsed using the operations console. Other automationdomains show the comment when browsing the requests with the commandlsresreq.

-T Writes trace command’s trace messages to standard output. For yoursoftware-service organization’s use only.



Parameters

node_nameThe name of the node.

Return codes0 The command ran successfully.4 The command was unable to contact the end-to-end automation manager.12 The user is not authorized to execute the command.13 An incorrect flag was specified on the command line.14 An incorrect attribute was specified on the command line.16 The node against which the command was submitted was not found.18 The specified timeout was reached and the command terminated.19 The specified timeout is invalid.20 The node does not support the requested action.

Authorization

EEZOperator role

Examplesv To issue a start against the node p6sa11, enter:

nodereq -o start p6sa11 -V

Sample output:EEZS0137I A command to start the node p6sa11 has been issued.

done (RC=0).


quitPurpose

quit - closes the command shell in shell mode. The command is not used in linemode.

Format

quit [-h]

Usage

End-to-end domain X


Flags


Parameters

None.

Return codes

None.

resetresPurpose

resetres — resets the operational state of end-to-end automation resources from"Unrecoverable error" to "Unknown".

Format

resetres -h

resetres -r [resource_class:]resource_name[:resource_node] [-T] [-V]

Usage

End-to-end domain X


Comments

An end-to-end automation resource that has the operational state "Unrecoverableerror" must be manually reset to change the operational state to "Unknown" whenthe cause of the problem has been resolved. Only after the operational state haschanged will the end-to-end automation manager again start to calculate and issueactions against the resource. When the command is issued against a resourcegroup, the operational state of all group members is changed.


Flags

–r [resource_class:]resource_name[:resource_node]Specifies the name of the resource to be reset.




Parameters

None.


The specified resource was not found.

Authorization


ExampleEEZCS [eezadmin@FECluster] >resetres -r ChoiceGroup:DB2

resreqPurpose

resreq — issues requests against resources, cancels previously issued requests, orsuspends or resumes automation for resources. You can also use this command forresources which support the resource role concept to change their current activerole to a new role. Requests can be set against resources of all types (Resources,Resource References, Groups, and so on.) which have a desired state not equal to"No_Change".

Format

resreq -h

resreq -o action [-p priority] [-t timeout] [-S source] [-u user_name] [-c comments] [-T][-V] [resource_class:]resource_name[:resource_node]

Usage

End-to-end domain X



Comments

The resreq command is used to submit or cancel online and offline requests and tosuspend and resume automation for resources. Depending on the currentlyconnected automation domain, options and actions might show different effects ormight not even be supported.

The command shell allows you to perform the following additional tasks whichcannot be performed from the operations console:v Issue requests against resources that are in observed state “Unknown”.v Issue requests with different priorities. Note that the priority has no relevance

when suspending or resuming automation.v Specify the source of the request, which may be necessary for canceling start and

stop requests because this requires that the request to be canceled and the cancelrequest have the same source. Note that the source has no relevance whensuspending or resuming automation.

v Issue requests to set the role of the targeted resource to the new specified role.

Flags

–o actionSpecifies the type of request. Possible types:

startSpecifies that the resource is to be started (Online request). This commandcan also be issued against resources of an automation domain that is notrequest driven. In this case, it has to be compared to the Bring Onlinecommand available in the operations console. In this case, this start requestcannot be cancelled. It will be overwritten by a stop request.

stopSpecifies that the resource is to be stopped (Offline request). This commandcan also be issued against resources of an automation domain that is notrequest driven. In this case, it has to be compared to the “Bring Offline”command available in the operations console. In this case, this stop requestcannot be cancelled. It will be overwritten by a start request.

restartSpecifies that the resource is to be restarted (Restart request).

cancelCancels a start or stop request that was submitted against the resource bythe same source. This request action is only supported by request-drivenautomation domains.

suspendSuspends automation for a resource

setrole:role_nameSets the role of the resource to role_name. This action is only supported forresources which have the attribute SupportsSetRole set to "true". Therole_name value has to be specified after a colon (":") appended to theaction "setrole". Only specify roles for role_name values that are listed ascontent of the "SupportedRoles" attribute.

resumeResumes automation for a resource


–p priorityDetermines the priority rank of the request. The request with the highestpriority overrules requests that have a lower priority. The priority allows theend-to-end automation manager to resolve conflicting requests for the sameresource. priority can be one of the following values:

lowLow priority. This is the default value.

highHigh priority. Takes precedence over requests submitted with low priority.

forceTakes precedence over requests submitted with high priority.

-t timeoutA positive integer representing the number of seconds before this synchronouscommand which sends a request against a resources will be terminated. If theobserved state of the targeted resource does not match the new desired statewhen the timeout period has expired, the command will exit with the statusindicating that the timeout has been reached. The request will remain againstthe resource and the observed status of the resource targeted by this requestmight even be reached at a later point in time.

When this option is not specified, the default is to send the commandasynchronously.

–S sourceOn automation domains of the System Automation product family (SystemAutomation for Multiplatforms, System Automation z/OS, and SystemAutomation Application Manager) source can be one of the following strings:OperatorExtSchedAutomation

On connected first level automation domains, the value for source is notnecessarily predefined.

Specification of a source might not have any effect for resource requests of thisdomain.

On other automation domains, the value for source is not predefined. If sourceis not specified, it will default to \"Operator\". When canceling the request,the same source must be specified. Note that each source can only have oneactive request of each type against a resource.

The source option can also be used to distinguish between who made therequest or where the request came from, for example, from an operator versusan automation shell script.

–u user_nameThe originator of the request. This can be any string. If the string containsblanks, it must be enclosed in quotation marks. If this option is not specified,the user ID that was specified when the connection to the automation managerwas established with the eezcs command is used.

–c commentA comment is a string representing a remark that is related to the request. Ifthe string contains blanks, it must be enclosed in quotation marks. Someautomation domains only write the specified comment to their domain log,


which can be browsed using the Operations Console. Other automationdomains show the comment when browsing the requests with the commandlsresreq.

Note: The character semicolon ";" is not allowed in comments.




Parameters

[resource_class:]resource_name[:resource_node]Specifies the class, name, and node of the resource. resource_class andresource_node are optional except on FLA domains, where they are required.This is the entry point at which the requests is introduced into the resourcestructure and from which it propagates outward.


The resource against which the command was submitted was not found.17 The specified Selection_string does not match any request.18 The specified timeout was reached and the command terminated.19 The specified timeout is invalid.20 The resource does not support the requested action.

Authorization


Examplesv To issue a high priority request against the resource “HTTP Server”, enter:

resreq -o start -p high -u Bob -c "Need it up now." "HTTP Server"

Sample output:EEZS0131I The Start request has been issued against resource HTTP Server.

v To wait 30 seconds for request completion of a stop request against resource DB2of a First Level Automation Domain named “DB_Cluster” in line mode, enter:eezcs –D DB_Cluster –c "resreq –o stop –t 30 DB2" –du root –dp secret

Using selection stringsAbout this task

Some of the commands described in “Command shell commands” on page 43allow you to specify a selection string for the –s option. The selection string alwaysapplies to attributes of resources or requests. The attribute name must be specifiedexactly as it is displayed in the output and match it with the value specified in theselection string.


To specify a selection string, different types of expressions can be used, namely,regular expressions or SQL-like expressions. The selection strings shown in thefollowing two examples will produce the same result when they are used in aquery. Both will return resources whose name starts with a ‘W’ and ends with thestring “Server”:-s “Name =~ 'W.*Server'”-s “Name LIKE 'W%Server'”

Within a single selection string, multiple attributes may be combined by a booleanoperator. For example:-s “(Name LIKE 'W%Server') OR (Owner LIKE '%Owens')”

A query with this selection string will return all resources which either match byName (as in the example above) or are owned by a person called “Owens”.

The set of operators that can be used in selection strings is summarized in thefollowing table.

Table 18. Operators that can be used in selection strings

Operator Description

Types

Left | Right Return

< less than see Table 19 on page81

boolean

> greater than boolean

<= less than or equal to boolean

>= greater than or equalto

boolean

==

=

equal to boolean

<> not equal to boolean

!= matches

(regular expression)

boolean

=~ does not match

(regular expression)

boolean

=?

like

LIKE

SQL like boolean

!?

not like

NOT LIKE

SQL not like boolean

OR

{

or (one of the twomust be true)

boolean

AND

&&

and (both need to betrue)

boolean


The following table lists the available left and right data types. An "X" in a tablecell indicates that the operator shown in the header row can be used with the datatype shown on the left (numbers, strings, boolean):

Table 19. Selection strings: Data types

Operator: < > <= >= = != =~ !~ =? !? { &&

Numbers X X X X X X X X X X X X

Strings X X X X X X X X X X X X

boolean X X X X X X X X

Configuration commandsThere are various components of System Automation Application Manager that canbe separately configured using various commands:

Table 20. Configuration commands

Configurationcommand Description

cfgeezdmn Can be used to:

v Configure common Application Manager settings.

v Configure the agentless adapter for non-clustered nodes.

v Configure high availability of System Automation ApplicationManager.

v Configure the hardware adapter.

v Configure a TPC-R domain.

v Refresh the currently active configuration of different components inthe running system.

v Test the configuration settings of different components.

cfghacadapter Can be used to configure the end-to-end automation adapter for HighAvailability Cluster Multi-Processing (HACMP).

cfgmscsadapter Can be used to configure the end-to-end automation adapter forMicrosoft Failover Cluster (FOC).

cfgvcsadapter Can be used to configure the end-to-end automation adapter forVeritas Cluster Server (VCS) for Solaris.

All commands can be used to run the respective configuration task in graphical aswell as silent mode.

cfgeezdmnPurpose

cfgeezdmn — Configure the System Automation Application Manager.

Format

cfgeezdmn [-h]

cfgeezdmn [-s [-e] [-g|-gr|-r] [-l location]]

cfgeezdmn [-s -eu [-g|-gr] [-l location]]


cfgeezdmn [-s -ru -o host [-g| -gr|-ra [-w configdir]|-rr|-rd -u userid -p password[-llocation]]]

cfgeezdmn [-s -eh [-g|-gr|-r|-t] [-l location]]

cfgeezdmn [-s -et [-g|-gr|-r|-t] [-l location]]

cfgeezdmn [-s -ea [-ad] [-g|-gr] [-l location]]

Comments

The cfgeezdmn command performs the following tasks depending on the enteredformat:v Invokes the System Automation Application Manager configuration dialog.v Configures the System Automation Application Manager in silent mode.v Generates an input properties file for silent configuration.

Flags

<no option> Invokes the configuration dialog as the default action when no option isspecified.

-s

v Invokes the configuration utility in silent mode if the -g or -gr option is notspecified.

v Generates an input properties file for silent configuration if the -g or -groption is specified.

-e Configures System Automation Application Manager common settings. This isthe default configuration option.

-euConfigures the local agentless adapter for non-clustered nodes.

-ruPerforms one of the configuration tasks (add, remove, distribute, modify) for aremote agentless adapter for non-clustered nodes.

Additional options:v -ra: A new configuration for a remote agentless adapter is added.v -rr: The configuration for a remote agentless adapter is removed.v -rd: A configuration for a remote Agentless Adapter is distributed to the

host where the adapter is installed.

If -ru is specified without any additional options, the configuration for aremote agentless adapter is modified.

-o hostSpecifies the host system where the remote agentless adapter instance isinstalled. The requested remote agentless adapter configuration task isperformed for that adapter instance.

-raAdds a new remote agentless adapter configuration. The configuration isadded for the remote agentless adapter instance that is installed on the host


system specified with option -o. A new set of configuration files with empty ordefault values is created in the directory <EEZ_CONFIG_ROOT>/host on theApplication Manager server host.

-w configdirDefines the directory where the remote agentless adapter configuration files arelocated on the host system specified with option -o. If the remote host is aWindows system, this option is required in conjunction with option -ra. If thehost system specified with option -o is a Unix system, omit this option.

-rrRemoves a remote agentless adapter configuration. The configuration isremoved for the remote agentless adapter instance that is installed on the hostsystem specified with option -o. Directory <EEZ_CONFIG_ROOT>/host and allcontained configuration files are deleted on the Application Manager serverhost.

-rdDistributes a remote agentless adapter configuration from directory<EEZ_CONFIG_ROOT>/host on the Application Manager server host to theconfiguration directory on the host system specified with option -o.

-u useridUser credentials are only required if you use option -rd. Specifies the user IDto login to the host system specified with option -o.

-p passwordUser credentials are only required if you use option -rd. Specifies thepassword to login to the host system specified with option -o.

-ehConfigures the hardware adapter.

-etConfigures a TPC-R domain (not supported on all operating system platforms).

-eaConfigures the System Automation Application Manager high availability.

-adConfigures the System Automation Application Manager high availabilitypolicy for a two-site disaster recovery setup. If not specified together with -ea,this option is ignored. If -ea is specified without -ad, the regular SystemAutomation Application Manager high availability policy is configured.

-r Refreshes the currently active configuration in the running system. No silentinput properties file is required for this task. The -r option can be used torefresh settings of the common configuration, the hardware adapterconfiguration, or the TPC-R domain configuration.

-t Tests the hardware adapter or the TPC-R domain configuration. No silent inputproperties file is required for this task.

-g Generates an input properties file for silent configuration if it does not yetexist.

-grGenerates an input properties file for silent configuration and replaces theexisting file.

-l locationIn conjunction with options -g and -gr the input properties file for silentconfiguration is generated in the directory that is specified with location. To


perform a silent configuration using option -e, -eu, -ru, -eh, -et, or -ea, theinput properties file is retrieved from the directory that is specified withlocation. If -l is omitted, the default directory is used, see Examples section.


Return codes

All return codes greater than zero apply if the command is invoked in silent mode,using the -s option.

0 Command has run successfully.

1 The command has run successfully, but the command output containswarnings.

2 The command failed. Invalid or missing input is detected in the silentinput properties file. The command output contains corresponding errormessages.

3 The command failed. The attempt to update at least one of the targetconfiguration files failed. The command output lists files and errormessages for the unsuccessful update attempts.

9 The command failed due to an unexpected unrecoverable error. Thecommand output contains corresponding error messages.

Authorization

The command requires either root authority or write access to the directory/etc/opt/IBM/tsamp/eez/cfg.

The user ID to start the command must be in same group as the user ID you usedfor installing System Automation Application Manager.

If a remote agentless adapter configuration is distributed using the options -s -ru-o host -rd -u userid -p password, write access for user ID userid to the distributiontarget directory on the host system specified with option -o is required. Thedistribution target directory is /etc/opt/IBM/tsamp/eez/rala/cfg.

Examples1. To generate an input properties file for the silent configuration of System

Automation Application Manager common settings, enter:cfgeezdmn -s -g

Sample output:----- Generate silent configuration input properties file -----Silent configuration input properties file/etc/opt/IBM/tsamp/eez/cfg/silent.eezcommon.properties has been created.

2. To generate an input properties file for silent configuration of the agentlessadapter in a location other than the default location, enter:cfgeezdmn -s -eu -g -l /var/config

Sample output:----- Generate silent configuration input properties file -----Silent configuration input properties file/var/config/silent.eezaladapt.properties has been created.

3. To create a new remote agentless adapter configuration for an adapter that isinstalled on host my.host.system, enter:


cfgeezdmn -s -ru -o my.host.system -ra

Sample output:----- Add remote agentless adapter configuration -----

The remote agentless adapter configuration for remote host my.host.system hasbeen successfully added.The configuration directory on host my.host.system is /etc/opt/IBM/tsamp/eez/rala/cfg.

4. To configure the System Automation Application Manager high availability insilent mode, enter:cfgeezdmn -s -ea

Sample output:Configuration completed successfully with warnings.----- Configuration update status -----Configuration File: /etc/opt/IBM/tsamp/eez/cfg/eez.automation.engine.propertiesUpdate: OKConfiguration File: /etc/opt/IBM/tsamp/eez/cfg/sas.eezcs.propertiesUpdate: No changeConfiguration File: /etc/opt/IBM/tsamp/eez/cfg/eez.dla.propertiesUpdate: No changeConfiguration File: /etc/opt/IBM/tsamp/eez/cfg/eez.automation.engine.dif.propertiesUpdate: No changeConfiguration File: /etc/opt/IBM/tsamp/eez/cfg/sas.eezdmn.propertiesUpdate: No changeConfiguration File: /etc/opt/IBM/tsamp/eez/cfg/eez.publisher.omnibus.propertiesUpdate: No changeConfiguration File: /etc/opt/IBM/tsamp/eez/cfg/eez.publisher.gdps.propertiesUpdate: No changeConfiguration File: /etc/opt/IBM/tsamp/eez/cfg/eez.publisher.gdpsbackup.propertiesUpdate: No changeConfiguration File: /etc/opt/IBM/tsamp/eez/cfg/eez.fla.ssl.propertiesUpdate: No changeConfiguration File: /etc/opt/IBM/tsamp/eez/cfg/eezjlog.propertiesUpdate: No changeConfiguration File: /etc/opt/IBM/tsamp/eez/cfg/eezautomate.propertiesUpdate: OKConfiguration File: /etc/opt/IBM/tsamp/eez/cfg/eez.aladapter.propertiesUpdate: OKConfiguration File: /etc/opt/IBM/tsamp/eez/cfg/eez.aladapter.jlog.propertiesUpdate: No changeConfiguration File: /etc/opt/IBM/tsamp/eez/cfg/eez.hwadapter.propertiesUpdate: OK----- End configuration update status -----

5. To test the hardware adapter in silent mode, enter:cfgeezdmn -s -eh -t

Sample output:----- Test current configuration values -----The current hardware adapter configuration has been successfully tested.

cfghacadapterPurpose

cfghacadapter — Allows to configure the end-to-end automation adapter forPowerHA.

Format

cfghacadapter [-h]

cfghacadapter [-s]

cfghacadapter [-s [-g|-gr] [-l location]]


Comments

The cfghacadapter command invokes the PowerHA adapter configuration dialog,configures the PowerHA adapter in silent mode, or generates an input propertiesfile for silent configuration.

Flags


-s





-l locationIn conjunction with options -g and -gr the input properties file for silentconfiguration is generated in the directory that is specified with location. Toperform a silent configuration using option -e, -eu, -eh, -et, or -ea, the inputproperties file is retrieved from the directory that is specified with location. If-l is omitted, the default directory is used, see Examples section.


Return codes







Authorization

The command requires either root authority or write access to the directory/etc/opt/IBM/tsamp/eez/hac/cfg.


Examples1. To generate an input properties file for silent configuration, enter:

cfghacadapter -s -g

Sample output:----- Generate silent configuration input properties file -----Silent configuration input properties file/etc/opt/IBM/tsamp/eez/hac/cfg/silent.hacadapter.properties has been created.

2. To generate an input properties file for silent configuration in a location otherthan the default location, enter:cfghacadapter -s -g -l /var/config

Sample output:----- Generate silent configuration input properties file -----Silent configuration input properties file/var/config/silent.hacadapter.properties has been created.

3. To configure the PowerHA adapter in silent mode, enter:cfghacadapter -s

Sample output:Configuration completed successfully.----- Configuration update status -----Configuration file: /etc/opt/IBM/tsamp/eez/hac/cfg/hac.adapter.propertiesUpdate: OKConfiguration file: /etc/opt/IBM/tsamp/eez/hac/cfg/hac.adapter.ssl.propertiesUpdate: OKConfiguration file: /etc/opt/IBM/tsamp/eez/hac/cfg/hac.adapter.confUpdate: No changeConfiguration file: /etc/opt/IBM/tsamp/eez/hac/cfg/hac.adapter.jaas.propertiesUpdate: No changeConfiguration file: /etc/opt/IBM/tsamp/eez/hac/cfg/hac.adapter.jlog.propertiesUpdate: No change----- End configuration update status -----

cfgmscsadapterPurpose

cfgmscsadapter — Allows to configure the end-to-end automation adapter forMicrosoft Failover Cluster (FOC).

Format

cfgmscsadapter [-h]

cfgmscsadapter [-s]

cfgmscsadapter [-s [-g|-gr] [-l location]]

Comments

The cfgmscsadapter command invokes the FOC adapter configuration dialog,configures the FOC adapter in silent mode, or generates an input properties file forsilent configuration.

Flags



-s





-l locationIn conjunction with options -g and -gr the input properties file for silentconfiguration is generated in the directory that is specified with location. Toperform a silent configuration using option -e, -eu, -eh, -et, or -ea, the inputproperties file is retrieved from the directory that is specified with location. If-l is omitted, the default directory is used, see Examples section.


Return codes







Authorization

The command requires either root authority or write access to the directory<EEZ_INSTALL_ROOT>\cfg.


cfgmscsadapter -s -g

Sample output:----- Generate silent configuration input properties file -----Silent configuration input properties fileC:\Program Files\IBM\tsamp\eez\mscs\cfg\silent.mscsadapter.properties has been created.

2. To generate an input properties file for silent configuration in a location otherthan the default location, enter:cfgmscsadapter -s -g -l D:\temp\cfg


Sample output:----- Generate silent configuration input properties file -----Silent configuration input properties fileD:\temp\cfg\silent.mscsadapter.properties has been created.

3. To configure the FOC adapter in silent mode, enter:cfgmscsadapter -s

Sample output:Configuration completed successfully.----- Configuration update status -----Configuration file: C:\Program Files\IBM\tsamp\eez\mscs\cfg\mscs.adapter.propertiesUpdate: OKConfiguration file: C:\Program Files\IBM\tsamp\eez\mscs\cfg\mscs.adapter.plugin.propertiesUpdate: No changeConfiguration file: C:\Program Files\IBM\tsamp\eez\mscs\cfg\mscs.adapter.ssl.propertiesUpdate: OKConfiguration file: C:\Program Files\IBM\tsamp\eez\mscs\cfg\mscs.adapter.jlog.propertiesUpdate: No change----- End configuration update status -----

cfgvcsadapterPurpose

cfgvcsadapter — Allows to configure the end-to-end automation adapter forVeritas Cluster Server (VCS) for Solaris.

Format

cfgvcsadapter [-h]

cfgvcsadapter [-s]

cfgvcsadapter [-s [-g|-gr] [-l location]]

Comments

The cfgvcsadapter command invokes the VCS adapter configuration dialog,configures the VCS adapter in silent mode, or generates an input properties file forsilent configuration.

Flags


-s





-l locationIn conjunction with options -g and -gr the input properties file for silentconfiguration is generated in the directory that is specified with location. To


perform a silent configuration using option -e, -eu, -eh, -et, or -ea, the inputproperties file is retrieved from the directory that is specified with location. If-l is omitted, the default directory is used, see Examples section.


Return codes







Authorization

The command requires either root authority or write access to the directory/etc/opt/IBM/tsamp/eez/vcs/cfg.


cfgvcsadapter -s -g

Sample output:----- Generate silent configuration input properties file -----Silent configuration input properties file/etc/opt/IBM/tsamp/eez/vcs/cfg/silent.vcsadapter.properties has been created.

2. To generate an input properties file for silent configuration in a location otherthan the default location, enter:cfgvcsadapter -s -g -l /var/config

Sample output:----- Generate silent configuration input properties file -----Silent configuration input properties file/var/config/silent.vcsadapter.properties has been created.

3. To configure the VCS adapter in silent mode, enter:cfgvcsadapter -s

Sample output:Configuration completed successfully.----- Configuration update status -----Configuration file: /etc/opt/IBM/tsamp/eez/vcs/cfg/vcs.adapter.propertiesUpdate: OKConfiguration file: /etc/opt/IBM/tsamp/eez/vcs/cfg/vcs.adapter.plugin.propertiesUpdate: No changeConfiguration file: /etc/opt/IBM/tsamp/eez/vcs/cfg/vcs.adapter.ssl.propertiesUpdate: OKConfiguration file: /etc/opt/IBM/tsamp/eez/vcs/cfg/vcs.adapter.conf


Update: No changeConfiguration file: /etc/opt/IBM/tsamp/eez/vcs/cfg/vcs.adapter.jaas.propertiesUpdate: No changeConfiguration file: /etc/opt/IBM/tsamp/eez/vcs/cfg/vcs.adapter.jlog.propertiesUpdate: No change----- End configuration update status -----

Controlling adapters commandsResources that are integrated into an end-to-end automation policy via resourcereferences are managed using automation adapters. There is a command to controleach of those adapters:

eezaladapterAllows to start, stop, and monitor the status of the Agentless Adapter. Formore information, refer to “eezaladapter.”

eezhwadapterAllows to start, stop, and monitor the status of the hardware adapter. Formore information, refer to “eezhwadapter” on page 92.

hacadapterAllows to start, stop, and monitor the status of the HACMP adapter. Formore information, refer to “hacadapter” on page 94.

vcsadapterAllows to start, stop, and monitor the status of the VCS adapter. For moreinformation, refer to “vcsadapter” on page 95.

eezaladapterPurpose

eezaladapter — Allows to control the agentless adapter. You can start and stop theagentless adapter or monitor the current status.

Format

eezaladapter [start|stop|status]

Comments

The eezaladapter command starts a daemon process that runs in the backgroundwithout an attached terminal. You can log out from the system after you startedthe agentless adapter. The process keeps on running and does not terminate likenormal user processes.

Flags

startThe option start is the default value that is used when you enter thecommand eezaladapter without specifying an option. Starts the agentlessadapter on local node.

stopStops the agentless adapter on local node.

statusReturns the status of the agentless adapter.


Parameters

None.

Return codes

start

0 Command run successfully.

1 Command failed.

stop

0 Command run successfully.

1 Command failed.

status

1 Agentless adapter is running.

2 Agentless adapter is stopped.

Authorization

To use the agentless adapter, root authority is required.

eezhwadapterPurpose

eezhwadapter — Allows to control the Hardware Adapter. You can start and stopthe Hardware Adapter or monitor the current status.

Format

eezhwadapter [start|stop|status|-h]

Comments

The hardware adapter provides:v Management access to cluster hardware for classic DR access. It controls systems

via direct access to the service processors of the cluster hardware (via a scriptexit or SNMP). Mapping between hardware and cluster node names isconfigured in the disaster recovery policy.

v Access to the zEnterprise HMC via zEnterprise HMC Web Services API, tocontrol virtual servers available in this HMC.

Flags

start

Default value that is used when you enter the command eezhwadapter withoutspecifying an option. This command starts the hardware adapter.

Classic DR access:

1. During startup, the hardware adapter reads and processes the configurationparameters and hardware credentials you specified on the HardwareAdapter pages of the configuration dialog. For information about the


end-to-end automation manager configuration dialog, see Tivoli SystemAutomation Application Manager, Installation and Configuration Guide.

2. When the hardware adapter has started successfully, it is displayed as"Online" in the operations console. If a disaster recovery policy for thedomain had previously been active, the last active policy will be reactivatedautomatically on the hardware adapter.

zEnterprise Hardware access:

1. During startup, the hardware connects to the zEnterprise HMC. Thehardware adapter registers itself with the automation JEE framework andretrieves all available virtual servers from the zEnterprise HMC.

2. The automation JEE framework sends a list of all hostnames of which it isaware - that is, all hostnames of the nodes of all automation domainsconnected to the hardware adapter.

3. The hardware adapter searches in its list of virtual servers to determine ifthere are virtual servers with the same hostnames, and return these virtualservers to the automation JEE framework.

4. The automation JEE framework persistently stores this information in theautomation database, updates it if required, and adds new information. Forexample, if a new node becomes part of a cluster then this information isdistributed to clients such as the operations console or the command shell.

Note:

1. Classic DR access: After starting the hardware adapter, you may receive amessage indicating that it is in the state:v STARTING - this happens if the hardware adapter fails to establish initial

contact with the automation engine. As soon as the automation engine isup and running, it establishes contact, and changes its state to running.

v IDLE and that no disaster recovery policy is activated though such apolicy had previously been active - this is because it takes its time toreactivate the last policy that was active.

2. After making changes in the end-to-end automation manager configurationdialog, you must restart the hardware adapter using eezhwadapter stopand eezhwadapter start, for the changes to take effect.

stop

Stop the hardware adapter in a controlled way.

status

Retrieve information about the current state of the hardware adapter. Whenyou issue the command, the following message (for both classic DR access andzEnterprise HMC access) is displayed:State of the hardware adapter for <adapter type> is: <state-related information>

where <adapter type> stands for one of the adapters, either “classic DRaccess” or “zEnterprise HMC access”

<state-related information> stands for one of the states described in “Returncodes” on page 94.


Note: Options can be entered in either lowercase or uppercase.


Return codes

To retrieve information about the current state of the hardware adapter, use thestatus option. It delivers the following return codes:

0 State-related information in the message: IDLE - no DR policy activatedor RUNNING - DR policy for domain EEZHardwareAdapter is activated

This is the normal state after the hardware adapter has been started.

2 State-related information in the message: STARTING - the hardwareadapter is not yet ready

The hardware adapter is being started.

6 State-related information in the message: NOT AVAILABLE - the hardwareadapter probably not started

No contact to the hardware adapter can be established. It is assumed thatit has not been started yet.

8 State-related information in the message: Invalid hardware adapterconfiguration file <fileName> - see message log for details

The hardware adapter configuration file contains invalid values. Check themessage log file for information on the problems that have occurred. If youcannot resolve the problem, contact IBM support.

10 State-related information in the message: PROBLEM during commandexecution - see message log for details

Severe problems have been detected. Check the message log file forinformation about the problems that have occurred. If you cannot resolvethe problems, contact IBM support.

21 Multiple plugins are configured and one of them is currently unavailable.

Check the automation engine message log file for details.

Authorization

To use the hardware adapter, root authority is required.

hacadapterPurpose

hacadapter — Allows to control the PowerHA adapter. You can start and stop thePowerHA adapter or monitor the current status.

Format

hacadapter [-start]

hacadapter [-stop]

hacadapter [-status]

Flags

-start Starts the adapter if it is not running:


v If the adapter is automated, the command requests PowerHA cluster servicesto start the adapter on the preferred node. The command returns when theclRGmove command completed.

v If the adapter is not automated, it is started on the node where thecommand was issued. The exit code is 0 if the command was successful.

-stopStops the adapter if it is running:v If the adapter is automated, the command requests PowerHA cluster services

to stop the adapter on the preferred node. The command returns when theclRGmove command completed.

v If the adapter is not automated, it is stopped on the node where thecommand was issued. The exit code is 0 if the command was successful.

-statusChecks if the adapter is running and returns the RSCT return code for theoperational state (OpState).

Return codes

To check the status of the PowerHA adapter, use the -status option. It delivers thefollowing return codes,

0 Unknown. The adapter status cannot be determined.

1 Online. The adapter is running.

2 Offline. The adapter is not running.

Authorization

To use the PowerHA adapter, root authority is required.

vcsadapterPurpose

vcsadapter — Allows to control the VCS adapter. You can start and stop the VCSadapter or monitor the current status.

Comments

A VCS adapter is active when it is running and listening for requests from a host(end-to-end automation manager or operations console), which is listening forevents from the adapter on a different connection.

Format

vcsadapter [-start]

vcsadapter [-stop]

vcsadapter [-status]

Flags

-start Starts the adapter if it is not running:


v If the adapter is automated, the command requests VCS to start the adapteron the preferred node.

v If the adapter is not automated, it is started on the node where thecommand was issued. The exit code is 0 if the command was successful.

-stopStops the adapter if it is running:v If the adapter is automated, the command requests VCS to stop the adapter

on the preferred node.v If the adapter is not automated, it is stopped on the node where the

command was issued. The exit code is 0 if the command was successful.

Note: The VCS adapter cannot be stopped from the operations console. A stopattempt results in an error message.

-statusChecks whether the adapter is running.

Return codes

To check the status of the VCS adapter, use the -status option. It delivers thefollowing return codes,

0 Unknown. The adapter status cannot be determined.

1 Online. The adapter is running.

2 Offline. The adapter is not running.

Authorization

To use the VCS adapter, root authority is required.

Controlling the GDPS agentAbout this task

Use the eezgdpsagent command to control the GDPS agent. Note that theWebSphere Application Server hosting the Application Manager JEE applicationmust be running.

If you have made System Automation Application Manager highly available, theGDPS agent is automated as part of the automation policy. In this case, use of theeezgdpsagent command can interfere with the automation and is notrecommended.

eezgdpsagentPurpose

eezgdpsagent — allows you to control the GDPS agent. You can start, stop, ormonitor the current status of the GDPS agent.

Format

eezgdpsagent start [-V]

eezgdpsagent stop [-V]


eezgdpsagent status [-V]

Flags

start Starts the GDPS agent

stopStops the GDPS agent

statusDisplays the status of the GDPS agent

-V Writes verbose output to the system log and automation engine log.

Return codes

The return codes depend on the requested action.

start0 The command completed successfully.7 The command failed.

stop0 The command completed successfully.7 The command failed.

status1 The GDPS agent is online.2 The GDPS agent is offline.3 The GDPS agent is failed offline.5 The GDPS agent is pending online.

Command-line interface commandsThe following commands are used to control the automation manager.

Note: Options can be entered in either lowercase or uppercase.

eezdmnPurpose

eezdmn — Allows to control the end-to-end automation engine.

Comments

You can start and stop the end-to-end automation engine or monitor the currentstatus, or install the feature licences.

Note:

1. The eezdmn command starts a daemon process that runs in the backgroundwithout attached terminal. You can logout from the system after you started theautomation engine. The process keeps on running and does not terminate likenormal user processes do.

2. In general it is sufficient to just use the command eezdmn, because a symboliclink named eezdmn was created in your /usr/bin directory.


Format

eezdmn [start]

eezdmn [stop]

eezdmn [status]

eezdmn [instcert]

eezdmn [-h]

Flags

start

The option start is the default value that is used when you enter the commandeezdmn without specifying an option. The command starts the automationengine. During startup, the automation engine reads and processes theconfiguration parameters you specified on the Domain and User credentialspages of the configuration dialog. For information about the end-to-endautomation manager configuration dialog, see Tivoli System AutomationApplication Manager, Installation and Configuration Guide.

When the automation engine has started successfully, the end-to-endautomation domain is displayed on the operations console. The domain has thename that is defined in the Domain name field on the Domain page of theconfiguration dialog.

When you start the automation engine for the first time after you installedSystem Automation Application Manager, you must subsequently activate anend-to-end automation policy.

If a policy for the domain had previously been active, the last active policy willbe reactivated automatically if it is found in the policy pool directory.

Note:

1. After starting the automation engine, you may receive a message indicatingthat the automation engine is in IDLE state and that no policy is activatedalthough the last active policy is available in the policy pool directory. Thisis because it takes time to load the last active policy.

2. After making changes in the end-to-end automation manager configurationdialog, you must restart the automation engine using eezdmn stop andeezdmn start.

stop

Use the option stop to stop the automation engine in a controlled way. Whenthe automation engine is stopped, end-to-end automation for the resources thatare defined in the end-to-end automation policy will stop as well.

If you stop the automation engine, contact to the first-level automationdomains will be lost, which means that events are no longer received and theresource state information that is displayed on the operations console will beoutdated shortly after the engine has stopped.

status


Use the option status to retrieve information about the current state of theautomation engine. When you issue the command, the following message isdisplayed:

State of the EEZ automation engine is: <state-related information>

where <state-related information> stands for one of the exit status describedin “Return codes.”

instcert

Use this command option to install a license certificate.

The syntax of the command is:eezdmn instcert <fully qualified path to license file>

-h

Writes the command usage statement to standard output.

Return codes

The following is a list of the exit status that are returned by the command eezdmnstart

0 The automation engine started successfully.

7 Error: The automation engine could not be started. Check the automationengine log file for details.

8 Error: Incorrect attributes were specified. The automation engine could notbe started.

The following is a list of the exit status that are returned by the command eezdmnstop

0 The automation engine was stopped successfully.

7 Error: The automation engine could not be stopped. Check the automationengine log file for details.

8 Error: Incorrect attributes were specified. The automation engine could notbe stopped.

The following is a list of the exit status that are returned by the command eezdmnstatus .

1 State-related information in the message: ONLINE – Policy is activated

This is the normal state after a policy has been activated and end-to-endautomation is running.

2 State-related information in the message: OFFLINE – Automation enginedoes not accept requests anymore

The automation engine is being stopped.

The following is a list of the exit status that are returned by the command eezdmninstcert:

0 OK- License has been installed.

1 OK - License was already installed.

2 ERROR - Unable to read license certificate file.


3 ERROR - Unable to install license certificate file: see Automation EngineLog for more details.

Authorization

Root authority is required.

eezpolicycheckerPurpose

eezpolicychecker — Allows to check an end-to-end automation policy forsyntactical and semantic correctness. The command eezpolicychecker verifies if apolicy is correct without activating the policy. If you want to check a policy andthen activate it automatically, use the eezpolicy command. See also “eezpolicy” onpage 57.

Format

eezpolicychecker policy_file_name

Comments

The eezpolicychecker command parses the specified end-to-end automation policythat is stored in the policy pool directory of the System Automation ApplicationManager node and checks thatv the policy is syntactically correctv the policy adheres to the rules described in “Automation policy rule reference”

on page 124

The command issues messages for any warnings or errors that it detects.

Parameters

policy_file_nameSpecifies the name of the file that contains the policy to be checked. If thepolicy is an end-to-end automation policy that is located in the end-to-endpolicy pool, specify just the file name. If the policy is not located in theend-to-end policy pool, including any agentless adapter policy, specify the filename including the fully qualified path.

Return codes

0 The command ran successfully. For information about your policy, checkthe messages sent to STDOUT.

1 Unable to open the specified policy.

Authorization

EEZConfigurator and EEZEndToEndAccess roles.

eezdlaPurpose

eezdla — Allows to export the currently active System Automation ApplicationManager resource topology to an Identity Markup Lanugage (IdML) discoverybook. You can load the resulting IdML book into IBM Tivoli ApplicationDependency Discovery Manager (TADDM). After the IdML book is loaded into


TADDM, the configuration items related to the System Automation ApplicationManager instance that have been loaded into TADDM before are replaced.

Format

eezdla

Comments

The eezdla command discovers the System Automation Application Managerresource topology. The discovery is based on the active end-to-end automationpolicy. The resulting discovery book is an IdML file. You can load the file into IBMTivoli Application Dependency Discovery Manager.

By default, the discovery book is written to the Tivoli Common Directory on thelocal file system where the command is invoked. Use the end-to-end automationmanager configuration tool cfgeezdmn to modify the output directory or to specifya remote system to save the discovery book.

Return codes

0 IdML discovery book has been created successfully.

1 Command has been invoked with a parameter, although no parameters aresupported. The IdML book has not been created.

2 Failed to create an IdML discovery book. See the log file of the end-to-endautomation engine for related messages.

Authorization

EEZMonitor and EEZEndToEndAccess roles are required to obtain the resourcetopology from the end-to-end automation manager. Write access to the IdML bookdirectory is required to write the discovery book to the file system.

Data model mappingSystem Automation Application Manager integrates with the ApplicationDependency Discovery Manager (TADDM) through the Discovery Library Adapter(DLA) to discover system resources. This information is output as XML files,referred to as Books, which conform to the Discovery Library IdML XML schemaand Common Data Model (CDM). The Books can be loaded by various products,including Change and Configuration Management Database (CCMDB) andBusiness Service Manager (TBSM) products.

The relationships between System Automation Application Manager concepts andthe Common Data Model are listed in Table 21.

Table 21. Data model mapping

System Automation Application ManagerCommon Data Model (CDM), asimplemented in TADDM

System Automation manager Management Software System (MSS)

(in CCMDB also known as OperationalManagement Product (OMP))

Static and dynamic (runtime) data Static data

end-to-end automation domain BusinessSystem


Table 21. Data model mapping (continued)

System Automation Application ManagerCommon Data Model (CDM), asimplemented in TADDM

Resource (group, reference) BusinessSystem

Membership relationship Federates relationship

Automation relationship Uses relationship

Resource identified by resource key Configuration item (BusinessSystem)identified by:

v CDM naming rule (for TADDM)

v Source token (for SA AM)

To use the Discovery Library Adapter effectively you are recommended to followthese guidelines.

Data mappingv Map the static aspects of the active automation resource topology, based on the

currently active end-to-end automation policy.v If at all possible, use existing CDM classes.

New MSS-specific classes have the potential to overload the model withoutbeing reused by other products, which contradicts the idea of a common datamodel.

v The end-to-end automation domain is mapped to a BusinessSystem CI thatfederates all BusinessSystem CIs that are based on top-level resources of theend-to-end automation domain.

Data reductionv Map static information only, not runtime. Dynamic runtime information changes

too quickly and is not appropriate to be stored in the CMDB.v If more details or runtime information are needed, launch the operations

console.v Fine-grained automation relationships (StartAfter, StopAfter (reversed),

ForcedDownBy) are mapped to the generic "uses" CDM relationship.

Combining MSS and the source token provides:v Information required to enable a "launch in context" of the operations console.

This is contained in the System Automation Application Manager configurationitems,

v Information required for programmatic access via System AutomationApplication Manager WebServices (EEZIM).

Policy XML referenceFind out everything you want to know about policy XML reference informationand messages for System Automation Application Manager end-to-end automationand disaster recovery.

End-to-end automation policy XML reference

This topic lists the XML elements, sub-elements, and attributes of end-to-endautomation policies in alphabetical order. For each element, the followinginformation is provided:


Name The name and a short description of the element or sub-element.

ExamplesOne or more examples showing how the element is used.

AttributesDescriptions of the element's attributes.

Contexts

Childrena list of elements the element can contain

Parentsa list of elements that can directly contain the element

OccurrenceThe possible number of occurrences of the element.

XML special charactersThe characters "&", "<", and ">" cannot be used directly for XML property values.If you want to use these characters, you have to use the replacement text asspecified in Table 22

Table 22. XML special characters

Character Replacement text

& &

< <

> >

AutomationDomainThe AutomationDomain element is used within a ResourceReference specification.It is used to specify the name of the first-level automation domain that hosts theReferencedResource. Maximum number of characters supported: 64.

Examples<ResourceReference name="WebSphere EE">

<DesiredState>Offline</DesiredState><Owner>Harry Smith</Owner><InfoLink>http://www.example.com/Websphere/help</InfoLink><ReferencedResource>

<AutomationDomain>FEPLEX2</AutomationDomain><Name>WAS</Name><Class>APG</Class><Node>node1</Node>

</ReferencedResource></ResourceReference>

AttributesNone.

Contexts

ChildrenNone.

ParentsReferencedResource

OccurrenceOnce.


AutomationDomainNameThe AutomationDomainName element specifies the name of the end-to-endautomation domain for which the policy will be used. A policy can only beactivated if the name specified in its AutomationDomainName element is identicalto the name specified on the Domain page of the configuration dialog (fieldDomain name). Maximum number of characters supported: 64.

Examples<PolicyInformation>

<PolicyName>Sample E2E Policy</PolicyName><AutomationDomainName>FriendlyE2E</AutomationDomainName><PolicyToken> 1.0.1</PolicyToken><PolicyAuthor>Michael Atkins</PolicyAuthor><PolicyDescription>Sample policy for domain

FriendlyE2E</PolicyDescription></PolicyInformation>

AttributesNone.

Contexts

ChildrenNone.

ParentsPolicyInformation

OccurrenceOnce.

AutomationPolicyThe AutomationPolicy element is the top-level element of the end-to-endautomation policy. It serves as a container for all other elements of the policy.

Examples<AutomationPolicy version="1.0"

xmlns="http://www.ibm.com/TSA/Policy.xsd"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ibm.com/TSA/Policy.xsd EEZPolicy.xsd">

...</AutomationPolicy>

Attributes

version="VersionNumber"Identifies the minimum version of the System AutomationApplication Manager. The attribute is required. Maximum numberof characters supported: 32

xmlns="NamespaceURL"Name space declaration for this policy. The attribute is requiredand must be specified as presented in the example above.

xmlns:xsi="SchemaInstanceURL"Identifies the XML schema format for this policy XML. Theattribute is required and must be specified as presented in theexample above.

xsi:schemaLocation="SchemaURL"Identifies the XML schema to which this XML policy mustconform. The attribute is required and must be specified aspresented in the example above.


Contexts

ChildrenPolicyInformation, ResourceReference, ResourceGroup,ChoiceGroup, ReplicationReference, Relationship, ServerGroup

ParentsNone.

OccurrenceOnce.

AvailabilityTargetThe AvailabilityTarget element is used to define the number of members within aServerGroup. The ServerGroup tries to start and to keep the number of membersonline that are defined in the AvailabilityTarget element.

Refer to “ServerGroup” on page 121 for a description about how the availabilitytarget affects the automation behavior of a ServerGroup.

The value for the AvailabilityTarget must be an integer value. The minimum valueis one and the maximum value is the number of members that are defined in theServerGroup. The value range of AvailabilityTarget is:1 <= AvailabilityTarget <= number of group members

Example<ServerGroup name="HTTP Servers"><DesiredState>Online</DesiredState><Description>ServerGroup which tries to keep 3 HTTP

servers online</Description><Owner>Jenny Parker</Owner><InfoLink>http://www.friendly.com/server</InfoLink><AvailabilityTarget>3</AvailabilityTarget><Members><ResourceReference name="HTTP Server 1"/><ResourceReference name="HTTP Server 2"/><ResourceReference name="HTTP Server 3"/><Members></ServerGroup>

AttributesNone

Contexts

ChildrenNone

ParentsServerGroup

OccurrenceOnce

ChoiceGroupThe ChoiceGroup element is used as a logical container for a collection ofredundant, equivalent end-to-end automation domain resources of which one isdefined as the preferred member. If the group's desired state is Online, the preferredmember is active and the other members of the group serve as standbys. Theautomation manager will try to keep the preferred member online and will restart itin place if it fails. It will also try to keep all other members than the preferred


member offline. If the preferred member fails or is to be stopped, an operator canstart one of the remaining members of the ChoiceGroup.

Example<ChoiceGroup name="HTTP Server">

<DesiredState> Offline </DesiredState><Description>Choice group for choosing one HTTP Server</Description><Owner>Jenny Parker</Owner><InfoLink>http://www.friendly.com/choice</InfoLink><Members>

<ResourceReference name="HTTP Server Prim" preferred="true"/><ResourceReference name="HTTP Server Backup"/>

</Members></ChoiceGroup>

Attributes

name="ChoiceGroupName"The attribute is used to specify the name of the ChoiceGroup. Thename must be unique within an XML policy document, that is, thename that is used for a ChoiceGroup must not be used for anyother ChoiceGroup, ResourceGroup or ResourceReference in thesame XML policy. The attribute is required.

The name can have a maximum of 64 characters. Do not use morethan one blank to separate strings within the name. Duplicateblanks will be ignored.

preferred="true|false"To specify the preferred member of a ChoiceGroup. This attributecan be set only in the context of higher-level ChoiceGroupspecifications, that is, in the children of ChoiceGroup subelementMembers.

businessCritical="true|false"To mark the ChoiceGroup and all its members as business criticalworkload. Business critical workload can be specified only indisaster recovery policies, which are described in “Disasterrecovery policy XML reference” on page 151.

switchableByDROnly="true|false"This attribute is used to specify a disaster recovery ChoiceGroup.Disaster recovery ChoiceGroups can be specified only in disasterrecovery policies, which are described in “Disaster recovery policyXML reference” on page 151.

Contexts

ChildrenDescription, DesiredState, InfoLink, Members, Owner, ServerGroup

ParentsAutomationPolicy

In ResourceGroup specifications:

ChildrenNone

ParentsMembers

In Relationship specifications:


ChildrenNone

ParentsSource, Target

Occurrence0 to any

ClassThe Class element is used within a ResourceReference definition. It specifies theclass of the first-level automation ReferencedResource (for example,IBM.ResourceGroup). The element is optional, but must be specified forReferencedResources that are managed by System Automation for Multiplatformsor System Automation for z/OS. Maximum number of characters supported: 64

System Automation: Only create resource references to first-level automationresources of Class type IBM.ResourceGroup. Resources references that refer tofirst-level automation resources of class types IBM.Application, IBM.ServiceIP, andIBM.Test may cause undesired effects or severe problems in first-level automationmanagement.

Example<ResourceReference name="WebSphere EE">

<DesiredState>Offline</DesiredState><Description>Resource reference WebSphere EE </Description><Owner>Harry Smith</Owner><InfoLink>http://www.example.com/Websphere/help</InfoLink><ReferencedResource>



AttributesNone

Contexts

ChildrenNone


Occurrence0 to 1

DescriptionThe Description element is used to add a free text that provides furtherinformation about the parent element. Maximum number of characters supported:1024

Example

<Description>Fixed Resource - This is the error reporting daemon ofxDR.</Description>

AttributesNone

Contexts


ChildrenNone

ParentsChoiceGroup, ResourceGroup, ResourceReference,ReplicationReference, ServerGroup

Occurrence0 to 1

DesiredRoleThe DesiredRole element is used to define the default desired replication directionfor its parent element, which can only be a ReplicationReference. Possible valuesare "H1-H2" and "H2-H1". Maximum number of occurrences per parent element isone. The element is not optional.

Example<ReplicationReference name="Data Replication MMSession"><DesiredState>Offline</DesiredState><DesiredRole>H1-H2</DesiredRole><Description>Resource reference to MMSession data replication </Description><Owner>Harry Smith</Owner><InfoLink>http://www.example.com/help/TPCR.html</InfoLink><ReferencedReplicationResource>

<ReplicationDomain>TPCR</ReplicationDomain><Name>MMSession</Name></ReferencedReplicationResource></ResourceReference>

AttributesNone

Contexts

ChildrenNone

ParentsReplicationReference

OccurrenceOnce

DesiredStateThe DesiredState element is used to define the default desired state (theautomation goal) for its parent element. Possible values are Online and Offline.The end-to-end automation manager will try to keep the resource in theDesiredState.

Maximum number of occurrences per parent element: 1 As the element is optional,it can be omitted. In such a case, the following rules apply:v If the desired state for a top-level resource reference is not defined in the policy,

the default desired state is set to Online.v If the desired state for a top-level resource group is not defined in the policy, the

default desired state is set to Online.The end-to-end automation manager will try to keep all members of the resourcegroup (including nested resource groups and their members) online. Desiredstate settings for individual resource references or nested resource groups areignored.

v If the desired state for a choice group is not defined in the policy, the defaultdesired state is set to Online. The end-to-end automation manager will try tokeep the preferred member online and the other members offline.



<DesiredState>Offline</DesiredState><Description>Resource reference WebSphere EE</Description><Owner>Harry Smith</Owner><InfoLink>http://www.example.com/Websphere/help</InfoLink><ReferencedResource>



AttributesNone

Contexts

ChildrenNone


Occurrence0 to 1

DRPolicyThe DRPolicy element is used in disaster recovery policies to include the disasterrecovery policy drml file. For a detailed description of disaster recovery policiessee “Disaster recovery policy XML reference” on page 151. The content must be thename of a drml file located in the policy pool. Maximum number of characterssupported: 1024.

Example<PolicyInformation><PolicyName>Sample Disaster Recovery Policy</PolicyName><AutomationDomainName>FriendlyE2E</AutomationDomainName><PolicyToken> 1.0.1</PolicyToken><PolicyAuthor>Michael Atkins</PolicyAuthor><PolicyDescription>Sample disaster recovery policy for domainFriendlyE2E</PolicyDescription><DRPolicy>sampleDRPolicy.drml</DRPolicy>

</PolicyInformation>

AttributesNone

Contexts

ChildrenNone


OccurrenceOnce

InfoLinkThe element InfoLink is used to specify the URL of an HTML page where theoperator can find additional information about the resource. Maximum number ofcharacters supported: 1024



<DesiredState>Offline</DesiredState><Description>Resource reference WebSphere EE</Description><Owner>Harry Smith</Owner><InfoLink>http://www.example.com/Websphere/help</InfoLink><ReferencedResource>



AttributesNone

Contexts

ChildrenNone


Occurrence0 to 1

NodeThe element Node is used within a ReferencedResource specification. It is used tospecify the host name (System Automation) or system name (System Automationfor z/OS) where the first-level automation resource (the ReferencedResource) islocated. If the useWildcard attribute of the ReferencedResource is set to true, thenthis name can contain the wildcard character ("*").

Restrictions

v Maximum number of characters supported: 256v Host name or system name must be specified in first-level domain syntax.v The Node element is optional. Only specify the Node element when you create a

resource reference for a fixed resource. Do not specify the node for any othertype of first-level automation resource.Note that creating resource references for fixed resources is not recommended.

Example<ResourceReference name="NFS Client">

<DesiredState>Offline</DesiredState><Description>Resource reference NFS Client </Description><Owner>Henry Smith</Owner><InfoLink>http://www.example.com/help/NFS/?help+NFS+Client</InfoLink><ReferencedResource><AutomationDomain>cm1cm2</AutomationDomain><Name>nfs-client</Name><Class>IBM.ResourceGroup</Class><Node>lnxcm2</Node></ReferencedResource>

</ResourceReference>

AttributesNone

Contexts

ChildrenNone



Occurrence0 to 1

MembersThe Members element is a container element. It contains the list of resources thatare members of an end-to-end automation ResourceGroup, ChoiceGroup, orServerGroup.

Example<ResourceGroup name="Friendly Computer Shop" >

<DesiredState>Offline</DesiredState><Description>Resource group Friendly Computer Shop</Description><Owner>Jerr Owens</Owner><InfoLink>http://www.example.com/help/policy/compshop.html</InfoLink><Members>

<ResourceGroup name="mySAP Solutions"/><ResourceReference name="WebSphere AE"/>

</Members></ResourceGroup>

Example of a Members element in a ChoiceGroup specification:<ChoiceGroup name="HTTP Server">

<DesiredState> Offline </DesiredState><Description>Choice group for choosing one HTTP Server</Description><Owner>Jenny Parker</Owner><InfoLink>http://www.example.com/choice</InfoLink><Members>

<ResourceReference name="HTTP Server Prim" preferred="true"/><ResourceReference name="HTTP Server Backup"/>

</Members></ChoiceGroup>

AttributesNone

Contexts

ChildrenResourceReference, ResourceGroup, ChoiceGroup,ReplicationReference, ServerGroup

In ServerGroup specifications:

ChildrenResourceReference

ParentsChoiceGroup, ResourceGroup , Server Group

OccurrenceOnce

NameThe Name element is used within a ReferencedResource specification. It is used tospecify the actual name the ReferencedResource in its first-level domain. Thisname may be different from the name specified for the ResourceReference thatrefers to this resource. If the useWildcard attribute of the ReferencedResource is setto true, then this name can contain the wildcard character ("*"). Maximum numberof characters supported: 64


Example<ResourceReference name="SAP AppServer">

<DesiredState>Offline</DesiredState><Description>Resource reference SAP AppServer </Description><Owner>Jenny Parker</Owner><InfoLink>http://www.example.com/help/policy/SAPAPP.html</InfoLink><ReferencedResource>

<AutomationDomain>FEClusterSAP</AutomationDomain><Name>SAP AppServer</Name><Class>ResourceGroup</Class><Node>node4</Node>


AttributesNone

Contexts

ChildrenNone


OccurrenceOnce

OwnerThe element Owner is used to provide information about the owner of the parentelement, for example, the name and telephone number of the owner of areferenced resource. Maximum number of characters supported: 1024

Example<ResourceReference name="SAP AppServer">

<DesiredState>Offline</DesiredState><Description>Resource reference SAP AppServer </Description><Owner>Jenny Parker</Owner><InfoLink>http://www.example.com/help/policy/SAPAPP.html</InfoLink><ReferencedResource>

<AutomationDomain>FEClusterSAP</AutomationDomain><Name>SAP AppServer</Name><Class>ResourceGroup</Class><Node>node4</Node>


AttributesNone

Contexts

ChildrenNone

ParentsResourceReference, ChoiceGroup, ResourceGroup,ReplicationReference, ServerGroup

Occurrence0 to 1

PolicyAuthorThe PolicyAuthor element is used to identify the author of the policy. Maximumnumber of characters supported: 64.


Example<PolicyInformation>

<PolicyName>Sample E2E Policy</PolicyName><AutomationDomainName>FriendlyE2E</AutomationDomainName><PolicyToken> 1.0.1</PolicyToken><PolicyAuthor>Michael Atkins</PolicyAuthor><PolicyDescription>Sample policy for domain FriendlyE2E</PolicyDescription>


AttributesNone

Contexts

ChildrenNone


Occurrence0 to 1

PolicyDescriptionThe PolicyDescription element is available for adding a free text to the XMLdocument. It can be used, for example, to maintain a change history within the file.Maximum number of characters supported: 1024


<PolicyName>Sample E2E Policy</PolicyName><AutomationDomainName>FriendlyE2E</AutomationDomainName><PolicyToken> 1.0.1</PolicyToken><PolicyAuthor>Michael Atkins</PolicyAuthor><PolicyDescription>Sample policy for domain FriendlyE2E

Last Update: 08/16/04Last Editor: Michael AtkinsChange History:------------------------------------------------------Date Name Description------------------------------------------------------08/16/05 Michal Atkins Initial policy definition------------------------------------------------------

</PolicyDescription></PolicyInformation>

AttributesNone

Contexts

ChildrenNone


Occurrence0 to 1

PolicyInformationThe PolicyInformation element contains subelements that uniquely identify thispolicy.

Restrictions

The element is required and must occur only once in an XML policy file.





AttributesNone

Contexts

ChildrenPolicyName, AutomationDomainName, PolicyToken, PolicyAuthor,PolicyDescription, DRPolicy


OccurrenceOnce

PolicyNameThe PolicyName element is used to specify a meaningful name for the specificpolicy. Maximum number of characters supported: 64




AttributesNone

Contexts

ChildrenNone


OccurrenceOnce

PolicyTokenThe PolicyToken element specifies the version of the policy. It should be updatedwhenever the policy is changed. Maximum number of characters supported: 64




AttributesNone

Contexts


ChildrenNone


OccurrenceOnce

ReferencedReplicationResourceThe ReferencedReplicationResource element is a child of the ReplicationReferenceelement. The children of the ReferencedReplicationResource element describe thereplication session in a TPC-R domain to which the ReplicationReference refers to.

Restrictions

The value for the ReferencedReplicationResource element and for itschildren must be unique within the policy. The sameReferencedReplicationResource must not be referenced by more than oneReplicationReference.

Example<ReplicationReference name="Data Replication MMSession"><DesiredState>Offline</DesiredState><DesiredRole>H1-H2</DesiredRole><Description>Resource reference to MMSession data replication </Description><Owner>Harry Smith</Owner><InfoLink>http://www.example.com/help/TPCR.html</InfoLink><ReferencedReplicationResource><ReplicationDomain>TPCR</ReplicationDomain>

<Name>MMSession</Name></ReferencedReplicationResource></ReplicationReference>

AttributesNone

Contexts

ChildrenReplicationDomain, Name

ParentsReplicationReference

OccurrenceOnce

ReferencedResourceThe ReferencedResource element is a child of the ResourceReference element. Thechildren of the ReferencedResource element are used to describe the actualfirst-level automation resource to which the ResourceReference refers.

Restrictions

v The ReferencedResource as defined by the values specified for itschildren (AutomationDomain, Name, Class, and Node) must be uniquewithin the policy, that is, the same ReferencedResource must not bereferenced by more than one ResourceReference.

v System Automation for Multiplatforms: Resource references shouldalways point to top-level resources (resource groups of resource classtype IBM.ResourceGroup). Creating resource references for first-levelautomation resources of resource class types IBM.Application,IBM.ServiceIP, and IBM.Test is not recommended and may causeproblems in first-level automation management.


ExampleExample 1: Regular resource reference:<ResourceReference name="Enterprise DB2">

<DesiredState>Offline</DesiredState><Description>Resource reference Enterprise DB2 </Description><Owner>Bob Owens</Owner><InfoLink>http://www.example.com/help/DB2</InfoLink><ReferencedResource>

<AutomationDomain>FEPLEX2</AutomationDomain><Name>DB2</Name><Class>ResourceGroup</Class><Node>node1</Node>


Example 2: Dynamic resource reference:<ResourceReference name="WAS">

<DesiredState>Online</DesiredState><Description>Dynamic resource reference WAS*</Description><Owner>Jane Smith</Owner><InfoLink>http://www.example.com/help/WAS</InfoLink>

<ReferencedResource useWildcard="true"><AutomationDomain>ALAProduction</AutomationDomain><Name>WAS*</Name><Class>IBM.RemoteApplication</Class><Node>node*</Node>


AttributesuseWildcard="true|false"

Use this optional attribute to indicate if the resource reference is a dynamicresource reference. If it is set to true, then the Name and Node elements cancontain one or multiple wildcard character(s) ("*").

Contexts

ChildrenAutomationDomain, Name, Class, Node

ParentsResourceReference

OccurrenceOnce

RelationshipThe sub-elements of the Relationship element are used to define the relationship(StartAfter, StopAfter, ForcedDownBy) between two end-to-end automationresources (ResourceReferences or end-to-end automation groups).

Example<Relationship>

<Source><ResourceReference name="DB2 Connect Client"/>

</Source><Type> StartAfter</Type><Target>

<ResourceReference name="Enterprise DB2"/></Target>

</Relationship>

AttributesNone


Contexts

ChildrenSource, Target, Type


Occurrence0 to any

ReplicationDomainThe ReplicationDomain element is used within a ReplicationReferencespecification. Is specifies the name of the TPC-R replication domain that hosts theReferencedReplicationResource. For example, the replication session in the TPC-Rservers. Maximum number of characters supported: 64.

Example<ReplicationReference name="Data Replication MMSession"><DesiredState>Offline</DesiredState><DesiredRole>H1-H2</DesiredRole><Description>Resource reference to MMSession data replication </Description><Owner>Harry Smith</Owner><InfoLink>http://www.example.com/help/TPCR.html</InfoLink><ReferencedReplicationResource><ReplicationDomain>TPCR</ReplicationDomain><Name>MMSession</Name></ReferencedReplicationResource></ReplicationReference>

AttributesNone

Contexts

ChildrenNone

ParentsReferencedReplicationResource

OccurrenceOnce

ReplicationReferenceThis element is used in the following three contexts:v To define a reference to a replication session, that is provided by a TPC-R

replication domain. The element has a number of required sub-elements.v To specify which replication references are members of a ResourceGroup.v To specify the source and target of a relationship.

The value of the name attribute must be unique within the policy. The namecannot be used for more than one ReplicationReference. The same name must notbe used for a ChoiceGroup, ResourceGroup, or ResourceReference.

Example<ReplicationReference name="Data Replication MMSession"><DesiredState>Offline</DesiredState><DesiredRole>H1-H2</DesiredRole><Description>Resource reference to MMSession data replication </Description><Owner>Harry Smith</Owner><InfoLink>http://www.example.com/help/TPCR.html</InfoLink><ReferencedReplicationResource>


<ReplicationDomain>TPCR</ReplicationDomain><Name>MMSession</Name>

</ReferencedReplicationResource></ResourceReference>

Example of a ReplicationReference element in a ResourceGroupspecification:<ResourceGroup name="Friendly Computer Shop"><DesiredState>Offline</DesiredState><Description>Resource group Friendly Computer Shop</Description><Owner>Jerry Owens</Owner><InfoLink>http://www.example.com/help/policy/compshop.html</InfoLink><Members><ResourceGroup name="mySAP Solutions"/><ResourceReference name="WebSphere AE"/><ReplicationReference name="Data Replication MMSession"/></Members></ResourceGroup>

Example of a ReplicationReference element in a Relationship specification:<Relationship><Source><ResourceReference name="WebSphere EE"/></Source><Type>StartAfter</Type><Target><ReplicationReference name="Data Replication MMSession " /></Target></Relationship>

Attributes

name=ReplicationReferenceNameThe name by which the end-to-end automation domain resourcewill be known in the end-to-end automation domain. The namecan differ from the name used for theReferencedReplicationResource in the replication domain. Thename can have a maximum of 64 characters. Do not use more thanone blank to separate strings within the name. Duplicate blankswill be ignored.

Contexts

ChildrenDesiredState, Description, Owner, InfoLink, DesiredRole,ReferencedReplicationResource


In ResourceGroup specifications:

ChildrenNone

ParentsMembers


ChildrenNone


Occurrence0 to any


ResourceGroupThe ResourceGroup element is used to define end-to-end automation resourcegroups. ResourceGroups can be nested, but a ResourceGroup must not be amember of more than one ResourceGroup.

Example<ResourceGroup name="Friendly Computer Shop" >




Attributes

name="ResourceGroupName"The attribute is used to specify the name of the ResourceGroup.The name must be unique within an XML policy document, that is,the name that is used for a ResourceGroup must not be used foranother ResourceGroup, ChoiceGroup, ReplicationReference orResourceReference within the same XML policy. The attribute isrequired.


preferred="true|false"To specify the preferred member of a ChoiceGroup. This attributecan be set only in the context of ChoiceGroup specifications, thatis, in the children of ChoiceGroup subelement Members.

businessCritical="true|false"To mark the ResourceReference as business critical workload.Business critical workload can be specified only in disasterrecovery policies, which are described in “Disaster recovery policyXML reference” on page 151.

Contexts

ChildrenDescription, Owner, InfoLink, Members, ServerGroup


Occurrence0 to any

ResourceReferenceThis element is used in three contexts:v It is used to define an end-to-end automation resource. Each XML policy must

contain at least one ResourceReference element. The element has a number ofrequired sub-elements.

v In ResourceGroup and ChoiceGroup definitions, it is used to specify whichresources references are members of a group.

v In Relationship definitions, it is used to specify the source and target of arelationship.


The value of the Name attribute must be unique within the policy, that is, thename cannot be used for more than one ResourceReference. The same name mustnot be used for a ReplicationReference, ChoiceGroup or ResourceGroup.

Example<ResourceReference name="WebSphere AE">

<DesiredState>Offline</DesiredState><Description>Resource reference WebSphere AE </Description><Owner>Harry Smith</Owner><InfoLink>http://www.example.com/help/Websphere.html</InfoLink><ReferencedResource>

<AutomationDomain>FECluster</AutomationDomain><Name>WebSphere AppServer</Name><Class>ResourceGroup</Class><Node>node2</Node>


Example of a ResourceReference element in a ResourceGroup specification:<ResourceGroup name="Friendly Computer Shop" >




Example of ResourceReference elements in a Relationship specification:<Relationship>

<Source><ResourceReference name="WebSphere EE"/>


<ResourceReference name="DNS Server"/></Target>

</Relationship>

Attributes

name="ResourceReferenceName"The name by which the end-to-end automation domain resourcewill be known in the end-to-end automation domain. The namespecified here can differ from the name used for theReferencedResource in its first-level automation domain.


preferred="true|false"To specify the preferred member of a ChoiceGroup. This attributecan be set only in the context of ChoiceGroup specifications, thatis, in the children of ChoiceGroup subelement Members.

businessCritical="true|false"To mark the ResourceReference as business critical workload.Business critical workload can be specified only in disasterrecovery policies, which are described in “Disaster recovery policyXML reference” on page 151.

Contexts

ChildrenDesiredState, Description, Owner, InfoLink, ReferencedResource



n ResourceGroup or ChoiceGroup specifications:

ChildrenNone

ParentsMembers


ChildrenNone


Occurrence0 to any

ServerGroup

The ResourceGroup element is used to define end-to-end automationServerGroups. ServerGroups can be a member of other groups, but a ServerGroupmust not be a member of more than one group.

The members of the ServerGroup may not be the source or target of relationships.

Example<ServerGroup name="serverGroup"><DesiredState>Offline</DesiredState><Description>This is a basic sample of a server group</Description><Owner>Jenny Parker</Owner><InfoLink>http://www.friendly.com/server</InfoLink><AvailabilityTarget>2</AvailabilityTarget><Members><ResourceReference name="Ref1"/><ResourceReference name="Ref2"/><ResourceReference name="Ref3"/></Members></ServerGroup>

Attributes

name="ServerGroupName"The attribute is used to specify the name of the ServerGroup. Thename must be unique within an XML policy document. The namethat is used for a ServerGroup must not be used for anotherresource element within the same XML policy. The attribute isrequired.


Contexts

Children

v “DesiredState” on page 108: mandatoryv “Description” on page 107: optionalv “Owner” on page 112: optional


v “InfoLink” on page 109: optionalv “Members” on page 111: mandatoryv “AvailabilityTarget” on page 105: mandatory

A ServerGroup contains the following members:v “ResourceReference” on page 119

Parents

v “AutomationPolicy” on page 104v “Members” on page 111v “ChoiceGroup” on page 105v “ResourceGroup” on page 119

Occurrence0 to any

SourceThe Source element is a container element. Its subelement ResourceReference,ResourceGroup, ReplicationReference, and ChoiceGroup specifies the dependentresource (ResourceReference, ResourceGroup, ReplicationReference, andChoiceGroup) in a relationship (element Relationship).




<ResourceReference name="DNS Server"/></Target>

</Relationship>

AttributesNone

Contexts

ChildrenResourceReference, ResourceGroup, ChoiceGroup,ReplicationReference

ParentsRelationship

OccurrenceOnce

TargetThe Target element is used to specify the supporting resource (ResourceReference,ResourceGroup, ReplicationReference, or ChoiceGroup) in a relationship (elementRelationship).



</Source><Type> StartAfter</Type>


<Target><ResourceReference name="DNS Server"/>

</Target></Relationship>

AttributesNone

Contexts

ChildrenResourceReference, ResourceGroup, ChoiceGroup,ReplicationReference

ParentsRelationship

OccurrenceOnce

TypeThe Type element is used to specify the relationship between two resources (theSource and the Target). The relationship defines in which sequence the resourcesmust be started or stopped. The automation manager will interpret a relationshipdefinition as automation rule and will ensure that the resources are started orstopped in the correct sequence.

Possible values:

StartAfterDefines in which sequence two dependent resources must be started.For arelationship Resource A StartAfter Resource B this means that when resourceA is to be started, Resource B is started first. Only after Resource B hasbecome online will Resource A be started.

StopAfterDefines in which sequence two resources must be stoppedFor arelationship Resource A StopAfter Resource B this means that when resourceA has to be stopped, Resource B is stopped first. Only after Resource B hasstopped will Resource A be stopped.

ForcedDownByDefines that a resource must be forced down when another resource isstopped.For a relationship Resource A ForcedDownBy Resource B this meansthat resource A must be forced offline if Resource B goes offlineunexpectedly or is forced down itself. Resource A and Resource B maystop in parallel. The force down of Resource A will be triggered in thefollowing situations:v When Resource B enters in any of the regular down states (Offline) after

having previously been in an online state.v When Resource B enters any of the terminal down states (Failed offline),

regardless of its former state.



</Source><Type> StartAfter</Type>


<Target><ResourceReference name="DNS Server"/>


AttributesNone

Contexts

ChildrenNone

ParentsRelationship

OccurrenceOnce

Automation policy rule referenceWhen you define an end-to-end automation policy, you must ensure that a numberof rules are observed. The compliance with these rules is checked automaticallywhen you activate a policy. If one of the rules is violated, a warning or an errormessage is issued. Policies for which only warnings are generated can be activated,errors prohibit the activation of a policy.

You can check the rules also without actually activating a policy by using theeezpolicychecker command. For more information, see “eezpolicychecker” onpage 100.

Rules for resource groups and choice groupsAn error message is issued if one of the following rules is not observed:v Only resource references that are defined in the policy can be added as members

to a group.v A choice group or a resource group cannot belong to more than one group.v A resource reference must not be a member of more than one choice group.v A resource reference must not be a member of both a resource group and a

choice group.v A member must not occur in a group more than once.

A warning message is issued if the following rule is not observed:v A member of a choice group must not be the source or the target of a

relationship.

Relationship rulesAn error message is issued if one of the following rules is not observed:v Source and target resources of a relationship must have been defined as resource

references.v A resource reference must not be the first source and the last target of a

relationship of the same type.

A warning message is issued if one of the following rules is not observed:v A relationship of type StartAfter and a relationship of StopAfter must not have

the same source and target.v A member of a choice group must not be the source or the target of a

relationship.


Rules that ensure that resource names are uniqueAn error message is issued if one of the following rules is not observed:v Each resource reference in a policy must have a unique name.v The name of a resource reference must not be used for a resource group or

choice group.v Each resource group in a policy must have a unique name.v The name of a resource group must not be used for a resource reference,

replication reference or choice group.v Each choice group in a policy must have a unique name.v The name of a choice group must not be used for a resource reference,

replication reference or resource group.v Each replication reference in a policy must have a unique name.v The name of a replication reference must not be used for a resource reference, a

choice group or resource group.

Additional rulesGeneral rule:v An end-to-end automation resource reference can only reference resources of

other automation domains.

An error message is issued if one of the following rules is not observed:v A first-level automation resource can only be referenced by one resource

reference.v Each choice group or resource group must have at least one member.v At least one resource reference must be defined in a policy.v For one member of a choice group the attribute preferred must be set to true.

If the policy is not a disaster recovery policy, an error message is issued if one ofthe following rules is not observed:v Specification of a disaster recovery ChoiceGroup is not possible. ChoiceGroup

specifications must not contain a switchableByDROnly attribute with the valuetrue.

v Specification of business critical workload is not possible. ResourceReference,ResourceGroup and ChoiceGroup specifications must not contain abusinessCritical attribute with the value true.

Sample automation policy

This is the sample automation policy sample.xml. You find it in your policy pooldirectory.<?xml version="1.0" encoding="UTF-8" ?><AutomationPolicy version="3.2.2" xmlns="http://www.ibm.com/TSA/Policy.xsd"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ibm.com/TSA/Policy.xsd EEZPolicy.xsd"><PolicyInformation><PolicyName>Sample E2E Policy</PolicyName><AutomationDomainName>FriendlyE2E</AutomationDomainName><PolicyToken>1.0.1</PolicyToken><PolicyAuthor>Michael Atkins</PolicyAuthor><PolicyDescription>Contains a sample policy for domain FriendlyE2E</PolicyDescription>

</PolicyInformation>


<ResourceReference name="Enterprise DB2"><DesiredState>Offline</DesiredState><Description>This is the reference with the name Enterprise DB2</Description><Owner>Bob Owens</Owner><InfoLink>http://www.example.com/help/DB2</InfoLink><ReferencedResource><AutomationDomain>FEPLEX2</AutomationDomain><Name>DB2</Name><Class>APG</Class><Node>node1</Node>

</ReferencedResource></ResourceReference><ResourceReference name="DB2 Connect Client"><DesiredState>Offline</DesiredState><Description>This is the reference with the name DB2 Connect Client</Description><Owner>Bob Owens</Owner><InfoLink>http://www.example.com/help/DB/Client</InfoLink><ReferencedResource><AutomationDomain>FECluster</AutomationDomain><Name>DB2 Connect</Name><Class>IBM.ResourceGroup</Class>

</ReferencedResource></ResourceReference><ResourceReference name="DB2 Connect Client Backup"><DesiredState>Offline</DesiredState><Description>This is the reference with the name DB2 Connect Client Backup</Description><Owner>Bob Owens</Owner><InfoLink>http://www.example.com/help/DB/Client</InfoLink>

- <ReferencedResource><AutomationDomain>FEPLEX2</AutomationDomain><Name>DB2 Connect</Name><Class>APG</Class><Node>node2</Node>

</ReferencedResource></ResourceReference><ResourceReference name="WebSphere EE"><DesiredState>Offline</DesiredState><Description>This is the reference with the name WebSphere EE</Description><Owner>Harry Smith</Owner><InfoLink>http://www.example.com/Websphere/help</InfoLink><ReferencedResource>


</ReferencedResource></ResourceReference><ResourceReference name="DNS Server"><DesiredState>Offline</DesiredState><Description>This is the reference with the name DNS Server</Description><Owner>Jenny McDowell</Owner><InfoLink>http://www.example.com/help/DNS Server</InfoLink><ReferencedResource><AutomationDomain>FECluster</AutomationDomain><Name>DNS Server</Name><Class>IBM.ResourceGroup</Class>

</ReferencedResource></ResourceReference><ResourceReference name="NFS Client"><DesiredState>Offline</DesiredState><Description>This is the reference with the name NFS Client</Description><Owner>Henry Smith</Owner><InfoLink>http://www.example.com/help/NFS/client/minor_01/?help+NFS+Client</InfoLink><ReferencedResource><AutomationDomain>FECluster</AutomationDomain><Name>nfs-client</Name><Class>IBM.ResourceGroup</Class>

</ReferencedResource></ResourceReference><ResourceReference name="NFS Server"><DesiredState>Offline</DesiredState><Description>This is the reference with the name "NFS Server"</Description><Owner>Bob Owens</Owner><InfoLink>file://X:/help/NFS.pdf</InfoLink><ReferencedResource><AutomationDomain>FEPLEX1</AutomationDomain><Name>NFS Server</Name><Class>APG</Class><Node>node3</Node>


</ReferencedResource></ResourceReference><ResourceReference name="WebSphere AE"><DesiredState>Offline</DesiredState><Description>This is the reference with the name WebSphere AE</Description><Owner>Harry Smith</Owner><InfoLink>http://www.example.com/help/Websphere.html</InfoLink><ReferencedResource><AutomationDomain>FECluster</AutomationDomain><Name>WebSphere AppServer</Name><Class>IBM.ResourceGroup</Class>

</ReferencedResource></ResourceReference><ResourceReference name="eMail Hosting"><DesiredState>Online</DesiredState><Description>This is the reference with the name eMail Hosting</Description><Owner>Sarah O’Neill</Owner><InfoLink>http://www.example.com/help/policy/email.html</InfoLink><ReferencedResource><AutomationDomain>FECluster</AutomationDomain><Name>Mail Server</Name><Class>IBM.Application</Class>

</ReferencedResource></ResourceReference><ResourceReference name="HTTP Server Prim"><DesiredState>Offline</DesiredState><Description>This is the reference with the name HTTP Server</Description><Owner>Owens, Bob</Owner><InfoLink>http://www.example.com/help/policy/HTTPServer.html</InfoLink><ReferencedResource><AutomationDomain>FEClusterSAP</AutomationDomain><Name>HTTP Server</Name><Class>IBM.ResourceGroup</Class>

</ReferencedResource></ResourceReference><ResourceReference name="HTTP Server Backup"><DesiredState>Offline</DesiredState><Description>This is the reference with the name HTTP Server</Description><Owner>Harry O’Neill</Owner><InfoLink>--- No help ---</InfoLink><ReferencedResource><AutomationDomain>FECluster</AutomationDomain><Name>HTTP Server Back</Name><Class>IBM.ResourceGroup</Class>

</ReferencedResource></ResourceReference><ResourceReference name="SAP ENQ Server"><DesiredState>Offline</DesiredState><Description>This is the reference with the name SAP ENQ Server</Description><Owner>Bob Owens</Owner><InfoLink>http://www.example.com/help/policy/enq.html</InfoLink><ReferencedResource><AutomationDomain>FEPLEX1</AutomationDomain><Name>SAP ENQ Env.</Name><Class>IBM.Application</Class>

</ReferencedResource></ResourceReference><ResourceReference name="SAP AppServer"><DesiredState>Offline</DesiredState><Description>This is the reference with the name SAP AppServer</Description><Owner>Jenny Parker</Owner><InfoLink>http://www.example.com/help/policy/SAPAPP.html</InfoLink><ReferencedResource><AutomationDomain>FEClusterSAP</AutomationDomain><Name>SAP AppServer</Name><Class>IBM.ResourceGroup</Class>


- - - - - <ChoiceGroup name="HTTP Server"><DesiredState>Offline</DesiredState><Description>This is the choice group for choosing one HTTP Server</Description><Owner>Jenny Parker</Owner><InfoLink>http://www.example.com/choice</InfoLink><Members><ResourceReference name="HTTP Server Prim" preferred="true" />


<ResourceReference name="HTTP Server Backup" /></Members>

</ChoiceGroup><ChoiceGroup name="DB2"><DesiredState>Offline</DesiredState><Description>This is the choice group for choosing one DB2 Client</Description><Owner>Jenny Parker</Owner><InfoLink>http://www.example.com/choice</InfoLink><Members><ResourceReference name="DB2 Connect Client" preferred="true" /><ResourceReference name="DB2 Connect Client Backup" />

</Members></ChoiceGroup><ResourceGroup name="WebSphere E2E"><DesiredState>Offline</DesiredState><Description>This is the collection group with the name WebSphere E2E</Description><Owner>Harry Smith</Owner><InfoLink>http://www.example.com/help/policy/Websphere.html</InfoLink><Members><ResourceReference name="Enterprise DB2" /><ResourceReference name="WebSphere EE" /><ResourceReference name="DNS Server" /><ResourceReference name="NFS Client" /><ResourceReference name="NFS Server" /><ResourceReference name="WebSphere AE" />

</Members></ResourceGroup><ResourceGroup name="mySAP Solutions"><DesiredState>Offline</DesiredState><Description>This is the collection group with the name mySAP Solutions</Description><Owner>Jerry Owens</Owner><InfoLink>http://www.example.com/help/policy/mysap/Solution.html</InfoLink><Members><ResourceReference name="DNS Server" /><ResourceReference name="SAP ENQ Server" /><ResourceReference name="SAP AppServer" />

</Members></ResourceGroup><ResourceGroup name="Friendly Computer Shop"><DesiredState>Offline</DesiredState><Description>This is the collection group with the name Friendly Computer Shop</Description><Owner>Jerr Owens</Owner><InfoLink>http://www.example.com/help/policy/compshop.html</InfoLink><Members><ResourceGroup name="mySAP Solutions" /><ResourceReference name="WebSphere AE" /><ChoiceGroup name="HTTP Server" />


- - - - - - <Relationship><Source><ResourceReference name="WebSphere EE" />

</Source><Type>StartAfter</Type><Target><ResourceReference name="DNS Server" />

</Target></Relationship><Relationship><Source>


<ResourceGroup name="mySAP Solutions" /></Source><Type>StartAfter</Type><Target><ChoiceGroup name="DB2" />

</Target></Relationship><Relationship><Source><ResourceReference name="NFS Client" />

</Source><Type>ForcedDownBy</Type><Target><ResourceReference name="NFS Server" />

</Target></Relationship><Relationship><Source><ResourceReference name="NFS Client" />

</Source><Type>StartAfter</Type><Target><ResourceReference name="SAP AppServer" />

</Target></Relationship><Relationship>+ <Source>

<ResourceReference name="SAP AppServer" /></Source><Type>StartAfter</Type><Target><ResourceReference name="SAP ENQ Server" />

</Target></Relationship><Relationship><Source><ResourceReference name="SAP ENQ Server" />

</Source><Type>StopAfter</Type><Target><ResourceReference name="SAP AppServer" />

</Target></Relationship><Relationship><Source><ResourceReference name="SAP AppServer" />

</Source><Type>ForcedDownBy</Type><Target><ResourceReference name="SAP ENQ Server" />


</AutomationPolicy>

Agentless adapter policy XML referenceThis topic lists the XML elements, sub-elements, and attributes of agentless adapterautomation policies in alphabetical order. For each element, the followinginformation is provided:




ContextsParents: a list of elements that can directly contain the element.

Children: a list of elements the element can contain.

OccurrenceThe possible number of occurrences of the element.


AutomationDomainNameThe AutomationDomainName element specifies the name of the Agentless Adapterdomain for which the policy will be used. A policy can only be activated if thename specified in its AutomationDomainName element is identical to the namespecified as one of the domains managed by the agentless adapter on the Adaptertab of the Application Manager agentless adapter configuration dialog. Maximumnumber of characters supported: 64


<PolicyName>Agentless adapter sample policy</PolicyName><AutomationDomainName>AgentlessDomain</AutomationDomainName><PolicyToken> 1.0.1</PolicyToken><PolicyAuthor>Michael Atkins</PolicyAuthor><PolicyDescription>Agentless adapter sample policy</PolicyDescription>


AttributesNone

Contexts

ChildrenNone


OccurrenceOnce

AutomationPolicyThe AutomationPolicy element is the top-level element of the Agentless Adapterpolicy. It serves as a container for all other elements of the policy.

Example<AutomationPolicy productID="EEZALAdapter" version="3.2.2"xmlns="http://www.ibm.com/TSA/EEZALPolicy.xsd"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ibm.com/TSA/EEZALPolicy.xsd EEZALPolicy.xsd ">...</AutomationPolicy>

Attributes

versionMandatory. Identifies the minimum version of the EEZSDK. Theattribute is required. Maximum number of characters supported:32.

xmlns Mandatory with fixed value "http://www.ibm.com/TSA/EEZALPolicy.xsd". Identifies the default name space for the XMLschema. Other values are rejected.

xmlns:xsiOptional with fixed value "http://www.w3.org/2001/XMLSchema-instance". Identifies the XML schema format for this policy XML.Other values are ignored.

xsi:schemaLocationOptional with fixed value "http://www.ibm.com/TSA/EEZALPolicy.xsd EEZALPolicy.xsd". Identifies the XML schema.The XML schema contains the syntax rules for a valid XML policyfile. Other values are ignored.


product IDMandatory with fixed value "EEZALAdapter". Identifies the kindof policy contained in the AutomationPolicy element.

Contexts

ChildrenPolicyInformation, Resource, IBM.RemoteApplicationAttributes

ParentsNone

OccurrenceOnce

ClassAttributesReferenceUsed to specify a reference to the remote application attributes. Enables to reusethe same IBM.RemoteApplicationAttributes specification in multiple places.

Example<Resource name="WebServer" class="IBM.RemoteApplication" node="localhost"><ClassAttributesReference>

<IBM.RemoteApplicationAttributes name=""WebServer-Attributes"/></ClassAttributesReference>

</Resource>

AttributesNone

Contexts

ChildrenIBM.RemoteApplicationAttributes

ParentsResource

OccurrenceOnce

DescriptionThe Description element is used to add a free text that provides furtherinformation about the parent element. Maximum number of characters supported:1024

Example<Desription>This is a sample web server resource.</Description>

AttributesNone

Contexts

ChildrenNone

ParentsIBM.RemoteApplicationAttributes

Occurrence0 to 1


IBM.ITMResourceAttributesUsed to specify the attributes of an Tivoli Monitoring managed resource. TheIBM.ITMResourceAttributes element defines how resources which are monitoredby a specific Tivoli Monitoring agent are started, stopped, and monitored usingthis agent. It also defines the agent’s attribute values that are used for monitoringthe availability state and how they are mapped to System Automation states. Thesame IBM.ITMResourceAttributes element can be referenced by one or multipleResource elements.

Example<IBM.ITMResourceAttributes name="IBM.ITMWebServerAgentAttributes" >

<Description>ITCAM web server agent monitoring an ApacheServer</Description><StartCommand>HT:startServer</StartCommand><StopCommand>HT:stopServer</StopCommand><MonitorAttribute>Apache_Web_Server.Status</MonitorAttribute><MonitorValueOnline>Running</MonitorValueOnline><MonitorValueOffline>Stopped</MonitorValueOffline><MonitorValueFailedOffline>Error</MonitorValueFailedOffline><UserName>sysadmin</UserName><StartCommandTimeout>60</StartCommandTimeout><StopCommandTimeout>60</StopCommandTimeout><MonitorCommandPeriod>10</MonitorCommandPeriod><Property>Version</Property><Property>Web_Server_Name</Property><Property>Start_Date_and_Time</Property><Property>Process_ID</Property><Property>Configuration_File</Property>

</IBM.ITMResourceAttributes>

Attributes

name Mandatory and must be unique. A resource element can refer tothis name. Maximum characters: 64

Contexts

ChildrenStartCommand, StopCommand, MonitorAttribute,MonitorValueOnline, MonitorValueOffline, Description, Owner,InfoLink, StartCommandTimeout, StopCommandTimeout,MonitorCommandTimeout, MonitorCommandPeriod,monitorValueFailedOffline, MonitorValueUnknown,MonitorValueStarting; MonitorValueStopping, UserName


Occurrence0 to multiple times

IBM.RemoteApplicationAttributesUsed to specify the attributes of a remote resource.

Example<IBM.RemoteApplicationAttributes name="WebServer-Attributes"><Owner>John Smith</Owner><InfoLink>http://www.ibm.com</InfoLink><Description>Sample web server resource</Description><StartCommand>/bin/touch /tmp/web1</StartCommand><StopCommand>/bin/rm /tmp/web1</StopCommand><MonitorCommand>/bin/ls -la /tmp/web1</MonitorCommand><UserName>root</UserName><MonitorCommandPeriod>10</MonitorCommandPeriod>


<MonitorCommandTimeout>5</MonitorCommandTimeout><StartCommandTimeout>10</StartCommandTimeout><StopCommandTimeout>10</StopCommandTimeout></IBM.RemoteApplicationAttributes>

Attributes

name Mandatory and must be unique. A Resource element can refer tothis name. Maximum characters: 64

Contexts

ChildrenDescription, Owner, InfoLink, StartCommand, StopCommand,MonitorCommand, StartCommandTimeout,StopCommandTimeout, MonitorCommandTimeout,MonitorCommandPeriod, MonitorCommandReturnCodes,UserName, RemoteProtocol, RemotePort



InfoLinkThe element InfoLink is used to specify the URL of an HTML page where theoperator can find additional information about the resource. Maximum number ofcharacters supported: 1024.

Example<IBM.RemoteApplicationAttributes name="WebServer-Attributes"><Owner>John Smith</Owner><InfoLink>http://www.ibm.com</InfoLink><Description>Sample web server resource</Description><StartCommand>/bin/touch /tmp/web1</StartCommand><StopCommand>/bin/rm /tmp/web1</StopCommand><MonitorCommand>/bin/ls -la /tmp/web1</MonitorCommand><UserName>root</UserName><MonitorCommandPeriod>10</MonitorCommandPeriod><MonitorCommandTimeout>5</MonitorCommandTimeout><StartCommandTimeout>10</StartCommandTimeout><StopCommandTimeout>10</StopCommandTimeout></IBM.RemoteApplicationAttributes>

AttributesNone

Contexts

ChildrenNone


Occurrence0 to 1

MonitorAttributeValue = String. Maximum characters: 1024.

Specifies the Tivoli Monitoring agent attribute group and attribute which is queriedto determine the observed state of the resource. Attribute group and attribute areseparated by a dot, for example “Application_Server.Status”, where


“Application_Server” is the attribute group and “Status” is the attribute name. Thevalue of the specified agent attribute is queried periodically to determine or updatethe observed state of the resource. If the query returns an empty result, theresource assumes Offline as observed state.

The query must not return multiple rows in order to be able to unambiguouslymap an attribute value to an observed state for the resource. If multiple rows arereturned, use a MonitorQueryAttrFilter to limit the query results to exactly onerow.

Example<IBM.ITMResourceAttributes name="IBM.ITMWebServerAgentAttributes" ><Description>ITCAM web server agent monitoring an Apache server</Description><StartCommand>HT:startServer</StartCommand><StopCommand>HT:stopServer</StopCommand><MonitorAttribute>Apache_Web_Server.Status</MonitorAttribute><MonitorValueOnline>Running</MonitorValueOnline><MonitorValueOffline>Stopped</MonitorValueOffline><MonitorValueFailedOffline>Error</MonitorValueFailedOffline><UserName>sysadmin</UserName><StartCommandTimeout>60</StartCommandTimeout><StopCommandTimeout>60</StopCommandTimeout><MonitorCommandPeriod>10</MonitorCommandPeriod><Property>Version</Property><Property>Web_Server_Name</Property><Property>Start_Date_and_Time</Property><Property>Process_ID</Property><Property>Configuration_File</Property>


AttributesNone

Contexts

ChildrenNone

ParentsIBM.ITMResourceAttributes

OccurrenceOnce

MonitorCommandThe value contains the exact command and arguments that will be executedperiodically to determine or update the observed state of the resource. The exitvalue from the command is used as the new observed state of the resourcedepending on the MonitorCommandReturnCodes. Value = String.

The first string specified as command must be a full qualified path name to anexecutable file. The specified user id <UserName> must have the authority to runthis command

Maximum characters: 1024

Example<IBM.RemoteApplicationAttributes name="WebServer-Attributes"><Owner>John Smith</Owner><InfoLink>http://www.ibm.com</InfoLink><Description>Sample web server resource</Description><StartCommand>/bin/touch /tmp/web1</StartCommand><StopCommand>/bin/rm /tmp/web1</StopCommand><MonitorCommand>/bin/ls -la /tmp/web1</MonitorCommand><UserName>root</UserName><MonitorCommandPeriod>10</MonitorCommandPeriod>


<MonitorCommandTimeout>5</MonitorCommandTimeout><StartCommandTimeout>10</StartCommandTimeout><StopCommandTimeout>10</StopCommandTimeout></IBM.RemoteApplicationAttributes>

AttributesNone

Contexts

ChildrenNone


OccurrenceOnce

MonitorCommandPeriodThe value specifies the amount of time (number of seconds) to wait betweeninvocations of the MonitorCommand. This period is started after the prior invocationcompletes. Positive Integer value in seconds with a default of 10.


AttributesNone

Contexts

ChildrenNone


Occurrence0 to 1

MonitorCommandReturnCodesSpecifies how the monitor command return code will be interpreted.v UNIX = 0 (default)v SAMP = 1

Use the SAMP command return code style for new scripts.

Example<IBM.RemoteApplicationAttributes name="WebServer-Attributes"><Owner>John Smith</Owner><InfoLink>http://www.ibm.com</InfoLink><Description>Sample web server resource</Description><StartCommand>/bin/touch /tmp/web1</StartCommand><StopCommand>/bin/rm /tmp/web1</StopCommand><MonitorCommand>/bin/ls -la /tmp/web1</MonitorCommand>


<UserName>root</UserName><MonitorCommandReturnCodes>1</MonitorCommandReturnCodes>

<MonitorCommandPeriod>10</MonitorCommandPeriod><MonitorCommandTimeout>5</MonitorCommandTimeout><StartCommandTimeout>10</StartCommandTimeout><StopCommandTimeout>10</StopCommandTimeout></IBM.RemoteApplicationAttributes>

AttributesNone

Contexts

ChildrenNone


Occurrence0 to 1

MonitorCommandTimeoutProvides the amount of time a monitor command is allowed to run before it iskilled via remote session close. If the command times out, the observed state of theresource is set to Unknown, the operational state is set to LostCommunication andthe compound state to Warning. Positive Integer value in seconds with a default of10.


AttributesNone

Contexts

ChildrenNone


Occurrence0 to 1

MonitorQueryAttrFilterValue = String. Maximum characters: 1024.

When querying the MonitorAttribute, this filter is applied to reduce the amount ofreturned data based on the specified filter criteria. In the filter you can specifywhich attribute must meet which filter criteria. The result is that only the matching


rows of the attribute group that contains the attribute is returned. The value for theMonitorQueryAttrFilter element has the form

attribute_name;operator;value

where attribute_name is the name of the attribute on which the filter is applied. Itmust exist in the attribute group specified in the MonitorAttribute.

operator may be: EQ, NE, GE, GT, LE, LT or LIKE.

EQ “equals”

NE “not equal”

GE “greater than or equal to”

GT “greater than”

LE “less than or equal to”

LT “less than”

LIKE can be used if pattern matching is required.

Available pattern characters when using LIKE are:

'%' matches any single character.

' * ' matches one to many characters.

LIKE is supported only for character attributes.

value is the value on which the operator is applied.

The MonitorQueryAttrFilter element can be specified multiple times if you wantto specify multiple filter criteria. Multiple filters are applied using a logical ANDoperation.

Filter criteria are optional. However, it must be ensured that the query of themonitor attribute does not return more than one row.

AttributesNone

Contexts

ChildrenNone


Occurrence0 to multiple times.

MonitorValueFailedOfflineValue = String. Maximum characters: 256.


Specifies one of the values that the agent attribute used as MonitorAttribute canassume. This value maps to the System Automation operations console observedstate Offline , operational state NonRecoverableError and compound state Fatal. TheMonitorValueFailedOffline element can be specified multiple times if more thanone agent attribute value should be mapped to those error states. In most cases,you are not required to define a specific mapping for FailedOffline and this elementcan be omitted because the agentless adapter determines a failed stateautomatically based on error situations.

Example<IBM.ITMResourceAttributes name="IBM.ITMWebServerAgentAttributes"><Description>ITCAM Web Server Agent monitoring an Apache Server</Description><StartCommand>HT:startServer</StartCommand><StopCommand>HT:stopServer</StopCommand><MonitorAttribute>Apache_Web_Server.Status</MonitorAttribute><MonitorValueOnline>Running</MonitorValueOnline><MonitorValueOffline>Stopped</MonitorValueOffline><MonitorValueFailedOffline>Error</MonitorValueFailedOffline><UserName>sysadmin</UserName><StartCommandTimeout>60</StartCommandTimeout><StopCommandTimeout>60</StopCommandTimeout><MonitorCommandPeriod>10</MonitorCommandPeriod><Property>Version</Property><Property>Web_Server_Name</Property><Property>Start_Date_and_Time</Property><Property>Process_ID</Property><Property>Configuration_File</Property></IBM.ITMResourceAttributes>

AttributesNone

Contexts

ChildrenNone



MonitorValueOfflineValue = String. Maximum characters: 256.

Specifies one of the values that the agent attribute used as MonitorAttribute canassume. This value maps to the System Automation operations console observedstate Offline. The MonitorValueOffline element can be specified multiple times ifmore than one agent attribute value must be mapped to the observed state Offline.If MonitorValueOffline is not specified, you must specify a<MonitorValueAttrFilter element and the resource state will be mapped to Offlineif the attribute query using the specified filter returns an empty result set.

Example<IBM.ITMResourceAttributes name="IBM.ITMWebServerAgentAttributes" ><Description>ITCAM Web Server Agent monitoring an Apache Server</Description><StartCommand>HT:startServer</StartCommand><StopCommand>HT:stopServer</StopCommand><MonitorAttribute>Apache_Web_Server.Status</MonitorAttribute><MonitorValueOnline>Running</MonitorValueOnline><MonitorValueOffline>Stopped</MonitorValueOffline><MonitorValueFailedOffline>Error</MonitorValueFailedOffline><UserName>sysadmin</UserName><StartCommandTimeout>60</StartCommandTimeout>


<StopCommandTimeout>60</StopCommandTimeout><MonitorCommandPeriod>10</MonitorCommandPeriod><Property>Version</Property><Property>Web_Server_Name</Property><Property>Start_Date_and_Time</Property><Property>Process_ID</Property><Property>Configuration_File</Property>


AttributesNone

Contexts

ChildrenNone



MonitorValueOnlineValue = String. Maximum characters: 256.

Specifies one of the values that the agent attribute used as MonitorAttribute canassume. This value maps to the System Automation operations console observedstate Online. The MonitorValueOnline element can be specified multiple times ifmore than one agent attribute value must be mapped to the observed state Online.

Example<IBM.ITMResourceAttributes name="IBM.ITMWebServerAgentAttributes" ><Description>ITCAM Web Server Agent monitoring an Apache Server</Description><StartCommand>HT:startServer</StartCommand><StopCommand>HT:stopServer</StopCommand><MonitorAttribute>Apache_Web_Server.Status</MonitorAttribute><MonitorValueOnline>Running</MonitorValueOnline><MonitorValueOffline>Stopped</MonitorValueOffline><MonitorValueFailedOffline>Error</MonitorValueFailedOffline><UserName>sysadmin</UserName><StartCommandTimeout>60</StartCommandTimeout><StopCommandTimeout>60</StopCommandTimeout><MonitorCommandPeriod>10</MonitorCommandPeriod><Property>Version</Property><Property>Web_Server_Name</Property><Property>Start_Date_and_Time</Property><Property>Process_ID</Property><Property>Configuration_File</Property>


AttributesNone

Contexts

ChildrenNone



MonitorValueStartingValue = String. Maximum characters: 256.


Specifies one of the values that the agent attribute used as MonitorAttribute canassume. This value maps to the System Automation operations console observedstate Starting, operational state InProgress and compound state Warning. TheMonitorValueStarting element can be specified multiple times if more than oneagent attribute value must be mapped to the observed state Starting. In most casesyou are not required to define a specific mapping for the Starting state and thiselement can be omitted because the agentless adapter automatically sets a resourcein a Starting state while the start is being processed.

AttributesNone

Contexts

ChildrenNone



MonitorValueStoppingValue = String. Maximum characters: 256.

Specifies one of the values that the agent attribute used as MonitorAttribute canassume. This value maps to the System Automation operations console observedstate Stopping, operational state InProgress and compound state Warning. TheMonitorValueStopping element can be specified multiple times if more than oneagent attribute value must be mapped to the observed state Stopping. In most casesyou are not required to define a specific mapping for the Stopping state and thiselement can be omitted because the agentless adapter automatically sets a resourcein a Stopping state while the stop is being processed.

AttributesNone

Contexts

ChildrenNone



MonitorValueUnknownValue = String. Maximum characters: 256.

Specifies one of the values that the agent attribute used as MonitorAttribute canassume. This value maps to the System Automation observed state Unknown, andcompound state Warning. The MonitorValueUknown element can be specifiedmultiple times if more than one agent attribute value must be mapped to theobserved state Unknown.

AttributesNone

Contexts


ChildrenNone



OwnerThe element Owner is used to provide information about the owner of the parentelement, for example, the name and telephone number of the owner of a remoteresource. Maximum number of characters supported: 1024


AttributesNone

Contexts

ChildrenNone


Occurrence0 to 1

PolicyAuthorThe PolicyAuthor element is used to identify the author of the policy. Maximumnumber of characters supported: 64


<PolicyName>Agentless adapter sample policy</PolicyName><AutomationDomainName>AgentlessDomain</AutomationDomainName><PolicyToken> 1.0</PolicyToken><PolicyAuthor>Michael Atkins</PolicyAuthor><PolicyDescription>Agentless adapter sample policy</PolicyDescription>


AttributesNone

Contexts

ChildrenNone



Occurrence0 to 1

PolicyDescriptionThe PolicyDescription element is available for adding a free text to the XMLdocument. It can be used, for example, to maintain a change history within the file.Maximum number of characters supported: 1024




AttributesNone

Contexts

ChildrenNone


OccurrenceOnce

PolicyInformationThis element is mandatory. The PolicyInformation element uses the sub-elementslisted in the following to provide an identification of the policy.




AttributesNone

Contexts

ChildrenPolicyName, AutomationDomainName, PolicyToken,PolicyDescription, PolicyAuthor

ParentsNone

Occurrence0 to 1

PolicyNameThe PolicyName element is used to specify a meaningful name for the specificpolicy. Maximum number of characters supported: 64


<PolicyName>Agentless adapter sample policy</PolicyName><AutomationDomainName>AgentlessDomain</AutomationDomainName>


<PolicyToken> 1.0</PolicyToken><PolicyAuthor>Michael Atkins</PolicyAuthor><PolicyDescription>Agentless adapter sample policy</PolicyDescription>


AttributesNone

Contexts

ChildrenNone


OccurrenceOnce

PolicyTokenThe PolicyToken element specifies the version of the policy. It should be updatedwhenever the policy is changed. Maximum number of characters supported: 64




AttributesNone

Contexts

ChildrenNone


OccurrenceOnce

PropertyValue = String. Maximum characters: 1024.

Specifies an Tivoli Monitoring agent attribute which must be part of the attributegroup specified in the MonitorAttribute element. The value of an attributespecified in a Property element is added to the additional properties of a resourcethat are displayed in the System Automation operations console. The attributevalue is queried periodically with every monitor call. Avoid specifying attributeswith frequently changing values, for example CPU utilization, because a resourcemodified event is triggered every time the attribute value changes. The Propertyelement can be specified multiple times if more than one agent attribute value isadded to the additional properties of a resource.

ExampleIBM.ITMResourceAttributes name="IBM.ITMWebServerAgentAttributes" ><Description>ITCAM Web Server Agent monitoring an Apache Server</Description><StartCommand>HT:startServer</StartCommand><StopCommand>HT:stopServer</StopCommand><MonitorAttribute>Apache_Web_Server.Status</MonitorAttribute><MonitorValueOnline>Running</MonitorValueOnline><MonitorValueOffline>Stopped</MonitorValueOffline>


<MonitorValueFailedOffline>Error</MonitorValueFailedOffline><UserName>sysadmin</UserName><StartCommandTimeout>60</StartCommandTimeout><StopCommandTimeout>60</StopCommandTimeout><MonitorCommandPeriod>10</MonitorCommandPeriod><Property>Version</Property><Property>Web_Server_Name</Property><Property>Start_Date_and_Time</Property><Property>Process_ID</Property><Property>Configuration_File</Property>


AttributesNone

Contexts

ChildrenNone

ParentsIBMITMResourceAttributes


RemotePortSpecifies the network port used for the target system access. Positive Integer value.Default is 22 for SSH and 445 for WIN.

Example<IBM.RemoteApplicationAttributes name="WebServer-Attributes"><Owner>John Smith</Owner><InfoLink>http://www.ibm.com</InfoLink><Description>Sample web server resource</Description><StartCommand>/bin/touch /tmp/web1</StartCommand><StopCommand>/bin/rm /tmp/web1</StopCommand><MonitorCommand>/bin/ls -la /tmp/web1</MonitorCommand><UserName>root</UserName><RemotePort>22</RemotePort><RemoteProtocol>SSH</RemoteProtocol>


AttributesNone

Contexts

ChildrenNone


Occurrence0 to 1

RemoteProtocolSpecifies the network protocol used for the target system access. Possible values forconnections are:v SSH for connections to the UNIX sshd (default)v WIN for SMB connections to the Windows OS


Value = String.

Example<IBM.RemoteApplicationAttributes name="WebServer-Attributes"><Owner>John Smith</Owner><InfoLink>http://www.ibm.com</InfoLink><Description>Sample web server resource</Description><StartCommand>/bin/touch /tmp/web1</StartCommand><StopCommand>/bin/rm /tmp/web1</StopCommand><MonitorCommand>/bin/ls -la /tmp/web1</MonitorCommand><UserName>root</UserName><RemotePort>22</RemotePort><RemoteProtocol>SSH</RemoteProtocol>


AttributesNone

Contexts

ChildrenNone


Occurrence0 to 1

ResourceIt describes two types of resources:v Resources running on a remote system that are managed by the Agentless

Adapter via a remote access protocol like SSH (remote resources).v Resources which represent Tivoli Monitoring resources (ITM resources).

The type of resource is determined by the class attribute. The node attribute is alsodifferent depending on the type of resource. For remote resources, the nodeattribute value is the name of the host where the remote application runs. For ITMResources, the node attribute value is the ITM managed system name. Themanaged system name identifies an ITM agent on a specific remote endpoint thatis used to monitor and control the application that is represented by this resource.

Examples

Remote Resource:<Resource name="WebServer" class="IBM.RemoteApplication" node="localhost"><ClassAttributeReference><IBM.RemoteApplicationAttributes name="WebServer-Attributes"/></ClassAttributeReference></Resource>

ITM Resource:<Resource name="Apache Web Server" class="IBM.ITMResource"

node="Apache:saxb32e:KHTP"><ClassAttributesReference><IBM.ITMResourceAttributes name="IBM.ITMWebServerAgentAttributes"/></ClassAttributesReference></Resource>

Attributes


name Mandatory, user defined. Maximum characters: 64

node Mandatory. For resources of class IBM.RemoteApplication this is thenode on which the resource runs. For resources of classIBM.ITMResource it is the managed system name as returned byITM. It has a maximum of 256 characters.

Note:

For Remote Resources:1. If an IPv6 host name is specified as node name, the DNS server

must be configured to return IPv6 records only.2. If the DNS server is configured to return IPv4 and IPv6 records,

only the IPv4 address is used. In case you want to use IPv6,explicitly specify the IPv6 address as node name instead of thehost name.

Use the command host -a <ipv6_hostname> to check the DNSlookup records.

For ITM Resources:

A valid managed system name consists of two or three namecomponents (tokens) which are separated by colons. You can findout the managed system name using the Tivoli Enterprise Portal.Within a managed system name, the name of the host where theITM managed resource is located is the last but one namecomponent. It is always followed by a token that represents theproduct code of the ITM agent. If, for example, the host name is“saxb32e”, valid examples for managed system names are:v apache:saxb32e:KHTPv saxb32e:LZ

Only the host name token of the managed system name will bedisplayed as node value for an ITM resource in the operationsconsole. Also when building the unique resource key consisting ofname and node (required for defining end-to-end resourcereferences referring to an ITM resource), only the host name tokenis used in case of an ITM resource.

class Mandatory. Possible values are IBM.RemoteApplication andIBM.ITMResource.

Contexts

ChildrenClassAttributesReference



StartCommandValue = String. Maximum characters: 1024.

When being used in IBM.RemoteApplicationAttributes: The value contains theexact command and arguments that are run when the resource receives a startrequest for the corresponding resource instance. The command is run under the


user ID specified with the UserName attribute. The command runs with theauthority and environment of the specified user. It is run on the node specified onthe node attribute of the resource tag.

The command must be a fully qualified path name to an executable file. Thespecified user ID <UserName> must have the authority to run this command.

When being used in IBM.ITMResourceAttributes: The value contains the exactcommand and arguments that are run by the Tivoli Monitoring agent when theresource receives a start request for the corresponding resource instance. Thecommand can either be a predefined "take action" command supported by theTivoli Monitoring agent or any remote system command. To use a predefined "takeaction" command of a specific Tivoli Monitoring agent, simply specify the name ofthe command and its parameters. You are not required to specify a fully qualifiedfile path. To trigger a different command on the system, the fully qualified path tothat command must be specified. The command is run on the managed systemwhich is specified in the node attribute of the resource element.

The specified user ID <UserName> must have the authority to execute SOAPrequests against the Tivoli Enterprise Monitoring Server for the resource.

Examples

Remote Resource:<IBM.RemoteApplicationAttributes name="WebServer-Attributes"><Owner>John Smith</Owner><InfoLink>http://www.ibm.com</InfoLink><Description>Sample web server resource</Description><StartCommand>/bin/touch /tmp/web1</StartCommand><StopCommand>/bin/rm /tmp/web1</StopCommand><MonitorCommand>/bin/ls -la /tmp/web1</MonitorCommand><UserName>root</UserName><MonitorCommandPeriod>10</MonitorCommandPeriod><MonitorCommandTimeout>5</MonitorCommandTimeout><StartCommandTimeout>10</StartCommandTimeout><StopCommandTimeout>10</StopCommandTimeout></IBM.RemoteApplicationAttributes>

ITM Resource:<IBM.ITMResourceAttributes name="IBM.ITMWebServerAgentAttributes" >

<Description>ITCAM Web Server Agent monitoring an ApacheServer</Description><StartCommand>HT:startServer</StartCommand><StopCommand>HT:stopServer</StopCommand><MonitorAttribute>Apache_Web_Server.Status</MonitorAttribute><MonitorValueOnline>Running</MonitorValueOnline><MonitorValueOffline>Stopped</MonitorValueOffline><MonitorValueFailedOffline>Error</MonitorValueFailedOffline><UserName>sysadmin</UserName><StartCommandTimeout>60</StartCommandTimeout><StopCommandTimeout>60</StopCommandTimeout><MonitorCommandPeriod>10</MonitorCommandPeriod><Property>Version</Property><Property>Web_Server_Name</Property><Property>Start_Date_and_Time</Property><Property>Process_ID</Property><Property>Configuration_File</Property>


AttributesNone

Contexts


ChildrenNone

ParentsIBM.RemoteApplicationAttributes, IBM.ITMResourceAttributes

OccurrenceOnce

StartCommandTimeoutOnly positive integer values are allowed. The default is 10 and the timeout ismeasured in seconds.

When used in IBM.RemoteApplicationAttributes: Specifies the amount of time astart command is allowed to run. If the command times out, the observed state ofthe resources is set to Offline, the operational state to NonRecoverableError and thecompound state to Fatal.

When used in IBM.ITMResourceAttributes: Specifies the amount of time theagentless adapter allows the resource to move into an Online observed state basedon the value of the MonitorAttribute. During processing of the start command, theresource shows an observed state of Starting until the MonitorAttribute reports anOnline state.

If MonitorAttribute retrieves an Offline state during this StartCommandTimeOutperiod, it is ignored until the StartCommandTimeOut expires.

If the StartCommandTimeOut expires before the MonitorAttribute reports an Onlinestate for the application, the observed state of the resource is set according to whatis reported by the MonitorAttribute.

Example<IBM.RemoteApplicationAttributes name="WebServer-Attributes">

<Owner>John Smith</Owner><InfoLink>http://www.ibm.com</InfoLink><Description>Sample web server resource</Description><StartCommand>/bin/touch /tmp/web1</StartCommand><StopCommand>/bin/rm /tmp/web1</StopCommand><MonitorCommand>/bin/ls -la /tmp/web1</MonitorCommand><UserName>root</UserName><MonitorCommandPeriod>10</MonitorCommandPeriod><MonitorCommandTimeout>5</MonitorCommandTimeout><StartCommandTimeout>10</StartCommandTimeout><StopCommandTimeout>10</StopCommandTimeout>

</IBM.RemoteApplicationAttributes>

AttributesNone

Contexts

ChildrenNone


Occurrence0 to 1

StopCommandValue = String. Maximum characters: 1024.


When used in IBM.RemoteApplicationAttributes: The value contains the exactcommand and arguments that is run when the resource receives a stop request forthe resource instance. All aspects related to running the command are the same asfor StartCommand.

When used in IBM.ITMResourceAttributes: The value contains the exactcommand and arguments that is run by the Tivoli Monitoring agent when theresource receives a stop request for the corresponding resource instance. All aspectsrelated to running the command are the same as for StartCommand.

Examples

Remote Resource:<IBM.RemoteApplicationAttributes name="WebServer-Attributes">



ITM Resource:<IBM.ITMResourceAttributes name="IBM.ITMWebServerAgentAttributes" ><Description>ITCAM Web Server Agent monitoring an Apache Server</Description><StartCommand>HT:startServer</StartCommand><StopCommand>HT:stopServer</StopCommand><MonitorAttribute>Apache_Web_Server.Status</MonitorAttribute><MonitorValueOnline>Running</MonitorValueOnline><MonitorValueOffline>Stopped</MonitorValueOffline><MonitorValueFailedOffline>Error</MonitorValueFailedOffline><UserName>sysadmin</UserName><StartCommandTimeout>60</StartCommandTimeout><StopCommandTimeout>60</StopCommandTimeout><MonitorCommandPeriod>10</MonitorCommandPeriod><Property>Version</Property><Property>Web_Server_Name</Property><Property>Start_Date_and_Time</Property><Property>Process_ID</Property><Property>Configuration_File</Property>


AttributesNone

Contexts

ChildrenNone


OccurrenceOnce

StopCommandTimeoutOnly positive integer values are allowed. The default is 10 and the timeout ismeasured in seconds.


When used in IBM.RemoteApplicationAttributes: Specifies the amount of time astop command is allowed to run. If the command times out, the observed state ofthe resources is set to Online, the operational state to NonRecoverableError and thecompound state toFatal.

When being used in IBM.ITMResourceAttributes: Specifies the amount of timethe Agentless Adapter allows the resource to move into an Offline observed statebased on the value of the MonitorAttribute. During processing of the stopcommand the resource shows an observed state Stopping until theMonitorAttribute reports an Offline state.

If MonitorAttribute retrieves an Online state during this StopCommandTimeOutperiod, it is ignored until the StopCommandTimeOut expires.

If the StopCommandTimeOut expires before the MonitorAttribute reports an Offlinestate for the resource, the observed state of the resource is set according to what isreported by the MonitorAttribute.

Example<IBM.RemoteApplicationAttributes name="WebServer-Attributes">



AttributesNone

Contexts

ChildrenNone


Occurrence0 to 1

UserNameThe value defines a user name under which the MonitorCommand, StartCommandand StopCommand are executed. The commands run with the authority andenvironment of the specified user. A check will be made on each node to ensurethat the user name exists whenever the policy is activated. Value = String.Maximum characters: 1024

Example<IBM.RemoteApplicationAttributes name="WebServer-Attributes"><Owner>John Smith</Owner><InfoLink>http://www.ibm.com</InfoLink><Description>Sample web server resource</Description><StartCommand>/bin/touch /tmp/web1</StartCommand><StopCommand>/bin/rm /tmp/web1</StopCommand><MonitorCommand>/bin/ls -la /tmp/web1</MonitorCommand><UserName>root</UserName>



AttributesNone

Contexts

ChildrenNone


OccurrenceOnce

Disaster recovery policy reference

Disaster recovery policy XML referenceA disaster recovery policy consist of two files: an end-to-end automation policydescribing the resources being managed, and a drml file describing the disasterrecovery setup.

The end-to-end automation policy is described in “End-to-end automation policyXML reference” on page 102. “drml file XML reference” on page 152 describes theXML elements and XML attributes of the disaster recovery policy drml file.

This topic describes the XML element and XML attributes in the end-to-endautomation policy that are specific to disaster recovery.

The XML element DRPolicy is used in the PolicyInformation to include the disasterrecovery policy. It specifies the name of the file in the policy pool directory thatcontains the disaster recovery policy. The existence of the XML element DRPolicymarks an end-to-end automation policy to be part of a disaster recovery policy.Therefore, all the rules that are listed in “Disaster recovery policy rule reference”on page 161 are enabled in addition to the automation policy rules that are listedin “Automation policy rule reference” on page 124.

The XML attribute businessCritical is used in the XML elementsResourceReference, ResourceGroup and ChoiceGroup to mark a resource asbusiness-critical. Only business-critical workload is recovered in case of a disaster.A true business-critical property is propagated from a ResourceGroup and aChoiceGroup to its members. Business-critical application fault events are onlyissued for resources that have the businessCritical attribute explicitly set to true.The rules for specifying business-critical and discretionary workload are listed in“Rules for business-critical and discretionary workload” on page 161.

The XML attribute switchableByDROnly is used in the XML element ChoiceGroupto specify a disaster recovery choice group. This attribute is only applicable tonon-stretched clusters. Disaster recovery choice groups are used to organizeredundant business-critical resource references within cluster sets of non-stretchedclusters. The rules for specifying disaster recovery choice groups are listed in“Rules for disaster recovery choice groups” on page 162.


drml file XML referenceA disaster recovery policy consist of two files: an end-to-end automation policydescribing the resources being managed, and a drml file describing the disasterrecovery setup.

The drml file is the part of the disaster recovery policy that specifies the disasterrecovery setup. The abbreviation drml stands for disaster recovery markuplanguage. The drml file is an XML file. The drml file name is referenced in theDRPolicy element of the end-to-end automation policy.

This topic lists the XML elements, sub-elements, and attributes of the drml file inalphabetical order. For each element, the following information is provided:


RestrictionsPossible restrictions that apply.



ContextsA list of elements that can directly contain the element (its "Parents") and alist of elements the element can contain (its "Children").

Box:The Box element specifies a box as an aggregation of slots hosting hardwaredevices that can be controlled by the hardware adapter.

A box can be a Blade Center, Standalone Computer System, etc. It stores commonconfiguration information for hardware access, such as the SNMP agentinformation.

Restrictions

The name of a Box must be unique within a DRPolicy specification.

Examples<Box name="P-Blade Area 51">

<SNMPAgent host="9.152.21.164"port="161"authProtocol="MD5"privProtocol="None"serviceProcessorType="MM"/>

<Slot name="Blade 6" bay="6"><HardwareManagementTask operation="PowerOff" mechanism="SNMP"/><HardwareManagementTask operation="PowerOn" mechanism="SNMP"/>

</Slot>...

</Box>

Within a HardwareDevice specification:<HardwareDevice>

<Box>P-Blade Room 56</Box><Slot>Blade 1</Slot>

</HardwareDevice>


Attributes

name="BoxName"The name of the Box used to associate hardware devices with boxes. Thisattribute can be used only in the context of Box specifications, it is notallowed if the Box is a subelement of HardwareDevice.

Context

Children: “Slot” on page 159, “SNMPAgent” on page 160

Parents: “DRPolicy” on page 155, “HardwareDevice” on page 155

Class:The Class element specifies the class name of a Node. This name is determined bythe system automation product of the first-level automation domain that the nodeis defined in.

Table 23 provides the class names for supported system automation products. Useit to determine the value of the Class subelement.

Table 23. Classes of nodes in the various system automation products

System automation product name Class name of nodes

IBM SA z/OS SYS (only if the node is not directlymanaged by GDPS)

IBM PowerHA IBM.HacmpNode

System Automation for Multiplatforms IBM.PeerNode

VCS VCS.System

FOC MSCS.Node

Restrictions

Class is a mandatory subelement of Node.

Examples<Node name="node">

<Site index="1"/><Domain name="ApplCluster F"/><Class>IBM.PeerNode</Class><HardwareDevice><Box>P-Blade Room 56</Box><Slot>Blade 1</Slot>

</HardwareDevice></Node>

Attributes

None.

Context

Children: None.

Parents: “Node” on page 157.


Domain:Specifies a first-level automation domain that is part of a disaster recovery setup.The Domain element is used as a subelement of DRPolicy to specify a first-levelautomation domain and as a subelement of Node to specify the domain that thenode is defined in.

Note: Specified domains are only displayed in the operations console if theyactually exist.

Restrictions

None.

Examples

As a Domain specification:<Domain name="WASCluster F"

clusterSetName="GlobalWASCluster"/>

As a reference within a Node specification:<Node name="node">



Attributes

clusterSetName="ClusterSetName"The name of the cluster set that is associated with this first-levelautomation domain. A cluster set has to be associated with exactly onedomain on each of the two sites. This attribute is not allowed if theDomain is a subelement of Node. Allowed characters are: a–z, A–Z, 0–9, '_',and '.'. Maximum number of characters supported: 16.

workloadSetup=”workloadSetup”

This option attribute is only applicable to stretched clusters. It specifies thetype of the workload setup. The following values are allowed:

active-activeThe business-critical workload is running concurrently on bothsites.

active-passiveThe business-critical workload is not running concurrently. Itinitially runs on Site1 and optionally moves to backup site Site2.This is the default value if the attribute workloadSetup is notspecified.

name="DomainName"The name of the first-level automation domain which is used in theAutomationDomain element in the end-to-end automation policy.Maximum number of characters supported: 64.


Context

Children: None.

Parents: “DRPolicy,” “Node” on page 157.

DRPolicy:The DRPolicy element is the top-level element of the disaster recovery policy drmlfile. It serves as a container for all other elements of the drml file.

Restrictions

The element is required and must occur only once in a policy.

Examples<DRPolicy xmlns="http://www.ibm.com/TSA/DRPolicy.xsd"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ibm.com/TSA/DRPolicy.xsd EEZDRPolicy.xsd">

...</DRPolicy>

Attributes

version="VersionNumber"Identifies the minimum version of the System Automation ApplicationManager. The attribute is required. Maximum number of characterssupported: 32.

xmlns="NamespaceURL"Name space declaration for this drml file. The attribute is required andmust be specified as in the example.

xmlns:xsi="SchemaInstanceURL" Identifies the XML schema format for this DML file XML. The attribute isrequired and must be specified as in the example.

xsi:schemaLocation="SchemaURL"Identifies the XML schema that this drml file must conform to. Theattribute is required and must be specified as in the example.

Context

Children: “Site” on page 158, “Domain” on page 154, “Node” on page 157, “Box”on page 152.

Parents: None.

HardwareDevice:The HardwareDevice element specifies the hardware device which is hosting aNode. By specifying Box and Slot, the hardware adapter can determine thehardware management tasks required to control the hardware device.

Restrictions

A HardwareDevice is an optional subelement of Node that can occur at most once.The subelements Box and Slot are mandatory.





Attributes

None.

Context

Children: “Box” on page 152, “Slot” on page 159.

Parents: “Node” on page 157.

HardwareManagementTask:The element HardwareManagementTask specifies a hardware management task asoperation which is performed by the hardware adapter on hardware devices inorder to control them.

Hardware management tasks are defined for Slots. Though there might be multiplehardware management tasks per Slot, the operation of the hardware managementtask must be unique. That is, there must be at most one hardware managementtask with the operation PowerOn, and at most one with the operation PowerOff.

Restrictions

If the attribute mechanism="Script" is specified, the HardwareManagementTaskelement must contain one Script subelement.

Examples<Slot name="Blade 1">

<HardwareManagementTask operation="PowerOff" mechanism="Script"><Script command="./poweroff_Blade_1.sh"

workingDir="/etc/opt/IBM/tsamp/eez/scripts"commandTimeout="10000"runCommandSync="1" />

</HardwareManagementTask></Slot>

Attributes

operation="PowerOff|PowerOn"Identifier of the operation that is performed by the hardware managementtask.

mechanism="Script|SNMP"Identifier of the mechanism which is used to perform the hardwaremanagement task.


Context

Children: “Script.”

Parents: “Slot” on page 159.

Node:The Node element specifies a node that is defined in a first-level automationdomain. It may further specify the hardware device hosting the node in order tocontrol it via the hardware adapter.

Note: Specified nodes are only displayed in the operations console if they actuallyexist.

Restrictions

None.




Attributes

name="NodeName"Name of the node as defined in the first-level automation domain. Thisname may also be used in the Node element in the end-to-end automationpolicy. Maximum number of characters supported: 64.

Context

Children: “Site” on page 158, “Domain” on page 154, “Class” on page 153,“HardwareDevice” on page 155.

Parents: “DRPolicy” on page 155.

Script:The Script element specifies a hardware management task using the scriptmechanism.

Restrictions

A HardwareManagementTask with the attribute mechanism="Script" must containone Script subelement.


Examples<HardwareManagementTask operation="PowerOff" mechanism="Script">

<Script command="./poweroff_Blade_1.sh"workingDir="/etc/opt/IBM/tsamp/eez/scripts"commandTimeout="10000"runCommandSync="1" />

</HardwareManagementTask>

Attributes

command="CommandLine"The command with all its arguments being executed in the workingdirectory.

workingDir="WorkingDirectory"Full-qualified path to the working directory in which the command isbeing executed.

commandTimeout="Millis"Timeout limit for the command in milliseconds. If the command does notterminate before the timeout is reached, it is aborted.

runCommandSync="n"If the value is set to 0 or 2, the command is executed asynchronously. Forall other values, it is executed synchronously. In this case, a timeout limit ismandatory. The hardware adapter then waits for command completionuntil the timeout is reached.

If the attribute is not specified, the hardware adapter executes thecommand asynchronously.

Context

Children: None.

Parents: “HardwareManagementTask” on page 156.

Site:Specifies the site as physical location of a disaster recovery setup. The Site elementis used as subelement of DRPolicy to specify the two sites of a disaster recoverysetup and as subelement of Node to specify the site where the node is located.

Restrictions

DRPolicy must contain exactly two Site sub-elements.

Examples

As a Site specification:<Site index="1" name="Frankfurt"/>

As a reference within a Node specification:<Node name="node">

<Site index="1"/><Domain name="ApplCluster F"/><Class>IBM.PeerNode</Class><HardwareDevice>




Attributes

index="1|2"The site index.

name="Name"The name of the site. This attribute is not allowed if the Site is subelementof Node. Maximum number of characters supported: 64.

Context

Children: None.

Parents: “DRPolicy” on page 155, “Node” on page 157.

Slot:The Slot element is used to specify a Slot in a Box or to reference a Slot within aHardwareDevice specification. A slot is an actual system. It can be an LPAR, Blade,etc.

Restrictions

The name of a Slot must be unique within a Box specification.

Examples

Slot specification within a Box specification:<Box name="P-Blade Room 56">


<Slot name="Blade 6" bay="6"><HardwareManagementTask operation="PowerOff" mechanism="SNMP"/><HardwareManagementTask operation="PowerOn" mechanism="SNMP"/>

</Slot>...<Slot name="Blade 1"><HardwareManagementTask operation="PowerOff" mechanism="Script">

<Script command="./poweroff_Blade_1.sh"workingDir="/etc/opt/IBM/tsamp/eez/scripts"commandTimeout="10000"runCommandSync="1" />

</HardwareManagementTask></Slot>...

</Box>

As a reference within a HardwareDevice specification:<HardwareDevice>


</HardwareDevice>


Attributes

name="SlotName"This attribute contains the name of the Slot. It can be used only in thecontext of Box specifications, that is, if the Slot is a subelement of Box.

bay="BayNumber"This optional attribute of type Integer contains the bay number of the slotwithin a blade. It attribute can be used only in the context of Boxspecifications, that is, if the Slot is a subelement of Box.

Context

Children: “HardwareManagementTask” on page 156.

Parents: “HardwareDevice” on page 155, “Box” on page 152.

SNMPAgent:The SNMPAgent element specifies the SNMP agent which is accessed by thehardware adapter in order to control the hardware devices of a box.

Restrictions

At most one SNMPAgent element may be specified as the subelement of Box.

Examples<Box name="P-Blade Area 51">


...</Box>

Attributes

host="HostIPAddress"The name or IP address of the SNMP agent's host.

port="PortNumber"Number of port on which the SNMP agent is listening. Minimum value is1, maximum value is 65535 (usually 161).

authProtocol="MD5|SHA|None"Identifier of the SNMP agent's authentication protocol.

privProtocol="DES|AES|None"Identifier of the SNMP agent's privacy protocol.

serviceProcessorType="MM"Identifier of the service processor type that is hosting the SNMP agent.

Context

Children: None.

Parents: “Box” on page 152.


Disaster recovery policy rule referenceDisaster recovery policies consist of two files: an end-to-end automation policy anda disaster recovery policy drml file describing the disaster recovery setup. Bothfiles must be located in the policy pool directory.

The following rules are checked together with the rules described in “Automationpolicy rule reference” on page 124.

Rules for sites, domains and cluster sets: An error message is issued if one of thefollowing rules is not observed:v There must be exactly two sites specified in the disaster recovery policy.v The site index of the initially primary site has to be set to 1.v The site index of the initially secondary site has to be set to 2.v Site names are required, must not be empty and must be unique.v GDPS imposes the following syntax rules for cluster sets, domain names, and

resource reference names:– The following characters are allowed: A–Z (mixed case), 0-9, _ (underscore), -

(hyphen).– Names can be a maximum of 16 characters.

v Domains supporting business-critical resources must be associated with a clusterset.

v Domain names are mandatory, must not be empty and must be unique.v The domain names ALL and EEZHardwareAdapter are reserved and therefore not

allowed.v Cluster set names must not be the same as any domain names.v Exactly one domain must be specified per cluster set and site to ensure

well-defined and complete site-coverage.v Every node must be assigned to a domain and to a site where it is located. The

location of domains is determined via their nodes.v Class is a mandatory subelement of Node that is required for controlling and

monitoring the nodes.

Rules for business-critical and discretionary workload: An error message isissued if one of the following rules is not observed:v For convenience in specifying the policy, the business-critical attribute is

propagated from groups into their members.v Application fault- and fault cleared events are issued only for resources that are

explicitly set as business-critical, not for resources whose business-criticalattribute is propagated.

v A resource that is explicitly set discretionary is not allowed as member of abusiness-critical group to avoid propagation conflicts.

v There must be no dependencies of business-critical resources to discretionaryresources: No relationships from business-critical source to discretionary target.

v A business-critical resource is not allowed as member of a discretionary group toavoid critical dependencies.

v GDPS imposes the following syntax rules for resource reference names:– The following characters are allowed: A–Z (mixed case), 0-9, _ (underscore), -

(hyphen).– Names can be a maximum of 16 characters.


Rules for disaster recovery choice groups: Disaster recovery choice groups areused to organize the business-critical resource references within the boundaries ofcluster sets of non-stretched clusters. They must not be used for stretched clusters.Disaster recovery choice groups have the attribute switchableByDROnly="true".The switchableByDROnly attribute is used to distinguish disaster recovery choicegroups from regular choice groups.

An error message is issued if one of the following rules is not observed:v Disaster recovery choice groups have to be set explicitly business-critical or have

to be placed in business-critical groups.v Business-critical does not imply that a choice group is a disaster recovery choice

group. Ordinary choice groups can also be business-critical.v All members of a disaster recovery choice group have to be associated with the

same cluster set via the domains in which the referenced resources are defined.v Exactly one resource reference must be specified as a member of a disaster

recovery choice group per site to ensure well-defined and completesite-coverage.

v There must be no further dependencies of members of disaster recovery choicegroups to other policy constructs: No relationships and no grouping. Instead,use the disaster recovery choice groups itself to model dependencies withbusiness-critical resources.

v Only business-critical resource references are allowed to be members of disasterrecovery choice groups, no discretionary resources and no groups.

v Disaster recovery choice groups are allowed as members in other groups.v The initially preferred member of a disaster recovery choice group has to be

defined in the initially productive domain, that is, the domain which is locatedat site with index '1'.

Disaster recovery policy definition worksheetsPrint out and use these worksheets to collect the information required for creatinga disaster recovery policy.

If you need to define more cluster sets, hardware boxes, slots, or nodes print outmore copies of the appropriate worksheet.

Table 24. Worksheet to define disaster recovery topology

Site 1 Index 1

Name

Site 2 Index 2

Name

Cluster set ClusterSetName

Domain Name Site 1

Domain Name Site 2

WorkloadSetup


Domain Name Site 1

Domain Name Site 2

WorkloadSetup


Table 24. Worksheet to define disaster recovery topology (continued)


Domain Name Site 1

Domain Name Site 2

WorkloadSetup


Domain Name Site 1

Domain Name Site 2


Domain Name Site 1

Domain Name Site 2

WorkloadSetup


Domain Name Site 1

Domain Name Site 2

WorkloadSetup


Domain Name Site 1

Domain Name Site 2

WorkloadSetup


Domain Name Site 1

Domain Name Site 2

WorkloadSetup

Table 25. Worksheet to define disaster recovery hardware. Reuse this table for each site.Name of Site1 /Site2:

Hardware Box Name

Slot 1 Name

PowerOff mechanism Script / SNMP

PowerOn mechanism Script / SNMP

Slot 2 Name



Slot 3 Name



Slot 4 Name



SNMPAgent (Ifmechanism="SNMP")

Host

Port

AuthProtocol MD5 / SHA / None

PrivProtocol DES / AES / None

ServiceProcessorType MM


Table 25. Worksheet to define disaster recovery hardware (continued). Reuse this table foreach site.Name of Site1 /Site2:

Hardware Box Name

Slot 1 Name



Slot 2 Name



Slot 3 Name



Slot 4 Name



SNMPAgent (Ifmechanism="SNMP")

Host

Port

AuthProtocol MD5 / SHA / None

PrivProtocol DES / AES / None

ServiceProcessorType MM

Node Name

Site index 1 / 2

Domain name

Class SYS / IBM.HacmpNode / IBM.PeerNode / VCS.System / MSCS.Node

HardwareDevice Box

Slot

Node Name

Site index 1 / 2

Domain name


HardwareDevice Box

Slot

Node Name

Site index 1 / 2

Domain name


HardwareDevice Box

Slot

Node Name

Site index 1 / 2

Domain name


HardwareDevice Box

Slot

Node Name


Table 25. Worksheet to define disaster recovery hardware (continued). Reuse this table foreach site.Name of Site1 /Site2:

Site index 1 / 2

Domain name


HardwareDevice Box

Slot

Node Name

Site index 1 / 2

Domain name


HardwareDevice Box

Slot

Table 26. Worksheet to define disaster recovery workload

Business-critical workload:

Resource name Cluster set name 1

1

2

3

4

5

6

7

8

Discretionary workload:

Resource name Cluster set name Site index

1

2

3

4

5

6

7

8

1. Business-critical workload must be able to run on either site in a cluster set, so you donot need to collect an associated domain name with this worksheet.

Tivoli Monitoring Resource Templates Reference

The policy editor supports the creation of Tivoli Monitoring resources in anAgentless Adapter policy based on predefined templates for specific TivoliMonitoring agents.v WebSphere Application Server Agent


v Custom Agent built with Agent Builderv Linux OS Agentv DB2 Agentv UNIX OS Agentv Apache Web Server Agent

The templates are dynamically loaded by the policy editor from the following filelocation on the System Automation Application Manager host where they reside aspolicy snippets: <SA Application Manager PolicyPool>/snippets/itm.

The following sections describe the defaults that are used in the predefined policytemplates and the corresponding XML snippets.

DB2 agent resource template

The following table describes the mapping of attributes and values for the TivoliMonitoring DB2 agent.

The values of the following properties need to be adapted to match your specificagent and environment:v Managed System Namev Database instance name and partition used in start and stop commands

Table 27. DB2 agent resource attribute mappings

Property Value Comment

Product Code UD

Product Description IBM Tivoli Composite Application Manager for DB2

Managed System Name db2inst1:NODE:UD Adapt to match yourenvironment

Start Command kudStartDB2 db2inst1 0 Take Action command,where

“db2inst1” is the databaseinstance name and “0” is thepartition

Stop Command kudStopDB2 db2inst1 0 See the Start Commandcomment

Start Timeout 60 Allow 60 seconds to start

Stop Timeout 60 Allow 60 seconds to stop

Monitor Attribute KUDINFO00.db2_status

State Mapping Active → Online,

InActive/Busy, Quiesced →Offline,

Quiesce_Pending → Stopping,

Unknown → Unknown

Monitor Command Period 10 Query value of monitorattribute every 10 seconds


Table 27. DB2 agent resource attribute mappings (continued)

Additional Properties db2start_time,

version,

instance_name,

prdid,

server_db2_type

Corresponding policy XML output:<Resource name="DB2 - db2inst" class="IBM.ITMResource" node="db2inst1:NODE:UD"><ClassAttributesReference>

<IBM.ITMResourceAttributes name="IBM.ITMDB2AgentAttributes"/></ClassAttributesReference>

</Resource>

<IBM.ITMResourceAttributes name="IBM.ITMDB2AgentAttributes" ><Owner></Owner><InfoLink></InfoLink><Description>ITCAM DB2 Agent monitoring a DB2 instance.

Adapt the following to match your environment:- Managed System Name- StartCommand/StopCommand: Verify DB2 instance name and partition

</Description>

<StartCommand>kudStartDB2 db2inst1 0</StartCommand><StopCommand>kudStopDB2 db2inst1 0</StopCommand>

<StartCommandTimeout>60</StartCommandTimeout><StopCommandTimeout>60</StopCommandTimeout>

<MonitorAttribute>KUDINFO00.db2_status</MonitorAttribute><MonitorValueOnline>Active</MonitorValueOnline><MonitorValueOffline>InActive/Busy</MonitorValueOffline><MonitorValueOffline>Quiesced</MonitorValueOffline><MonitorValueStopping>Quiesce_Pending</MonitorValueStopping><MonitorValueUnknown>Unknown</MonitorValueUnknown><MonitorCommandPeriod>10</MonitorCommandPeriod><Property>db2start_time</Property><Property>version</Property><Property>instance_name</Property><Property>prdid</Property><Property>server_db2_type</Property>


WebSphere Application Server agent resource template

The following table describes the mapping of attributes and values for the TivoliMonitoring WebSphere Application Server agent.

The values of the following properties need to be adapted to match your specificagent and environment:v Managed System Namev Start Command and Stop Command: Specify the WebSphere Application Server

admin user ID and password, or configure the WebSphere Application Server tostart and stop without requiring a password

Table 28. Tivoli Monitoring WebSphere Application Server agent resource attributemappings


Product Code YN

Product Description IBM Tivoli Composite Application Manager Agent forWebSphere Applications


Table 28. Tivoli Monitoring WebSphere Application Server agent resource attributemappings (continued)

Managed System Name server1:NODE:KYNS Adapt to match yourenvironment

Start Command StartAppSvr $user $pwd Take Action command. For$user and $pwd specify theWebSphere ApplicationServer admin user id andpassword, or configure theWebSphere ApplicationServer server to start andstop without requiring apassword

Stop Command StopAppSvr $user $pwd Take Action command. For$user and $pwd specify theWebSphere ApplicationServer admin user ID andpassword, or configure theWebSphere ApplicationServer server to start andstop without requiring apassword



Monitor Attribute Application_Server.Status

State Mapping Connected → Online

Disconnected → Offline

Unconfigured → Unknown


Additional Properties Server_Name,

Version,

Start_Date_and_Time,

Process_ID,

Server_Type,

Server_Instance_Name

Corresponding policy XML output:Resource name="WAS server" class="IBM.ITMResource" node="server1:NODE:KYNS">

<ClassAttributesReference><IBM.ITMResourceAttributes name="IBM.ITMWASAgentAttributes"/>

</ClassAttributesReference></Resource>

<IBM.ITMResourceAttributes name="IBM.ITMWASAgentAttributes" ><Owner></Owner><InfoLink></InfoLink><Description>ITCAM WebSphere Agent monitoring a WebSphere

Application Server.Adapt the following to match your environment:- Managed System Name- StartCommand and StopCommand: Specify WAS admin user id and passwordor configure the WAS server to stop without requiring a password


</Description>

<StartCommand>YN:StartAppSvr $user $pwd</StartCommand><StopCommand>YN:StopAppSvr $user $pwd</StopCommand>

<StartCommandTimeout>300</StartCommandTimeout><StopCommandTimeout>300</StopCommandTimeout><MonitorAttribute>Application_Server.Status</MonitorAttribute><MonitorValueOnline>Connected</MonitorValueOnline><MonitorValueOffline>Disconnected</MonitorValueOffline><MonitorValueUnknown>Unconfigured</MonitorValueUnknown><MonitorCommandPeriod>10</MonitorCommandPeriod><Property>Server_Name</Property><Property>Version</Property><Property>Start_Date_and_Time</Property><Property>Process_ID</Property><Property>Server_Type</Property><Property>Server_Instance_Name</Property>


Apache agent resource template

The following table describes the mapping of attributes and values for the TivoliMonitoring Apache Web Server agent.

The values of the following properties need to be adapted to match your specificagent and environment:v Managed System Name

Table 29. Apache agent resource attribute mappings


Product Code HT

Product Description IBM Tivoli Composite Application Manager Agent for HTTPServers

Managed System Name NAME:NODE:KHTP Adapt to match yourenvironment

Start Command HT:startServer Take Action command

Stop Command HT:stopServer Take Action command



Monitor Attribute Apache_Web_Server.Status

State Mapping Running → Online

Stopped → Offline

Error → FailedOffline


Aditional Properties Version,

Web_Server_Name,

Start_Date_and_Time,

Process_ID,

Configuration_File

Corresponding policy XML output:


<Resource name="Apache Web Server" class="IBM.ITMResource" node="NAME:NODE:KHTP"><ClassAttributesReference>

<IBM.ITMResourceAttributes name="IBM.ITMWebServerAgentAttributes"/></ClassAttributesReference>

</Resource>

<IBM.ITMResourceAttributes name="IBM.ITMWebServerAgentAttributes" ><Owner></Owner><InfoLink></InfoLink><Description>ITCAM Web Server Agent monitoring an Apache Server.

Adapt the following to match your environment:- Managed System Name

</Description><StartCommand>HT:startServer</StartCommand><StopCommand>HT:stopServer</StopCommand><StartCommandTimeout>60</StartCommandTimeout><StopCommandTimeout>60</StopCommandTimeout><MonitorAttribute>Apache_Web_Server.Status</MonitorAttribute><MonitorValueOnline>Running</MonitorValueOnline><MonitorValueOffline>Stopped</MonitorValueOffline><MonitorValueFailedOffline>Error</MonitorValueFailedOffline><MonitorCommandPeriod>10</MonitorCommandPeriod><Property>Version</Property><Property>Web_Server_Name</Property><Property>Start_Date_and_Time</Property><Property>Process_ID</Property><Property>Configuration_File</Property>


Tivoli Monitoring custom agent resource template

Custom Agents which are built using the IBM Tivoli Monitoring Agent Builder canbe used to monitor the availability of applications by doing either process/servicemonitoring or by evaluating command return codes of a user-created monitorscript. The availability status which is determined based on one of these methodsis written into well-defined attributes within an “Availability” attribute group.

The values of these attributes can be queried using the SOAP interface likeattributes of other application agents. When querying the availability attributegroup, you have to specify Kxx_AVAILABILITY as a pre-defined name of theattribute group, where xx is the product code of the custom agent. For AgentBuilder built custom agents the product codes 00 - 99 are reserved.

For System Automation monitoring purposes, the important attributes of theKxx_AVAILABILITY attribute group are:

Application_ComponentA unique descriptive name of the application component that is beingmonitored. When querying the availability attribute group in order todetermine the status of an application component, the result set could havemultiple rows with one row for each component / process monitored bythe custom agent. The Application_Component attribute can be used tofind the row that corresponds to the specific resource that must beintegrated in System Automation.

Name The name of the process, service, or functional test. This matches theexecutable name of the process, the service short name, or the name of thecommand used to test the application.

Status The status of the application component.v For processes the pre-defined values are 'UP', 'DOWN', 'WARNING' or

'PROCESS_DATA_NOT_AVAILABLE'. The status for a process is


'PROCESS_DATA_NOT_AVAILABLE' if the process is running, but noresource usage information can be collected for that process.

v For services the pre-defined values are 'UP', 'DOWN' or 'UNKNOWN'.The status for a service is 'UNKNOWN' if the service is not installed.

v For command return codes, the predefined values are 'PASSED' or'FAILED'. See the “Functionality_Test_Status” attribute for commandreturn codes details.

Functionality_Test_StatusThe return code of the functionality test. When the monitored applicationis running correctly, 'SUCCESS' is displayed. 'NOT_RUNNING' isdisplayed when it is not running correctly or 'N/A' when the row does notrepresent a functionality test. Possible values:v N/A (1), SUCCESS (0), GENERAL_ERROR (2), WARNING (3),

NOT_RUNNING (4), DEPENDENT_NOT_RUNNING (5),ALREADY_RUNNING (6), PREREQ_NOT_RUNNING (7), TIMED_OUT(8), DOESNT_EXIST (9), UNKNOWN (10),DEPENDENT_STILL_RUNNING (11), orINSUFFICIENT_USER_AUTHORITY (12)

For the integration in System Automation Application Manager, the “Status” andthe “Functionality_Test_Status” attributes are of particular interest, because theyare used for the specific purpose of monitoring the availability of an applicationcomponent which is exactly what is required by System Automation.

The following mapping is a generic mapping which you can use for custom agentsthat use either process/service monitoring or monitoring based on commandreturn codes.

The values of the following properties need to be adapted to match your specificagent and environment:v Managed System Namev WebSphere Business Monitor Attribute: Replace 00 with your agent's product

codev MonitorQueryAttrFilter: Replace MY_APPNAME with the application name as

specified in the Agent Builderv Start- / Stop command

Table 30. Tivoli Monitoring custom agent resource attribute mappings


Product Code 00 Customers can use 00 - 99

Product Description Custom Agent for K00

Managed System Name NODE:00 Adapt to match yourenvironment

Start Command /home/mypath/start_script.sh Any remote systemcommand / script availableon the target system

Stop Command /home/mypath/stop_script.sh Any remote systemcommand / script availableon the target system




Table 30. Tivoli Monitoring custom agent resource attribute mappings (continued)

Monitor Attribute K00_AVAILABILITY.Status The status of the applicationcomponent. For possiblevalues, refer to thedescription of the “Status”attribute.

You have to change the K00part of the attribute group tomatch the product code ofyour custom agent.

Monitor Query AttributeFilter

Application_Component;EQ;MY_APPNAME

MY_APPNAME is the nameof the application that isbeing monitored. The nameis entered as Display Namein the Agent Builder Dialog.

State Mapping UP → OnlineDOWN → Offline

UP / DOWN used forprocesses and Windowsservices

PROCESS_DATA_NOT_AVAILABLE → Online

PROCESS_DATA_NOT_AVAILABLE

used for a process when thematching process is runningbut the resource usageinformation cannot becollected for that process.

UNKNOWN → Unknown UNKNOWN used forWindows services if theservice is not installed

PASSED → OnlineFAILED → Offline

PASSED / FAILED used forcommand return codes basedmonitoring



Table 30. Tivoli Monitoring custom agent resource attribute mappings (continued)

Additional Properties Application_Component Display Name of themonitored application.

Name The name of the process,service, or functional test.This matches the executablename of the process, theservice short name, or thename of the command usedto test the application

Functionality_Test_Status The return code of thefunctionality test. When themonitored application isrunning correctly 'SUCCESS'is displayed,'NOT_RUNNING' when it isnot running correctly or'N/A' when the app. is notmonitored via commandreturn codes.

Functionality_Test_Message The text message thatcorresponds to theFunctionality Test Status.This is valid only forcommand return codes-basedmonitoring.

Full_Name The full name of the processincluding information that isprocess-dependent.

Type Identifies the type of theapplication component.Components are processes,services, or command returncodes (functionality test)

PID The process id associatedwith the process. Thiscontains only valid data forprocesses.

Command_Line The program name and anyarguments specified on thecommand line when theprocess was started. It hasthe value N/A if it is aService or Functionality test.

Corresponding policy XML output:<Resource name="MyCustomAppl" class="IBM.ITMResource" node="NODE:00">

<ClassAttributesReference><IBM.ITMResourceAttributes name="IBM.ITMCustomAgentAttributes"/>


<IBM.ITMResourceAttributes name="IBM.ITMCustomAgentAttributes" ><Owner></Owner><InfoLink></InfoLink><Description>Custom Agent.

Adapt the following to match your environment:- Managed System Name- Monitor Attribute Group: Replace 00 with your agent’s product code- MonitorQueryAttrFilter: Replace MY_APPNAME with the applicationname as specified in the Agent Builder


- StartCommand and StopCommand</Description><StartCommand>/home/mypath/start_script.sh</StartCommand><StopCommand>/home/mypath/stop_script.sh</StopCommand><StartCommandTimeout>30</StartCommandTimeout><StopCommandTimeout>30</StopCommandTimeout><MonitorAttribute>K00_AVAILABILITY.Status</MonitorAttribute><MonitorQueryAttrFilter>Application_Component;EQ;MY_APPNAME</MonitorQueryAttrFilter><MonitorValueOnline>UP</MonitorValueOnline><MonitorValueOnline>PROCESS_DATA_NOT_AVAILABLE</MonitorValueOnline><MonitorValueOnline>PASSED</MonitorValueOnline><MonitorValueOffline>DOWN</MonitorValueOffline><MonitorValueOffline>FAILED</MonitorValueOffline><MonitorValueUnknown>UNKNOWN</MonitorValueUnknown><MonitorCommandPeriod>10</MonitorCommandPeriod><Property>Application_Component</Property><Property>Name</Property><Property>Functionality_Test_Status</Property><Property>Functionality_Test_Message</Property><Property>Full_Name</Property><Property>Type</Property><Property>PID</Property><Property>Command_Line</Property>


Linux OS agent resource template

The following mapping definition uses the Linux OS Agent to determine whether aspecific process is available based on the process list. This is a simple monitoringscheme and you should, if possible, use a custom agent built using the AgentBuilder, or a specific application agent.

The values of the following properties need to be adapted to match your specificagent and environment:v Managed System Namev Start- / Stop commandv MonitorQueryAttrFilter: Replace MY_PROCESS_NAME with your process

command name

Table 31. Linux OS agent resource attribute mappings


Product Code LZ

Product Description Monitoring Agent for Linux OS

Managed System Name NODE:LZ Adapt to match yourenvironment





Monitor Attribute KLZ_Process.State The state of the process(Sleeping, Disk, Running,Zombie, Trace, Dead, orNot_Available).


Table 31. Linux OS agent resource attribute mappings (continued)


rocess_Command_Name;EQ;MY_PROCESS_NAME

MY_PROCESS_NAME is thename of the processcommand withoutarguments. Valid value is analphanumeric text string,with a maximum length of32 characters.Note: If it is not sufficientto compare the processname, use the following filterto compare the full processcommand line with a filterstring. The filter string cancontain wildcard characters:Proc_CMD_Line;LIKE;<filter_string>

State Mapping Sleeping → Online

Disk → Online

Running → Online

Trace → Online

Zombie → Offline

Dead → Offline

If no row matching theattribute filter is found in theprocess list of the OS agent,an offline state is assumed.


Additional Properties Process_ID The identifier of the process.

Parent_Process_ID The identifier for the parentprocess.

Process_Command_Name The name of the processcommand. Valid value is analphanumeric text string,with a maximum length of32 characters

Proc_CMD_Line The process command-linestring. Valid value is a textstring, with a maximumlength of 768 characters.

Corresponding policy XML output:<Resource name="MyOSAgentAppl" class="IBM.ITMResource" node="NODE:LZ">

<ClassAttributesReference><IBM.ITMResourceAttributes name="IBM.ITMLZOSAgentAttributes"/>


<IBM.ITMResourceAttributes name="IBM.ITMLZOSAgentAttributes" ><Owner></Owner><InfoLink></InfoLink><Description>Application controlled via Linux OS Agent.

Adapt the following to match your environment:- Managed System Name- StartCommand and StopCommand- MonitorQueryAttrFilter: Replace MY_PROCESS_NAME with your processcommand name</Description><StartCommand>/home/mypath/start_script.sh</StartCommand>


<StopCommand>/home/mypath/stop_script.sh</StopCommand><StartCommandTimeout>30</StartCommandTimeout><StopCommandTimeout>30</StopCommandTimeout><MonitorAttribute>KLZ_Process.State</MonitorAttribute><MonitorQueryAttrFilter>Process_Command_Name;EQ;MY_PROCESS_NAME</MonitorQueryAttrFilter><MonitorValueOnline>Sleeping</MonitorValueOnline><MonitorValueOnline>Disk</MonitorValueOnline><MonitorValueOnline>Running</MonitorValueOnline><MonitorValueOnline>Trace</MonitorValueOnline><MonitorValueOffline>Zombie</MonitorValueOffline><MonitorValueOffline>Dead</MonitorValueOffline><MonitorCommandPeriod>10</MonitorCommandPeriod><Property>Process_ID</Property><Property>Parent_Process_ID</Property><Property>Process_Command_Name</Property><Property>Proc_CMD_Line</Property>


UNIX OS agent resource template

The following mapping definition uses the UNIX OS Agent to determine whether aspecific process is available based on the process list. The UNIX OS Agent supportsthe following UNIX flavors: AIX, Solaris, and HP-UX. It is a simple monitoringscheme. You should use, if possible, a custom agent built using the Agent Builder,or a specific application agent.

The values of the following properties need to be adapted to match your specificagent and environment:v Managed System Namev Start- / Stop commandv MonitorQueryAttrFilter: Replace MY_PROCESS_CMD with your process

command

Table 32. UNIX OS agent resource attribute mappings


Product Code UX

Product Description Monitoring Agent for UNIX OS

Managed System Name NODE:KUX Adapt to match yourenvironment





Monitor Attribute Process.Execution_State The state of the process


Table 32. UNIX OS agent resource attribute mappings (continued)


Process_Command;EQ;MY_PROCESS_CMD

MY_PROCESS_CMD is thename of the processcommand includingarguments. Valid value is analphanumeric text string,with a maximum length of100 characters.Note: If you do not needthe command arguments toidentify your process, youcan also use the attributenamed Command, whichcontains only the commandexcluding the arguments.

State Mapping Active → Online

Intermediate → Online

Running → Online

Sleeping → Online

Runnable → Online

Waiting → Online

Growing → Online

Stopped → Offline

Zombie → Offline

Nonexistent → Offline

If no row matching theattribute filter is found in theprocess list of the OS agent,an offline state is assumed.


Additional Properties Process_ID The identifier of the process.

Parent_Process_ID The identifier for the parentprocess.

Process_Command The process commandincluding arguments up to amaximum length of 100characters.

StartTime Time when the process wasstarted in the formatCYYMMDDHHMMSSmmm

User_Name Name of the user name whoowns the process

Type The type of UNIX operatingsystem residing on themonitored host

Corresponding policy XML output:<Resource name="MyUNIXOSAgentAppl" class="IBM.ITMResource" node="NODE:KUX">

<ClassAttributesReference><IBM.ITMResourceAttributes name="IBM.ITMUXOSAgentAttributes"/>



<IBM.ITMResourceAttributes name="IBM.ITMUXOSAgentAttributes" ><Owner></Owner><InfoLink></InfoLink><Description>Application controlled via UNIX OS Agent.

Adapt the following to match your environment:- Managed System Name- StartCommand and StopCommand- MonitorQueryAttrFilter: Replace MY_PROCESS_CMD with your process command

</Description><StartCommand>/home/mypath/start_script.sh</StartCommand><StopCommand>/home/mypath/stop_script.sh</StopCommand><UserName>sysadmin</UserName><StartCommandTimeout>30</StartCommandTimeout><StopCommandTimeout>30</StopCommandTimeout><MonitorAttribute>Process.Execution_State</MonitorAttribute><MonitorQueryAttrFilter>Process_Command;EQ;MY_PROCESS_CMD</MonitorQueryAttrFilter>

<MonitorValueOnline>Active</MonitorValueOnline><MonitorValueOnline>Intermediate</MonitorValueOnline><MonitorValueOnline>Running</MonitorValueOnline><MonitorValueOnline>Runnable</MonitorValueOnline><MonitorValueOnline>Sleeping</MonitorValueOnline><MonitorValueOnline>Waiting</MonitorValueOnline><MonitorValueOnline>Growing</MonitorValueOnline><MonitorValueOffline>Stopped</MonitorValueOffline><MonitorValueOffline>Nonexistent</MonitorValueOffline><MonitorValueOffline>Zombie</MonitorValueOffline><MonitorCommandPeriod>10</MonitorCommandPeriod><Property>Process_ID</Property><Property>Parent_Process_ID</Property><Property>Process_Command</Property><Property>User_Name</Property><Property>StartTime</Property><Property>Type</Property>


User rolesAssign access roles that determine which System Automation Application Managertasks are available to a user in the Dashboard Application Services Hub.

Access roles are created during the installation of System Automation ApplicationManager and assigned to the user groups listed in the right column of the table. Toassign access roles to individual users, add the users' IDs to the corresponding usergroups.

Table 33. Access roles for System Automation Application Manager

Role Permissions Group name

EEZMonitor Grants minimum access rights. Userswho have the EEZMonitor role can runquery-type operations. This rolecannot activate and deactivateautomation policies or run actionsthat modify the state of resources, forexample, they cannot submit startrequests.

The following dashboards areavailable to EEZMonitor users:

v Welcome Page

v Domain and Automation Health

v Explore Automation Nodes

v Operate End-to-End Resources

v Explore Automation Domains

EEZMonitorGroup


Table 33. Access roles for System Automation Application Manager (continued)


EEZOperator In addition to the permissions grantedby the EEZMonitor role, users whohave this role can send requestsagainst resources. With this role, userscannot run tasks that change theconfiguration, such as activating anddeactivating policies.

The following dashboards areavailable to EEZOperator users:

v Welcome Page





To manage both first-level andend-to-end automation resources,EEZOperator users must also have theEEZEndToEndAccess role.

EEZOperatorGroup

EEZConfigurator In addition to the permissions grantedby the EEZMonitor role, users whohave this role can run tasks thatchange the configuration, such asactivating and deactivating policies.

Users who have only this role cannotsubmit requests against resources. Therole is required to be able to workwith policies.

The following dashboards areavailable to EEZConfigurator users:

v Welcome Page





To be able to work with end-to-endautomation policies, EEZConfiguratorusers must also have theEEZEndToEndAccess role.

EEZConfiguratorGroup


Table 33. Access roles for System Automation Application Manager (continued)


EEZAdministrator Extends the EEZOperator andEEZConfigurator roles, grantingmaximum access rights.

Users who have this role can run alloperations available on the operationsconsole.

The following dashboards areavailable to EEZAdministrator users:

v Welcome Page





To be able to manage both first-leveland end-to-end automation domains,EEZAdministrator users must alsohave the EEZEndToEndAccess role.

EEZAdministratorGroup

EEZEndToEndAccessUsers who do not have this role, canview, and monitor the end-to-endautomation domain and the resourcesthat are hosted by the domain.

This role is only required if a userneeds to start or stop end-to-endautomation resources or activate anddeactivate end-to-end automationpolicies.

This role determines which type ofautomation domain a user who hasthis role can or cannot access. It doesnot determine which operations auser can run given this role.

EEZEndToEndAccessGroup

The EEZ* access roles authorize only users to access and work with SystemAutomation Application Manager tasks and dashboards. Other administrativeconsole tasks of the Dashboard Application Services Hub are only available tousers who have the iscadmins access role.

You also need the iscadmins role to be able modify existing or create newdashboards in the Dashboard Application Services Hub.

By default, the iscadmins role is assigned to the default System Automationadministrator (for example eezadmin) during the installation of System AutomationApplication Manager.


Chapter 3. Messages

All messages that are generated by the sub-components and automation adaptersof the System Automation Application Manager are listed in this topic includingthe appropriate user responses to the messages.

Policy editor messagesThis reference provides all messages that are generated by the policy editor ofSystem Automation for Multiplatforms.

SAMP0001E: An 'IOException' was caught in methodmethodName of class className. The received message wasmessage.

Explanation

The processing was interrupted by this exception and cannot complete.

System action

The task is ended.

Operator response

Try to resolve the problem described in the exception message and resubmit thecommand.

SAMP0002E: The specified policy policyLocation is not valid.Explanation

The policy is not valid. You cannot perform any task with this policy.

System action

The current task ends.

Operator response

Try to make the policy valid by analyzing the error messages following thismessage. Then resubmit the command.

SAMP0003E: Not able to create an object of type Object-type.The name of the tree-node is node-name.

Explanation

There is a problem when building an internal object of the input XML.

System action



Operator response

Check for related messages. If you cannot resolve the problem contact IBMsupport.

SAMP0004E: Not able to retrieve the policy information.Explanation

The policy information cannot be retrieved because the policy is not valid.

System action


Operator response

Try to make the policy valid by analyzing all the error messages.

SAMP0005E: Received errors when trying to activate thepolicy.

Explanation

Policy activation task resulted in errors.

System action

The activation task ends.

Operator response

Analyze the error messages and try to resolve the problem.

SAMP0006E: The specified policy file " policyFile " cannot befound.

Explanation

The policy cannot be loaded from this location.

System action


Operator response

Verify the policy XML file name and its path.

SAMP0007E: Original Parser Exception: exceptionMessageExplanation

An internal problem occurred while parsing this policy.


System action

The task cannot be performed.

Operator response

Verify if the product is installed correctly.

SAMP0008E: Received errors when trying to deactivate thecurrent policy.

Explanation

Policy deactivation resulted in errors.

System action

The deactivation task ends.

Operator response


SAMP0009E: Received errors when trying to check the policy.Explanation

Policy check task resulted in errors.

System action

The check task ends.

Operator response


SAMP0010E: Received errors when trying to save the currentpolicy.

Explanation

Policy save task resulted in errors.

System action

The save task ends.

Operator response


Chapter 3. Messages 183

SAMP0011E: The resource with name resourceName and classclassName was found as member of multiple groups.

Explanation

A resource can only be member of one group.

System action

This policy is not valid and cannot be activated.

Operator response

Check that each resource is only member of at most one group element in thispolicy.

SAMP0012E: The resource with name resourceName and classclassName was found as member of an equivalency and of agroup.

Explanation

A resource cannot be member of a group and of an equivalency.

System action


Operator response

Check that each resource is only member of either a group or an equivalency.

SAMP0013E: The specified member " memberName " wasfound multiple times in the same <groupForm> " groupName ".

Explanation

All <Members> child elements must be unique in one group.

System action

This policy is not valid.

Operator response

Check that the group has no duplicate <Members> child elements in this policy.

SAMP0014E: The specified <groupForm> " groupName " wasfound as member of itself.

Explanation

A group cannot be member of itself.


System action


Operator response

Check that no group is member of itself in this policy.

SAMP0015E: The resource group with nameresourceGroupName has a nesting level of more than 50.

Explanation

The nesting level of a resource group is limited to 50.

System action


Operator response

Reduce the nesting level of this group and resubmit the command.

SAMP0016E: An 'Exception' was caught in methodmethodName of class className. The received message wasmessage.

Explanation


System action

The task is ended.

Operator response

Try to resolve the problem described in the exception message and resubmit thecommand.

SAMP0017E: The relationship with the source with namesourceName and type type has a target with the same key.

Explanation

A relationship cannot have the same source and target.

System action


Operator response

Correct the relationship and resubmit the command.


SAMP0018E: The relationship source with name sourceNameand class sourceClass is not a resource group nor member ofa resource group.

Explanation

A relationship source must either be a resource group or member of a resourcegroup.

System action


Operator response


SAMP0019E: An error occurred in method methodName ofclass className. Error details details.

Explanation

The processing was interrupted by this error and cannot complete.

System action

The task is ended.

Operator response

Try to resolve the problem described in the error details and resubmit thecommand.

SAMP0020E: The specified <Relationship> with the <Type> "relationType ", the <Source> with the name " source " and the<Target> with the name " target " was found multiple times inthe policy document.

Explanation

All <Relationship> elements must be unique.

System action

This policy cannot be activated.

Operator response

Check that at most one <Relationship> of this type is specified in this policy.


SAMP0021E: An 'UTFDataFormatException' was caught inmethod methodName of class className. The receivedmessage was message.

Explanation


System action

The task cannot be performed.

Operator response

Ensure the correct data format of the policy document by only using editors whichcreate UTF-8 conform documents.

SAMP0022E: A <Element> can only contain either a<subElement1> or a <subElement2>.

Explanation

It is not allowed to specify both kinds of sub-elements for this element.

System action


Operator response

Check that at only one of the conflicting sub-elements is specified in this policy.

SAMP0023E: A <Element> that contains a <subElement1> mustalso contain a <subElement2>.

Explanation

It is not allowed to specify only one of these sub-elements for this element.

System action


Operator response

Check that both sub-elements are specified in this policy.

SAMP0024E: A <Element> that contains a <subElement1> mustalso contain a <subElement2> or a <subElement3>.

Explanation

It is not allowed to specify only one of these sub-elements for this element.


System action


Operator response

Check that both sub-elements are specified in this policy.

SAMP0025E: The <Element> with the name " referenceName "refers to a resource that does not exist on the cluster.

Explanation

Every resource that is referenced within the policy must exist in the cluster.

System action


Operator response

Create the resource on the cluster then resubmit the command.

SAMP0026E: The node with the name " nodeName " does notexist on the cluster.

Explanation

Every node that is referred to within the policy must exist in the cluster.

System action


Operator response

Correct the value of the node in the policy then resubmit the command.

SAMP0027E: The node with the name " nodeName " is notonline in the cluster.

Explanation

Every node that is referred to within a resource attribute must be online in thecluster.

System action


Operator response

Correct the value of the node in the policy or make the node online then resubmitthe command.


SAMP0028E: The value " domainName " of the element<elementName> does not conform to the real name of thecluster " actualDomainName ".

Explanation

The name of the cluster specified in the policy must be equal to the real name.

System action


Operator response

Correct the value in the policy then resubmit the command.

SAMP0029E: The specified element <element> with the name "groupName " contains a member with a different name "memberName " .

Explanation

For this kind of group all <Members> child elements must have the same name asthe group itself.

System action


Operator response

Check that the groups name is equal to all <Members> child elements names inthis policy.

SAMP0030E: The specified element <element> was found morethan once.

Explanation

Only zero or one element of this type is allowed in the policy.

System action


Operator response

Check that at most one element of this type is specified in the policy.

SAMP0031E: The specified element <childElement> was foundmore than once as child element of <parentElement>.

Explanation

Only zero or one element of this type is allowed.


System action


Operator response

Check that at most one element of this type is specified in this policy.

SAMP0032E: The specified element <childElement> was foundmore than once as child element of <parentElement> with thename " parentName ".

Explanation

Only zero or one element of this type is allowed in this group.

System action


Operator response

Check that at most one element of this type is specified in this group in this policy.

SAMP0033E: The value " value " of the element <allowedNode>does not exist as a node, nor is an equivalency with thisname defined.

Explanation

This value must either be a node or the name of an equivalency.

System action


Operator response

Correct the policy and resubmit the command.

SAMP0034E: The element <element> with the name "equivalencyName " cannot be target of a location relationship.

Explanation

A location relationship cannot have a target element of that kind.

System action


Operator response



SAMP0035E: The element <element> with the value "elementValue " can only be used with a location relationshipexcept the relationship of the type " isStartableType ".

Explanation

A condition is not allowed for this kind of relationship.

System action


Operator response


SAMP0036E: The element <element> with the name "elementValue " has got members that are not from the sameresource class.

Explanation

All members of an equivalency must be from the same resource class.

System action


Operator response

Correct the equivalency and resubmit the command.

SAMP0037E: The connection to the backend failed becausethe following exception occurred exception.

Explanation

An exception occurred when trying to perform an operation on the backend.

System action

The policy cannot be activated.

Operator response

Try to analyze the exception description and try to correct the problem. If theproblem persists, contact IBM support.

SAMP0038E: The element <tie-breaker> with the name " name "is set to active although at least one other element of thiskind is set to active, too.

Explanation

Only one such element is allowed to be active.


System action


Operator response

Ensure there is at most one active element of this kind in the policy and resubmitthe command.

SAMP0039E: The specified element <element> with the value "value " of the subelement <subelement1> cannot contain asubelement <subelement2> as well.

Explanation

For this kind of element some subelements are not allowed for certain subelementvalues.

System action


Operator response

Remove the invalid subelement or change the value of the other subelement andresubmit the command.

SAMP0040E: An IOException was caught when trying to writethe policy to the file " filename ". The exception message was:exception-message.

Explanation

The file could not be written.

System action

The active task ends.

Operator response

Ensure the directory does exist and there is enough disk space available thenresubmit the command.

SAMP0041E: Exception occurred when trying to validate theselection string " selectString ". Either the selection string isnot valid or the connection to the backend failed. Exceptionmessage was: exception.

Explanation

An exception occurred when trying to validate the selection string.


System action


Operator response

Ensure the selection string is valid. Try to analyze the exception description andtry to correct the problem. If the problem persists, contact IBM support.

SAMP0042E: The <Element> with the name " referenceName "has an invalid value for the subelement <Sub-Element>.

Explanation

<ResourceReference> elements may not have one of the following values for their<Class> subelement: IBM.Application, IBM.ServiceIP, IBM.Test .

System action


Operator response

Correct the subelement value then resubmit the command.

SAMP0043E: The <Element> with the type " value " is notallowed on a " value " system.

Explanation


System action


Operator response

Correct the value then resubmit the command.

SAMP0044E: A <Element> must either contain a <Subelement>or a <Subelement>.

Explanation


System action


Operator response

Correct the element then resubmit the command.


SAMP0045E: An IOException was caught when trying to readfrom the included policy file " filename ". The exceptionmessage was: exception-message.

Explanation

The file could not be read.

System action


Operator response

Ensure the file does exist and the userid used for the command has sufficientaccess rights then resubmit the command.

SAMP0046E: The syntax of the input policy file " filename " isinvalid. The line in error is: invalid line.

Explanation

The input policy file contains an invalid line.

System action


Operator response

Correct the invalid line in the input file then resubmit the command.

SAMP0047E: Variable referenced within line " invalid line " notfound in top-level XML file. Variable is referenced within file: "inputfilename ".

Explanation

The input policy contains a variable that is not defined in the top-level XML file.

System action


Operator response

Add the variable to the top-level XML file then resubmit the command.

SAMP0048E: The policy created from the top-level filepolicyLocation is not valid. The resulting policy can be found inthe temporary file temp-filename.

Explanation

The resulting policy is not valid. You cannot perform any task with this policy.


System action


Operator response

Try to make the policy valid by analyzing the error messages following thismessage. Then resubmit the command.

SAMP0049E: An error occurred in class: className method:methodName. The resource resourceName could not bedefined. There was no exception, but the define call did notreturn any object either.

Explanation

The current process was interrupted by this exception and cannot complete.

System action

The policy activation process stops and will return with this error message.

Operator response

Try to find out, if this resource was described properly in the XML policydocument and restart the activation. Please contact IBM support, if the problempersists and provide logs and traces.

SAMP0050E: An error occurred in class: className method:methodName. The resource resourceName could not bedefined. The received exception was exception

Explanation

The process was interrupted by this exception and cannot complete.

System action

The policy activation process stops and will not complete.

Operator response

Try to find out, if this resource was described properly in the XML policydocument and restart the activation. Please contact IBM support, if the problempersists and provide logs and traces.

SAMP0051E: An error occurred in class: className method:methodName. The resource resourceName could not be addedto the resource group groupName. The received exception wasexception

Explanation



System action


Operator response

Try to solve the problem described in the exception message and resubmit thecommand.

SAMP0052E: An error occurred in class: className method:methodName. The resource group groupName could not be setto the desired state state. The received exception wasexception

Explanation


System action


Operator response


SAMP0053E: An error occurred in class: className method:methodName. The resource resourceName could not beundefined. The received exception was exception

Explanation

The reason could be that the resource is not Offline or FailedOffline or the resourcemight have been deleted before by internal commands.

System action

The policy activation or deactivation will continue.

Operator response

Try to verify, if the resource still exists. Analyze the exception and try to resubmitthe command.


SAMP0054E: An error occurred in class: className method:methodName. The resource resourceName could not beidentified and located. This can be caused by an exception orthe resource could not be found. Therefore the resourceresourceName cannot be added to the resource groupgroupName. The received exception was exception

Explanation


System action


Operator response


SAMP0055E: An error occurred in class: className method:methodName. The resource group groupName could not beidentified and located. This can be caused by an exception orthe resource could not be found. Therefore the resourcegroup groupName cannot be set to the state state. Thereceived exception was exception

Explanation


System action


Operator response


SAMP0056E: An error occurred in class: className method:methodName. The resource resourceName could not beidentified and located. This can be caused by an exception orthe resource could not be found. Therefore the resourceresourceName cannot be created, because it requires resourceresourceName. The received exception was exception

Explanation



System action


Operator response


SAMP0057E: An error occurred in class: className method:methodName. The resource resourceName could not beidentified and located. This can be caused by an exception orthe resource could not be found. Therefore the resourceresourceName cannot be deleted. The received exception wasexception

Explanation

The resource might have been deleted before by internal commands.

System action

The current process will continue.

Operator response


SAMP0058E: An error occurred in class: className method:methodName. The resource resourceName could not beidentified and located. This can be caused by an exception orthe resource could not be found. Therefore the resourceresourceName cannot be modified. The received exception wasexception

Explanation


System action

The current process will continue.

Operator response



SAMP0059E: An error occurred in class: className method:methodName. The resource resourceName could not bemodified. There was no exception, but the define call did notreturn any object either.

Explanation


System action


Operator response

Try to find out, if this resource was described properly in the XML policy.

SAMP0060E: An error occurred in class: className method:methodName. The resource resourceName could not bemodified. The received exception was exception

Explanation


System action


Operator response

Try to find out, if this resource was described properly in the XML policy andrestart the activation. Please contact IBM support, if the problem persists andprovide logs and traces.

SAMP0061E: An error occurred in class: className method:methodName. The IBM.TieBreaker resource resourceNamecould not be identified and located. The received exceptionwas exception

Explanation


System action


Operator response



SAMP0062E: An error occurred in class: className method:methodName. The active IBM.TieBreaker resource could not beidentified and located. Therefore the IBM.TieBreaker resourceresourceName could not be modified or created. The receivedexception was exception

Explanation


System action


Operator response


SAMP0063E: An error occurred in class: className method:methodName. The IBM.TieBreaker resource resourceNamecould not be set to active. The received exception wasexception

Explanation


System action


Operator response


SAMP0064E: An error occurred in class: className method:methodName. The subscription from consumer consumer toresource resourceName has failed. The received exception wasexception

Explanation


System action



Operator response


SAMP0065E: The attempt to update the current automationpolicy failed because errors were detected.

Explanation

The policy update task resulted in errors.

System action

The policy update task ends.

Operator response

Analyze the subsequent error messages and try to resolve the problem.

SAMP0066E: The <element> with the name elementNamecontains a member that has an invalid value className for itsattribute class.

Explanation

For this kind of element the value of the class attribute must be equal for all itsmembers.

System action


Operator response

Check that all members have the correct value for the class attribute.

SAMP0067E: An error occurred in class: className method:methodName. The resource resourceName could not beremoved from the resource group groupName. The receivedexception was exception

Explanation


System action


Operator response



SAMP0068E: The specified resource group with the name "name " contains a member that is a <subelement>. This is onlyallowed for resource groups that have a value of " value " forthe subelement <subelement1>.

Explanation

Resource groups that are collocated cannot have concurrent members.

System action


Operator response

Remove the invalid member or change the value of the subelement and resubmitthe command.

SAMP0070E: An error occurred in class: className method:methodName.

Explanation


System action

The policy deactivation process stops and will return with this error message.

Operator response

Try to submit the command, again. Please contact IBM support, if the problempersists and provide logs and traces.

SAMP0071E: An error occurred in class: className method:methodName.

Explanation


System action

The policy save process stops and will return with this error message.

Operator response



SAMP0072E: Failed to set information about the activatedpolicy file name: fileName, the error message is: error-message.

Explanation

The actual activation of the policy was successful, but saving its name and timefailed.

System action

The name of the file of the activated policy and the activation time was not saved.

Operator response


SAMP0073E: Failed to set information about deactivating apolicy. The error message is: error-message.

Explanation

The actual deactivation of the policy was successful, but saving the fact failed.

System action

The fact that the policy was deactivated was not saved.

Operator response


SAMP0074E: The <Element> element with the nameelementName must contain a <Subelement> subelement,because it describes an IPv6 address.

Explanation

The required subelement is missing. The processing was interrupted by this errorand cannot complete.

System action


Operator response



SAMP0075E: The <Element> element with the nameelementName contains both a <Subelement> subelement and a<Subelement> subelement.

Explanation

It is not allowed to specify both subelements. The processing was interrupted bythis error and cannot complete.

System action


Operator response


SAMP0076E: The <Element> element with the nameelementName contains a <Subelement> subelement that is toolarge.

Explanation


System action


Operator response


SAMP0077E: The <Element> element with the nameelementName contains a link local address.

Explanation


System action


Operator response


SAMP0078E: The <Element> element with the nameelementName contains a multicast address.

Explanation



System action


Operator response


SAMP0079E: The <Element> element is not supported with thecurrent Active Version avn.

Explanation


System action


Operator response

Correct the element or update the Active Version then resubmit the command.

SAMP0080E: The activation task was not able to delete allexisting resources. The reason for this is shown in theprevious messages.

Explanation

Deletion of existing resources failed. The processing was interrupted by this errorand cannot complete.

System action

The activation task ends.

Operator response

If the reason for the failure is that some resource is not Offline respectively FailedOffline then you may retry the command using the force option -f.

SAMP0081E: The deactivation task was not able to delete allexisting resources. The reason for this is shown in theprevious messages.

Explanation

Deletion of resources failed. The processing was interrupted by this error andcannot complete.

System action

The deactivation task ends.


Operator response

If the reason for the failure is that some resource is not Offline respectively FailedOffline then you may retry the sampolicy command using the force option -f.

SAMP0082E: The update task was not able to delete allexisting resources. The reason for this is shown in theprevious messages.

Explanation

Deletion of existing resources failed. The processing was interrupted by this errorand cannot complete.

System action

The update task ends.

Operator response

If the reason for the failure is that some resource is not Offline respectively FailedOffline then you may retry the command using the force option -f.

SAMP0083E: The value element of the var element with nameelement is not valid for the specified type " .

Explanation

The value specified needs to be of the specified type.

System action


Operator response

Correct the value and resubmit the command.

SAMP0084E: The value attribute of the var element with nameelement must not be empty.

Explanation

The value attribute must not be empty.

System action


Operator response

Specify a value and resubmit the command.


SAMP0085E: The element attribute value of the includeelement that points to file element must not be empty.

Explanation

The attribute value must not be empty.

System action


Operator response


SAMP0086E: At least on of the value attributes of the nestedvar elements of varoption element with name element is notvalid for the specified type.

Explanation

The value specified needs to be of the specified type.

System action


Operator response

Correct the value and resubmit the command.

SAMP0087E: The element attribute value of the var elementwith name element must not be empty.

Explanation

The attribute value must not be empty.

System action


Operator response


SAMP0088E: The dynSelString attribute of the var elementwith name element must not contain only one var name.

Explanation

There must be more than one var name in the dynSelString attribute.

System action



Operator response

Specify two var names separated by "," and resubmit the command.

SAMP0089E: At least one var that is referenced in thedynSelString attribute of the var element with name elementdoes not exist.

Explanation

The var elements referenced in the dynSelString attribute must exist for the policy.

System action


Operator response

Specify two var names separated by "," and resubmit the command.

SAMP0090E: The var element referenced in the multi attributeof the include element that points to file element does notexist.

Explanation

A var element that is referenced in a multi attribute value must exist for the policy.

System action


Operator response

Remove the include element or change the value of the multi attribute to anexisting var; then resubmit the command.

SAMP0091E: Two include elements must not point to thesame file: element.

Explanation

Two include elements must not point to one and the same xml file.

System action


Operator response

Remove one include element or change the xml file it points to; then resubmit thecommand.


SAMP0092E: If the enumeration attribute is set tovalue="choice", the attribute validValues must also bespecified and vice versa. The var element with name elementdoes contain either only enumeration=choice or validValue.

Explanation

If you set the enumeration attribute to value="choice", the validValues attributemust also be specified. If you specify the validValue attribute, you must set theenumeration attribute to value="choice".

System action


Operator response

Either specify both values or remove the specified enumeration=choice/validValuesattribute. Resubmit the command.

SAMP0093E: At least one of the entries of the validValuesattribute value does not match the specified type attributevalue and/or the min/max attribute values of the var elementwith name element.

Explanation

All entries of the validValues attribute value must comply with the specified typeattribute value and or the min/max attribute values.

System action


Operator response

Correct the validValues attribute value and resubmit the command.

SAMP0094E: At least one var that is referenced in the multiattribute of the include element that points to the xml fileelement does not exist.

Explanation

The var elements referenced in the multi attribute must exist for the policy.

System action


Operator response

Specify existing var names separated by "," and resubmit the command.


SAMP0095E: The value attribute of the varoption element withname element must not be empty.

Explanation

The value attribute must not be empty.

System action


Operator response

Specify either "yes" or "no" and resubmit the command.

SAMP0096E: There is no valid license available for the policyyou are trying to activate.

Explanation

The policy you are trying to activate requires a separate license that is currentlynot installed.

System action

This policy cannot be activated without the missing license.

Operator response

Install the license and resubmit the command.

SAMP0097E: The value of the max attribute is smaller than thevalue of the min attribute for the var element with nameelement.

Explanation

The value of the max attribute must be greater than or equal to the value of themin attribute.

System action


Operator response

Correct the min and max attribute values and resubmit the command.

SAMP0500W: The specified policy policyLocation contains noresource group.

Explanation

The policy is valid, but without a resource group there is no automation active.


System action

Processing continues.

Operator response

Ensure this is what you want to do. Otherwise change the policy to contain at leastone resource group and resubmit the command.

SAMP0501W: An 'Exception' was caught in methodmethodName of class className. The received message wasmessage.

Explanation

The processing was interrupted by this exception but it can continue.

System action


Operator response

Try to resolve the problem described in the exception message.

SAMP0502W: The two <Relationship> elements with <Type>"StartAfter" and <Type> "StopAfter" were found with the same<Source> with the name " source " and <Target> with thename " target ".

Explanation

The two <Relationship> elements with <Type> "StartAfter" and <Type> "StopAfter"should not have the same <Source> and <Target>. With this configuration the<Target> is started before the <Source> and the <Target> is stopped before the<Source>.

System action

Application continues.

Operator response

Verify this behavior. The common usage of "StartAfter" together with "StopAfter" isthe following: 1. The <Source> of the "StartAfter" is the <Target> of the"StopAfter". 2. The <Target> of the "StartAfter" is the <Source> of the "StopAfter".


SAMP0503W: All members of the group with the name "groupName " should be collocated, because the group is partof a location relationship or of a relationship of the type "dependsOnType ". Set the value of the groups tag<memberLocation> to " collocatedValue ".

Explanation

For these kinds of relationships all members of a source or target group should becollocated.

System action


Operator response

Check that all members of this group are collocated in this policy.

SAMP0504W: The specified <Relationship> with <Type> "relationType " and <Source> with the name " Sourcename " and<Target> with the name " Target " was found in a loop.

Explanation

<Relationship> elements of the same <Type> where one <Relationship> element<Target> is the next <Relationship> element <Source> should not form a loop.

System action


Operator response

Check that the <Relationship> elements are not defined as loop in this policy.

SAMP0505W: A <Relationship> with the <Type> " relationType "was found that has linked more than 100 resources.

Explanation

The numbers of resources linked by a relationship is limited to 100.

System action


Operator response

Reduce the number of resources linked by the relationship.


SAMP0506W: The specified element <element> with the value "value " of the subelement <subelement1> should not contain asubelement <subelement2> as well. This subelement isignored.

Explanation

For this kind of element some subelements are not supported for certainsubelement values.

System action

Application continues. Subelement is ignored.

Operator response

Remove the invalid subelement or change the value of the other subelement.

SAMP0507W: The resource group with nameresourceGroupName has linked more than 100 resources.

Explanation

The numbers of resources linked by a resource group is limited to 100.

System action


Operator response

Reduce the number of resources linked by this group.

SAMP0508W: An error occurred in method methodName ofclass className. Error details details.

Explanation

The processing was interrupted by this error but it can continue.

System action


Operator response

Try to resolve the problem described in the error details.

SAMP0509W: A non-critical error occurred in methodmethodName of class className during activation of a newpolicy. Error details details.

Explanation



System action

Activation continues.

Operator response

Try to resolve the problem described in the error details. Please try to activate thepolicy again and check, if the error still occurs. If the error persists, please contactIBM support and provide logs and traces.

SAMP0510W: A non-critical error occurred in methodmethodName of class className during deactivation of thecurrent policy. Error details details.

Explanation


System action

Deactivation continues.

Operator response

Try to resolve the problem described in the error details. Please try to deactivatethe policy again and check, if the error still occurs. If the error persists, pleasecontact IBM support and provide logs and traces.

SAMP0511W: A non-critical error occurred in methodmethodName of class className during saving of the currentpolicy. Error details details.

Explanation


System action

Saving process continues.

Operator response

Try to resolve the problem described in the error details. Please try to resubmit thesave command and check, if the error still occurs. If the error persists, pleasecontact IBM support and provide logs and traces.

SAMP0512W: The resource group member name is specifiedwith the invalid attribute combination of non-mandatory and "value ".

Explanation

For this kind of element this combination of attribute values is invalid.


System action


Operator response

Correct the invalid value and resubmit the command.

SAMP1000I: Usage: sampolicy -h sampolicy [-T] [-V] [-q] [-f] -afilename sampolicy [-T] [-V] [-q] -u filename sampolicy [-T] [-V][-q] [-f] -r filename sampolicy [-T] [-V] [-q] [-f] -d sampolicy [-T][-V] -s [filename] sampolicy [-T] [-V] [-u] -c filename sampolicy[-T] [-V] -i filename sampolicy [-T] [-V] [-q] [-f] -a -ttemplatefilename sampolicy [-T] [-V] [-q] -u -t templatefilenamesampolicy [-T] [-V] [-q] [-f] -r -t templatefilename sampolicy [-T][-V] [-u] -c -t templatefilename sampolicy [-T] [-V] -i -ttemplatefilename sampolicy [-T] [-V] -w templatefilename

Explanation

No additional information is available for this message.

SAMP1001I: The specified policy policyLocation is valid.Explanation

The policy is valid and can be activated.

System action


Operator response

None.

SAMP1002I: The policy has the following policy information:policyInfo.

Explanation

This is the information for the policy.

System action


Operator response

None.


SAMP1003I: The policy has been activated successfully.Explanation

The policy is now active in the domain.

System action


Operator response

None.

SAMP1004I: The activation task ends.Explanation

The policy is not going to be activated because the user did not confirm thisaction.

System action

Processing ends.

Operator response

None.

SAMP1005I: The activation task ends.Explanation

The automation policy could not be activated.

System action

Processing ends.

Operator response

None.

SAMP1006I: The current policy was saved to file filename.Explanation


SAMP1007I: The automation policy was deactivatedsuccessfully.

Explanation

There is now no policy active in the domain.


System action


Operator response

None.

SAMP1008I: Template processing failed. The active task ends.Explanation

Template processing failed and therefore the active task cannot completesuccessfully.

System action

Processing ends.

Operator response

None.

SAMP1009I: The automation policy was updated successfully.Explanation

The current automation policy was updated with the new policy.

System action


Operator response

None.

SAMP1010I: The update task ends because you did notconfirm the action.

Explanation

The current automation policy can only be updated if you confirm the updateaction.

System action

Processing ends.

Operator response

None.


SAMP1011I: The attempt to update the current automationpolicy failed.

Explanation

The current automation policy could not be updated.

System action

Processing ends.

Operator response

None.

SAMP1100I: Starting to check policy policyLocation.Explanation


SAMP1101I: Starting to load policy.Explanation


SAMP1102I: Retrieving policy info of policyLocation.Explanation


SAMP1103I: Are you sure you want to activate a newautomation policy? Yes (y) or No (n) ?

Explanation


SAMP1104I: Deactivation will remove all resources which canbe created via policy activation. Deactivation will not changeany resources of the class IBM.TieBreaker Are you sure youwant to deactivate the current automation policy? Yes (y) orNo (n) ?

Explanation


SAMP1105I: Please enter the root password:Explanation



SAMP1106I: Now calling the backend in order to retrieve alldata needed.

Explanation


SAMP1107I: Now calling the backend in order to activate thepolicy.

Explanation


SAMP1108I: Now calling the backend in order to deactivatethe policy.

Explanation


SAMP1109I: Removed resources successfully.Explanation


SAMP1110I: Created and changed resources successfully.Explanation


SAMP1111I: Are you sure you want to update the currentautomation policy? Yes (y) or No (n) ?

Explanation


EEZ message codeMost messages that are generated by subcomponents of System AutomationApplication Manager begin with a unique message code.

Example:

EEZS1234E

v EEZ – component identifier of the System Automation Application Managerv S – represents one of the following prefixes:

– A - Messages issued by automation adapters

Note: System Automation for z/OS adapter messages:- Within NetView an additional * may be appended to the end of the

message text.


- Because these messages are written to the syslog on z/OS, the message textmust be in English.

– B, J, L, T – Automation JEE framework messages– C – Messages issued by various utilities– D – Automation engine messages– E – Discovery library adapter messages– F – Automation engine resource adapter messages– G – Automation web services messages– H – Hardware adapter messages– I – Automation manager resource adapter messages– K, X – Automation Software Development Kit messages– P – Policy-related messages– Q – ITM integration messages– R – Agentless adapter messages– S - Messages issued by the command shell of the end-to-end automation

manager– U – Operations console messages– V – VCS Solaris adapter messages– Y, Z - MSCS adapter messagesMessages are sorted alphabetically by subcomponent prefix.

v 1234 – unique four-digit numberv E – one of the following severity code identifiers:

– I for Information– W for Warning– E for Error

EEZ message catalogThis section lists the messages that are generated by subcomponents of the SystemAutomation Application Manager that have the prefix EEZ. The messages aresorted alphabetically by subcomponent prefix.

For information about additional messages you might encounter while workingwith the System Automation Application Manager,see the remaining messagesections of this document and to the documentation for the correspondingfirst-level automation product.

Prefix EEZA

EEZA0001E Syntax error on line line number

Explanation: A syntax error has occurred in theconfiguration file, for example a leading = on a line.

System action: The automation adapter stops.

Operator response: Analyze the configuration file forinvalid syntax.

EEZA0002E Wrong datatype in key the key. Expectedthe desired type, found value the value thatwas found

Explanation: The value of the given key cannot beinterpreted as the desired type. For example, thesystem expected a boolean value but found the stringhello.


Operator response: Analyze the configuration file forinvalid key/value pairs.

Prefix EEZA • EEZA0002E


EEZA0003E The key the key that was not found wasnot found and no default value wasgiven

Explanation: The system attempted to retrieve a valuefrom the configuration file that did not exist and nodefault value was given.


Operator response: Supply a value for the key in theconfiguration file.

EEZA0004E Integer out of bounds in key the key .Expected value between the lower boundexpected and the upper bound expected,found the value parsed

Explanation: The system expected an integer valuebetween the given bounds (inclusive) for the given key,but found a value outside these bounds.


Operator response: Supply a value within the givenbounds for the key.

EEZA0006E Cannot create an instance of the classbecause class not found: class name

Explanation: The automation adapter cannot load theclass.

System action: The automation adapter rejects therequest.

Operator response: Check whether the class name isvalid and is available in the corresponding classpath.

EEZA0007E Cannot create an instance of the classbecause method not found: class name

Explanation: The automation adapter can load theclass but cannot create an instance.


Operator response: Check whether the class is valid.

EEZA0008E Cannot create an instance of the classbecause of an unknown error: class name

Explanation: The automation adapter cannot load theclass or create an instance.


Operator response: Check whether the class is validand analyze the attached original exception.

EEZA0009E Invocation of adapter plug-in failed:plug-in=plug-in name, method=methodname, internalRetcode=internal returncode, taskRetcode=task return code

Explanation: The automation adapter client API wascalled to execute a task on the remote adapter. The callfailed. There are three error categories: The clientsuffers an error on the connection or the execution ofthe task within the automation adapter backend failedor execution failed in the automation adapter plug-in.

System action: Execution of the remote task failed.

Operator response: Analyze the return codedescription. If it is an internal error, check IBMElectronic Support for additional information -http://www.ibm.com/support/entry/portal/

EEZA0010E Request expires before the adapterpasses it to the adapter plug-in. Timeoutperiod is timeout value seconds

Explanation: All requests have an associatedexpiration date. The request is scheduled to anexecution thread that detected that the expiration timehad expired.


Operator response: Analyze the reason (for example,high working load). Increase the timeout period ifnecessary.

EEZA0011E The backend program specification isinvalid

Explanation: The backend program is not a Javaprogram or the Java program name was not specified.


Operator response: Check the program that called theautomation adapter client API.

EEZA0012E Invalid parameter list

Explanation: The automation adapter detected arequest that is associated with an invalid parameter list.


Operator response: Check the program that called theautomation adapter client API.

EEZA0013E Authentication for user ID user namewas unsuccessful

Explanation: The request is associated with an user IDand password that have been validated unsuccessfully.

EEZA0003E • EEZA0013E



Operator response: Check whether the user ID isauthorized for the system and check the security policy.

EEZA0014E The original exception original-classneeds to be transported to the remotecaller

Explanation: An exception from an underlyingcomponent needs to be transported to the remote caller.

System action: None.

Operator response: Analyze the original exceptionattached with this message.

EEZA0015E Method not supported: name of themissing method

Explanation: The automation adapter detected anunknown method name. The list of all valid methodnames is defined in the EEZAdapterInteractioninterface.


Operator response: Check IBM Electronic Support foradditional information - http://www.ibm.com/support/entry/portal/

EEZA0017E Request not supported: name of theunsupported request

Explanation: The automation adapter plug-in does notsupport the specified request.

System action: The request might be rejecteddepending on the behavior of the plug-in.

Operator response: Check if the automation domainsupports this type of request.

EEZA0022E Adapter client is unable to connect tothe adapter at host:port due to exception:the exception that was caught

Explanation: The automation adapter client cannotconnect to the server at the given host and port. Theoriginal exception text is provided.

System action: The connection is not established.

Operator response: Analyze the original exception.

EEZA0023E Cache directory is invalid

Explanation: The EIF cache directory is not adirectory.


Operator response: Correct the configuration file.

EEZA0024E EIF sender and receiver must not beequal

Explanation: The EIF configuration parameters are notallowed to point to each other.



EEZA0025E Cannot find the plug-in configurationfile: configuration file name

Explanation: The master configuration file containsthe name of a plug-in configuration file that cannot befound.



EEZA0026E No plug-in configuration file wasspecified

Explanation: The master configuration file mustcontain at least one plug-in configuration file.



EEZA0027E Cannot load configuration file:configuration file name

Explanation: The specified configuration file cannot beloaded.



EEZA0028E Plug-in configuration file does notcontain all mandatory parameters:configuration file name

Explanation: The specified configuration file does notcontain all mandatory parameters. The plug-in is notused.

System action: The automation adapter does notdeploy the plug-in.


EEZA0029E Cannot create the first instance of theplug-in class: class name

Explanation: An attempt was made to create the firstinstance of the plug-in during initialization. Creationfailed.





EEZA0030E Cannot set up event subscription list forplug-in configuration file: plug-inconfiguration file name

Explanation: The specification of the EIF event classesin the plug-in configuration file is invalid.



EEZA0031E Cannot load configuration file from:plug-in configuration file name

Explanation: The automation adapter cannot load thespecified configuration file because either noconfiguration file or an invalid one was specified.


Operator response: Check whether the name of theconfiguration file is correct.

EEZA0032E Initialization of the adapter failedoriginalexception

Explanation: An error occurred in the initializationstep of the automation adapter.


Operator response: Analyze the associated exception.If there is no exception text for this message, try to findadditional messages that were sent previously.

EEZA0033E Unable to create type of factorySocketFactory

Explanation: The automation adapter server or clientcannot create a socket factory for remote contact.

System action: The automation adapter client cannotcreate a connection or the automation adapter servercannot receive connections.

Operator response: Analyze the reason using previousmessages.

EEZA0036E The adapter suffered an unexpectedinterruption: original exception

Explanation: The automation adapter waits for atermination command. An unexpected interruptionoccurred.


Operator response: Analyze original exception.

EEZA0037E The adapter stops running because noplug-in has been successfully initialized

Explanation: At least one plug-in must have beensuccessfully initialized otherwise the automationadapter stops.


Operator response: Analyze previous messages andexceptions issued by the failing plug-in.

EEZA0038E A (SSL) socket configuration erroroccurred: exception text

Explanation: An error occurred during the loading orprocessing of (SSL) socket-related configuration data.An SSL handshake exception will only be reportedduring initial contact.

System action: The automation adapter client cannotcreate a connection or the automation adapter servercannot receive connections.

Operator response: Analyze the exceptions text.Check the SSL configuration file if necessary.

EEZA0039E Not all data was read from socket:number of bytes read bytes read, number ofbytes expected bytes expected to be read

Explanation: The incoming request has a length inbytes, but not all bytes can be read.


Operator response: Check why the socket connectionwas broken while transfering data.

EEZA0040E The adapter client cannot establishconnection to the adapter: stringrepresentation of the connection

Explanation: Opening the connection failed. A requestcannot be sent to the automation adapter. The stringrepresentation of the connection contains details aboutthe connection.

System action: The automation adapter frontendfailed.

Operator response: Analyze the connectioninformation.

EEZA0041E The adapter client cannot invoke anadapter request: InternalRC=internalreturn code, TaskRC=task return code

Explanation: A connection to the automation adapterhas been successfully established. The automationadapter frontend might have sent a request to theautomation adapter but the request failed. If theinternal or task return codes are not applicable (n/a),



some other unexpected exception occurred.


Operator response: Analyze the internal and taskreturn codes (see EEZA0009E for an explanation of thereturn codes).

EEZA0042E The adapter has thrown a remoteexception: InternalRC=internal returncode, TaskRC=task return code. Theoriginal message was: message text

Explanation: A connection to the automation adapterhas been successfully established. The automationadapter frontend has sent a request to the automationadapter but the plug-in has thrown an exception.


Operator response: Analyze the internal and taskreturn codes (see EEZA0009E for an explanation of thereturn codes).

EEZA0043E A required command line parameter ismissing

Explanation: One of the required command lineparameters is missing (such as -start, -stop or-terminate).


Operator response: Specify the requiredcommand-line parameters and try again.

EEZA0045E The adapter cannot establish a serversocket due to illegal arguments: exceptiontext

Explanation: The automation adapter cannot establisha receiver thread and cannot accept incomingconnections.


Operator response: Analyze the configuration file forinvalid IP address.

EEZA0047E The adapter is unable to acceptconnections due to socket exceptionexception

Explanation: An exception occurred as the automationadapter was about to accept an incoming connection.


Operator response: Analyze the exception text.

EEZA0051W Termination of the adapter failed due toexception: error message

Explanation: The attempt to stop the receiver threadfailed because an exception occurred.


Operator response: Analyze the exception text.

EEZA0052E Cannot create an in-storage EIFconfiguration file: exception text

Explanation: An instance of the Java classByteArrayInputStream cannot be created or written.


Operator response: This is probably an internal error.The exception text might give the reason for theproblem.

EEZA0053E Missing argument for command lineparameter the parameter

Explanation: A required argument for a command lineparameter (such as -start) is missing. For example,AdapterCmd -start would be wrong, because -startrequires an argument. A correct example would be:AdapterCmd -startcom.ibm.ing.saplugin.INGXPluginInvocation.

System action: Processing of this command ends.

Operator response: Check the documentation forinformation about valid command line arguments andtheir parameters.

EEZA0055E Remote Contact inactivity thresholdexceeded: elapsed seconds=elapsedseconds threshold=threshold

Explanation: The automation adapter calculates theelapsed time since the last synchronous request wasreceived. The automation adapter stops itself if thistime exceeds the number specfied in the parametereez-remote-contact-activity-interval-seconds. Anyincoming event is used as a trigger for the calculation.


Operator response: You might want to increase thenumber of seconds specified by parametereez-remote-contact-activity-interval-seconds. Setting thisparameter to 0 (zero) means it never expires.

EEZA0056I Initial contact was enabled and theconnection to the management serverhas been established

Explanation: The parameter eez-initial-contact was setto true and the automation adapter attempted toconnect the management server. The handshake to themanagement server was successful.

EEZA0042E • EEZA0056I



Operator response: No action required.

EEZA0057E The connection to the managementserver cannot be established

Explanation: The automation adapter stops attemptingto connect the management server because the timeoutinterval is over.


Operator response: You might want to increase thenumber of minutes specified by parametereez-initial-contact-retry-interval-minutes. Specify thevalue 0 (zero) in order to retry forever.

EEZA0058E The plug-in has not been deployed or isnot yet started: name of the Java plug-inclass

Explanation: An attempt was made by the automationserver to issue a request to the automation adapteragainst an unknown plug-in or a plug-in that has notbeen started.


Operator response: Check the plug-in configurationfile on the automation adapter site for the parameterplugin-impl-class. Compare it with the plugin classname specified in the message. If there is a mismatchan installation problem might be the reason for theproblem. Analyze further adapter messages e.g.EEZA0115I.

EEZA0059E An internal error occurred

Explanation: The automation adapter detected aninternal error.



EEZA0060I The termination of the adapter isdelayed for duration of the delay in secondsseconds

Explanation: Stopping the automation adapter isdelayed for a short while until it has sent theappropriate domain leave events. You can configure theduration of this delay with the eez-stop-delay-secondsparameter.

System action: The automation adapter attempts tosend domain leave events.


EEZA0061E Unable to bind a socket to addresseez-remote-contact-hostname at porteez-remote-contact-port. Reason: message ofthe exception

Explanation: The automation adapter was unable touse this address or port. Possible causes of the problemare: 1) The port is already in use by another program.2) The address could not be assigned.


Operator response: Make sure that no program usesthis port (that is, an automation adapter that is alreadyrunning). If another program needs this port, thenconfigure the automation adapter to use another port(with the eez-remote-contact-port parameter in themaster configuration file). Ensure that the address isvalid.

EEZA0062I The start command of the automationplug-in name of the Java plug-in class wassuccessful

Explanation: The selected automation plug-in wassuccessfully started.

System action: The automation adapter has started theautomation plug-in.


EEZA0063I The stop command of the automationplug-in name of the Java plug-in class wassuccessful

Explanation: The selected automation plug-in wassuccessfully stopped.

System action: The automation adapter has stoppedthe automation plug-in.


EEZA0064I The termination command for theadapter was successful

Explanation: The automation adapter was successfullystopped.



EEZA0070E The host name eez-remote-contact-hostnameis unknown

Explanation: The automation adapter was unable toresolve the host name.


Operator response: Specify a valid host name.



EEZA0071E The domain name is either null orempty

Explanation: The plug-in returned an invalid domainname since its is either null or empty.

System action: The plug-in cannot be started.

Operator response: Specify a valid domain name inthe plug-in configuration file.

EEZA0100I The adapter has been started

Explanation: This is the first of a sequence of threemessages until the automation adapter is ready. Theautomation adapter starts initialization and will try toconnect to the management server ifeez-initial-contact=true.



EEZA0101I The adapter is active

Explanation: The automation adapter becomes activeafter a connection has been successfully established tothe management server. The automation adaptercontinues initialization, finds and starts up all plug-ins.



EEZA0102I The adapter is ready

Explanation: The automation adapter startup sequenceis complete.



EEZA0103I The adapter is stopping

Explanation: An internal or an external stop commandhas been received.

System action: The automation adapter is about tostop.


EEZA0104I The adapter has been stopped

Explanation: The automation adapter termination iscomplete. All possible stop delay periods are over. Theprocess stops immediately.

System action: The automation adapter has stopped.


EEZA0105I The adapter has been stopped due to afailure, rc=return code

Explanation: The automation adapter stopped becausean error occurred. All possible stop delay periods areover. The process stops immediately.


Operator response: Search for error messages thatwere issued previously. On z/OS return code 28 mightbe caused due to the 64-bit JVM. You should use the32-bit JVM instead. If a stop command has been issuedagainst the adapter, while the adapter is trying toestablish an inital contact to the management server,the adapter will stop with return code 12 or 13indicating that the adapter was not able to establish aninital contact within the time period before the stopcommand was received. See also message EEZA0057E.

EEZA0111I The plug-in is starting: name of the Javaplug-in class

Explanation: The automation adapter has alreadysuccessfully created an instance of the plug-in class andwill now call function INIT_DOMAIN.



EEZA0112I The plug-in has been started: name of theJava plug-in class

Explanation: The automation adapter plug-in hassuccessfully initialized the domain (INIT_DOMAIN).



EEZA0113I The plug-in is stopping: name of the Javaplug-in class

Explanation: The automation adapter will call plug-infunction TERM_DOMAIN.



EEZA0114I The plug-in has been stopped: name ofthe Java plug-in class

Explanation: The automation adapter plug-in hassuccessfully stopped the domain (TERM_DOMAIN).



EEZA0071E • EEZA0114I


EEZA0115I The plug-in startup failed: name of theJava plug-in class

Explanation: This message might follow afterEEZA0111I, but the attempt to start the plug-in viafunction INIT_DOMAIN failed. The automationadapter plug-in will not be started automatically.

System action: The plug-in will be disabled. A joinevent was not sent.

Operator response: You might want to restart theplug-in using the automation adapter start command.Analyze further plug-in messages.

EEZA0116I The status of the event sender changed:Address=Address, Port=Port,Status=Status

Explanation: This message occurs if the status of theEIF connection changed. The reason could be that anew EIF connection is created or an existing EIFconnection is lost. The reason can be found in thestatus. A status='connection timed out' is expected ifthe SA Application Manager is stopped e.g. if the SAApplication Manager moves to another system andtherefore the adapter needs to change the EIF senderdestination.



EEZA9991E The message file is not installed

Explanation: The English message file must beavailable.


Operator response: Make sure that the message file isin the class path.

EEZA9992E EEZAdapterLogger is not available

Explanation: The automation adapter loggingcomponent has not been initialized.

System action: The automation adapter stops. Otherprocesses using the automation adapter client API willbe unable to write messages into log and trace files.


Prefix EEZB

EEZB0001E The following runtime exceptionoccurred: exceptionText

Explanation: Processing was interrupted by aRuntimeException and cannot complete correctly.

System action: The current task ends.

Operator response: Evaluate the exception details.Check the message log for additional messages.

EEZB0003E A critical error has occurred in class:className, method: methodName. Thelogger object could not be initialized.

Explanation: This component could not initialize andaccess a logger object. This indicates either aconfiguration or programming error.

System action: The process cannot be completed. Allparts of this component are affected. The system is notoperational.

Operator response: Check that the path settings arecorrect and all required libraries exist.

EEZB0015E An error has occurred in class:className. The variable 'locale' has notbeen set.

Explanation: This variable is mandatory for executinga request at the automation engine. This indicates aprogramming error on the EJB exploiter side.



EEZB0025E An error has occurred in class:className, method: methodName. Illegalparameter at invocation of this method.

Explanation: The method has been invoked with anull parameter. The method must be invoked with aparameter that is not null. This indicates aprogramming error.



EEZB0030E A exception has occurred in class:className, method: methodName. Thenested exception equals null.

Explanation: No exception object was linked to theResourceException that has been caught. This is anunexpected behavior and indicates a programmingerror on the J2C side.



EEZA0115I • EEZB0030E


EEZB0031E An error has occurred in class:className, method: methodName. Invalidnested exception: nestedException.

Explanation: An invalid exception object was linkedto the ResourceException that has been caught. This isan unexpected behavior and indicates a programmingerror on the J2C side.



EEZB0033E An error has occurred in class:className, method: methodName. JNDIName: jndiName did not return aConnectionFactory object.

Explanation: The JNDI lookup of this J2C hasencountered an internal error. The ConnectionFactoryobject could not be retrieved. This indicates a JNDIconfiguration error.

System action: The current task ends. No connectionto the automation engine will be possible until thisproblem is fixed.

Operator response: Ensure that the JNDI settings forthe J2C connection factories are correct and restart theserver.

Prefix EEZC

EEZC0001I Setting up Tivoli Common Directory atlocation where Tivoli Common Directory isbeing set up.

Explanation: The Tivoli Common Directory path wasset to its default value, as shown in the message text.

System action: No system action required.

Operator response: No operator action required.

EEZC0002I Unable to determine Tivoli CommonDirectory. Diverting serviceabilityrelated output to alternative location.

Explanation: The system was not able to determinethe Tivoli Common Directory.

System action: Processing continues. The applicationwill attempt to divert serviceability related output toanother location for this session.

Operator response: In order to manage itsserviceability related output, the application should begranted read/write permission to the location/etc/ibm/tivoli/common.

EEZC0003I Base output directory for serviceabilityrelated files (for example, message logfiles and trace files) has been set to newoutput directory.

Explanation: The output directory for serviceabilityrelated files was set to its default value, as shown inthe message text.

System action: From now on the application willwrite serviceability related information to the directorythat is contained in the message text.

Operator response: No action is required if the baseoutput directory for serviceability related files isacceptable. Otherwise, if it is required to relocate thebase output directory, modify the entry inlog.properties which should be located at/etc/ibm/tivoli/common/cfg/log.properties. Changesto this file will take effect once the correspondingcomponent is restarted.

EEZC0004I Changing base output directory forserviceability related files of name oflogger from old output directory to newoutput directory.

Explanation: Due to changes in configuration settingsthe output directory of serviceability related files hasbeen relocated.

System action: From now on the system will writeserviceability related information to the new location.

Operator response: No action is required if the baseoutput directory for serviceability related files isacceptable. Otherwise, if it is required to relocate thebase output directory, modify the entry inlog.properties which should be located at/etc/ibm/tivoli/common/cfg/log.properties. Changesto this file will take effect once the correspondingcomponent is restarted.

EEZC0006E Remote replication operation failed forfile fileName . A connection from localnode loaclNode to remote noderemoteNode could not be established.

Explanation: An error occurred when attempting toreplicate, create or delete a file on a remote node.Establishing a connection between the local node andthe remote target node on which the replication,creation or deletion actually was supposed to beperformed failed. The remote file operation could notbe completed successfully.

System action: The failing remote file operation isskipped and processing continues.

Operator response: Make sure that the local as well asthe remote node are known host names and that IPconnectivity between those two systems is correctly setup. Check whether network problems were reported atthe time where the failure occured.

EEZB0031E • EEZC0006E


EEZC0007E Remote replication operation failed forfile fileName . Authentication failedwhen establishing a connection fromlocal node loaclNode to remote noderemoteNode for user ID userID .

Explanation: An error occurred when attempting toreplicate, create or delete a file on a remote node.Establishing a connection between the local node andthe remote target node on which the replication,creation or deletion actually was supposed to beperformed failed due to incorrect user credentials. Theremote file operation could not be completedsuccessfully.

System action: The failing remote file operation isskipped and processing continues.

Operator response: Make sure that the user ID andpassword used to perform the remote file operation arecorrectly defined on the target node.

EEZC0008E Replication of file fileName failed. Theconnection from local node loaclNode toremote node remoteNode was lost. Theoriginal exception was: excMessage .

Explanation: An error occurred when attempting toreplicate a file on a remote node. The connectionbetween the local node and the remote target node onwhich the replication actually was supposed to beperformed was lost during the replication operation.The replication of the file could not be completedsuccessfully.

System action: The failing file replication is skippedand processing continues.

Operator response: Make sure that IP connectivitybetween those two systems is correctly set up. Thefailure may also occur due to timeouts. The originalexception message may give some hints about the rootcause of the problem.

EEZC0009E Remote deletion of file fileName failed.The connection from local nodeloaclNode to remote node remoteNode waslost. The original exception was:excMessage .

Explanation: An error occurred when attempting todelete a file on a remote node. The connection betweenthe local node and the remote target node on which thedeletion actually was supposed to be performed waslost during the delete operation. The remote deletion ofthe file could not be completed successfully.

System action: The failing remote file deletion isskipped and processing continues.

Operator response: Make sure that IP connectivitybetween those two systems is correctly set up. Thefailure may also occur due to timeouts. The original

exception message may give some hints about the rootcause of the problem.

EEZC0010E Remote creation of file fileName failed.The connection from local nodeloaclNode to remote node remoteNode waslost. The original exception was:excMessage .

Explanation: An error occurred when attempting tocreate a file on a remote node. The connection betweenthe local node and the remote target node on which thecreation actually was supposed to be performed waslost during the create operation. The remote creation ofthe file could not be completed successfully.

System action: The failing remote file creation isskipped and processing continues.

Operator response: Make sure that IP connectivitybetween those two systems is correctly set up. Thefailure may also occur due to timeouts. The originalexception message may give some hints about the rootcause of the problem.

EEZC0011E An unexpected I/O Exception occurredwhen attempting to replicate filefileName from local node loaclNode onremote node remoteNode . The originalexception was: excMessage .

Explanation: An error occurred when attempting toreplicate a file on a remote node. Writing the file on theremote target node failed with an unexpected I/Oexception. The replication of the file could not becompleted successfully.

System action: The failing file replication is skippedand processing continues.

Operator response: Make sure that the directory onthe target node where the file is to be written iscorrectly defined and accessible in read/write mode.The original exception message may give some hintsabout the root cause of the problem.

EEZC0012E An unexpected I/O Exception occurredwhen attempting to delete file fileNameon remote node remoteNode . Theoriginal exception was: excMessage .

Explanation: An error occurred when attempting todelete a file on a remote node. Deleting the file on theremote target node failed with an unexpected I/Oexception. The remote deletion of the file could not becompleted successfully.

System action: The failing remote file deletion isskipped and processing continues.

Operator response: Make sure that the directory onthe target node where the file is to be deleted iscorrectly defined and accessible in read/write mode.The original exception message may give some hints

EEZC0007E • EEZC0012E


about the root cause of the problem.

EEZC0013E An unexpected I/O Exception occurredwhen attempting to create file fileNameon remote node remoteNode . Theoriginal exception was: excMessage .

Explanation: An error occurred when attempting tocreate a file on a remote node. The name of the remotefile indicates either the file actually to be created or atemporary file that is supposed to be created beforerenaming it to the actual target file. Creating the file onthe remote target node failed with an unexpected I/Oexception. The remote creation of the file could not becompleted successfully.

System action: The failing remote file creation isskipped and processing continues.

Operator response: Make sure that the directory onthe target node where the file is to be created iscorrectly defined and accessible in read/write mode.The original exception message may give some hintsabout the root cause of the problem.

EEZC0014E Remote creation of file fileName toremote node remoteNode failed.Renaming temporary file tempFile toactual target file targetFile failed withreturn code rc . The issued renamecommand was: cmd . The commandresult was: cmdResult .

Explanation: An error occurred when attempting tocreate a file on a remote node. The create operationconsists of two steps: first creating a temporary file onthe remote node and second renaming the temporaryfile to the file actually to be created. The creation of thetemporary file completed successfully, but renaming itto the target file failed.

System action: The failing remote file creation isskipped, the temporary file is removed and processingcontinues.

Operator response: Inspect the result output that wasproduced by the rename command and that is includedin the message text to determine the reason for thefailure.

EEZC0015E The server nameserverNameAndOptionalPort could not beparsed successfully.

Explanation: An error occurred while evaluating theserver name. Allowed input are host names, or IPv4addresses, or IPv6 addresses. The host name or the IPaddress can be followed by a colon and a port number.If a literal IPv6 address is supplied, it has to beenclosed with brackets, for example: [::1], or [::1]:2809

System action: Evaluation of the server name ends.

Operator response: Inspect the server name for

syntactical correctness. If a host name has beenspecified, check if the host name can be resoved byDNS (for example, try to ping the host).

Prefix EEZD

EEZD0002E An exception was caught while trying tocontact the JMS queue of the end-to-endautomation manager.

Explanation: The automation engine was unable toestablish contact with the end-to-end automationmanager. This contact is required to forward EIF eventsfrom other automation domains.

System action: The automation engine is unable tocontact the server. It has to be restarted when theproblem has been resolved.

Operator response: Check the correct configurationfor WAS Access User ID and Password. Restart theautomation engine.

EEZD0003E A 'JMSSecurityException' was caughtwhile trying to contact the JMS queueof the end-to-end automation manager.



Operator response: Check the correct configurationfor WAS Access User ID and Pasword. Restart theautomation engine.

EEZD0004E Method was invoked with a null orempty parameter.

Explanation: A null or empty (list of) parameter wasencountered.

System action: The method returns withoutprocessing the request any further.


EEZD0005E A 'NoPermissionException' was caughtwhile trying to contact the server withhostname: server hostname on port: serverport.

Explanation: The automation engine was unable tocreate an initial contact with the server in order to startthe system automation.

System action: The automation engine is unable to

EEZC0013E • EEZD0005E


contact the server. It has to be restarted after theproblem has been resolved.

Operator response: Check the setup of permissions inorder to contact the server as an EJB client. Check theWAS access User ID.

EEZD0006E An 'InterruptedException' was caught inmethod methodName of class className.The received message was message.

Explanation: The processing was interrupted by thisexception and cannot complete.



EEZD0007E A 'RemoteException' was caught inmethod methodName of class className.




EEZD0008E An 'AlreadyBoundException' of servicehandlerName was caught during startupof the automation engine.

Explanation: This service has already bound before.

System action: The automation engine ends.

Operator response: Verify the automation engine isonly started once on your system.

EEZD0009E A 'MalformedURLException' of servicehandlerName was caught during startupof the automation engine.

Explanation: This service name is not valid in yourenvironment.



EEZD0010E The dispatcher thread threadName of theautomation engine is unable to dispatcha message or request to the automationJEE framework. The number of retrieswas: Number of already attempted retries.Original exception text was: OriginalException text

Explanation: The automation JEE framework is not

accessible at the moment. This message will occurperiodically as long as the problem persists.

System action: The thread will keep on trying tocontact the automation JEE framework to dispatch therequest or event.

Operator response: Ensure that the application serverhosting the automation JEE framework of theautomation manager is up and running. Verify that theautomation JEE framework is running. Check theconfiguration of the automation engine.

EEZD0013E The required library <Name of Library>cannot be loaded by the automationengine.

Explanation: The library, which contains modulesrequired by the automation engine, cannot be loaded.

System action: The core logic engine is unable toinitialize. The automation engine is not able to receiveany further commands and will terminate.

Operator response: Ensure that the library exists inthe lib directory of the automation engine install root.

EEZD0014E A remote exception was caught whileexecuting command line interfacefunction <Name of CLI method>.

Explanation: The command line interface functioncaught a remote exception while trying to connect tothe automation engine.

System action: The command line interface wasunable to execute the requested function.

Operator response: Ensure that the automation engineis running on this system and that you are allowed toexecute commands against it.

EEZD0015E An error occurred preparing a request tothe core logic engine used by theautomation engine. Internal errormessage is: <Reason for encoder error>.

Explanation: A request to the Core Logic Engine couldnot be created.

System action: The current action fails.


EEZD0016E An IOException was caught while tryingto load policy Name of policy from thepolicy pool.

Explanation: The policy could not be read.

System action: The policy cannot be parsed. Theautomation engine is not able to activate this policy

EEZD0006E • EEZD0016E


and will continue to run with the currently activatedpolicy.

Operator response: Resolve the error indicated by theexception text.

EEZD0017E No or invalid policy pool directoryspecified. The value specified is: <PolicyPool Directory>

Explanation: The value specified for the Policy Pool iseither empty or does not specify a directory.

System action: The automation engine was not able tofind or load a policy document and will continue torun with the current policy.

Operator response: Ensure that the indicatedenvironment variable points to the correct directory onthe local machine where policy documents are placed.Ensure that the automation engine process hassufficient rights to open this directory.

EEZD0019E Unable to activate policy <Name ofpolicy>

Explanation: The policy cannot be activated. Thispolicy either does not comply with the required XMLsyntax or has not passed the consistency check done bythe policy checker.

System action: The policy cannot be activated. Theautomation engine will continue operation with itscurrently activated policy

Operator response: See detailed error messageslogged for this policy above. Resolve the error(s) in thispolicy before trying to activate it again.

EEZD0020E Domain name <Name of domain in policy>in policy <Name of policy> does notmatch automation engine domain <Nameof automation engine domain>.

Explanation: The policy cannot be activated. It is validonly for the indicated domain.

System action: The policy cannot be activated. Theautomation engine will continue operation with itscurrently activated policy.

Operator response: Activate a policy for the currentlyactive domain, or reconfigure and restart theautomation engine to represent another domain.

EEZD0021E Expression <unsupported filter value> usedduring query is not supported.

Explanation: The specified filter is not supported.

System action: The enumeration of resources orrelationships fails.

Operator response: Check IBM Electronic Support for

additional information - http://www.ibm.com/support/entry/portal/

EEZD0022E Unknown event <Event Type> withreason <Event Reason> was received bythe automation engine.

Explanation: This event cannot be handled by theautomation engine.

System action: The automation engine continuesprocessing.


EEZD0023E An EEZConfigurationException wasreceived while trying to set the usercredentials for the list of domainsspecified in the policy.

Explanation: The policy cannot be activated.

System action: The automation engine is not able toactivate this policy and will continue to run with thecurrently activated policy.


EEZD0024E A Generic user ID or password is notspecified in the <file name> file.

Explanation: A user and password for the GENERICdomain must always be specified in the properties file.

System action: The load of the properties file failed.

Operator response: Specify a user and password valuefor the GENERIC domain.

EEZD0025E Key: <key> occurs more than once in theproperties file.

Explanation: To avoid confusion, only unique keyscan be specified in the properties file.


Operator response: Delete the duplicate keys from theproperties file.

EEZD0027E The required thread thread name of theautomation engine process terminated.The exception exception name caused thethread to terminate.

Explanation: The thread terminated because of theindicated unhandled exception.

System action: The automation engine will try torestart this required thread. Tasks which were justprocessed by the thread during this termination may



have not been completed. This can cause a loss ofevents or requests sent against other automationdomains. The automation engine will performsynchronization actions.

Operator response: Evaluate the exception details. Ifthe problem persists then restart the end-to-endautomation engine.

EEZD0028E A NotBoundException of service<handlerName > was caught duringshutdown processing of the automationengine.

Explanation: This service has not been bound before.



EEZD0029E No referenced resources hosted by afirst-level automation domain werereturned from the core logic engine.

Explanation: The currently activated policy containsno, or invalidly specified, resource references, or aproblem occurred during execution of a task within thecore logic engine.

System action: The automation engine cannot executethe current task.

Operator response: Check the currently activatedpolicy and activate it again.

EEZD0030E Problem occurred parsing the core logicengine response for orders. An orderwas received, but an unknown actionwas found.

Explanation: The response to an internal workitemfrom the engine could not be parsed correctly.



EEZD0032E Method Method name cannot be executed,since the automation engine process isstarting.

Explanation: A public method of the automationengine has been called, but the automation engine hasnot finished its startup processing.


Operator response: Wait until the automation enginestartup completed message has been returned. Thencall the method again.

EEZD0033E Method Method name cannot be executed,since automation engine process isstopping.

Explanation: A public method of the automationengine has been called, but the automation engine iscurrently shutting down on request.



EEZD0034E Unable to create a registry for theautomation engine process on port: PortNumber to bind its services.

Explanation: An exception was caught during startupof the automation engine while trying to create aregistry object. This can be caused by anotherautomation engine process running on this system, oranother process using the port.

System action: The automation engine cannotcomplete the startup task. The automation engineprocess will terminate.

Operator response: Ensure that only one instance ofthe automation engine process is started on yoursystem. If this is not the cause of this error, find outwhich process is blocking the port number indicated inthe message text.

EEZD0035E Unable to create the Command LineInterface (CLI) handler of theautomation engine process.

Explanation: A RemoteException was caught duringstartup of the CLI handler.



EEZD0036E Unable to create the main thread of theautomation engine process.

Explanation: A RemoteException was caught duringstartup of the main thread.





EEZD0037E The following services are bound:Service Name.

Explanation: The automation engine is unable tocreate a new registry. The listed services are alreadybound


Operator response: Ensure that only one instance ofthe automation engine process is started on yoursystem.

EEZD0038E Unable to start the EIF receiver for theautomation engine process on system:Hostname port: Port Number to bind itsservices.

Explanation: An exception was caught during startupof the automation engine while trying to start the EIFreceiver. This can be caused by another automationengine process running on this system, another processusing the port, or a hostname that cannot be resolved.


Operator response: Ensure that only one instance ofthe automation engine process is started on yoursystem. If this is not the cause of this error, find outwhich process is blocking the port number indicated inthe message text. If necessary configure another Eventport number in the automation engine configuration.Ensure that the hostname can be resolved on the localsystem and that the hostname is not the loopbackaddress.

EEZD0039E Automation engine process is in anillegal state to perform the requestedoperation.

Explanation: A public method of the automationengine has been called, but the automation engine iscurrently not in valid state to perform this operation.

System action: The automation engine does notexecute the current task.

Operator response: To perform this operation ensurethat the automation engine is running and has a policyactivated.

EEZD0040E Not all required properties are specifiedwithin the properties file: file name.Value for property Property name is notspecified.

Explanation: The properties file cannot be loaded ifnot all of the required properties (key/value pairs) arespecified in the file.


Operator response: Specify the required propertycorrectly in the properties file.

EEZD0041E Property Property name exceeds themaximum length of Maximum length ofProperty

Explanation: The properties file contains invalidvalues for the specified property.


Operator response: Specify all required propertiescorrectly in the properties file.

EEZD0042E Value for property Property name is not anumeric value.

Explanation: The specified property must be anumber.


Operator response: Specify all required propertiescorrectly in the properties file.

EEZD0050E An IOException occurred during startupof the automation engine process.Original Exception text is: IO Exceptiontext

Explanation: The IOException cannot be handled bythe automation engine process.

System action: The automation engine processterminates.

Operator response: Ensure that the automation enginehas sufficient rights to access the indicated file.

EEZD0060E An EEZIllegalArgumentException wascaught when trying to execute a list ofrequests. Following is a list of requestscausing this exception: List of failingrequests

Explanation: The requests cannot be executed onresources of the targeted automation domain.

System action: The automation engine will not try toinvoke these requests again. They will be ignored. Theautomation engine continues to work.




EEZD0061E An EEZExecutionFailedException wascaught trying to execute a list ofrequests. Following is a list of requestscausing this exception: List of failingrequests. The following message wasreturned by the exception: ExceptionMessage. Original message contained inthe caught exception: Original message

Explanation: The requests cannot be executed onspecified resources of the targeted automation domain.This might be caused by a broken communication linkto the referenced resource.

System action: The automation engine will not try toinvoke these requests again. They will be ignored. Theautomation engine continues to work.

Operator response: Ensure that the targeted first levelautomation domain is accessible by the end-to-endautomation manager.

EEZD0062E An EEZExecutionTimeoutException wascaught trying to execute a list ofrequests on domain Domain name. Retrynumber is: Retry number. Following is alist of requests causing this exception:List of failing requests. Original messagetext is: Exception text

Explanation: The requests could not be completedwithin a timeout period.

System action: The automation engine tries to invokethese requests again. The automation engine continuesto work.


EEZD0063E An EEZIllegalArgumentException wascaught trying to subscribe to otherautomation domains. Following is a listof domains the automation engine triedto subscribe to: List of domains to subscribeto

Explanation: The subscription cannot be executed.

System action: The automation engine will not try tosubscribe to these domains again. They will be ignored.The automation engine continues to work.


EEZD0064E An EEZExecutionFailedException wascaught trying to subscribe to otherautomation domains. Following is a listof domains causing this exception: Listof domains to subscribe to. The followingmessage was returned by the exception:Exception Message


System action: The automation engine will not try tosubscribe to these domains again. The domains will beignored. The automation engine continues to work.

Operator response: Check the status of each listeddomain. If the domains are working properly issue thecommand shell command 'eezctrl -r *' to refresh theend-to-end automation engine, or restart the end-to-endautomation engine.

EEZD0065E An EEZExecutionTimeoutException wascaught trying to subscribe to otherautomation domains. Following is a listof domains causing this exception: Listof domains to subscribe to.




EEZD0066E An EEZIllegalArgumentException wascaught trying to subscribe to resourceshosted on other automation domains.Following is a list of resources theautomation engine tried to subscribe to:List of resources to subscribe to


System action: The automation engine will not try tosubscribe to these domains again. They will be ignored.The automation engine continues to work.


EEZD0067E An EEZExecutionFailedException wascaught trying to subscribe to resourceshosted on other automation domains.Following is a list of resources theautomation engine tried to subscribe to:List of resources to subscribe to. Thefollowing message was returned by theexception: Exception Message



Operator response: Check the status of each listeddomains. Check resources for each domain to verify ifthe domain is working properly. If the domains areworking properly then issue the command shellcommand 'eezctrl -r *' to refresh the end-to-end



automation engine, or restart the end-to-endautomation engine.

EEZD0068E An EEZExecutionTimeoutException wascaught trying to subscribe to resourceshosted on other automation domains.Following is a list of resources theautomation engine tried to subscribe to:List of resources to subscribe to




EEZD0069E A security exception was caught tryingto subscribe to resources hosted onautomation domain Automation domainname. The automation engine tried tosubscribe to the following list ofresources: List of resources to subscribe to.



Operator response: Ensure that the user credentials inthe configuration of the automation engine are correct.If you modified the credentials refresh the automationengine using the Refresh button on the ApplicationManager tab of the System Automation ApplicationManager Configuration dialog or using thecorresponding option in silent configuration mode(cfgeezdmn command).

EEZD0072E An EEZUserSecurityException wascaught trying to contact anotherautomation domain. Original messagetext is: Security Exception text

Explanation: The automation engine was unable tocontact the automation domain to execute commands.

System action: The automation engine will not try toinvoke the command again.

Operator response: Resolve the error indicated by theexception text. Ensure that the user credentials in theconfiguration of the automation engine contains correctUser IDs and valid passwords to access the indicatedautomation domain. After fixing the problem it is alsorequired to refresh the automation engine by clickingthe Refresh button on the Application Manager tab ofthe System Automation Application ManagerConfiguration dialog or using the corresponding optionin silent configuration mode (cfgeezdmn command).

EEZD0073E An EEZSystemSecurityException wascaught trying to contact anotherautomation domain. Original messagetext is: Security Exception text



Operator response: Resolve the error indicated by theexception text. Ensure that the User credentials in theconfiguration of the automation engine contains correctUser IDs and valid passwords to access the indicatedautomation domain. After fixing the problem it is alsorequired to refresh the automation engine by clickingthe Refresh button on the Application Manager tab ofthe System Automation Application ManagerConfiguration dialog or using the corresponding optionin silent configuration mode (cfgeezdmn command).

EEZD0074E The properties file contains an invalidline.

Explanation: A line in the properties file is notmarked as a comment and cannot be read as akey-value pair.


Operator response: Correct a line in the properties filethat should be a comment or that is missing theseparator character.

EEZD0075E An EEZDomainNotAccessibleExceptionwas caught trying to contact anotherautomation domain. Original messagetext is: Exception text



Operator response: Resolve the error indicated by theexception text. After fixing the problem it is alsorequired to refresh the automation engine by clickingthe Refresh button on the Application Manager tab ofthe System Automation Application ManagerConfiguration dialog or using the corresponding optionin silent configuration mode (cfgeezdmn command).

EEZD0080E An Exception was caught trying toinstall the license certifcate <Certificatefile name>. Original exception was:Original exeption text

Explanation: The automation engine was unable toinstall the mentioned license certificate.

System action: The automation engine is unable tohandle this license key. It will not perform any function



until a license key was successfully installed.


EEZD0081E An Error occured trying to install thelicense certifcate <Certificate file name>.Original return code of the license usagemanagement library was: LUM returncode

Explanation: The automation engine was unable toinstall the mentioned license certificate.

System action: The automation engine is unable tohandle this license key. It will not perform any functionuntil a license key was successfully installed.


EEZD0082E An Error occured trying to initialize thelicense usage management library.Original return code was: LUM returncode

Explanation: The automation engine was unable toinitialize the license use management.

System action: The automation engine is unable tohandle license keys and will terminate.


EEZD0083E No valid installed license key found onyour system. Message returned by thelicense usage management library was:LUM return message Original return codewas: LUM return code.

Explanation: The automation engine was unable todetect an installed license on your system.

System action: Without installed license key theautomation engine will not start.


EEZD0084E The automation engine does not have avalid license enrolled. If you purchaseda license for this product, then you havea production license. This license willbe automatically installed on yoursystem during the installation process.

Explanation: The automation engine was unable todetect an installed license on your system.

System action: Without installed license key theautomation engine will not start.

Operator response: If you installed this product withhelp of the product installer the installation processmust have encountered a problem. Check theinstallation log file.

EEZD0085E The automation engine does not findthe required feature license for featureName of licensed feature enrolled on thissystem.

Explanation: The automation engine was unable todetect a required feature license on your system.

System action: Without installed feature license theautomation engine will not perform the requestedaction.

Operator response: If you purchased the mentionedfeature license enroll it on the local system theautomation engine is running. Do this by using thecommand eezdmn -instcert.

EEZD0086E The feature license for feature Name oflicensed feature is not supported on thissystem.

Explanation: The current operating system or platformis not eligible for the feature you try to install.

System action: The feature license will not beinstalled.

Operator response: Check the documentation for thelist of supported operating systems and platforms.

EEZD0084W The automation engine already has avalid license of this type enrolled.

Explanation: An attempt was made to install a licensecertificate on the system which is already active.

System action: The automation engine will not installthis license certificate again.

Operator response: Check if you specified the correctlicense name. You can call this function again whenusing another license certificate.

EEZD0100E An error occurred within the core logicengine used by the automation engine.Message code <InternalMessageCode> hasbeen returned.

Explanation: The preprocessing of an internalworkitem failed.

System action: The current action fails.




EEZD0101E An error occurred during initializationof the core logic engine used by theautomation engine. The logic deck<LogicDeckName> cannot be activated.Message code <InternalMessageCode> hasbeen returned.

Explanation: The core logic engine required by theautomation engine could not be created.

System action: The automation engine is not able toreceive any further commands and will terminate.


EEZD0102E The internal encoder used by theautomation engine did not return aresult.

Explanation: The current workitem could not beencoded by the automation engine.

System action: The automation engine is not able toexecute the current task.


EEZD0103E The core logic engine used by theautomation engine did not return anyresult.

Explanation: The current workitem could not beexecuted by the automation engine.

System action: The automation engine is not able toexecute the current task.


EEZD0104E The resource resource name is not achoice group.

Explanation: The set preferred member operation issupported by choice groups only.

System action: The automation engine cannotcomplete this task.

Operator response: Ensure that the resource is achoice group.

EEZD0105E The automation engine received anempty list of orders from the Core LogicEngine.

Explanation: The response from the CLE indicates thatthere are orders to be handled but the list of orders isempty.


Operator response: Activate the policy again.

EEZD0106E An error occurred during initializationof the core logic engine used by theautomation engine. The logic deck<LogicDeckName> cannot be found oropened.

Explanation: The core logic engine required by theautomation engine could not be created.


Operator response: Check that a correct file name isspecfied for the Logic definition file of the advanceddomain configuration of the automation engine.

EEZD0107E An error occurred during initializationof the automation engine. The domainidentification file<DomainIdentificationFile> cannot befound or opened.

Explanation: The automation engine needs thedomain identification file in order to set up connectionsto other automation domains.


Operator response: Check that a correct file name isspecfied for the domain identfication file of theautomation engine.

EEZD0110E Resource ResourceName is not defined asmember of choice group GroupName. Itcannot be set as new preferred memberof this group.

Explanation: Only member resoures of the specifiedchoice group can be specified as new preferredmember.

System action: The automation engine will not changethe current preferred member.

Operator response: Specify some defined memberresource to be set as new preferred member.

EEZD0111E Resource GroupName is not defined aschoice group in current active policy.

Explanation: Only choice groups have a definedpreferred member.

System action: The automation engine will not handlethis request.

Operator response: Specify some valid choice groupas target of this request.



EEZD0112E Unable to activate policy Name of policyin the hardware adapter. Originalexception text is: Original Exception text

Explanation: The policy to be activated is a disasterrecovery policy, but cannot be activated in thehardware adapter.

System action: The disaster recovery policy cannot beactivated in the hardware adapter. Disaster recoverycommands therefore cannot be executed.

Operator response: Ensure that the hardware adapterand the automation JEE framework is up and running.

EEZD0113E Unable to activate policy Name of policybecause the hardware adapter is notavailable.

Explanation: The policy to be activated is a disasterrecovery policy, but cannot be activated in thehardware adapter because the hardware adapter is notavailable.

System action: The policy cannot be activated.

Operator response: Ensure that the hardware adapterand the automation JEE framework is up and running.Then activate the policy again.

EEZD0114E The following disaster recovery requestwas rejected: Disaster recovery requestname Request Name, issued by source:Source, user ID: User Id with comment:Comment text. The cluster set specified inthe -c parameter of the disaster recoveryrequest does not exist.

Explanation: The cluster set specified in the disasterrecovery request is not defined in the automationengine. Therefore, successful processing of the disasterrecovery request cannot be ensured.

System action: The automation engine will notprocess this disaster recovery request.

Operator response: Determine and correct the clusterset parameter, e.g. by using the command shellcommand lsclustersets, or in the disaster recoverypolicy.

EEZD0115E The following disaster recovery requestwas rejected: Disaster recovery requestname Request Name, issued by source:Source, user ID: User Id with comment:Comment text. The site specified in the -sparameter of the disaster recoveryrequest does not exist.

Explanation: The site specified in the disaster recoveryrequest is not defined in the automation engine.Therefore, successful processing of the disaster recoveryrequest cannot be ensured.


Operator response: Determine and correct the siteparameter, e.g. by using the command shell commandlsclusterset, or in the disaster recovery policy.

EEZD0116E The following disaster recovery requestwas rejected: Disaster recovery requestname Request Name, issued by source:Source, user ID: User Id with comment:Comment text. The addressed domainDomain Name has not joined orcommunication to it is broken.

Explanation: Currently, workload of the domaincannot be controlled, because no requests can be passedfrom the automation engine to the domain. Therefore,successful processing of the disaster recovery requestcannot be ensured.


Operator response: Ensure that the domain isaccessible by the automation engine. Add the forceoption -f to the disaster recovery request to disable thechecks in the preparation phase.

EEZD0117E The following disaster recovery requestwas rejected: Disaster recovery requestname Request Name, issued by source:Source, user ID: User Id with comment:Comment text. The compound state of theaddressed workload of type Type is notOK.

Explanation: The addressed workload is inunsatisfactory compound state. Therefore, successfulprocessing of the disaster recovery request cannot beensured.


Operator response: Ensure that the workload is insatisfactory state. Add the force option -f to the disasterrecovery request to disable the check in preparationphase.

EEZD0118E The following disaster recovery requestwas rejected: Disaster recovery requestname Request Name, issued by source:Source, user ID: User Id with comment:Comment text. The disaster recoveryrequest would trigger the start ofbusiness critical workload at a secondsite in a domain with no active-activeworkload setup.

Explanation: Start of business-critical workload atmultiple sites is only possible in domains withactive-active workload setup. Therefore, successful



processing of the disaster recovery request cannot beensured.


Operator response: Stop the business critical workloadat the other site first.

EEZD0119E The following disaster recovery requestwas rejected: Disaster recovery requestname Request Name, issued by source:Source, user ID: User Id with comment:Comment text. The addressed domainDomain Name is externally managed, thecluster set is managed by anotherautomation product.

Explanation: Starting and stopping of workload isonly possible for cluster sets that are managed by theautomation manager. Therefore, successful processingof the disaster recovery request cannot be ensured.


Operator response: Use the corresponding SA productto start or stop the workload.

EEZD0120E Processing of the disaster recoveryrequest Request Name failed which wasissued by source: Source, user ID: User Idwith comment: Comment text. Theexecution of the core logic engineworkitem for this disaster recoveryrequest failed.

Explanation: The automation engine can not processthis disaster recovery request.

System action: Processing of the current disasterrecovery request failed.


EEZD0121E A system check failed in preparationphase of disaster recovery requestRequest Name issued by source: Source,user ID: User Id with comment: Commenttext. The addressed domain DomainName has not joined or communicationto it is broken.

Explanation: Currently, workload of the domain is notcontrollable, because no requests can be passed fromthe automation engine to the domain. Therefore,successful processing of the disaster recovery requestcannot be ensured.

System action: Nevertheless, the automation enginewill process this disaster recovery request, because theforce option is set.

Operator response: Ensure that the domain isaccessible by the automation engine.

EEZD0122E A system check failed in preparationphase of disaster recovery requestRequest Name issued by source: Source,user ID: User Id with comment: Commenttext. The compound state of theaddressed workload of type Type is notOK.

Explanation: The addressed workload is inunsatisfactory compound state. Therefore, successfulprocessing of the disaster recovery request cannot beensured.

System action: Nevertheless, the automation enginewill process this disaster recovery request, because theforce option is set.

Operator response: Ensure that the workload iscontrollable by the automation engine.

EEZD0123E The following disaster recovery requestwas rejected: Disaster recovery requestname Request Name, issued by source:Source, user ID: User Id with comment:Comment text. Some resources of theaddressed workload of type Type aresuspended from automation.

Explanation: Successful processing of the disasterrecovery request cannot be ensured if some of theaddressed workload is suspended from automation.


Operator response: Resume the resources which aresuspended from automation either manually or byadding the force option -f to the disaster recoveryrequest.

EEZD0124E A system check failed in preparationphase of disaster recovery requestRequest Name issued by source: Source,user ID: User Id with comment: Commenttext. Some resources of the addressedworkload of type Type are suspendedfrom automation.

Explanation: Successful processing of the disasterrecovery request cannot be ensured if some of theaddressed workload is suspended from automation.

System action: Nevertheless, the automation enginewill process this disaster recovery request, because theforce option is set. The corresponding resources that aresuspended from automation will be resumed by theautomation engine.

Operator response: No action required



EEZD0125E The following disaster recovery requestwas rejected: Disaster recovery requestname Request Name, issued by source:Source, user ID: User Id with comment:Comment text. This disaster recoveryrequest is not supported in a stretchedcluster set because there is nodiscretionary workload allowed atprimary site.

Explanation: There is no discretionary workload atthis site of the cluster set since discretionary workloadis restricted to secondary site in stretched cluster sets.



EEZD0126E Request persistency method methodNamecould not be successfully invoked in theautomation JEE framework. Thefollowing exception was encountered:exceptionDetails

Explanation: The remote method invocation on theautomation JEE framework failed.

System action: The current request persistency relatedtask ends unsuccessfully. The automation enginecontinues to work.

Operator response: Ensure that the application serverhosting the automation JEE framework of theautomation manager is up and running. Verify that theautomation JEE framework is running. Check theconfiguration of the automation engine.

EEZD0127E Switching the preferred member ofGroupName is not supported since theaddressed resource is a disaster recoverychoice group in current active policy.

Explanation: The preferred member of disasterrecovery choice groups can only be switched by thedisaster recovery manager.


Operator response: Issue disaster recovery requestsfrom the disaster recovery manager to control theassociated workload.

EEZD0128E Requests against resource ResourceNamewill be refused since this resoure ismember of a choice group.

Explanation: It is not allowed to issue requests againstchoice group members. Choice group members canonly be started or stopped by issuing a request againstthe choice group itself.


Operator response: Issue the request against thechoice group.

EEZD0129E Rejected the requestName request againstthe resource resourceName of classresourceClass in domain domainName .

Explanation: The resource does not support thisrequest.

System action: The request is not processed.


EEZD0130E Rejected the requestName request againstthe resource resourceName of classresourceClass in domain domainName .

Explanation: The resource addressed in the requestdoes not exist in this domain.


Operator response: Check the resource key of therequest.

EEZD0131E Rejected the SetRole request withrequested role requestedRole against theresource resourceName of classresourceClass in domain domainName .

Explanation: The resource does not support the rolespecified in the request.


Operator response: Specify a role in the SetRolerequest that is supported by the resource.

EEZD0132E The following disaster recovery requestwas rejected: Disaster recovery requestname Request Name, issued by source:Source, user ID: User Id with comment:Comment text. This disaster recoveryrequest is not supported.

Explanation: A cluster set with this setup and currentrun-state does not support this disaster recoveryrequest.



EEZD0140E Unable to delete policy Policy File Name.This policy is currently active.

Explanation: The current active policy cannot bedeleted.



System action: The automation engine will notprocess this request.

Operator response: In order to delete this policy it isrequired to deactivate it first.

EEZD0150E Request sent to following resources areoverdue: Resource List.

Explanation: Requests have been sent to the specifiedresources, but no request event has been receivedacknowledging that they have been received by theautomation domain. No further automation seems to bepossible with the referenced resource.

System action: The automation engine sets theoperational state to broken. No further automation willbe done for these resources.

Operator response: Resolve potential communictionproblem with the referenced resources. Press the resetbutton when problem has been solved.

EEZD0151E The automation manager rejects therequest requestName for the dynamicresource referencedynamicResourceReferenceName . Thedynamic resource reference does notmatch a first-level automation resource.

Explanation: Requests are only allowed for dynamicresource references that are resolved to a matchingfirst-level automation resource.

System action: The automation manager rejects therequest.

Operator response: Create a first-level automationresource that matches the pattern that is defined in thedynamic resource reference. Then issue the requestagain for the resolved dynamic resource reference.

EEZD0152E The automation manager wasinterrupted by an exception while it washandling dynamic resource references.Details of the exception: exceptionDetails

Explanation: An unexpected exception occurred.

System action: The automation manager stops tohandle dynamic resource references in the context ofthe current task. The automation manager continues tohandle the overall task.

Operator response: Review the exception details,resolve the root cause, and retry the operation. If theend-to-end automation domain does not contain theexpected set of dynamic resource references, thenactivate the end-to-end automation policy again.

EEZD0160E The resource resource name is not a servergroup.

Explanation: The operation to change a target value issupported by server groups only.


Operator response: Ensure that the resource is aserver group.

EEZD0161E The target value new_target_value is notin the allowed range.

Explanation: The new target value must be higherthen 0 and lower or equal to the number of members.


Operator response: Ensure to specify only targets invalid range.

EEZD0200E A runtime exception was caught duringexecution of method method name.Original exception text is: exception name.

Explanation: An unexpected exception was caught.


Operator response: Resolve the runtime exception,and ensure correct installation of the product.

EEZD1004W The event notifying the automationserver about the terminating automationengine cannot be delivered.

Explanation: The automation engine assumes that theautomation server has already been terminated.

System action: The automation engine continues toshut down.

Operator response: Check the shutdown sequence.The automation engine should be terminated before theautomation server.

EEZD1005W Unable to contact the server onhostname: server hostname on port: serverport.

Explanation: The automation engine assumes arunning server in order to start the system automation.

System action: The automation engine will retry tocontact this server periodically.

Operator response: Ensure that this server is runningand reachable under this hostname. Check theconfiguration for Host name or IP address of theautomation engine.

EEZD0150E • EEZD1005W


EEZD1010W One or more resource reference(s) inyour currently active policy point toresources that cannot be found on thereferenced automation domain withname Name of automation domain.Following is the list of resourcereferences that cannot be resolved: Listof Resources which are invalid

Explanation: The resource reference(s) may have beenmisspelled in your currently active policy, or they justhave not been created on the referenced domain yet.

System action: The automation engine is not able todo any automation task or handle any requests againstthe specified resource reference(s).

Operator response: Check if the resource referencesare possibly misspelled. In this case, resolve this errorwithin the policy and activate it again.

EEZD1011W No policy can be found in the policypool: Policy Pool Directory which matchesthis domain: Domain Name

Explanation: The automation engine found at leastone policy file with extension '.xml' or '.XML' but nopolicy file matches the current domain represented bythe automation engine.

System action: The automation engine is not able toprovide a list of available policies.

Operator response: Check that a correct file name isspecfied for the Policy pool of the advanced domainconfiguration of the automation engine. Ensure thatpolicy documents inside this policy pool are defined forthe domain name configured for the automationengine.

EEZD1012W No policy can be found in the policypool: Policy Pool Directory

Explanation: The automation engine cannot find anyfile with extension '.xml' or '.XML'

System action: The automation engine is not able toprovide a list of available policies.

Operator response: Check that a correct file name isspecfied for the Policy pool of the advanced domainconfiguration of the automation engine. Ensure thatpolicy documents inside this policy pool are defined forthe domain name configured for the automationengine. Ensure that the user id used to start theautomation engine has sufficient rights to access thisdirectory.

EEZD1013W Problems occurred while trying to loadpolicy Name of policy from the policypool.

Explanation: The policy contains errors.

System action: The policy cannot be loaded andparsed. The automation engine is not able to activatethis policy.

Operator response: Check the named policy for errors.

EEZD1014W The resource reference Name of theresource reference defined in yourcurrently active policy points to aresource that cannot be controlled bythe end-to-end automation manager.

Explanation: During event processing the end-to-endautomation manager found that the referenced resourceis existing but the current observed state cannot bechanged by requests from the end-to-end automationmanager.

System action: The automation engine is not able todo any automation task or handle any requests againstthe specified resource reference. The referencedresource will only be monitored. The observed state ofthis resource reference will follow the observed state ofthe referenced resource. The operational state of thisresource will be set accordingly.

Operator response: Check if the resource referencepoints to the intended resource on the first levelautomation domain and change the end-to-endautomation policy if not.

EEZD1015W The request requestName with priorityrequestPriority by user requestUserid andsource requestSource has been removedbecause the related resourceresourceName is no longer defined in thecurrently active policy policyName . Thefollowing comment was associated withthe request: requestComment

Explanation: The automation engine encountered apersistent request related to a resource that is no longerdefined in the currently active end-to-end policy. Theautomation engine removed this request automatically.

System action: The automation engine continues torestore persistent requests for those resources that arestill defined in the currently active policy.

Operator response: Verify that the related resource hasnot been removed from the end-to-end automationpolicy by mistake.

EEZD1016W The request requestName with priorityrequestPriority by user requestUserid andsource requestSource has been removedbecause the related resourceresourceName is a direct or indirectmember of a choice group as defined inthe currently active policy policyName .The following comment was associatedwith the request: requestComment

EEZD1010W • EEZD1016W


Explanation: The automation engine encountered apersistent request related to a resource that is now amember of a choice group as defined in the currentlyactive end-to-end policy. The automation engineremoved this request automatically.

System action: The automation engine continues torestore persistent requests.

Operator response: Verify that the related resource hasnot been moved to a choice group within theend-to-end automation policy by mistake.

EEZD1017W The request requestName with priorityrequestPriority by user requestUserid andsource requestSource has been removedbecause the related resourceresourceName is no longer a direct orindirect member of a suspended groupas defined in the currently active policypolicyName .

Explanation: The automation engine encountered apersistent request related to a resource that is no longera direct or indirect member of a suspended group asdefined in the currently active end-to-end policy. Theautomation engine removed this request automatically.


Operator response: Verify that the related resource hasnot been moved to a different group within theend-to-end automation policy by mistake.

EEZD1018W The request requestName with priorityrequestPriority by user requestUserid andsource requestSource has been removedbecause the related resource referenceresourceName references anon-changeable first-level automationresource as defined in the currentlyactive policy policyName .

Explanation: The automation engine encountered apersistent request related to a resource reference thatpoints to a non-changeable first-level automationresource as defined in the currently active end-to-endpolicy.

System action: The automation engine removes therequest automatically.

Operator response: Verify that the related resourcereference has not been modified within the end-to-endautomation policy by mistake.

EEZD1020W The set preferred member request forchoice group choiceGroupName is nolonger valid because the preferredmember preferredMemberName that isspecified in the request is not definedas a member of the choice group in the

currently active policy policyName .

Explanation: The automation engine encountered apersistent set preferred member request that specifiesan invalid resource as the new preferred memberaccording to the currently active end-to-end policy. Theautomation engine removed this request automatically.


Operator response: Verify that the end-to-endautomation policy has not been modified by mistake.

EEZD1021W The request requestName with priorityrequestPriority by user requestUserid andsource requestSource for resourceresourceName has been removed becausethe request is equal to the defaultdesired role as defined in the activeend-to-end automation policy policyName.

Explanation: The automation engine encountered apersistent request that matches the default desired roleof the related resource as defined in the currently activeend-to-end policy.


Operator response: Verify that the related resource hasnot been modified within the end-to-end automationpolicy by mistake.

EEZD1022W The persistent request requestName withpriority requestPriority by userrequestUserid and source requestSource forresource resourceName has been removedbecause an exception occurred whiletrying to restore it after policypolicyName was activated. The exceptiondetails are: exceptionDetails

Explanation: The automation engine encountered anexception while trying to restore a persistent request.


Operator response: Evaluate the exception details.

EEZD1071W A RemoteException was caught whilere-trying to contact automation domainDomain name in order to issue followingreuqests: List of requests. Retry numberis: Retry number.

Explanation: The automation engine was unable tocontact the automation domain to execute commandsthis time. It might have been caused by a temporaryproblem.

EEZD1017W • EEZD1071W


System action: The automation engine will try todeliver the request again.

Operator response: If the targeted automation domaincannot be accessed for a longer period of time checkthe connection properties of this domain in theend-to-end automation manager configuration dialog.

EEZD1072W Unable to deactivate current policy inthe hardware adapter. Originalexception text is: Original Exception text

Explanation: The current policy is a disaster recoverypolicy, but cannot be deactivated in the hardwareadapter.

System action: The disaster recovery policy cannot bedeactivated in the hardware adapter. The automationengine will continue to run without active policy. Nexttime a policy is activated, it will also be activated in thehardware adapter, and overwrite the current policythere.


EEZD1073W Unable to activate policy Name of policyin the hardware adapter. Originalexception text is: Original Exception text

Explanation: The policy to be activated is a disasterrecovery policy, but cannot be activated in thehardware adapter.

System action: The disaster recovery policy cannot beactivated in the hardware adapter. The automationengine will continue to run with this policy, andactivate it in the hardware adapter as soon as it is upand running.


EEZD1074W The first-level automation resourcefirstLevelResourceName matches the twodynamic resource referencesdynamicReferenceName1 anddynamicReferenceName2 .

Explanation: The wildcard patterns of both dynamicresource references match the same first-levelautomation resource. The automation manager does notcreate related instances for the dynamic resourcereferences to avoid conflicting goals for the first-levelautomation resource.

System action: The automation manager does notcreate dynamic resource references for the first-levelautomation resource.

Operator response: Review if the use of wildcardswithin the end-to-end automation policy is correct.

EEZD1075W The first-level automation resourcefirstLevelResourceName matches thedynamic resource referencedynamicReferenceName but the first-levelautomation resource is alreadyreferenced by the static resourcereference staticReferenceName .

Explanation: The wildcard pattern of the dynamicresource reference matches the first-level automationresource, but there exists a static resource referencewhich already references the same first-levelautomation resource. The automation manager does notcreate a related instance for the dynamic resourcereference to avoid conflicting goals for the first-levelautomation resource.

System action: The automation manager does notcreate a dynamic resource reference for the first-levelautomation resource.


EEZD1076W The resource firstLevelResourceNamematches multiple dynamic end-to-endresource references:dynamicResourceReferenceNames .

Explanation: The resource that was added in thefirst-level automation domain matches the patterns ofmultiple dynamic resource references. The automationmanager does not create related instances for thedynamic resource references to avoid conflicting goalsfor the first-level automation resource.

System action: The automation manager does notcreate dynamic resource references for the first-levelautomation resource.


EEZD2001I The automation engine has been startedby a user with ID User ID. Theautomation engine is idling. No policyactivated.

Explanation:

System action:

Operator response:

EEZD2002I The automation engine is shutting downon request by a user with ID User ID.

Explanation:

System action:

Operator response:

EEZD1072W • EEZD2002I


EEZD2003I The automation engine has beenterminated.

Explanation:

System action:

Operator response:

EEZD2004I The automation engine was called torefresh its configuration.

Explanation:

System action:

Operator response:

EEZD2005I The automation engine has been startedas a converter of EIF messages by a userwith ID User ID.

Explanation:

System action:

Operator response:

EEZD2010I The currently active policy Currentlyactive policy name will be deactivatedbefore the new policy New policy namecan be activated.

Explanation: Only one policy can be active at anytime. Therefore the old policy will be deactivated first.

System action: The old policy will be deactivated. Alldefined resource references, groups and relationshipswill be deleted. All requests issued by any operatoragainst any resource reference or group will be deletedas well.

Operator response: If desired, requests will have to beissued again by an operator for the resource referencesand groups defined by the new policy. The same is trueif the currently active policy is re-activated.

EEZD2011I The policy Active policy name has beenactivated by a user with ID User ID .The policy was loaded from the fileActive policy file name .

Explanation: The policy has been activatedsuccessfully.

System action: The policy has been activated. Ifanother policy was active before, all resource stateinformation and all operator requests against theresource defined in the old policy have been deleted.


EEZD2012I The active policy has been deactivatedby a user with ID User ID.

Explanation: The policy has been deactivatedsuccessfully.

System action: The policy has been deactivated.


EEZD2013I The policy Active policy name has beenautomatically activated. The policy wasloaded from the file Active policy filename .

Explanation: The policy has been activatedsuccessfully.

System action: The policy has been activated. Ifanother policy was active before, all resource stateinformation and all operator requests against theresource defined in the old policy have been deleted.


EEZD2020I The automation engine was informedabout a joined automation domainAutomation domain name.

Explanation: The automation domain hosts resourcesthat are referenced by at least one resource reference inthe currently active policy. The automation engine willtry to get the current state information of theseresources.

System action: The automation engine will handle thisdomain join event.


EEZD2021I The automation engine was informedabout a leaving automation domainAutomation domain name.

Explanation: The automation domain hosts resourcesthat are referenced by at least one resource reference inthe currently active policy. The automation engine willupdate the state of these resource referencesaccordingly.

System action: The automation engine will handle thisdomain leave event.


EEZD2022I The automation engine was informedabout a communication state change ofdomain Automation domain name. Thenew communication state is: Newcommunication State name. The oldcommunication state was: Oldcommunication State name.

Explanation: The automation domain hosts resources

EEZD2003I • EEZD2022I


that are referenced by at least one resource reference inthe currently active policy. The automation engine willupdate the state of these resource referencesaccordingly.

System action: The automation engine will handle thiscommunication state change event.


EEZD2023I The automation engine was called tosynchronize itself with the automationdomain Automation domain name.

Explanation: The automation domain hosts resourcesthat are referenced by at least one resource reference inthe currently active policy. The automation engine willverify and update the state of these resource referencesaccordingly.

System action: The automation engine will handle thissynchronization request.


EEZD2024I The automation engine was informedabout a domain state change of domainAutomation domain name. The newdomain state is: Communication Statename.

Explanation: The automation domain hosts resourceswhich are referenced by at least one resource referencein the currently active policy. The automation enginewill handle requests to these resource referencesaccording to the domain state.

System action: Requests will not be sent to a domainwhich is in the OFFLINE state.


EEZD2025I The automation engine was informedabout a policy change on oneautomation domain Automation domainname.

Explanation: The indicated automation domain hostsresources that are referenced by at least one resourcereference in the currently active policy. The automationengine will invalidate the existing observed states ofthese resource references and get the current data bysubscribing to this domain again.

System action: The automation engine will handle thisevent.


EEZD2030I Request: Request Name was issued byUser ID: User Id against Resource Classwith name: Resource Name. Followingcomment was specified: Comment text

Explanation:

System action: The automation engine will handle thisrequest.


EEZD2031I Request was removed by User ID: UserID from Resource Class with name:Resource Name

Explanation:

System action: The automation engine will handle thisremove request.


EEZD2032I Resource New preferred member is the newpreferred member of choice group Choicegroup name.

Explanation:

System action: The automation engine sets thepreferred member.


EEZD2033I A request to suspend the Resource Classwith name: Resource Name fromautomation was received from User ID:User ID. Following comment wasspecified: Comment text

Explanation:

System action: The automation engine will handle thisrequest to suspend the resource.


EEZD2034I A request to resume automation ofResource Class with name: Resource Namewas received from User ID: User ID.

Explanation:

System action: The automation engine will handle thisrequest to resume automation of the resource.


EEZD2035I Accepted disaster recovery requestRequest Name and assigned receipt IDReceiptID to it. Disaster recovery requestsource: Source, user ID: User Id,comment: Comment text.

Explanation: The disaster recovery request was issued,

EEZD2023I • EEZD2035I


passed to the automation engine and successfullychecked and prepared for execution.

System action: The automation engine will handle thisdisaster recovery request.


EEZD2036I Status of disaster recovery request withreceipt ID ReceiptID is NewRequestStatus.

Explanation: The status of the disaster recoveryrequest changed.



EEZD2040I The automation engine was called toinstall the license certificate from file:Certificate file name.

Explanation: A successful installation of the licensecertificate is required in order for the end-to-endautomation engine to run.

System action: The automation engine will handle thisrequest.


EEZD2041I The license certificate is successfullyinstalled.

Explanation: A successful installation of the licensecertificate is required to run the end-to-end automationengine.

System action: Processing continues.


EEZD2050I Request to change the availability targetof Resource Name was issued by User ID:User Id. New target value is:new_availability_target. Followingcomment was specified: Comment text.

Explanation:

System action: The automation engine will handle thisrequest and change the availability target.


Prefix EEZE

EEZE0001E The required discovery library adapterconfiguration property property namecould not be found or its value isundefined.

Explanation: Either the specified configurationproperty cannot be found in the DLA configuration fileor it exists but does not contain a nonempty value.

System action: The discovery library adapter stops. Itdoes not create an IdML discovery book.

Operator response: Use the end-to-end configurationtool to verify that the missing property is set to anonempty value.

EEZE0002E The required discovery library adapterconfiguration property file property filename could not be found.

Explanation: The specified configuration property filecannot be found.


Operator response: Verify the path name of the fileand if the userid that is used to run the DLA has readaccess to the file.

EEZE0003E An IO exception occurred while readingdiscovery library adapter property fileproperty file name .

Explanation: The specified configuration property filecannot be read.


Operator response: Verify that the specified propertiesfile exists and that it is not corrupted. Verify that thesystem has sufficient temp space.

EEZE0004E The system environment variablevariable name is used in a discoverylibrary adapter properties file but notset in the environment.

Explanation: The specified system environmentvariable cannot be resolved.


Operator response: Set the environment variable andstart the DLA again.

EEZE0005E The discovery library adapterencountered an exception: originalexception message

Explanation: The discovery library adapter wasinterrupted by an unexpected exception.


Operator response: Evaluate the message of theoriginal exception.

EEZD2036I • EEZE0005E


EEZE0006E The discovery library adapter stopsbecause the following error occurred:original exception message

Explanation: The discovery library adapter processstops because a non-recoverable error occured.


Operator response: Evaluate the information aboutthe original error supplied with this message. Checkthe message log for error messages preceding thismessage. In case there exists an error message in themessage log before this message, refer to the operatorresponse of the error message.

EEZE0007E An error occurred while trying to writeto the IdML file: original exception message

Explanation: The discovery library adapter wasinterrupted by an unexpected IO exception.


Operator response: Evaluate the message of theoriginal exception. Check if the IdML book directoryexists as specified in the end-to-end automationconfiguration. If it does not exist, create the IdML bookdirectory. Check if the file system has enough freespace and if the user has appropriate write access.

EEZE0008E No naming rule was found for the datamodel class className

Explanation: The discovery library adapterencountered a data model class that is not supportedby the naming rules file.



EEZE0009E No naming rule was found that couldbe satisfied for the resourceinstanceName . Its source class of theresource is sourceClassName . Themapped data model class iscdmClassName .

Explanation: The resource is an instance of a sourceclass that can be mapped to a data model classgenerally. However, the resource does not containsufficient attribute data in order to satisfy any of thenaming rules that exist for the data model class.

System action: This resource is skipped and does notappear in the discovery book. The discovery libraryadapter continues to discover other resources.


EEZE0010E The discovery library adapter stopssince the IdML book directorydirectoryName on server serverName doesnot exist.

Explanation: The specified directory does not exist orcannot be reached.


Operator response: Verify that the specified directoryexists on the specified server. If it exists, verify that theuser has read and write access rights to the directory.In case the server is the local system, the userid that isused to run the discovery library adapter process has tobe considered. In case the server is a remote system,the userid specified in the configuration tool has to beconsidered.

EEZE0011E The discovery library adapter cannotcreate file filename . The original errormessage is: errorMessage

Explanation: The specified file cannot be created.


Operator response: Check if the IdML book directoryexists as specified in the end-to-end automationconfiguration. If it does not exist, create the IdML bookdirectory. Verify that the user has write access rights tothe full directory path.

EEZE0012E In the XML file filename the root elementfoudRootElement was found. However, theexpected root element isexpectedRootElement .

Explanation: The specified XML file cannot beevaluated because its structure does not look likeexpected.


Operator response: Correct the errors in the XML fileand restart the discovery library adapter.

EEZE0013E In the XML file filename the requiredelement requiredElement was not found.

Explanation: The specified XML file cannot beevaluated because its structure does not look likeexpected.


EEZE0006E • EEZE0013E


Operator response: Correct the errors in the XML fileand restart the discovery library adapter.

EEZE0014E Cannot find parent XML nodeparentName for the class className in thenaming rules file.

Explanation: An unexpected type of object wasencountered that is not supported by the naming rulesfile.



EEZE0015E The discovery library adapter does notfind an accessible end-to-endautomation domain.

Explanation: The discovery library adaptersuccessfully connected to the end-to-end automationmanager but there is no end-to-end automation domainaccessible at this time.


Operator response: Check the runtime status of theend-to-end automation engine. If the end-to-endautomation engine is running, review its message logfor errors. Resolve the errors and restart it. Then runthe discovery library adapter again.

EEZE1000W The discovery library adapter stopsbecause its configuration could not beloaded.

Explanation: The discovery library adapter processstops because the configuration initialization failed.


Operator response: Check the message log for errormessages preceding this message. In case there existsan error message in the message log before thismessage, refer to the operator response of the errormessage.

EEZE1001W Cannot find target resource for relationrelationName with source resourcesourceName .

Explanation: A relation has been found but the targetresource of the relation cannot be resolved.

System action: The discovery library adapter processdrops this particular relation and continues to collectdata.

Operator response: Check the message log for error

messages preceding this message. In case there existsan error message in the message log before thismessage, refer to the operator response of the errormessage.

EEZE1002W A relation relationName from sourceresource sourceName to target resourcetargetName has been found, but one ofthe resources cannot be resolved.

Explanation: A relation has been found but the sourceresource or the target resource of the relation cannot beresolved.

System action: The discovery library adapter processdrops this particular relation and continues to collectdata.


EEZE1003W The discovery library adapter cannotfind domain domainName .

Explanation: The domain does not exist in theend-to-end manager. It may have been removed after aperiod of inactivity.

System action: The discovery library adapter ignoresthis domain and continues to collect data from otherdomains.


EEZE2000I The discovery library adapter starts tocreate a discovery book.

Explanation: The discovery library adapter processstarts.

System action: The discovery library adapter processstarts.


EEZE2001I The discovery library adapter hassuccessfully created the discovery book.The discovery took execution timeseconds.

Explanation: The discovery library adapter processstops after having successfully created a discoverybook.

System action: The discovery library adapter processends.

EEZE0014E • EEZE2001I


Operator response: If necessary, load the discoverybook into CMDB.

EEZE2002I The discovery library adapter hasloaded the following configurationproperties: configPropertiesList

Explanation: The discovery library adapter hassuccessfully evaluated the configuration properties file.This message lists the configuration properties thatwere found.

System action: The discovery library adapter processcontinues to discover data and to write a discoverybook according to the values of the configurationproperties.

Operator response: In case of errors, review theconfiguration properties if the values are as expected. Ifnot, use the end-to-end configuration tool in order toadjust the configuration properties values.

Prefix EEZF

EEZF0001E The WebSphere infrastructure hasreported a severe error situation:runtimeExceptionMessage

Explanation: The application was interrupted by aRuntimeException and cannot complete its task.

System action: The current task ends. The transactionis rolled back.

Operator response: Check if the description of theerror situation indicates that the server database oranother subsystem is unavailable.

EEZF0003E A critical error has occurred in class:className, method: methodName. Thelogger object could not be initialized.




EEZF0006E A exception has occurred in class:className, method: methodName. Theconnection to the automation enginecould not be established.

Explanation: The end-to-end automation applicationcould not connect to the automation engine. Thisindicates a network or configuration problem.


Operator response: Check if the automation engineneeds to be started or restarted.

EEZF0007E An error has occurred in class:className, method: methodName. Theconnection to the automation enginecould not be established.

Explanation: The JNDI lookup of the objectrepresenting the automation engine failed and returnednull. This indicates a network or configuration problem.

System action: The current task will not be completed.The system and automation engine remain operational.


EEZF0011E An error has occurred in class:className, method: methodName. Illegalinvocation of this method.

Explanation: This method is required by the J2Cspecification, but it is not implemented in thiscomponent and must not be called by any exploiter.This indicates a programming error or an illegal accessto this component.



EEZF0012E An error has occurred in class:className, method: methodName. Illegalparameter at invocation of this method.




EEZF0014E An error has occurred in class:className, method: methodName. Illegalparameter combination at invocation ofthis method.

Explanation: This method is required by the J2Cspecification, but it is not implemented in thiscomponent and must not be called by any exploiter.This indicates a programming error or an illegal accessto this component.



EEZE2002I • EEZF0014E



EEZF0015E An error has occurred in class:className. The variable 'locale' has notbeen set.

Explanation: This variable is mandatory for executinga request at the automation engine. This indicates aprogramming error on the EJB exploiter side.



EEZF0016E An error has occurred in class:className, method: methodName. Illegalautomation engine operation requested.

Explanation: The J2C architecture tried to execute anoperation on the automation engine that is eitherunknown or not supported. This indicates aprogramming error.



EEZF0017E A exception has occurred in class:className, method: methodName.

Explanation: The method encountered an expectederror during invocation of an operation on theautomation engine backend. This indicates a connectionproblem.



EEZF0019E An error has occurred in class:className, method: methodName. Illegalparameter at invocation of this method.

Explanation: Method createManagedConnection()must not be called with a null ConnectionRequestInfoobject. This is an indication of an internal JCA error.



EEZF0031E A exception has occurred in class:className, method: methodName. Aconnection object could not be allocated.

Explanation: The call to getConnection() returned withan exception. This indicates an internal J2Cprogramming or architectural error.



EEZF0032E An error has occurred in class:className, method: methodName. Aconnection factory object could not beallocated.

Explanation: The ManagedConnectionFactory of thisJ2C encountered an internal error. TheConnectionManager instance was null. This indicatesan internal J2C programming or architectural error.



EEZF0033E Unable to read the end-to-endautomation engine properties filefilePathName . Original exception text is:IOExceptionText

Explanation: The end-to-end automation engineproperties file cannot be read.

System action: The end-to-end automation JEEframework cannot be fully initialized. It does notaccept any requests until the problem is solved.

Operator response: Ensure that the properties fileexists at the location indicated in the message text.Ensure that the WebSphere userid associated with theEEZAsync role has sufficient rights to read theindicated file. For this type of problems, the end-to-endautomation JEE framework refreshes its stateautomatically. In case the file exists in a differentlocation than the location indicated in the message text,open the WebSphere administrative console and adjustthe value of the propertyEEZAutomationEnginePropertiesPath which isassociated to the resource adapter connection factoryEEZDmnManagedConnectionFactory. After havingchanged this property, restart the WebSphereapplication server.

EEZF0034E Unable to find the required propertyEEZAutomationEnginePropertiesPath forthe end-to-end automation engineresource adapter connection factoryEEZDmnManagedConnectionFactory.

EEZF0015E • EEZF0034E


Explanation: The required property has been removedfrom the resource adapter connection factory.

System action: The end-to-end automation JEEframework cannot be fully initialized. It does notaccept any requests until the problem is solved.

Operator response: Open the WebSphereadministrative console and navigate to the resourceadapter connection factoryEEZDmnManagedConnectionFactory. If it does notexist, create the propertyEEZAutomationEnginePropertiesPath. Set its value to${EEZ_CONFIG_ROOT}/cfg/eez.automation.engine.properties (literally as shownhere, but without the quotes). Ensure that theproperties file exists at the specified location, and thatthe userid associated with the EEZAsync role has readaccess to the file. After having created or changed thisproperty, restart the WebSphere application server.

EEZF0035E Unable to read file filePathName .Details: exceptionDetails

Explanation: The file exists but the SystemAutomation end-to-end automation engine connectorcannot read it.


Operator response: Verify that the file accesspermissions are set such that the System Automationend-to-end automation engine connector has readaccess to the file. This includes read access to theparent directories.

EEZF0036E Unable to write file filePathName .Details: exceptionDetails

Explanation: The System Automation end-to-endautomation engine connector cannot write to the file.


Operator response: Verify that the file accesspermissions are set such that the System Automationend-to-end automation engine connector has read andwrite access to the file and its parent directories.

EEZF0037E Unable to create directorydirectoryPathName .

Explanation: The System Automation end-to-endautomation engine connector cannot create thedirectory.


Operator response: Verify that the file accesspermissions are set such that the System Automationend-to-end automation engine connector has read andwrite access to each parent directory that is listed in thedirectory path name.

EEZF0038E Unable to delete file filePathName .

Explanation: The System Automation end-to-endautomation engine connector cannot delete the file.


Operator response: Verify that the file accesspermissions are set such that the System Automationend-to-end automation engine connector has read andwrite access to the file and its parent directories.

EEZF0501W An exception was encountered andignored in order to continue operation.Exception string: exceptionString

Explanation: The invoked method is designed toignore exceptions and continue operation. It logs theexception for problem determination purposes.

System action: Ignores the exception.


EEZF0502W The connection to the automationengine backend failed in class:className, method: methodName.Exception: exception.

Explanation: The application was interrupted by aNameNotFoundException and cannot complete its task.

System action: The system might repeat this operationuntil the automation engine is found.

Operator response: Ensure that the automation engineis up and running.

Prefix EEZG

EEZG0001E The resource identified by the sourcetoken resource source token could not befound.

Explanation: The specified resource cannot be found.


Operator response: Verify the input source token. If itidentifies an existing resource, verify that thecorresponding automation domain is online.

EEZG0002E The policy pool of automation domainDomainName does not contain a policywith filename FileName

Explanation: The specified poliy file cannot be found.


Operator response: Verify the input parameters.

EEZF0035E • EEZG0002E


EEZG0003E The value for automation domain nameDomainName is not valid.

Explanation: Setting the string to the specified value isnot valid.



EEZG0004E The infrastructure has reported anexception: original exception message

Explanation: The application was interrupted by anunexpected exception.



EEZG0005E The supplied automation domain nameis null or empty.

Explanation: An empty domain name is considered asan error.


Operator response: Supply a non-empty inputparameter that identifies an existing automationdomain.

EEZG0006E Unable to initialize the EEZIM webservice SOAP implementation class.Exception details: original exceptionmessage

Explanation: An unexpected exception occurredduring initialization of the web service implementationclass.



EEZG0007E The payload XML stringpayloadXMLString could not be convertedto a credential object.

Explanation: The payload XML is not valid or notsupported.


Operator response: Check the content of the payloadXML string and verify that it corresponds to asupported credential class. If the problem persists,provide the trace file and this message text to the webservice client provider.

EEZG0008E No automation domain could be foundthat matches the given source tokendomain source token . The domain namederived from the source token is domainname .

Explanation: An empty domain name is considered asan error.


Operator response: Supply a non-empty inputparameter that identifies an existing automationdomain.

EEZG0009E The JavaBeans XML decoder was unableto decode an XML string and to buildthe corresponding JavaBean instance.

Explanation: The JavaBeans XML decoder failed.


Operator response: Reproduce the problem with themaximum level of tracing enabled. Provide the tracefile and this message text to the web service clientprovider.

EEZG0010E An unexpected input value wasencountered in class: className, method:methodName, parameter: parameterName,value: parameterValue

Explanation: A method parameter with an unexpectedvalue was encountered.



EEZG0011E Source token could not be parsedsuccessfully. Original message is:errorMessage

Explanation: A source token was encountered thatcould not be parsed successfully.



EEZG1000W An exception was encountered duringXML serialization. Exception details:exceptionDetails

Explanation: This might be subject to back-leveltoleration. In this case, the error can be ignored.

EEZG0003E • EEZG1000W


System action: The exception is ignored. The processwill be continued.


EEZG2001I Policy activation request for policy filename successfully delivered toautomation domain domain name.

Explanation: This message is returned as anacknowledgement that the policy activation requestwas received. It does not mean that the policy hasalready been activated.

System action: The current task completedsuccessfully.

Operator response: No operator resonse needed.

EEZG2002I Policy deactivation request successfullydelivered to automation domain domainname.

Explanation: This message is returned as anacknowledgement that the policy deactivation requestwas received. It does not mean that the policy hasalready been deactivated.



EEZG2003I The request to set the preferred memberhas been successfully delivered toautomation domain domain name

Explanation: This message is returned as anacknowledgement that the invoke request was received.It does not mean that the request has already beensatisfied.



EEZG2004I The connection to the web serviceimplementation has been testedsuccessfully.

Explanation: This message is returned as anacknowledgement that the connection to the webservice implementation has been created and testedsuccessfully.



Prefix EEZH

EEZH0001E Resource not found: key of the missingresource

Explanation: The hardware adapter cannot find thespecified resource.

System action: The request to be executed on theresource is rejected.

Operator response: Correct and reactivate yourautomation policy.

EEZH0002E No disaster recovery policy: name of thepolicy file

Explanation: The policy to be activated for thehardware adapter is no policy for disaster recovery.

System action: The request to activate the policy isrejected.


EEZH0003E Policy file not found: name of the policyfile The original message was: messagetext

Explanation: The hardware adapter cannot find thepolicy file.



EEZH0004E Error in policy file: name of the policy fileThe original message was: message text

Explanation: The plug-in has found an error in theautomation policy. For example, a policy rule wasviolated. Check the message log for details.


Operator response: Analyze the original message.Correct and reactivate your automation policy.

EEZH0010E Unsupported SNMP service processortype and operation service processor typeand operation. Supported SNMP serviceprocessor type and operations are serviceprocessor types.

Explanation: Mechanism SNMP is specified for anunsupported service processor type and operation.


EEZG2001I • EEZH0010E



EEZH0011E The hardware adapter failed to establishan SNMP session with host host andport port. The original message was:message text.

Explanation: The hardware adapter received anexception while establishing an SNMP session.


Operator response: Analyze the original message.Check the log and trace files for more details.

EEZH0012E The hardware adapter received an errorfor an SNMP SET operation on host hostand port port. The original error messagewas: message text.

Explanation: The hardware adapter received an errorwhile executing an SNMP SET operation.



EEZH0013E The hardware adapter encounteredproblems for an SNMP SET operationon host host and port port. Neither anSNMP response nor an SNMP reportwas returned from the SNMP agent. ThePDU the SNMP agent returned was:PDU.

Explanation: The hardware adapter encounteredproblems while executing an SNMP SET operation.


Operator response: Analyze the PDU returned fromthe SNMP agent. Check the log and trace files for moredetails.

EEZH0014E The hardware adapter received an errorreport for an SNMP SET operation onhost host and port port. The error reportindicates a decryption error.

Explanation: The hardware adapter received adecryption error while executing an SNMP SEToperation.


Operator response: Check the log and trace files formore details, and analyze the privacy settings of yourSNMP agent. If the privacy protocol of the SNMP agent

on the box is DES or AES, make sure that you havespecified the correct privacy password for the SNMPuser ID. To do so, run the Hardware adapterconfiguration task of the configuration dialog of SystemAutomation Application Manager. Make sure that theprivacy password required for SNMP access is correctfor the hardware box in table Configured hardwareaccess credentials. After fixing the problem it isrequired to click the Refresh button on the DisasterRecovery tab of the Application Manager Configurationdialog or using the corresponding option in silentconfiguration mode (cfgeezdmn command).

EEZH0015E The hardware adapter received an errorreport for an SNMP SET operation onhost host and port port. The error reportindicates a wrong password.

Explanation: The hardware adapter received an errorreport indicating a wrong password while executing anSNMP SET operation.


Operator response: Check the log and trace files formore details, and analyze the authentication settings ofyour SNMP agent. Make sure that you have specifiedthe correct password for the SNMP user ID. To do so,run the Hardware adapter configuration task of theconfiguration dialog of System Automation ApplicationManager. Make sure that the password required forSNMP access is correct for the hardware box in tableConfigured hardware access credentials. After fixingthe problem it is required to click the Refresh button onthe Disaster Recovery tab of the Application ManagerConfiguration dialog or using the corresponding optionin silent configuration mode (cfgeezdmn command).

EEZH0016E The hardware adapter received an errorreport for an SNMP SET operation onhost host and port port. The error reportindicates an unknown engine ID.

Explanation: The hardware adapter received an errorreport indicating an unknown engine ID whileexecuting an SNMP SET operation.


Operator response: Analyze the SNMP agent. Checkthe log and trace files for more details.

EEZH0017E The hardware adapter received an errorreport for an SNMP SET operation onhost host and port port. The error reportindicates an unknown user name: username.

Explanation: The hardware adapter received an errorreport indicating an unknown user name whileexecuting an SNMP SET operation.

EEZH0011E • EEZH0017E



Operator response: Check the log and trace files formore details, and analyze whether the user name youspecified is defined and valid on the host where theSNMP agent runs. To do so, run the Hardware adapterconfiguration task of the configuration dialog of SystemAutomation Application Manager. Make sure that theuesr ID required for SNMP access is correct for thehardware box in table Configured hardware accesscredentials. After fixing the problem it is required toclick the Refresh button on the Disaster Recovery tab ofthe Application Manager Configuration dialog or usingthe corresponding option in silent configuration mode(cfgeezdmn command).

EEZH0018E The hardware adapter received an errorreport for an SNMP SET operation onhost host and port port. The error reportindicates timing problems.

Explanation: The hardware adapter received an errorreport indicating timing problems while executing anSNMP SET operation.


Operator response: Analyze the connection betweenhardware adapter and SNMP agent. Check the log andtrace files for more details.

EEZH0019E The hardware adapter received an errorreport for an SNMP SET operation onhost host and port port. The error reportindicates an unsupported security levelfor the SNMP agent. The security levelspecified in the disaster recovery policyis as follows. Authentication protocol:authentication protocol, privacy protocol:privacy protocol.

Explanation: The hardware adapter received an errorreport indicating an unsupported security level whileexecuting an SNMP SET operation.


Operator response: Check the log and trace files formore details, and analyze whether the security levelyou specified for the SNMP agent in the disasterrecovery policy matches the actual security level on theSNMP agent. If there are mismatches, either change thesecurity level on the SNMP agent to match yourdisaster recovery policy, or change your disasterrecovery policy to match the security level on theSNMP agent. In the latter case, reactivate yourautomation policy.

EEZH0020E The hardware adapter received an errorreport for an SNMP SET operation onhost host and port port. The originalerror report was: message text.

Explanation: The hardware adapter received an errorreport while executing an SNMP SET operation.


Operator response: Analyze the original report,especially the report PDU returned by the SNMP agent.Check the log and trace files for more details.

EEZH0021E The hardware adapter received an errorreport for an SNMP SET operation onhost host and port port. The originalerror report does not contain any PDU:message text.

Explanation: The hardware adapter received an errorreport while executing an SNMP SET operation.


Operator response: Analyze the original report. Checkthe log and trace files for more details.

EEZH0022E The hardware adapter received asecurity exception while executing scriptcommand script command on hardwaredevice key of the hardware device. Theoriginal message was: message text

Explanation: The hardware adapter received a securityexception while executing a script command.


Operator response: Analyze the original message, andcheck the log and trace files for more details. Checkwhether the definition of the script command in yourautomation policy matches your setup on the systemwhere the System Automation Application Managerruns. Either correct and reactivate your automationpolicy, or modify your setup to match your automationpolicy.

EEZH0023E The hardware adapter received an I/Oexception while executing scriptcommand script command on hardwaredevice key of the hardware device. Theoriginal message was: message text

Explanation: The hardware adapter received an I/Oexception while executing a script command.


Operator response: Analyze the original message, and



check the log and trace files for more details. Checkwhether the definition of the script in your automationpolicy matches your setup on the system where theSystem Automation Application Manager runs. Eithercorrect and reactivate your automation policy, ormodify your setup to match your automation policy.

EEZH0024E The hardware adapter was interruptedwhile executing script command scriptcommand on hardware device key of thehardware device. The original messagewas: message text

Explanation: The hardware adapter was interruptedwhile executing a script command.



EEZH0025E Invalid hardware adapter mainconfiguration file: name of theconfiguration file

Explanation: The hardware adapter mainconfiguration file either cannot be found, or containsinvalid values.

System action: The hardware adapter fails to load thecredentials for the hardware devices.

Operator response: Analyze the hardware adaptermain configuration file, and check the log and tracefiles for more details. Make sure that the hardwareadapter main configuration file exists and can be readby the System Automation Application Managerdaemon user ID.

EEZH0026E The hardware adapter mainconfiguration file name of theconfiguration file does not contain a valuefor property name of the property.

Explanation: The hardware adapter mainconfiguration file does not contain a value for arequired property.

System action: The hardware adapter fails to load thecredentials for the hardware devices.

Operator response: Analyze the hardware adaptermain configuration file, and check the log and tracefiles for more details. Make sure that the hardwareadapter main configuration file exists and can be readby the System Automation Application Managerdaemon user ID.

EEZH0027E The hardware adapter encounteredproblems while reading the hardwareadapter plugin configuration file: nameof the configuration file The originalmessage was: message text

Explanation: The hardware adapter encounteredproblems while reading the hardware adapter pluginconfiguration file.

System action: The hardware adapter cannot load thecredentials for the hardware devices.

Operator response: Analyze the hardware adapterplugin configuration file, and check the log and tracefiles for more details. Make sure that the hardwareadapter plugin configuration file exists and can be readby the System Automation Application Managerdaemon user ID.

EEZH0028E Method not supported: name of theunsupported method

Explanation: The hardware adapter does not supportthe specified method.

System action: The request is rejected.


EEZH0029E EEZHardwareAdapterLogger is notavailable

Explanation: The hardware adapter loggingcomponent has not been initialized.

System action: The hardware adapter stops.


EEZH0030E EEZTecEmitter is not available

Explanation: The hardware adapter internal eventemitter has not been initialized.

System action: The hardware adapter cannot sendevents.


EEZH0031W No credentials are specified in theplugin properties file of the hardwareadapter for SNMP access to hardwarebox boxName .

Explanation: Usually SNMP access is protectedthrough password authentication, and/or encryption.Missing credentials may cause SNMP access to fail.

System action: SNMP access is attempted, but mayfail due to missing credentials.

EEZH0024E • EEZH0031W


Operator response: Run the Hardware adapterconfiguration task of the configuration dialog of SystemAutomation Application Manager. Make sure that thecredentials required for SNMP access are listed for thehardware box in table Configured hardware accesscredentials. User ID and password are required if theauthentication protocol of the SNMP agent on the boxis MD5 or SHA. A privacy password is required if theprivacy protocol of the SNMP agent on the box is DESor AES. After fixing the problem it is required to clickthe Refresh button on the Disaster Recovery tab of theApplication Manager Configuration dialog or using thecorresponding option in silent configuration mode(cfgeezdmn command).

EEZH0032W No credentials are specified in theplugin properties file of the hardwareadapter for script execution on hardwarebox boxName .

Explanation: Usually scripts for managing hardwarerequire user ID and password to authenticate againstthe backend hardware box. Missing credentials maycause script execution to fail.

System action: Script execution is attempted, but mayfail due to missing credentials.

Operator response: Run the Hardware adapterconfiguration task of the configuration dialog of SystemAutomation Application Manager. Make sure that thecredentials required for script execution are listed forthe hardware box in table Configured hardwarecredentials. After fixing the problem it is required toclick the Refresh button on the Disaster Recovery tab ofthe Application Manager Configuration dialog or usingthe corresponding option in silent configuration mode(cfgeezdmn command).

EEZH0033W No credentials are specified in theplugin properties file of the hardwareadapter for script execution on hardwareslot slotName on box boxName .

Explanation: Usually scripts for managing hardwarerequire user ID and password to authenticate againstthe backend hardware slot. Missing credentials maycause script execution to fail.

System action: Script execution is attempted, but mayfail due to missing credentials.

Operator response: Run the Hardware adapterconfiguration task of the configuration dialog of SystemAutomation Application Manager. Make sure that thecredentials required for script execution are listed forthe hardware slot in table Configured hardware accesscredentials. After fixing the problem it is required toclick the Refresh button on the Disaster Recovery tab ofthe Application Manager Configuration dialog or usingthe corresponding option in silent configuration mode(cfgeezdmn command).

EEZH0034E The working directory workingDirectoryfor script execution on hardware slotslotName on box boxName does not exist.

Explanation: The working directory for scriptexecution does not exist. This will cause scriptexecution to fail with an IOException.

System action: Script execution is attempted, but willfail due to a non-existing working directory.

Operator response: Check whether the definition ofthe script in your automation policy matches yoursetup on the system where the System AutomationApplication Manager runs. Either correct and reactivateyour automation policy, or modify your setup to matchyour automation policy.

EEZH0035E The working directory workingDirectoryfor script execution on hardware slotslotName on box boxName cannot be read.

Explanation: The working directory for scriptexecution cannot be read. This will cause scriptexecution to fail with an IOException orSecurityException.

System action: Script execution is attempted, but willfail due to missing access rights on the workingdirectory.

Operator response: Check whether the definition ofthe script in your automation policy matches yoursetup on the system where the System AutomationApplication Manager runs. Either correct and reactivateyour automation policy, or modify your setup to matchyour automation policy.

EEZH0036W Operation operation is not defined forhardware slot slotName on box boxName .

Explanation: Your automation policy does not definethe operation for the hardware device.

System action: When the associated power-off orpower-on commands are issued for the site thehardware slot belongs to, an exception will be raised.The hardware slot must be powered off or on manually.Operation of other hardware slots is not affected by theexception.

Operator response: Check your automation policy forcompleteness, and correct and reactivate it if theomission is not intentional.

EEZH0037I Test of the System AutomationApplication Manager hardware adapterhas started.

Explanation: The System Automation ApplicationManager hardware adapter has been invoked in testmode via the cfgeezdmn configuration utility.

System action: The hardware adapter checks and

EEZH0032W • EEZH0037I


verifies all hardware management tasks defined in yourautomation policy, and the associated credentials youspecified in the configuration dialog of SystemAutomation Application Manager. Warnings and errorsare logged to the message log of System AutomationApplication Manager.


EEZH0038I Test of the System AutomationApplication Manager hardware adapterhas completed.

Explanation: The System Automation ApplicationManager hardware adapter has been invoked in testmode via the cfgeezdmn configuration utility andcompleted successfully.

System action: The hardware adapter has checked andverified all hardware management tasks defined inyour automation policy, and the associated credentialsyou specified in the configuration dialog of SystemAutomation Application Manager. Warnings and errorshave been logged to the message log of SystemAutomation Application Manager.

Operator response: Check the message log of SystemAutomation Application Manager for warnings anderrors, and follow the instructions listed there.IMPORTANT: Only some static aspects of your disasterrecovery setup can be checked. Others, like properauthorization for hardware operations, or successfulscript execution, can be verified only through realfiredrill tests.

EEZH0039E The hardware adapter encounteredproblems while testing SNMP access foroperation operation for hardware slotslotName on box boxName . The originalerror message was: message text.

Explanation: The hardware adapter encounteredproblems while testing SNMP access.

System action: The test to be executed on the resourcefailed.


EEZH0040E The hardware adapter encounteredproblems while testing script access foroperation operation for hardware slotslotName on box boxName . The originalerror message was: message text.

Explanation: The hardware adapter encounteredproblems while testing script access.

System action: The test to be executed on the resourcefailed.


EEZH0041I Script access for operation operation forhardware slot slotName on box boxNamehas been successfully tested. The returncode was: returnCode .

Explanation: The script specified in the disasterrecovery policy was invoked with option -TEST, andcompleted successfully.



EEZH0042I SNMP access for operation operation forhardware slot slotName on box boxNamehas been successfully tested.

Explanation: An SNMP GET has been successfullyexecuted as test for SNMP SET.



EEZH0043E The hardware adapter does not have avalid feature license enrolled for SystemAutomation Application Manager forDistributed Disaster Recovery.

Explanation: The hardware adapter was unable todetect an installed feature license for SystemAutomation Application Manager for DistributedDisaster Recovery on your system.

System action: Without installed feature license keythe hardware adapter will not start.

Operator response: If you plan to use SystemAutomation Application Manager for DistributedDisaster Recovery, order the feature certificate for it,and follow the instructions in the Administrator's andUser's Guide to enable it. If you do not plan to use it,do not try to start the hardware adapter.

EEZH0044I The hardware adapter has been started.

Explanation:

System action:

Operator response:

EEZH0045I The hardware adapter has beenterminated.

Explanation:

System action:

Operator response:

EEZH0038I • EEZH0045I


EEZH0046I The hardware adapter has refreshed itsconfiguration.

Explanation:

System action:

Operator response:

EEZH0047I The disaster recovery policy with nameActive policy name has been activated inthe hardware adapter. The disasterrecovery policy was loaded from the filewith name Active policy file name .

Explanation: The disaster recovery policy has beenactivated successfully in the hardware adapter.

System action: The disaster recovery policy has beenactivated in the hardware adapter. If another policywas active before, all hardware information defined inthe old policy has been deleted.


EEZH0048I The active disaster recovery policy hasbeen deactivated in the hardwareadapter.

Explanation: The disaster recovery policy has beendeactivated successfully in the hardware adapter.

System action: The disaster recovery policy has beendeactivated in the hardware adapter.


EEZH0049I The hardware adapter has successfullyexecuted the following requests: Successlist.

Explanation:

System action: The hardware adapter has successfullyexecuted the requests listed. The list contains for eachrequest the requested operation, and the hardware boxand slot on which the request has been executed.


EEZH0050E The hardware adapter has thrown aremote exception. The original messagewas: message text

Explanation: A connection to the hardware adapterhas been successfully established. The automationadapter frontend has sent a request to the hardwareadapter but the hardware adapter has thrown a remoteexception.


Operator response: Analyze the original message.

EEZH0051E Invocation of hardware adapter failedwith return code=return code

Explanation: The hardware adapter was called toexecute a request on a hardware device. The requestfailed with the indicated return code.

System action: Execution of the request failed.

Operator response: Analyze the return code, andcheck the message and trace logs for more details.

EEZH0052E The hardware adapter command linecannot invoke a request on thehardware adapter. The original messagewas: message text

Explanation: A connection to the hardware adapterhas been successfully established. The hardwareadapter command line has sent a request to thehardware adapter but the hardware adapter has thrownan exception.

System action: The hardware adapter command linefailed.

Operator response: Analyze the original message.

EEZH0053E The hardware adapter script script namefor hardware slot slotName on boxboxName timed out.

Explanation: The hardware adapter issued a script tomanage hardware (e.g. powering off or on a system).The script command timeout exceeded.

System action: The script is considered as failed.

Operator response: Check why the script could notfinish in time. Note that the script could have finishedin the meantime.

EEZH0054E Testing the invocation of operationoperation for hardware slot slotName onbox boxName failed. The return codewas: returnCode .

Explanation: The script specified in the disasterrecovery policy was invoked with option -TEST, andfailed.


Operator response: Analyze the return code, andcheck the message and trace logs for more details.Check if the user credentials are correct.

EEZH0055I Requesting HMC zEnterprise UnifiedResource Manager API version fromhost hostName.

Explanation: A Query API Version HTTP request isbeing sent to the HMC zEnterprise Unified ResourceManager on the identified host in order to verify that



network connectivity to the HMC host is available andthat the zEnterprise Unified Resource Manager APIversion on the HMC host is compatible with theversion of the API supported by this zEnterpriseUnified Resource Manager client.

System action: Continue processing.


EEZH0056I Request for HMC zEnterprise UnifiedResource Manager API version on hosthostName was successful. The HMCname is hmcName. The firmware versionis firmwareVersion. The API version isapiVersion.

Explanation: A Query API Version HTTP request wassent to the HMC zEnterprise Unified Resource Manageron the identified host and a response was received withinformation about the HMC and the zEnterpriseUnified Resource Manager API.



EEZH0057E The HMC zEnterprise Unified ResourceManager API version on host hostNameis incompatible with the version of theAPI supported by this zEnterpriseUnified Resource Manager client. TheHMC zEnterprise Unified ResourceManager API version on host hostNameis hmcAPIVersion. The API versionsupported by this zEnterprise UnifiedResource Manager client isclientSuppAPIVersion.

Explanation: The HMC zEnterprise Unified ResourceManager API version on the identified host isincompatible with the version of the API supported bythis zEnterprise Unified Resource Manager client. ThezEnterprise Unified Resource Manager client mayexperience problems when performing managementtasks for resources managed by the zEnterprise UnifiedResource Manager.

System action: If the zEnterprise hardware adapter isbeing initialized, it fails to initialize. If the zEnterprisehardware adapter configuration is being tested, the testcompletes with an error code.

Operator response: Verify that the configured HMChost information is correct. Also verify that the versionof the HMC zEnterprise Unified Resource Managerclient software is what you expect.

EEZH0058E Request for the HMC zEnterpriseUnified Resource Manager API versionon host hostName failed. Detailed errorinformation is: errorMsg

Explanation: A Query API Version HTTP request was

sent to the HMC zEnterprise Unified Resource Manageron the identified host and the request failed. Thedetailed error information is displayed.

System action: If the zEnterprise hardware adapter isbeing initialized, it fails to initialize. If the zEnterprisehardware adapter configuration is being tested, the testcompletes with an error code.

Operator response: Verify that the configured HMChost information is correct. Examine the detailed errorinformation and determine if there is a problem withthe HMC.

EEZH0059I Logging on to HMC zEnterprise UnifiedResource Manager on host hostNamewith user ID userId.

Explanation: A Logon HTTP request is being sent tothe HMC zEnterprise Unified Resource Manager on theidentified host in order to verify that the identified userID has access.



EEZH0060I Logon HTTP request for user ID userIDto HMC zEnterprise Unified ResourceManager on host hostName wassuccessful.

Explanation: A Logon for the identified user ID wassent in an HTTP request to the HMC zEnterpriseUnified Resource Manager on the identified host inorder to verify that the user ID has access. The logonwas successful.



EEZH0061E Logon HTTP request for user ID userIdto HMC zEnterprise Unified ResourceManager on host hostName failed.Detailed error information is: errorMsg

Explanation: A Logon for the identified user ID wassent in an HTTP request to the HMC zEnterpriseUnified Resource Manager on the identified host andthe request failed. The detailed error information isdisplayed.


Operator response: Examine the detailed errorinformation to identify the reason for the failure. Insurethat the user ID is defined to the HMC zEnterpriseUnified Resource Manager on the identified host andthat it has been given the necessary authorizations.

EEZH0056I • EEZH0061E


EEZH0062I Logging off user ID userID from HMCzEnterprise Unified Resource Manageron host hostName.

Explanation: A Logoff for the identified user is beingsent in an HTTP request to the HMC zEnterpriseUnified Resource Manager on the identified host.



EEZH0063I Logoff for user Id userId sent in HTTPrequest to HMC zEnterprise UnifiedResource Manager on host hostName wassuccessful.

Explanation: A Logoff for the identified user ID wassent in an HTTP request to the HMC zEnterpriseUnified Resource Manager on the identified host and itwas successful.



EEZH0064E Logoff for user Id userId sent in HTTPrequest to HMC zEnterprise UnifiedResource Manager on host hostNamefailed. Detailed error information is:errorMsg

Explanation: A Logoff for the identified user ID wassent in an HTTP request to the HMC zEnterpriseUnified Resource Manager on the identified host andthe request failed. The detailed error information isdisplayed.


Operator response: Examine the detailed errorinformation to identify the reason for the failure.

EEZH0065I Logon and notification subscriptionrequests being sent to the HMCzEnterprise Unified Resource Manageron host hostName with user ID userId.

Explanation: An HTTP request is being sent to theHMC zEnterprise Unified Resource Manager on theidentified host in order to logon the identified user IDand start a session. If the session is started, it is used tosubscribe for notifications.



EEZH0066I Logon and notification subscriptionrequests to HMC zEnterprise UnifiedResource Manager on host hostNamewith user ID userID were successful.

Explanation: The Logon and notification subscription

requests to the HMC zEnterprise Unified ResourceManager on the identified host with the identified userID were successful.



EEZH0068I Test of the System AutomationApplication Manager zEnterprisehardware adapter configuration hasstarted.

Explanation: The System Automation ApplicationManager zEnterprise hardware adapter has beeninvoked in test mode via the cfgeezdmn configurationutility.

System action: The System Automation ApplicationManager zEnterprise hardware adapter verifies that theinformation provided in the configuration dialog forcommunicating with the HMC zEnterprise UnifiedResource Manager is valid. A connectivity test to theHMC is performed by requesting the zEnterpriseUnified Resource Manager API version. The APIversion returned is checked to insure compatibility withthe version of the API supported by the adapter. Thegeneric user ID and password are verified by loggingon to the zEnterprise Unified Resource Manager andthen logging off. The results from these tests are loggedto the message log of the System AutomationApplication Manager.


EEZH0069I Test of the System AutomationApplication Manager zEnterprisehardware adapter configuration hascompleted.

Explanation: The System Automation ApplicationManager zEnterprise hardware adapter has beeninvoked in test mode via the cfgeezdmn configurationutility and the test sequence has completed.

System action: The System Automation ApplicationManager zEnterprise hardware adapter has checkedand verified the information provided in theconfiguration dialog for communicating with the HMCzEnterprise Unified Resource Manager. Messagesshowing the results have been logged to the SystemAutomation Application Manager log.

Operator response: Read the result messages. Correctthe identified errors.



EEZH0070E The System Automation ApplicationManager zEnterprise hardware adapterwas not able to read the automationengine domain identification file,fileName, and cannot get the user ID andpassword it needs to log on to thezEnterprise Universal ResourceManager. The system error message was:errorMsg

Explanation: The System Automation ApplicationManager zEnterprise hardware adapter was beingstarted or refreshed and it was not able to open andread the automation engine domain identification file.The adapter will not be able to communicate with thezEnterprise Universal Resource Manager because it willnot know the user ID and password needed toestablish a session.

System action: If the System Automation ApplicationManager zEnterprise hardware adapter was beingstarted, the start fails. If the System AutomationApplication Manager zEnterprise hardware adapterwas being refreshed, the refresh fails and the adaptercontinues to run with the configuration settings it wasrunning with. Messages showing the results have beenlogged to the System Automation Application Managerlog.

Operator response: Make sure that the automationengine domain identification file identified in thismessage exists and can be read by the SystemAutomation Application Manager functional user ID.

EEZH0071E The System Automation ApplicationManager zEnterprise hardware adapterwas not able to find credentials fordomain domainName in the automationengine domain identification filefileName and cannot log on to thezEnterprise Universal ResourceManager.

Explanation: The System Automation ApplicationManager zEnterprise hardware adapter was beingstarted or refreshed and it was not able to findcredentials for its domain in the automation enginedomain identification file. The adapter will not be ableto communicate with the zEnterprise UniversalResource Manager because it will not know the user IDand password needed to establish a session.

System action: If the System Automation ApplicationManager zEnterprise hardware adapter was beingstarted, the start fails. If the System AutomationApplication Manager zEnterprise hardware adapterwas being refreshed, the refresh fails and the adaptercontinues to run with the configuration settings it wasrunning with. Messages showing the results have beenlogged to the System Automation Application Managerlog.

Operator response: Make sure that the automation

engine domain identification file identified in thismessage exists and can be read by the SystemAutomation Application Manager functional user ID.

EEZH0072E The System Automation ApplicationManager zEnterprise hardware adapteris unable to start because the inputcontext has an invalid value ofdomainName for the domain name.

Explanation: The System Automation ApplicationManager zEnterprise hardware adapter is unable toobtain its domain name from its input context andcannot start.

System action: The System Automation AutomationManager zEnterprise hardware adapter logs an errorand fails to start.

Operator response: Make sure that the SystemAutomation Application Manager zEnterprise hardwareadapter configuration file exists and can be read by theSystem Automation Application Manager functionaluser ID.

EEZH0073E The System Automation ApplicationManager zEnterprise hardware adapterfor domain domainName is unable tostart because the input context has aninvalid value of propertyValue forproperty propertyKeyName.

Explanation: The System Automation ApplicationManager zEnterprise hardware adapter for theidentified domain is unable to start because the inputcontext has the identified invalid value for theidentified property.

System action: The System Automation ApplicationManager zEnterprise hardware adapter fails to startand logs the error.

Operator response: Make sure that the SystemAutomation Application Manager zEnterprise hardwareadapter configuration file exists and can be read by theSystem Automation Application Manager functionaluser ID.

EEZH0074I The System Automation ApplicationManager zEnterprise hardware adapterfor domain domainName is being startedand the input context has an invalidvalue of propertyValue for propertypropertyKeyName. A default value ofdefaultPropertyValue will be used.

Explanation: The System Automation ApplicationManager zEnterprise hardware adapter for theidentified domain is being started and the input contexthas the identified invalid value for the identifiedproperty. The default value identified is being used tostart the adapter.

EEZH0070E • EEZH0074I


System action: The System Automation ApplicationManager zEnterprise hardware adapter is started withthe identified default value for the identified property.

Operator response: Make sure that the SystemAutomation Application Manager zEnterprise hardwareadapter configuration file exists and can be read by theSystem Automation Application Manager functionaluser ID. If the default value used for the identifiedproperty is a problem for your environment you willneed to restart the adapter after correcting the problem.

EEZH0075E The System Automation ApplicationManager zEnterprise hardware adapterfor domain domainName failed to startbecause it was not able to connect to theHMC zEnterprise Unified ResourceManager at host hostName.

Explanation: The System Automation ApplicationManager zEnterprise hardware adapter for theidentified domain has failed to start because it wasunable to connect to the HMC zEnterprise UnifiedResource Manager at the identified host.

System action: The System Automation ApplicationManager zEnterprise hardware adapter fails to start.

Operator response: Verify that the host nameconfigured for the zEnterprise hardware adapter for theidentified domain is correct. If the configured hostname is correct, verify that the HMC zEnterpriseUnified Resource Manager is running and that thenetwork connecting the adapter to the HMC isavailable.

EEZH0076E The System Automation ApplicationManager zEnterprise hardware adapterfor domain domainName failed to startbecause it was not able to either logonto or start receiving notifications fromthe HMC zEnterprise Unified ResourceManager at host hostName as useruserName. Detailed error information is:errorMsg

Explanation: The System Automation ApplicationManager zEnterprise hardware adapter for theidentified domain has failed to start because it wasunable to logon to or start receiving notifications fromthe HMC zEnterprise Unified Resource Manager at theidentified host as the identified user.


Operator response: Look at the detailed errorinformation in this message for the failure reason.Verify that the identified user has been given the accessrequired to logon to and receive notifications from theHMC zEnterprise Unified Resource Manager on theidentified host.

EEZH0077E The System Automation ApplicationManager zEnterprise hardware adapterfor domain domainName is being startedand has obtained an invalid value ofpropertyValue for system propertypropertyName.

Explanation: The System Automation ApplicationManager zEnterprise hardware adapter for theidentified domain is being started and has obtained theidentified invalid value for the identified systemproperty.


Operator response: Make sure that the SystemAutomation Application Manager hardware adapterstart script, eezhwadapter.sh, defines the identifiedproperty.

EEZH0078E The System Automation ApplicationManager zEnterprise hardware adapterfor domain domainName failed to startbecause the HMC zEnterprise UnifiedResource Manager API version on hosthostName is incompatible with theversion of the API supported by theSystem Automation ApplicationManager. The HMC zEnterprise UnifiedResource Manager API version on hosthostName is hmcAPIVersion. The APIversion supported by the SystemAutomation Application Manager isclientSuppAPIVersion.

Explanation: The System Automation ApplicationManager zEnterprise hardware adapter for theidentified domain has failed to start because the HMCzEnterprise Unified Resource Manager API version atthe identified host is incompatible with the version ofthe API supported by the System AutomationApplication Manager.


Operator response: Verify that the configured HMChost information is correct. Also verify that the versionof the System Automation Application Manager is whatyou expect.

EEZH0079E The System Automation ApplicationManager zEnterprise hardware adapterfor domain domainName failed to startbecause it was not able to get the virtualserver inventory from the HMCzEnterprise Unified Resource Managerat host hostName as user userName.Detailed error information is: errorMsg

Explanation: The System Automation ApplicationManager zEnterprise hardware adapter for the



identified domain has failed to start because it wasunable to get the virtual server inventory from theHMC zEnterprise Unified Resource Manager at theidentified host as the identified user.


Operator response: Look at the detailed errorinformation in this message for the failure reason.Verify that the identified user has been given the accessrequired to request the virtual server inventory fromthe HMC zEnterprise Unified Resource Manager on theidentified host. Also verify that the identified user hasbeen given the access required to get the virtual serverinformation for all System Automation ApplicationManager nodes.

EEZH0080E HTTP reqName request for URI: urifailed. The request was sent by useruserId. HTTP status was statusCode:statusMsg.

Explanation: The identified HTTP request with theidentified URI was sent to the zEnterprise UnifiedResource Manager for the identified user and it failed.The HTTP status code and its associated message aredisplayed.

System action: Log error and continue.

Operator response: Read the HTTP status code andmessage. If the identified URI was not found, verify thefollowing: 1) The zEnterprise Unified ResourceManager is running and accessible on your network. 2)The configured host information for the zEnterpriseUnified Resource Manager is correct. 3) The identifieduser is defined to the zEnterprise Unified ResourceManager and has the necessary access to managezEnterprise objects.

EEZH0081E HTTP reqName request for URI: urifailed. The request was sent by useruserId. HTTP status was statusCode:statusMsg. zEnterprise Unified ResourceManager reason was uRsMgrReason:uRsMgrReasonMsg.

Explanation: The identified HTTP request with theidentified URI was sent to the zEnterprise UnifiedResource Manager for the identified user and it failed.The HTTP status code and its associated message aredisplayed. The zEnterprise Unified Resource Managerreason code and its associated message are displayed.


Operator response: Read the HTTP and zEnterpriseUnified Resource Manager status codes and messages.If the identified URI was not found, verify thefollowing: 1) The zEnterprise Unified ResourceManager is running and accessible on your network. 2)The configured host information for the zEnterpriseUnified Resource Manager is correct. 3) The identified

user is defined to the zEnterprise Unified ResourceManager and has the necessary access to managezEnterprise objects.

EEZH0082E HTTP reqName request for URI: urifailed. The request was sent by useruserId. HTTP status was statusCode:statusMsg. zEnterprise Unified ResourceManager error information received wasin unexpected format and could not beread. The detailed error informationwas: exceptionMsg.

Explanation: The identified HTTP request with theidentified URI was sent to the zEnterprise UnifiedResource Manager for the identified user and it failed.The HTTP status code and its associated message aredisplayed. The zEnterprise Unified Resource Managererror information received could not be read and theexception message generated when trying to read theinformation is displayed.


Operator response: Read the HTTP status code andmessage. If the identified URI was not found, verify thefollowing: 1) The zEnterprise Unified ResourceManager is running and accessible on your network. 2)The configured host information for the zEnterpriseUnified Resource Manager is correct. 3) The identifieduser is defined to the zEnterprise Unified ResourceManager and has the necessary access to managezEnterprise objects.

EEZH0083E HTTP reqName request for URI: urifailed. HTTP status was statusCode:statusMsg.

Explanation: The identified HTTP request with theidentified URI was sent to the zEnterprise UnifiedResource Manager and it failed. The HTTP status codeand its associated message are displayed.


Operator response: Read the HTTP status code andmessage. If the identified URI was not found, verify thefollowing: 1) The zEnterprise Unified ResourceManager is running and accessible on your network. 2)The configured host information for the zEnterpriseUnified Resource Manager is correct.

EEZH0084E HTTP reqName request for URI: urifailed. The HTTP status was statusCode:statusMsg. The zEnterprise UnifiedResource Manager reason wasuRsMgrReason: uRsMgrReasonMsg.

Explanation: The identified HTTP request with theidentified URI was sent to the zEnterprise UnifiedResource Manager and it failed. The HTTP status codeand its associated message are displayed. ThezEnterprise Unified Resource Manager reason code and



its associated message are displayed.


Operator response: Read the HTTP and zEnterpriseUnified Resource Manager status codes and messages.If the identified URI was not found, verify thefollowing: 1) The zEnterprise Unified ResourceManager is running and accessible on your network. 2)The configured host information for the zEnterpriseUnified Resource Manager is correct.

EEZH0085E HTTP reqName request for URI: urifailed. The HTTP status was statusCode:statusMsg. The zEnterprise UnifiedResource Manager error informationreceived was in unexpected format andcould not be read. The detailed errorinformation was: exceptionMsg.

Explanation: The identified HTTP request with theidentified URI was sent to the zEnterprise UnifiedResource Manager and it failed. The HTTP status codeand its associated message are displayed. ThezEnterprise Unified Resource Manager errorinformation received could not be read and theexception message generated when trying to read theinformation is displayed.


Operator response: Read the HTTP status code andmessage. If the identified URI was not found, verify thefollowing: 1) The zEnterprise Unified ResourceManager is running and accessible on your network. 2)The configured host information for the zEnterpriseUnified Resource Manager is correct.

EEZH0086E HTTP reqName request for URI: urifailed due to an HTTP client runtimeexception. The exception message was:exceptionMsg

Explanation: An attempt to send the identified HTTPrequest with the identified URI to the zEnterpriseUnified Resource Manager was made and it failedbecause the HTTP client threw an exception. The HTTPclient exception message is displayed.


Operator response: Read the HTTP client exceptionmessage to determine if the problem is caused by anerror in the configuration information for thezEnterprise Unified Resource Manager.

EEZH0087E HTTP reqName request for URI: urifailed due to an unexpected exception.The exception message was: exceptionMsg

Explanation: An attempt to send the identified HTTPrequest with the identified URI to the zEnterpriseUnified Resource Manager was made and it failedbecause an unexpected exception was thrown.


Operator response: Read the exception message todetermine if the problem is caused by an error in theconfiguration information for the zEnterprise UnifiedResource Manager.

EEZH0088E HTTP reqName request for URI: urifailed due to an HTTP client runtimeexception. The request was sent by useruserId. The exception message was:exceptionMsg

Explanation: An attempt to send the identified HTTPrequest with the identified URI to the zEnterpriseUnified Resource Manager was made and it failedbecause the HTTP client threw an exception. The usersending the request is identified and the HTTP clientexception message is displayed.


Operator response: Read the HTTP client exceptionmessage to determine if the problem is caused by anerror in the configuration information for thezEnterprise Unified Resource Manager.

EEZH0089E HTTP reqName request for URI: urifailed due to an unexpected exception.The request was sent by user userId. Theexception message was: exceptionMsg

Explanation: An attempt to send the identified HTTPrequest with the identified URI to the zEnterpriseUnified Resource Manager was made and it failedbecause an unexpected exception was thrown. The usersending the request is identified and the HTTP clientexception message is displayed.


Operator response: Read the exception message todetermine if the problem is caused by an error in theconfiguration information for the zEnterprise UnifiedResource Manager.

EEZH0090E No credentials were provided withmethodName invocation of zEnterprisehardware adapter.

Explanation: The System Automation ApplicationManager zEnterprise hardware adapter is configured torequire credentials and the identified methodinvocation did not provide any.

System action: The invoked method logs the errorand exits by throwing an exception. Processingcontinues.




EEZH0091E Request to receive notifications from theHMC zEnterprise Unified ResourceManager on host hostName failed.Detailed error information is: errorMsg

Explanation: A request to subscribe to notificationsfrom the HMC zEnterprise Unified Resource Manageron the identified host failed to complete successfully.The detailed error information is displayed.


Operator response: Verify that the configured HMChost information is correct. Examine the detailed errorinformation and determine if there is a problem withthe HMC.

EEZH0092E An internal error has occurred. Location:location.

Explanation: An internal error has occurred. Thelocation where the internal error was detected isdisplayed.



EEZH0093E The System Automation ApplicationManager zEnterprise hardware adaptermethod, methodName, was invoked withuser name, userName, and it does notmatch the configured functional username, functionalUserName.

Explanation: A System Automation ManagerzEnterprise hardware adapter method that must usethe configured functional user name has been invokedwith a user name that does not match it. Or, thehardware adapter is configured to use the configuredfunctional user for all functions and the identifiedmethod has been invoked with a user name that doesnot match it.

System action: The invoked method logs the errorand exits by throwing an exception. Processingcontinues.

Operator response: The functional user name is savedin the automation engine domain identification filewhich is read by the zEnterprise hardware adapter andthe Application Manager. If the file is changed andboth components are not refreshed, the hardwareadapter may not be able to perform function requests.Make sure that the zEnterprise hardware adapter isusing the same version of the file as the ApplicationManager.

EEZH0094I Requesting inventory of virtual serversfrom the HMC zEnterprise UnifiedResource Manager on host hostNamewith user ID userId.

Explanation: An HTTP request is being sent to theHMC zEnterprise Unified Resource Manager on theidentified host using the identified user ID in order toget the inventory of virtual servers.



EEZH0095I Inventory of virtual servers wassuccessfully received from the HMCzEnterprise Unified Resource Manageron host hostName with user ID userID.

Explanation: An HTTP request to get the virtualserver inventory from the HMC zEnterprise UnifiedResource Manager on the identified host using theidentified user ID completed successfully.



EEZH0096E Discovered a new zEnterprise virtualserver with hostname hostName. and URInewURI. A zEnterprise virtual serverwith URI priorURI already was matchedto the System Automation node withthis hostname.

Explanation: System Automation Application Managerrequires that At most one zEnterprise virtual server hasthe same hostname as a System Automation node. TheSystem Automation Application Manager zEnterprisehardware adapter received a notification from the HMCzEnterprise Unified Resource Manager. This notificationidentified a zEnterprise virtual server that matched thehostname for a System Automation node.

System action: The System Automation ApplicationManager zEnterprise hardware adapter emits an eventindicating that the new zEnterprise virtual server isassociated with the System Automation node.Processing continues.

Operator response: Ensure that the zEnterprise virtualservers that are managed by System Automation haveunique hostnames.

EEZH0097I The node with hostname hostname wasrequested to be shutdown. A commandto shutdown the node will be submittedto zEnterprise HMC. The followingcomment was specified by user user:comment.

Explanation:

System action:

EEZH0091E • EEZH0097I


Operator response:

EEZH0098I The node with hostname hostname wasrequested to be started. A command tostartup the node will be submitted tozEnterprise HMC. The followingcomment was specified by user user:comment.

Explanation:

System action:

Operator response:

Prefix EEZI

EEZI0001E The WebSphere infrastructure hasreported a severe error situation:runtimeExceptionMessage.



Operator response: Check the description of the errorsituation if it indicates that the server database oranother subsystem is unavailable.

EEZI0003E A critical error has occurred in class:className, method: methodName. Unableto initialize Logger.

Explanation: No Logger object could be initializedand accessed.

System action: The process cannot be completed. Allparts of this component are affected


EEZI0005E Failing Logger initialization in: variabletext, in class: className. Information:someInfo

Explanation: Critical error. No logger object could beobtained. The entire application might be affected.

System action: Method terminates with aConfigurationFailedException.

Operator response: Ensure the correct classpathconfiguration.

EEZI0012E Internal error. Null parameter passed inmethod: methodName, in class: className.

Explanation: Method getConnection() must not becalled with null parameters. This is an indication of aprogramming error on the EJB exploiter side.

System action: Method terminates with anIllegalArgumentException.

Operator response: Invoke getConnection() with afully initialized EEZFLAConnectionSpec object as avalid parameter.

EEZI0013E Internal error. Illegal parameter passedin method: methodName, in class:className.

Explanation: The EEZFLAConnectionSpec parametercontained an uninitialized EEZFLAConfigData memberobject.


Operator response: Invoke getConnection() with afully initialized EEZFLAConnectionSpec object as avalid parameter.

EEZI0014E Illegal invocation of method:methodName, in class: className.

Explanation: Method invoke() must not be called withthis parameter combination. It is not supported.

System action: Method terminates with anIllegalOperationException.

Operator response: Invoke invoke() with thesignature(InteractionSpec, Record) as a valid parametercombination.

EEZI0015E Critical error in class: className, method:methodName. A connection to theAdapter could not be established.

Explanation: The call toEEZAdapterConnection.open(..) returned value 0.

System action: The method terminates with aConnectionFailedException.

Operator response: See the WebSphere andautomation adapter logs if they contain further detailsabout this error situation.

EEZI0016E Critical error in class: className, method:methodName. UnknownAdapterException return code in variabletext.

Explanation: The operation has terminated with anAdapterException, but the internal return code isunknown.

System action: The method terminates with aExecutionFailedException.


EEZH0098I • EEZI0016E


EEZI0017E Critical error in class: className, method:methodName. The operation could not beperformed because of exception.

Explanation: An exception other than a subtype ofEEZApplicationException occurred during interactionwith the backend.

System action: The method terminates with aExecutionFailedException.



Explanation: The EEZFLAConnectionRequestInfoparameter contained an uninitializedEEZFLAConfigData member object.



EEZI0019E Internal error. Illegal invocation ofmethod: methodName, in class: className.

Explanation: Method createConnection() must not becalled without parameters. This is an indication of aninternal JCA error.


Operator response: Invoke createConnection() with afully initialized ConnectionManager object as a validparameter.

EEZI0021E Security violation detected for anend-to-end automation adapter at IPaddress ipAddress and port numberportNumber . Using SSL is required forall first-level automation adapters butnot enabled for this particular adapter.

Explanation: According to the SSL configuration ofthe end-to-end automation manager, it is required touse SSL for the connections to all first-level automationadapters. However, this particular adapter is notconfigured to communicate via SSL.


Operator response: If all communication between theend-to-end automation manager and the first-levelautomation adapters should use SSL, then ensure thatthe failing first-level automation adapter is properlyconfigured to use SSL. If it should be allowed that the

end-to-end automation manager and fist-levelautomation adapters do not use SSL, then use theend-to-end automation manager configuration dialogand change the property that enforces SSL connectivity.After having saved the change in the end-to-endautomation manager configuration dialog, restart theWebSphere Application Server.

EEZI0022E Security violation detected in class:className, method: methodName. The SSLconfiguration file could not be found.

Explanation: The connection factory of this J2Cconnector requires SSL-secure connections, but the filecontaining the necessary properties could not be found.

System action: The method terminates with aConfigurationException.

Operator response: Check the custom properties ofthe EEZFLAConnectionFactory and ensure that the SSLconfiguration file exists at the correct location.

EEZI0023E Security violation detected in class:className, method: methodName. The SSLconfiguration file could not be opened.

Explanation: The ConnectionFactory of this JCArequires SSL-secure connections, but the file containingthe necessary properties could not be opened and read.


Operator response: Ensure the properties file is notcorrupt and has the appropriate read access rights.

EEZI0031E Connector exception detected in class:className, method: methodName. Thecontent is: exceptionDetails. A Connectionobject could not be allocated.

Explanation: The call to getConnection() returned withan exception that is not attributable to an internalapplication exception.

System action: The method terminates with aResourceException.

Operator response: See the WebSphere logs for furtherdetails about this error situation.

EEZI0032E Connector exception detected in class:className, method: methodName. AConnectionFactory object could not beallocated.

Explanation: The ManagedConnectionFactory of thisJCA encountered an internal error. TheConnectionManager instance was null.


EEZI0017E • EEZI0032E


Operator response: Ensure the properties file is notcorrupt and has the appropriate read access rights.


Explanation: The parameter passed to this object wasnot initialized.


Operator response: Invoke this method with a fullyinitialized object as a valid parameter.

EEZI0042E Internal error. Illegal call to methodmethodName, in class className.

Explanation: This method is specified and required bythe J2C specification, but must not be called this way.



EEZI0044E Critical error in methodName, in classclassName. SSL problem. Propertyproperty is null.

Explanation: The SSL properties file could not be readcorrectly. One or more properties do not exist or areincorrect.

System action: The J2C Connector will fail to load andnot be operational.

Operator response: Make sure all settings in the SSLproperties file are correct and restart the server.

EEZI0046E Critical error in methodName, in classclassName. SSL problem.

Explanation: An SSL connection could not beestablished. One reason might be corrupt or incorrectSSL files.


Operator response: Make sure all settings in the SSLproperties file are correct and that all SSL files are inthe correct location and not corrupted.

EEZI0047E A 'JMSSecurityException' was caughtwhile trying to contact the JMS queueof the end-to-end automation manager.



Operator response: Check the correct configurationfor WAS Access User ID and Pasword. Restart theautomation engine.

EEZI0048E An exception was caught while trying tocontact the JMS queue of the end-to-endautomation manager.



Operator response: Check the correct configurationfor WAS Access User ID and Password. Restart theautomation engine.

EEZI0049E Rejected the requestName request againstthe resource resourceName in domaindomainName .

Explanation: The resource does not support thisrequest.




Explanation: The resource is currently in a state thatdoes not support this request.


Operator response: Bring the resource into a statewhere the request is supported and issue the requestagain.


Explanation: The resource addressed in the request isnot existing in the domain.


Operator response: Check the resource key of therequest.



EEZI0052E Rejected the SetRole request withrequested role requestedRole against theresource resourceName in domaindomainName .

Explanation: The resource does not support the rolespecified in the request.


Operator response: Specify a role in the SetRolerequest that is supported by the resource.

EEZI0053E Unable to access the replication domaindomainName which is associated with theTPC-R server serverAddress on port port .Original message text is: original messagetext

Explanation: The connection to the specified TPC-Rserver could not be established. The correspondingreplication domain is not accessible.

System action: The operation is not processed.

Operator response: Use the end-to-end automationmanager configuration dialog to ensure that the serverand port for the TPC-R domain are correct and refreshthe configuration if it needs to be modified. If theconfiguration is correct, verify that the TPC-R server isrunning.

EEZI0054E Unable to authenticate with thereplication domain domainName which isassociated with the TPC-R serverserverAddress on port port . Originalmessage text is: Security Exception text

Explanation: While trying to establish a connectionwith the TPC-R server, it was detected that the usercredentials specified in the TPC-R configuration are notvalid.

System action: The system will no longer try to accessthe TPC-R server until the configuration is refreshed.

Operator response: Use the end-to-end automationmanager configuration dialog to ensure that the usercredentials in the configuration of the TPC-R domaincontains the correct user ID and a valid password toaccess the indicated TPC-R server and refresh theTPC-R server by using the end-to-end automationmanager configuration dialog refresh functionality.

EEZI0055E Operation operation name caused aproblem on TPC-R server serverAddresson port port . associated with domaindomain name Original message text is:exception text

Explanation: An internal error has occured.



EEZI0056E The TPC-R server associated with thereplication domain domainName runningon serverAddress : port . is not asupported version to be connected withSystem Automation ApplicationManager. Original message text is:original message text

Explanation: While trying to connect to the TPC-Rserver it was detected that this version of the TPC-Rserver is not supported by System AutomationApplication Manager.


Operator response: Install a supported version ofTPC-R.

EEZI0057E There was a timeout while trying toaccess the replication domaindomainName which is associated with theTPC-R server serverAddress on port port .Original message text is: original messagetext

Explanation: The operation timed out.


Operator response: Verify that the TPC-R server isrunning.

EEZI0058E Operation operation name timed out onTPC-R server serverAddress on port port .



Operator response: Verify that the TPC-R server isrunning and accessible. If it is not accessible, restart theTPC-R server.

EEZI0059E Unable to connect to the replicationdomain domainName while trying tosubmit the command command for thesession session . The replication domainis associated with the TPC-R serverserverAddress on port port . Originalmessage text is: original message text

Explanation: No connection is established to thisTPC-R server, the command is not submitted.

System action: The operation is not processed.

Operator response: Use the end-to-end automationmanager configuration dialog to ensure that the serverand port for the TPC-R domain are correct and refreshthe configuration if it needs to be modified. If the



configuration is correct, verify that the TPC-R server isrunning.

EEZI0060E Submitting the command command forthe session session on replication domaindomainName timed out. The replicationdomain is associated with the TPC-Rserver serverAddress on port port .Original message text is: original messagetext



Operator response: Verify that the TPC-R server isrunning.

EEZI0061E Authentication with the replicationdomain domainName is no longer valid.The replication domain is associatedwith the TPC-R server serverAddress onport port .

Explanation: While periodically checking theconnection to the TPC-R server, it was detected that theauthentication is no longer valid.


Operator response: Use the end-to-end automationmanager configuration dialog to ensure that the usercredentials in the configuration of the TPC-R domaincontains the correct user ID and a valid password toaccess the indicated TPC-R server and refresh theTPC-R server by using the end-to-end automationmanager configuration dialog refresh functionality.

EEZI0062E At least one of the TPC-R serversdefined in the end-to-end automationmanager configuration dialog isaccessible, but none of the servers isdeclared as 'ACTIVE'. TPC-R server one:tpcrServerOne, TPC-R server two:tpcrServerTwo. The servers are associatedwith the replication domain domainName

Explanation: While trying to connect to the TPC-Rserver it was detected that no TPC-R server is declared'ACTIVE'.

System action: The replication domain will remain inan Offline state until one of the TPC-R servers willbecome 'ACTIVE'.

Operator response: Ensure that both TPC-R serversare running. Declare one of the servers as 'ACTIVE' inTPC-R.

EEZI0063E The TPC-R server(s) defined in theend-to-end automation managerconfiguration dialog are not compatibleto the the current System AutomationApplication Manager release. TPC-Rserver version is: tpcrServerOne.

Explanation: System Automation Application Managercontains a TPC-R interface code that is not able tocommunicate successfully with this TPC-R version.


Operator response: Refer to the System AutomationApplication Manager Release Notes® to determinewhich Application Manager service level is compatiblewith the TPC-R server version.

EEZI0064E The TPC-R server(s) defined in theend-to-end automation managerconfiguration dialog are not on theminimum level required for interactionwith the current System AutomationApplication Manager release. For the 3.4TPC-R product stream, TPC-R version3.4.1.8 is required, for the 4.1 productstream, TPC-R 4.1.1.1 is required.

Explanation: System Automation Application Managercontains a TPC-R interface code that is not able tocommunicate successfully with this TPC-R version.


Operator response: Upgrade your TPC-R server to afixpack level that is supported. Refer to the SystemAutomation Application Manager Release Notes forfurther information.

EEZI0501W An exception was encountered andignored in order to continue operation.Exception string: exceptionString




EEZI0502W Both defined TPC-R servers are declaredas 'ACTIVE'. The servers are no longersynchronized. TPC-R server one:tpcrServerOne, TPC-R server two:tpcrServerTwo. The servers are associatedwith the replication domain domainName

Explanation: Both TPC-R servers are declard as'ACTIVE' in TPC-R.

System action: The server defined as TPC-R server

EEZI0060E • EEZI0502W


one will be use for further communication.

Operator response: Ensure that you configured thecorrect TPC-R server pair using the end-to-endautomation manager configuration dialog. If theconfiguration is correct, set one of these servers as astandby server in TPC-R.

EEZI0503W TPC-R server two is defined in theend-to-end automation managerconfiguration dialog, but it is notaccessible. The ability to takeover to theTPC-R server two is no longer given.TPC-R server one: tpcrServerOne, TPC-Rserver two: tpcrServerTwo. The servers areassociated with the replication domaindomainName

Explanation: TPC-R server two is defined, but notaccessible.

System action: TPC-R server one will be used forfurther communication.

Operator response: Ensure that TPC-R server two isrunning. Reconnect the servers using TPC-R if theyhave been disconnected.

EEZI0504W TPC-R server one is not accessible.TPC-R server two is accessible anddeclared as 'ACTIVE'. The ability totakeover to the TPC-R server one is nolonger given. TPC-R server one:tpcrServerOne, TPC-R server two:tpcrServerTwo. The servers are associatedwith the replication domain domainName.

Explanation: TPC-R server is not accessible.

System action: TPC-R server two will be use forfurther communication.

Operator response: Ensure that TPC-R server one isrunning. Reconnect the servers using TPC-R if theyhave been disconnected.

EEZI0545W Possible error in methodName, in classclassName. SSL problem. Propertyproperty equals null.

Explanation: The SSL properties file could not be readcorrectly. One or more properties do not exist or areincorrect.

System action: The J2C Connector will start, but willonly be operational for non-SSL operations.

Operator response: Make sure all settings in the SSLproperties file are correct, and restart the server if SSLoperations are desired.

EEZI2001I Request: Request Name was issued byUser ID: User Id against Resource Classwith name: Resource Name. Followingcomment was specified: Comment text

Explanation:

System action: The replication domain will handlethis request.


EEZI2002I SetRole request with requested role:Requested Role was issued by User ID:User Id against Resource Class with name:Resource Name. Following comment wasspecified: Comment text

Explanation:

System action: The replication domain will handlethis request.


EEZI2003I The configured TPC-R servers forreplication domain domainName are bothaccessible and run in a validACTIVE/STANDBY setup. TPC-R serverone (activeStandby): tpcrServerOne, TPC-Rserver two (activeStandby): tpcrServerTwo.

Explanation:

System action: The system will communicate with theserver declared as ACTIVE.


EEZI2004I The configured TPC-R servertpcrServerOne for the replication domaindomainName is accessible and declared asACTIVE.

Explanation:

System action: The system will communicate with theconfigured TPC-R server.


Prefix EEZJ

EEZJ0001E The WebSphere infrastructure hasreported a severe error situation:RuntimeException message



Operator response: Check the description of the errorsituation if it indicates that the server database or

EEZI0503W • EEZJ0001E


another subsystem is unavailable. If the problempersists, check IBM Electronic Support for additionalinformation - http://www.ibm.com/support/entry/portal/.

EEZJ0002E The WebSphere infrastructure hasreported an error situation: Exceptionmessage

Explanation: The application was interrupted by anunexpected exception or error that is not aRuntimeException.

System action: The current task ends, but the databaseoperations that have been performed already remainvalid (no transaction rollback).

Operator response: Check IBM Electronic Support foradditional information - http://www.ibm.com/support/entry/portal/.

EEZJ0003E Operation operationName encountered aFinderException because automationdomain domainName is unknown in thescope of the management server. Theoperation continues processing of theother automation domains.

Explanation: Possible causes of the problem are: 1)The automation domain name was incorrect. 2) Theautomation domain has been deleted in the meantime.

System action: The operation task ends as far as theindicated automation domain is concerned. Theoperation continues processing of the other automationdomains.

Operator response: Refresh the list of existingautomation domains and verify that the domain nameis contained in the list of existing domains. If not, andif the domain still exists and participates in automation,then restart the end-to-end automation adapter for thisdomain.

EEZJ0004E Expected a nonempty list of input databut received none in class: className,method: methodName, parameter:parameterName

Explanation: A null or empty list parameter wasencountered. This is an indication of a programmingerror on the EJB client side.

System action: The server method ends withoutprocessing the request.


EEZJ0005E Expected nonempty input but receivedno input in class: className, method:methodName, parameter: parameterName

Explanation: A parameter with a null value wasencountered. This is an indication of a programmingerror on the EJB client side.



EEZJ0006E Domain type domainType of automationdomain domainName is unknown.

Explanation: The domain type of an automationdomain is unknown.



EEZJ0007E Within the list of resource requests, arequest was encountered that contains anull or empty automation domain name.

Explanation: One of the requests within the parameterlist contains a null or empty automation domain name.

System action: All requests in the list are ignored.


EEZJ0008E System Automation ApplicationManager is unable to publish an eventto JMS topic topicName. The topicconnection factory istopicConnectionFactoryName. Thefollowing exception was encountered:exceptionDetails

Explanation: An invocation of the WebSphereApplication Server's JMS service failed.

System action: System Automation ApplicationManager failed to publish a message to the topic. Thismay result in a loss of event data.

Operator response: Evaluate the exception details andretry the operation. Restart the WebSphere applicationserver.

EEZJ0002E • EEZJ0008E


EEZJ0009E Within the list of resource requests forautomation domain firstDomainName, arequest was encountered for automationdomain differentDomainName

Explanation: Request lists must contain requestsagainst a single automation domain only. The requestlist that causes the problem contains requests againstmultiple automation domains.

System action: All requests in the list are ignored.

Operator response: Select only resources that arecontained by a single automation domain, and retry theoperation.

EEZJ0010E The EEZDomainNameList parameterreceived in class: className, method:methodName contains an element that isnot a string.

Explanation: An incorrect parameter value wasdetected. This is an indication of a programming erroron the EJB client side.

System action: The method ends but the sessioncontinues to exist.


EEZJ0011E The subscription method methodName inclass className was called before thesubscriber id was set in the session.

Explanation: Before a subscribe or unsubscribemethod can be called, the subscriber id must be setwithin the session. This is an indication of aprogramming error on the EJB client side.

System action: The method ends but the sessioncontinues to exist.

Operator response: Restart the application that failedand retry the operation.

EEZJ0013E Subscriber subscriberId was unable tounsubscribe from some resources indomain domainName because theautomation domain is not accessible atthis time.

Explanation: The automation domain is currently notaccessible, so the unsubscribe request could not beforwarded to the domain. However, the subscriptioncleanup within the management server was successful.Appropriate cleanup mechanisms in the domain (atdomain adapter startup, for example) will take care ofthe orphaned subscription at the domain level.

System action: The unsubscribe operation continues tounsubscribe from resources that reside within otherautomation domains.

Operator response: Determine why the automationdomain is not accessible at this time. If necessary,restart the end-to-end automation adapter for thatdomain in order to trigger resynchronization. If thedomain has left, no further action is required.

EEZJ0014E Subscriber subscriberId was unable tounsubscribe from all resources inautomation domain domainName becausethe domain is not accessible at this time.

Explanation: The automation domain is currently notaccessible, so the unsubscribe request could not beforwarded to the domain. However, the subscriptioncleanup within the management server was successful.Appropriate cleanup mechanisms in the domain (atdomain adapter startup, for example) will take care ofthe orphaned subscription at the domain level.

System action: The unsubscribe operation continues tounsubscribe from all resources that the subscriber hassubscribed to previously and that reside withindomains other than the failing one.

Operator response: Determine why the automationdomain is not accessible at this time. If necessary,restart the end-to-end automation adapter for thatdomain in order to trigger resynchronization. If thedomain has left, no further action is required.

EEZJ0015E An attempt to invoke operationmethodName within automation domaindomainName has been detected. The typeof this domain does not support therequested operation.

Explanation: A caller tried to invoke an operation thatis not supported.

System action: The operation request is ignored.

Operator response: Restart the application that failedand retry the operation.

EEZJ0016E Unable to create an initial context.

Explanation: The JNDI naming directory is notaccessible, and the attempt to create an initial contextfailed.


Operator response: Restart the application that loggedthis message. If this does not solve the problem, restartthe WebSphere Application Server that provides theruntime environment for the automation manager.

EEZJ0017E Looking up object jndiLookupName inJNDI failed.

Explanation: Possible causes of the problem are: 1)The JNDI naming directory is not accessible. 2) Theobject was not bound to the JNDI correctly.




Operator response: Restart the WebSphere ApplicationServer that provides the runtime environment for theautomation manager.

EEZJ0018E Automation domain domainName doesnot exist.

Explanation: Possible causes of the problem are: 1) Aninvalid automation domain name was supplied. 2) Theautomation domain has been deleted in the meantime.


Operator response: Check if the automation adapterthat corresponds to the automation domain is running.Restart the automation adapter and verify that theautomation domain is listed in the operations consoleor the command shell.

EEZJ0019E Automation domain domainName is notaccessible at this time.

Explanation: The automation domain exists, but it iscurrently not possible to communicate with it.


Operator response: Make sure that the automationdomain is running. If it is a first-level automationdomain, verify that the automation adapter is running.Retry the operation after the timeout period defined bythe environment variable com.ibm.eez.aab.watchdog-interval-seconds. If the problem persists, restart theautomation adapter (in case of a first-level automationdomain) or the end-to-end automation engine (in caseof an end-to-end automation domain).

EEZJ0020E Automation domain domainName seemsto be not accessible at this time.Invocation of method methodName failedwith a RemoteException.



Operator response: Make sure that the automationdomain is running. If it is a first-level automationdomain, verify that the automation adapter is running.Retry the operation after the timeout period defined bythe environment variable com.ibm.eez.aab.watchdog-interval-seconds. If the problem persists, restart theautomation adapter (in case of a first-level automationdomain) or the end-to-end automation engine (in caseof an end-to-end automation domain).

EEZJ0021E Automation domain domainName cannotbe accessed because of a problem withinthe JEE framework.

Explanation: An attempt to create a session failedwithin the JEE framework.



EEZJ0022E An unrecoverable error occurred duringstartup of application productName. Theapplication stops. Details about theerror: exceptionDetails.

Explanation: An exception was encountered.



EEZJ0023E An attempt to activate policy policyNamein automation domain domainNameresulted in an error which indicates thatthe policy is invalid.

Explanation: The automation domain indicates that anerror was detected while processing the specifiedautomation policy.


Operator response: Verify the correctness of theautomation policy, and activate it again.

EEZJ0024E An attempt to activate policy policyNamein automation domain domainNameresulted in an error which indicates thatthe policy cannot be found.

Explanation: The automation domain indicates thatthe specified automation policy cannot be found in thefile system.


Operator response: Verify that the automation policyfile exists and contains a valid policy, and activate itagain.

EEZJ0025E The operation setPreferredMember hasended since the automation domainname specified by the choice group key:choiceGroupDomainName did not matchthe domain name specified by thepreferred member key:preferredMemberDomainName

Explanation: The resource keys that were provided do



not point to the same automation domain. It isnecessary, however, that the choice group and itsmembers reside within the same domain.



EEZJ0026E Operation operation name is notsupported by class class name.

Explanation: A caller tried to invoke an operation thatis not supported.



EEZJ0029E An attempt to publish an event wasstopped since there is an activetransaction. Event automation domainname is domainName and event reason iseventReason.

Explanation: The application does not supportsending of JMS messages within a transactionalboundary.



EEZJ0030E The end-to-end automation manager isnot fully initialized and refuses toaccept requests. The followingsubcomponents are not yet initialized:listOfMissingComponents

Explanation: The EEZEAR application is eitherstarting or stopping. During these periods, no methodrequests are accepted.


Operator response: If the EEZEAR application isstarting, retry the request. If the EEZEAR application isstopping, restart the application and retry the request.If the problem persists, review the System Automationdocumentation for specific information about thesubcomponents that are included in this message.

EEZJ0031E Refused to invoke operation methodNameon end-to-end automation domaindomainName because the user iduserIdName is not in theEEZEndToEndAccess role.

Explanation: The target of this operation is an

end-to-end automation domain. This operation may beinvoked against end-to-end automation domains onlyby operators that are in the EEZEndToEndAccess role.

System action: The operation request is ignored.

Operator response: If the operator is not allowed toinvoke operations against end-to-end resources, noaction is required. If the operator should be allowed toinvoke operations against end-to-end resources, theoperator's userid or a user group that contains theoperator's userid has to be added to roleEEZEndToEndAccess.

EEZJ0032E Within the list of resource keys forautomation domain firstDomainName, aresource key was encountered forautomation domain differentDomainName

Explanation: In the context of this operation, eachelement of the list of resource keys must point to thesame automation domain. This condition is notsatisfied.


Operator response: Select only resources that arecontained by a single automation domain, and retry theoperation.

EEZJ0033E Automation domain domainNamerequires user authentication.

Explanation: The automation domain requires thatauthentication information be supplied for each task.The authentication information consists of a userid anda password. The failing task did not supply thatinformation.


Operator response: Case 1: If user authenticationchecking is enabled in the automation domain, ensurethat user credential information for the automationdomain is supplied. If the failing task was invokedfrom the System Automation operations console, usethe Log In task to enter the credential. If the failing taskwas invoked from the end-to-end automation engine,ensure that the user credentials in the configuration ofthe automation engine are correct. If you modified thecredentials refresh the automation engine using theRefresh function of the configuration utility (cfgeezdmncommand). Case 2: If user authentication checking hasbeen disabled in the automation domain, restart theadapter for that automation domain.

EEZJ0034E You are not authorized to perform theoperation.

Explanation: The authorization failed while accessingthe end-to-end automation manager.

System action: The requested operation is cancelled.



Operator response: Ensure that the permissions anduser roles defined in the WebSphere Application Serverare set up correctly. If the problem persists, contactyour system administrator.

EEZJ0035E You are not authorized to perform theoperation. error details.

Explanation: The authorization failed while accessingthe end-to-end automation manager.


Operator response: Ensure that the permissions anduser roles defined in the WebSphere Application Serverare set up correctly. If the problem persists, contactyour system administrator.

EEZJ0036E A WebSphere user transaction with anunexpected status was encounteredwhile operation operationName wasprocessed. The expected status isexpectedStatus but the actual status isactualStatus.

Explanation: In the process of using a WebSphere usertransaction, an unexpected transaction state wasencountered.


Operator response: Retry the operation. If theproblem persists, restart the WebSphere ApplicationServer.

EEZJ0037E No end-to-end automation domain isaccessible at this time.

Explanation: Either no end-to-end automation domainexists at all, or it exists but it is currently not accessible.


Operator response: Make sure that an end-to-endautomation automation domain is running. If theproblem persists, restart the end-to-end automationengine.

EEZJ0038E An event has been successfullypublished to the subscriberssuccessfulSubscriberIdList. However, eventpublishing failed for at least onesubscriber: failureDetailsPerSubscriberId

Explanation: Publishing an event has failed for at leastone event subscriber.


Operator response: Evaluate the message, whichcontains failure details for each subscriber the eventcould not be published to. Check if just before thismessage, other messages appear that may provideadditional information on how to solve the problem.

EEZJ0039E Sending events to OMNIbus is currentlydisabled since an earlier attempt todeliver an event has failed. Theend-to-end JEE framework regularlytries to send an event and enablessending events again as soon as theretry operation succeeds.

Explanation: Publishing an event to OMNIbus hasfailed before. In order to avoid that failing attempts tosend events block the event sender for a long timeperiod, sending end-to-end automation events toOMNIbus is currently disabled. The JEE frameworkperiodically tries to send an event to OMNIbus in orderto check if it is available again.


Operator response: Check if OMNIbus is available.Use the end-to-end automation manager configurationtool to check if the event server hostname and port areset to the correct values.

EEZJ0040E Sending events to GDPS is currentlydisabled since an earlier attempt todeliver an event to GDPS failed. Theend-to-end JEE framework regularlytries to send an event and enablessending events to GDPS again as soonas the retry operation succeeds.

Explanation: Publishing an event to GDPS has failedbefore. In order to avoid that failing attempts to sendevents to GDPS block the event sender for a long timeperiod, sending end-to-end automation events to GDPSis currently disabled. The JEE framework periodicallytries to send an event to GDPS in order to check if it isavailable again.


Operator response: Check if GDPS is available. Usethe end-to-end automation manager configuration toolto check if the GDPS server hostname and port are setto the correct values.

EEZJ0041E The requests which should be stored inthe automation database are based ondifferent resource keys. The firstresource key is firstResourceKey . Theother resource key is otherResourceKey .

Explanation: The administrative interface allowsstoring requests that are based on one single resourcekey only. In order to store requests related to multipleresource keys, the administrative interface has to beinvoked multiple times.

System action: The current task ends. The requestshave not been stored in the automation database.




EEZJ0042E The requests which should be stored inthe automation database cannot beserialized into a string with maximumlength maxLength. Even after allcomment strings have been removed,there are still numberOfExtraCharacterscharacters beyond the maximum length.

Explanation: The database column that is designed tostore a serialized form of the requests accepts serializedstrings up to the size defined by the maximum lengthvalue. But even after all superfluous information hasbeen removed from the requests, the serialized string istoo long.



EEZJ0043E The request property name propertyNameis not supported.

Explanation: The automation JEE framework accepts aspecific list of request property names only.

System action: The current task ends. The request hasnot been stored in the automation database.


EEZJ0044E The request property propertyName doesnot support the value propertyValue

Explanation: For some request property names thereis a specified set of supported values.

System action: The current task ends. The request hasnot been stored in the automation database.


EEZJ0045E The request property list containsduplicate property names:propertyNameList

Explanation: Duplicate property names within requestproperty lists are not supported.



EEZJ0046E The request properties which should bestored in the automation databasecannot be serialized into a string withmaximum length maxLength. There arenumberOfExtraCharacters charactersbeyond the maximum length.

Explanation: The database column that is designed tostore a serialized form of the request properties acceptsserialized strings up to the size defined by themaximum length value.



EEZJ0047E The request list contains a request oftype vote.

Explanation: Only regular requests are applicable forbeing stored in the automation database. Votes areindirect consequences of regular requests. They areautomatically restored when the corresponding regularrequest is restored.



EEZJ0048E The automation JEE frameworkencountered the unknown WebSphereApplication Server propertypropertyName .

Explanation: This property is not supported by theautomation JEE framework.



EEZJ0049E The list of requests passed to classclassName and method methodNamecontains mismatching requests:requestListWithError

Explanation: A request list that contains restartrequests and other requests was encountered. This is anindication of a programming error on the client side.

System action: The automation manager ignores therequest list.

Operator response: Collect the traces of theautomation JEE framework.



EEZJ0050E One or multiple restart requests areissued to resources that cannot berestarted at this time:listOfResourceNamesWithAssociatedErrorReasons

Explanation: The restart requests are invalid.

System action: The automation manager ignores theinvalid requests and processes the valid requests.

Operator response: Resolve the problems indicated inthe message text. Retry the operation.

EEZJ0051E A restart request by userName failed forresource resourceId . The followingexception was encountered while tryingto stop the resource: errorReason

Explanation: The restart was interrupted because theautomation domain returned an exception during thestop request.

System action: Terminates the restart cycle of theresource.

Operator response: Review the exception details.Resolve the problem and issue the restart request again.

EEZJ0052E A restart request by userName failed forresource resourceId after durationSecondsseconds. The following exception wasencountered while trying to start theresource: errorReason

Explanation: The restart was interrupted because theautomation domain returned an exception during thestart request.


Operator response: Review the exception details.Resolve the problem and issue the restart request again.

EEZJ0053E A restart request by userName failed forresource resourceId after durationSecondsseconds. The state of the restart cycle ispreviousState . The reason code is:errorReason .

Explanation: The restart cycle was interrupted by anevent.


Operator response: Check the status of the affectedresource. If needed issue a new request.

EEZJ0054E A restart request to resource resourceIdalready exists.

Explanation: A resource that is currently restartingcannot be restarted.

System action: Rejects the restart request.

Operator response: Wait until the previous restartrequest finishes. If needed, cancel the previous requestand issue a new restart request.

EEZJ0055E The end-to-end automation JEEframework cannot contact the databasemanager. Details about the exception:ExceptionDetails

Explanation: A connection to the database managercould not get established or an existing connection gotdisconnected.


Operator response: Ensure that the database manageris running. Verify the configuration of the data sourcethat is used by the automation JEE framework. If theproblem persists, restart the automation JEEframework.

EEZJ0056E The operation operationName is notsupported as a synchronous request.

Explanation: Only the operations Online, Offline,Restart, CancelRequest, Suspend, Resume, and SetRoleare supported as synchronous requests.


Operator response: Do not specify the operation as asynchronous request.

EEZJ0057E The timeout value timeoutValue is toosmall. The timeout value must be atleast equal to pollIntervalValue .

Explanation: The timeout value must be at least equalto the polling interval length. The polling intervallength is defined by the JVM propertycom.ibm.eez.aab.monitor-interval-seconds. Default: 5,minimum: 2, maximum: 60 seconds.


Operator response: Adjust the timeout value for therequest. If needed, set or modify the propertycom.ibm.eez.aab.monitor-interval-seconds.

EEZJ0058E Unable to retrieve the current status ofresource resourceId . Monitoring ofrequest requestName ends.

Explanation: The request has been issued successfullybut now the resource cannot be found any more.



Therefore it is no longer possible to monitor its state.


Operator response: Check if the resource has beenremoved in the meantime.

EEZJ0059E The request requestName for resourceresourceId did not finish within thespecified timeout of timeout seconds.

Explanation: The request has been issued successfully.The resource did not reach the expected state withinthe specified timeout interval.

System action: The synchronous monitoring of theresource ends. The resource might reach the expectedstate later.

Operator response: Increase the timeout value forfuture requests against this resource.

EEZJ0060E The request requestName for resourceresourceId has been forwarded to theautomation domain but the response isempty.

Explanation: The request has been issued without anexception but the automation domain did not returnthe updated request data.

System action: The synchronous monitoring of theresource ends. The resource might reach the expectedstate later.

Operator response: Check the status of the resource. Ifneeded, issue the request again.

EEZJ0061E An authentication exception occurredwhile looking up the JNDI namejndiName: exceptionDetails

Explanation: The client program uses invalid usercredentials to access the Java Naming and DirectoryInterface (JNDI).


Operator response: Ensure that the JNDI client usesvalid credentials. For example if the JNDI client is theend-to-end automation engine or the end-to-endautomation manager configuration tool then verify thatthe System Automation Application Manager functionaluser credentials are valid.

EEZJ0062E The resource resourceName cannot bestored because it is not a node resource.Its resource type is resourceType .

Explanation: Only node resources can be stored by theoperation.

System action: The current task ends. The resourcedoes not get stored.


EEZJ0063E SA Application Manager has not yetreceived an event from automationdomain domainName . The automationJEE framework does not allow access tothat domain because the event pathfrom the automation domain to the SAApplication Manager is not yetestablished. The end-to-end automationmanagement host of the automationdomain is managementHostName .

Explanation: After the automation JEE framework hasbeen restarted it is required to receive an event fromeach automation domain. This ensures that theautomation adapter has acknowledged the connectionto this SA Application Manager. The automationadapter might not be configured correctly to sendevents to this SA Application Manager. In a DR setup,the adapter might be sending events to the SAApplication Manager instance on the other site, or itmight have a version that does not support a siteswitch of the SA Application Manager. If the value ofthe end-to-end automation management host isundefined this is a strong indication that theautomation adapter version does not yet support a siteswitch.

System action: Access to the automation domain isrejected until an event is received from the respectiveautomation adapter, except for viewing the domain logfile. If the automation JEE framework does not receivean event within the domain removal timeout (asdefined by com.ibm.eez.aab.domain-removal-hours),the automation domain will be removed from the scopeof this SA Application Manager.

Operator response: Check if the automation adapterhas been configured for the correct SA ApplicationManager IP address and port. Check the adapter log. Ifyou have a DR setup with an System AutomationApplication Manager at each site, ensure that theSystem Automation Application Manager at the othersite is offline. Refer to the System AutomationApplication Manager documentation for the minimumrequired automation adapter version. Upgrade theautomation adapter and configure it for SystemAutomation Application Manager toggle.

EEZJ0064E The policy directory name directoryNamecontains a path separator character.

Explanation: The policy directory name must be arelative directory name. The system appends thisdirectory name to the snippets subdirectory within theend-to-end automation policy pool directory. Thesystem does not support further nesting ofsubdirectories.




Operator response: Specify a relative directory namewithout any path separator characters.

EEZJ0065E The policy file name fileName contains apath separator character.

Explanation: The policy file name must be a relativefile name.


Operator response: Specify a policy file name withoutany path separator characters.

EEZJ0066E The policy file name fileName does notend with .xml.

Explanation: The policy file name must end with .xml.


Operator response: Specify a valid XML policy filename suffix.

EEZJ0067E Event publishing failed for at least onesubscriber: failureDetailsPerSubscriberId

Explanation: Publishing an event has failed for at leastone event subscriber.


Operator response: Evaluate the message, whichcontains failure details for each subscriber the eventcould not be published to. Check if just before thismessage, other messages appear that may provideadditional information on how to solve the problem.

EEZJ0068E User wasUserName could not beauthenticated in first-level automationdomain automationDomainName using thefirst-level automation domain userautomationUserName . The originalmessage is: originalMessageText

Explanation: The automation domain requires userauthentication, but no valid user credential has beensupplied with the request.


Operator response: Case 1: If user authenticationchecking is enabled in the automation domain, ensurethat user credential information for the automationdomain is supplied. If the failing task was invokedfrom the System Automation operations console, theoperations console asks for a new valid user credential.Enter the new credential directly and store it to theDomain Credential store, or navigate to Settings -Stored Domain Credentials and edit the credentials asneeded. If the failing task was invoked from theend-to-end automation manager (either automationengine or automation JEE framework within

WebSphere Application Server), ensure that a usercredential for the first-level automation domain iscorrectly defined in the configuration of the automationengine. After you modified the credentials refresh theautomation engine using the Refresh function of theconfiguration utility (cfgeezdmn command). Case 2: Ifuser authentication checking has been disabled in theautomation domain, restart the adapter for thatautomation domain.

EEZJ0069E Creating the EIF event publisher basedon the configuration filepublisherConfigurationFile failed withexception exceptionDetails

Explanation: The EIF event publisher could not becreated.


Operator response: Review the details of theexception. Use the end-to-end automation managerconfiguration tool to modify EIF event publisherproperties.

EEZJ0070E The EIF event publisher configurationfile publisherConfigurationFile for EIFevent target eifTargetName does not exist.

Explanation: The EIF event publisher cannot becreated since the required configuration file cannot befound in the file system.


Operator response: Verify the EIF event publisherconfiguration file path.

EEZJ0071E The EIF event publisher configurationfile publisherConfigurationFile for EIFevent target eifTargetName cannot beread.

Explanation: The EIF event publisher configurationfile exists but the automation JEE framework cannotread the file.


Operator response: Verify the file access permissionsof the EIF event publisher configuration file.

EEZJ0072E Reading the EIF event publisherconfiguration filepublisherConfigurationFile for EIF eventtarget eifTargetName failed with exceptionexceptionDetails

Explanation: The EIF event publisher configurationfile exists but the automation JEE framework cannotread the file.




Operator response: Review the details of theexception. Use an editor to verify that the file isreadable. Use the end-to-end automation managerconfiguration tool to modify the content of theconfiguration file.

EEZJ0073E The publisher for EIF event targeteifTargetName failed to send an eventwith reason eventReason and messageeventMessage

Explanation: The EIF event publisher methodsendEvent returned error codeTECAgent.SEND_FAILURE.

System action: The current task ends. In order toavoid that failing attempts to send events block theevent sender for a long time period, sendingend-to-end automation events to the EIF event target isdisabled. The JEE framework periodically tries to sendan event to the EIF event target in order to check if it isavailable again.

Operator response: Check if the EIF event target isavailable. Use the end-to-end automation managerconfiguration tool to check if the event target hostnameand port are set to the correct values.

EEZJ0074E The publisher for EIF event targeteifTargetName with exceptionexceptionDetails

Explanation: The EIF event publisher failed to sendthe event.


Operator response: Check if the EIF event target isavailable.

EEZJ0075E The publisher for EIF event targeteifTargetName failed to send an eventwith reason eventReason and messageeventMessage within timeoutSecondsseconds.

Explanation: The EIF event publisher methodsendEvent did not complete within the expected time.

System action: The current task ends. In order toavoid that failing attempts to send events block theevent sender for a long time period, sendingend-to-end automation events to the EIF event target isdisabled. The JEE framework periodically tries to sendan event to the EIF event target in order to check if it isavailable again.

Operator response: Check if the EIF event target isavailable. Use the end-to-end automation managerconfiguration tool to check if the event target hostnameand port are set to the correct values.

EEZJ0076E The functional user userName can notaccess the automation domaindomainName because of the security issuesecurityExceptionMessage .

Explanation: A security problem occurred whileaccessing the domain with the first-level automationdomain credentials that are stored for the functionaluser.

System action: The system blocks all attempts of thefunctional user to retrieve data from the first-levelautomation domain until the security issue is cleared.

Operator response: Open the end-to-end automationconfiguration tool and verify the credentials for thefunctional user and this first-level automation domain.Save the changes and refresh the end-to-endautomation configuration. Review the adapterconfiguration for the affected first-level automationdomain. For example, verify that the appropriatePluggable Authentication Module (PAM) service isdefined. Restart the automation adapter after havingchanged the adapter configuration.

EEZJ0100E The processing of an event resulted inan exception: exceptionDetails

Explanation: The EventHandlerBean received anexception when processing an event.



EEZJ0101E Cannot create or use a connection to thefirst-level automation domaindomainName. Details about the exception:exceptionDetails.

Explanation: The EventHandlerBean received anexception when processing an AdapterJoin event. Itwas not able to create or use a connection to afirst-level automation domain.

System action: The processing of the AdapterJoinevent ends.

Operator response: Resolve the problem that isdescribed in the original exception.

EEZJ0102E Not able to add a subdomain to thedomain domainName. Details about theexception: exception.

Explanation: The EventHandlerBean tried to locatethis automation domain, but it received an exception.Therefore it is not able to add a subdomain to thisautomation domain.

System action: The current task ends but eventprocessing continues.




EEZJ0103E Encountered a FinderException for thedomain domainName.

Explanation: The EventHandlerBean tried to locatethis automation domain, but it received aFinderException, because the automation domain isunknown in the scope of the end-to-end automationmanagement server.



EEZJ0104E Received an exception related to atransaction when processing an event ofdomain domainName. Details about theexception: exception.

Explanation: The transaction that was started whenprocessing an event resulted in an exception.



EEZJ0105E Not able to communicate withautomation domain domainName. Detailsabout the exception: exception.

Explanation: The EventHandlerBean received adomain join event of an automation domain, but it wasnot able to communicate with this automation domain.An exception was thrown instead.

System action: The processing of the domain joinevent ends.


EEZJ0106E Received a CreateException trying tocreate a domain for the domain namedomainName.

Explanation: The EventHandlerBean received aCreateException while trying to create an automationdomain object.



EEZJ0107E Forwarding an event to the end-to-endautomation domain domainName failed.Details about the exception: exception.

Explanation: The EventHandlerBean tried to forwardan event to the automation engine. This operationfailed.

System action: The current task ends. But the eventprocessing continues.


EEZJ0108E Activating policy policyName failed.Details about the exception: exception

Explanation: The EventHandlerBean tried to activatean end-to-end automation policy on an automationengine. This operation failed.


Operator response: Try to activate the policy using theoperations console.

EEZJ0109E Resynchronizing the end-to-endautomation domain domainName failed.Details about the exception: exception.

Explanation: The EventHandlerBean tried toresynchronize the automation engine. This operationfailed.



EEZJ0110E FinderException received while trying tofind subscriptions for entity entityName.

Explanation: The EventHandlerBean tried to findsubscriptions for this entity, but it received aFinderException.



EEZJ0111E CreateException received while trying tocreate a connection to the end-to-endautomation domain domainName.

Explanation: The EventHandlerBean received aCreateException while trying to create a connection tothe automation engine.





EEZJ0112E RemoteException received whencommunicating with the end-to-endautomation domain domainName.

Explanation: The EventHandlerBean received aRemoteException when it called a function of theautomation engine.



EEZJ0113E Calling checkHealth returned a nullobject for domain domainName.

Explanation: The EventHandlerBean received a nullobject when calling checkHealth for an automationdomain that just sent a domain join event. The domainjoin processing failed for this automation domain.



EEZJ0114E The domain object returned bycheckHealth has a different domainname than the according domain joinevent. The event domain name isdomainName.

Explanation: The EventHandlerBean received anincorrect object from checkHealth. The domain joinprocessing failed for this automation domain.



EEZJ0115E Exception received while trying topublish an event. Details about theexception: exception details.

Explanation: The EventHandlerBean received anexception when it tried to publish an event.



EEZJ0116E Exception received while trying to createthe SSL session to connect to the OSLCregistry. Details about the exception:exception details.

Explanation: While trying to setup a secureconnection to the OSLC registry, an error occurredwhich prevented the successful creation of theconnection.

System action: Automation engine continues to work,but OSLC registration is aborted.

Operator response: Use the exceptions details tocorrect the configuration for OSLC registration.Re-activate the automation policy to trigger a newOSLC registration action.

EEZJ0117E Exception received while trying to(de-)register the resource resourceKey. atthe OSLC registry. Details about theexception: exception details.

Explanation: While trying to register or deregister aresource to the OSLC registry, an error occurred whichprevented the OSLC services to correctly register theresource.

System action: Automation engine continues to work,but the resource in question will not be registered.

Operator response: Use the exceptions details to learnmore about the failure. Either re-activate theautomation policy to trigger a new OSLC registrationaction or register the resource manually.

EEZJ0119E The automation domain domainName onhost hostName and port portNumber cannot be contacted. At leastnumberOfAttempts connection attemptshave failed.

Explanation: Several subsequent attempts to contactthe automation domain are either hanging or havetimed out.

System action: The automation domain is set to thecommunication state "domain has left". As aconsequence, the end-to-end automation manager doesnot try to contact the automation domain any moreuntil its automation adapter is restarted.

Operator response: Ensure that the network andfirewall setup allow establishing connections from theend-to-end automation manager host to the first-levelautomation host. Ensure that the first-level automationadapter gets sufficient operating system resources toperform well. Restart the end-to-end adapter for thefirst-level automation domain.



EEZJ0501W An exception was encountered andignored in order to continue operation.Details about the exception:exceptionString




EEZJ0509W One or multiple restart requests forautomation domain domainName havebeen interrupted. The reason code iseventReason . The following resources areaffected: resourceList

Explanation: The cause of the event leads toterminating the restart cycle.

System action: Terminates the restart cycle of theresources regardless of their individual restart status.

Operator response: Check the status of theautomation domain as mentioned in the reason code.Check the status of the affected resources.

EEZJ0510W A restart request to resource resourceIdrequested by operator userName hastimed out after timeoutHours hour(s). Thestate of the restart cycle is previousState .

Explanation: The restart request has timed out. Thetimeout value is defined by the environment variablecom.ibm.eez.aab.resource-restart-timeout-hours.


Operator response: Check the status of the resource.For more information on how to change the timeoutvalue refer to the Reference and Problem DeterminationGuide.

EEZJ0511W Found numberOfMatchingNodesautomation domain nodes for hostnamehostname. All of these nodes are mappedto the virtual server virtualServerName.The nodes exist within automationdomains listOfDomainNames.

Explanation: Hostnames should be uniquely bemapped to automation domain nodes, so theautomation domain nodes can be uniquely mapped tovirtual servers.

System action: The system maps multiple automationdomain nodes to a single virtual server.

Operator response: Check which nodes can beaddressed using the same hostname. Verify if thesenodes should be mapped to the same virtual server. If

the mapping is not correct then reconfigure the nodessuch that their hostnames are distinct. If the mapping iscorrect and if you want to suppress this message frombeing logged again, create a WebSphere ApplicationServer JVM custom property with namecom.ibm.eez.aab.suppress_EEZJ0511W and value 1.Restart WebSphere Application Server to enable theproperty.

EEZJ0512W The automation adapter of automationdomain domainName is not configured tosupport System Automation ApplicationManager DR toggle. System AutomationApplication Manager can togglebetween ipAddress1 and ipAddress2 .

Explanation: The automation adapter has to beconfigured for two end-to-end automation managementhosts to support the System Automation ApplicationManager toggle. The adapter is currently notconfigured to send events to the other SystemAutomation Application Manager instance.


Operator response: Check the automation adapterversion and the adapter configuration. Refer to theSystem Automation Application Managerdocumentation for the minimum required automationadapter version.

EEZJ0513W The automation adapter of automationdomain domainName does not supportSystem Automation ApplicationManager DR toggle. System AutomationApplication Manager can togglebetween ipAddress1 and ipAddress2 .

Explanation: The automation adapter version does notyet support System Automation Application Managertoggle.


Operator response: Refer to the System AutomationApplication Manager documentation for the minimumrequired automation adapter version. Upgrade theautomation adapter and configure it for SystemAutomation Application Manager toggle.

EEZJ0514W An exception for automation domaindomainName was encountered andignored. Details about the exception:exceptionString




EEZJ0501W • EEZJ0514W


EEZJ0515W A user security exception for first-levelautomation domain domainName hasbeen encountered.

Explanation: The automation domain requires userauthentication, but no valid user credential has beensupplied with the request.


Operator response: Case 1: If user authenticationchecking is enabled in the automation domain, ensurethat user credential information for the automationdomain is supplied. If the failing task was invokedfrom the System Automation operations console, theoperations console asks for a new valid user credential.Enter the new credential directly and store it to theDomain Credential store, or navigate to Settings -Stored Domain Credentials and edit the credentials asneeded. If the failing task was invoked from theend-to-end automation manager (either automationengine or automation JEE framework withinWebSphere Application Server), ensure that a usercredential for the first-level automation domain iscorrectly defined in the configuration of the automationengine. After you modified the credentials refresh theautomation engine using the Refresh function of theconfiguration utility (cfgeezdmn command). Case 2: Ifuser authentication checking has been disabled in theautomation domain, restart the adapter for thatautomation domain.

EEZJ0516W The EIF event publisher failed todisconnect from EIF event targeteifTargetName with exceptionexceptionDetails

Explanation: The automation JEE framework tries todisconnect from the EIF event target while the sessionthat owns the EIF event publisher is removed.



EEZJ0600W A RemoveException was received whiletrying to remove an entity from thedatabase when processing an eventreceived from automation domaindomainName.

Explanation: The EventHandlerBean received aRemoveException while trying to remove an entityafter processing an event.



EEZJ0601W The policy name stored in the JEEframework and the policy namesupplied by a policy changed event arenot equal. The policy name stored in theJEE framework is aab policyName. Thepolicy name supplied by the event isevent policyName.

Explanation: The JEE framework received a policychanged event that contains a policy name that doesnot match the policy name that was stored previouslyin the JEE framework.


Operator response: Verify that the policy names areset correctly. If necessary, activate the policy again.

EEZJ0602W Not able to communicate withautomation domain domainName.

Explanation: The EventHandlerBean tried tocommunicate with an automation domain, but itreceived an exception.



EEZJ0603W Automation domain oldDomainName hasleft and automation domainnewDomainName has joined. Thesedomains have the same access data.Apparently the domain has beenrenamed.

Explanation: The EventHandlerBean received adomain join event. The access data of this event, suchas the hostname and port, is the same as that of anexisting automation domain with a different name. TheEventHandlerBean created a new object for theautomation domain that joined and will soon removethe object for the automation domain that left.


Operator response: Verify that the automation domainhas not been renamed by mistake.

EEZJ0604W There are numberOfThreads active threadsthat are managed by componentcomponentName and may be hung.

Explanation: The component has detected that severalof its threads did not terminate within the expectedtime frame and are still active.

System action: The component continues to createnew threads as needed.

Operator response: Evaluate the message log forpotential reasons why the threads do not terminatewithin the expected time frame. If the number ofpotentially hanging threads continues to increase

EEZJ0515W • EEZJ0604W


consider to restart the WebSphere application server inorder to avoid the server reaching its memorylimitations eventually. Check IBM Electronic Supportfor additional information - http://www.ibm.com/support/entry/portal/

EEZJ0605W Ignoring a domain leave event fordomain domainName since the storedhost name or IP address ipAddressStoreddoes not match the host name or IPaddress ipAddressInEvent that is definedwithin the event.

Explanation: The domain leave event of theautomation domain contains a different host name orIP address than the stored domain data. A domainleave event is published when a first-level domain'sadapter is stopped, for example, when it moves fromone node to another node in the first-level automationdomain.

System action: The leave event is ignored.

Operator response: Check the first-level adapterconfiguration and verify that the adapter can bereached by using a single host name or IP address evenif the adapter is made highly available. In this case, avirtual IP address should be used. Additionally check ifthere exist multiple first-level automation domains thatuse the same end-to-end domain name.

EEZJ1604I All of the threads that are managed bycomponent componentName haveterminated.

Explanation: The component has previously detectedthat several of its threads did not terminate within theexpected time frame. In the meantime, all of them haveterminated.

System action: The component continues to createnew threads as needed.


EEZJ1000I Application productName has startedworking.

Explanation: The application starts its asynchronouswork.



EEZJ1001I Application productName was shut downby the JEE container and has stoppedworking.

Explanation: The application stops its asynchronouswork.


Operator response: If required, restart the application.

EEZJ1002I Domain domainName has been inactivefor a long period of time and has beenremoved from the automation scope.

Explanation: The timeout defined by the environmentvariable com.ibm.eez.aab.domain-removal-hours hasbeen reached for this automation domain.


Operator response: No operator action required.When the automation domain that has been removedfrom the automation scope joins the automation scopeagain, it is recreated.

EEZJ1003I The communication state of automationdomain domainName has changed frompreviousCommState to newCommState.

Explanation: The communication health state haschanged.

System action: The system publishes a related event.

Operator response: Depending on the current statevalues and the desired communication state of theautomation domain, it might be necessary to restart theautomation adapter.

EEZJ1004I The timeout for backend automationcalls is timeoutValue seconds.

Explanation: Controls how many seconds each call tothe backend may take at most. Default: 60, minimum:30, maximum: 3600.


Operator response: If needed, set or modify theenvironment variable com.ibm.eez.aab.invocation-timeout-seconds.

EEZJ1005I The timeout to determine domaincommunication health state istimeoutValue seconds.

Explanation: Controls the number of seconds ofinactivity after which the health of the communicationto the automation domain is checked automatically.Default: 300, minimum: 60, maximum: 86400.


Operator response: If needed, set or modify theenvironment variable com.ibm.eez.aab.watchdog-interval-seconds.

EEZJ0605W • EEZJ1005I


EEZJ1006I The timeout before removing domainsthat have left is timeoutValue hour(s).

Explanation: Controls the number of hours ofinactivity after which the automation domain'srepresentation in the management server is removedautomatically. Default: 48, minimum: 1, maximum:1000.


Operator response: If needed, set or modify theenvironment variable com.ibm.eez.aab.domain-removal-hours.

EEZJ1008I The domain state of domain domainNamehas changed from previousDomainState tonewDomainState

Explanation: The state of the automation domain haschanged.

System action: The system publishes a related event.

Operator response: Depending on the current statevalues and the desired state of the automation domain,it might be necessary to restart the domain.

EEZJ1013I SA Application Manager does not sendevents to IBM Tivoli Netcool/OMNIbusas defined in the end-to-end automationmanager configuration.

Explanation: The property that contols OMNIbusevent creation is set to a value that prevents eventcreation.

System action: SA Application Manager does not sendevents to OMNIbus.

Operator response: If events should be sent toOMNIbus, start the end-to-end automation managerconfiguration tool and enable the OMNIbus eventgeneration checkbox.

EEZJ1014I SA Application Manager sends events toIBM Tivoli Netcool/OMNIbus asdefined in the end-to-end automationmanager configuration.

Explanation: The property that contols OMNIbusevent creation is set to a value that enables eventcreation.

System action: SA Application Manager sends eventsto OMNIbus.

Operator response: If events should not be sent toOMNIbus, start the end-to-end automation managerconfiguration tool and disable the OMNIbus eventgeneration checkbox.

EEZJ1015I Restart of resource resourceId starts asrequested by userName .

Explanation: The restart request is validatedsuccessfully. The stopping phase of the restart cyclebegins.

System action: The automation manager sends a stoprequest to the resource.


EEZJ1016I The resource resourceId has reached thestate observed offline afterdurationSeconds seconds. The startingphase of the restart cycle begins asrequested by userName .

Explanation: The stopping phase of the restart cycle iscompleted successfully. The starting phase of the restartcycle begins.

System action: The automation manager sends a startrequest to the resource.


EEZJ1017I Restart of resource resourceId iscompleted successfully afterdurationSeconds seconds as requested byuserName .

Explanation: The resource is restarted successfully.



EEZJ1018I The timeout before interruptingresource restart requests is timeoutValuehour(s).

Explanation: Controls how many hours the resourcerestart workflow waits for the expected sequence ofevents. Default: 1, minimum: 1, maximum: 3600.

System action: When the timeout occurs, then thesystem interrupts the resource restart workflow. Thesystem does not send any online or offline requests tothe resource based on the timeout.

Operator response: When the timeout occurs, checkthe status and the request list of the affected resource inorder to determine why either the stopping phase orthe starting phase of the resource restart did notcomplete. To control the timeout value, set or modifythe environment variable com.ibm.eez.aab.resource-restart-timeout-hours.

EEZJ1006I • EEZJ1018I


EEZJ1019I System Automation ApplicationManager has connected successfully tothe database manager.

Explanation: Previously reported problems to connectto the database manager are resolved.



EEZJ1020I The status of the EIF event targeteifTargetName changed: Address=Address,Port=Port, Status=Status

Explanation: This message occurs if the status of theEIF connection changed. The reason could be that anew EIF connection is created or an existing EIFconnection is lost. The reason can be found in thestatus. A status='connection timed out' is expected ifthe EIF event target is stopped, e.g. if the EIF eventtarget moves to another system and therefore the EIFpublisher needs to change the EIF destination. Thefollowing status values are supported: 1 - connectioncreated, 2 - connection changed, 4 - connection closed, 8- connection timed out.



EEZJ1100I Attributes of domain domainName havechanged: listOfChangedAttributes

Explanation: The domain join event of the automationdomain contains different attribute values than thedomain object. The domain object will be updated withthe values of the event.

System action: Processing continues with the updateddomain object.

Operator response: Review the modified attributes. Ifyou find inappropriate values reconfigure the relatedautomation adapter and restart the automation adapter.

EEZJ1101I The host name or IP address of domaindomainName has changed fromipAddressOld to ipAddressNew .

Explanation: The domain join event of the automationdomain contains a different host name or IP addressthan the stored domain data. A domain join event ispublished when a first-level domain's adapter isstarted, for example, when it moves from one node toanother node in the first-level automation domain.

System action: The stored domain data will beupdated with the data of the event. Processingcontinues with the updated domain object.

Operator response: Verify that this change of the hostname or IP address is expected and authorized. Forexample, check if there exist multiple first-level

automation domains with the same end-to-end domainname.

Prefix EEZK

EEZK0003E String someString is too long: themaximum length of nameOfTheStringstrings is maxLength.

Explanation: Setting the string to the specified valuedid not succeed due to string length.



EEZK0004E String named someStringName must notbe null and must not exceed themaximum length of maxLength.

Explanation: Setting the string to null is not allowed.



EEZK0005E An exception that is not an instance ofEEZApplicationException has beenpassed to theEEZApplicationTransientException. Thetype of the message is exceptionType. Theexception message is: exceptionMessage.

Explanation: This is an unexpected behavior.

System action: The current task will continue. Theexception will be processed.

Operator response: If any other error occurs, pleaseprovide the logs and traces as an aid to analysis.

EEZK0006E A string has been encountered thatcannot be decomposed to a valid SystemAutomation source token. The internalreason is: internalReason

Explanation: System Automation supports the conceptof source tokens in order to identify automationdomains and automation resources. Generally, sourcetokens are strings used to uniquely identify objectswithin the scope of a particular software product. Forthis purpose, source tokens have to conform toproduct-specific syntactical rules. In this case, at leastone of the syntactical rules is violated.


Operator response: Evaluate the internal reason.

EEZJ1019I • EEZK0006E


EEZK0007E A problem occurred handling theencryption of a user credential. Theoriginal exception was: original exception.

Explanation: System Automation uses credentials(user and password pairs) to authenticate actionsagainst other components. Passwords are encrypted ordecrypted as needed. One of these functions failed.

System action: The current task ends. SystemAutomation is unable to use this credential foraccessing another component.

Operator response: Evaluate the original exception.Ensure that you have correctly set up the userencryption for this System Automation component.Ensure that user name and password have beencorrectly specified and files storing credentials have notbeen modified.

EEZK0008E A problem occurred handling theencryption of the credential for userwith name user. The original exceptionwas: original exception.

Explanation: System Automation uses credentials(user and password pairs) to authenticate actionsagainst other components. Passwords are encrypted ordecrypted as needed. One of these functions failed forthe specified user name.

System action: The current task ends. SystemAutomation is unable to use this credential foraccessing another component.

Operator response: Evaluate the original exception.Ensure that you have correctly set up the userencryption for this System Automation component.Ensure that user name and password have beencorrectly specified and files storing credentials have notbeen modified.

EEZK0009E The input string inputString is too long.The maximum length of a string of typetypeOfString is maxLength after it hasbeen encoded to UTF-8. The number ofcharacters of the input string isnumberOfCharacters. The number ofcharacters of the encoded input string isnumberOfUTF8Characters.

Explanation: The UTF-8 encoded input string is largerthan the maximum supported length for strings of thistype. The maximum length is defined by theend-to-end automation database table that is designedto store the input string in UTF-8 encoding format.


Operator response: Modify the input string such thatit becomes shorter and repeat the current task.

Prefix EEZL

EEZL0001E The WebSphere infrastructure hasreported a severe error situation:runtimeExceptionMessage



Operator response: Check the description of the errorsituation if it indicates that the server database oranother subsystem is unavailable.

EEZL0002E The WebSphere infrastructure hasreported an error situation:exceptionMessage

Explanation: The application was interrupted by anunexpected exception or error that is not aRuntimeException.

System action: The current task ends, but the databaseoperations that have been performed already remainvalid (no transaction rollback).


EEZL0003E A critical error has occurred in class:className, method: methodName. Thelogger object could not be initialized.




EEZL0004E An error has occurred in class:className, method: methodName,parameter: parameterName

Explanation: The method has been invoked with anempty or null parameter list. The method must beinvoked with a parameter list that is not null and filled.This indicates a programming error.



EEZK0007E • EEZL0004E


EEZL0005E An error has occurred in class:className, method: methodName,parameter: parameterName




EEZL0015E An error has occurred in class:className.

Explanation: Configuration data object is null.




Explanation: First-level automation name has not beenset.




Explanation: Host address has not been set.




Explanation: Adapter plugin class has not been set.




Explanation: Port has not been set.




Explanation: Timeout value has not been set.




Explanation: User Credentials object is null.




Explanation: Username has not been set.




Explanation: Password has not been set.



EEZL0024E An error has occurred in class:className, method: methodName. Illegalreturn object.

Explanation: The JCA has returned an illegalargument to the EJB, which has caused aClassCastException.



EEZL0005E • EEZL0024E



EEZL0025E An error has occurred in class:className, method: methodName. Illegalparameter at invocation of this method.




EEZL0030E A exception has occurred in class:className, method: methodName. Thenested exception is null.

Explanation: No exception object was linked to theResourceException that has been caught. This is anunexpected behavior and indicates a programmingerror on the J2C side.



EEZL0031E An error has occurred in class:className, method: methodName. Invalidnested exception: nestedException.

Explanation: An invalid exception object was linkedto the ResourceException that has been caught. This isan unexpected behavior and indicates a programmingerror on the J2C side.



EEZL0032E An error has occurred in class:className, method: methodName. NoConnection object could be obtained.

Explanation: The call toEEZConnectionFactory.getConnection(..) returned null.This is an unexpected behavior and indicates aprogramming error at J2C side.



EEZL0033E An error has occurred in class:className, method: methodName. NoInteraction object could be obtained.

Explanation: The call toEEZConnection.createInteraction() returned null. This isan unexpected behavior and indicates a programmingerror at J2C side.



EEZL0034E An error has occurred in class:className, method: methodName. JNDIname: jndiName did not return aConnectionFactory object.

Explanation: The JNDI lookup of this J2C hasencountered an internal error. The ConnectionFactoryobject could not be retrieved. This indicates a JNDIconfiguration error.

System action: The current task ends. No connectionto the first-level automation will be possible until thisproblem is fixed.

Operator response: Ensure the JNDI settings for theJ2C connection factories are correct and restart theserver.

EEZL0040E Error occurred during XML(de)serialization process. Exception:exception detected in className methodmethodName.

Explanation: The XML decoder has received an XMLstring that contained unsupported encoding.

System action: The method terminates with anExecutionFailedException.


EEZL0501W An exception was encountered andignored in order to continue operation.Exception string: exceptionString




EEZL0025E • EEZL0501W


EEZL0510W An exception was encountered at XMLserialization in class className methodmethodName. Exception string:exceptionDetails

Explanation: This might be subject to back-leveltoleration and can be ignored.

System action: The exception is ignored. The processwill be continued.


Prefix EEZP

EEZP0001E The specified <Source> source in the<Relationship> source relationshipTypetarget does not exist as a<ResourceReference>, <ResourceGroup>or <ChoiceGroup>.

Explanation: The <Source> and <Target> of a<Relationship> must exist as exactly one<ResourceReference>, <ResourceGroup> or<ChoiceGroup>.

System action: This policy cannot be activated.

Operator response: Verify this <Relationship> in thepolicy.

EEZP0002E The specified <Target> target in the<Relationship> source relationshipTypetarget does not exist as a<ResourceReference>, <ResourceGroup>or <ChoiceGroup>.

Explanation: The <Source> and <Target> of a<Relationship> must exist as exactly one<ResourceReference>, <ResourceGroup> or<ChoiceGroup>.


Operator response: Verify this <Relationship> in thispolicy.

EEZP0003E The specified <policyElement> namenameOfElement was found more thanonce as the name of a<ResourceReference>, <ResourceGroup>or <ChoiceGroup>.

Explanation: The value of the name attributes of<ResourceReference>, <ResourceGroup> and<ChoiceGroup> must be unique.


Operator response: Verify this name attribute in thispolicy.

EEZP0004E The specified member groupMember ofthe <groupElement> name groupNamedoes not exist as a<ResourceReference>, <ResourceGroup>or <ChoiceGroup>.

Explanation: The member in a group must exist asexactly one <ResourceReference>, <ResourceGroup> or<ChoiceGroup>.


Operator response: Verify this member name in thispolicy.

EEZP0005E Syntax error in line lineNumber columncolumnNumber. Original parser exception:errorMessage

Explanation: A syntax error occurred while parsingthis policy.


Operator response: Correct the syntax error in thispolicy.

EEZP0006E The specified policy file policyFile cannotbe found.

Explanation: The policy cannot be loaded from thislocation.


Operator response: Verify the policy XML file nameand its path.

EEZP0007E Original Parser Exception:exceptionMessage

Explanation: An internal problem occurred whileparsing this policy.


Operator response: Verify that the product is correctlyinstalled.

EEZP0008E An unsupported character character wasfound in the string completeString . Thisstring was found in the element<elementName> of the parent element<parentElement>.

Explanation: The character found in the string is notsupported.


Operator response: Remove the unsupportedcharacter from this string in this policy.

EEZL0510W • EEZP0008E


EEZP0009E The specified name nameOfElements wasfound in the elements <policyElement>and <otherPolicyElement>.

Explanation: The value of the name attribute must beunique.


Operator response: Verify this name attribute in thispolicy.

EEZP0010E The specified <ResourceReference>referenceName was found as a member ofmultiple <ChoiceGroup> elements.

Explanation: A <ResourceReference> can only be amember of one <ChoiceGroup>.


Operator response: Check that the<ResourceReference> is a member of at most one<ChoiceGroup> element in this policy.

EEZP0011E The specified <groupForm> groupNamewas found as a member of multipleother groups.

Explanation: A group can only be a member of onegroup.


Operator response: Check that the group is a memberof at most one group element in this policy.

EEZP0012E The two <ResourceReference> or<ReplicationReference> elementsreference and otherReference point to thesame referenced resource resource .

Explanation: A first level resource cannot bereferenced by more than one <ResourceReference> or<ReplicationReference> at a time.


Operator response: Check that every<ResourceReference> or <ReplicationReference>references a separate <ReferencedResource> or<ReferencedReplicationResource> as child element inthis policy.

EEZP0013E The specified member memberName wasfound multiple times in the same<groupForm> groupName .

Explanation: All <Members> child elements must beunique in one group.


Operator response: Check that the group has noduplicate <Members> child elements in this policy.

EEZP0014E The specified <ResourceReference>reference was found as a member of the<ResourceGroup> resourceGroupNameand the <ChoiceGroup> choiceGroupName.

Explanation: A <ResourceReference> can only be amember of multiple <ResourceGroup> elements or one<ChoiceGroup> element.


Operator response: Check that the<ResourceReference> is not a member of a<ResourceGroup> and a <ChoiceGroup> at the sametime in this policy.

EEZP0015E The specified <Relationship> <Type>relationType with <Source> Source and<Target> Target was found in a loop.

Explanation: <Relationship> elements of the same<Type> where one <Relationship> element <Target> isthe next <Relationship> element <Source> must notform a loop.


Operator response: Check that the <Relationship>elements are not defined as a loop in this policy.

EEZP0016E The specified element <childElement>was found more than once as a childelement of <parentElement> nameparentName .

Explanation: At most one element of this type isallowed in this group.


Operator response: Check that at most one element ofthis type is specified in this group in this policy.

EEZP0017E The specified element <parentElement>name parentName was found without<Members> child elements.

Explanation: At least one <Members> child elementmust be specified in this group.


Operator response: Check that at least one<Members> child element is specified in this group inthis policy.

EEZP0018E The policy document does not contain a<ResourceReference> or <include>element.

Explanation: At least one <ResourceReference>element or an <include> element must be specified inthis policy.

EEZP0009E • EEZP0018E



Operator response: Check that at least one<ResourceReference> element is specified in this policyor that another policy is included using an <include>element.

EEZP0019E The specified element <ChoiceGroup>name groupName was found with morethan one <Members> child elementwith the preferred attribute equal totrue.

Explanation: One <ChoiceGroup> member must havethe preferred attribute equal to true.


Operator response: Check that exactly one<ChoiceGroup> member has the preferred attributeequal to true.

EEZP0020E The specified <Relationship> with the<Type> relationType, the <Source> sourceand the <Target> target was foundmultiple times in the policy document.

Explanation: All <Relationship> elements must beunique.


Operator response: Check that at most one<Relationship> of this type is specified in this policy.

EEZP0021E A 'UTFDataFormatException' wascaughed in method methodName of classclassName. The received message wasmessage.


System action: The policy cannot be loaded.

Operator response: Ensure the correct data format ofthe policy document by only using editors which createUTF-8-compliant documents.

EEZP0022E The specified <groupType> namegroupName was found in a loop.

Explanation: Group elements cannot form a loop withtheir members.


Operator response: Check that the group <Members>child elements are not defined as a loop in this policy.

EEZP0023E The specified element <ChoiceGroup>name groupName has no <Members>child element with the preferredattribute equal to true.

Explanation: One <ChoiceGroup> member must havethe preferred attribute equal to true.


Operator response: Check that exactly one<ChoiceGroup> member has the preferred attributeequal to true.

EEZP0024E The specified element<ResourceReference> name referencepoint to the same<AutomationDomainName> valuespecified for the element<PolicyInformation> in this policy.

Explanation: A <ResourceReference> child element<AutomationDomain> cannot point to the same<AutomationDomainName> value specified for theelement <PolicyInformation> in this policy.


Operator response: Check that no<ResourceReference> child element<AutomationDomain> has the same value as the<PolicyInformation> child element<AutomationDomainName> in this policy.

EEZP0025E There is no <Site> specified with index1.

Explanation: There has to be specified a <Site> withindex 1, which is the initially primary site.

System action: This disaster recovery policy cannot beactivated.

Operator response: Specify a <Site> with attributeindex set to 1 in this disaster recovery policy.

EEZP0026E There are multiple <Site> elementsspecified with the same index siteIndexnamed listOfSiteNames.

Explanation: <Site> indices have to be unique.


Operator response: Change the index attributes of<Site> elements in this disaster recovery policy so thatthey are unique or remove redundant <Site>specifications.



EEZP0027E There are multiple <Domain> elementsspecified with the same nameFLADomainName .

Explanation: <Domain> names have to be unique.


Operator response: Change the <Domain> names inthis disaster recovery policy so that they are unique orremove the redundant <Domain> specifications.

EEZP0029E More than one <Domain> is specifiedon <Site> with index siteIndex in theCluster Set ClusterSetName . Found:listOfFLADomainNames.

Explanation: At most one <Domain> is allowed per<Site> in a Cluster Set.


Operator response: Ensure that in this disasterrecovery policy, at most one <Domain> located at this<Site> specifies this Cluster Set in its attributeclusterSetName.

EEZP0030E There are multiple <Node> elementsspecified with the same name nodeNamein the <Domain> FLADomainName .

Explanation: The names for <Node> elements definedin a <Domain> have to be unique.


Operator response: Ensure that there are not multiple<Node> elements specified with equal pairs of nameattributs and <Domain> subelements in this disasterrecovery policy.

EEZP0032E The <Site> which is referenced by<Node> nodeName in <Domain>FLADomainName is not defined.

Explanation: Cannot assign a <Node> to a <Site>which is not specified in the disaster recovery policy.


Operator response: Ensure that the index attribute ofthe <Site> subelement of the <Node> matches with theindex attribute of the corresponding <Site> in thisdisaster recovery policy.

EEZP0033E The <Domain> FLADomainName whichis referenced by <Node> nodeName isnot specified in the disaster recoverypolicy.

Explanation: The <Domain> referenced by a <Node>has to be specified in the disaster recovery policy.


Operator response: Add a specification for the<Domain> to this disaster recovery policy.

EEZP0034E The <Domain> FLADomainName whichis referenced by the membermemberName of the disaster recoverychoice group nodeName is not specifiedin the disaster recovery policy.

Explanation: Each <Domain> referenced by a disasterrecovery choice group member has to be specified inthe disaster recovery policy.


Operator response: Add a specification to the disasterrecovery policy for this <Domain>.

EEZP0035E <ResourceReference> namedresourceReferenceName is specified asbusinessCritical, but its <Domain>FLADomainName is not associated with aCluster Set.

Explanation: Each <ResourceReference> specified inthe disaster recovery scope has to be associated with aCluster Set via its supporting <Domain>.


Operator response: Ensure that the supporting<Domain> is specified in the disaster recovery policyand that its clusterSetName attribute is set properly orremove the businessCritical attribute from the<ResourceReference>.

EEZP0036E The members of the disaster recoverychoice group DRChoiceGroupName are notall associated with the same Cluster Set.Members are associated with thefollowing Cluster Sets:listOf(ClusterSetName).

Explanation: A disaster recovery choice group canonly switch between the resource references of a singleCluster Set.


Operator response: Ensure in this disaster recovery



policy that the same value is set in the clusterSetNameattribute of every <Domain> providing a member ofthis disaster recovery choice group.

EEZP0037E There are multiple members in thedisaster recovery choice groupDRChoiceGroupName that belong to the<Site> with index siteIndex . Foundmembers listOf(resRefName atclusterSetName).

Explanation: There is at most one<ResourceReference> allowed for each <Site> in andisaster recovery choice group.


Operator response: Remove redundant memberslocated at this <Site> from the disaster recovery choicegroup in this disaster recovery policy.

EEZP0038E The member named MemberName ofdisaster recovery choice group namedchoiceGroupName is not provided by a<Domain> that has a Cluster Set and<Site> specified.

Explanation: Each member of a disaster recoverychoice group has to be associated to a Cluster Set andto a <Site> via its <Domain>.


Operator response: Ensure in this disaster recoverypolicy that the <ChoiceGroup> member is provided bya <Domain> that has the clusterSetName attribute setand that has at least one <Node> defined at a <Site>.

EEZP0039E The member named MemberName ofdisaster recovery choice group namedchoiceGroupName is not a<ResourceReference>.

Explanation: Only <ResourceReference> elements areallowed as members of an disaster recovery choicegroup.


Operator response: Ensure in this disaster recoverypolicy that each member of the disaster recovery choicegroup is a <ResourceReference>.

EEZP0040E The preferred member namedMemberName of disaster recovery choicegroup named choiceGroupName is notlocated at <Site> with index 1.

Explanation: The preferred member of a disaster

recovery choice group has to be located at initiallyprimary <Site>.


Operator response: Ensure in this disaster recoverypolicy that the preferred member of this disasterrecovery choice group is located at <Site> with index 1.

EEZP0041E The drml file DRMLFileName could notbe found in the policy pool.

Explanation: The file does not exist or access rightsare not set properly.

System action: The disaster recovery policy cannot beparsed. The automation engine is not able to activatethe disaster recovery policy including this drml file andwill continue to run with the currently activated policy.

Operator response: Ensure that the specified drml filecan be accessed in the policy pool.

EEZP0042E A SAXException was caught whileparsing the policy fullQualifiedPolicyPathfrom the policy pool.

Explanation: The policy is not compliant to thecorresponding XML Schema.

System action: The policy cannot be parsed. Theautomation engine is not able to activate this policyand will continue to run with the currently activatedpolicy.

Operator response: Ensure that the policy isconformant with the XML Schema.

EEZP0043E Disaster recovery specific attributes likebusinessCritical andswitchableByDROnly were found in thepolicy, but the policy is not disasterrecovery enabled.

Explanation: The attributes businessCritical andswitchableByDROnly are only allowed if the policy isdisaster recovery enabled.


Operator response: Either remove the disasterrecovery specific attributes from this policy or add the<DRPolicy> subelement in the <PolicyInformation>specifying the corresponding drml file.

EEZP0044E The <Domain> named domainName isstretched across more than two sites.Found <Node> elements with siteindices listOfIndices.

Explanation: Spread of domains is restricted to atmost two sites.




Operator response: Limit the <Node> elements of this<Domain> to at most two <Site> elements in thisdisaster recovery policy.

EEZP0045E The <HardwareDevice> of <Node>nodeName in <Domain> domainNamereferences a non-existing <Box> / <Slot>pair.

Explanation: In order to provide<HardwareManagementTasks> for HardwareDevices,the referenced pair of <Box> and <Slot> has to bespecified in the disaster recovery policy.


Operator response: Add the <Box> and <Slot>specifications with names corresponding to the namesreferenced in the <HardwareDevice> of the <Node> tothis disaster recovery policy.

EEZP0047E There is no corresponding<ResourceReference> specified for<Site> with index siteIndex in disasterrecovery choice groupDRChoiceGroupName .

Explanation: This disaster recovery choice groupcannot switch to a member at this <Site> and thuscannot be recovered at that <Site>.


Operator response: To ensure disaster recoverycapability of the <ChoiceGroup> also at this <Site>,specify a proper <ResourceReference> and add it to thegroup in this disaster recovery policy.

EEZP0048E No credentials are specified for the<Box> named boxName in the pluginproperties file of the hardware adapter.

Explanation: Security setup is required for eachhardware box. The credentials must be specified usingthe Hardware adapter configuration task of theconfiguration dialog of System Automation ApplicationManager. The credentials specified there might beempty, if none are needed to access the hardware box.


Operator response: Run the Hardware adapterconfiguration task of the configuration dialog of SystemAutomation Application Manager. Make sure that eachhardware box is listed in table Configured hardwareaccess credentials, even if the credentials are empty.

EEZP0049E No credentials are specified for the<Slot> named slotName of the <Box>named boxName in the plugin propertiesfile of the Hardware Adapter.

Explanation: Security setup is required for eachhardware slot. The credentials must be specified usingthe Hardware adapter configuration task of theconfiguration dialog of System Automation ApplicationManager. The credentials specified there might beempty, if none are needed to access the hardware slot.


Operator response: Run the Hardware adapterconfiguration task of the configuration dialog of SystemAutomation Application Manager. Make sure that eachhardware slot is listed in table Configured hardwareaccess credentials, even if the credentials are empty.

EEZP0050E The discretionary group namedGroupName contains a business criticalmember named MemberName .

Explanation: Business critical resource references orgroups are not allowed as members of discretionarygroups.


Operator response: In this disaster recovery policy,either remove the businessCritical attribute consistentlyin all of the group's members or set the groupbusinessCritical.

EEZP0051E Syntax error in line lineNumber columncolumnNumber of policy file filePath .Original parser exception: errorMessage

Explanation: A syntax error occurred while parsingthis policy.


Operator response: Correct the syntax error in thispolicy.

EEZP0052E The number of specified <Site>elements in the disaster recovery policyis not two.

Explanation: Only setups with exatcly two sites aresupported.


Operator response: Make sure that there are exactlytwo <Site> elements in the disaster recovery policy.



EEZP0053E The <Site> indices are not set asrequired. Found indices listOf(siteIndex).

Explanation: The <Site> indices have to be a sequenceof increasing numbers starting with 1.


Operator response: Set the index attributes in the<Site> elements properly in this disaster recoverypolicy.

EEZP0054E There is no corresponding <Domain>specified on <Site> with index siteIndexfor the Cluster Set clusterSetName .

Explanation: The resources of a Cluster Set cannot berecovered at a <Site> that has no corresponding<Domain> specified supporting a corresponding<ResourceReference>.


Operator response: To ensure disaster recoverycapability of the Cluster Set in this disaster recoverypolicy, assign a <Domain> located at the missing <Site>to the Cluster Set by properly setting theclusterSetName attribute.

EEZP0055E Found a relationshipName <Relationship>with a business critical <Source> namedsourceName and a discretionary <Target>named targetName .

Explanation: It is recommended that a business criticalresource is not dependent on a discretionary resource.


Operator response: Remove the <Relationship> orchange the businessCritical attribute of either the<Source> or the <Target> in this disaster recoverypolicy.

EEZP0056E The business critical group namedgroupName has a member namedmemberName that is explicitly set todiscretionary.

Explanation: Discretionary members are not allowedin business critical groups.


Operator response: Remove the businessCriticalattribute of either the group from where it waspropagated or of its member in this disaster recoverypolicy.

EEZP0058E The member named memberName of thedisaster recovery choice groupchoiceGroupName participates directly ina Relationship named relationshipName .

Explanation: The members of disaster recovery choicegroups are not allowed to participate directly inrelationships.


Operator response: Use the disaster recovery choicegroup instead of its member to model the relationshipin this disaster recovery policy.

EEZP0059E The member named memberName of thedisaster recovery choice groupchoiceGroupName is also member of agroup named groupName .

Explanation: The members of a disaster recoverychoice group are not allowed to be direct members ofother groups.


Operator response: In this disaster recovery policy,put the disaster recovery choice group instead of itsmember in the group.

EEZP0060E The business critical<ResourceReference>resourceReferenceName is not member of adisaster recovery choice group, but its<Domain> does not cover all sites.

Explanation: Business critical leaf resources that donot cover all sites, i.e. that are provided by a <Domain>that is not stretched across all sites, have to be placedin disaster recovery choice groups.


Operator response: In this disaster recovery policy,put the <ResourceReference> into a proper disasterrecovery choice group.

EEZP0061E The disaster recovery choice groupchoiceGroupName with the attributeswitchableByDROnly is discretionary.

Explanation: Disaster recovery choice groups have tobe business critical.


Operator response: Either put the <ChoiceGroup>into a business critical group, specify the disasterrecovery choice group explicitly as businessCritical, or



remove the switchableByDROnly attribute in thisdisaster recovery policy.

EEZP0062E A exceptionClassName was caught in ruleruleClassName of the policy checker.

Explanation: The policy check was interrupted by thisexception and failed.

System action: This policy contains errors and cannotbe activated.


EEZP0063E No SNMP agent for: key of the resource

Explanation: Mechanism SNMP is specified for ahardware management task though no SNMP agent hasbeen defined for the enclosing box.



EEZP0064E Inconsistent hardware management taskdefinition for: key of the resource

Explanation: Mechanism SNMP is specified for ahardware management task with a Script element.




Explanation: Mechanism Script is specified for ahardware management task though no Script elementhas been defined for it.




Explanation: No timeout is defined for synchroneousexecution of the script command.


Operator response: Correct and reactivate yourautomation policy: Either define a timeout for the scriptcommand, or specify asynchroneous execution by

setting attribute runCommandSync to 0 or 2 in thedrml file.

EEZP0067E The <ResourceReference>ResourceReferenceName references a fixedresource in <Domain> DomainNamewhose hosting <Node> NodeName is notspecified.

Explanation: Workload on a <Domain> with anincomplete <Node> specification cannot be controlled.


Operator response: Add the missing <Node>specification to this drml file.

EEZP0068E The value value of the attributeattributeName in the element<ElementName> is not allowed.

Explanation: This value is reserved.


Operator response: Change the value.

EEZP0069E The name name is used as domain nameand as cluster set name.

Explanation: Names for domains and cluster sets areused as identifier and must be unique.


Operator response: Change the either the domainname or the cluster set name.

EEZP0070E The specified <groupForm> groupNamewas found as member of itself.

Explanation: A group cannot be member of itself.

System action: This policy is not valid.

Operator response: Check that no group is member ofitself in this policy.

EEZP0071E Not able to create an object of typeObject-type. The name of the tree-node isnode-name.

Explanation: There is a problem when building aninternal object of the input XML.


Operator response: Check for related messages.



EEZP0072E An empty string was found for amandatory element. This empty stringwas found in the element <elementName>of the parent element <parentElement>with name name .

Explanation: The empty string value is not supportedfor this element.


Operator response: Add a valid value for this elementin this policy.

EEZP0073E An unsupported character character wasfound in the string completeString . Thisstring was found in the attributeattributeName of the element <element>.

Explanation: The character found in the string is notsupported.


Operator response: Remove the unsupportedcharacter from this string in this policy.

EEZP0074E An empty string was found for amandatory element. This empty stringwas found in the element <elementName>of the parent element <parentElement>.

Explanation: The empty string value is not supportedfor this element.


Operator response: Add a valid value for this elementin this policy.

EEZP0075E The member member name has parentgroups with different <DesiredState>.

Explanation: Groups having the same member musthave the same <DesiredState>.


Operator response: Ensure that all parent groups ofthis member have the same <DesiredState> specified inthe policy.

EEZP0076E The workloadSetup attribute of the<Domain> element with name domainname is not allowed for this domain.

Explanation: The workloadSetup attribute must not bedefined in non-stretched domains.


Operator response: Remove the workloadSetupattribute of the <Domain> element in the policy.

EEZP0077E Found <ReplicationReference> elementsin the disaster recovery policy.

Explanation: <ReplicationReference> elements are notsupported in disaster recovery enabled policies.


Operator response: Either remove the<ReplicationReference> elements from the policy orremove the <DRPolicy> subelement in the<PolicyInformation> specifying the policy as disasterrecovery enabled.

EEZP0078E Found <Resource> elements of classIBM.ITMResource in the policy, butintegration with IBM Tivoli Monitoringis not enabled in the Agentless Adapterconfiguration.

Explanation: <Resource> elements of classIBM.ITMResource are only supported if the integrationwith IBM Tivoli Monitoring has been configured andenabled using the configuration utility of SystemAutomation Application Manager.


Operator response: Use the Agentless Adapterconfiguration task in the configuration utility of SystemAutomation Application Manager to enable andconfigure the integration with IBM Tivoli Monitoring.

EEZP0079E The element <MonitorAttribute> isspecified in an invalid format. It mustcontain a dot separating the attributegroup of an IBM Tivoli Monitoringagent and the name of the attributewithin that attribute group that shouldbe used to determine the observed stateof the resource. The specified value ofthe <MonitorAttribute> element isMonitorAttributeValue and was found inthe parent element <parentElement> withname name .

Explanation: In order to determine the observed stateof the resource, the agent attribute specified in thepolicy element MonitorAttribute is queried periodically.The attribute is specified in the form<AttributeGroup>.<AttributeName> in the policyelement MonitorAttribute. The attribute group and theattribute name within that group must be separated byexactly one dot.


Operator response: Modify the value of theMonitorAttribute element in the policy, so that a validattribute group and attribute name are specified. Thenreactivate the policy.



EEZP0080E The node attribute of a resource of classIBM.ITMResource is specified in aninvalid format. It must contain a validmanaged system name as known to theIBM Tivoli Monitoring environment. Avalid managed system name containstwo or three name components whichare separated by colons. The specifiedvalue of the node attribute is node valueand was found in the <Resource>element named resource name .

Explanation: For resources of class IBM.ITMResource,the node attribute must contain a valid managedsystem name corresponding to the Tivoli Monitoringagent that manages the resource. A valid managedsystem name contains two or three name componentswhich are separated by colons. For example, a validmanaged system name is Apache:host1:KHTP.


Operator response: Modify the node attribute value ofthe Resource element in the policy, so that it contains avalid managed system name. Then reactivate the policy.

EEZP0081E No <UserName> has been specified forthe <IBM.ITMResourceAttributes>element which is named name and nogeneric IBM Tivoli Monitoring user hasbeen configured in the SA ApplicationManager configuration utility.

Explanation: You can configure a generic user to login to the IBM Tivoli Monitoring SOAP server using theSA Application Manager configuration utitlity. Thisgeneric user is used if no <UserName> is specified inthe <IBM.ITMResourceAttributes> element within thepolicy. If no generic user is configured, you mustspecify a <UserName> element in the policy for the<IBM.ITMResourceAttributes> element. For thisAgentless Adapter instance no generic user has beenconfigured, and this policy contains<IBM.ITMResourceAttributes> elements that do notcontain a <UserName> element.


Operator response: Add <UserName> elements to all<IBM.ITMResourceAttributes> elements in the policy,or define a generic IBM Tivoli Monitoring user usingthe SA Application Manager configuration utility.

EEZP0082E The availability target of<ServerGroup> server group name is notin the valid range of 1 to member count .

Explanation: The availability target of a ServerGrouphas to be greater than zero and not greater than themember count.


Operator response: Adjust the value of the

availabilityTarget attribute of the <ServerGroup>element in this policy.

EEZP0083E The satisfactory target of<ServerGroup> server group name is notin the valid range of 1 to member count .

Explanation: The availability target of a ServerGrouphas to be greater than zero and not greater than themember count.


Operator response: Adjust the value of theavailabilityTarget attribute of the <ServerGroup>element in this policy.

EEZP0084E The availability target of<ServerGroup> server group name is notin the valid range. The availabilitytarget must be equal to or greater thanthe satisfactory target, which issatisfactory target .

Explanation: The availability target of a ServerGrouphas to be equal to or greater than the satisfactorytarget.


Operator response: Adjust the values of theavailabilityTarget attribute and/or the satisfactoryTargetof the <ServerGroup> element in this policy.

EEZP0085E The <ResourceReference> resourcereference name is the source of arelationship and also member of the<ServerGroup> server group name . Onlyone of both is allowed.

Explanation: The members of a <ServerGroup> mustnot be the source of relationships.


Operator response: Either remove all relations startingfrom the <ResourceReference> or remove the<ResourceReference> from the <ServerGroup>

EEZP0086E The <ResourceReference> resourcereference name is the target of arelationship and also member of the<ServerGroup> server group name . Onlyone of both is allowed.

Explanation: The members of a <ServerGroup> mustnot be the target of relationships.


Operator response: Either remove all relationspointing to the <ResourceReference> or remove the<ResourceReference> from the <ServerGroup>



EEZP0087E The ServerGroup server group name hasmore members than the maximumallowed value ( maximum server groupmembers ).

Explanation: The amount of members of a<ServerGroup> is limited.


Operator response: Reduce the number of membersfrom the <ServerGroup>

EEZP0088E The <Relationship> relationshipNamebetween <Source> sourceResourceNameand <Target> targetResourceName linkstwo dynamic resource references.

Explanation: Relationships between two dynamicresource references are not supported.


Operator response: Change the relationship to includeat most one dynamic resource reference.

EEZP0089E The <ChoiceGroup> choiceGroupNamecontains the dynamic resource referencedynamicResourceReferenceName in its<Members> list.

Explanation: Dynamic resource references are notsupported as members of choice groups. A dynamicresource reference can be a member of a<ResourceGroup>.


Operator response: Remove the dynamic resourcereference from the member list of the choice group.Add one or multiple static resources instead. The staticresource can be a <ResourceGroup> which contains thedynamic resource reference.

EEZP0090E The <ServerGroup> serverGroupNamecontains the dynamic resource referencedynamicResourceReferenceName in its<Members> list.

Explanation: Dynamic resource references are notsupported as members of server groups. A dynamicresource reference can be a member of a<ResourceGroup>.


Operator response: Remove the dynamic resourcereference from the member list of the server group.Add one or multiple static resources instead. The staticresource can be a <ResourceGroup> which contains thedynamic resource reference.

EEZP0500W The specified member memberName ofthe <ChoiceGroup> choiceGroupName wasalso found as a <Source> or <Target> ofa <Relationship>.

Explanation: The member of a <ChoiceGroup> shouldnot be the <Source> or <Target> of a <Relationship> atthe same time.

System action: Application continues.

Operator response: To avoid complexity, delete the<Relationship> or delete this <ChoiceGroup> memberin this policy.

EEZP0502W The two <Relationship> elements with<Type> StartAfter and <Type>StopAfter were found with the same<Source> source and <Target> target .

Explanation: The two <Relationship> elements with<Type> StartAfter and <Type> StopAfter should nothave the same <Source> and <Target>. With thisconfiguration the <Target> is started before the<Source> and the <Target> is stopped before the<Source>.


Operator response: Verify this behavior. The commonusage of StartAfter together with StopAfter is thefollowing: 1. The <Source> of the StartAfter is the<Target> of the StopAfter. 2. The <Target> of theStartAfter is the <Source> of the StopAfter.

EEZP0503W The <DesiredState> Reference State of the<ResourceReference> with nameReference Name does not match the<DesiredState> Group State of its parentgroup with name Group Name .

Explanation: The <DesiredState> of the groupmember will be ignored.

System action: The <DesiredState> of this<ResourceReference> will be set to the <DesiredState>of its parent group. Application continues.

Operator response: To avoid this warning specify thesame <DesiredState> for this <ResourceReference> andits parent group.

EEZP0504W The <DesiredState> member group Stateof the group with name member groupName does not match the <DesiredState>hosting group state of its parent groupwith name hosting group name .

Explanation: The <DesiredState> of the groupmember will be ignored.

System action: The <DesiredState> of this group willbe set to the <DesiredState> of its parent group.Application continues.

EEZP0087E • EEZP0504W


Operator response: To avoid this warning specify thesame <DesiredState> for this group and its parentgroup.

EEZP0505W The <ChoiceGroup> choiceGroupNamewas found as member of the<ChoiceGroup> choiceGroupName .

Explanation: The member of a <ChoiceGroup> shouldnot be another <ChoiceGroup>.


Operator response: To avoid complexity, delete the<ChoiceGroup> from the <ChoiceGroup> in this policy.

EEZP0506W The resource group with nameresourceGroupName has linked more than100 resources.

Explanation: The numbers of resources linked by aresource group is limited to 100.


Operator response: Reduce the number of resourceslinked by this group.

EEZP0507W Found a StartAfter relationship withsource Source Name having<DesiredState> Online and target TargetName having <DesiredState> Offline.

Explanation: An online request will be propagatedalong this relationship. Therefore, the <DesiredState> ofthe target resource will be ignored.

System action: The <DesiredState> of the targetresource will be set to Online. Application continues.

Operator response: To avoid this warning, specify the<DesiredState> Online also for the target of thisrelationship.

EEZP2003I Policy has been verified.

Explanation:

System action:

Operator response:

EEZP2004I Policy could not be verified.

Explanation:

System action:

Operator response:

EEZP2005I The following policy errors were found:

Explanation:

System action:

Operator response:

EEZP2006I The following policy warnings werefound:

Explanation:

System action:

Operator response:

EEZP2007I ERROR:

Explanation:

System action:

Operator response:

EEZP2008I WARNING:

Explanation:

System action:

Operator response:

EEZP2009I eezpolicychecker

Explanation:

System action:

Operator response:

EEZP2011I EXPLANATION:

Explanation:

System action:

Operator response:

EEZP2012I USER ACTION:

Explanation:

System action:

Operator response:

EEZP2013I Setting the <DesiredState> of thetop-level resource Resource Name toOnline, because it is not specified in thepolicy.

Explanation: Top-level resources require a default<DesiredState>.

System action: The <DesiredState> for this resource isset to Online. Application continues.

EEZP0505W • EEZP2013I



Prefix EEZQ

EEZQ0001E Unable to create the URL for URL name .Exception details: exceptionDetails

Explanation: The system failed to build an URL objectfrom the the URL name.


Operator response: Check IBM Electronic Support foradditional information - http://www.ibm.com/support/entry/portal/.

EEZQ0002E Unable to connect to the IBM TivoliEnterprise Monitoring Server (TEMS) atconnectionName . Exception details:exceptionDetails

Explanation: The system failed to connect to theTEMS server.


Operator response: Verify that the target system andthe TEMS application are available.

EEZQ0003E Unable to create an SSL socket factory.Exception details: exceptionDetails

Explanation: The system failed to create or to initializea transport layer security (TLS) context.


Operator response: Verify that the TLS protocol isavailable within this Java virtual machine.

EEZQ0004E Communicating with the IBM TivoliEnterprise Monitoring Server (TEMS) atconnectionName failed. Exception details:exceptionDetails

Explanation: An exception occured while sending orreceiving data.


Operator response: Evaluate the exception details.Retry the operation.

EEZQ0005E Unable to parse the response that wasreceived from the IBM Tivoli EnterpriseMonitoring Server (TEMS) atconnectionName . Exception details:exceptionDetails

Explanation: An exception occured while processingthe XML data that were received from TEMS.


Operator response: Evaluate the exception details.Retry the operation.

EEZQ0006E Did not receive a Result object withinthe response to the remote systemcommand commandName for targettargetName that was sent to the IBMTivoli Enterprise Monitoring Server(TEMS). The following data have beenreturned instead: returnedData

Explanation: The TEMS accepted the command butdid not return a proper Result return code.


Operator response: Evaluate the command and thereturned data. Retry the operation.

EEZQ0007E A SOAP fault was received as responseto request requestName for targettargetName that was sent to the IBMTivoli Enterprise Monitoring Server(TEMS). The following SOAP fault datahave been returned: returnedData

Explanation: The TEMS returned a SOAP faultresponse to the request.


Operator response: Evaluate the command and thereturned fault data. Retry the operation.

EEZQ0008E Expected nonempty input but receivedno input in class: className, method:methodName, parameter: parameterName

Explanation: A parameter with a null or empty valuewas encountered. This is an indication of aprogramming error on the client side of the ITMfacade.

System action: The method ends without processingthe request.


Prefix EEZR (Reporting)

EEZR0001E The following SQLException occurred:Exception text

Explanation: The processing was interrupted by aSQLException and cannot complete correctly.


Operator response: Verify your database credentials. Ifthe problem persists, contact your DB2 systemadministrator.

Prefix EEZQ • EEZR0001E



Explanation: The processing was interrupted by aSQLException and cannot complete correctly. Thedatabase server name, port, the database name itself orthe schema name maybe incorrect.


Operator response: Verify that your database servername, port, the database name itself and the schemaname is correct and the database is running. If theproblem persists, contact your DB2 systemadministrator.

EEZR0003E The JDBC drivercom.ibm.db2.jcc.DB2Driver could not beloaded.

Explanation: The JDBC driver could not be loaded,the connection to the database could not be established.

System action: The connection establishment ended.

Operator response: Verify that your installationdirectory contains the files db2jcc_javax.jar anddb2jcc.jar.

EEZR0004E An IOException with the followingmessage occured during the loading ofthe feeder configuration file: Exceptiontext

Explanation: The database feeder configuration filecould not be loaded, the connection to the databasecould not be established.


Operator response: Verify that you provided thecorrect path to the configuration file and that the file isunlocked.


Explanation: The processing was interrupted by aSQLException and cannot complete correctly.


Operator response: Check the DB2 information center(available online) for the cause of the exception. Usethe SQLSTATE value to identify the reason. If youcannot resolve the problem, contact your DB2 systemadministrator.

EEZR0006E The following parameters in thedatabase feeder configuration file aremissing: config parameters

Explanation: Parameters in the database feederconfiguration file are missing, the connection to the

database could not be established.


Operator response: Verify that you provided thecorrect parameters for the configuration file.

EEZR0007E An attempt to invoke operationmethodName in class className with theillegal eventType evenType has beendetected. For this eventType, thereporting functionality is not supported.

Explanation: A caller tried to invoke the method withan eventType that is not supported.

System action: The current task is not completedsuccessfully.


EEZR0008E An error occurred trying to look up thedatasource to connect to the end-to-enddatabase: Exception text

Explanation: An error has occurred while trying tolook up the automation JEE framework's datasourceEAUTODBDS. Possible causes: 1) The automation JEEframework (Enterprise application EEZEAR) is notstarted or is not deployed correctly. 2) The datasourceEAUTODBS is not deployed correctly.

System action: Processing ends.

Operator response: Check that the enterpriseapplication EEZEAR is started. Check that theEAUTODBDS is installed. If the problem persists,contact your system administrator.

EEZR0009E An error occurred: Exception text

Explanation: An error has occurred.


Operator response: Check the Websphere log fordetailed information on the exception.

EEZR0010E An error has occurred while accessingthe end-to-end automation manager:Exception text

Explanation: An error has occurred while accessingthe end-to-end automation manager componentrunning on the management server. The requestedaction could not be processed. Possible causes: 1) Themanagement server is down. 2) The automation JEEframework (Enterprise application EEZEAR) is notstarted. 3) The are some inconsistencies regarding thelevel of the reporting component and the end-to-endautomation manager.

System action: The requested action is cancelled.

EEZR0002E • EEZR0010E


Operator response: Ensure that the managementserver is up and running. Check that the enterpriseapplication EEZEAR is started. Verify that the levels ofthe reporting component and the end-to-endautomation manager are appropriate. If the problempersists, contact your system administrator.

EEZR0011E The following parameters that shouldhave been passed to the job are missing:parameters

Explanation: Parameters that should have been passedto the job are missing, the connection to the databasecould not be established.


Operator response: Verify that you provided thecorrect parameters for the job.

EEZR0012E An error occurred: Exception text

Explanation: An error has occurred.


Operator response: Check the log for additionalinformation on the exception.

EEZR0013E The domain selected in the parameterdialog is currently not available.

Explanation: The domain of the selected resource iscurrently not available. Possible causes: 1) The domainis offline. 2) If it is an end-to-end automation domain,the end-to-end automation engine is not running. 3) Ifit is a first-level automation domain, the adapter isoffline or not configured for this end-to-end automationdomain.

System action: No report data for this report could becalculated.

Operator response: Make the domain available andre-run the report.

EEZR0014E The resource selected in the parameterdialog is currently not available.

Explanation: The resource you selected is currentlynot available, i.e. it is not included in the currentautomation policy of the domain. With the currentlyactive automation policy, the report for this resourcecannot provide calculated data.


Operator response: Activate an automation policy thatincludes the desired resource and re-run the report.

EEZR0015E An invalid number was specified for thenumber of displayed resources.

Explanation: A positive number must be specified forthe number of displayed resources.


Operator response: Specify a positive number for thenumber of displayed resources.

Prefix EEZR (Agentless Adapter)

EEZR0020E Resource: resource does not exist.

Explanation: A request was submitted against aresource that does not exist.

System action: The request was not processed.

Operator response: Check whether the resource exists.If it does not exist, the resource was removed. If itexists, re-submit the request.

EEZR0021E The domain name domain_policyspecified in the policy file does notmatch the domain namedomain_configured configured in theend-to-end automation managerconfiguration utility.

Explanation: The policy was not activated, becausethe domain names do not match.

System action: The policy was not activated.

Operator response: Make sure that the domain namein the policy file matches the configured domain name.

EEZR0036E The request request is not implemented.

Explanation: The request is currently not supported.

System action: The request was not accepted.

Operator response: Check whether a more recentversion of the automation adapter is available thatsupports the request.

EEZR0038E The request request submitted againstresource resource failed. The remotecommand returned with return codereturn_code.

Explanation: The remote command that is defined forthe request in the policy failed with a non-zero returncode.

System action: The request was not processedsuccessfully.

Operator response: Check the preceding messages todetermine why the command failed.



EEZR0039E It is currently not allowed to submit therequest request against resource resource .Reset the resource before you re-submitthe request.

Explanation: It is currently not allowed to submit therequest against the resource.


Operator response: Reset the resource before youre-submit the request.

EEZR0040E The authentication for user ID userfailed. The authentication error messageis: message

Explanation: The user ID and password could not beauthenticated on the system where the AgentlessAdapter is running for a reaosn other than credentialvalidation or expiration.

System action: No requests will be accepted for thisuser ID.

Operator response: Check the authentication errormessage to determine the reason for the failure. OnLinux or AIX operation systems, make sure that theconfigured Pluggable Authentication Module (PAM)service name is correct.

EEZR0041E The credential validation for user IDuser failed. The authentication errormessage is: message

Explanation: The user ID and password validationfailed on the system where the Agentless Adapter isrunning.


Operator response: Check the authentication errormessage to determine the reason for the failure. Makesure that the specified the user ID and password whichis configured for the Agentless Adapter domain iscorrect. Note that those entries are case-sensitive.

EEZR0042E The login for user ID user failed,because the user account expired. Theauthentication error message is: message

Explanation: The user account is expired.


Operator response: Ask the system administrator toreactivate the user account.

EEZR0043E The login for user ID user failed,because the password expired. Theauthentication error message is: message

Explanation: The password is expired.


Operator response: Ask the system administrator toreset the password.

EEZR0044E An unexpected error occurred. The errormessage is: error-message.

Explanation: The automation adapter detected anerror that cannot be handled.

System action: The request may not have beenprocessed.


EEZR0051E The request request was submittedagainst resource resource. The requestwas ignored, because another requestagainst this resource is already currentlybeing processed.

Explanation: Only one request at a time can beprocessed against a resource.


Operator response: Wait for the request that iscurrently being processed to complete. Check the stateof the resource to determine whether the request wassuccessful. Otherwise check the log file.

EEZR0060E Authentication failed when establishinga connection from local node localNodeto remote node remoteNode with user IDuserID using authenticationModeauthentication for resource resource name.

Explanation: The user credentials used are incorrect.The remote operation could not be completedsuccessfully.

System action: The resource status is set tonon-recoverable error. The processing is stopped untilthe resource is reset.

Operator response: Make sure that the usercredentials used to perform the remote operation arecorrectly defined in the end-to-end automationmanager configuration utility. In the SystemAutomation operations console reset the resource.



EEZR0061E A connection from local node localNodeto remote node remoteNode could not beestablished for resource resource name .The original error was: excMessage

Explanation: A connection between the local andremote node could not be established. Possible problemreasons are: 1) The hostname specified in the policy fileis incorrect. 2) The remote node is not online. 3) Afirewall between the local node and the remote nodeblocks the connection. The command on the remotenode could not be executed.

System action: For monitor commands, the attempt toestablish the connection is repeated periodically.

Operator response: Make sure that the local as well asthe remote node are known host names and that IPconnectivity between those two systems is correctly setup. Check whether network problems were reported atthe time where the failure occured.

EEZR0062E The connection from local nodelocalNode to remote node remoteNode waslost for resource resource name . Theoriginal error was: excMessage

Explanation: An error occurred when attempting toexecute a command on a remote node. The connectionbetween the local node and the remote target node waslost during the operation. The operation could not becompleted successfully.


Operator response: Make sure that IP connectivitybetween the local node and the remote node is set upcorrectly. The failure may also occur due to timeouts.Check the original exception message to determine theroot cause of the problem.

EEZR0063E An unexpected I/O Exception occurredwhen attempting to execute thecommand cmdName on remote noderemoteNode for resource resource name .The original error was: excMessage

Explanation: An error occurred when attempting toexecute a command on a remote node. Executing thecommand on the remote target node failed with anunexpected I/O exception. The remote execution couldnot be completed successfully.


Operator response: Make sure that the command onthe target node is defined correctly and accessible inread and execute mode. Check the original exceptionmessage to determine the root cause of the problem.

EEZR0064E An unexpected file not found exceptionoccurred when attempting to execute thecommand cmdName on remote noderemoteNode for resource resource name .The original error was: excMessage

Explanation: An error occurred when attempting toexecute a command on a remote node. The execution ofthe command on the remote target node failed with anunexpected file not found exception. The remoteexecution could not be completed successfully.



EEZR0065E An unexpected timout occurred whileexecuting the command cmdName onremote node remoteNode with the timouttimeout seconds for resource resourcename .

Explanation: An error occurred while executing acommand on a remote node. The execution of thecommand on the remote target node failed with anunexpected timeout. The remote execution could not becompleted successfully.


Operator response: Make sure that the command onthe target node and the timeout value are definedcorrectly.

EEZR0066E An unexpected permission deniedexception occurred when attempting toexecute the command cmdName onremote node remoteNode for resourceresource name . The original error was:excMessage

Explanation: An error occurred when attempting toexecute a command on a remote node. Executing thecommand on the remote target node failed with anunexpected permission denied exception. The remoteexecution could not be completed successfully.





EEZR0071E An error occurred while storing thepolicy file fileName on local nodelocalNode . The original error was:errMessage

Explanation: The policy file could not be storedsuccessfully in the policy pool on the node where theAgentless Adapter is located.

System action: No policy file was saved.

Operator response: Check if there is enough diskspace on the node where the Agentless Adapter islocated. Check the original exception message todetermine the root cause of the problem.

EEZR0072E An error occurred while reading thepolicy file fileName on local nodelocalNode . The original error was:errMessage

Explanation: The policy file could not be readsuccessfully from the policy pool on the node wherethe Agentless Adapter is located.

System action: No policy file was read.

Operator response: Check if the file exists on the nodewhere the Agentless Adapter is located. Check theoriginal exception message to determine the root causeof the problem.

EEZR0073E The policy could not be activatedbecause the policy file policyFile couldnot be found.

Explanation: The policy file does not exist in thepolicy pool on the node where the Agentless Adapter islocated.

System action: The policy is not activated.

Operator response: Verify that the policy file exists inthe policy pool.

EEZR0074E No automation policies are available inthe policy pool directory directory forautomation domain domain .

Explanation: There are no policy files with the domainname mentioned above in the policy pool directory.

System action: No policies are found.

Operator response: Check if the policy pool containspolicy files for the mentioned domain.

EEZR0075E The policy file fileName cannot bedeleted because the policy is currentlyactive.

Explanation: The file of the currently active policycannot be deleted.

System action: The policy file is not deleted.

Operator response: Deactivate the current policy. Thentry to delete the policy file again.

EEZR0076E An error occurred when intialization theremote node access information. Theconfiguration file ConfigurationFilecannot be opened or has syntax errors.

Explanation: The adapter requires this configurationfile in order to set up connections to other nodes.

System action: Initializing the remote node accessinformation failed.

Operator response: Make sure that the adapterconfiguration file exists and is correctly configured.

EEZR0077E No user credentials are configured forthe resource resource name .

Explanation: A user and password must be definedfor the node on which the resource is running or thecorresponding SSH private and public keys must beconfigured.

System action: The remote command is not exectued.

Operator response: Locate the resource in the policy.Either define a user and password value for the nodethat is related to that resource using the configurationutility or configure the SSH private and public keys forthat node and user.

EEZR0079E Unable to activate the policy filepolicyFile in the policy pool directorypolicyPool using the user ID request userid.

Explanation: Either the policy does not comply to theXML syntax or the policy did not pass the policysemantics checks.

System action: The policy cannot be activated. Theadapter will continue operation with its currentlyactivated policy.

Operator response: Check error messages logged forthis policy before this message. Resolve the error(s) andthen activate the policy again.

EEZR0080E Unable to determine the observed statefor resource resource name because theattribute name attribute name does notexist in attribute group attributeGroup .The managed system name of thecorresponding IBM Tivoli Monitoringresource is: ITM managed system name .

Explanation: In order to determine the observed stateof the resource, the agent attribute specified in thepolicy element MonitorAttribute is queried periodically.The attribute is specified in the form<AttributeGroup>.<AttributeName> in the policy



element MonitorAttribute. The AttributeGroup wasqueried successfully but the specified AttributeNamedoes not exist in the attribute group.

System action: The observed state cannot bedetermined. The resource is set to a fatal error state.The processing is stopped until the resource is reset.


EEZR0081E Unable to determine the observed statefor resource resource name . The querythat was sent to the IBM TivoliEnterprise Monitoring Server (TEMS) inorder to retrieve the value for thespecified agent attribute attribute namefailed. The managed system name of thecorresponding IBM Tivoli Monitoringresource is: ITM managed system name .

Explanation: In order to determine the observed stateof the resource, the agent attribute specified in thepolicy element MonitorAttribute is queried periodically.The attribute is specified in the form<AttributeGroup>.<AttributeName> in the policyelement MonitorAttribute. The corresponding SOAPrequest against the hub monitoring server to retrievethe value of the attribute failed. Check previousmessages to determine the reason.


Operator response: Check the messages to determinethe reason why the SOAP request failed.

EEZR0082E Unable to determine the observed statefor resource resource name . The querythat was sent to the IBM TivoliEnterprise Monitoring Server (TEMS) inorder to retrieve the value for thespecified agent attribute attribute namefailed. The following attribute filter hasbeen specified: attribute filter . Themanaged system name of thecorresponding IBM Tivoli Monitoringresource is: ITM managed system name .

Explanation: In order to determine the observed stateof the resource, the agent attribute specified in thepolicy element MonitorAttribute is queried periodically.The attribute is specified in the form<AttributeGroup>.<AttributeName> in the policyelement MonitorAttribute. In addition there is anattribute filter specified in the policy that limits thedata returned by the query. The corresponding SOAPrequest against the hub monitoring server to retrievethe value of the attribute failed. Check previousmessages to determine the reason.


Operator response: Check the messages to determinethe reason why the SOAP request failed.

EEZR0083E Unable to determine the observed statefor resource resource name because thequery to retrieve the specified agentattribute returned multiple results. Thequery that was sent to the IBM TivoliEnterprise Monitoring Server (TEMS) inorder to retrieve the contents of thespecified agent attribute group attributegroup succeeded. However, the result sethas multiple rows and an attribute valuecannot be determined unambiguously.The following attribute filter has beenspecified: attribute filter . The rowsreturned by the query are: query resultsThe managed system name of thecorresponding IBM Tivoli Monitoringresource is: ITM managed system name .

Explanation: In order to determine the observed stateof the resource, the agent attribute specified in thepolicy element MonitorAttribute is queried periodically.The attribute is specified in the form<AttributeGroup>.<AttributeName> in the policyelement MonitorAttribute. In addition there is anattribute filter specified in the policy that limits thedata returned by the query. The AttributeGroup wasqueried successfully but the query returned multiplerows. The query must return only one row in order tobe able to map an attribute value to an observed statefor the resource.


Operator response: Modify the policy and use theMonitorQueryAttrFilter element to limit the datareturned by the query to a maximum of one row. Thenreactivate the policy.

EEZR0084E In order to start or stop resource resourcename, the commandremoteSystemCommand was issued againstITM managed system name but returnedwith error code rc .

Explanation: The policy elements StartCommand andStopCommand specify the command that should beused to start or stop the resource using an IBM TivoliMonitoring agent. The command has been successfullysubmitted to the target managed system via the SOAPinterface provided by the IBM Tivoli EnterpriseMonitoring Server (TEMS). However, the commandreturned with a non zero return code. The commandmay have been rejected because the resource is in a



state for which the specified command is not valid.

System action: The command has not been executedsuccessfully. The resource is set to a fatal error state.The processing is stopped until the resource is reset.

Operator response: Check the log file of the IBMTivoli Monitoring agent to determine why thecommand did not return successfully. Reset theresource before resending the command.

EEZR0085E Unable to determine the observed statefor resource resource name because theattribute attribute name specified in theMonitorAttribute policy element has aninvalid format.

Explanation: In order to determine the observed stateof the resource, the agent attribute specified in thepolicy element MonitorAttribute is queried periodically.The attribute is specified in the form<AttributeGroup>.<AttributeName> in the policyelement MonitorAttribute. The attribute group and theattribute name within that group must be separated byexactly one dot.



EEZR0086E Unable to determine the observed statefor resource resource name because theIBM Tivoli Monitoring agent is notrunning. The managed system name ofthe corresponding IBM TivoliMonitoring resource is: ITM managedsystem name .

Explanation: In order to determine the observed stateof the resource, the agent attribute specified in thepolicy element MonitorAttribute is queried periodically.The query returned no results because thecorresponding IBM Tivoli Monitoring agent was offline.

System action: The observed state cannot bedetermined. The resource is set to an error state.

Operator response: Start the IBM Tivoli Monitoringagent corresponding to the specified managed systemname.

EEZR0087E Unable to determine the observed statefor resource resource name because thespecified managed system name doesnot exist. The managed system name ofthe corresponding IBM TivoliMonitoring resource is: ITM managedsystem name .

Explanation: In order to determine the observed stateof the resource, the agent attribute specified in thepolicy element MonitorAttribute is queried periodically.The corresponding SOAP request against the hubmonitoring server failed because the managed systemname of the IBM Tivoli Monitoring resource does notexist. The managed system name is specified in thepolicy in the node attribute of the Resource element.


Operator response: Modify the managed system nameof the resource in the policy, so that an existingmanaged system name is specified. Then reactivate thepolicy.

EEZR0504W The location of the automation policypool location was not found on nodenode.

Explanation: When trying to show the list of availablepolicies, the policy pool location was not found on thenode where the adapter currently runs.

System action: No policies for activation are provided.

Operator response: Use the configuration utility tospecify the correct 'Policy pool location', which is thedirectory where the automation policy files are storedfor activation.

EEZR0601I The resource resource has already therequested state requested state.

Explanation: The request failed, because the requestedresource state and the current resource state are thesame.


Operator response: No further action is required,because the resource is already in the requested state.

EEZR0602I The resource resource can only be reset ifthe compound state is Fatal. Thecompound state of the resource iscurrently compound state and theoperational state is operational state .

Explanation: The reset request was rejected becausethe resource can only be reset if the compound state isFatal. The compound state is Fatal if the operationalstate implies that an operator intervention is required.

System action: The reset request was not processed.

Operator response: No further action is required,because the resource is not in compound state Fatal.

EEZR0085E • EEZR0602I


EEZR0610I The reset request was submitted againstresource resource by user ID userid toresolve a non-recoverable error.

Explanation: A resource in a non-recoverable errorstate is not monitored until the resource is reset. Theuser submitted a reset request for the resource to makeit eligible for monitoring again.

System action: The reset request was submittedagainst the resource and monitoring of the resourcewas started again.

Operator response: Verify that the resource does notshow any errors in the System Automation operationsconsole.

EEZR0611I The request request was submittedagainst resource resource using remoteuser ID target userid and requesting userID request userid . Comment: comment

Explanation: A user submitted a request to change theresource state.

System action: The request was submitted against theresource on the target node.

Operator response: Verify that the resource changesits state in the System Automation operations console.

EEZR0612I The policy was activated by user IDrequest userid using the policy filepolicyFile located in the policy pooldirectory policyPool .

Explanation: A user activated a new policy.

System action: The requested policy is activated. Theadapter starts monitoring the resources that are definedin the policy.

Operator response: Verify that the resources definedin the policy are displayed in the System Automationoperations console.

EEZR0613I The policy was deactivated by user IDrequest userid . The active policy file waspolicyFile located in the policy pooldirectory policyPool .

Explanation: A user deactivated the currently activepolicy.

System action: The active policy is deactivated. Theadapter no longer monitors the resources that aredefined in the deactivated policy.

Operator response: Verify that no resources defined inthe deactivated policy are displayed in the SystemAutomation operations console.

EEZR0614I During the adapter startup, a policy wasautomatically activated using the policyfile policyFile located in the policy pooldirectory policyPool .

Explanation: When the adapter was started, itautomatically activated the policy that was previouslyactive.

System action: The requested policy is activated. Theadapter starts monitoring the resources that are definedin the policy.

Operator response: Verify that the resources definedin the policy are displayed in the System Automationoperations console.

Prefix EEZS

EEZS0001E Not a recognized flag:command_flag_name.

Explanation: An unsupported flag or an incorrectcombination of flags was specified.

System action: The command ends withoutprocessing.

Operator response: Refer to the usage statement for alist of valid flags. Correct the command and run itagain.

EEZS0003E An incorrect combination of flags or anincorrect flag and operand combinationwas specified.

Explanation: The combination of the specified flags orthe specified flag and operand combination is notallowed.


Operator response: Refer to the usage statement for alist of valid flags, operands, and flag-operandcombinations. Correct the command and run it again.

EEZS0005E The flag_name flag requires an operand.

Explanation: The indicated flag must be specified withan operand when using this command.


Operator response: Check the command syntax andissue the command again.

EEZS0006E The specified policy could not beactivated because it contains noresource/because it is empty.

Explanation: In order to be activated, a policy must

EEZR0610I • EEZS0006E


contain at least one resource. The specified policy isempty.

System action: The policy could not be activated.Processing ends.

Operator response: Specify a non-empty policy andrun the command again.

EEZS0007E Unknown command command_name.

Explanation: An unknown command was specified onthe command line.


Operator response: Use the help command for a listof possible commands. Note that commands arecase-sensitive.

EEZS0008E An invalid number of operands wasspecified.

Explanation: The command was called with an invalidnumber of operands.


Operator response: Refer to the usage statement for alist of valid operands. Correct the command and run itagain.

EEZS0009E Invalid operand operand_name.

Explanation: An invalid operand was specified.


Operator response: Refer to the usage statement for alist of valid operands. Correct the command and run itagain.

EEZS0010E An invalid quoted string was specified.

Explanation: An opening or closing quotation mark ismissing or the specified quotation mark characters donot match.


Operator response: Correct the command and run itagain.

EEZS0011E The command command_name is notsupported by the currently connecteddomain of type domain_type.

Explanation: The requested command cannot beexecuted. The connected domain type does not supportthis command.


Operator response: Issue 'help' to see whichcommands are supported by the currently connecteddomain.

EEZS0012E This command is not supported by thecurrently connected domain with namedomain_name.

Explanation: The action cannot be executed. Thecapabilities of the connected domain does not supportthis action.


Operator response: Check the domain capabilities byissuing 'lseezdom -Ab -n domain_name' to see thesupported capabilities of the currently connecteddomain.

EEZS0013E The resource resource_name does notexist.

Explanation: The specified resource name does notexist.


Operator response: Check the resource name andissue the command again.

EEZS0014E The request to set a role requires thespecification of a new role name.

Explanation: The required role name does not exist.


Operator response: Review help text for thiscommand. Issue the command again and specify therequested role name.

EEZS0015E The specified timeout value {0} is notvalid.

Explanation: The timeout value has to be specified aspositive numeric value in seconds, with a maximumvalue of 2147483647.


Operator response: Issue the command again andspecify a valid timeout value.

EEZS0016E The command can not be executed,since no domain is contacted.

Explanation: This command requires a connectedautomation domain.


Operator response: Open a command shell again andspecify an online automation domain to be contacted.

EEZS0007E • EEZS0016E


EEZS0017E Timeout parameter cannot be used inconjunction with restart option.

Explanation: Timeout option is not supported inconjunction with restart option.


Operator response: Issue the command again andspecify the command without timeout option.

EEZS0018E The node resource_name does not exist.

Explanation: The specified node does not exist.


Operator response: Check the node name and issuethe command again.

EEZS0019E The request to move the resource toanother node requires the specificationof node name.

Explanation: The required node name does not exist.


Operator response: Review help text for thiscommand. Issue the command again and specify therequested node name.

EEZS0020E The request to move the resource is notsupported by group class of thespecified resource.

Explanation: The group class of the specified resourcedoes not support move operation.


Operator response: Review help text for thiscommand. Issue the command again and specify thecorrected resource name.

EEZS0185E None of the specified resources exists.

Explanation: No matching resources were found.


Operator response: Check the selection string orresource names and issue the command again.

EEZS0207E No relationships exist between thesource resource source_resource_name andthe target resource target_resource_name

Explanation: No relationships exist between thespecified resources.


Operator response: Issue the command again withexisting target resources for the source.

EEZS0223E No relationships were found for thespecified source resourcesource_resource_name

Explanation: The source resource is not associatedwith any existing relationship.


Operator response: Check the source resources andissue the command again.

EEZS0224E No relationships were found for thespecified target resourcetarget_resource_name

Explanation: The target resource is not associated withany existing relationship.


Operator response: Check the target resources andissue the command again.

EEZS0225E The requested command cannot besuccessfully processed in line mode,because no credentials are available foraccessing the zEnterprise HMC.

Explanation: To run the command shell in line mode,and accessing information from the zEnterprise HMC,functional credentials need to be available.

System action: Command ends.

Operator response: Use the end-to-end automationmanager configuration dialog to specify the requiredauthentication for the hardware adapter zEnterpriseHMC access.

EEZS0227E None of the specified source or targetresources exists.

Explanation: The source or target resources used toquery the relationships do not exist.


Operator response: Issue the command again with atleast one existing source resource.

EEZS0344E No relationships are defined in thepolicy.

Explanation: No relationships were found in thepolicy.


Operator response: Activate a policy that containsrelationships and issue the command again.



EEZS0345E The policy policy_file_name was notfound in the policy pool.

Explanation: No policy with the specified name hasbeen found in the configured policypool directory. Onlypolicies which are located in the policy pool directoryand are designed for the current active domain can beactivated. Onl


Operator response: Activate a policy for this domainfound in the policy pool directory.

EEZS0100I The policy policy_file_name has beenactivated.

Explanation:

System action:

Operator response:

EEZS0101I The policy policy_file_name has beendeactivated.

Explanation:

System action:

Operator response:

EEZS0102W No policy is currently active.

Explanation: Currently the automation manager isidling because no policy is active.


Operator response: Activate an automation policy asneeded.

EEZS0103E The policy policy_file_name was notfound in the policy poolpolicy_pool_directory.

Explanation: A policy with the specified file name wasnot found. Information about the policy cannot bedisplayed.


Operator response: Check the policy name and issuethe command again.

EEZS0104I The domain domain_name returnednumber_of_policies policies available foractivation.

Explanation:

System action:

Operator response:

EEZS0105E The domain domain_name returned nopolicies available for activation.

Explanation: The automation domain did not returnany policy which can be listed or activated.


Operator response: Check the contents of theconfigured policy pool directory. Ensure that at leastone policy file is available. Check the contents of thepolicy file and ensure that the policy you intend to listor to activate has been configured for the current activedomain name.

EEZS0110E The domain domain_name does not exist.

Explanation: The query for the specified domainreturned no value.


Operator response: Check the domain name and issuethe command again.

EEZS0112E The currently connected End-to-Enddomain has no resource referencesdefined to any known first levelautomation domain.

Explanation: Unable to get a list of referenceddomains.


Operator response: Check that an End-to-Endautomation policy is active. Make sure that at least onereferenced first level automation domain has beenjoined.

EEZS0111I Listing information for domaindomain_name.

Explanation:

System action:

Operator response:

EEZS0114E The following problem was encounteredprocessing command command_name :problem_details

Explanation: An unexpected problem has beenencountered.


Operator response: Evaluate the problem details andissue the command again.



EEZS0120I Using domain domain_name.

Explanation:

System action:

Operator response:

EEZS0121W Unable to connect to the automationdomain.

Explanation: If you specified the -D flag: a matchingautomation domain could not be found, or it is not instate Online. If you did not specify the -D flag: theautomation manager currently does not host anyend-to-end automation domain which is in stateOnline. Only a limited set of commands work in thissituation.


Operator response: Verify if the automation domainname is spelled correctly. Verify if the automationdomain is in the expected state using the commandlseezdom -Ab. If needed, restart the end-to-endautomation engine or the automation adapter.

EEZS0122E Unable to contact the automationmanager on server: server_name usingport: port_number

Explanation: The command shell is unable to contactthe automation manager.

System action: The command shell ends.

Operator response: Verify that the automationmanager is running on the specified host and checkthat the port number is correct.

EEZS0123E Unable to authenticate to theautomation manager on server:server_name with the specified user IDand password.

Explanation: The command shell was unable to opena session with the specified automation managerbecause a security exception was received.


Operator response: Check the user ID and passwordyou are using to contact the automation manager.Verify that the user ID has sufficient rights to access theautomation domain.

EEZS0124E The following exception occurred whileconnecting to server_name: exception_text

Explanation: The command shell is unable to contactthe server because a connection exception was received.


Operator response: Check the exception message forfurther information.

EEZS0125E You are not allowed to perform thecommand: command. Problem details:problem_details

Explanation: The user is not in the required role thatis needed to perform the command.


Operator response: Evaluate the problem details todetermine which role is required. Modify the user's roleconfiguration. For example, add the user to theappropriate user group.

EEZS0126E Unable to authenticate to theautomation domain: domain_name withthe specified user ID and password.

Explanation: The command shell was unable to opena session with the specified automation domainbecause a security exception was received.


Operator response: Check the user ID and passwordyou are using to contact the automation domain. Verifythat the user ID has sufficient rights to access theautomation domain.

EEZS0127E Unable to establish access to theautomation domain with the specifieduser ID and password.

Explanation: The command shell was unable to opena session with automation domain because an accessexception was received.


Operator response: Check the current domain statewith lseezdom. Check the user ID and password youare using to contact the automation domain. Verify thatthe user ID has sufficient rights and roles to access theSA Application Manager and the specified automationdomain.

EEZS0128E Unable to authenticate to theautomation domain: domain_name to runspecified command in line mode. UserID and password must be specified.

Explanation: The command shell was unable to opena session with the specified automation domain in linemode. No user ID and password have been specified.

System action: The command shell ends withoutexecuting the specified command in line mode.

Operator response: The current configuration of thecommand shell requires the specification of user ID andpassword with help of the flags -du and -dp for every

EEZS0120I • EEZS0128E


command you run in line mode. If you do not want tospecify these parameters with every commad you needto configure this mode with help of cfgeezdmn.

EEZS0130E Unknown request action: action_name.

Explanation: The specified request action is notsupported.

System action: The command cannot be executed.

Operator response: Correct the action string and issuethe command again.

EEZS0131E The target value: new_target_value is nota numeric or not in the valid range. Ithas to be a numeric value between 1and number of members.

Explanation: The specified target value is not in validrange.


Operator response: Correct the target value and issuethe command again.

EEZS0131I The request_name request has beenissued against resource resource_name.

Explanation:

System action:

Operator response:

EEZS0132I The request to set the role role_name hasbeen issued against resourceresource_name.

Explanation:

System action:

Operator response:

EEZS0133I The request to set availability targettarget_value has been issued againstresource resource_name.

Explanation:

System action:

Operator response:

EEZS0133E Found number of resources which matchthe name resource_name.

Explanation: An ambiguous resource name wasspecified as target for the request.


Operator response: Clarify the resource name by

using the full qualified signature class:name:node andissue the command again.

EEZS0134I Waiting for the specified timeout of {0}seconds for the request to be completed.

Explanation:

System action:

Operator response:

EEZS0135I The specified request has beencompleted after {0} seconds.

Explanation:

System action:

Operator response:

EEZS0136I The specified request has timed out.

Explanation:

System action:

Operator response:

EEZS0137I A command to {0} the node {1} has beenissued.

Explanation:

System action:

Operator response:

EEZS0140I The resource resource_name has been setas the new preferred member of choicegroup choice_group_name.

Explanation:

System action:

Operator response:

EEZS0150E Unable to obtain data from the localautomation manager.

Explanation: The command shell was unable to obtaindata from the automation manager on the local server.


Operator response: Verify that the automationmanager is running on the specified host and verifythat the WebSphere Application Server is running.



EEZS0151E The following exception occurred whilecontacting the automation managerexception_text

Explanation: The command shell is unable to retrievedata from the automation manager because anexception was received.



EEZS0152W Received invalid clusterset clustersetnamefrom the local automation manager.

Explanation: The command shell received an invalidclusterset name from the automation manager on thelocal server.

System action: The command continues processing,but no information about this clusterset can be shown.

Operator response: Verify that the policy is valid andactivated correctly.

EEZS0153E Domain name domain_name of theautomation manager is not equal to thedomain name object_domain_name of thedomain object received by theautomation manager.

Explanation: The command shell obtainedincompatible data from the automation manager on thelocal server.


Operator response: Verify that the policy is valid andactivated correctly.

EEZS0154I Are you sure you want to issue thecommand poweroff? Yes (y) or No (n) ?

Explanation:

System action:

Operator response:

EEZS0155W An invalid process ID process ID wasspecified.

Explanation: A process ID was specified that is not avalid integer.

System action: The command continues processing.

Operator response: Specifiy a valid integer process ID.

EEZS0156E Sending the request request-content to theautomation manager returned withinvalid data.

Explanation: The data returned by the automationmanager when processing the request is invalid.

System action: Command processing ends.

Operator response: Verify that the automationmanager is running on the specified host and verifythat the WebSphere Application Server is running.

EEZS0157E Sending the request request-content to theautomation manager returned with anerror.

Explanation: The automation manager was not able toprocess this request.

System action: Command processing ends.

Operator response: Check the log files of theautomation manager for more detailed information.

EEZS0158E The following exception occurred whentrying to write return data to file filename: exception_text

Explanation: The command shell is unable to write itsreturn data to the output file because an exception wasreceived.

System action: Command processing continues.


EEZS0159E The following exception occurred whiletrying to send a signal exception_text

Explanation: The command shell is unable to send asignal to the process that called it.

System action: Command processing continues.


EEZS0160E The clusterset clusterset_name does notexist.

Explanation: The query for the specified clustersetreturned no value.


Operator response: Check the clusterset name andissue the command again.



EEZS0161I No clusterset found.

Explanation: The query for clustersets returned novalue.


Operator response: Check the active policy forclusterset definitions and issue the command again.

EEZS0208I Showing information for policy:policy_file_name

Explanation:

System action:

Operator response:

EEZS0220I Resource information has been dumpedto: dump_file_name

Explanation:

System action:

Operator response:

EEZS0221E No event statistic available.

Explanation: No events have been received from anyautomation domain.


Operator response: At least one first level automationdomain has to be configured to contact the SAApplication Manager. The Automation Adapter has tobe started on the domain. Check IP configurations andports of Automation Adapter and SA ApplicationManager to resolve problems with sending/receivingevents.

EEZS0222E Operation operation_name not supportedby domain.

Explanation: Operation not supported by domaincapabilities.


Operator response: The domain you are connected todoes not support this operation.

EEZS0233E No event statistic for automationdomain domain_name available.

Explanation: No event statistic can be shown for thespecified domain.


Operator response: Check that you spelled thedomain name correctly. Check if the domain is knownby using the command lseezdom. If the domain isreturned in the list of known domains (shown with

command lseezdom) then no new events have beenreceived from this domain since the SA ApplicationManager has been started. If the domain is not shownin the list of known domains and it is spelled correctlythen you should check the adapter configuration of thatspecific domain and verify that correct SA ApplicationManager connection parameters have been specified.Check the connection from the adapter to the SAApplication Manager host.

EEZS0240I Already connected to domaindomain_name.

Explanation: The current connected domain is thesame as specified as argument to this command.

System action: Command ends. This command shellsession stays connected to the above mentioneddomain.

Operator response: If you want to switch to anotherautomation domain specify the correct name of thisnew domain. Domain names can be checked by usingthe command lseezdom. It is not possible to connect toan automation domain using a different user name asthe one specified the first time you connected to thisdomain. If you need to use another user name youhave to stop this command shell session first, restarteezcs and connect to this automation domain using thenew user name.

EEZS0241E Specify only one domain name toconnect to.

Explanation: This command only allows to connect toone automation domain at a time.

System action: Command ends. This command shellsession stays connected to current connectedautomation domain.

Operator response: If you want to switch to anotherautomation domain specify the correct name of thisnew domain. Domain names can be checked by usingthe command lseezdom. If domain name containsspaces you must enclose the name in quotes.

EEZS0234E The node node_name was not found inthe automation domainautomation_domain.

Explanation: A node with the specified name was notfound. Unable to process the command.


Operator response: Check the node name and issuethe command again.

EEZS0161I • EEZS0234E


EEZS0250E The specified source value node_name forthis request is not allowed.

Explanation: You can optionally specify one of thefollowing sources: operator, extsched or automation.

System action: Processing ends. Request will not beissued against the resource.

Operator response: Specify a valid source. Thespecification of a source is optional and defaults tooperator.

EEZS0260E The specified target value target_valuefor this chtarget call is invalid.

Explanation: The new target value has to be a positivenumeric value. It has to be greater than 0 and less orequal to the total number of group members.

System action: Processing ends. Request will not beissued against the resource.

Operator response: Specify a valid target value.

Prefix EEZT

EEZT0001W SA detected a domain status change indomain domainName . Domain status isdomainStatus .

Explanation: The status of this automation domainhas changed.


Operator response: Verify that the new state isintended for this automation domain.

EEZT0002I SA received a domain join event fromdomain domainName and processed thatevent successfully.

Explanation: This automation domain has successfullyjoined to System Automation.



EEZT0003W SA received a domain leave event fromdomain domainName and processed thatevent successfully.

Explanation: This automation domain has successfullyleft System Automation.



EEZT0004E SA cannot communicate with theautomation adapter on IP addressipAddress .

Explanation: An automation adapter was started andit tried to join to System Automation. The join attemptfailed because System Automation cannot communicatewith the automation adapter. Possible cause of theproblem is: a firewall could be preventingcommunication with this domain, or SSLcommunication is required to be setup forcommunication with the automation adapter.


Operator response: Determine the cause of thecommunication problem. For example, a firewall couldbe preventing that kind of communication.

EEZT0005E SA encountered a security problemwhile trying to access domaindomainName .

Explanation: System Automation cannot access thisautomation domain. This is caused by a securityproblem. Either the EEZAutomationManager does nothave the required authorization, or some credential thatis used by the end-to-end automation engine is invalid.For example, the password may have expired.


Operator response: Ensure that the user credentials inthe configuration of the automation engine are correct.If you modified the credentials refresh the automationengine using the Refresh button on the ApplicationManager tab of the System Automation ApplicationManager Configuration dialog or using thecorresponding option in silent configuration mode(cfgeezdmn command).

EEZT0006I SA domain domainName has activated anew policy. The filename of the policyis policyFileName .

Explanation: A new policy has been activated for thisautomation domain.


Operator response: Verify that the action is intendedfor this automation domain.

EEZT0007E SA domain domainName has encountereda severe problem. Check the SAApplication Manager end-to-endautomation domain log file on serverserverHostName for details.

Explanation: See message.


EEZS0250E • EEZT0007E


Operator response: Check the automation domain logfile for details.

EEZT0008I SA domain domainName no longerrequires someone to check its log file.

Explanation: An operator has inspected the logfile.



EEZT0009W SA detected a problem in domaindomainName . The resource referenceresourceName is unknown.

Explanation: The resource reference definition in theend-to-end automation policy does not match anyresource in the specified automation domain. Possiblecauses of this problem are: 1) the end-to-endautomation policy is incorrect, possibly caused by aspelling error. 2) the resource does not or does not yetexist in the specified automation domain.


Operator response: Verify the correctness of theresource reference definition in the policy. Verify thatthe referenced resource exists in the automationdomain.

EEZT0010I SA changed the preferred member ofresource group groupName in domaindomainName as requested.




EEZT0011W SA detected a domain communicationstatus change in domain domainName .Domain communication status iscommunicationState . Domain status isdomainState .

Explanation: The communication state for thisautomation domain has changed.



EEZT0012W SA domain domainName no longer hasan active policy.

Explanation: The automation policy has beendeactivated for this automation domain.


Operator response: Verify that the action is intendedfor this automation domain.

EEZT0013E SA detected a problem in domaindomainName . The resource referenceresourceName is unable to contact thereferenced resource. An operator needsto reset the resource reference manually.

Explanation: The operational state of the resourcereference indicates that an operator needs to fix someproblem and then reset the resource reference manually.


Operator response: Inspect the message log of theend-to-end automation domain in order to find thereason the resource reference is broken. Once the rootcause of the problem is fixed, reset the resourcereference.

EEZT0014W SA suspended automation for resourceresourceName in domain domainName .

Explanation: An operator requested suspendingautomation for this resource.

System action: If this resource is a resource reference,the end-to-end automation manager no longer sendsrequests or orders to its referenced resource. If thisresource is a resource group, the end-to-end automationmanager no longer sends requests or orders to itsmembers.

Operator response: If required, resume automation forthis resource.

EEZT0015I SA resumed automation for resourceresourceName in domain domainName .

Explanation: An operator requested resumingautomation for this resource.

System action: If this resource is a resource reference,the end-to-end automation manager sends requests ororders to its referenced resource if required. If thisresource is a resource group, the end-to-end automationmanager sends requests or orders to its members ifrequired.

Operator response: If required, suspend automationfor this resource.

EEZT0016I SA changed the desired role for resourceresourceName in domain domainName tonewDesiredRoleName .

Explanation: The desired role of an SA resourcechanged.

System action: The end-to-end automation managersends related orders to the referenced resources.

Operator response: If the new desired role is notappropriate, change the desired role of the resourceagain.

EEZT0008I • EEZT0016I


EEZT0017I SA detected that the observed role forresource resourceName in domaindomainName has changed tonewObservedRoleName .

Explanation: The observed role of an SA resourcechanged.

System action: The end-to-end automation managerconsiders the new role in its future automationdecisions.


EEZT0750W SA event with unknown reason indomain domainName .




EEZT0753I SA automation manager startedsuccessfully.




EEZT0754W SA automation manager stoppedsuccessfully.



Operator response: Verify that the automationmanager was stopped intentionally.

EEZT0756I SA detected a new configuration indomain domainName . New request forresource resourceName with action actionand source source created.




EEZT0758I SA detected a deleted configuration indomain domainName . Request forresource resourceName with action actionand source source deleted.




EEZT0759W SA detected a status change of resourceresourceName in domain domainName .Common observed state:CommonObservedState, Common desiredstate: CommonDesiredState, Commonoperational state:CommonOperationalState, Commoncompound state: CommonCompoundState

Explanation: The state of this automation resource inthe specified automation domain has changed.


Operator response: Verify that the new state isintended for this automation resource.

EEZT0770I SA started the automation of resourceresourceName in domain domainName .Common observed state:CommonObservedState, Common desiredstate: CommonDesiredState, Commonoperational state:CommonOperationalState, Commoncompound state: CommonCompoundState

Explanation: This resource is now under control ofSystem Automation.



EEZT0771I SA completed the automation ofresource resourceName in domaindomainName . Common observed state:CommonObservedState, Common desiredstate: CommonDesiredState, Commonoperational state:CommonOperationalState, Commoncompound state: CommonCompoundState

Explanation: This resource is no longer under controlof System Automation.



EEZT0778I SA set the resource resourceName onlineas requested in domain domainName .Common observed state:CommonObservedState, Common desiredstate: CommonDesiredState, Commonoperational state:CommonOperationalState, Commoncompound state: CommonCompoundState

Explanation: System Automation has set the resourceonline successfully.





EEZT0779I SA set the resource resourceName offlineas requested in domain domainName .Common observed state:CommonObservedState, Common desiredstate: CommonDesiredState, Commonoperational state:CommonOperationalState, Commoncompound state: CommonCompoundState

Explanation: System Automation has set the resourceoffline successfully.



EEZT0786W SA detected a warning in domaindomainName . The resource resourceNamehas problems caused by a dependencyto another resource. Common observedstate: CommonObservedState, Commondesired state: CommonDesiredState,Common operational state:CommonOperationalState, Commoncompound state: CommonCompoundState

Explanation: An automation operation on thespecified resource cannot be performed because itdepends on another resource which prevents theoperation.


Operator response: Inspect the status of the resourceson which the specified resource depends.

EEZT0789E SA detected a problem in domaindomainName . The resource resourceNamecannot be set to the requested state.Common observed state:CommonObservedState, Common desiredstate: CommonDesiredState, Commonoperational state:CommonOperationalState, Commoncompound state: CommonCompoundState

Explanation: An automation operation on thespecified resource cannot be performed.


Operator response: Inspect the individual status fieldsof this resource.

EEZT0790E SA detected a problem in domaindomainName . The resource resourceNameneeds a manual reset by the operator.Common observed state:CommonObservedState, Common desiredstate: CommonDesiredState, Commonoperational state:CommonOperationalState, Commoncompound state: CommonCompoundState

Explanation: An automation operation on thespecified resource cannot be performed.


Operator response: Reset the automation resourcemanually. Invoke the operation reset from broken in theoperation console.

EEZT0791I Interaction between GDPS and SystemAutomation Application Managerstarted successfully.

Explanation: Interaction between GDPS and SystemAutomation Application Manager started.



EEZT0792I Interaction between GDPS and SystemAutomation Application Managerstopped successfully.

Explanation: Interaction between GDPS and SystemAutomation Application Manager stopped.


Operator response: Verify that either the interactionwas stopped intentionally, either through stopping theSystem Automation Application Manager, or throughdeactivating or replacing the disaster recovery policy.

EEZT0793I The System Automation ApplicationManager is alive.

Explanation: Heartbeat event sent from SystemAutomation Application Manager to GDPS.



EEZT0794I The System Automation ApplicationManager request completed with returncode return code and reason code reasoncode. The original message text is:Original message text.

Explanation: A request was completed by the SystemAutomation Application Manager.




Operator response: Analyze the return code, reasoncode and the original message.

EEZT0800E SA detected that domain domainNamefailed.

Explanation: No commands can be sent to the domainand no events are received from the domain. Thisindicates a domain failure.


Operator response: Check the domain.

EEZT0801I SA detected that domain domainNamehas recovered from a failure and isonline and operational again.

Explanation: SA detected that the domain hasrecovered from a domain failure. The domain is onlineand operational again.


Operator response: Check the domain.

EEZT0802E SA detected that node nodeName failedin domain domainName .

Explanation: No commands can be sent to the nodeand no events are received from the node. Thisindicates a node failure.


Operator response: Check the node.

EEZT0803I SA detected that node nodeName hasrecovered from a failure and is onlineand operational in domain domainNameagain.

Explanation: SA detected that the node has recoveredfrom a node failure. The node is online and operationalagain.


Operator response: Check the node.

EEZT0804E SA detected that business criticalresource resourceName failed in domaindomainName .

Explanation: No commands can be sent to theresource and no events are received from the resource.This indicates a resource failure.


Operator response: Check the resource.

EEZT0805I SA detected that the business criticalresource resourceName has recoveredfrom a failure and is online andoperational in domain domainNameagain.

Explanation: SA detected that the resource hasrecovered from a failure. The resource is online andoperational again.


Operator response: Check the resource.

Prefix EEZU

EEZU0001E The following RuntimeExceptionoccurred: Exception text

Explanation: The processing was interrupted by aRuntimeException and cannot complete correctly.



EEZU0002E The following error occurred whilewriting file filename : Exception text

Explanation: The processing was interrupted by anerror and cannot complete correctly.


Operator response: Check the error details and retrythe operation.

EEZU0003E The following error occurred whilereading file filename : Exception text

Explanation: The processing was interrupted by anerror and cannot complete correctly.


Operator response: Check the error details and retrythe operation.

EEZU0004E An error has occurred while accessingthe end-to-end automation manager:Exception text

Explanation: An error has occurred while accessingthe end-to-end automation manager componentrunning on the management server. The requestedaction could not be processed. Possible causes: 1) Themanagement server is down. 2) The automation JEEframework (Enterprise application EEZEAR) is notstarted. 3) The are some inconsistencies regarding thelevel of the operations console and the end-to-endautomation manager.

EEZT0800E • EEZU0004E


System action: The requested action is cancelled.

Operator response: Ensure that the managementserver is up and running. Check that the enterpriseapplication EEZEAR is started. Verify that the levels ofthe operations console and the end-to-end automationmanager are appropriate. Refer to the 'Related errors'section for more details about the problem. If theproblem persists, contact your system administrator.

EEZU0005E The credential vault service was notfound or could not be loaded: Exceptiontext

Explanation: The credential vault cannot be accessedbecause the corresponding service was not found orcould not be loaded due to an initialization error.



EEZU0006E The page with the ID Page UID couldnot be found: Exception text

Explanation: The application tried to load the pagewith the specified ID to display the log data. However,the page with this ID could not be found.

System action: The application continues, but the logdata cannot be displayed.


EEZU0007E The credential vault cannot be accessed:Exception text

Explanation: Possible causes: 1) The credential vault isnot accessible for technical reasons. 2) The credentialvault is not accessible for security reasons.


Operator response: Evaluate the error details andcheck if one of the possible causes applies.

EEZU0008E The credential secret for automationdomain Automation domain name is notset: Exception text

Explanation: A user credential for a certainautomation domain was requested but is not set for theuser.


Operator response: Logout and login again.

EEZU0010E Unable to receive events from theend-to-end automation manager. Thefollowing error occurred while trying toread an event: Exception text

Explanation: An error has occurred while trying toaccess the event path to the management server. Theoperations console is not able to receive any events andis therefore not able to update the status informationfor resources if the status changes. Possible causes: 1)The management server is down. 2) The JMS service ofthe management server is not working properly. 3) TheJMS topic used for sending events is not available

System action: Processing continues, but no eventscan be received.

Operator response: Ensure that the managementserver is up and running. Check that the JMS service ofthe management server is setup correctly and that theJMS topic used for sending events is available. If theproblem persists, contact your system administrator.

EEZU0011E Unable to set up the event path betweenthe operations console and themanagement server: Exception text

Explanation: The connection to the right JMS serviceon the management server could not be established.This connection is used to receive events about statuschanges from the end-to-end automation manager.Possible causes: 1) The management server is down. 2)The JMS service of the management server is notworking properly. 3) The JMS topic used for sendingevents is not available



EEZU0012E An error occurred trying to look up theJMS service on the management serverto establish the event path: Exception text

Explanation: An error has occurred while trying toaccess the management server. Possible causes: 1) Themanagement server is down. 2) The JMS service of themanagement server is not working properly. 3) TheJMS topic used for sending events is not available



EEZU0005E • EEZU0012E


EEZU0013E An error has occurred while trying toestablish the connection to theend-to-end automation manager:Exception text

Explanation: An error has occurred while connectingto the end-to-end automation manager componentrunning on the management server. Possible causes: 1)The management server is down. 2) The automationJEE framework (Enterprise application EEZEAR) is notstarted. 3) The are inconsistencies regarding the level ofthe operations console and the end-to-end automationmanager. 4) You are not authorized to access theautomation JEE framework.


Operator response: Ensure that the managementserver is up and running. Check that the enterpriseapplication EEZEAR is started. Ensure that you havethe right permissions. Also verify that the levels of theoperations console and the end-to-end automationmanager are appropriate. Refer to the 'Related errors'section for more details about the problem. If theproblem persists, contact your system administrator.

EEZU0015E The log data cannot be displayedbecause the service to launch a newpage was not found or could not beloaded.

Explanation: The log data is normally displayed on anew page within the Dashboard Application ServicesHub, but the service to launch a new page was notfound or could not be loaded due to an initializationerror.

System action: The application continues, but the logdata cannot be displayed.


EEZU0016E An error occurred trying to look up theautomation JEE framework to connect tothe end-to-end automation manager:Exception text

Explanation: An error has occurred while trying tolook up the automation JEE framework's Session Beansthat are part of the Enterprise application EEZEAR.Possible causes: 1) The management server is down. 2)The automation JEE framework (Enterprise applicationEEZEAR) is not started or is not deployed correctly.


Operator response: Ensure that the managementserver is up and running. Check that the enterpriseapplication EEZEAR is started. If the problem persists,contact your system administrator.

EEZU0017E There is no log data available forautomation domain Automation domain .

Explanation: No log file exists for the automationdomain. The log file is normally located on the nodewhere the automation domain's automation adapter isrunning, or if it is the end-to-end automation domain,where the end-to-end automation engine is running.

System action: The application continues withoutdisplaying log data.

Operator response: Ensure that logging is set upcorrectly for this automation domain; for example,check the eezjlog.properties file. If the problem persists,contact your system administrator.

EEZU0018E Creating EIF event receiver failed, errormessage is: Exception text .

Explanation: The operations console accessesfirst-level automation domains directly (direct accessmode). To be able to receive events from first-levelautomation domains an Event Integration Facility (EIF)event receiver must be created. Creating the eventreceiver failed.

System action: The operations console will not receiveevents.

Operator response: Examine the error message to findthe cause of failure.

EEZU0019E The operations console was notifed ofnew domain new domain that has thesame name as the known domain knowndomain .

Explanation: The operations console accessesfirst-level automation domains directly (direct accessmode). It was notifed about a new domain that has thesame name as a domain that is already known by theoperations console. However, the connectioninformation of the of the form 'domainname@ip-address:port' suggest that the new domain automates adifferent cluster than the known domain. Every domainoperated from an operations console must have aunique name.

System action: The domain is not allowed to join andtherefore, will not show up in the topology view.

Operator response: Try to determine from theinformation of new domain where the domain islocated. If the new domain automates a different clusterthan the known domain, have the name of the newdomain changed, and its automation adapter restartedto notify the operations console.



EEZU0020E The operations console was notifed ofdomain domain from adapter adapter withversion adapter version that is lower thanthe required minimum version minimumversion .

Explanation: The operations console accessesfirst-level automation domains directly (direct accessmode). It was notifed about a domain from an adapterwith a version that is too low for reliable operation.

System action: The domain is not allowed to join andtherefore, will not show up in the topology view.

Operator response: Try to locate the adapter that triedto join the domain and have it upgraded to a versionthat is equal or higher than the required minimumversion. Then have the automation adapter restarted tonotify the operations console.

EEZU0021E The operations console contacted adomain domain with adapter adapter atversion adapter version that is lower thanthe required minimum version minimumversion .

Explanation: The operations console accessesfirst-level automation domains directly (direct accessmode). It contacted a domain from an adapter with aversion that is too low for reliable operation.

System action: The operations console must notcommunicate with the domain which has a too lowversion and therefore, the domain will remain disabledin the topology view.

Operator response: Try to locate the adapter of thedomain and have it upgraded to a version that is equalor higher than the required minimum version. Thenhave the automation adapter restarted to notify theoperations console.

EEZU0022E The resource with resource nameresource and resource class resource classdoes not exist on domain domain .

Explanation: The operations console was launchedfrom another component passing resource contextinformation. The specified resource cannot be found.Reasons can be that the resource does not existanymore, the corresponding automation adapter is notrunning, the host name or the event port used by theautomation adapter are configured incorrectly or thedomain name is mapped to a different name by theautomation adapter.

System action: The current task ends. The operationsconsole starts without navigating to the specifiedresource.

Operator response: Press OK to continue workingwith the operations console.

EEZU0023E The domain domain does not exist.

Explanation: The operations console was launchedfrom another component passing a domain name ascontext information. The specified domain cannot befound. Reasons can be that the correspondingautomation adapter is not running, the host name orthe event port used by the automation adapter areconfigured incorrectly or the domain name is mappedto a different name by the automation adapter.

System action: The current task ends. The operationsconsole starts without navigating to the specifieddomain.


EEZU0024E The resource with resource nameresource and resource class resource classlocated on node resource node does notexist on domain domain.

Explanation: The operations console was launchedfrom another component passing resource contextinformation. The specified resource cannot be found.Reasons can be that the resource does not existanymore, the corresponding automation adapter is notrunning, the host name or the event port used by theautomation adapter are configured incorrectly or thedomain name is mapped to a different name by theautomation adapter.



EEZU0025E Unable to contact the end-to-endautomation manager using the specifiedserver name Server name and port Port .

Explanation: Before the connection properties arestored, it is verified that the end-to-end automationmanager can be accessed using the specified servername and port. However, the connection to theend-to-end automation manager via the automation JEEframework could not be established. Possible causes: 1)You specified incorrect values for server name andport. 2) The automation JEE framework (Enterpriseapplication EEZEAR) is not started. 3) You are notauthorized to access the automation JEE framework

System action: The connection properties are notstored.

Operator response: Verify that your entries for servername and port are correct. This is theBOOTSTRAP_ADDRESS configured for the applicationserver to accept Web client requests. Ensure that youhave the right permissions. Also check that theenterprise application EEZEAR is started. Refer to the



'Related errors' section for more details about theproblem. If the problem persists, contact your systemadministrator.

EEZU0026E Unable to launch the page with thename Page name . Error details: Exceptiontext

Explanation: An internal error occurred while tryingto launch a new page in the Dashboard ApplicationServices Hub. This might be related to an installation orsetup problem.

System action: The new page is not launched.

Operator response: Verify that your environment isset up correctly, re-start the WebSphere ApplicationServer and try again.

EEZU0027E Error while writing preference settingsto disk. Error details: Exception text

Explanation: Some preferences are stored in propertiesfiles on the system where the WebSphere ApplicationServer runs. These properties files are located in aproduct specific directory below the currentApplication Server profile. An error occurred whiletrying to write the preferences to disk.

System action: The application continues withoutstoring the preference values.

Operator response: Ensure that the mentioneddirectory exists and that you have the rights to writeinto this directory.

EEZU0028E Node node cannot be included, becausesite site is in maintenance mode.

Explanation: Site maintenance was started for thenodes of this site by a disaster recovery manager. Thisinvolves excluding this node from automation.

System action: The node is not included.

Operator response: Wait until the site maintenanceperiod is over.

EEZU0029E The resource reference resource namereferring to first-level automationdomain firstLevelDomain does not existon end-to-end automation domaine2eDomain.

Explanation: The operations console was launchedfrom another component passing resource contextinformation. The specified resource cannot be found.Reasons can be that the resource does not existanymore or the end-to-end automation engine is notrunning.



EEZU0030E You are not authorized to perform theoperation methodName . The user IDneeds to be granted one of thefollowing user roles: List of required roles .

Explanation: Authorization failed while trying toinvoke an operation for which a specific user role isrequired. The user ID used to log in to the DashboardApplication Services Hub is not granted any of therequired user roles.


Operator response: Ensure that the permissions anduser roles defined in the WebSphere Application Serverare set up correctly. User IDs can be granted specificrights by adding them to one of the predefined usergroups. For example add a user ID to the user groupEEZAdministratorGroup to assign the user roleEEZAdministrator to this user ID. User Managementcan be performed using the 'Users and Groups' >'Manage Users' task.

EEZU0031E The virtual server for node nodenamecould not be found. The requestedoperation will not be performed.

Explanation: The virtual server for the node could notbe found. Neither a shutdown nor a startup operationcan be performed against the node.


Operator response: Ensure that the hardware adapteris running and the connection to zEnterprise HMC isestablished.

EEZU0032E The end-to-end automation managementserver on hostname has been stopped.

Explanation: The automation JEE framework has beenstopped. Either the enterprise application EEZEAR orthe WebSphere Application Server hosting it has beenstopped. The operations console cannot communicatewith any automation backend without the automationJEE framework.

System action: The operations console will be closed.

Operator response: Ensure that the managementserver is up and running. Check that the enterpriseapplication EEZEAR is started. Then restart theoperations console.

EEZU0500W The automation domain domain name nolonger exists.

Explanation: You specified an automation domain thatno longer exists. Possible reasons are that theautomation domain has been deleted in the meantime.

EEZU0026E • EEZU0500W


System action: The current task continues.

Operator response: Check if the adapter for thespecified domain is running properly. If the domain isdeleted in the meantime, remove the correspondingwidget from the dashboard.

EEZU0501W The selected resource resource name nolonger exists.

Explanation: You selected a resource that no longerexists. Possible reasons are that the resource has beendeleted in the meantime or the automation policy hasbeen changed or deactivated.


Operator response: If the resource is still displayed,use menu item 'Refresh all' to obtain the currentlyavailable resources.

EEZU0502W The selected node node name no longerexists.

Explanation: You selected a node that no longer exists.Possible reasons are that the node has been deleted inthe meantime.


Operator response: If the node is still displayed, usemenu item 'Refresh all' to obtain the currently availablenodes.

EEZU0503W The request has been submitted but hasnot been processed yet.

Explanation: A request has been submitted but wasnot processed by the corresponding automationmanager. Reasons for this can be a slow network or anautomation manager that is not responding.

System action: The application continues.

Operator response: If the request is not processedsoon, send the request again. If the problem persists,check the connections to the automation manager andinspect the log files of the automation manager forproblems.

EEZU0504W The order to cancel the operator requesthas been submitted, but the request isstill not cancelled yet.

Explanation: A cancel request has been submitted butwas not processed by the corresponding automationmanager. Reasons for this can be a slow network or anautomation manager that is not responding.

System action: The application continues.

Operator response: If the request is not processedsoon, cancel the request again. If the problem persists,check the connections to the automation manager and

inspect the log files of the automation manager forproblems.

EEZU0505W The order to change the automationpolicy has been submitted, but thepolicy change has not been completelyprocessed yet.

Explanation: The order to change the automationpolicy has been submitted to the correspondingautomation manager, but the processing of this changehas not finished yet. Reasons for this can be a slownetwork or an automation manager that is notresponding.

System action: The application continues. When theprocessing of the policy change has been completed thescreen will automatically refresh to reflect the change.

Operator response: If the problem persists, check theconnections to the automation manager and inspect thelog files of the automation manager for problems.

EEZU0506W Domain Domain name becameunavailable.

Explanation: The operations console accessesfirst-level automation domains directly (direct accessmode). A domain that had been contacted successfullybefore, became unavailable when the operationsconsole tried to perform a request on a first-levelautomation domain. The automation adapter or thenode of the domain may have shut down withoutbeing able to notify the operations console.

System action: The request and any further requestwill not be performed on the domain until it becomesavailable.

Operator response: If you are using the operationsconsole and the automation domain is still displayed,use menu item 'Refresh all' to obtain the currentlyavailable domains. If 'Refresh all' is not available, closeand restart the current task to obtain the currentlyavailable domains.

EEZU0507W The management server is no longeravailable.

Explanation: The session may be no longer valid (e.g.timed out or logged off).

System action: None

Operator response: Logout and login again. If theproblem persists, restart the WebSphere ApplicationServer.

EEZU0508W The automation resource with resourceID resource id no longer exists.

Explanation: You specified an automation resourcethat no longer exists. Possible reasons are that the

EEZU0501W • EEZU0508W


automation resource has been deleted in the meantime.


Operator response: Check if the specified resource stillexists in your automation topology. If the resource isdeleted in the meantime, remove the correspondingwidget from the dashboard.

EEZU0509W No automation policies are available fordomain domain name.

Explanation: The specified automation domain didnot return any policy to display.


Operator response: Check if the specified domainsupports to list policies and has a proper policy pooldefined. Check that policies with correctly specifieddomain name exist in this policy pool.

EEZU0510W Automation domain domain name is notaccessible at this moment.

Explanation: The specified automation domain cannotbe accessed.


Operator response: Check if the specified domain isonline and communication state is OK.

EEZU0511W Automation domain domain name doesnot support policy activation with thisproduct.

Explanation: The specified automation domain doesnot support to list or activate policies through thisproduct.


Operator response: This product cannot be used tohandle policies of this domain.

EEZU0512W The automation JEE framework(Enterprise application EEZEAR) is notfully initialized yet and refuses toaccept requests. Wait until the EEZEARapplication is fully initialized, thenre-open the dashboard.

Explanation: The automation JEE framework(Enterprise application EEZEAR) is not fully initializedyet. The communication with attached domains is notpossible until all components of the EEZEARapplication are initialized.

System action: The system waits until the automationJEE framework is initialized before processing requests.

Operator response: Re-open the dashboard.

EEZU0520W The log file of automation domaindomain name requires operator attention.

Explanation: The log file contains errors or warningswhich require operator attention.


Operator response: View the log and look for warningor error messages to be resolved by human interaction.

EEZU0550W Automation domain domainName is notaccessible at this time.


System action: You can continue using the policyeditor, however it is not possible to use the harvestingfunctionality against the offline domain or to make useof that domain's policy pool while the domain isoffline.

Operator response: If you want to use the harvestingfunctionality or the policy pool of the offline domain,make sure that the automation domain is running. If itis a first-level automation domain, verify that theautomation adapter is running. Retry the operationafter the timeout period defined by the environmentvariable com.ibm.eez.aab.watchdog-interval-seconds. Ifthe problem persists, restart the automation adapter (incase of a first-level automation domain) or theend-to-end automation engine (in case of an end-to-endautomation domain). Note that you can save yourpolicy temporarily to local file instead of to the policypool.

EEZU0100E Memory shortage exception

Explanation: It was detected that there is less than 20percent of WebSphere heap size still available. To avoidan out of memory situation which could cause themanagement server not to function anymore, thecurrent task has been interrupted.

System action: The current task ends. The displayedpolicy may be incomplete.

Operator response: Increase the WebSphere heap size.It is recommended that you close this policy editorsession.

EEZU0101E An unexpected error occured: situationdescription

Explanation: The processing was interrupted becausean unexpected error occurred.



EEZU0509W • EEZU0101E


EEZU0102E Cannot overwrite the currently activepolicy

Explanation: You selected the policy file which iscurrently the domain's active policy as target to storeyour current policy. For an end-to-end automationdomain or for an agentless domain, it is not allowed tooverwrite the active policy.

System action: The policy is not stored.

Operator response: Store the current policy under adifferent file name.

EEZU0103E Received empty policy from JEEframework

Explanation: The received policy was empty. This mayhappen if the user tried to open the currently activepolicy from a domain which does not have any policyactivated.

System action: The policy is not received.

Operator response: Verify that the policy you try toopen exists.

EEZU0601W The policy contains XML comments.XML comments will be removed.

Explanation: The policy XML file contains XMLcomments which are not supported. These XMLcomments will be lost when the policy is loaded intothe policy editor.

System action: The policy editor continues to load thepolicy file, but XML comments are removed.

Operator response: If editing policy XML filesmanually, you should not use XML comments. You canuse the Description field of resources instead.

EEZU0602W The version of this policy file or of theused connected domain does not matchthe version of the policy editor. Versionof policy file or used domain: version inpolicy file . Version of policy editor: policyeditor version

Explanation: The version of the policy XML file doesnot match the version of the policy editor. This mayresult in incompatibilities. In case you have connectedthe policy editor to a domain running a different level,it might be impossible to activate the policy generatedwith this version of the policy editor.

System action: If the version of the policy XML ishigher than the version of the policy editor, someelements unknown to this policy editor version may beaccidentally removed if saving the policy. If the versionof the policy XML is lower than the version of thepolicy editor and you save it, down-level versions ofthe corresponding automation product may reject toactivate that policy. If you save a policy to a domain

with a lower level than the policy editor, that domainmight not be able to activate that policy.

Operator response: After saving the policy with thisversion of the policy editor, please check manuallywhether any expected component is missing. Use apolicy editor with the corresponding version wheneverpossible.

EEZU0603W While trying to read history data fromthe automation database, it was detectedthat no schema name has been specifiedfor the automation database.

Explanation: The parameter 'database-schema-name' ismissing in the file eez.automation.engine.properties.

System action: The default schema name'EAUTOUSR' will be used.

Operator response: If you use another schema namethan 'EAUTOUSR', ensure that the parameter'database-schema-name' exists in the fileeez.automation.engine.properties.

EEZU0603E The resource with resource nameresource and resource class resource classcontains an invalid property. Propertyproperty cannot be empty.

Explanation: The property is required.

System action: In order to avoid creating an invalidpolicy, the policy XML is not changed.

Operator response: Type in some value for theproperty.

EEZU0604E The resource with resource nameresource and resource class resource classcontains an invalid property. For theproperty property, a valid integer valuewith a maximum allowed value ofmaxValue is expected.

Explanation: The input value is above the maximumallowed value.


Operator response: Type in a valid value which isbelow the maximum allowed value.

EEZU0605E The resource with resource nameresource and resource class resource classcontains an invalid property. For theproperty property, a valid integer valuewith a minimum allowed value ofminValue is expected.

Explanation: The input value is below the minimumallowed value.




Operator response: Type in a valid value which isabove the minimum allowed value.

EEZU0606E The resource with resource nameresource and resource class resource classcontains an invalid property. For theproperty property, a valid integer valuewith a value between minValue andmaxValue expected.

Explanation: The property value is outside of theallowed range.


Operator response: Type in a value which is withinthe valid range.

EEZU0607E The resource with resource nameresource and resource class resource classhas a non-unique resource name.

Explanation: All resources have to have a uniqueresource name.


Operator response: Choose a unique resource name.

EEZU0608E Attempt to create multiple references tothe resource with resource key resourcekey.

Explanation: It is not possible to create multipleresource references referencing the same referencedresource.


Operator response: Only create one resource referenceper base resource.

EEZU0609E Failed to parse Tivoli SA XML policyfile fileName.

Explanation: The specified file does not contain aparsable Tivoli SA XML policy, or it cannot be opened.

System action: The requested operation is aborted.

Operator response: Make sure to specify a valid TivoliSA XML policy file which is accessible and whichcontains valid XML data.

EEZU0610E Empty policy file name.

Explanation: Policy file name entry field cannot beempty.

System action: The file load operation is not executed.

Operator response: Specify a file name.

EEZU0611E The resource with resource nameresource and resource class resource classcontains an invalid property. Propertyproperty must be a valid IPv6 address.

Explanation: The property should contain a valid IPv6address.


Operator response: Type in a valid IPv6 address forthe property.

EEZU1000I No policy is activated.

Explanation: No resources are displayed because nopolicy is activated.


Operator response: Activate a policy.

EEZU2000I Domain State for domain domain name isdomain state.

Explanation: The domain changed its state to thespecified value.

System action: The system will handle this change.End-to-End resources to this domain will change theirstate accordingly.

Operator response: None.

EEZU2001I Domain domain name joined successfully.

Explanation: The domain is now online and ready forbeing managed.



EEZU2002I Domain Communication State fordomain domain name is domaincommunication state.

Explanation: The domain has a new communicationstate.


EEZU0606E • EEZU2002I



EEZU2003I Request event for request type requesthas been received from domain domainname for resource resource name.

Explanation: A request has been added on thespecified resource.

System action: The system will handle this change.


EEZU2004I Request deleted event has been receivedfrom domain domain name for resourceresource name.

Explanation: A request has been added on thespecified resource.



EEZU2005I Policy changed event has been receivedfrom domain domain name.

Explanation: The policy containing resource, groupand relationship definitions has changed for thisdomain.



EEZU2000W Domain domain name left.

Explanation: The domain is not available anymore forbeing managed.



EEZU2002W Domain Communication State fordomain domain name is domaincommunication state.




EEZU2002E Domain Communication State fordomain domain name is domaincommunication state.




Prefix EEZY

EEZY0001E An error occurred while initializing theautomation adapter plug-in. Additionalinformation: additionalInformation .

Explanation: Possible reasons for the error are: 1)Missing or corrupted product files. 2) Not enoughmemory available. 3) Not enough disk space available.4) Programming error in plug-in.


Operator response: Evaluate the additionalinformation. Check if one of the reasons applies thatare listed in the explanation.

EEZY0002E An event cannot be generated forresource resourceName.

Explanation: The processing was interrupted by thisexception and cannot complete event generation.



EEZY0003E An error occurred while stopping theautomation adapter plug-in. Additionalinformation: additionalInformation .

Explanation: An error occurred while stopping theplug-in.


Operator response: Check the additional informationfor details.

EEZY0004E Failed to load file fileName from disk.Additional information:additionalInformation .

Explanation: Failed to load the file specified in themessage from disk. This file is necessary for runningthe automation adapter plug-in.



EEZU2003I • EEZY0004E


EEZY0005E An operation named operationName wasrequested although the automationadapter plug-in is not ready forprocessing requests.

Explanation: The plug-in was requested to perform anoperation but it is not yet initialized or alreadystopped.

System action: Processing of the operation ends.

Operator response: Wait until the automation adapterplug-in is fully initialized, or restart it. Then retry theoperation.

EEZY0006E An unsupported operation namedoperationName was requested.

Explanation: The automation adapter plug-in wasrequested to perform an operation but this operation isnot supported.



EEZY0007E An error occurred while processing theoperation named operationName.Additional information:additionalInformation .

Explanation: An error occurred while processing theoperation.



EEZY0008E An error occurred while processing anoperation. Additional information:additionalInformation .

Explanation: An error occurred while processing anoperation.



EEZY0009E Failed to obtain entry pointentryPointName in module moduleName.Additional information:additionalInformation .

Explanation: Failed to obtain the entry point specifiedin the message.



EEZY0010E Failed to receive enough free memory toprocess the current operation.Additional information:additionalInformation .

Explanation: Not enough memory is available.



EEZY0011E An operation on a resource with thefollowing key was requested: nameresourceName, class className, automationdomain domainName, node nodeName .There is no resource with the specifiedkey.

Explanation: An operation on a resource wasrequested but the resource with the specified key doesnot exist. Possible reasons for the error are: 1) Theresource key information is not spelled correctly. 2) Theresource with the specified key does not exist. 3) Theresource with the specified key was deleted shortlybefore or when processing the operation.


Operator response: Verify that the resource keyinformation is spelled correctly. Correct the informationand submit the operation again.

EEZY0012E An operation to enumerate the membersof the group with the following key wasrequested: name resourceName, classclassName, automation domaindomainName, node nodeName . There isno group with the specified key.

Explanation: An operation to enumerate the membersof a group was requested but the group with thespecified key does not exist. Possible reasons for theerror are: 1) The resource key information is not spelledcorrectly. 2) The resource key information does notrepresent a group. 3) The group with the specified keydoes not exist. 4) The group with the specified key wasdeleted shortly before or when processing theoperation.


Operator response: Verify that the resource keyinformation is spelled correctly. Correct the informationand submit the operation again.

EEZY0013E Failed to process an operation becausemalformed or incomplete input wasspecified.

Explanation: The automation adapter plug-in was notable to correctly process the requested operationbecause malformed or incomplete input was specified.

EEZY0005E • EEZY0013E



Operator response: Check the specified input andsubmit the operation request again if desired.

EEZY2001I A problem occured in class className,method methodName, file fileName, linelineNumber. Additional information:additionalInformation .

Explanation: An problem has occurred duringprocessing and this message indicates the locationwhere the problem occurred. An additional messageindicates which problem occurred.

System action: The system action depends on theproblem that occurred.

Operator response: You may search the messagerelated to the problem that occurred and follow therecommendations given there.

Prefix EEZZ

EEZZ0001E Failed to open a connection to theMicrosoft Server Clustering namedclusterName. Additional information:additionalInformation .

Explanation: The automation adapter plug-in wasunable to open a connection to the specified MicrosoftServer Clustering. The name can be a network name oran IP address. Possible reasons are: 1) There is nocluster with the specified name. 2) The cluster with thespecified name is not reachable from the systemrunning the plug-in. 3) The cluster with the specifiedname is not operational. The name NULL indicates theMicrosoft Server Clustering in which the system thatruns the plug-in is a cluster node.


Operator response: Check the additional informationfor details. 1) Verify that the specified cluster name isspelled correctly. If not, correct the name. 2) Verify thatthe cluster is reachable from the system running theplug-in. If not, correct the problem. 3) Verify that thecluster is running and can be contacted by other means.If not, repair the cluster.

EEZZ0002E An event cannot be generated forresource resourceName.

Explanation: The processing was interrupted by thisexception and cannot complete event generation.



EEZZ0003E Microsoft Server Clustering failed toperform an operation requested by theautomation adapter plug-in. Additionalinformation: additionalInformation .

Explanation: Microsoft Server Clustering failed toperform an operation requested by the plug-in. Possiblereasons are: The cluster is not reachable from thesystem running the plug-in. The cluster is notoperational. The plug-in passed wrong input whenrequesting the operation.



EEZZ0004E Failed to bring resorce resourceNameonline on behalf of user userID.Specified comment: comment .Additional information:additionalInformation .

Explanation: The automation adapter plug-in receiveda request to bring the specified resource online butfailed to perform the request.


Operator response: Check the additional errorinformation for the reason why the request processingfailed.

EEZZ0005E Failed to take resorce resourceNameoffline on behalf of user userID.Specified comment: comment .Additional information:additionalInformation .

Explanation: The automation adapter plug-in receiveda request to take the specified resource offline butfailed to perform the request.



EEZZ0006E Failed to bring group groupName onlineon behalf of user userID. Specifiedcomment: comment . Additionalinformation: additionalInformation .

Explanation: The automation adapter plug-in receiveda request to bring the specified group online but failedto perform the request.



EEZY2001I • EEZZ0006E


EEZZ0007E Failed to take group groupName offlineon behalf of user userID. Specifiedcomment: comment . Additionalinformation: additionalInformation .

Explanation: The automation adapter plug-in receiveda request to take the specified group offline but failedto perform the request.



EEZZ0008E Failed to include node nodeName into thecluster on behalf of user userID.Specified comment: comment .Additional information:additionalInformation .

Explanation: The automation adapter plug-in receiveda request include the node into the cluster but failed toperform the request.



EEZZ0009E Failed to exclude node nodeName fromthe cluster on behalf of user userID.Specified comment: comment .Additional information:additionalInformation .

Explanation: The automation adapter plug-in receiveda request exclude the node from the cluster but failedto perform the request.



EEZZ0010E The automation adapter plug-in receivedan unsupported request namedrequestName on behalf of user userID.Specified comment: comment .

Explanation: The plug-in received a unsupportedrequest which will not be executed.


Operator response: Correct the request and submit itagain if desired.

EEZZ0011E The automation adapter plug-in receiveda request to take the resourceresourceName offline on behalf of useruserID. The plug-in rejects this request.

Explanation: The plug-in received a request to take aresource offline on which it depends. The plug-inrejects the request because processing the requestwould make the plug-in unavailable.


Operator response: Use another way to take thisMicrosoft Server Clustering resource offline.

EEZZ0012E The automation adapter plug-in receiveda request to take the group groupNameoffline on behalf of user userID. Theplug-in rejects this request.

Explanation: The plug-in received a request to take agroup offline on which it depends. The plug-in rejectsthe request because processing the request would makethe plug-in unavailable.


Operator response: Use another way to take thisMicrosoft Server Clustering group offline.

EEZZ2001I Performing request to bring resorceresourceName online on behalf of useruserID. Specified comment: comment .

Explanation: The automation adapter plug-in receiveda request to bring the specified resource online. Thisrequest was already forwarded to Microsoft ServerClustering and did not report an error until now.Processing the request may still fail.

System action: Processing of the operation continues.

Operator response: Check for messages or otherindications whether the request was successfullycompleted.

EEZZ2002I Performing request to take resorceresourceName offline on behalf of useruserID. Specified comment: comment .

Explanation: The automation adapter plug-in receiveda request to take the specified resource offline. Thisrequest was already forwarded to Microsoft ServerClustering and did not report an error until now.Processing the request may still fail.



EEZZ0007E • EEZZ2002I


EEZZ2003I Performing request to bring groupgroupName online on behalf of useruserID. Specified comment: comment .

Explanation: The automation adapter plug-in receiveda request to bring the specified group online. Thisrequest was already forwarded to Microsoft ServerClustering and did not report an error until now.Processing the request may still fail.



EEZZ2004I Performing request to take groupresourceName offline on behalf of useruserID. Specified comment: comment .

Explanation: The automation adapter plug-in receiveda request to take the specified group offline. Thisrequest was already forwarded to Microsoft ServerClustering and did not report an error until now.Processing the request may still fail.



EEZZ2005I Performing request to exclude nodenodeName from the cluster on behalf ofuser userID. Specified comment: comment.

Explanation: The automation adapter plug-in receiveda request to exclude the specified node from the cluster.This request was already forwarded to Microsoft ServerClustering and did not report an error until now.Processing the request may still fail.



EEZZ2006I Performing request to include nodenodeName into the cluster on behalf ofuser userID. Specified comment: comment.

Explanation: The automation adapter plug-in receiveda request to include the specified node into the cluster.This request was already forwarded to Microsoft ServerClustering and did not report an error until now.Processing the request may still fail.



VCS Solaris adapter messagesThis reference provides all messages that are generated by the VCS Solaris adapter.

Prefix EEZV

EEZV0001E Failed to load library: lib, message is:message.

Explanation: Loading a library failed. Either thelibrary or a prerequisite library is not available.

System action: The automation adapter will not start.

Operator response: Try to identify which librarycannot be loaded using the following steps. Use 'find-name' to find the library. Use 'ldd library' to determinewhich library is not available.

EEZV0002E Domain domain went offline and theautomation adapter is stopped.

Explanation: An event indicated that the domain wentoffline. The automation adapter can only operate with adomain that is online. Therefore, the automationadapter is stopped.

System action: The automation adapter does notaccept any further requests. The automation adapter isstopped.

Operator response: If the automation adapter isautomated no action is required and it will be restartedwhen the domain comes back online. If the automationadapter is not automated, restart it using command'vcsadapter start' after the domain has become online.Use the command 'vcsadapter status' to find out if theautomation adapter is automated.

EEZV0003E Request request must not be applied onautomated adapter resource resource.

Explanation: Automated resources that control theadapter cannot accept such request because it preventscorrect automation of the adapter. For example, settingthe adapter 'Offline' will cause the domain to becomeunreachable from the administration console.

System action: The request was not performed.

EEZZ2003I • EEZV0003E


Operator response: Use only supplied scripts'vcsadapter start' and 'vcsadapter stop' to control theadapter from one of the nodes in the domain.

EEZV0010E Failed to exclude node node fromautomation, message is message.

Explanation: An error occurred, when trying toexclude the node from automation. The reason may befound in the message.

System action: Excluding the node was notperformed.

Operator response: Examine the message for thereason why excluding the node failed.

EEZV0011E Failed to unsubscribe resource resource,message is message.

Explanation: An error occurred when trying toremove the subscription for the resource. The reasonmay be found in the message.

System action: The subscription may not have beenremoved.

Operator response: Examine the message for thereason why removing the subscription failed.

EEZV0013E Failed initialize, message is message.

Explanation: Trying to initialize the backend failed.Therefore, the request cannot be satisfied.

System action: No further requests are processed.

Operator response: Examine the message to find outwhy initialization failed.

EEZV0016E Failed to include node node intoautomation, message is message.

Explanation: An error occurred when trying toinclude the node into automation. The reason may befound in the message.

System action: Including the node was not performed.

Operator response: Examine the message for thereason why including the node failed.

EEZV0018E Failed to subscribe resource resource,message is message.

Explanation: An error occurred when requesting asubscription for the resource. The reason may be foundin the message.

System action: The subscription has not been made.

Operator response: Examine the message for thereason why requesting the subscription failed.

EEZV0020E Failed to validate resource: grp.

Explanation: The resource for which a request wasmade does not exist.

System action: The request is not performed

Operator response: Use list commands to verify thatthe resource exists. If it does not exist, the resource hadbeen removed. If it exists the request should berepeated.

EEZV0022E Failed to get resource relationships,message is message.

Explanation: An error occurred when trying to getrelationships between resources. The reason may befound in the message.

System action: No relationships were returned.

Operator response: Examine the message for thereason why the request failed.

EEZV0035E Adapter stops because domain domain isgoing offline.

Explanation: The adapter was notified by an eventthat the domain is going offline. The adapter cannotcontinue to exist if the domain is offline. Therefore, theadapter is stopped.

System action: The adapter is stopped.

Operator response: If the domain is online and theadapter is automated it will restart automatically.Otherwise, issue command 'vcsadapter start' to restartthe adapter.

EEZV0037E No domain that is online was detected.Automation adapter is stopped.

Explanation: No online domain was found or an erroroccurred when trying to query the domain. Theautomation adapter can only operate with a domainthat is online. Therefore, the automation adapter isstopped.


Operator response: If the automation adapter isautomated no action is required and it will be restartedwhen the domain comes back online. If the automationadapter is not automated, restart it using command'vcsadapter start' after the domain has become online.Use the command 'vcsadapter status' to find out if theautomation adapter is automated.

EEZV0010E • EEZV0037E


EEZV0038E Request request on resource resourcereturned with code: return-code, and errormessage: error.

Explanation: The request returned with a non-zeroreturn code which indicates that it has not beensuccessfully performed. The reason may be found inthe message.



EEZV0040E Log in for user ID user failed for anunknown reason, message is: message

Explanation: The user ID and password validationcould not be performed because PAM returned with anerror.

System action: NO requests will be accepted for thisuser ID.

Operator response: Examine the message. Try to login again. Make sure to specify the user ID andpassword in the correct case because the entries arecase-sensitive.

EEZV0041E Log in for user ID user failed, messageis: message

Explanation: The user ID and password failedvalidation on the node where the log in wasperformed.



EEZV0042E Log in for user ID user failed, becausethe user account expired, message is:message



Operator response: Have the system administratorchange the expiration date of the user account.

EEZV0043E Log in for user ID user failed becausethe password expired, message is:message

Explanation: The password is expired. Have thesystem administrator change the expiration date.


Operator response: Have the password changed.

EEZV0044E Programming error detected, message iserror-message.


System action: A request may not have beenprocessed.


EEZV0046E Resource group resource is already onlineon node node.

Explanation: Trying to start a resource group failed,because it is already online on that node. The state ofthe resource group was offline at the time whenRequest online was selected, but had changed to onlinewhen the request was tried to process.

System action: The online request is not performed,because the resource group is already online.

Operator response: Since the goal was to have theresource group online on the node, no further action isrequired.

EEZV0047E Resource group resource is already onlineon node online-node and therefore cannotbe started on node requested-node.

Explanation: Trying to start a resource group on aspecific node failed, because it is already online onanother node.

System action: The online request is not performed.

Operator response: Check on which node the resourcegroup is online. If the resource group must be onlineon another node, first bring offline on the node whereit is online. Then repeat the online request on the othernode.

EEZV0051E Request request on resource resource hasalready been submitted and is currentlybeing performed.

Explanation: The request is pending in its executionand therefore will not be submitted again.


Operator response: Wait for the pending command tocomplete. State changes in the resource may indicatedthat it has completed. If the log requires attention, viewthe log to see if the request failed.

EEZV0038E • EEZV0051E


EEZV0502W Unable to locate resource with name:name, class: class, node: node.

Explanation: The resource identified in an event byname, class, and node could not be found.

System action: The resource is not updated with eventinformation.

Operator response: Check if the resource exists. Verifythe status of the resource.

EEZV0610I Command reset from non-recoverableerror has been performed on resourceresource on behalf of user userid.

Explanation: A user found a resource flagged withnon-recoverable error by automation, which means theresource is not automated until a user issued the reset.

System action: The reset has been issued to theresource.

Operator response: No action is required. You canverify in the operations console if the resource is nomore in error.

EEZV0611I Command request has been performedon resource resource with return code:return-code on behalf of user userid withcomment: comment.

Explanation: A user has issued a command thatrequests a change of the resource state. This commandis being performed by automation on the indicatedresource.

System action: The command has been issued to theresource.

Operator response: No action is required. You canverify in the operations console if the resource changedits state.

EEZV0612I Node node has been excluded fromautomation on behalf of user userid.

Explanation: A user has requested to exclude the nodefrom automation. See 'System action below'.

System action: Resources on that node are stopped byautomation. Then automation tries to restart theresources on other nodes in the domain.

Operator response: No action is required. You canverify in the operations console if the resources hadbeen restarted on other nodes in the domain, or thattheir new state is acceptable.

EEZV0613I Node node has been included intoautomation on behalf of user userid.

Explanation: A user has requested to include the nodeinto automation. See 'System action below'.

System action: Once the node has been included intoautomation, automation may try to start resources onthe node.

Operator response: No action is required. You canverify in the operations console if resources areautomated on the included node.

EEZV0614I A request to move resource groupresource to node node has been performedwith return code: return-code on behalfof user userid with comment: comment.

Explanation: A user has issued a request to move aresource group to another node. The command is beingperformed by automation.

System action: The move request has been issued tothe resource.

Operator response: No action is required. You canverify in the operations console if the resource wasmoved.

EEZV0502W • EEZV0614I


PowerHA and automation adapter messagesThis reference provides all messages that are generated by the PowerHA adapterand the end-to-end automation adapter of System Automation for Multiplatforms.

Prefix SAMA

SAMA0001E Failed to load library: lib, message is:message.

Explanation: Loading a library failed. Either thelibrary or a prerequisite library is not available.

System action: The automation adapter will not start.

Operator response: Try to identify which librarycannot be loaded using the following steps. Use 'find-name' to find the library. Use 'ldd library' to determinewhich library is not available.

SAMA0002E Domain domain went offline and theautomation adapter is stopped.

Explanation: An event indicated that the domain wentoffline. The automation adapter can only operate with adomain that is online. Therefore, the automationadapter is stopped.


Operator response: If the automation adapter isautomated no action is required and it will be restartedwhen the domain comes back online. If the automationadapter is not automated, restart it using command'samadapter start' after the domain has become online.Use the command 'samadapter status' to find out if theautomation adapter is automated.

SAMA0003E Request request must not be applied onan automated adapter resource resource.

Explanation: Automated resources that control theadapter cannot accept such a request because itprevents correct automation of the samadapter. Forexample, requesting the samadapter to become 'Offline'will cause the domain to become unreachable from theoperations console.


Operator response: Use only supplied scripts'samadapter start' and 'samadapter stop' to control thesamadapter from one of the nodes in the SAMPdomain.

SAMA0004E Request request failed on resourceresource with message: message.

Explanation: The request could not be performed onthe resource. The reason may be found in the message.



SAMA0005E Unable to build command from requestrequest for resource resource.

Explanation: The request could not be built for theresource. The reason may be that the command is notallowed on this type of resource.



SAMA0006E Failed to reset resource resource, messageis: message.

Explanation: An error occurred when trying to resetthe resource that was marked non recoverable. Thereason may be found in the message.

System action: The request to reset the resource wasnot performed.

Operator response: Examine the message for thereason why the reset failed.

SAMA0007E Failed to obtain members of groupresource, message is: message.

Explanation: An error occcured when trying to obtainthe members for resource. The reason may be found inthe message.

System action: Due to the error no memberscontained in the resource were returned.

Operator response: Examine the message for thereason why obtaining contained resource failed.

SAMA0008E Failed to get top level resources,message is: message.

Explanation: An error occurred when trying to obtainresources that are not contained in other resources. Thereason may be found in the message.

System action: Due to the error no resources werereturned.

Operator response: Examine the message for thereason why obtaining top level resource failed.

Prefix SAMA • SAMA0008E


SAMA0009E Cannot establish remote access foroperating console in direct mode,message is message.

Explanation: Access from a remote operating consoleover RMI was specified insam.adapter.plugin.properties. Attempting to providethe direct access failed.

System action: The adapter is not reachable from aremote operating console.

Operator response: Examine the message. Check theconfiguration of the adapter for direct access from aremote operating console.

SAMA0010E Failed to exclude node node fromautomation, message is message.

Explanation: An error occurred when trying toexclude the node from automation. The reason may befound in the message.

System action: Excluding the node was notperformed.

Operator response: Examine the message for thereason why excluding the node failed.

SAMA0011E Failed to unsubscribe resource resource,message is message.

Explanation: An error occurred when trying toremove the subscription for the resource. The reasonmay be found in the message.

System action: The subscription may not have beenremoved.

Operator response: Examine the message for thereason why removing the subscription failed.

SAMA0013E Failed establish a session, message ismessage.

Explanation: Trying to establish an RMC session withthe backend failed. Therefore, the request cannot besatisfied.

System action: No session with RMC is established.

Operator response: Examine the message to find outwhy the RMC session failed.

SAMA0016E Failed to include node node intoautomation, message is message.

Explanation: An error occurred when trying toinclude the node into automation. The reason may befound in the message.

System action: Including the node was not performed.

Operator response: Examine the message for thereason why including the node failed.

SAMA0018E Failed to subscribe resource resource,message is message.

Explanation: An error occurred when requesting asubscription for the resource. The reason may be foundin the message.

System action: The subscription has not been made.

Operator response: Examine the message for thereason why requesting the subscription failed.

SAMA0019E Failed to obtain details for domaindomain, message is message.

Explanation: The domain was retrieved successfully,but trying to obtain associated class information failed.The reason may be found in the message.

System action: The information for the domain ismissing.

Operator response: Examine the message for thereason why obtaining the additional information failed.

SAMA0020E Failed to validate resource: grp.

Explanation: The resource for which a request wasmade does not exist.


Operator response: Use list commands to verify thatthe resource exists. If it does not exist, the resource hadbeen removed. If it exists the request should berepeated.

SAMA0022E Failed to get resource relationships,message is message.

Explanation: An error occurred when trying to getrelationships between resources. The reason may befound in the message.

System action: No relationships were returned.


SAMA0023E Failed to lookup resources, message ismessage.

Explanation: An error occurred when trying toidentify resources. The reason may be found in themessage.

System action: No resource were returned.


SAMA0009E • SAMA0023E


SAMA0024E Failed to get resources based on filter:filter, message is: message.

Explanation: An error occurred when trying to getresources based on a filter. The reason may be found inthe message.

System action: No filtered resource were returned.


SAMA0025E Failed to get the parent resource forresource, message is message.

Explanation: An error occurred when trying to getparent of the resource. The reason may be found in themessage.

System action: The parent resource was not returned.


SAMA0026E Failed to get the resources on node node,message is message.

Explanation: An error occurred when trying to get theresources that can run on the node. The reason may befound in the message.

System action: No resources on that node werereturned.


SAMA0027E Failed to refresh resources, message ismessage.

Explanation: An error occurred when trying to refreshresources. The reason may be found in the message.

System action: No resource were refreshed.


SAMA0028E Failed to get nodes of the domain,message is message.

Explanation: An error occurred when trying to get thenodes in the domain. The reason may be found in themessage.

System action: No nodes were returned.


SAMA0029E Failed to get nodes from an equivalency,message is message.

Explanation: An error occurred when trying to get thenodes from an equivalency. The reason may be foundin the message.



SAMA0033E Failed to get nodes excluded fromautomation, message is message.

Explanation: An error occurred when trying to get thenodes that are excluded from automation. The reasonmay be found in the message.



SAMA0034E Failed to enable event publishing infirst-level automation manager, messageis message.

Explanation: The reason for failing to enablepublishing may be an inoperative IBM.RecoveryRM.Details may be found in the message.

System action: Event publishing was not enabled.

Operator response: Examine the message for thereason why enabling event publishing failed.

SAMA0035E Adapter stops because domain domain isgoing offline.

Explanation: The adapter was notified by an eventthat the domain is going offline. The adapter cannotcontinue to exist if the domain is offline. Therefore, theadapter is stopped.


Operator response: If the domain went offlineunexpectedly determine the reason. The domain can berestarted using command 'startrpmdomain<domain-name>'. If the domain is online and theadapter is automated it will restart automatically.Otherwise, issue command 'samadapter start' to restartthe adapter.

SAMA0036E Request request is not implemented.

Explanation: The request is currently not supported


Operator response: Check if a more recent version ofthe automation adapter is available that supports therequest.



SAMA0037E No domain that is online was detected.Automation adapter is stopped.

Explanation: No online domain was found or an erroroccurred when trying to query the domain. Theautomation adapter can only operate with a domainthat is online. Therefore, the automation adapter isstopped.


Operator response: If the automation adapter isautomated no action is required and it will be restartedwhen the domain comes back online. If the automationadapter is not automated, restart it using command'samadapter start' after the domain has become online.Use the command 'samadapter status' to find out if theautomation adapter is automated.

SAMA0038E Request request on resource resourcereturned with code: return-code, and errormessage: error.

Explanation: The request returned with a non-zeroreturn code which indicates that it has not beensuccessfully performed. The reason may be found inthe message.



SAMA0039E Request request on resource resourcereturned without result.

Explanation: The request did not respond with returncode and message.

System action: Most likely the request was notperformed.

Operator response: If the error persists examine thelog for other messages around that time.

SAMA0040E Log in for user ID user failed for anunknown reason, message is: message

Explanation: The user ID and password validationcould not be performed because PAM returned with anerror.



SAMA0041E Log in for user ID user failed, messageis: message

Explanation: The user ID and password failedvalidation on the node where the log in wasperformed.



SAMA0042E Log in for user ID user failed, becausethe user account expired, message is:message



Operator response: Have the system administratorchange the expiration date of the user account.

SAMA0043E Log in for user ID user failed, becausethe password expired, message is:message

Explanation: The password is expired. Have thesystem administrator change the expiration date.


Operator response: Have the password changed.

SAMA0044E Programming error detected, message iserror-message.


System action: A request may not have beenprocessed.


SAMA0045E Failed to get nodes for resource groupresource, message is message.

Explanation: An error occurred when trying to getnodes on which the resource group can run. The reasonmay be found in the message.

System action: The nodes were not returned.




SAMA0046E Resource group resource is already onlineon node node.

Explanation: Trying to start a resource group failed,because it is already online on that node. The state ofthe resource group was offline at the time whenRequest online was selected, but had changed to onlinewhen the request was tried to process.

System action: The online request is not performed,because the resource group is already online.

Operator response: Since the goal was to have theresource group online on the node, no further action isrequired.

SAMA0047E Resource group resource is already onlineon node online-node and therefore cannotbe started on node requested-node.

Explanation: Trying to start a resource group on aspecific node failed, because it is already online onanother node.

System action: The online request is not performed.

Operator response: Check on which node the resourcegroup is online. If the resource group must be onlineon another node, first bring offline on the node whereit is online. Then repeat the online request on the othernode.

SAMA0048E Adapter stops because domain domain isgoing offline.

Explanation: The adapter was notified by an eventthat the domain represented by the cluster services hadbeen stopped. The adapter cannot continue to exist ona node where the cluster services have been stopped.Therefore, the adapter is stopped.


Operator response: If the cluster services stoppedunexpectedly determine the reason. The cluster servicescan be restarted using smitty hacmp. If the clusterservices are startedthe adapter is automated it willrestart automatically. Otherwise, issue command'hacadapter start' to restart the adapter.

SAMA0049E No domain that is online was detected.Automation adapter is stopped.

Explanation: The domain represented by the clusterservices was not found online or an error occurredtrying to trying to query the domain. The automationadapter can only operate with a domain that is online.Therefore, the automation adapter is stopped.


Operator response: If the automation adapter is

automated by HACMP no action is required and it willbe restarted when the domain comes back online. If theautomation adapter is not automated, restart it usingcommand 'hacadapter start. Use command 'hacadapterstatus' to find out if the automation adapter isautomated.

SAMA0050E Request request is not allowed, becausedomain cluster has SubState: substate.SubState: STABLE is required.

Explanation: The request can only be performed if thedomain (cluster) is in SubState: STABLE.

System action: The automation adapter does notaccept the request.

Operator response: Wait until the domain has reachedSubState: STABLE. To check the SubState in theoperations console select the domain and inspect theCluster-SubState in tab Additional Info. Select Refreshall before inspecting the Cluster-SubState again. If theSubState does not change to STABLE within reasonabletime use smitty hacmp > Problem determination toresolve the condition.

SAMA0051E Request request on resource resource hasalready been submitted and is currentlybeing performed.

Explanation: The request is pending in its executionand therefore will not be submitted again.


Operator response: Wait for the pending command tocomplete. State changes in the resource may indicatedthat it has completed. If the log requires attention, viewthe log to see if the request failed.

SAMA0052E Deactivating the current automationpolicy failed with error message: error.

Explanation: The request to deactivate the currentlyactive automation policy returned with an error.

System action: The policy was not deactivatedcorrectly.

Operator response: Examine the message for thereason why the policy could not be deactivated. UseView log on the domain to find additional errormessages.

SAMA0053E Activating automation policy from filefile failed with error message: error.

Explanation: The request to activate the automationpolicy returned with an error.

System action: The policy was not activated.

Operator response: Examine the message for thereason why the policy could not be activated. Use View



log on the domain to find additional error messages.

SAMA0054E Automation policy request request cannotbe performed because policy requestcurrent-req is in progress.

Explanation: The automation policy request cannot beperformed because another request is still in progress.

System action: The policy request has been rejected.

Operator response: Wait for the current policy requestto finish. Use View log on the domain to findadditional information on policy request results.

SAMA0055E Request request must not be applied onan automated adapter resource resource.

Explanation: Automated resources that control theadapter cannot accept such a request because itprevents correct automation of the hacadapter. Forexample, bringing the hacadapter 'Offline' will causethe domain to become unreachable from the operationsconsole.


Operator response: Use only supplied scripts'hacadapter start' and 'hacadapter stop' to control theadapter from one of the nodes in the HACMP cluster.

SAMA0056E Failed to get information about thecurrently active policy. The errormessage is: error-message.

Explanation: Trying to retrieve information about thecurrently active policy failed.

System action: No information about the currentlyactive policy can be provided.

Operator response: Evaluate the error message. Try tosubmit the command again.

SAMA0057E The policy file " policyFile " cannot befound.

Explanation: The policy does not exist.

System action: The policy is not activated.

Operator response: Verify the policy XML file by thatpath and name exists.

SAMA0058E No automation policies are available inpolicy pool directory for automationdomain domain.

Explanation: There are no policy files in the policypool directory.

System action: No policies are listed.

Operator response: Verify the policy pool containspolicy files before trying to work with a policy.

SAMA0059E The policy file " policyFile " for thecurrently active policy cannot be found.

Explanation: The active policy once was successfullyactivated from the file. But currently the file cannot befound.

System action: The currently active policy could notbe checked, because the file was not found. Therefore,the policy information is incomplete.

Operator response: If the file had been accidentlyremoved, use command 'sampolicy -s filename' to savethe policy. Otherwise move the file to the path, or usecfgsamadapter to correct the policy pool path andactivate the policy from there.

SAMA0060E Trying to replicate policy file " fileName "from local node " localNode " on remotenodes " remoteNodes " failed. Theoriginal error was: " errMessage ".

Explanation: An error occurred when attempting toreplicate a policy file on remote nodes. See originalerror for details.

System action: See original error for details.

Operator response: See original error for details.

SAMA0061E Trying to store policy file " fileName " onlocal node " localNode " failed. Theoriginal error was: " errMessage ".

Explanation: An error occurred when attempting tostore a policy file locally. See original error for details.

System action: The attempt to store the policy filelocally failed. No policy file was created.

Operator response: Check if there is enough space onthe local node. See original error for details.

SAMA0062E The policy file " fileName " on node "localNode " could not be found.

Explanation: The policy file does not exist in thepolicy pool directory.

System action: No policy file was read.

Operator response: Make sure that the policy fileexists in the policy pool directory.

SAMA0063E A move request is not allowed onresource group " rsourcegroup " because itis contained in another resource group.

Explanation: A move requests is only allowed on aresource group which is not contained in any otherresource group.

System action: The move request is not performed.

Operator response: If possible, move the



top-level-resource group in which the resource group iscontained.

SAMA0064E Trying to delete policy file " fileName "on remote nodes " remoteNodes " failed.The original error was: " errMessage ".

Explanation: An error occurred when attempting todelete a policy file on remote nodes.


Operator response: See original error for details.

SAMA0065E Deleting policy file " fileName " is notallowed, because the policy is currentlyactivated.

Explanation: The file of the currently active policycannot be deleted.

System action: The policy file is not deleted.

Operator response: Deactivate the current policy. Thentry to delete the file.

SAMA0066E The location of the automation policypool was not specified on node node.

Explanation: The Policy pool location was notspecified in the configuration dialog.

System action: The operation is canceled.

Operator response: Use the configuration dialog'cfgsamadapter' to specify a 'Policy pool location',which is the directory where automation policy files arestored for activation. If a policy from that location isshown as active policy, it may have been activated fromanother node in the domain, where the policy poolexists. Make sure the configuration and policies arecopied to all other nodes in the domain.

SAMA0500W Event of type type are not processed inthis version.

Explanation: The event of this type is not supported.

System action: The event is not processed.

Operator response: Check if a more recent version ofthe automation adapter is available that supports thistype of event.

SAMA0501W Closing session failed.

Explanation: An error was encountered, when thesession with RMC was closed.

System action: The session may not have been closed.


SAMA0502W Unable to locate resource with name:name, class: class, node: node.

Explanation: The resource identified in an event byname, class, and node could not be found.

System action: The resource is not updated with eventinformation.

Operator response: Check if the resource exists. Verifythe status of the resource.

SAMA0503W Automation mode on domain domainhas changed from mode1 to mode2.

Explanation: The automation mode can be Auto(resources are automated) or Manual (resources areonly monitored).


Operator response: Check if the automation mode hasbeen modified intentionally.

SAMA0504W The location of the automation policypool location was not found on nodenode.

Explanation: When trying to show the list of availablepolicies, the Policy pool location was not found on thenode where the adapter currently runs.

System action: No policies for activation are provided.

Operator response: Use the configuration dialog'cfgsamadapter' to specify a 'Policy pool location',which is the directory where automation policy files arestored for activation. If a policy from that location isshown as active policy, it may have been activated fromanother node in the domain, where the policy poolexists. Make sure the policies are copied to all othernodes in the domain.

SAMA0505W The policy file " policyFile " for thecurrently active policy is not in thepolicy file pool " policyPool ".

Explanation: The active policy once was successfullyactivated from the file from a path that is not theconfigured policy pool.

System action: The currently active policy is notadded to the list of policies in the policy pool.

Operator response: If the file had been activated, usecommand 'sampolicy -a filename' move the file to thepolicy pool and activate the policy again from thepolicy path. Otherwise, use cfgsamadapter to correctthe policy pool path to the file path of the currentlyactive policy.

SAMA0064E • SAMA0505W


SAMA0610I Command reset from non-recoverableerror has been performed on resourceresource on behalf of user userid.

Explanation: A user found a resource flagged withnon-recoverable error by automation which means theresource is not automated until a user issued the reset.

System action: The reset has been issued to theresource.

Operator response: No action is required. You canverify in the operations console if the resource is nomore in error.

SAMA0611I Command request has been performedon resource resource with return code:return-code on behalf of user userid withcomment: comment.

Explanation: A user has issued a command thatrequests a change of the resource state. This commandis being performed by automation on the indicatedresource.

System action: The command has been issued to theresource.

Operator response: No action is required. You canverify in the operations console if the resource changedits state.

SAMA0612I Node node has been excluded fromautomation on behalf of user userid.




SAMA0613I Node node has been included intoautomation on behalf of user userid.




SAMA0614I A request to move resource groupresource away from nodes node has beenperformed with return code: return-codeon behalf of user userid with comment:comment.

Explanation: A user has issued a request to move aresource group away from one or more nodes. Thecommand is being performed by automation.



SAMA0615I A request to move resource groupresource to node node has been performedwith return code: return-code on behalfof user userid with comment: comment.

Explanation: A user has issued a request to move aresource group to another node. The command is beingperformed by automation.



SAMA0616I Node node has been excluded fromautomation on behalf of user userid withcomment: comment.




SAMA0617I Node node has been included intoautomation on behalf of user userid withcomment: comment.




SAMA0610I • SAMA0617I



Using IBM Support Assistant

IBM Support Assistant is a free, standalone application that you can install on anyworkstation. IBM Support Assistant saves you time searching product, support,and educational resources and helps you gather support information when youneed to open a problem management record (PMR) or Electronic Tracking Record(ETR), which you can then use to track the problem.

You can then enhance the application by installing product-specific plug-inmodules for the IBM products you use. The product-specific plug-in for TivoliSystem Automation for Multiplatforms provides you with the following resources:v Support linksv Education linksv Ability to submit problem management reportsv Capability to collect traces

Installing IBM Support Assistant and the Tivoli System Automation forMultiplatforms plug-in

To install the IBM Support Assistant V4.1, complete these steps:v Go to the IBM Support Assistant Web site:

www.ibm.com/software/support/isa/

v Download the installation package for your platform. Note that you will need tosign in with an IBM user ID and password (for example, a MySupport ordeveloperWorks® user ID). If you do not already have an IBM user ID, you maycomplete the free registration process to obtain one.

v Uncompress the installation package to a temporary directory.v Follow the instructions in the Installation and Configuration Guide, included in

the installation package, to install the IBM Support Assistant.

To install the plug-in for System Automation for Multiplatforms, complete thesesteps:1. Start the IBM Support Assistant application. IBM Support Assistant is a web

application that is displayed in the default, system configured web browser.2. Click the Updater tab within IBM Support Assistant.3. Click the New Products and Tools tab. The plug-in modules are listed by

product family.4. Select Tivoli > Tivoli System Automation for Multiplatforms.5. Select the features you want to install and click Install. Be sure to read the

license information and the usage instructions.6. Restart IBM Support Assistant.


http://www.ibm.com/software/support/isa/


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationMail Station P3002455 South RoadPoughkeepsie New York 12601-5400U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law: INTERNATIONAL


BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. Some states do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM web sites are provided forconvenience only and do not in any manner serve as an endorsement of those websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those web sites is at your own risk.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

TrademarksIBM, the IBM logo, ibm.com®, are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both. If these and other IBM trademarked terms are marked on their firstoccurrence in this information with a trademark symbol (® or ™), these symbolsindicate U.S. registered or common law trademarks owned by IBM at the time thisinformation was published. Such trademarks may also be registered or commonlaw trademarks in other countries.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,and/or other countries.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

UNIX is a registered trademark of The Open Group in the United States and othercountries.


Index

Aagentless adapter

fails to connect 30log files 30refresh states 31

AIX systemsmultiple CPUs 15

automation domaindatabase cleanup timeout 12

automation enginecommand-line options 43, 97eezdmn command 97log and trace files 2stopping 97troubleshooting 21XML log file, viewing 2

automation JEE frameworklog and trace files 2

automation managerfails to initialize 18

automation policyagentless adapter

XML reference 129automation policy rules 124AutomationDomain

XML element 103AutomationDomainName

XML element 104, 130AutomationPolicy

XML element 104, 130AvailabilityTarget 105

BBox XML element 152business-critical workload policy

rules 161

Ccfgeezdmn command 81cfghacadapter command 85cfgmscsadapter command 87cfgvcsadapter command 89choice groups

rules 124ChoiceGroup

XML element 105chprefmbr command 44chtarget command 46Class

XML element 107Class XML element 153ClassAttributesReference

XML element 131Cluster-SubState

PowerHA clusters 26command shell

troubleshooting 21

command shell commandsoverview 43

command-line interface commands 97command-line options

automation engine 43, 97commands

cfgeezdmn 81cfghacadapter 85cfgmscsadapter 87cfgvcsadapter 89chprefmbr 44chtarget 46command shell 43command-line interface 97configuration 81connect 47controlling adapters 91eezaladapter 91eezcs 48eezctrl 52eezdiag 54eezdla 100eezgdpsagent 96eezhwadapter 92eezpolicy 57eezpolicychecker 100hacadapter 94help 59lsclustersets 61lseezdom 62lsnode 64lsrel 66lsres 68lsresreq 71nodereq 73quit 75resetres 75resreq 76vcsadapter 95

commands reference 43components

traceable 3configuration

troubleshooting 39configuration commands

overview 81connect command 47controlling adapter commands 91conversion-only mode 97CORBA.NO_RESPONSE

errors 12

Ddata

mapping 102reduction 102

data modelmapping 101

DescriptionXML element 107, 131

DesiredRoleXML element 108

DesiredStateXML element 108

disaster recovery choice groups, policyrules 162

disaster recovery policyXML reference 151

disaster recovery policy rules 161discretionary workload policy rules 161distributed disaster recovery

log files 3Distributed Disaster Recovery

troubleshooting 22domain log

OutOfMemory exception 4Domain XML element 154domains

displaying, troubleshooting 6drml file

XML reference 152DRPolicy

XML element 109DRPolicy XML element 155

Ee-mail address xve2einstallerlogs

log file collector utility 37EEZ prefix 219eezaladapter command 91EEZBus

resolving problems 16eezcs command 48eezctrl command 52eezdiag command 54eezdla command 100eezdmn command

options-h 97instcert 97start 97status 97stop 97

using 97eezgdpsagent l command 96eezhwadapter command 92

options-help 92-monitor 92-shutdown 92-start 92

EEZIMEARtroubleshooting 20

eezinstall.logNoClassDefFoundError 36

eezpolicy command 57eezpolicychecker command 100end-to-end automation policies

XML reference 102, 129


environment variablesJava EE framework 10

event path errorresolving 16

FFOC adapter

installation directory 26installation log files 26log files 26troubleshooting 26, 37

GGDPS agent

return codes 22troubleshooting 22

Hhacadapter command 94HardwareManagementTask XML

element 156help command 59HMC access

resolving timeout problems 10

IIBM Dashboard Application Services Hub

event path error 16IBM.ITMResourceAttributes

XML element 132IBM.RemoteApplicationAttributes

XML element 132IllegalMonitorStateException

troubleshooting 15InfoLink

XML element 109, 133installation

troubleshooting 33ISO 9000 xiv

JJava EE framework

environment variables 10

Llog file collector utility 37log files

automation engine 2distributed disaster rec... 3JEE framework 2locations 1multilingual environment 3

log viewer 2lsclustersets command 61lseezdom command 62lsnode command 64lsrel command 66lsres command 68

lsresreq command 71

MMembers

XML element 111messages

EEZ 220EEZ prefix 219overview 181policy editor 181PowerHA adapter 344VCS Solaris adapter 340

MessagesEEZA0001E 220EEZA0002E 220EEZA0003E 221EEZA0004E 221EEZA0006E 221EEZA0007E 221EEZA0008E 221EEZA0009E 221EEZA0010E 221EEZA0011E 221EEZA0012E 221EEZA0013E 221EEZA0014E 222EEZA0015E 222EEZA0017E 222EEZA0022E 222EEZA0023E 222EEZA0024E 222EEZA0025E 222EEZA0026E 222EEZA0027E 222EEZA0028E 222EEZA0029E 222EEZA0030E 223EEZA0031E 223EEZA0032E 223EEZA0033E 223EEZA0036E 223EEZA0037E 223EEZA0038E 223EEZA0039E 223EEZA0040E 223EEZA0041E 223EEZA0042E 224EEZA0043E 224EEZA0045E 224EEZA0047E 224EEZA0051W 224EEZA0052E 224EEZA0053E 224EEZA0055E 224EEZA0056I 224EEZA0057E 225EEZA0058E 225EEZA0059E 225EEZA0060I 225EEZA0061E 225EEZA0062I 225EEZA0063I 225EEZA0064I 225EEZA0070E 225EEZA0071E 226EEZA0100I 226

Messages (continued)EEZA0101I 226EEZA0102I 226EEZA0103I 226EEZA0104I 226EEZA0105I 226EEZA0111I 226EEZA0112I 226EEZA0113I 226EEZA0114I 226EEZA0115I 227EEZA0116I 227EEZA9991E 227EEZA9992E 227EEZB0001E 227EEZB0003E 227EEZB0015E 227EEZB0025E 227EEZB0030E 227EEZB0031E 228EEZB0033E 228EEZC0001I 228EEZC0002I 228EEZC0003I 228EEZC0004I 228EEZC0006E 228EEZC0007E 229EEZC0008E 229EEZC0009E 229EEZC0010E 229EEZC0011E 229EEZC0012E 229EEZC0013E 230EEZC0014E 230EEZC0015E 230EEZD0002E 230EEZD0003E 230EEZD0004E 230EEZD0005E 230EEZD0006E 231EEZD0007E 231EEZD0008E 231EEZD0009E 231EEZD0010E 231EEZD0013E 231EEZD0014E 231EEZD0015E 231EEZD0016E 231EEZD0017E 232EEZD0019E 232EEZD0020E 232EEZD0021E 232EEZD0022E 232EEZD0023E 232EEZD0024E 232EEZD0025E 232EEZD0027E 232EEZD0028E 233EEZD0029E 233EEZD0030E 233EEZD0032E 233EEZD0033E 233EEZD0034E 233EEZD0035E 233EEZD0036E 233EEZD0037E 234EEZD0038E 234


Messages (continued)EEZD0039E 234EEZD0040E 234EEZD0041E 234EEZD0042E 234EEZD0050E 234EEZD0060E 234EEZD0061E 235EEZD0062E 235EEZD0063E 235EEZD0064E 235EEZD0065E 235EEZD0066E 235EEZD0067E 235EEZD0068E 236EEZD0069E 236EEZD0072E 236EEZD0073E 236EEZD0074E 236EEZD0075E 236EEZD0080E 236EEZD0081E 237EEZD0082E 237EEZD0083E 237EEZD0084E 237EEZD0084W 237EEZD0085E 237EEZD0086E 237EEZD0100E 237EEZD0101E 238EEZD0102E 238EEZD0103E 238EEZD0104E 238EEZD0105E 238EEZD0106E 238EEZD0107E 238EEZD0110E 238EEZD0111E 238EEZD0112E 239EEZD0113E 239EEZD0114E 239EEZD0115E 239EEZD0116E 239EEZD0117E 239EEZD0118E 239EEZD0119E 240EEZD0120E 240EEZD0121E 240EEZD0122E 240EEZD0123E 240EEZD0124E 240EEZD0125E 241EEZD0126E 241EEZD0127E 241EEZD0128E 241EEZD0129E 241EEZD0130E 241EEZD0131E 241EEZD0132E 241EEZD0140E 241EEZD0150E 242EEZD0151E 242EEZD0152E 242EEZD0160E 242EEZD0161E 242EEZD0200E 242EEZD1004W 242

Messages (continued)EEZD1005W 242EEZD1010W 243EEZD1011W 243EEZD1012W 243EEZD1013W 243EEZD1014W 243EEZD1015W 243EEZD1016W 243EEZD1017W 244EEZD1018W 244EEZD1020W 244EEZD1021W 244EEZD1022W 244EEZD1071W 244EEZD1072W 245EEZD1073W 245EEZD1074W 245EEZD1075W 245EEZD1076W 245EEZD2001I 245EEZD2002I 245EEZD2003I 246EEZD2004I 246EEZD2005I 246EEZD2010I 246EEZD2011I 246EEZD2012I 246EEZD2013I 246EEZD2020I 246EEZD2021I 246EEZD2022I 246EEZD2023I 247EEZD2024I 247EEZD2025I 247EEZD2030I 247EEZD2031I 247EEZD2032I 247EEZD2033I 247EEZD2034I 247EEZD2035I 247EEZD2036I 248EEZD2040I 248EEZD2041I 248EEZD2050I 248EEZE0001E 248EEZE0002E 248EEZE0003E 248EEZE0004E 248EEZE0005E 248EEZE0006E 249EEZE0007E 249EEZE0008E 249EEZE0009E 249EEZE0010E 249EEZE0011E 249EEZE0012E 249EEZE0013E 249EEZE0014E 250EEZE0015E 250EEZE1000W 250EEZE1001W 250EEZE1002W 250EEZE1003W 250EEZE2000I 250EEZE2001I 250EEZE2002I 251

Messages (continued)EEZF0001E 251EEZF0003E 251EEZF0006E 251EEZF0007E 251EEZF0011E 251EEZF0012E 251EEZF0014E 251EEZF0015E 252EEZF0016E 252EEZF0017E 252EEZF0019E 252EEZF0031E 252EEZF0032E 252EEZF0033E 252EEZF0034E 252EEZF0035E 253EEZF0036E 253EEZF0037E 253EEZF0038E 253EEZF0501W 253EEZF0502W 253EEZG0001E 253EEZG0002E 253EEZG0003E 254EEZG0004E 254EEZG0005E 254EEZG0006E 254EEZG0007E 254EEZG0008E 254EEZG0009E 254EEZG0010E 254EEZG0011E 254EEZG1000W 254EEZG2001I 255EEZG2002I 255EEZG2003I 255EEZG2004I 255EEZH0001E 255EEZH0002E 255EEZH0003E 255EEZH0004E 255EEZH0010E 255EEZH0011E 256EEZH0012E 256EEZH0013E 256EEZH0014E 256EEZH0015E 256EEZH0016E 256EEZH0017E 256EEZH0018E 257EEZH0019E 257EEZH0020E 257EEZH0021E 257EEZH0022E 257EEZH0023E 257EEZH0024E 258EEZH0025E 258EEZH0026E 258EEZH0027E 258EEZH0028E 258EEZH0029E 258EEZH0030E 258EEZH0031W 258EEZH0032W 259EEZH0033W 259EEZH0034E 259

Index 359

Messages (continued)EEZH0035E 259EEZH0036W 259EEZH0037I 259EEZH0038I 260EEZH0039E 260EEZH0040E 260EEZH0041I 260EEZH0042I 260EEZH0043E 260EEZH0044I 260EEZH0045I 260EEZH0046I 261EEZH0047I 261EEZH0048I 261EEZH0049I 261EEZH0050E 261EEZH0051E 261EEZH0052E 261EEZH0053E 261EEZH0054E 261EEZH0055I 261EEZH0056I 262EEZH0057E 262EEZH0058E 262EEZH0059I 262EEZH0060I 262EEZH0061E 262EEZH0062I 263EEZH0063I 263EEZH0064E 263EEZH0065I 263EEZH0066I 263EEZH0068I 263EEZH0069I 263EEZH0070E 264EEZH0071E 264EEZH0072E 264EEZH0073E 264EEZH0074I 264EEZH0075E 265EEZH0076E 265EEZH0077E 265EEZH0078E 265EEZH0079E 265EEZH0080E 266EEZH0081E 266EEZH0082E 266EEZH0083E 266EEZH0084E 266EEZH0085E 267EEZH0086E 267EEZH0087E 267EEZH0088E 267EEZH0089E 267EEZH0090E 267EEZH0091E 268EEZH0092E 268EEZH0093E 268EEZH0094I 268EEZH0095I 268EEZH0096E 268EEZH0097I 268EEZH0098I 269EEZI0001E 269EEZI0003E 269EEZI0005E 269

Messages (continued)EEZI0012E 269EEZI0013E 269EEZI0014E 269EEZI0015E 269EEZI0016E 269EEZI0017E 270EEZI0018E 270EEZI0019E 270EEZI0021E 270EEZI0022E 270EEZI0023E 270EEZI0031E 270EEZI0032E 270EEZI0041E 271EEZI0042E 271EEZI0044E 271EEZI0046E 271EEZI0047E 271EEZI0048E 271EEZI0049E 271EEZI0050E 271EEZI0051E 271EEZI0052E 272EEZI0053E 272EEZI0054E 272EEZI0055E 272EEZI0056E 272EEZI0057E 272EEZI0058E 272EEZI0059E 272EEZI0060E 273EEZI0061E 273EEZI0062E 273EEZI0063E 273EEZI0064E 273EEZI0501W 273EEZI0502W 273EEZI0503W 274EEZI0504W 274EEZI0545W 274EEZI2001I 274EEZI2002I 274EEZI2003I 274EEZI2004I 274EEZJ0001E 274EEZJ0002E 275EEZJ0003E 275EEZJ0004E 275EEZJ0005E 275EEZJ0006E 275EEZJ0007E 275EEZJ0008E 275EEZJ0009E 276EEZJ0010E 276EEZJ0011E 276EEZJ0013E 276EEZJ0014E 276EEZJ0015E 276EEZJ0016E 276EEZJ0017E 276EEZJ0018E 277EEZJ0019E 277EEZJ0020E 277EEZJ0021E 277EEZJ0022E 277EEZJ0023E 277

Messages (continued)EEZJ0024E 277EEZJ0025E 277EEZJ0026E 278EEZJ0029E 278EEZJ0030E 278EEZJ0031E 278EEZJ0032E 278EEZJ0033E 278EEZJ0034E 278EEZJ0035E 279EEZJ0036E 279EEZJ0037E 279EEZJ0038E 279EEZJ0039E 279EEZJ0040E 279EEZJ0041E 279EEZJ0042E 280EEZJ0043E 280EEZJ0044E 280EEZJ0045E 280EEZJ0046E 280EEZJ0047E 280EEZJ0048E 280EEZJ0049E 280EEZJ0050E 281EEZJ0051E 281EEZJ0052E 281EEZJ0053E 281EEZJ0054E 281EEZJ0055E 281EEZJ0056E 281EEZJ0057E 281EEZJ0058E 281EEZJ0059E 282EEZJ0060E 282EEZJ0061E 282EEZJ0062E 282EEZJ0063E 282EEZJ0064E 282EEZJ0065E 283EEZJ0066E 283EEZJ0067E 283EEZJ0068E 283EEZJ0069E 283EEZJ0070E 283EEZJ0071E 283EEZJ0072E 283EEZJ0073E 284EEZJ0074E 284EEZJ0075E 284EEZJ0076E 284EEZJ0100E 284EEZJ0101E 284EEZJ0102E 284EEZJ0103E 285EEZJ0104E 285EEZJ0105E 285EEZJ0106E 285EEZJ0107E 285EEZJ0108E 285EEZJ0109E 285EEZJ0110E 285EEZJ0111E 285EEZJ0112E 286EEZJ0113E 286EEZJ0114E 286


Messages (continued)EEZJ0115E 286EEZJ0116E 286EEZJ0117E 286EEZJ0119E 286EEZJ0501W 287EEZJ0509W 287EEZJ0510W 287EEZJ0511W 287EEZJ0512W 287EEZJ0513W 287EEZJ0514W 287EEZJ0515W 288EEZJ0516W 288EEZJ0600W 288EEZJ0601W 288EEZJ0602W 288EEZJ0603W 288EEZJ0604W 288EEZJ0605W 289EEZJ1000I 289EEZJ1001I 289EEZJ1002I 289EEZJ1003I 289EEZJ1004I 289EEZJ1005I 289EEZJ1006I 290EEZJ1008I 290EEZJ1013I 290EEZJ1014I 290EEZJ1015I 290EEZJ1016I 290EEZJ1017I 290EEZJ1018I 290EEZJ1019I 291EEZJ1020I 291EEZJ1100I 291EEZJ1101I 291EEZJ1604I 289EEZK0003E 291EEZK0004E 291EEZK0005E 291EEZK0006E 291EEZK0007E 292EEZK0008E 292EEZK0009E 292EEZL0001E 292EEZL0002E 292EEZL0003E 292EEZL0004E 292EEZL0005E 293EEZL0015E 293EEZL0016E 293EEZL0017E 293EEZL0018E 293EEZL0019E 293EEZL0020E 293EEZL0021E 293EEZL0022E 293EEZL0023E 293EEZL0024E 293EEZL0025E 294EEZL0030E 294EEZL0031E 294EEZL0032E 294EEZL0033E 294EEZL0034E 294

Messages (continued)EEZL0040E 294EEZL0501W 294EEZL0510W 295EEZP0001E 295EEZP0002E 295EEZP0003E 295EEZP0004E 295EEZP0005E 295EEZP0006E 295EEZP0007E 295EEZP0008E 295EEZP0009E 296EEZP0010E 296EEZP0011E 296EEZP0012E 296EEZP0013E 296EEZP0014E 296EEZP0015E 296EEZP0016E 296EEZP0017E 296EEZP0018E 296EEZP0019E 297EEZP0020E 297EEZP0021E 297EEZP0022E 297EEZP0023E 297EEZP0024E 297EEZP0025E 297EEZP0026E 297EEZP0027E 298EEZP0029E 298EEZP0030E 298EEZP0032E 298EEZP0033E 298EEZP0034E 298EEZP0035E 298EEZP0036E 298EEZP0037E 299EEZP0038E 299EEZP0039E 299EEZP0040E 299EEZP0041E 299EEZP0042E 299EEZP0043E 299EEZP0044E 299EEZP0045E 300EEZP0047E 300EEZP0048E 300EEZP0049E 300EEZP0050E 300EEZP0051E 300EEZP0052E 300EEZP0053E 301EEZP0054E 301EEZP0055E 301EEZP0056E 301EEZP0058E 301EEZP0059E 301EEZP0060E 301EEZP0061E 301EEZP0062E 302EEZP0063E 302EEZP0064E 302EEZP0065E 302EEZP0066E 302EEZP0067E 302

Messages (continued)EEZP0068E 302EEZP0069E 302EEZP0070E 302EEZP0071E 302EEZP0072E 303EEZP0073E 303EEZP0074E 303EEZP0075E 303EEZP0076E 303EEZP0077E 303EEZP0078E 303EEZP0079E 303EEZP0080E 304EEZP0081E 304EEZP0082E 304EEZP0083E 304EEZP0084E 304EEZP0085E 304EEZP0086E 304EEZP0087E 305EEZP0088E 305EEZP0089E 305EEZP0090E 305EEZP0500W 305EEZP0502W 305EEZP0503W 305EEZP0504W 305EEZP0505W 306EEZP0506W 306EEZP0507W 306EEZP2003I 306EEZP2004I 306EEZP2005I 306EEZP2006I 306EEZP2007I 306EEZP2008I 306EEZP2009I 306EEZP2011I 306EEZP2012I 306EEZP2013I 306EEZQ0001E 307EEZQ0002E 307EEZQ0003E 307EEZQ0004E 307EEZQ0005E 307EEZQ0006E 307EEZQ0007E 307EEZQ0008E 307EEZR0001E 307EEZR0002E 308EEZR0003E 308EEZR0004E 308EEZR0005E 308EEZR0006E 308EEZR0007E 308EEZR0008E 308EEZR0009E 308EEZR0010E 308EEZR0011E 309EEZR0012E 309EEZR0013E 309EEZR0014E 309EEZR0015E 309EEZR0020E 309EEZR0021E 309EEZR0036E 309

Index 361

Messages (continued)EEZR0038E 309EEZR0039E 310EEZR0040E 310EEZR0041E 310EEZR0042E 310EEZR0043E 310EEZR0044E 310EEZR0051E 310EEZR0060E 310EEZR0061E 311EEZR0062E 311EEZR0063E 311EEZR0064E 311EEZR0065E 311EEZR0066E 311EEZR0071E 312EEZR0072E 312EEZR0073E 312EEZR0074E 312EEZR0075E 312EEZR0076E 312EEZR0077E 312EEZR0079E 312EEZR0080E 312EEZR0081E 313EEZR0082E 313EEZR0083E 313EEZR0084E 313EEZR0085E 314EEZR0086E 314EEZR0087E 314EEZR0504W 314EEZR0601I 314EEZR0602I 314EEZR0610I 315EEZR0611I 315EEZR0612I 315EEZR0613I 315EEZR0614I 315EEZS0001E 315EEZS0003E 315EEZS0005E 315EEZS0006E 315EEZS0007E 316EEZS0008E 316EEZS0009E 316EEZS0010E 316EEZS0011E 316EEZS0012E 316EEZS0013E 316EEZS0014E 316EEZS0015E 316EEZS0016E 316EEZS0017E 317EEZS0018E 317EEZS0019E 317EEZS0020E 317EEZS0100I 318EEZS0101I 318EEZS0102W 318EEZS0103E 318EEZS0104I 318EEZS0105E 318EEZS0110E 318EEZS0111I 318EEZS0112E 318

Messages (continued)EEZS0114E 318EEZS0120I 319EEZS0121W 319EEZS0122E 319EEZS0123E 319EEZS0124E 319EEZS0125E 319EEZS0126E 319EEZS0127E 319EEZS0128E 319EEZS0130E 320EEZS0131E 320EEZS0131I 320EEZS0132I 320EEZS0133E 320EEZS0133I 320EEZS0134I 320EEZS0135I 320EEZS0136I 320EEZS0137I 320EEZS0140I 320EEZS0150E 320EEZS0151E 321EEZS0152W 321EEZS0153E 321EEZS0154I 321EEZS0155W 321EEZS0156E 321EEZS0157E 321EEZS0158E 321EEZS0159E 321EEZS0160E 321EEZS0161I 322EEZS0185E 317EEZS0207E 317EEZS0208I 322EEZS0220I 322EEZS0221E 322EEZS0222E 322EEZS0223E 317EEZS0224E 317EEZS0225E 317EEZS0227E 317EEZS0233E 322EEZS0234E 322EEZS0240I 322EEZS0241E 322EEZS0250E 323EEZS0260E 323EEZS0344E 317EEZS0345E 318EEZT0001W 323EEZT0002I 323EEZT0003W 323EEZT0004E 323EEZT0005E 323EEZT0006I 323EEZT0007E 323EEZT0008I 324EEZT0009W 324EEZT0010I 324EEZT0011W 324EEZT0012W 324EEZT0013E 324EEZT0014W 324EEZT0015I 324

Messages (continued)EEZT0016I 324EEZT0017I 325EEZT0750W 325EEZT0753I 325EEZT0754W 325EEZT0756I 325EEZT0758I 325EEZT0759W 325EEZT0770I 325EEZT0771I 325EEZT0778I 325EEZT0779I 326EEZT0786W 326EEZT0789E 326EEZT0790E 326EEZT0791I 326EEZT0792I 326EEZT0793I 326EEZT0794I 326EEZT0800E 327EEZT0801I 327EEZT0802E 327EEZT0803I 327EEZT0804E 327EEZT0805I 327EEZU0001E 327EEZU0002E 327EEZU0003E 327EEZU0004E 327EEZU0005E 328EEZU0006E 328EEZU0007E 328EEZU0008E 328EEZU0010E 328EEZU0011E 328EEZU0012E 328EEZU0013E 329EEZU0015E 329EEZU0016E 329EEZU0017E 329EEZU0018E 329EEZU0019E 329EEZU0020E 330EEZU0021E 330EEZU0022E 330EEZU0023E 330EEZU0024E 330EEZU0025E 330EEZU0026E 331EEZU0027E 331EEZU0028E 331EEZU0029E 331EEZU0030E 331EEZU0031E 331EEZU0032E 331EEZU0100E 333EEZU0101E 333EEZU0102E 334EEZU0103E 334EEZU0500W 331EEZU0501W 332EEZU0502W 332EEZU0503W 332EEZU0504W 332EEZU0505W 332EEZU0506W 332


Messages (continued)EEZU0507W 332EEZU0508W 332EEZU0509W 333EEZU0510W 333EEZU0511W 333EEZU0512W 333EEZU0520W 333EEZU0550W 333EEZU0601W 334EEZU0602W 334EEZU0603E 334EEZU0603W 334EEZU0604E 334EEZU0605E 334EEZU0606E 335EEZU0607E 335EEZU0608E 335EEZU0609E 335EEZU0610E 335EEZU0611E 335EEZU1000I 335EEZU2000I 335EEZU2000W 336EEZU2001I 335EEZU2002E 336EEZU2002I 335EEZU2002W 336EEZU2003I 336EEZU2004I 336EEZU2005I 336EEZV0001E 340EEZV0002E 340EEZV0003E 340EEZV0010E 341EEZV0011E 341EEZV0013E 341EEZV0016E 341EEZV0018E 341EEZV0020E 341EEZV0022E 341EEZV0035E 341EEZV0037E 341EEZV0038E 342EEZV0040E 342EEZV0041E 342EEZV0042E 342EEZV0043E 342EEZV0044E 342EEZV0046E 342EEZV0047E 342EEZV0051E 342EEZV0502W 343EEZV0610I 343EEZV0611I 343EEZV0612I 343EEZV0613I 343EEZV0614I 343EEZY0001E 336EEZY0002E 336EEZY0003E 336EEZY0004E 336EEZY0005E 337EEZY0006E 337EEZY0007E 337EEZY0008E 337EEZY0009E 337

Messages (continued)EEZY0010E 337EEZY0011E 337EEZY0012E 337EEZY0013E 337EEZY2001I 338EEZZ0001E 338EEZZ0002E 338EEZZ0003E 338EEZZ0004E 338EEZZ0005E 338EEZZ0006E 338EEZZ0007E 339EEZZ0008E 339EEZZ0009E 339EEZZ0010E 339EEZZ0011E 339EEZZ0012E 339EEZZ2001I 339EEZZ2002I 339EEZZ2003I 340EEZZ2004I 340EEZZ2005I 340EEZZ2006I 340

MonitorAttributeXML element 133

MonitorCommandXML element 134

MonitorCommandPeriodXML element 135

MonitorCommandReturnCodesXML element 135

MonitorCommandTimeoutXML element 136

MonitorQueryAttrFilterXML element 136

MonitorValueFailedOfflineXML element 137

MonitorValueOfflineXML element 138

MonitorValueOnlineXML element 139

MonitorValueStartingXML element 139

MonitorValueStoppingXML element 140

MonitorValueUnknownXML element 140

multilingual characterscommand shell 21

multilingual environmentlog files 3operations console 5

NName

XML element 111NoClassDefFoundError

eezinstall.log 36Node

XML element 110Node XML element 157nodereq command 73notices 355

Ooperations console

log and trace files 2time zone settings 14

ORB request timeout 12ORB service 12OutOfMemory exception

domain log 4OutOfMemoryError

log files 15Owner

XML element 112, 141

Ppolicies

rulesautomation policy 124disaster recovery policy 161

sample policy 125worksheet 162XML elements

AutomationDomain 103AutomationDomainName 104,

130AutomationPolicy 104, 130Box 152ChoiceGroup 105Class 107, 153ClassAttributesReference 131Description 107, 131DesiredRole 108DesiredState 108Domain 154DRPolicy 109, 155HardwareDevice 155HardwareManagementTask 156IBM.ITMResourceAttributes 132IBM.RemoteApplicationAttribute 132InfoLink 109, 133Members 111MonitorAttribute 133MonitorCommand 134MonitorCommandPeriod 135MonitorCommandReturnC... 135MonitorCommandTimeout 136MonitorQueryAttrFilter 136MonitorValueFailedOffline 137MonitorValueOffline 138MonitorValueOnline 139MonitorValueStarting 139MonitorValueStopping 140MonitorValueUnknown 140Name 111Node 110, 157Owner 112, 141PolicyAuthor 112, 141PolicyDescription 113, 142PolicyInformation 113, 142PolicyName 114, 142PolicyToken 114, 143Property 143ReferencedReplicationRe... 115ReferencedResource 115Relationship 116RemotePort 144

Index 363

policies (continued)XML elements (continued)

RemoteProtocol 144ReplicationDomain 117ReplicationReference 117ResourceGroup 119ResourceReference 119Script 157Site 158Slot 159SNMPAgent 160Source 122StartCommand 146StartCommandTimeout 148StopCommand 148StopCommandTimeout 149Target 122Type 123UserName 150

XML reference 102, 129, 151, 152policy

XMLautomation policy 129

policy editormessages 181troubleshooting 29

PolicyAuthorXML element 112, 141

PolicyDescriptionXML element 113, 142

PolicyInformationXML element 113, 142

PolicyNameXML element 114, 142

PolicyTokenXML element 114, 143

PowerHA adapterdoes not connect to host 25does not start 25log file locations 25messages 344terminates 25trace logging level

increasing 24troubleshooting 24

PowerHA clustersAdditional Info page 26Cluster-SubState 26

PowerHA resource groupsstarting fails 26stopping fails 26

PropertyXML element 143

Qquit command 75

RReferencedReplicationResource

XML element 115ReferencedResource

XML element 115Relationship

XML element 116

relationshipsrules 124

RemotePortXML element 144

RemoteProtocolXML element 144

ReplicationDomainXML element 117

ReplicationReferenceXML element 117

resetres command 75resource groups

rules 124resource states

analyze 31ResourceGroup

XML element 119ResourceReference

XML element 119resreq command 76restart workflow 4return codes

GPDS agent 22rules

automation policy rules 124business-critical workload 161choice groups 124cluster sets 161disaster recovery choice groups 162disaster recovery policy 161discretionary workload 161domains 161general 125relationships 124resource groups 124sites 161unique resource names 125

SSAMA0001E 344SAMA0002E 344SAMA0003E 344SAMA0004E 344SAMA0005E 344SAMA0006E 344SAMA0007E 344SAMA0008E 344SAMA0009E 345SAMA0010E 345SAMA0011E 345SAMA0013E 345SAMA0016E 345SAMA0018E 345SAMA0019E 345SAMA0020E 345SAMA0022E 345SAMA0023E 345SAMA0024E 346SAMA0025E 346SAMA0026E 346SAMA0027E 346SAMA0028E 346SAMA0029E 346SAMA0033E 346SAMA0034E 346SAMA0035E 346

SAMA0036E 346SAMA0037E 347SAMA0038E 347SAMA0039E 347SAMA0040E 347SAMA0041E 347SAMA0042E 347SAMA0043E 347SAMA0044E 347SAMA0045E 347SAMA0046E 348SAMA0047E 348SAMA0048E 348SAMA0049E 348SAMA0050E 348SAMA0051E 348SAMA0052E 348SAMA0053E 348SAMA0054E 349SAMA0055E 349SAMA0056E 349SAMA0057E 349SAMA0058E 349SAMA0059E 349SAMA0060E 349SAMA0061E 349SAMA0062E 349SAMA0063E 349SAMA0064E 350SAMA0065E 350SAMA0066E 350SAMA0500W 350SAMA0501W 350SAMA0502W 350SAMA0503W 350SAMA0504W 350SAMA0505W 350SAMA0610I 351SAMA0611I 351SAMA0612I 351SAMA0613I 351SAMA0614I 351SAMA0615I 351SAMA0616I 351SAMA0617I 351sample policy 125sample.xml 125Script XML element 157security exception 9selection strings

using 79ServerGroup 121Site XML element 158Slot XML element 159smart refresh

messages 340SNMPAgent XML element 160Source

XML element 122special characters

XML 103StartCommand

XML element 146StartCommandTimeout

XML element 148starting

automation engine 97


StopCommandXML element 148

StopCommandTimeoutXML element 149

stoppingautomation engine 97

support 1

TTarget

XML element 122time zone settings 14timeouts

resolving problems 10Tivoli Common Directory 1trace files

automation engine 2JEE framework 2locations 1

traceablecomponents 3

trademarks 356troubleshooting 1

administration 1automation engine 21command shell 21

multibyte characters 21configuration 39DB2

connection problem 14Distributed Disaster Recovery 22EEZIMEAR 20FOC adapter 26, 37GPDS agent 22installation 33policy editor 29PowerHA adapter 24VCS adapter 29WebSphere Application Server 15

connection problem 14Type

XML element 123

UUninstalling manually

FOC adapter 38unique resource names

rules 125user roles 178UserName

XML element 150

VVCS adapter

installation directory 29log files 29troubleshooting 29

VCS Solaris adaptermessages 340

vcsadapter command 95

Wwatchdog

infrastructure 13monitoring 11, 13

Web browsersmultiple browser windows 5

WebSphere Application Serverconnection problem

troubleshooting 14troubleshooting 15

what's new4.1 xvii

worksheetfor disaster recovery policy

definition 162

XXML

special characters 103XML elements

Box 152Class 153Domain 154DRPolicy 155HardwareDevice 155HardwareManagementTask 156Node 157Script 157Site 158Slot 159SNMPAgent 160

XML reference 129

ZzEnterprise HMC access

resolving timeout problems 10

Index 365


Readers’ Comments — We'd Like to Hear from You

System Automation Application ManagerReference and Problem Determination GuideVersion 4.1

Publication No. SC34-2703-01

We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,organization, subject matter, or completeness of this book. The comments you send should pertain to only theinformation in this manual or product and the way in which the information is presented.

For technical questions and information about products and prices, please contact your IBM branch office, yourIBM business partner, or your authorized remarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in anyway it believes appropriate without incurring any obligation to you. IBM or any other organizations will only usethe personal information that you supply to contact you about the issues that you state on this form.

Comments:

Thank you for your support.

Submit your comments using one of these channels:v Send your comments to the address on the reverse side of this form.v Send a fax to the following number: (+49)+7031-16-3456v Send your comments via email to: [email protected] Send a note from the web page: http://www.ibm.com/support/knowledgecenter/SSPQ7D/welcome

If you would like a response from IBM, please fill in the following information:

Name Address

Company or Organization

Phone No. Email address

Readers’ Comments — We'd Like to Hear from YouSC34-2703-01

SC34-2703-01

IBM®Cut or FoldAlong Line

Cut or FoldAlong Line

Fold and Tape Please do not staple Fold and Tape

Fold and Tape Please do not staple Fold and Tape

NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES

BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

IBM Deutschland Research and Development GmbHDepartment 3248Schoenaicher Str. 22071032 BoeblingenGermany

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

_

IBM®

Product Number: 5724-S92

Printed in USA

SC34-2703-01

Date post:	10-Sep-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

Tivoli System Automation Application Manager V4.1.0.1: … · 2018. 7. 30. · Edition Notices...

Documents