reference guide...figure 1. symbols used in this guide iso 9000 iso 9000 registered quality systems...
TRANSCRIPT
Tivoli System Automation for MultiplatformsVersion 4.1.0.6
Reference Guide
IBM
SC34-2700-04
Note!
Before using this information and the product it supports, read the information in “Notices” on page267.
This edition of System Automation for Multiplatforms Reference Guide applies to Version 4, Release 1, Modification 0 ofIBM Tivoli System Automation for Multiplatforms, program number 5724–M00, and to all subsequent releases andmodifications of this product until otherwise indicated in new editions.
This edition replaces SC34-2700-01.
IBM® welcomes your comments. A form for readers' comments may be provided at the back of this publication, or youmay address your comments to the following address:
IBM Deutschland Research and Development GmbHDepartment 3282Schoenaicher Str. 220D-71032 BoeblingenFederal Republic of Germany FAX (Germany): 07031 16-3456FAX (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:
Title and order number of this bookPage 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 any way itbelieves appropriate without incurring any obligation to you.© Copyright International Business Machines Corporation 2006, 2020.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.
Contents
Figures................................................................................................................ vii
Tables.................................................................................................................. ix
About this guide................................................................................................... xiWho should use this guide.......................................................................................................................... xiWhere to find more information..................................................................................................................xiConventions ................................................................................................................................................ xiISO 9000.....................................................................................................................................................xiiRelated RSCT information.......................................................................................................................... xiiHow to obtain publications........................................................................................................................ xiiHow to reach us by e-mail..........................................................................................................................xii
What's new in this release.................................................................................. xiii
Chapter 1. Troubleshooting and support.................................................................1Troubleshooting........................................................................................................................................... 1
How automation works.......................................................................................................................... 1How to obtain troubleshooting information.......................................................................................... 3Error analysis........................................................................................................................................12Problem analysis.................................................................................................................................. 16Cluster cannot be set up...................................................................................................................... 21Remote node unable to access shared disks after node crash.......................................................... 21Reporting problems..............................................................................................................................21Known problems and limitations......................................................................................................... 22Common pitfalls and user errors......................................................................................................... 22How to enable or disable ManualMode for a domain in state Offline............................................23How to increase the response time for remote resource managers during resource validation...... 23
Troubleshooting the SAP high availability solution.................................................................................. 24No valid license available when activating SAP Central Services high availability policy..................24
Troubleshooting the Oracle high availability policy..................................................................................24Oracle database listener does not start up......................................................................................... 24Oracle database process is monitored unknown................................................................................ 25
Troubleshooting the NFS tiebreaker......................................................................................................... 26NFS tiebreaker on Linux....................................................................................................................... 26NFS tiebreaker on AIX..........................................................................................................................26
Using IBM Support Assistant.....................................................................................................................26Installing IBM Support Assistant and the Tivoli System Automation for Multiplatforms plug-in .....26
Chapter 2. Reference........................................................................................... 29Commands Reference............................................................................................................................... 29
RSCT RMC commands and files........................................................................................................... 30Setting the environment variables.......................................................................................................31addrgmbr.............................................................................................................................................. 32cfgsamadapter......................................................................................................................................35chequ.................................................................................................................................................... 37chrel...................................................................................................................................................... 40chrg....................................................................................................................................................... 45chrgmbr................................................................................................................................................ 48
iii
installSAM.............................................................................................................................................51lsequ..................................................................................................................................................... 53lsrel....................................................................................................................................................... 57lsrg........................................................................................................................................................ 61lsrgreq...................................................................................................................................................66lssam.....................................................................................................................................................69lssamctrl............................................................................................................................................... 73mkequ................................................................................................................................................... 75mkrel.....................................................................................................................................................78mkrg......................................................................................................................................................82pidmon..................................................................................................................................................85prereqSAM............................................................................................................................................87rgmbrreq...............................................................................................................................................88rgreq......................................................................................................................................................91rmequ....................................................................................................................................................94rmrel..................................................................................................................................................... 95rmrg...................................................................................................................................................... 99rmrgmbr..............................................................................................................................................101samadapter........................................................................................................................................ 104samcc................................................................................................................................................. 105samctrl................................................................................................................................................109samdiag.............................................................................................................................................. 111samlicm.............................................................................................................................................. 114samlog................................................................................................................................................ 115sampolicy........................................................................................................................................... 119samsimul............................................................................................................................................ 122samwhy.............................................................................................................................................. 124uninstallSAM...................................................................................................................................... 125samnonrootuser ................................................................................................................................ 126setupAdapterNonRoot....................................................................................................................... 127Using expressions.............................................................................................................................. 129
Policy XML reference............................................................................................................................... 137XML special characters...................................................................................................................... 139AutomationPolicyTemplate............................................................................................................... 139var....................................................................................................................................................... 140include................................................................................................................................................ 141AutomationPolicy............................................................................................................................... 141PolicyInformation...............................................................................................................................142ControlInformation............................................................................................................................ 143Resource.............................................................................................................................................143MoveGroup......................................................................................................................................... 144ConcurrentGroup............................................................................................................................... 145ConstituentResource......................................................................................................................... 146ResourceGroup.................................................................................................................................. 147Relationship....................................................................................................................................... 148Equivalency........................................................................................................................................ 149ResourceReference............................................................................................................................151IBM.AgFileSystem..............................................................................................................................152IBM.Application..................................................................................................................................153IBM.ServiceIP.................................................................................................................................... 154IBM.Test............................................................................................................................................. 155IBM.TieBreaker.................................................................................................................................. 156Members.............................................................................................................................................157Description......................................................................................................................................... 158Owner................................................................................................................................................. 158InfoLink...............................................................................................................................................159Example XML policy........................................................................................................................... 159
iv
Chapter 3. Messages..........................................................................................163System Automation for Multiplatforms messages................................................................................. 163sampolicy messages............................................................................................................................ 213End-to-end automation adapter messages............................................................................................235High availability policies messages.........................................................................................................245Extended disaster recovery (xDR) feature messages.............................................................................253Adapter messages................................................................................................................................... 253
Using IBM Support Assistant..............................................................................265Installing IBM Support Assistant and the Tivoli System Automation for Multiplatforms plug-in ........265
Notices..............................................................................................................267Trademarks..............................................................................................................................................268
Index................................................................................................................ 269
v
vi
Figures
1. Symbols used in this guide.......................................................................................................................... xii
2. WebServerGroup resource group............................................................................................................. 159
vii
viii
Tables
1. Highlighting conventions used in this book................................................................................................. xi
2. System Automation for Multiplatforms commands................................................................................... 29
3. Operators that can be used in strings...................................................................................................... 132
4. Default preference rules when using operators.......................................................................................135
5. Specifying expressions in an XML file.......................................................................................................137
6. Availability of XML elements by product version..................................................................................... 137
7. XML special characters............................................................................................................................. 139
ix
x
About this guide
This guide explains how to implement and use the policy-based automated recovery capabilities that areprovided by IBM Tivoli System Automation for Multiplatforms (System Automation for Multiplatforms).
System Automation for Multiplatforms provides high-availability for resources on AIX® clusters (on IBMSystem p), Linux® clusters (on IBM System x, System z®, System i®, and System p), and Windows clusters(on IBM System x).
Who should use this guideThis guide is intended for system administrators and operators who want to use the automation andfailover capabilities of System Automation for Multiplatforms.
Where to find more informationThe Tivoli System Automation library comprises the following books, including this publication, describingTivoli System Automation for Multiplatforms:
• System Automation for Multiplatforms Administrator's and User's Guide, SC34-2698-01• Tivoli System Automation for Multiplatforms Installation and Configuration Guide, SC34-2699-01• Tivoli System Automation for Multiplatforms Reference Guide, SC34-2700-01• Tivoli System Automation for Multiplatforms High Availability Policies Guide, SC34-2660-01
You can download the complete documentation at
http://www.ibm.com/support/knowledgecenter/SSRM2X/welcome
The Tivoli System Automation library contains the following books, including this one, describing SystemAutomation Application Manager:
• System Automation Application Manager Administrator's and User's Guide, SC34-2701-00• System Automation Application Manager Installation and Configuration Guide, SC34-2702-00• System Automation Application Manager Reference and Problem Determination Guide, SC34-2703-00
You can download the books at:
http://www.ibm.com/support/knowledgecenter/SSPQ7D/welcome
The IBM Tivoli System Automation home page contains useful up-to-date information, including supportlinks and downloads for maintenance packages. You will find the IBM Tivoli System Automation homepage at:
www.ibm.com/software/tivoli/products/sys-auto-multi/
ConventionsThe following highlighting conventions are used in this book:
Table 1. Highlighting conventions used in this book
Bold Identifies commands, subroutines, keywords, files, structures, directories, and otheritems whose names are predefined by the system. Also identifies graphical objectssuch as buttons, labels, and icons that the user selects.
Italic Identifies parameters whose actual names or values are to be supplied by the user.
© Copyright IBM Corp. 2006, 2020 xi
Table 1. Highlighting conventions used in this book (continued)
monospace Identifies examples of specific data values, examples of text similar to what you mightsee displayed, examples of portions of program code similar to what you might writeas a programmer, messages from the system, or information you should actually type.
This manual uses symbols to show resources, resource groups, equivalencies, and relationships. Thesymbols used are as follows:
Figure 1. Symbols used in this guide
ISO 9000ISO 9000 registered quality systems were used in the development and manufacturing of this product.
Related RSCT informationThe following IBM Reliable Scalable Cluster Technology (RSCT) publications are available on the SystemAutomation for Multiplatforms CD:
• RSCT Administration Guide• RSCT for AIX 5L: Technical Reference• RSCT for Multiplatforms: Technical Reference• RSCT Messages• RSCT Diagnosis Guide
For more information about RSCT, see IBM Cluster systems.
For more information, see the Linux on IBM zSeries and S/390®: High Availability for z/VM® and Linux IBMRedpaper.
How to obtain publicationsThe System Automation for Multiplatforms publications are also available (valid at the time of release) atthese 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 e-mailIf you would like to contact us by e-mail, send your comments to [email protected]
xii Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
What's new in this release
Get a quick overview about the new features of System Automation for Multiplatforms version 4.1.0.Improved operations on the command line with new samcc command
System Automation for Multiplatforms version 4.1.0.2 adds a new command samcc, which can beused as operations console on the command line interface. For more information, see .
Additional platforms support
System Automation for Multiplatforms version 4.1.0.1 supports the following new platforms:
• SUSE SLES 12 (64-bit)• Red Hat RHEL 7 (64-bit)• Ubuntu 14.04 (64-bit): System x, Power Systems (Little Endian only)
System Automation for Multiplatforms version 4.1.0.2 supports the following new platforms:
• Red Hat RHEL 7.1 on Power Systems Little Endian (64-bit)
System Automation for Multiplatforms version 4.1.0.3 supports the following new platforms:
• AIX 7.2
System Automation for Multiplatforms version 4.1.0.4 supports the following new platforms:
• Ubuntu 16.04 (64-bit): System x, Power Systems (Little Endian only).
For more information, see System Automation for Multiplatforms Installation and Configuration Guide.
System Automation for Multiplatforms version 4.1.0.5 supports the following new platforms:
• SUSE SLES 15 (64-bit)• Ubuntu 18.04 (64-bit): System x, Power Systems (Little Endian only).
System Automation for Multiplatforms version 4.1.0.5 adds support for:
• SAP Netweaver 7.5.3 ENSA2.
System Automation for Multiplatforms version 4.1.0.6 supports the following new platforms:
• Red Hat RHEL 8 (64-bit)• Ubuntu 20.04 (64-bit): System x, Power Systems (Little Endian only)
System Automation for Multiplatforms version 4.1.0.6 adds support for:
• Added SAP NetWeaver support for S/4HANA 1809• Added SAP NetWeaver support for S/4HANA 1909• Added support for Oracle 19c• Added support for SAP HANA 2.0 SPS 04 Revision 046
Improved high availability policy for SAP
The SAP Central Services high availability policy is available as System Automation for Multiplatformsoptional feature, which is priced separately. This SAP Central Services high availability policy is nowadapted to SAP Netweaver technology.
The user can start and stop the SAP Netweaver stack by using the SAP user interface withoutinterfering with the System Automation policy. The SAP Software Update Manager is able to updatethe Netweaver solution without the need to disable System Automation during the update process.
Supported SAP configuration options: Java, ABAP, and DUAL stack support for SAP Central Servicesfailover. Additionally, the following configuration options are supported:
© Copyright IBM Corp. 2006, 2020 xiii
• Application server (restart in place of primary and additional application server)• SAP router failover• SAP Web Dispatcher failover• Start after dependency support to database
System Automation for Multiplatforms version 4.1.0.2 adds support for:
• SAP HANA System Replication failover
The supported SAP kernel version is 7.20 or higher.
For more information, see System Automation for Multiplatforms High Availability Policies Guide.
Gathering information about application failures
The samwhy program is a simple and easy-to-use tool that offers the detection of application failuresand their analysis for applications that are controlled by System Automation. samwhy helps theoperator to understand what happened and provides an explanation why System Automation reactedthe way it did.
For more information, see System Automation for Multiplatforms Reference Guide.
High availability of the end-to-end automation adapter is simplified
An extra automation policy or virtual IP address is not required any more.
For more information, see System Automation for Multiplatforms Installation and ConfigurationGuide.
Run the end-to-end automation adapter with a non-root user
By default, the end-to-end automation adapter runs with a root user. Now the adapter can also be setup to run with a non-root user.
For more information, see System Automation for Multiplatforms Installation and ConfigurationGuide.
xiv Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Chapter 1. Troubleshooting and supportTroubleshooting and support information for System Automation for Multiplatforms helps youunderstand, isolate, and resolve problems.
Troubleshooting and support information contains instructions for using the problem-determinationresources that are provided with your IBM® products. To resolve a problem on your own, you can find outhow to identify the source of a problem, how to gather diagnostic information, where to get fixes, andwhich knowledge bases to search. If you need to contact IBM Support, you can find out what diagnosticinformation the service technicians need to help you address a problem.
TroubleshootingThis section covers the following topics:
• “How automation works” on page 1
This topic summarizes important concepts of System Automation.• “How to obtain troubleshooting information” on page 3
Use this topic to learn how you can gather information about automated resources and resource groups.• “Error analysis” on page 12
Use the error scenarios described in this topic to learn how to understand, isolate, and resolve errorsthat are reported by System Automation. The following errors are discussed:
– “A resource has an OpState of Failed Offline” on page 12– “A resource group has an OpState of Failed Offline” on page 13– “A resource has an OpState of Stuck Online” on page 14– “Timeout messages are found in the system log” on page 14
• “Problem analysis” on page 16
Use the problem scenarios described in this topic to effectively troubleshoot problems related toSystem Automation that are typically not indicated by error messages. The following problems arediscussed:
– “A resource does not start” on page 16– “A resource group does not start” on page 17– “A resource does not stop” on page 17– “A resource group does not stop” on page 18– “A start/stop request against a resource does not cause StartCommand or StopCommand to run” on
page 18– “No failover occurs after a node is excluded ” on page 19– “No failover occurs after a node crash or reboot ” on page 20– “No reset occurs after a start control operation timeout” on page 21– “Other problems” on page 21
How automation worksThis topic summarizes important concepts of System Automation. For detailed information, refer toSystem Automation for Multiplatforms Administrator's and User's Guide.
Automation manager
The automation manager consists of the binder and the logic deck.
© Copyright IBM Corp. 2006, 2020 1
BinderThe binder is responsible to find a placement for the members of a resource group when the group isstarted, or when the resources must be started on a different node because the node on which they werepreviously running is crashed or is rebooted. The corresponding task is the so-called binding step, and theresult of the task is reflected in the BindingState of a resource.
The following BindingStates for a resource exist:Unbound
The resource is not bound and therefore Offline. System Automation for Multiplatforms did not yettry to find a placement for the resource.
BoundThe resource is bound to a node, and the resource is either running on that node or SystemAutomation for Multiplatforms starts the resource on the node after all dependencies on otherresources are fulfilled.
SacrificedSystem Automation for Multiplatforms cannot find a placement for the resource. There is no node onwhich this resource might be started, which is why the resource is not started by System Automationfor Multiplatforms.
SacrificialThe resource is online and bound, but needs to be stopped and unbound caused by an unboundresource with a higher priority.
If the placement of more than one resource group results in a conflict, the priority value controls whichgroup loses the conflict, which means that it is not placed and its binding state is set to Sacrificed.Check out the following example:
In a two-node cluster, resource group RG1 contains resource R1, and resource group RG2 containsresource R2. Resource R1 depends on resource R2. Both are started. Then, R1 fails. The resultingbehavior depends on the priority of the resource groups:
• If RG1 and RG2 have the same priority, R1 is not restarted.• If RG1 has at least a priority of 21 (and RG2 has a priority of 0), R2 is stopped and R2 and R1 are started
on a different node.
Logic deck
The logic deck is responsible for sending out the start and stop orders for the individual resources to bringthem Online or Offline. When sending out the orders, the logic deck ensures that all start and stopdependencies defined in the automation policy are fulfilled.
Important internal resource statesSystem Automation for Multiplatforms maintains information about many internal states for eachresource.
The most important internal states are:DesiredState
The state that System Automation anticipates for a resource is called DesiredState; it is the state theresource should be in when requests and votes from other resources are taken into account. TheDesiredState is either Online or Offline.
The DesiredState of a resource is not necessarily identical to the value of the NominalState attributeof the resource group that contains the resource, because requests and votes that are submittedagainst a resource have a higher priority than the NominalState. For detailed information aboutrequest priorities, refer to System Automation for Multiplatforms Administrator's and User's Guide.
ObservedStateThe ObservedState is the actual state of the resource. It is monitored by the resource's resourcemanager, for example, with the MonitorCommand for a resource of class IBM.Application, and anystate change is reported to the automation manager.
2 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
The goal of System Automation is to ensure that all resources ObservedState values match theirDesiredState.
Some commands display the state as a text, other commands and audit logs display a correspondinginteger value. The mapping is as follows:
• 0 – Unknown• 1 – Online• 2 – Offline• 3 - Failed Offline• 4 – Stuck Online• 5 – Pending Online• 6 – Pending Offline• 8 – Ineligible
How to obtain troubleshooting information
Collecting debug and trace data
At any time of operation, the subsystems of System Automation for Multiplatforms and RSCT write debugand trace data to trace files on the local disk. The trace files are created as ring buffers to limit the amountof space taken up by the files. When the available space is exceeded, the trace files are overwritten.Depending on the number of resources and the activity on the nodes, large amounts of data may belogged to theses files and they may be overwritten at any time.
To ensure that no debug and trace data is lost and to increase the probability that all required diagnosticinformation is available should you need to contact IBM support, it is recommended that you collect alltrace data before starting your troubleshooting activities, which may generate trace output.
Use the getsadata script provided with System Automation for Multiplatforms to gather all relevanttrace and debug data.
The getsadata script is found under
/usr/sbin/rsct/install/bin/getsadata
The following parameters are supported:
• all Maximum data collection, including all collection options listed below.• ctsnap: Default behavior for getsadata. Runs the ctsnap tool and collects its output.• logs: Collects logs and other general information.• traces: Formats and collects all IBM.RecoveryRM and IBM.GlbResRM traces.• spooldays: Same as traces but limits collection to specified number of days <# of days>.• spoolmbytes: Same as traces but limits collection to max megabytes per daemon <# of MB> .• skipspool: Same as traces but will prevent running rpttr against lots of spooled trace files.• cores: Collects any IBM.RecoveryRM and IBM.GblResRM core files that may exist.• env: Collects system environment information that is not related to System Automation for
Multiplatforms or RSCT.• rsct Collects the RSCT environment details.• sam Collects the System Automation for Multiplatforms policy details, depending if IBM.RecoveryRMd
is running.• scripts: Collects all policy scripts and sampolicy output.• install: Collects all installSAM and prereqSAM logs from the /tmp directory.• db2: Collects db2 related details if possible.
Chapter 1. Troubleshooting and support 3
• outdir <path>: Specify location to be used for data collection. The default is /tmp.• timer <seconds>: Specify default time limit to wait for individual commands to run.• verbose: Verbose mode. Echo to stdout the commands that run.• noprompt: This would allow this script to be run without any user prompting.• nojava: Prevent the running of commands dependent on Java™.• ftphelp: Displays FTP instructions and exits.
The command generates a compressed file in the /tmp directory.
Note: : Make sure that the script getsadata always runs on the node that runs the RecoveryRM masterdaemon first, to avoid overwriting essential trace information. The script prompts for confirmation in caseit is not running on the node running the RecoveryRM master.
To find out on which node the RecoveryRM master daemon is running, issue the following command:
lssrc –ls IBM.RecoveryRM | grep Master
Gathering information about application failuresThe samwhy command is a simple and easy-to-use tool that detects and analyses application failures ofapplications that are controlled by System Automation.
For more information, refer to System Automation for Multiplatforms Administrator's and User's Guide.
Using the system log as information source
The messages that are generated by all subsystems of System Automation and by RSCT are the firstsource of information in troubleshooting and problem determination:
• Linux: Messages are written to the system log (/var/log/messages).• AIX: The system logger is not configured by default. Messages are written to the error log.
To be able to obtain the debug data, it is recommended that you configure the system logger in thefile /etc/syslog.conf. When you have made the necessary changes, you must recycle the syslogdusing the command refresh –s syslogd. The location of the log file is defined in /etc/syslog.conf.
Messages are logged to the system log for the following events:
• Start of a subsystem, for example:
Mar 10 13:04:15 node1 RecoveryRM[5482]: (Recorded using libct_ffdc.a cv 2):::Error ID: 824....zgK22/WNI/8cU0B....................:::Reference ID: :::Template ID: 0:::Details File: :::Location: RSCT,IBM.RecoveryRMd.C,1.21.1.2,135 :::RECOVERYRM_INFO_0_ST IBM.RecoveryRM daemon has started.
• Stop of a subsystem, for example:
Mar 10 13:04:28 node1 RecoveryRM[5482]: (Recorded using libct_ffdc.a cv 2):::Error ID: 822....AhK22/osT18cU0B....................:::Reference ID: :::Template ID: 0:::Details File: :::Location: RSCT,RecoveryRMDaemon.C,1.14,177 :::RECOVERYRM_2621_402_ER IBM.RecoveryRM daemon stopped by SRC command or exiting due to an error condition . Error id 0
• Error of a subsystem, for example:
Mar 10 13:04:14 node1 srcmstr: src_error=-9035, errno=0,module='srchevn.c'@line:'251', 0513-035 The IBM.RecoveryRM Subsystem endedabnormally. SRC will try and restart it.
• Messages related to the Quorum state of the subcluster, for example:
Mar 9 16:13:07 node1 ConfigRM[31411]: (Recorded using libct_ffdc.a cv2):::Error ID: :::Reference ID: :::Template ID: 0:::DetailsFile: :::Location:
4 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
RSCT,PeerDomain.C,1.99.11.1,15510 :::CONFIGRM_HASQUORUM_ST The operational quorum state of the active peer domain has changed to HAS_QUORUM. In this state, cluster resources may be recovered and controlled as needed by management applications.
• Start and stop of an IBM.ServiceIP resource, for example:
Mar 8 09:41:08 node1 GblResRM[1886]: (Recorded using libct_ffdc.a cv 2):::Error ID: :::Reference ID: :::Template ID: 0:::Details File: :::Location: RSCT,ServiceIP.C,1.2.5,1360 :::GBLRESRM_IPONLINE IBM.ServiceIP assigned address on device. IBM.ServiceIP 10.67.78.89 eth1:1
Mar 8 09:42:44 node1 GblResRM[1886]: (Recorded using libct_ffdc.a cv 2):::Error ID: :::Reference ID: :::Template ID: 0:::Details File: :::Location: RSCT,ServiceIP.C,1.2.5,1434 :::GBLRESRM_IPOFFLINE IBM.ServiceIP removed address. IBM.ServiceIP 10.67.78.89
• A StartCommand, StopCommand, or MonitorCommand for a resource of class IBM.Application runsinto a timeout, for example:
Mar 13 10:25:55 node1 GblResRM[24275]: (Recorded using libct_ffdc.a cv 2):::Error ID: :::Reference ID: :::Template ID: 0:::Details File: :::Location: RSCT,Application.C,1.2.1,2434 :::GBLRESRM_MONITOR_TIMEOUT IBM.Application monitor command timed out. Resource name resource1
Tip: In addition to the data that is logged by default, it is recommended that you log the execution of theStartCommand and StopCommand of IBM.Application resources to a specific location.
The scripts that are provided with the pre-canned policies for System Automation log all executions of theStartCommand and StopCommand for a resource to the system log by default. The following sampleoutput shows the data that is written to the system log when a resource is started out of theStartCommand of the pre-canned policy for the NFS server:
Mar 13 10:34:31 node1 /usr/sbin/rsct/sapolicies/nfsserver/nfsserverctrl-server:[27230]: NFS server started
Using audit logs as information source
IBM.RecoveryRM master daemon audit logThe IBM.RecoveryRM master daemon maintains an audit log in which it records all requests, errorresponses to the requests, important information about the current policy, and about binding issues,as well as OpState changes of resources. To view the audit log of the current RecoveryRM master ofthe last day, enter the following samlog command on any node of the domain:
samlog –n <master node name> –s R –r
To view the merged IBM.RecoveryRM audit logs of all nodes in the domain, enter:
samlog –s R
For more information about the samlog command, refer to System Automation for MultiplatformsReference Guide.
Example:
The following example shows the four records that appear in the audit log for the following fourevents:
• An operator issues a start request against resource group "A".• This effects a start request against its member resource "RA".• A stop request is issued against resource group "A".• This effects a stop request against its member resource "RA".• OpState change of resource „RA“.
12:16:20.168613 T(1096711088) _RCD Online request injected: A/ResGroup/IBM.ResourceGroup12:16:20.181285 T(1096711088) _RCD Online Request against RA on node saxb02
Chapter 1. Troubleshooting and support 5
12:16:35.722675 T(1096711088) _RCD Offline request injected: A/ResGroup/IBM.ResourceGroup12:16:35.727970 T(1096711088) _RCD Offline Request against RA on node saxb0212:16:37.264652 T(1096711088) _RCD ReportState: Resource : RA/Fixed/IBM.Application/saxb02 reported state change: 2
GblResRM daemon audit logOn every node, the GblResRM daemon maintains an audit log in which it records any execution of astart command, stop command, or reset operation for a resource, every start or stop of a ServiceIPresource, and every OpState change of a resource. To view such an audit log of a specific node of thelast day, enter the following samlog command on any node of the domain:
samlog –n <node name> –s G –r
For more information about the samlog command, refer to System Automation for MultiplatformsReference Guide.
Example:
The following example shows the records that appear in the audit log when a resource appfloataand an IBM.ServiceIP resource ip are stopped.
12:51:08.864796 T(4152898784) _GBD Taking application resource offline: Name=appfloata Handle=0x6028 0xffff 0xff2f99d1 0x13fbb275 0x1046ca5c 0x98691b60 12:51:10.877355 T(4152603872) _GBD Stop command for application resource "appfloata" (handle 0x6028 0xffff 0xff2f99d1 0x13fbb275 0x1046ca5c 0x98691b60) succeeded with exit code 0 12:51:12.888128 T(4150719712) _GBD Monitor detect OpState change for resource Name=appfloata OldOpState=6 NewOpState=2 Handle=0x6028 0xffff 0xff2f99d1 0x13fbb275 0x1046ca5c 0x98691b60 12:51:12.961970 T(4152898784) _GBD Resource "ip" (handle 0x6029 0xffff 0xff2f99d1 0x13fbb275 0x1046ca62 0x544260f8): IP address 10.47.77.97 has been successfully taken offline on network interface "eth0:0" 12:51:12.962272 T(4152898784) _GBD Monitor reports: No network device flagged UP with IP address 10.47.77.97. Taking resource "ip" (handle 0x6029 0xffff 0xff2f99d1 0x13fbb275 0x1046ca62 0x544260f8) offline.
Pulling a stack dump from a live resource manager
You can create a stack dump from a live resource manager on Linux on System x or System z, and AIX 5.3or higher. To obtain a stack dump of a currently running IBM.RecoveryRM or IBM.GblResRM, proceedas follows:
1. Get the PID. Enter
ps –ef | grep RMd
or
lssrc –l –s <resource manager>
2. Send the SIGUSR1 signal to the resource manager process, enter
kill –SIGUSR1 <pid>
3. The resource manager creates a stack dump file for each thread named stackdump_<resourcemanager>_tid_-<thread ID>.xml and locates the file in its default run directory /var/ct/<domain>/run/mc/<resource manager>. The stack dump files are XML files containinginformation about the execution state of the resource manager. This file is used by for IBM support.
Using the command history
The file /var/ct/IBM.RecoveryRM.log is used to record the IBM Tivoli® System Automationcommand history. It contains entries for all System Automation commands that have been executedlocally on the node.
6 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Example:
User root invoked "chrg -o Online samadapter-rg on Thu Mar 1 16:51:53 CET 2007User root invoked "chrg -o Offline samadapter-rg on Thu Mar 1 17:00:14 CET 2007User root invoked "chrg -o Online samadapter-rg on Thu Mar 1 17:00:20 CET 2007
Using commands to gather information
Use the commands described in this section to obtain detailed information about resources and resourcegroups if the information provided in the system log was not sufficient to resolve the problem. For bestresults, you should invoke the commands in the sequence in which they are listed. For detailedinformation about the commands, see System Automation for Multiplatforms Reference Guide.
The following commands can be used to gather information about resources and resource groups:lssam -V
The command lssam displays summary information about the operational states of the managedresources on a per node basis. It provides additional information about excluded or offline nodes andrequests that were issued against resources or resource groups.
The option -V displays:
• Relationships and resource details. For example the IPAddress of IBM.ServiceIP resource, orthe mount point of IBM.AgFileSytem resource.
• More verbose resource states, such as BindingState and ControlState of a resource orresource group in case a problem or non-default value is set.
• Error messages for a non-functional sub-system of System Automation, and in situations where theuser has insufficient permissions to run the command.
Example:
In this example, the command lssam was used to find out why the resource 'app1' is offline althoughthe nominal state of the resource group 'rg1', of which it is a member, is Online.
node1:~ # lssamOnline IBM.ResourceGroup:rg1 Nominal=Online |- Online IBM.ServiceIP:ip1 |- Online IBM.ServiceIP:ip1:node1 '- Offline IBM.ServiceIP:ip1:node2 Node=Excluded '- Offline IBM.Application:app1 Request=Offline |- Offline IBM.Application:app1:node1 '- Offline IBM.Application:app1:node2 Node=ExcludedOffline IBM.ResourceGroup:rg2 Nominal=Offline '- Offline IBM.Application:app2 '- Offline IBM.Application:app2:node2 Node=Excluded
The output shows why 'app1' is offline although the nominal state of resource group 'rg1' is Online(Nominal=Online):
• Node 'node2' is in the list of excluded nodes (Node=Excluded), which is why all resources on thenode, including 'app1', are offline.
• An Offline request has been issued against 'app1' (Request=Offline), which explains why it is alsooffline on node 'node1'.
Note: The most important information is highlighted in color in the output.
Using the option -V shows also more detailed information including the relationships between theresource, for example:
node1:~ # lssam -VOnline IBM.ResourceGroup:rg1 Nominal=Online |- Online IBM.AgFileSystem:fs1 MNT=/fs1 -. <. |- Online IBM.AgFileSystem:fs1:node1 | | '- Offline IBM.AgFileSystem:fs1:node2 SO SA '- Online IBM.Application:app1 <. -. -. <' -' |- Online IBM.Application:app1:node1 | | | '- Offline IBM.Application:app1:node2 | | |Online IBM.ResourceGroup:rg2 Nominal=Online | | |
Chapter 1. Troubleshooting and support 7
|- Online IBM.ResourceGroup:rg3 Nominal=Offline | | | |- Online IBM.Application:app3 | | | <. -. |- Offline IBM.Application:app3:node1 | | | | | '- Online IBM.Application:app3:node2 | | | | DO '- Online IBM.Application:fs3 | | | | <' |- Offline IBM.Application:fs3:node1 | | | | '- Online IBM.Application:fs3:node2 | | | | '- Online IBM.ResourceGroup:rg4 Nominal=Offline | | | | |- Online IBM.ResourceGroup:rg5 Nominal=Offline | | | | |- Online IBM.AgFileSystem:fs5 MNT=/fs5 | | | | <. -. |- Offline IBM.AgFileSystem:fs5:node1 | | | | | | '- Online IBM.AgFileSystem:fs5:node2 AA AA SA | SA SO '- Online IBM.Application:app5 -' <' <' | -. -' <' |- Offline IBM.Application:app5:node1 | | '- Online IBM.Application:app5:node2 | | '- Online IBM.ResourceGroup:rg6 Nominal=Offline DO SA |- Online IBM.Application:app6 -. -' <' |- Offline IBM.Application:app6:node1 | '- Online IBM.Application:app6:node2 SA '- Online IBM.ServiceIP:ip1 IP=10.1.1.23 <' -. |- Offline IBM.ServiceIP:ip1:node1 | '- Online IBM.ServiceIP:ip1:node2 DOOnline IBM.Equivalency:niequ <' |- Online IBM.NetworkInterface:eth0:node1 '- Online IBM.NetworkInterface:eth0:node2
lsrg –Ab –V –g <resource-group-name>
The command lsrg –Ab shows all information about the resource groups that are defined in theautomation policy. Add the -V option to also display the most important automation details, includingthe DesiredState, ObservedState and BindingState. When analyzing the output, make sure to check ifthe value of the ConfigValidity attribute indicates a configuration problem. For more information aboutthe ConfigValidity attribute, refer to System Automation for Multiplatforms Administrator's and User'sGuide.
This example shows the information that is displayed for a resource group that is Offline:
node1:~ # lsrg -Ab -V -g rg1Starting to list resource group information.
Displaying Resource Group information:All AttributesFor Resource Group "rg1".
Resource Group 1: Name = rg1 MemberLocation = Collocated Priority = 0 AllowedNode = ALL NominalState = Offline ExcludedList = {} Subscription = {} Owner = Description = Instruction = ActivePeerDomain = domain1 OpState = Offline TopGroup = rg1 MoveStatus = [None] ConfigValidity = AutomationDetails[CompoundState] = Satisfactory [DesiredState] = Offline [ObservedState] = Offline [BindingState] = Unbound [AutomationState] = Internal [StartableState] = Yes [HealthState] = Not Applicable
This example shows the information that is displayed for a resource group that is Online:
node1:~ # lsrg -Ab -V -g rg1Starting to list resource group information.
Displaying Resource Group information:All AttributesFor Resource Group "rg1".
8 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Resource Group 1: Name = rg1 MemberLocation = Collocated Priority = 0 AllowedNode = ALL NominalState = Online ExcludedList = {} Subscription = {} Owner = Description = Instruction = ActivePeerDomain = domain1 OpState = Online TopGroup = rg1 MoveStatus = [None] ConfigValidity = AutomationDetails[CompoundState] = Satisfactory [DesiredState] = Online [ObservedState] = Online [BindingState] = Bound [AutomationState] = Internal [StartableState] = Yes [HealthState] = Not Applicable
lsrg –m
The command displays the operational state of all managed resources and shows mandatory versusnon-mandatory resource members.
Example:
node1:~ # lsrg –m
Displaying Member Resource information:Class:Resource:Node[ManagedResource] Mandatory MemberOf OpState WinSource LocationIBM.ServiceIP:ip1 True rg1 Online Nominal node1IBM.Application:app1 True rg1 Online Nominal node1IBM.Application:app2 True rg2 Offline
lssamctrl
The command lssamctrl displays the global automation parameters. For example whether theautomation is currently enabled, the list of excluded nodes, and the RetryCount. The RetryCountspecifies the maximum number of retries for the StartCommand when the resource does not start atthe first attempt.
Example:
node1:~ # lssamctrlDisplaying SAM Control information:
SAMControl:TimeOut = 60RetryCount = 3Automation = AutoExcludedNodes = {}ResourceRestartTimeOut = 5ActiveVersion = [4.1.0.0,Thu Apr 24 11:10:58 METDST 2014]EnablePublisher = DisabledTraceLevel = 31ActivePolicy = []
The command lsrgreq –L lists all requests that were issued against resource groups. Suchrequests are either issued directly from the command line using the command rgreq, or implicitly bythe System Automation Application Manager end-to-en automation manager. In the latter case, theSource of the request is ‘Automation’.
Example:
node1:~ # lsrgreq –L
Displaying Resource Group request information:All request information
Chapter 1. Troubleshooting and support 9
ResourceGroup Priority Action Source NodeList Active UserID MoveStatusrg1 low Start Operator {} Active None
If the command is executed with the -m option, all requests against resource group members aredisplayed.
Example:
node1:~ # lsrgreq -L –m
Displaying Member Resource request information:All request information
Member Resource 1: Class:Resource:Node[ManagedResource] = IBM.Application:app1 Priority = low Action = Start Source = Operator ActiveStatus = Active UserID =
The command lsequ –Ab is used to display all resources of type "equivalency" that are defined inthe automation policy. Typically, equivalencies are used to define the network interfaces that can beused by resources of type IBM.ServiceIP.
When analyzing the output of the command, make sure to check if the value of the ConfigValidityattribute indicates a configuration problem (for more information about the ConfigValidity attribute,refer to System Automation for Multiplatforms Administrator's and User's Guide).
Example:
node1:~ # lsequ –AbDisplaying Equivalency information:All Attributes
Equivalency 1: Name = eq1 MemberClass = IBM.NetworkInterface Resource:Node[Membership] = {eth0:node1,eth0:node2} SelectString = "" SelectFromPolicy = ANY MinimumNecessary = 1 Subscription[Consumer,…] = {[EEZ,All,None]} ActivePeerDomain = domain1 Resource:Node[ValidSelectResources] = {eth0:node1,eth0:node2} Resource:Node[InvalidResources] = {} ConfigValidity = AutomationDetails[CompoundState] = Undefined
The attribute Resource:Node[ValidSelectResources] must contain resources, especially if a dynamicSelectString is used. Subsequently, the OpState of the valid resources must be checked:
# lsrsrc IBM.<MemberClass-attribute-value> Name NodeNameList OpState
lsrgreq -L {-m}lsrel –Ab
The command lsrel –Ab is used to display all relationships that are defined in the automationpolicy.
Example:
node1:~ # lsrel –AbDisplaying Managed Relationship Information:All Attributes
Managed Relationship 1: Class:Resource:Node[Source] = IBM.Application:app1 Class:Resource:Node[Target] = {IBM.Application:app2} Relationship = StartAfter Conditional = NoCondition Name = app1_StartAfter_app2
10 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
ActivePeerDomain = domain1 ConfigValidity =
When analyzing the output, check the relationships for completeness (for example, both the Sourceand the Target of a relationship must be defined), and check if the value of the ConfigValidityattribute indicates a configuration problem (for more information about the ConfigValidity attribute,refer to System Automation for Multiplatforms Administrator's and User's Guide).
This command lists the public attribute of the CHARMControl class, which represents the automationengine itself. The command currently only returns the value of the Automating attribute, which isusually 1. In rare cases, the configuration of resource groups and relationships may becomedamaged, preventing automation from working properly. When this happens, the value of theAutomating attribute changes to 0, indicating that automation has been stopped.
Stopping automation instead of recycling the RecoveryRM (as was the case in System Automation forMultiplatforms releases prior to 2.3) allows you to collect diagnostic information and to even fix theconfiguration. A relationship with a non-existing target, for example, is considered a damagedconfiguration. Once such relationship is corrected or deleted, automation can be resumed by stoppingand restarting the current master RecoveryRM with the commands stopsrc and startsrc.
lsrsrc -A d -c IBM.CHARMControl
The command samdiag is used to display detailed state information for an individual resource. Thecommand can also be used to externalize all internal variables of a resource from the automationmanager. The command is very helpful in problem analysis, but it is not intended for daily usebecause it generates a large amount of information.
Example:
node1:~ # samdiag -g rg1
Displaying information for the following: Resource Group "rg1":
Diagnosis::Resource: rg1/ResGroup/IBM.ResourceGroup type: CHARM Resource Group Status - Observed: Online - Available Desired: Online - Requested Online (Nominal: Online - Nominal State: Online) Automation: Idle - CharmBase trigger linked Startable: Yes - Resource is startable Binding: Bound - Bound Compound: Satisfactory - Satisfactory
Resource Based Quorum: Not Supported - CharmBase trigger linked Members and Memberships: +---HasMember ---> app1/Fixed/IBM.Application/node1 +---HasMember ---> ip1/Fixed/IBM.ServiceIP/node1 +---bind/HasMember ---> app1/Float/IBM.Application +---bind/HasMember ---> ip1/Float/IBM.ServiceIP Group Constraint: Collocated Binding Constraints: Flags: None Orders: Outstanding Order: None - Resource is Available Dependencies: Start: Satisfied +---InCluster ---> Cluster Stop: Satisfied Binding exceptions: None Static Relationships: +---InCluster ---> Cluster Dynamic Relationships: +---bind/HasMember ---> app1/Float/IBM.Application +---bind/HasMember ---> ip1/Float/IBM.ServiceIP"
samdiag IBM.<resource-class-name>:<resource-name>:<node-name>
To query the details for a specific resource, the command has to be executed as follows:
Chapter 1. Troubleshooting and support 11
For example, for the resource ‘app1’ on node ‘node1’:
node1:~ # samdiag IBM.Application:app1:node1Displaying information for the following: Resource "IBM.Application:app1:node1":
Diagnosis::Resource: app1/Fixed/IBM.Application/node1 type: Fixed Resource Status - Reported: Online - Online Observed: Online - Online Desired: Online - Requested Online (Nominal: Offline - Defaulted: offline) Automation: Idle - Idle - Online completed Startable: Yes - Resource is startable Binding: Bound - Bound Compound: Satisfactory - Satisfactory
Resource Based Quorum: Not Supported - CharmBase trigger linked Groups and Aggregates: <---HasMember ---- rg1/ResGroup/IBM.ResourceGroup <---bind/HasMember ---- rg1/ResGroup/IBM.ResourceGroup Binding Constraints: Flags: None Orders: Outstanding Order: None - Idle - Online completed Dependencies: Start: Satisfied +---RunsOn ---> node1/Node/IBM.PeerNode Stop: Satisfied <---HasMember ---- rg1/ResGroup/IBM.ResourceGroup Static Relationships: +---RunsOn ---> node1/Node/IBM.PeerNode Dynamic Relationships: <---bind/HasMember ---- rg1/ResGroup/IBM.ResourceGroup"
samdiagFor deep analysis.
Error analysisUse the error scenarios described in this topic to learn how to effectively troubleshoot errors that arereported by System Automation for Multiplatforms.
A resource has an OpState of Failed Offline
This error has three possible causes:The cluster node is not Online
If a cluster node is not Online, all resources that are defined on the node have an OpState of FailedOffline. In such a case, the problem is not resource- but node-related.
The MonitorCommand of the resource returns with return code 3 (= Failed Offline)To find out if this is the case, you execute the MonitorCommand manually and check the return codeof the command. Perform these steps:
1. Get the value of the MonitorCommand attribute for the resource:
# lsrsrc –s ‘Name=”<resource_name>” ‘ IBM.Application Name MonitorCommand
2. Execute the MonitorCommand3. Get the return code of the MonitorCommand:
# echo $?
If the return code is 3 (Failed Offline), investigate why the MonitorCommand itself returns this valueand resolve the problem. After the problem has been resolved, the resource should have an OpStateof Offline.
12 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
System Automation has set the resource to ‘Failed Offline’ because previous attempts to start theresource failed
If the MonitorCommand returns 2 (Offline) but the resource has an OpState of ‘Failed Offline’, thisindicates either that the execution of the StartCommand for this resource returned with an error (not0 or timeout) or that System Automation could not start the resource within the number of attemptsdefined in the RetryCount attribute (see the description of the lssamctrl command above).
To investigate the problem, do this:
1. Check the system log for messages indicating a timeout for the StartCommand for this resource.2. If there is no such message, check the appropriate log files for the application that is behind the
resource. Identify and correct all problems.3. Check the audit trail.
The following audit trail entries indicate problems in the start script:
12:16:35.727970 T(1096711088) _RCD RMC Rejected online request against RA on node saxb0212:16:35.727970 T(1096711088) _RCD Failed Offline Request against RA on node saxb02
The following entries indicate that the start command repeatedly ran into a timeout:
12:16:35.727970 T(1096711088) _RCD Maximum timer cancelled for RA on node saxb0212:16:35.727970 T(1096711088) _RCD Failed Offline Request against RA on node saxb02
4. Finally, use the following command to reset the resource from the ‘Failed Offline’ state:
# resetrsrc –s ‘Name=”<resource_name>” && NodeNameList={“node_name”}’ IBM.Application
Now the resource should have an OpState of Offline and System Automation for Multiplatformsstarts the resource again if the desired state of the resource is Online.
A resource group has an OpState of Failed Offline
If the resources of a resource group do not start and the resource group has an OpState of ‘Failed Offline’this indicates that the binder was unable to find a placement for the resources and furthermore theresource group’s BindingState is Sacrificed. Check this using lssam -V or the following command:
# lsrg –Ab –V –g <resource_group_name>
If the BindingState is Sacrificed, do this:
• Check the audit trail for entries like in the following example:
9:22:46.520729 T(229390) _RCD Online request injected: A/ResGroup/IBM.ResourceGroup 09:22:46.522817 T(229390) _RCD RIBME-Hist for <NULL>: BINDER: Bind A/ResGroup/IBM.ResourceGroup 09:22:46.532464 T(229390) _RCD RIBME-Hist for <NULL>: BINDER: Resource RA/Fixed/IBM.Test/saxb02 hsa no usable options 09:22:46.532467 T(229390) _RCD RIBME-Hist for <NULL>: BINDER: Resource RB/Fixed/IBM.Test/saxb03 hsa no usable options Resource RB/Fixed/IBM.Test/saxb02 hsa no usable options Resource RA/Fixed/IBM.Test/saxb03 hsa no usable option
The example shows a resource group that is collocated but has two fixed members on different nodespreventing the binder from placing the resources; this is expressed as 'having no usable option'.
• Use the lssam -V option to check that there are no resources with OpState ‘Failed Offline’ within thatgroup.
• Nodes are not excluded.• All relationships for starting the group are fulfilled.• All equivalencies in the automation policy all have Online members.
Chapter 1. Troubleshooting and support 13
A resource has an OpState of Stuck Online
There are two possible reasons, why a resource has an OpState of Stuck Online:
• In rare cases, the MonitorCommand of a resource returns with return code 4 (= Stuck Online). This canbe checked by executing the MonitorCommand manually and checking the command's return code:
1. Retrieve the value of the MonitorCommand attribute for this resource:
lsrsrc –s ‘Name=”<resource_name>” ‘ IBM.Application Name MonitorCommand
2. Execute the MonitorCommand.3. Retrieve the return code of the MonitorCommand:
echo $?
If the return code is 4 (Stuck Online), investigate why the MonitorCommand itself returns this value.After this problem has been resolved, the resource should have an OpState of Offline.
• The second and more likely reason for a resource to have an OpState of Stuck Online (if theMonitorCommand returns 1 (Online) or 6 (Pending Offline), but the resource has an OpState of ‘StuckOnline’) is that a the resource could not be stopped by System Automation for Multiplatformspreviously, and System Automation for Multiplatforms has finally set the resource to Stuck Online. Thisis the case if the execution of the StopCommand for this resource and a subsequent reset against thatresource failed to bring the resource offline.
This error cannot be recovered by System Automation for Multiplatforms and manual intervention isrequired. After investigating why the resource did not stop, an operator must stop the resource. Whenthe OpState of the resource is evaluated as Offline at the next execution of the MonitorCommand,System Automation for Multiplatforms will again take control of this resource, and no further manualsteps are required.
Timeout messages are found in the system log
StartCommand timed out
A message is logged in the system log if the StartCommand for a resource did not finish within the timeperiod defined in the StartCommandTimeout attribute for this resource. There are two possible causes forthis problem:
• The value defined in the StartCommandTimeout attribute is to low
To check the value of the attribute, perform these tasks:
1. Determine the actual setting of this attribute for this resource:
# lsrsrc –s ‘Name=”<resource_name>” ‘ IBM.Application Name \StartCommandTimeout
2. Determine how long it takes to execute the StartCommand for this resource
Important: This should never be done on a running production system, but only duringmaintenance, or on another test system!
Keep in mind that the time needed to execute the command may increase if the system is underload.
3. Compare the actual setting of the timeout value with the time needed to execute the command4. If necessary, adjust the StartCommandTimeout value:
# chrsrc -s 'Name=="<resource_name>"' \ IBM.Application StartCommandTimeout=<new_value_in_seconds>
This change can be done dynamically.• The StartCommand execution results in a hang situation, because one of the statements within the
executed script hangs.
14 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
– Investigation requires manual execution of the StartCommand
Important: This should never be done on a running production system, but only during maintenance!– If it turns out that the script is not finishing (hanging), additional debugging can be activated by
adding set –x as the second line of the StartCommand script.– Identify the statement that results in the hang and correct the problem. Note that this is out of the
scope of System Automation.
StopCommand timed out
A message is logged in the system log if the StopCommand for a resource did not finish within the timeperiod defined in the StopCommandTimeout attribute for this resource. There are two possible causes forthis problem:
• The value defined within the StopCommandTimeout attribute is to low
To check if this is the case, do this:
1. Determine the actual setting of this attribute for this resource:
# lsrsrc –s ‘Name=”<resource_name>” ‘ IBM.Application Name \StopCommandTimeout
2. Determine how long it takes to execute the StopCommand for this resource
Important: This should never be done on a running production system, but only duringmaintenance, or on another test system!
Keep in mind that the time needed to execute the command may increase if the system is underload.
3. Compare the actual setting of the timeout value with the time needed to execute the command.4. Adjust the SopCommandTimeout value if needed:
# chrsrc –c ‘Name=”<resource_name>” ‘ IBM.Application \StopCommandTimeout=<new_value_in_seconds>
This change can be done dynamically.• The StopCommand execution results in a hang situation, because one of the statements within the
executed script hangs.
– Investigation requires manual execution of the StopCommand
Important: This should never be done on a running production system, but only during maintenance!– If it turns out that the script is not finishing (hanging), then additional debugging can be activated by
adding set –x as the second line of the StopCommand script.– Identify the statement that results in the hang and correct the problem. Note that this is out of the
scope of System Automation.
MonitorCommand timed out
A message is logged in the system log if the MonitorCommand for a resource did not finish within the timeperiod defined in the MonitorCommand attribute for this resource. There are two possible causes for thisproblem:
• The value defined within the MonitorCommandTimeout attribute is to low
To check if this is the case, do this:
1. Determine the actual settings of the MonitorCommand attributes for this resource:
# lsrsrc –s ‘Name=”<resource_name>” ‘ IBM.Application Name \MonitorCommand MonitorCommandTimout MonitorCommandPeriod
Chapter 1. Troubleshooting and support 15
2. Determine how long it takes to execute the MonitorCommand for this resource by issuing theMonitorCommand directly on the command line.
Keep in mind that the time needed to execute the command may increase if the system is underload.
3. Compare the actual setting of the timeout value with the time needed to execute the command.4. Adjust the MonitorCommandTimeout value if needed:
# chrsrc –c ‘Name=”<resource_name>” ‘ IBM.Application \ MonitorCommandTimeout=<new_value_in_seconds>
This change can be done dynamically.• The MonitorCommand execution results in a hang situation, because one of the statements within that
script executed is hanging.
– Investigation requires manual execution of the MonitorCommand– If it turns out that the script is not finishing (hanging), then additional debugging can be activated by
adding set –x as the second line of the MonitorCommand script.– Determine the statement that results in the hang and correct the problem. Note that this is out of the
scope of System Automation
Problem analysisUse this section to learn how to analyze and resolve problems.
A resource does not start
If a resource does not start, perform the following steps:
1. Check for messages related to the execution of the StartCommand for that resource in the system log,the appropriate application log, and the process table (ps –ef). If the StartCommand has not beenexecuted at all, proceed with Step 2, otherwise investigate why the application does not come Online.
2. Check for Operational Quorum:
# lssrc –ls IBM.RecoveryRM | grep Quorum
If Operational Quorum == HAS_QUORUM, proceed with Step 3. If not, find out how many nodes areOnline, using:
# lsrpnode
Operational quorum requires that either more than half of the nodes in the cluster are online or exactlyhalf of the nodes are online and the tiebreaker has been reserved:
• If less than half of the nodes are online, start additional nodes.• If exactly half of the nodes are online, check the attribute of the active tiebreaker:
# lsrsrc –c IBM.PeerNode OpQuorumTieBreaker
If the value of this attribute is Operator, the tiebreaker must set manually:
a. Deny ownership of the tiebreaker to the node that should not get it (if the other node is stillonline):
# runact –c IBM.PeerDomain ResolveOpQuorumTie Ownership=0
b. Grant ownership of the tiebreaker to the node that should get it:
# runact –c IBM.PeerDomain ResolveOpQuorumTie Ownership=1
The best way to ensure that the problem does not reoccur is to define an automatic disk or networktiebreaker, which ensures that the tiebreaker is reserved automatically.
16 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Now, check the setting for the active tiebreaker:
# lsrsrc –s ‘Name=”<name-of-active-tiebreaker>”’ IBM.TieBreaker
Check that the disk is correctly allocated for a disk tiebreaker or that the IP address is available for anetwork tiebreaker. Note that these settings can only be changed if configuration quorum isestablished, which means that more than half of the nodes must be online.
3. Check for requests against the resource or the containing resource group:
# lssam -V# lsrgreq –L# lsrgreq –L –m
If a stop request was issued against the resource or resource group, this explains why the resourcestays offline. To resolve the problem, cancel the request.
4. Check that the cluster is in automation mode and not in manual mode, which would prevent SystemAutomation from starting resources, and that the node or nodes are not in the list of excluded nodes,because System Automation cannot start resources on excluded nodes. Use one of the followingcommands:
# lssam# lssamctrl
If the value of the Automation attribute is Manual, the cluster is in manual mode. The mode can be setto Auto using:
# samctrl –M F
If there are nodes in the list of excluded nodes, they can be deleted from the list using:
# samctrl –u d <node_name>
5. Check the DesiredState, ObservedState, and BindingState of the resource using this command for allnodes:
# samdiag IBM.<resource-class>:<resource-name>[:<node-name>]
If the BindingState for the resource is Sacrificed on all nodes, this indicates that the binder was notable to find a placement for this resource that satisfies all relationships to other resources. Typically,this problem occurs at the time when an automation policy is created or changed.
A resource group does not start
A resource group is comprised of a number of resources. If none of the resources of the group is starting,perform the following steps:
1. Identify which of the resources should start first by evaluating the relationships.2. Find out why this resource does not start by proceeding as described in section “A resource does not
start” on page 16. Make sure to check for requests against the resource group, and evaluate allrelationships in which the resource group is defined as source resource. To determine theBindingState of the resource group, use one of these commands:
# lssam -V# lsrg –Ab –V –g <resource-group-name># samdiag –g <resource-group-name>
A resource does not stop
If a resource does not stop, perform the following steps:
1. If a resource does not stop after the StopCommand was executed, System Automation forMultiplatforms will issue a reset operation against the resource, which triggers the execution of theStopCommand. If the resource still does not reach the OpState Offline, the OpState of the resource
Chapter 1. Troubleshooting and support 17
will finally be set to Stuck Online. To resolve the problem, proceed as described in “A resource has anOpState of Stuck Online” on page 14.
2. If the StopCommand for the resource has not been executed, check for requests against the resourceor the containing resource group, using one of these commands:
# lssam -V# lsrgreq –L # lsrgreq –L –m
If there is a start request against the resource or resource group, check if the request can be canceled.3. Check that the cluster is in automation mode, not in manual mode:
# lssamctrl
If the value for the attribute Automation is Manual, the cluster is in manual mode, and SystemAutomation will not stop any resources. This can be set to Auto using:
# lssam# samctrl –M F
4. Check if there are relationships from other resources that prevent this resource from stopping,especially, check for the following relationships:
• StartAfter (a StartAfter relationship keeps the dependent resource online)• DependsOn and DependsOnAny (both relationships implicitly include a StartAfter relationship, which
will keep the dependent resource online5. Check if there are StopAfter relationships to other resources which prevent this resource from
stopping (if the target resource needs to stay online, the source resource will also stay online).
A resource group does not stop
A resource group is comprised of a number of resources. If none of the resources of the group is stopping,perform the following steps:
1. Identify which of the resources should stop first by evaluating the relationships.2. Find out why this resource does not stop by proceeding as described in section “A resource does not
stop” on page 17. Make sure to check for requests against the resource group, and evaluate allrelationships in which the resource group is defined as target resource.
A start/stop request against a resource does not cause StartCommand or StopCommand to run
System Automation for Multiplatforms does not allow a StartCommand and StopCommand to be run forthe same resource at the same time:
• System Automation for Multiplatforms will block the execution of the next command until the previousis finished.
There are certain conditions that cause the product to apparently hang, although a request to stop or starta resource is actually being blocked by a still-running StartCommand or StopCommand. The following isan example of such a situation:
• The MonitorCommand for a resource monitors the OpState of this resource as Online, while theStartCommand of the resource is still running for a longer time.
• lssam and other commands will show the resource as Online. However, a stop request against theresource will not be successful until the StartCommand is finished or has run into the timeout.
• During that time, samdiag against the resource will show an 'Automation' state of 'Ordered - Onlinesent', and the 'Compound' state shows 'InAutomation - In Automation'. However, the resource OpStateshows already Online.
Here is the complete samdiag output for this situation:
samdiag IBM.Application:R1:node1Displaying information for the following:
18 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Resource "IBM.Application:R1:node1":
Diagnosis::Resource: R1/Fixed/IBM.Application/node1 type: Fixed Resource Status - Reported: Online - Online Observed: Online - Online Desired: Online - Requested Online (Nominal: Offline - Defaulted: offline) Automation: Ordered - Online sent Startable: Yes - Resource is startable Binding: Bound - Bound Compound: InAutomation - In Automation Move: None - Resource Move State is None
Resource Based Quorum: Not Supported - CharmBase trigger linked
Cleanup Flag: Groups and Aggregates: <---HasMember ---- R1/Float/IBM.Application <---Selects/1 ---- R1/Float/IBM.Application Binding Constraints: Flags: None Orders: Outstanding Order: Online - Online sent Progress: None - Online sent Reason: None - Online sent Dependencies: Start: Satisfied +---RunsOn ---> node1/Node/IBM.PeerNode Stop: Satisfied <---HasMember ---- R1/Float/IBM.Application Static Relationships: +---RunsOn ---> node1/Node/IBM.PeerNode Dynamic Relationships:"
After the command that is running has completed:
• The 'Automation' state will change to 'Idle'.• The 'Compound' state will change to 'Satisfactory'.• A stop request against the resource is now possible.
To prevent this situation from occurring, ensure the scripts for the StartCommand and StopCommand donot run into a timeout.
No failover occurs after a node is excluded
If no failover occurs after a node is excluded, perform the following steps:
1. Check that the cluster is in automation mode and not in manual mode, and that a node is available onwhich the resources can be started using:
# lssam
If the value for attribute Automation is Manual, the cluster is in manual mode, and System Automationwill not start any resources. This can be set to Auto using:
# samctrl –M F
Display the list of nodes that are online and compare it with the list of excluded nodes using:
# lsrpnode
If there are too many or all nodes in the list of excluded nodes, you can delete nodes from the listusing the following command:
# samctrl –u d <node_name>
2. Check if there are resources with OpState ‘Failed Offline’. If there are, proceed as described in section“A resource does not start” on page 16.
Chapter 1. Troubleshooting and support 19
3. Check if there are resources with OpState ‘Stuck Online’. If there are, proceed as described in “Aresource has an OpState of Stuck Online” on page 14.
4. Check the BindingState of the resource group to be started first:
• If the Binding State is 'Sacrificed', System Automation could not find a placement for the resources.
Check the equivalencies for valid member resources and check that the OpState of these resourcesis Online, using:
# lssam -V# lsequ –Ab
Check the attribute ValidSelectResources.• If the BindingState is 'Bound', System Automation could not start the resources. Proceed as
described in section “A resource does not start” on page 16.5. Check for relationships that cannot be fulfilled without the excluded node.
No failover occurs after a node crash or reboot
To analyze and resolve the problem, perform the following steps:
1. Check for operational quorum:
# lssrc –ls IBM.RecoveryRM | grep Quorum
If Operational Quorum == HAS_QUORUM, proceed with Step 2. If not, find out how many nodes areOnline, using:
# lsrpnode
Operational quorum requires that either more than half of the nodes in the cluster are online or exactlyhalf of the nodes are online and the tiebreaker has been reserved:
• If less than half of the nodes are online, start additional nodes.• If exactly half of the nodes are online, check the attribute of the active tiebreaker:
# lsrsrc –c IBM.PeerNode OpQuorumTieBreaker
If the value of this attribute is Operator, the tiebreaker must be set manually:
a. Deny ownership of the tiebreaker to the node that should not get it (if the other node is stillonline):
# runact –c IBM.PeerDomain ResolveOpQuorumTie Ownership=0
b. Grant ownership of the tiebreaker to the node that should get it:
# runact –c IBM.PeerDomain ResolveOpQuorumTie Ownership=1
The best way to ensure that the problem does not reoccur is to define an automatic disk or networktiebreaker, which ensures that the tiebreaker is reserved automatically.
Now, check the setting for the active tiebreaker:
# lsrsrc –s ‘Name=”<name-of-active-tiebreaker>”’ IBM.TieBreaker
Check that the disk is correctly allocated for a disk tiebreaker or that the IP address is available for anetwork tiebreaker. Note that these settings can only be changed if configuration quorum isestablished, which means that more than half of the nodes must be online.
2. Check that the cluster is in automation mode and not in manual mode, which would prevent SystemAutomation from starting resources, and check that the node or nodes are not in the list of excludednodes, because System Automation cannot start resources on excluded nodes. Use one of thefollowing commands:
20 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
# lssam -V # lssamctrl
If the value of the Automation attribute is Manual, the cluster is in manual mode. The mode can be setto Auto using:
# samctrl –M F
If there are nodes in the list of excluded nodes, you can delete nodes from the list using the followingcommand:
# samctrl –u d <node_name>
3. Depending on whether the entire resource group or only one of its members does not start, proceed asdescribed in the appropriate section above.
No reset occurs after a start control operation timeout
The operation timer is started when IBM Tivoli System Automation first sends a resource start controloperation to a resource. If the resource does not reach the desired state (online) within the timeoutperiod and IBM Tivoli System Automation fails to issue a reset operation against the resource, performthe following steps:
1. Stop the cluster using the stoprpdomain command.2. Restart the cluster using the startrpdomain command.
Other problems
If the problem is most likely related to the automation manager, you should try recycling the automationmanager (IBM.RecoveryRM) before contacting IBM support. This can be done using the followingcommands:
1. Find out on which node the RecoveryRM master daemon is running using the following command:
lssrc –ls IBM.RecoveryRM | grep Master
2. On the node running the master, retrieve the PID and kill the automation manager:
lssrc –ls IBM.RecoveryRM | grep PIDkill -9 <PID>
As a result, an automation manager on another node in the domain will take over the master role, andproceeds with making automation decisions. The src subsystem will restart the killed automationmanager immediately.
Cluster cannot be set upSee System Automation for Multiplatforms Administrator's and User's Guide for information on how toavoid problems with setting up a cluster. A typical obstacle, for example, not having set the environmentvariable CT_MANAGEMENT_SCOPE, is also mentioned there.
Remote node unable to access shared disks after node crashIf your AIX node crashes and the remote node is unable to access the shared disks (that is, if they arelocked), this may be because your shared volume groups are not enhanced concurrent capable. Forinstructions on making shared volume groups enhanced concurrent capable on AIX, see IBM TivoliSystem Automation for Multiplatforms Installation and Configuration Guide.
Reporting problemsProblems for which no troubleshooting information is available should be reported as PMRs against theproduct IBM Tivoli System Automation for Multiplatforms. When you report the problem, supply thefollowing information:
Chapter 1. Troubleshooting and support 21
• The debug and trace data you collected before troubleshooting (see “Collecting debug and trace data”on page 3)
• A short description of the tasks performed before the error occurred
Known problems and limitations
Tabular output is incorrectly aligned for multibyte languages
Tabular output of line commands may not be aligned correctly when displayed in a shell that has been setto a locale for a multibyte language. This is caused by problem in the Perl scripting language due to whichthe width of multibyte characters is not calculated correctly.
Messages are presented in unexpected language
Some System Automation for Multiplatforms and RSCT commands have related messages that arepresented in a language that is different from the language defined in the user shell environment.
Commands that communicate with RSCT resource managers are started in an environment that is basedon the system locale. If the user shell locale is different from the system locale and if the resourcemanager returns a message to the user shell, this message is presented in the locale of the resourcemanager.
To modify the system locale, follow the instructions in IBM Tivoli System Automation for MultiplatformsInstallation and Configuration Guide.
samlog cannot locate threads.pm
If a message like "Can't locate threads.pm" is displayed when running samlog, the Perl installation onthe system does not support ithreads. If you want to use samlog on your cluster install a version ofPerl with threads enabled on all nodes of the cluster and make it the default Perl environment.
Common pitfalls and user errorsIn this section common pitfalls and user errors are discussed.
Creating a resource of class IBM.AgFileSystemResource of class IBM.AgFileSystem are harvested automatically by the StorageRM resourcemanager during domain start and thereafter.
To support this harvesting, add the mount point of the file system to the file system table on all nodes.You can find the mount point in the attribute SysMountPoint of the file system resource in the classIBM.AgFileSystem. You can specify a mount point after the harvesting as well by modifying theattribute MountPoint of the resource. Ensure, that the change is done for the complete resource (floaterand all constituents). When adding the file system to the file system table located in /etc/fstab onLinux, and /etc/filesystems on AIX, make the following configuration changes for the newly createdentry on all nodes:
• Specify mount option noauto to prevent file system mount during system start.• Disable the option file system check at startup for this file system.
Creating a resource of class IBM.Application
Resources of class IBM.Application require scripts or commands to start, stop, and monitor theapplication resource. Scripts have the following requirements:
• Copy the start, stop, and monitor script on all systems in the same directory.• Make sure that the user specified in the resource attribute UserName is authorized to execute the
scripts.• Make sure that the application resource does not automatically start or stop during system startup or
shutdown initiated by the operating system. Check inittab or init.d in different run levels. If turningoff autostart of a resource that is managed by System Automation for Multiplatforms fails, then it results
22 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
in an resource outage after rebooting a node. System Automation for Multiplatforms detects theresource online on both nodes at the same time, and as a result stops the resource on both nodes.
Creating a resource of class IBM.ServiceIP
The following requirements exist for IBM.ServiceIP resources:
• Make sure that the IP address is not activated by the operating system during system startup. If turningoff autostart of a resource that is managed by System Automation for Multiplatforms fails, then it resultsin an resource outage after rebooting a node. System Automation for Multiplatforms detects theresource online on both nodes at the same time, and as a result stops the resource on both nodes.
Adding a new resource which is observed online to a resource group
Resource definitions are made when all applications are offline. System Automation for Multiplatformsalso allows resource additions, modifications, and deletions when the resources are online. Freeze thecorresponding resource groups using a lock request.
How to enable or disable ManualMode for a domain in state OfflineWhen the cluster is offline, it is not possible to either enable or disable manual mode. The commandsamctrl cannot be used.
The cluster can be started in limited mode, so that resources are invisible. When the cluster is started inthis limited mode only the class IBM.CHARMControl is initialized to run the command samctrl, whileresources from other classes like groups, relationships, and equivalencies stay hidden from theautomation engine.
To enable or disable ManualMode while the cluster is Offline, run the following steps on each clusternode:
1. Copy the template configuration file /usr/sbin/rsct/share/RecoveryRM.cfg to /var/ct/cfg.2. Edit the copied file in /var/ct/cfg/RecoveryRM.cfg.3. Change #activate_charm_control_only 0 to activate_charm_control_only 1.4. After adjusting the configuration file on each cluster node, start the cluster. Now you can use thesamctrl interface, but commands like lsrg do not work.
5. Set ManualMode using samctrl -M T, or unset ManualMode using samctrl -M F.6. Stop the cluster.7. Remove the edited file /var/ct/cfg/RecoveryRM.cfg on each cluster node.8. Start the cluster up again, it will start in normal mode.
How to increase the response time for remote resource managers during resourcevalidation
During resource validation, IBM.RecoveryRM attempts to determine the status of all resources managedby the cluster. Resource validation is run either after domain start-up or after the masterIBM.RecoveryRM daemon moves to a new node. In large clusters some resource managers may not beable to respond back to the master IBM.RecoveryRM within the allotted time frame. The masterIBM.RecoveryRM daemon terminates and the master role is picked up by another IBM.RecoveryRMdaemon in the cluster with the expectation that resource validation completes. This can lead to a chainreaction of the master IBM.RecoveryRM daemon swapping from node to node over and over if one of theremote resource managers cannot respond back to the master IBM.RecoveryRM within the timeoutperiod.
The time setting can be adjusted using the following procedure:
• Copy the template configuration file /usr/sbin/rsct/share/RecoveryRM.cfg to /var/ct/cfg.• Edit the copied file in /var/ct/cfg/RecoveryRM.cfg. Uncomment the following entry and increase
the default period. For example:
Chapter 1. Troubleshooting and support 23
From #resource_verification_allowed_retries 200 to for exampleresource_verification_allowed_retries 300.
• Save the file.
Together with the default retry period of 200ms, the overall time to wait is calculated as:
resource_verification_allowed_retries x resource_verification_retry_period
If you use the default values, the overall time is: 200 x 200ms = 40secs.
If you use the values form this example, the overall time is: 200 x 300ms = 60secs.
After the configuration file is adjusted on each node, start the cluster with the adapted values.
Troubleshooting the SAP high availability solution
No valid license available when activating SAP Central Services high availability policyIf you activate the SAP Central Services high availability policy and the message SAMP0096E wasreturned, make sure that the IBM Tivoli System Automation for Multiplatforms license for the SAP CentralServices high availability policy is installed on all nodes in the cluster. If the license is not installed on allnodes, the SAP Central Services high availability policy cannot be activated.
SAMP0096E: There is no valid license available for the policy you are trying to activate.EXPLANATION: The policy you are trying to activate requires a separate license that is currently not installed.USER ACTION: Install the license and resubmit the command.Policy has been verified.
Troubleshooting the Oracle high availability policy
Oracle database listener does not start up
Problem
If the Oracle database listener is not started by the IBM Tivoli System Automation for Multiplatformspolicy successfully, check the following:
1. Start the database listener using Oracle commands:
#su - <oracle_user>#lsnrctl start
2. The following message should be displayed:
The command completed successfully.
Explanation
If the Oracle database listener is started manually using the command tnslsnr, ensure that the listenerport is not blocked by another process. The default port is 1521. This command is not supported to usethe System Automation for Multiplatforms policy.
Solution
1. Stop the tnslsnr process by using the following command:
#ps -ef | grep tnslsnr
24 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
If an entry like the one below is found, the Oracle listener was started manually using the commandtnslsnr:
#oracle 13749 13708 0 19:21 pts/2 00:00:00 tnslsnr
2. Terminate this process and reset the IBM Tivoli System Automation for Multiplatforms Oracledatabase listener resource if necessary.
3. Log on as Oracle user.4. Start the database listener manually, enter:
lsnctrl start
Such a start will be detected by IBM Tivoli System Automation for Multiplatforms.
If the listener does not start up after you ensured that the port is not blocked, refer to the Oracledatabase documentation.
Oracle database process is monitored unknown
Explanation
The Oracle database process is monitored as Unknown when the following situation is observed:
The MonitorCommandScript for the Oracle database searches for the processora_pmon_<Oracle_SID>. If this process is found, the script checks whether the database is open forrequests using the following commands on the node where the state Unknown is monitored:
#su - <Oracle_user>#sqlplus /nolog#connect / as sysdba#select status from v\\$instance;#exit
If the select statement returns the status OPEN, the MonitorCommandScript returns the status Online, inwhich the database allows transactions.
Example output for status OPEN:
sqlplus /nologSQL*Plus: Release 11.2.0.1.0 Production on Fri Feb 4 17:56:37 2011Copyright (c) 1982, 2009, Oracle. All rights reserved.SQL> connect / as sysdbaConnected.SQL> select status from v$instance;STATUS------------OPEN
For any other state, for example STARTED, the MonitorCommandScript returns the status Unknown, sincethe database is neither Online nor Offline, but also not in an intermediate state like Starting or Stopping.
Example output for status STARTED:
sqlplus /nologSQL*Plus: Release 11.2.0.1.0 Production on Fri Feb 4 17:53:39 2011Copyright (c) 1982, 2009, Oracle. All rights reserved.SQL> connect / as sysdbaConnected.SQL> select status from v$instance;STATUS------------STARTED
Chapter 1. Troubleshooting and support 25
Solution
To resolve the Unknown state, execute the following steps on the node where Unknown is monitored:
#su -<Oracle_user>#sqlplus /nolog#connect / as sysdba#shutdown immediate
Troubleshooting the NFS tiebreakerIf the System Automation for Multiplatforms NFS tiebreaker is started with option Log=2, additional traceinformation is written to syslog.
NFS tiebreaker on LinuxOn the NFS v4 server system, the output of the command rpcinfo –u localhost nfs needs tocontain the line
program 100003 version 4 ready and waiting
The nfsstat –s command returns details on the current status of NFS. The command dmesg|grep -infs displays NFS related kernel messages from the past few minutes.
NFS tiebreaker on AIXOn the NFS v4 server system, the output of the command rpcinfo –u localhost nfs needs tocontain the line
program 100003 version 4 ready and waiting
The nfsstat –m command returns details on the current status of NFS. You may restart the NFS relateddaemons with the following commands:
stopsrc –g nfsstartsrc –g nfs
Using IBM Support AssistantIBM Support Assistant is a free, standalone application that you can install on any workstation. IBMSupport Assistant saves you time searching product, support, and educational resources and helps yougather support information when you need to open a problem management record (PMR) or ElectronicTracking Record (ETR), which you can then use to track the problem.
You can then enhance the application by installing product-specific plug-in modules for the IBM productsyou use. The product-specific plug-in for Tivoli System Automation for Multiplatforms provides you withthe following resources:
• Support links• Education links• Ability to submit problem management reports• Capability to collect traces
Installing IBM Support Assistant and the Tivoli System Automation for Multiplatformsplug-in
To install the IBM Support Assistant V4.1, complete these steps:
• Go to the IBM Support Assistant Web Site: http://www.ibm.com/software/support/isa/
26 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
• Download the installation package for your platform. Note that you will need to sign in with an IBM userID and password (for example, a MySupport or developerWorks® user ID). If you do not already have anIBM user ID, you may complete the free registration process to obtain one.
• Uncompress the installation package to a temporary directory.• Follow the instructions in the Installation and Troubleshooting Guide, included in the installation
package, to install the IBM Support Assistant.
To install the plug-in for Tivoli System Automation for Multiplatforms, complete these steps:
1. Start the IBM Support Assistant application. IBM Support Assistant is a Web application that isdisplayed 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 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.
Chapter 1. Troubleshooting and support 27
28 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Chapter 2. ReferenceRead about the syntax and usage of System Automation for Multiplatforms commands. The AutomationPolicy XML reference helps you define your automation policies by specifying the correct XML elements .
Commands ReferenceThe following table lists the System Automation for Multiplatforms commands that are described in thismanual:
Table 2. System Automation for Multiplatforms commands.
Command Description
“addrgmbr” on page 32 Adds one or more resources to a resource group
“cfgsamadapter” on page 35 Configures the SA MP adapter
“chequ” on page 37 Changes a resource equivalency
“chrel” on page 40 Changes one or more managed relationships betweenresources
“chrg” on page 45 Changes persistent attribute values of a resource group(including starting and stopping a resource group)
“chrgmbr” on page 48 Changes the persistent attribute value(s) of a managedresource in a resource group
“installSAM” on page 51 Verifies that all installation prerequisites are met andinstalls System Automation for Multiplatforms, includingthe end-to-end automation adapter
“lsequ” on page 53 Lists equivalencies and their attributes
“lsrel” on page 57 Lists managed relationships
“lsrg” on page 61 Lists persistent attribute values of a resource group or itsresource group members
“lsrgreq” on page 66 Lists outstanding requests applied against resource groupsor managed resources
“lssam” on page 69 Lists resources groups and their members in tree format.
“lssamctrl” on page 73 Lists System Automation for Multiplatforms controls
“mkequ” on page 75 Makes an equivalency resource
“mkrel” on page 78 Makes a managed relationship between resources
“mkrg” on page 82 Makes a resource group
“pidmon” on page 85 Searches the process list for a given command string
“prereqSAM” on page 87 Checks whether all prerequisites for the installation ofSystem Automation for Multiplatforms are met
“rgmbrreq” on page 88 Requests a managed resource to be started or stopped, orcancels the request
“rgreq” on page 91 Requests a resource group to be started, stopped ormoved, or cancels the request
© Copyright IBM Corp. 2006, 2020 29
Table 2. System Automation for Multiplatforms commands. (continued)
Command Description
“rmequ” on page 94 Removes one or more resource equivalencies
“rmrel” on page 95 Removes a managed relationship between resources
“rmrg” on page 99 Removes a resource group
“rmrgmbr” on page 101 Removes one or more resources from the resource group
“samadapter” on page 104 Starts, stops or monitors the status of the SA MP Adapter
“samcc” on page 105 Controls the defined resource groups and their members intree format.
“samctrl” on page 109 Sets the System Automation for Multiplatforms controlparameters
“samdiag” on page 111 Gathers snap-shot information on a resource
“samlicm” on page 114 Installs, lists and upgrades the product license
“samlog” on page 115 Collects, formats, merges, and displays related logs
“sampolicy” on page 119 Activates, deactivates, and verifies a policy XML, saves aconfiguration, retrieves policy information
“samsimul” on page 122 Simulates a series of requests or state changes anddisplays the results.
“samwhy” on page 124 Retrieve information about application failures
“setupAdapterNonRoot” on page 127 Configures the end-to-end automation adapter to run witha user other than 'root'
“samnonrootuser ” on page 126 Configures local (non-root) system users to manage(operate or administrate) System Automation forMultiplatform resources
“uninstallSAM” on page 125 Uninstalls all components of System Automation forMultiplatforms
RSCT RMC commands and filesThe following table lists the RSCT commands that you need for working with IBM Tivoli SystemAutomation. For information, see RSCT peer domain configuration commands.
Command Description
addrpnode Adds a node to a cluster
chrsrc Changes persistent attribute values of a resource within a specified resource class
lsrpdomain Lists information about clusters
lsrpnode Lists information about nodes in a cluster
lsrsrc Lists resources of a resource class
lssrc Lists the status of subsystems
mkrpdomain Creates a new cluster
mkrsrc Creates resources of a specified resource class
preprpnode Prepares the node before creating a cluster (security setup)
30 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Command Description
resetrsrc Resets resources of a specified resource class
rmrpdomain Removes a cluster
rmrpnode Removes a node from a cluster
rmrsrc Removes resources of a specified resource class
runact Runs an action on a resource class
startrpdomain Brings a cluster online
startrpnode Brings a node in a cluster online
startrsrc Brings an individual resource online
startsrc Starts an individual subsystem
stoprpdomain Brings a cluster offline
stoprpnode Brings a node in a cluster offline
stoprsrc Brings an individual resource offline
stopsrc Stops an individual subsystem
Setting the environment variablesCT_CONTACT
When the CT_CONTACT environment variable is set to a host name or IP address, the commandcontacts the Resource Monitoring and Control (RMC) daemon on the specified host. If theenvironment variable is not set, the command contacts the RMC daemon on the local system wherethe command is being run. The resource class or resources that are displayed or modified by thecommand are located on the system to which the connection is established.
CT_LOCAL_SCOPEThe CT_LOCAL_SCOPE environment variable sets the RMC subsystem scope to the standaloneenvironment. By default, the RMC subsystem monitors and controls the resources and resourceclasses on all nodes in the cluster. A cluster can consist of one or more nodes. When a clusterconsists of one node, it is said to operate in a standalone environment. The scope of a command inthe standalone environment is the local node. The scope of a command in a cluster environment ofmore than one node is the entire cluster. For a cluster of more than one node, to return or changeresources or resource classes only on the node where RMC is running, set the CT_LOCAL_SCOPEenvironment variable to 1, as follows:
export CT_LOCAL_SCOPE=1
For example, assume that a cluster consists of nodes A, B, and C and the following command is run:
lsrsrc IBM.FileSystem
Resources for the file systems associated with nodes A, B, and C are returned.
If CT_LOCAL_SCOPE is set to 1 and the lsrsrc command is run on Node A, then only the file systemresources associated with node A are returned.
CT_MANAGEMENT_SCOPEThe CT_MANAGEMENT_SCOPE environment variable must be set on all nodes for all users of IBMTivoli System Automation. Enter CT_MANAGEMENT_SCOPE=2 (peer domain scope). The variablemay be permanently set in the profile.
Chapter 2. Reference 31
addrgmbr
Name
addrgmbr - Adds one or more resources to a resource group.
Synopsis
addrgmbr [-h] [-f data_input_file] [-T] [-V]
addrgmbr [-h] -s [-m T | F] [-p A | O[,Failback] [-T] [-V] -g Resource_groupResource_class:"selection_string" [Resource_class:"selection_string" [...]]
addrgmbr [-h] [-m T | F] [-p A |O[,Failback] [-T] [-V] -g Resource_groupResource_class:Resource_name[:Node][, Resource_name[:Node][, ...]][Resource_class:Resource_name[:Node][,Resource_name[:Node][, ...]] [...]]
addrgmbr [-r 0 | AutomaticRecovery | 1 | LockOnResFailure | 2 | LockOnAnyFailure]
Description
The addrgmbr command adds one or more new resources to a resource group. If a data_input_file andthe -f option is not specified, then either a selection string or a resource name must be specified whenthis command is used. A resource name or selection string must be specified with the resource class towhich it belongs. A fixed resource must include the resource class and the node name at which it islocated. A member resource cannot be included in more than one resource group at the same time. Amember resource cannot be in a resource group and in an equivalency at the same time. Each member ofthe resource group must exist as an RMC resource before it is added to a resource group. A resourcegroup member can be defined only on an online node in a cluster.
You can add multiple resources to a resource group if they are offline and if the nominal state of theresource group is offline. If the OpState of a resource to be added is online, the addition of that resourcewould cause an immediate stop of that resource. If the resource is stopping, the addition of anotherresource is rejected.
Member resources and their attribute flags can be specified on the command prompt as the syntaxindicates or from a file when used with the -f option. The value must be the same data type that isdefined for this resource attribute. Use the lsrsrcdef command to verify the data type and attributefield for each attribute.
Options
-f data_input_fileName of the file, which contains member resource attribute information.
-g Resource_groupThe unique name of the resource group, to which the member resources are to be added. Thisrepresents the MemberOf attribute of the managed resource.
-hHelp. Writes the command's usage statement to standard output.
-m T|FMandatory Attribute. Specifies whether this managed resource is required in the resource group.T
TRUE (the Default). These managed resources are required by the resource group.F
FALSE. These managed resources are not required by the resource group.-p A|O[,Failback]
Specifies the method to be used when a node is selected to place the resource on. The value can be:
32 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
AAny.
OOrdered. Default value.
FailbackOptional. Occurrence as comma-separated value. In combination with O (Ordered) only.
-sSpecifies that a selection string is used instead of the resource name.
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
-r 0 | AutomaticRecovery | 1 | LockOnResFailure | 2 | LockOnAnyFailureSpecifies the RecoveryPolicy attribute that defines how the group member is recovered from a failure.The value can be:0 | AutomaticRecovery
Automatically recover from the failure. Default value.1 | LockOnResFailure
Process a lock request on the resource group if the member fails. Automatically recover themember if the node, which hosts the member fails.
2 | LockOnAnyFailureProcess a lock request on the resource group if the member or the hosting node fails.
Parameters
Resource_class:"selection_string"
Specifies the selection string. The -s option determines this parameter. Each selection string mustbe preceded by a resource class. The specified selection string is applied to its correspondingResource_class attributes to determine which resources are to be made members of theResource_group. The selection_string and its resource class must be separated by the colon or ": "delimiter.
The selection string must be enclosed within either double or single quotation marks. If the selectionstring contains double quotation marks, enclose the entire selection string in single quotation marks.For example:
-s IBM.Application:'Name == "testing"'
-s IBM.Application:'Name ?= "test"'
-s IBM.Application:'Name like "%"' ( For all resources)
Resource_class:Resource_name[:Node]Member resources specify one or more member resources that are to be acted on. Resourcesbelonging to different resource classes can also be specified by using this syntax. Member resources,which belong to different classes must be separated by spaces. A member resource is identified bythe resource's class Resource_class, the resource's name Resource_name, and optionally the nodeNode the resource is on. The Resource_class, Resource, and Node must be separated by a colon.Resource_class is the name of the resource class the member resource belongs to. Resource is thename of the actual member resource in its class. The node must be included when it tries to act on afixed member resource. The node and its resource must be separated by the colon or ":" delimiter.Multiple resources, which belong to the same resource class can also be specified and are separatedby a comma:Resource_class:Resource[:Node][,Resource[:Node][,...]] The member resources must existin the resource group for the requested action to take place.
Chapter 2. Reference 33
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command prompt.
4Incorrect parameter on command prompt.
5Error occurred with RMC that was based on faulty command prompt input.
6The specified resource was not found.
7Resource exists.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
1. To create member resources, which use the data input file, proceed as follows:
a. To generate a template to aid in the defining of these resources in a file, enter the command:
lsrsrcdef -i IBM.ManagedResource >/tmp/MgdR.rdef
b. Edit the file /tmp/MgdR.rdef with your preferred file editor: (Enter values for all of the attributes,substituting an appropriate value for the type, or leave it blank if you want the default value.)
c. Run the addrgmbr command with the file as follows:
addrgmbr -f /tmp/MgdR.rdef
Sample data ínput file for addrgmbr:
You can enter values for all of the attributes and thus change the value shown below, or remove theline with the attribute if you want the default value.
PersistentResourceAttributes::resource 1:ManagedResource = IBM.Application:App1 MemberOf = "charmC" resource 2: ManagedResource = IBM.Application:Res2:saopt02 MemberOf = "charmC" Mandatory = false
2. To add a floating resource testerA belonging to resource class IBM.Application, as member to aresource group resA, enter:
addrgmbr -g resA IBM.Application:testerA
34 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
3. To add the floating resource testerA and testerB belonging to resource class IBM.Application,and the fixed resource ip1 of class IBM.ServiceIP, locating at node node1, as members to aresource group resA, enter:
addrgmbr -g resA IBM.Application:testerA,testerB IBM.ServiceIP:ip1:node1
4. To add selected member resources of the resource class IBM.Application, to a resource groupresA as a mandatory resource, enter:
addrgmbr -m T -g resA IBM.Application:testerA,resA
Sample data input file:
PersistentResourceAttributes::resource 1:ManagedResource = "0x001b 0xffff 0x35c05b13 0x00000000 0x9a6ee5e0 0x0de8934c"MemberOf = "charmC"resource 2:ManagedResource = "0x001b 0xffff 0x35c05b13 0x00000000 0xb4d7e1b0 0x0def4ba2"MemberOf = "charmC"Mandatory = 0NominalState = 0
Files
/usr/sbin/rsct/bin/addrgmbrLocation of the addrgmbr command.
data_input_file
See Also
The samctrl, chrel, chrg, chrgmbr, lsrg, mkrg, mkrel, rmrel, rmrg, rmrgmbr commands.
The rmccli general information file.
The Resource_Data_Input file
cfgsamadapter
Name
cfgsamadapter - Configure the end-to-end automation adapter.
Synopsis
cfgsamadapter [-h]
cfgsamadapter [-s]
cfgsamadapter [-s[-g|-gr] [-l location]]
Description
The cfgsamadapter command starts the end-to-end automation adapter configuration dialog,configures the end-to-end automation adapter in silent mode, or generates an input properties file forsilent configuration.
Options
<no option>Starts the configuration dialog as the default action when no option is specified.
Chapter 2. Reference 35
-s
• Starts the configuration utility in silent mode if the -g or -gr option is not specified.• Generates an input properties file for silent configuration if the -g or -gr option is specified.
-gGenerates an input properties file for silent configuration if it does not yet exist.
-grGenerates an input properties file for silent configuration. A file that already exists is replaced.
-l locationIn conjunction with options -g and -gr the input properties file for silent configuration is generated inthe directory that is specified with location.
To run a silent configuration, the input properties file is retrieved from the directory that is specifiedwith location.
If -l is omitted, the default directory is used, see Examples section.
-hWrites the command’s usage statement to standard output.
Exit Status
All return codes greater than zero apply if the command is run in silent mode, by using the -s option.0
The command ran successfully.1
The command run successfully, but the command output contains warnings.2
The command failed. Invalid or missing input is detected in the silent input properties file. Thecommand output contains corresponding error messages.
3The command failed. The attempt to update at least one of the target configuration files failed. Thecommand output lists files and error messages for the unsuccessful update attempts.
9The command failed due to an unexpected unrecoverable error. The command output containscorresponding error messages.
Security
The command requires either root authority or write access to the directories /etc/opt/IBM/tsamp/sam/cfg and /etc/Tivoli.
Examples
1. To generate an input properties file for silent configuration, enter:
cfgsamadapter -s -g
Output:
----- Generate silent configuration input properties file ----- Silent configuration input properties file /etc/opt/IBM/tsamp/sam/cfg/silent.samadapter.properties has been created.
2. To generate an input properties file for silent configuration in a location other than the default location,enter:
cfgsamadapter -s -g -l /var/config
36 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Output:
----- Generate silent configuration input properties file -----Silent configuration input properties file /var/config/silent.samadapter.properties has been created.
3. To configure the end-to-end automation adapter in silent mode, enter:
cfgsamadapter -s
Output:
Configuration completed successfully. ----- Configuration update status ----- Configuration file: /etc/opt/IBM/tsamp/sam/cfg/sam.adapter.properties Update: OK Configuration file: /etc/opt/IBM/tsamp/sam/cfg/sam.adapter.ssl.properties Update: OK Configuration file: /etc/opt/IBM/tsamp/sam/cfg/sam.adapter.conf Update: No change Configuration file: /etc/opt/IBM/tsamp/sam/cfg/sam.adapter.jaas.properties Update: No change Configuration file: /etc/opt/IBM/tsamp/sam/cfg/sam.adapter.jlog.properties Update: No changeConfiguration file: /etc/opt/IBM/tsamp/sam/cfg/sam.adapter.plugin.properties Update: No changeConfiguration file: /etc/Tivoli/samPublisher.conf Update: No change Configuration file: /etc/opt/IBM/tsamp/sam/cfg/EEZPublisher.conf Update: No change Configuration file: /etc/opt/IBM/tsamp/sam/cfg/JDBCPublisher.conf Update: OK ----- End configuration update status -----
Files
/opt/IBM/tsamp/sam/bin/cfgsamadapterLocation of the cfgsamadapter command.
chequ
Name
chequ - Changes an already-defined resource equivalency.
Synopsis
chequ [-h] [-i] -u a | d | r [-p A[,NoFailure | NoControl] | O[,Failback |NoFailure | NoControl]] [-m Minimum_Necessary] [-T] [-V] -S "Static_select_string" EquivalencyResource_class
chequ [-h] [-i] -u r [-p A[,NoFailure | NoControl]] [-m Minimum_Necessary] [-T] [-V] -D"Dynamic_select_string" Equivalency Resource_class
chequ [-h] [-i ] [-u a | d | r] [-p A[,NoFailure | NoControl] | O[,Failback |NoFailure | NoControl]] [-m Minimum_Necessary] [-c New_Equiv] [-T] [-V] Equivalency[Resource_class:Resource_name[:Node] [,Resource_name[:Node][,...]]]
Description
The chequ command changes a resource equivalency. Resources can be added, removed, or replaced inan equivalency. All resources in an equivalency must be from the same resource class. Even the name ofthe equivalency can be changed with this command.
Equivalencies and their attribute flags can be specified on the command prompt as the syntax indicates.The value must be the same data type that is defined for the resource attributes. Use the lsrsrcdefcommand to verify the data type and attribute field for each attribute.
Explicit specification of resource names without selection string is not supported for IPv6–enabledIBM.NetworkInterface equivalency members.
Options
-u a | d | rUpdate Equivalency resources.
Chapter 2. Reference 37
aAdds the specified resources to the specified equivalency.
dDeletes the specified resources from the specified equivalency.
rReplace/Overwrite Equivalency resources. Replaces the equivalency resources with the specifiedequivalency resources.
-c New_EquivSpecifies a new name that replaces the current Equivalency parameter.
-D "Dynamic_selection_string"The specified selection string is saved as the SelectString attribute for the concerned equivalency. Theoption dynamic_selection_string is then applied to all resources of the specified resource classby the Recovery Manager to dynamically determine what members are to be included in the specifiedequivalency. This option must be used with the r option and also cannot be combined with theResource_name [:Node] operand. The selection string must be enclosed within double or singlequotation marks. If the selection string contains double quotation marks, enclose the entire selectionstring in single quotation marks. For example:
-D 'Name == "testing"'
-D 'Name ?= "test"'
The -D option cannot be combined with the -S option or with an -p O option [ORDEREDSelectFromPolicy).
-hHelp. Writes the command's usage statement to standard output.
-iInteractive Prompt. Prompt before changing equivalency.
-p A | O [,Failback | NoFailure | NoControl]Specifies the equivalency select-from policy. The value can be:A
Any. Default value.O
Ordered. The value cannot be used together with the -D option.
Optional comma-separated values:
• Failback: only in combination with Ordered.• NoFailure• NoControl
-m Minimum_NecessaryMinimum Necessary Equivalency. Specifies the minimum necessary members to make an equivalencyvalid.
-S "Static_selection_string"The specified selection string applies to the specified resource class to determine the resources thatmake up the equivalency. These resources are saved as the MemberShip attribute for the concernedequivalency. This option cannot be combined with the Resource_name [: Node] operand. Resourcescan be added, deleted, and replaced when this string is used. The selection string must be enclosedwithin double or single quotation marks. If the selection string contains double quotation marks,enclose the entire selection string in single quotation marks. For example:
-S 'Name == "testing"'
-S 'Name ?= "test"'
38 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
-S cannot be combined with -D.-T
Writes the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
ParametersEquivalency
Specifies the unique name of the already defined equivalency to be changed.Resource_class:Resource_name[:Node]
Specifies one or more resources that are added to or deleted from the specified equivalency. All of theresources must be from the same resource class. An equivalency resource is identified by theresource class (Resource_class) and the resource name (Resource_name), and, optionally, the node(Node) at which the resource is located. Resource_class, Resource_Name, and Node must beseparated by a colon. Resource_class is the name of the Resource class the equivalency resourcebelongs to. The first resource or Resource_name[:Node] must be preceded by the Resource_class itbelongs to and it must be separated by the colon (:) delimiter. Multiple resources can be specified andare separated by a comma. Since all resources must be from the same class, the Resource_class is tobe specified only once as the syntax indicates.
This syntax is not supported for IPv6–enabled IBM.NetworkInterface equivalency members: useselection string syntax instead.
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command prompt.
4Incorrect parameter on command prompt.
5Error occurred with RMC that was based on faulty command prompt input.
6Resource specified was not found.
7Resource exists.
Security
This command requires root authority, or a user ID with appropriate permissions. (For more information,see System Automation for Multiplatforms Administrator's and User's Guide.)
Examples
1. To add another resource tester that belongs to resource class IBM.Application to an equivalencycalled resA, type:
chequ -u a resA IBM.Application:tester:node-name
Chapter 2. Reference 39
2. To delete a resource tester1 that belongs to resource class IBM.Application from an equivalencythat is called test, enter:
chequ -u d test IBM.Application:tester1:node-name
3. To add an equivalency that is called Jfoo with selected members of the resource classIBM.Application by using a select string, enter:
chequ -u a -S "ResourceType==0" Jfoo IBM.Application
4. To overwrite an equivalency that is called Jfoo with selected members of the resource classIBM.Application by using a dynamic select string, enter:
chequ -u r -D "ResourceType==0" Jfoo IBM.Application
Files
/usr/sbin/rsct/bin/chequLocation of the chequ command.
See Also
The samctrl, lsequ, mkequ, rmequ commands.
The rmccli general information file.
chrel
Name
chrel - Changes one or more managed relationships between resources.
Synopsis
chrel [-h] [-i] [-u a | d | r] -s "Selection_string" [-c relation_name] [-p relationship][-o condition][-W New_Target_Class[:Resource_name[:Node][,New_Target_Class[:Resource_name[:Node][,…]]]]] [-w "New_Target_string"] [-T] [-V]
chrel [-h] [-i] [-u a | d | r] [-c relation_name] [-p relationship] [-o condition] [-WNew_Target_Class[:Resource_name[:Node][,New_Target_Class[:Resource_name[:Node][,…]]]]] [-w "New_Target_string"] [-T] [-V] Managed_Relation
chrel [-h] [-i] [-u a | d | r] [-c relation_name] [-p relationship] [-o condition] [-WNew_Target_Class[:Resource_name[:Node][,New_Target_Class [:Resource_name[: Node][,…]]]]] [-w"New_Target_string"] -S Source_Class[:Resource_name[:Node]] [-s "Source_string"] [-G Target_Class[:Resource_name[:Node][,Target_Class[:Resource_name[:Node][,…]]]] [-g "Target_string"] [-P Current_relationship] [-OCurrent_condition] [-T] [-V]
Description
The chrel command modifies a managed relationship between resources. The managed relationship isbetween a source resource and one or more target resources. The source resource must be a managedresource, which is either a member of a resource group or a resource group. The target resource does nothave to be in a resource group. Managed relationships and their attributes can be specified on thecommand prompt as the syntax indicates. The attribute value must be of the same data type that isdefined for the resource attribute. Use the lsrsrcdef command to verify the data type and attributefield for each attribute.
40 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Options
-u a | d | r|Update targets.a
Add the specified new target resources to the relationship defined for the source resources.d
Delete the specified new target resources from the relationship that is defined for the sourceresources.
rReplaces (overwrites) the relationship that is defined for the source resource with the specifiednew target resources.
-o conditionSpecifies the new condition to be used when a Location relationship (Collocated, AntiCollocated,Affinity, or AntiAffinity) or a StartAfter relationship (IfPossible condition only) is defined. The value canbe the numeric value or the word (not case-sensitive):0x0000 or NoCondition
Specifies unconditional location relationship.0x0001 or IfOnline
Specifies that the target resource is online.0x0002 or IfOffline
Specifies that the target resource is offline, failed offline, or unknown.0x0003 or IfNotOnline
Specifies that the target resource is not online.0x0004 or IfNotOffline
Specifies that the target resource is not offline or failed offline.0x0005 or IfPossible
Used with the StartAfter relationship. Specifies that the target resource group can be bypassed ifit cannot be bound, in which case it ends up in Sacrificed state and the StartAfter relationship isignored.
-O conditionSpecifies the condition value to query all the defined relationship to find a match with an existingcondition. The value can be the numeric value or the word (not case-sensitive):0x0000 or NoCondition
Specifies unconditional location relationship.0x0001 or IfOnline
Specifies that the target resource is online.0x0002 or IfOffline
Specifies that the target resource is offline, failed offline, or unknown.0x0003 or IfNotOnline
Specifies that the target resource is not online.0x0004 or IfNotOffline
Specifies that the target resource is not offline or failed offline.0x0005 or IfPossible
Used with the StartAfter relationship. Specifies that the target resource group can be bypassed ifit cannot be bound, in which case it ends up in Sacrificed state and the StartAfter relationship isignored.
-g Target_stringThe Target_string is applied to all resources of the resource class that is specified by the -G option, todetermine the targets of the relationship.
Chapter 2. Reference 41
If the -g option is used to specify a target selection string, Resource_name and Node must not bespecified for the -G option.
-G Target_class:[Resource_name[:Node]]
Specifies the target resources to add, delete, or replace with the relationship. The target resource orresources is used with the source and any other specified query to find a match from all of the definedrelationships. A target resource is identified by the resource's class (Target_class), the resource name(Resource_name), and, optionally, the node Node on which the resource is located. Target_class,Resource_name, and Node must be separated by colons. Multiple target resources can be specifiedand are separated by commas. The colons are required, but omitting Target_class or Resource_namecauses the previously specified class or name to be used when multiple target resources arespecified.
If the -g option is used to specify a target selection string, Resource_name and Node must not bespecified for the -G option.
-hWrites the command's usage statement to standard output.
-iInteractive. Prompt before you change relationships.
-c relation_nameSpecifies the new name for the specified managed relationship. The change-of-name can be appliedonly to one relationship. If a name change is required, Queries and Selection strings should matchwith only one relationship.
-p relationshipSpecifies the new managed relationship to apply. The value can be the numeric value or the word (notcase-sensitive):0x0001 or Collocated
Specifies that the source and the target resources are to be on the same node.0x0002 or AntiCollocated
Specifies that the source and the target resources are to be on different nodes.0x0003 or Affinity
Specifies that the source resource and its specified affinity resource are to be on the same node, ifpossible.
0x0004 or AntiAffinitySpecifies that the source resource and its specified affinity resource are to be on different nodes,if possible.
0x0005 or IsStartableSpecifies that the source and its target resources are startable.
0x0006 or StartAfterSpecifies that the source is to be started after the target resources.
0x0007 or DependsOnSpecifies that the target resources must be online before the source resource is started.
• A DependsOn relationship also includes an implicit collocation between the source and targetresources (see the description of Collocated relationship in System Automation forMultiplatforms Administrator's and User's Guide.
• If a target resource fails, the source resource is also stopped.
0x0008 or DependsOnAnySpecifies that the target must be online before the source resource is started. It is identical to theDependsOn relationship except that it does not provide the collocated constraint for the startsequence. Therefore, the source and target resources cannot be started on the same node.
42 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
0x0009 or StopAfterSpecifies that the source resource cannot be stopped until after the target resource broughtoffline.
0x000A or ForcedDownBySpecifies that the source resource must be forced offline if either the target resource goes offlineunexpectedly or the target resource itself is forced offline.
-P relationshipSpecifies the managed relationship value that is used to query all the defined relationships to find amatch. The value can be a numeric value or the word (not case-sensitive):0x0001 or Collocated
Specifies that the source and the target resources are to be on the same node.0x0002 or AntiCollocated
Specifies that the source and the target resources are to be on different nodes.0x0003 or Affinity
Specifies that the source resource and its specified affinity resource are to be on the same node, ifpossible.
0x0004 or AntiAffinitySpecifies that the source resource and its specified affinity resource are to be on different nodes,if possible.
0x0005 or IsStartableSpecifies that the source and its target resources are startable.
0x0006 or StartAfterSpecifies that the source is to be started after the target resources.
0x0007 or DependsOnSpecifies that the target resources must be online before the source resource is started.
• A DependsOn relationship also includes an implicit collocation between the source and targetresources. See the description of Collocated relationship in System Automation forMultiplatforms Administrator's and User's Guide.
• If a target resource fails, the source resource is also stopped.
0x0008 or DependsOnAnySpecifies that the target must be online before the source resource is started. It is identical to theDependsOn relationship except that it does not provide the collocated constraint for the startsequence. Therefore, the source and target resources cannot be started on the same node.
0x0009 or StopAfterSpecifies that the source resource cannot be stopped until after the target resource is broughtoffline.
0x000A or ForcedDownBySpecifies that the source resource must be forced offline if either the target resource goes offlineunexpectedly or the target resource itself is forced offline.
-w New_Target_stringSpecifies the target selection string for the resources to add, delete, or replace with the relationship.New_Target_string is applied to all resources of the resource class that is specified by the -G option todetermine the targets of the relationship.
If the -g option is used to specify a target selection string, Resource_name and Node must not bespecified for the -G option.
-W New_Target_Class: Resource_name[: Node]New Target resources. These resources are added, deleted, or replaced as required to or from thecurrent list of target resources for the matching relationships. A target resource is identified by theresource's class Resource_class, the resource's name Resource_name, and optionally the node Nodethe resource is on. The Resource_class, Resource_name and Node must be separated by a colon.Multiple target resources can be specified and are separated by a comma. The colons are required but
Chapter 2. Reference 43
omitting the Resource_class or Resource_name causes the previously specified class or name to beused, when multiple target resources are specified.
If the -g option is used to specify a target selection string, Resource_name and Node must not bespecified for -G.
-s Selection_string
Specifies the source selection string of the relationship to change. Selection_string is applied to allresources of the resource class that is specified by the -S option to determine the source of therelationship. The result of the selection can contain one or more resources.
If the -s option is used to specify a source selection string, Resource_name and Node must not bespecified for the -S option.
-S Source_class:[Resource_name[:Node]]
Specifies the source resource of the relationship to change. A source resource is identified by theresource class (Resource_class) of the resource, the resource name (Resource_name), and, optionally,the node (Node) at which the resource is located. The result of the selection can contain one or moreresources.
If the -s option is used to specify a source selection string, Resource_name and Node must not bespecified for the -S option.
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
ParametersManaged_Relation
Name of the managed relationship to be changed. Using the -c option, even the name of therelationship can be modified.
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command prompt.
4Incorrect parameter on command prompt.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
7Resource exists.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
44 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Examples
1. To add a relationship for a resource tester that belongs to resource class IBM.Application withtarget resources from resource class IBM.Application, whose ResourceType is set to zero, enter:
chrel -u a -S IBM.Application:tester -W IBM.Application -w "ResourceType==0" -G IBM.Application -g "ResourceType==1"
2. To modify a relationship for a source resource narten that belongs to resource classIBM.Application to add resources tr0 and en0 of resource class IBM.NetworkInterface,enter:
chrel -u a -S IBM.Application:narten -W IBM.NetworkInterface:tr0,:en0
Files
/usr/sbin/rsct/bin/chrelLocation of the chrel command.
See Also
The addrgmbr, chequ, chrg, chrgmbr, lsrg, mkequ, mkrel, mkrg, rmequ, rmrel, rmrg, rmrgmbrcommands.
The rmccli general information file.
chrg
Name
chrg - Changes persistent attribute values of one or more resource groups, including starting andstopping resource groups.
Synopsis
chrg [-h] [-i] [-u a | d | r] -s "selection_string" [-l relationship ] [-n node_name | -e equiv_name][-o nominal_state] [-p priority] [-N Owner] [-D Description] [-I InfoLink] [-T] [-V] [-x node1, ...noden]
chrg [-h] [-i] [-u a | d | r] [-c new_name] [-l relationship ] [-n node_name | -e equiv_name] [-onominal_state] [-p priority] [-N Owner] [-D Description] [-I InfoLink] [-T] [-V] [-x node1, ...noden]Resource_group [ … ]
Description
The chrg command changes the persistent attribute values of one or more resource groups. The name ofthe resource group is specified by Resource_group. The resource groups to be changed can also bedetermined using the selection string with the -s option. The name of a resource group can also bechanged with this command using the -c option. System Automation for Multiplatforms will then updateall the associated member resources with this change. To allow System Automation for Multiplatforms tomonitor and control these resource groups, the resource group must be in an Online Nominal State.
Options
-c new_nameSpecifies the new Resource_group name. Renames the Resource_group name with new_name.
-e equiv_nameSpecifies the equivalency name of the nodes on which the Resource_group can run. This option cannotbe combined with the -n option. To set the resource group with the equivalency of all nodes in thecluster, specify equiv_name as the string ALL.
Chapter 2. Reference 45
-hWrites the command's usage statement to standard output.
-iInteractive. Prompt before changing resource groups.
-u a | d | rSpecifies what should be done with the specified node list. Note that these options require the -xoption.a
Adds the specified nodes to the list of excluded nodes.d
Deletes the specified nodes from the list.r
Replaces the exclude list with the specified nodes.-x node1, ...noden
Specifies the excluded node list. Only to be used in conjunction with -u a | d | r.-l relationship
Specifies the location relationship among the members of the resource group. The locationrelationship value can be entered as the numeric value or as the word (not case-sensitive):0x0000 or None
None. Specifies that member resources of the resource group can be on any node0x0001 or Collocated
Specifies that member resources of the resource group are to be located on the same node.-n node_name
Specifies the node on which the Resource_group can run. This option cannot be combined with the -eoption.
-o nominal_stateSpecifies the Nominal state of the resource group, which can be online or offline. Nominal state valuescan be entered as the numeric value or as the word (not case-sensitive):0x0000 or Online
Online. Specifies that the desired state of Resource_group is online.0x0001 or Offline
Offline. Specifies that the desired state of Resource_group is offline.-p priority
Specifies the relative importance of this resource group compared to other resource groups. Prioritycan be any integer from 0 to 200: the higher the integer, the higher the priority. The default priorityvalue is 0.
-N OwnerA string with the name of the owner or contact for the group.
-D DescriptionA string describing the purpose of the group.
-I InfoLinkA string containing the URL of a HTML page which shows additional information about the resourcegroup.
-s Selection_string
Specifies the source selection string of the persistent attribute values to change. Selection_string isapplied to all existing resource groups.
The selection string must be enclosed within either double or single quotation marks. If the selectionstring contains double quotation marks, enclose the entire selection string in single quotation marks.For example:
46 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
-s 'Name == "testing"'
-s 'Name ?= "test"'
-s 'Name like "%"' ( For all resources)
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
Parameters
Resource_groupThe unique name of the resource group to be changed. This resource group must already exist for thisoperation to succeed. Multiple resource groups can be specified but must be separated by spaces.
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
7Resource already exists.
Security
This command requires root authority, or a user ID with appropriate permissions.For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
1. To change the persistent-attribute location relationship to Collocated, Nominal state to Online,and the priority value to 34 of a resource group called resA, enter:
chrg -l collocated -o 0 -p 34 resA
2. To change the name of resource group resA to clusterfoo with location relationship now changedto None, and allowed node name of cluster, enter:
chrg -c clusterfoo -l 0 -n cluster resA
Chapter 2. Reference 47
3. To change the location relationship to None, and allowed node name cluster for all resource groupscontaining the name resA, enter:
chrg -l none -n cluster -s 'Name like "%resA%"'
Files
/usr/sbin/rsct/bin/chrgLocation of the chrg command.
See Also
The addrgmbr, samctrl, chrgmbr, lsrg, mkrg, rmrg, rmrgmbr commands.
The Resource_Data_Input file.
The rmccli general information file.
chrgmbr
Name
chrgmbr - Changes the persistent attribute value(s) of a managed resource in a resource group.
Synopsis
chrgmbr [-h] [-i] [-c New_group] [-m T | F] [-T] [-V] -g Resource_group [-p A |O]
chrgmbr [-h] [-i] -s [ -c New_group] [-m T | F] [-T] [-V] [-g Resource_group] [-p A |O[,Failback]"selection_string"
chrgmbr [-h] [-i] [-c New_group] [-m T | F ] [-T] [-V] -s [-g Resource_group] [-p A |O[,Failback]Resource_class:"selection_string" [Resource_class:"selection_string" [...]]
chrgmbr [-h] [-i] [-c New_group] [-m T | F ] [-T] [-V] [-g Resource_group] [-p A |O[,Failback]Resource_class:Resource_name[:Node][,Resource_name[:Node][,...]][Resource_class:Resource_name[:Node][,Resource_name[:Node][,...]] [... ]]
chrgmbr [-r 0 | AutomaticRecovery | 1 | LockOnResFailure | 2 | LockOnAnyFailure]
Description
The chrgmbr command changes the attributes of the specified member resources. When the selectionstring is the only parameter, then it is applied directly to IBM.ManagedResource class. Otherwise, aresource name or selection string must be specified with the class to which it belongs. This commandallows the user to specify changes to the Mandatory attribute of a managed resource by using the -moption and also allows the user to change the resource group to which the resource belongs by using the-c option. A fixed resource must include the resource class and the node name at which it resides. Theresource class and resource name, the resource name and the node must be separated by a colon.
Options
-c New_groupSpecifies a new resource group name, which changes the MemberOf attribute of the managedresource. This option specifies the Resource_group, or changes the Resource_group of which thismanaged resource is a member, to the New_group.
-g Resource_groupSpecifies the name of the resource group of which the resources are members. This represents theMemberOf attribute of the Managed Resource.
-hWrites the command's usage statement to standard output.
48 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
-iInteractive. Prompt before changing resource groups.
-m T | FSpecifies whether this managed resource is required in the resource group.T
TRUE. These managed resources are required by the resource group.F
FALSE. These managed resources are not required by the resource group.-p A|O[,Failback]
Specifies the method to be used when selecting a node for placing the resource on. The value can be:A
Any.O
Ordered. This is the default.Failback
Optional. Occurrence as comma separated value. In combination with O (Ordered) only.-s
Specifies that a selection string will be used.-T
Writes the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
-r 0 | AutomaticRecovery | 1 | LockOnResFailure | 2 | LockOnAnyFailureSpecifies the RecoveryPolicy attribute that defines how the group member is recovered from a failure.The value can be:0 | AutomaticRecovery
Automatically recover from the failure. This is the default.1 | LockOnResFailure
Process a lock request on the resource group if the member fails. Automatically recover themember if the node hosting the member fails.
2 | LockOnAnyFailureProcess a lock request on the resource group if the member or the hosting node fails.
Parameters
Resource_classSpecifies the name of the resource class to which the member resource belongs. The resource andthe resource class must be separated by the colon (:) delimiter. Also the selection_string and itsresource_class must be separated by the colon (:) delimiter.
Resource_class:"selection_string"The -s option determines this operand. Each selection string must be preceded by a resource class.Resource_class indicates the name of the resource class the selection_string will be applied to. Theselection_string and it's Resource_class must be separated by the colon (:) delimiter. The specifiedselection string will be applied to its corresponding Resource_class attributes to determine whichmember resources are to be changed. The selection string must be enclosed within double or singlequotation marks. If the selection string contains double quotation marks, enclose the entire selectionstring in single quotation marks. For example:
-s 'Name == "testing"'-s 'Name ?= "test"'-s 'Name like "%"' ( For all resources)
Chapter 2. Reference 49
Resource_class:Resource_name[:Node]This specifies one or more member resources that are to be changed. Resources belonging todifferent resource classes can also be specified using this syntax. However, member resourcesbelonging to different classes must be separated by spaces. A member resource is identified by theresource's class ( Resource_class), the resource's name (Resource_name), and optionally the node( Node) the resource is on. The Resource_class, Resource_name, and Node must be separated by acolon.
Resource_class is the name of the resource class the member resource belongs to. Resource_name isthe name of the actual member resource in its class. Node is the name of the node the resource islocated on. The Node is required when attempting to change a fixed member resource. The Node andits resource must be separated by the colon delimiter (:). Multiple resources belonging to the sameresource class can also be specified and are separated by a comma. In this case the first resource orResource_name[:Node] of a resource class must be preceded by the Resource_class it belongs to andit must be separated by the colon delimiter (:), while the remaining resources are separated by acomma.
Resource_class:Resource_name[:Node][Resource_name[:Node][,...]]The member resources must exist in the resource group for it to be changed.
Selection_stringSpecifies the selection string. The -s option determines this parameter. When this is the onlyparameter, then the selection string is applied to the member resources. But when included withResource_class, each selection string in this case will be applied to its corresponding Resource_classattributes to determine which resources are to be modified in the Resource_group. TheSelection_string and its Resource_class must be separated by the colon (:) delimiter. The selectionstring must be enclosed within either double or single quotation marks. If the selection string containsdouble quotation marks, enclose the entire selection string in single quotation marks. For example:
-s 'Name == "testing"'
-s 'Name ?= "test"'
-s 'Name like "%"' ( For all resources)
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
7Resource already exists.
50 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
1. To change the mandatory attribute to TRUE of a member resource tester that belongs to resourceclass IBM.Application, enter:
chrgmbr -m T IBM.Application:tester
2. To change the resource group to which member resources testerA, testerB, and testerC ofresource class IBM.Application belong from the current resource group resA to resource groupresAtest, enter:
chrgmbr -c resAtest -g resA IBM.Application:testerA,testerB,testerC
3. To change the Mandatory attribute to FALSE of selected member resources of resource group resAwith ResourceType attribute set to one, belonging to resource class IBM.Application, enter:
chrgmbr -m F -s -g resA IBM.Application:"ResourceType==1"
Files
/usr/sbin/rsct/bin/chrgmbrLocation of the chrgmbr command.
See Also
The addrgmbr, samctrl, chrel, chrg, lsrg, mkrel, mkrg, mkrg, rmrel, rmrgmbr commands.
The rmccli general information file.
installSAM
Name
installSAM - Checks that all installation or upgrade prerequisites are met and installs or upgradesSystem Automation for Multiplatforms, including the end-to-end automation adapter.
Synopsis
installSAM [--noliccheck] [--nonls] [--noupgrade] [-d inst_pkg_dir] [-l log_file] [-n language][--silent]
Description
The installSAM command first invokes the prereqSAM command, which checks that all prerequisitesfor the installation or upgrade of System Automation for Multiplatforms are met. If the system passes thecheck, installSAM verifies that the license file is available and installs or upgrades the product,including the end-to-end automation management adapter. Information about the actions that areperformed during both the prerequisites check and the installation are recorded in a log file. The defaultlog file is /tmp/installSAM.<#>.log, where <#> is a sequential number; the highest numberidentifies the most recent log file.
Typically, no options need to be specified. The available options allow you to install or upgrade theproduct although no license file is available (--noliccheck), to prevent an upgrade (--noupgrade), toinstall the product although the installSAM script is not in the package directory (-d), and to specifythat a log file other than /tmp/installSAM.<#>.log is to be used (-l).
Chapter 2. Reference 51
The installSAM command is not applicable to System Automation for Multiplatforms on Windows. Forinstructions on installing and upgrading System Automation for Multiplatforms on Windows, see SystemAutomation for Multiplatforms Installation and Configuration Guide.
Options
--noliccheckAllows you to install or upgrade IBM Tivoli System Automation although no license file is available.This option is used by products which bundle System Automation for Multiplatforms and install thelicense separately. Note that System Automation for Multiplatforms can not be used if no license isinstalled. If you specify the option, the fact is recorded in the log file.
--nonlsInstalls packages with English language support only. All messages are displayed in English. If thisoption is specified, option -n must not be specified.
--noupgradePrevents an upgrade of System Automation for Multiplatforms although an upgrade is required. Youcan use this option, for example, if only an initial installation is desired or to find out whether anupgrade would occur if the option were not specified.
-d inst_pkg_dirAllows the installation of packages from the specified directory although the installSAM script isnot available in the directory. This option is used by products which bundle System Automation forMultiplatforms.
-l log_fileLogs information generated by the installSAM command to the specified log file.
-n languageInstalls all available packages to support the specified language in addition to English. As aprerequisite, language-independent packages with the same version and release must already havebeen installed. To install more than one language, the installation must be repeated for each languagein turn. If this option is specified, option --nonls must not be specified. Valid values for language areas follows:BR
Portuguese (Brazil)DE
GermanES
SpanishFR
FrenchIT
ItalianJP
JapaneseKR
KoreanCN
Simplified ChineseTW
Traditional Chinese--silent
Suppresses output to the command line and prompts such as acceptance of license agreements.
52 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Exit Status
These are the return codes returned by the installSAM command during the license check andinstallation. For information about the return codes returned during the prerequisites check, refer to theman page for the prereqSAM command.0
The installation or upgrade completed successfully.1
<package installer> returned a return code other than 0; the return code and the correspondingmessage can be found in the log file. Package installer is:
• AIX: installp• Linux: rpm
2Package sam is already installed at the same version.
3Package sam is already installed at a higher version.
4Option --noupgrade was specified and package sam was found installed at a lower version than thepackage version. No upgrade was performed.
5The node on which the installation task must be performed is online in a System Automation forMultiplatforms cluster. The task was not performed.
6The license file for System Automation for Multiplatforms was not found, or no installed license couldbe detected, or the installation of the license failed.
7installSAM was unable to continue because directories or files could not be detected or otherconditions are not met.
8The specified language is not supported. This error code may only be returned if option -n was used.
Security
This command requires root authority.
lsequ
Name
lsequ - Lists already-defined resource equivalencies and their attributes.
Synopsis
lsequ [-h] [-s "selection_string"] [-e Equivalency] [-A p | d | b] [-l | -t | -d | -D Delimiter] [-T] [-V] [Attr...]
Description
The lsequ command lists the Equivalencies. If the equivalency name is omitted, all of the definedequivalencies are listed. If an equivalency is specified, the persistent attributes of the specifiedequivalency is listed. If the Attr operand is specified, the attributes that are specified for the equivalencyis listed.
If the attribute flag is specified, the persistent, or dynamic, or both attributes of the equivalencies arelisted. If specified, the Attr operand overrides the -A option. The Attr operand must be a valid equivalency
Chapter 2. Reference 53
attribute, when listing equivalency information. When the Attr operands are specified, the exact value ofthese attributes are listed. Otherwise, some of these attribute values are translated into English words.
Options
-A p | d | bAttribute type. By default, only persistent attributes are displayed. To view all the attributes of themember resources, this option must be used with -A b attribute type. The value can be:p
Display only persistent attributes. For best performance, specify this value.d
Display only dynamic attributes.b
Display both persistent and dynamic attributes.-d
Specifies delimiter-formatted output. The default delimiter is a colon (:). Use the -D option if you wantto change the default delimiter.
-D DelimiterSpecifies delimiter-formatted output that uses the specified delimiter. Use this option to specifysomething other than the default colon (:); for example, when the data to be displayed containscolons. Use this option to specify a delimiter of one or more characters.
-e EquivalencyThe name of the defined Equivalency to be listed.
-hWrites the command's usage statement to standard output.
-lSpecifies long formatted output. Each attribute is displayed on a separate line, which is the defaultdisplay format.
-s "Selection_string"Specifies a selection string. Used without the -e option, this option is applied to all the definedequivalencies. If the -e option is specified with a selection string, then this selection is applied only tothe specified equivalency. If the selection string contains double quotation marks, enclose the entireselection string in single quotation marks. For example:
-s 'Name == "testing"'
-s 'Name ?= "test"'
Only persistent attributes can be included in a selection string.
-tSpecifies tabular formatted output. Each attribute is displayed in a separate column, one resource perline.
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
ParametersAttr
Specifies the names of one or more attributes whose values are to be displayed. These attributesmust be separated by spaces.
54 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect option on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
1. To list all currently defined equivalencies, enter:
lsequ
Output:
Displaying Equivalency Information:resAresBequ1equ2
2. To list the persistent attributes of the equivalency resA, enter:
lsequ -A p -e resA
Output:
Displaying Equivalency Information:Persistent Attributesfor Equivalency "resA".
Equivalency 1: Name = resA MemberClass = IBM.Application Resource:Node[Membership] = {resource1-name:node-name, resource2-name:node-name,…} SelectString = "" SelectFromPolicy = ORDERED MinimumNecessary = 1 Subscription = {} ActivePeerDomain = domain-name
3. To list all the attributes of the equivalency equ1, enter:
lsequ -A b -e equ1
Chapter 2. Reference 55
Output:
Displaying Equivalency Information:All AttributesFor Equivalency "equ1".
Equivalency 1: Name = equ1 MemberClass = IBM.Application Resource:Node[Membership] = {resource1-name:node-name, resource2-name:node-name,…} SelectString = "" SelectFromPolicy = ORDERED MinimumNecessary = 1 Subscription = {} ActivePeerDomain = domain-name Resource:Node[ValidSelectResources] = {resource1-name:node-name, resource2-name:node-name,…} Resource:Node[InvalidResources] = {} ConfigValidity = AutomationDetails[CompoundState] = Automation
4. To list all the attributes of the equivalency equ1 in verbose mode, enter:
lsequ -V -A b -e equ1
Output:
Starting to list equivalency information.lsequ: Executed on Thu May 8 14:42:32 2008 at "node-name", master node "node-name".
Displaying Equivalency information:All AttributesFor Equivalency "equ1".
Equivalency 1: Name = equ1 MemberClass = IBM.Application Resource:Node[Membership] = {resource1-name:node-name, resource2-name:node-name,…} SelectString = "" SelectFromPolicy = ORDERED MinimumNecessary = 1 Subscription = {} ActivePeerDomain = domain-name Resource:Node[ValidSelectResources] = {resource1-name:node-name, resource2-name:node-name,…} Resource:Node[InvalidResources] = {} ConfigValidity = AutomationDetails[CompoundState] = Automation [DesiredState] = Undefined [ObservedState] = Unknown [BindingState] = Unbound [AutomationState] = Unknown [ControlState] = Undefined [HealthState] = Not ApplicableCompleted listing equivalency information.
5. To list the dynamic attributes of equivalency resA, enter:
lsequ -A d -e resA
Files
/usr/sbin/rsct/bin/lsequLocation of the lsequ command.
See Also
The chequ, samctrl, mkequ, rmequ commands.
The rmccli general information file.
56 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
lsrel
Name
lsrel - Lists an already-defined managed relationship and its attributes.
Synopsis
lsrel [-h] [-s "selection_string"] [-A p | d | b] [-l | -t | -d | -D Delimiter] [-T] [-V] [Attr...]
lsrel [-h] [-M relation_name] [-A p | d | b] [-l | -t | -d | -D Delimiter] [-T] [-V] [Attr...]
lsrel [-h] [-S Source_Class[:Resource_name[:Node]] [-s "Source_string"] [-GTarget_Class[:Resource_name[:Node][,Target class[:Resource_name[:Node][,…]]]] [-g "Target_string"] [-PCurrent_relationship] [-O Current_condition] [-A p | d | b] [-l | -t | -d | -D Delimiter] [-T] [-V][Attr...]
Description
The lsrel command lists the managed relationships. If the relationship name is omitted, all managedrelationships are listed. If the resource relationship is specified, the persistent attributes of the specifiedrelationship is listed. If the Attr parameter is specified, the attributes that are specified for therelationship is listed.
If the attribute option is specified, the persistent or dynamic attributes of the relationships are listed. Ifspecified, the Attr parameter overrides the -A option. The Attr parameter must be a valid relationshipattribute when listing relationship information. If the Attr parameters are specified, the exact value ofthese attributes are listed. Otherwise, some of these attribute values are translated to English words.
Options
-A p | d | bSpecifies an attribute type. By default, only persistent attributes are displayed. This option can beused only when no attribute names are specified on the command line. To view all the persistentattributes of the member resources, the option must be used with -p attribute type.p
Displays only persistent attributes.d
Displays only dynamic attributes.b
Displays both persistent and dynamic attributes.For best performance, specify the -A p option.
-dSpecifies delimiter-formatted output. The default delimiter is a colon (:). Use the -D option if you wantto change the default delimiter.
-D DelimiterSpecifies delimiter-formatted output that uses the specified delimiter. Use this option to specifysomething other than the default colon (:); for example, when the data to be displayed containscolons. Use this option to specify a delimiter of one or more characters.
-g Target_stringThe Target_string is applied to all resources of the resource class that is specified by the -G option, todetermine the targets of the relationship.
If the -g option is used to specify a source selection string, Resource_name and Node must not bespecified for the -G option.
Chapter 2. Reference 57
-G Target_class[:Resource_name[:Node]]
Specifies the target resources to display with the relationship. The target resource or resources areused with the source and any other specified query to find a match from all of the definedrelationships. A target resource is identified by the resource's class (Target_class), the resource name(Resource_name), and, optionally, the node (Node) at which the resource is located. Target_class,Resource_name, and Node must be separated by colons. Multiple target resources can be specifiedand are separated by commas. The colons are required, but omitting Target_class causes thepreviously specified class to be used when multiple target resources are specified.
If the -g option is used to specify a target selection string, Resource_name and Node must not bespecified for the -G option.
-hWrites the command's usage statement to standard output.
-lSpecifies long formatted output. Each attribute is displayed on a separate line, which is the defaultdisplay format.
-M relation_nameSpecifies the name of the managed relationship to be listed.
-P Current_relationshipSpecifies the managed relationship value that is used to query all the defined relationships to find amatch. The value can be a numeric value or the word (not case-sensitive):0x0001 or Collocated
Specifies that the source and the target resources are on the same node.0x0002 or AntiCollocated
Specifies that the source and the target resources are on different nodes.0x0003 or Affinity
Specifies that the source resource and its specified affinity resource are on the same node, ifpossible.
0x0004 or AntiAffinitySpecifies that the source resource and its specified affinity resource are on different nodes, ifpossible.
0x0005 or IsStartableSpecifies that the source and its target resources are startable.
0x0006 or StartAfterSpecifies that the source is to be started after the target resources.
0x0007 or DependsOnSpecifies that the target resources must be online before the source resource is started andincludes an implicit collocation between the source and target resources.
0x0008 or DependsOnAnySpecifies that the target must be online before the source resource is started. It is identical to theDependsOn relationship except that it does not provide the collocated constraint for the startsequence. Therefore, the source and target resources cannot be started on the same node.
0x0009 or StopAfterSpecifies that the source resource cannot be stopped until after the target resource is offline.
0x000A or ForcedDownBySpecifies that the source resource must be forced offline if either the target resource goes offlineunexpectedly or the target resource itself is forced offline.
-O Current_conditionIf condition query. Specifies the condition value to query all the defined relationships to find a match.The value can be the numeric value or the word (not case-sensitive):0x0000 or NoCondition
Specifies unconditional location relationship.
58 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
0x0001 or IfOnlineSpecifies that the target resource is online.
0x0002 or IfOfflineSpecifies that the target resource is offline, failed offline, or unknown.
0x0003 or IfNotOnlineSpecifies that the target resource is not online.
0x0004 or IfNotOfflineSpecifies that the target resource is not offline or failed offline.
0x0005 or IfPossibleUsed with the StartAfter relationship. Specifies that the target resource group can be bypassed ifit cannot be bound, in which case it ends up in Sacrificed state and the StartAfter relationship isignored.
-s "selection_string"Specifies a selection string. This option without the -S option is applied to all the definedrelationships and its attribute fields. All selection strings must be enclosed within either double orsingle quotation marks. If the selection string contains double quotation marks, enclose the entireselection string in single quotation marks. For example:
-s 'Name == "testing"'
-s 'Name ?= "test"'
Only persistent attributes can be listed in a selection string.
-s Source_string
Specifies the source selection string of the relationship to list. The Source_string is applied to allresources of the resource class that is specified by the -S option to determine the source of therelationship. The result of the selection may contain one or more resources.
If the -s option is used to specify a source selection string, Resource_name and Node must not bespecified for the -S option.
-S Source_class[:Resource_name[:Node]]
Specifies the source resource of the relationship to list. A source resource is identified by the resourceclass (Resource_class) of the resource, the resource name (Resource_name), and, optionally, the node(Node) at which the resource is located. The result of the selection can contain one or more resources.
If the -s option is used to specify a source selection string, Resource_name and Node must not bespecified for the -S option.
-tSpecifies tabular formatted output. Each attribute is displayed in a separate column, one resource perline.
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
Parameters
AttrSpecifies the names of one or more attributes whose values are to be displayed. These attributesmust be separated by spaces. When the -m option is specified, these attributes must match themember resource attribute fields; when the -m option is not specified, the attributes must match theresource group attribute fields.
Chapter 2. Reference 59
NodeSpecifies the node name. The node name must be included when an attempt is made to list a fixedmember resource. The node and its resource must be separated by the colon (:).
Resource_classSpecifies the name of the resource class to which the member resource belongs. The resource andthe resource class must be separated by spaces.
Resource_nameSpecifies the resource name. One or more resources can be specified along with the resource class towhich it belongs. Each resource or set of resources must be preceded by its resource class. Theresource and the resource class must be separated by spaces.
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
1. To list all the currently defined managed relationships, enter:
lsrel
Output:
Displaying Managed Relations :Name Resource:Node[Source] ResourceGroup[Source]resA IBM.Application:ja ResAjaffinity IBM.Application:ja ResA IBM.ResourceGroup:john Ja
2. To list the persistent attributes of the managed relationship resA, enter:
lsrel -A p -M resA
Output:
Displaying Managed Relationship Information:Persistent Attributesfor Managed Relationship "resA".
Managed Relationship 1: Class:Resource:Node[Source] = IBM.Application:ja:nodename Class:Resource:Node[Target] = {IBM.Application:Nate:Nodename}
60 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Relationship = Collocated Conditional = NoCondition Name = resA
3. To list the managed relationship that matches the source resA from class IBM.Application, havinga Collocated relationship value with target resource narten from class IBM.ResourceGroup, enter:
lsrel -S IBM.Application:ResA -P Collocated -G IBM.ResourceGroup:narten
Output:
Displaying Managed Relationship Information:Managed Relationship 1:Name = ResAClass:Resource:Node[Source] = IBM.Application:ResAClass:Resource:Node[Target] = {IBM.ResourceGroup:Narten ,IBM.Application:ja}Relationship = CollocatedConditional = NoConditionResourceGroup[Source] = charm
4. To list the dynamic attributes of the managed relationship name resA, enter:
lsrel -A d -M resA
5. To list the persistent attributes of the managed relationship name resA by using a selection string,enter:
lsrel -A p -s 'Name == "resA"'
Files
/usr/sbin/rsct/bin/lsrelLocation of the lsrel command.
See Also
The addrgmbr, samctrl, chrg, chrgmbr, mkrg, rmrg, rmrgmbr commands.
The rmccli general information file.
lsrg
Name
lsrg - Lists already-defined resource groups and their members.
Synopsis
lsrg [-h] [ -m] [ -s "Selection_string"] [-A p | d | b] [-l | -t | -d | -D Delimiter][-g Resource_group] [-T] [-V] [ [Attr...]
lsrg [-h] [ -m] -c [ -s "Selection_string"] [-A p | d | b] [-l | -t | -d | -D Delimiter] [-gResource_group] [-T] [-V] Resource_class:Resource[:Node][,Resource[:Node][,...]][Resource_class:Resource[:Node][,Resource [:Node][,...]] [... ]]
Description
The lsrg command lists resource groups or the members of a resource group. If the resource groupname is omitted, all of the resource groups are listed. If the resource group name is specified without the-m option the persistent attributes of the specified group will be listed. If the Attr parameter is specified,then the attributes specified for the resource group are listed. If the Attr parameter is specified here, theattributes specified for the resource group will be listed.
Chapter 2. Reference 61
If the resource group name is specified with the -m option, the members of that resource group will belisted. If the attribute option (-A) is specified, the persistent or dynamic attributes of the resource groupmembers will be listed. By default, the -m option lists the following attributes for the members of aresource group: Resource class name, Resource name, and the attributes MemberOf, OpState,WinSource, and Location. If the Attr operand is specified, then the attributes specified will be listed for themanaged resources (member resources).
The Attr parameter if specified will override the -A option. The Attr parameter must be a valid resourcegroup attribute when listing resource group information, and likewise be a valid member resourceattribute when listing a managed resource. If the Attr parameters are specified, then the exact value ofthese attributes will be listed. Otherwise, some of these attribute values are translated into Englishwords.
Options
-A p | d | bSpecifies an attribute type. By default, only persistent attributes are displayed. This option can beused only when no attribute names are specified on the command line. To view all the persistentattributes of the member resources, this option must be used with p attribute type.p
Displays only persistent attributes.d
Displays only dynamic attributes.b
Displays both persistent and dynamic attributes.For best performance, specify the -A p option.
-cSpecifies the resource and its class. This option indicates that parameters are resource classes,resource names, and, optionally, node names. The attributes of the member resources are listed ordisplayed. The attributes and selection strings when this option is used are applied to memberresources and not the resource groups; therefore, these attributes must exist for the memberresources.
-dSpecifies delimiter-formatted output. The default delimiter is a colon (:). Use the -D option if you wantto change the default delimiter.
-D DelimiterSpecifies delimiter-formatted output that uses the specified delimiter. Use this option to specifysomething other than the default colon (:); for example, when the data to be displayed containscolons. Use this option to specify a delimiter of one or more characters.
-g Resource_groupDisplays resource group information such as the name and the persistent and dynamic attributes ofthe defined resource group . When the -g option is used with the -m and -c options, the memberresources must belong to the specified resource group.
-hWrites the command's usage statement to standard output.
-lSpecifies long formatted output. Each attribute is displayed on a separate line. This is the defaultdisplay format.
-mSpecifies member resources and lists or displays the attributes of the member resources. When thisoption is used, th attributes and selection strings are applied to member resources and not toresource groups; therefore, the attribute fields must exist for the member resources.
62 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
-s "Selection_string"Specifies a selection string. This option without the -m option is applied to the resource-groupattribute fields; with the -m option or -c option, the selection string is applied to the member-resource attribute fields. All selection strings must be enclosed within either double or singlequotation marks. If the selection string contains double quotation marks, enclose the entire selectionstring in single quotation marks. For example:
-s 'Name == "testing"'
-s 'Name ?= "test"'
-tSpecifies tabular formatted output. Each attribute is displayed in a separate column, one resource perline.
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
Parameters
AttrSpecifies the names of one or more attributes whose values are to be displayed. These attributesmust be separated by spaces. When the -m option is specified, these attributes must match themember resource attribute fields; when the -m option is not specified, the attributes must match theresource group attribute fields.
NodeSpecifies the node name. The node name may have to be included when an attempt has been made tolist a fixed member resource. The node and its resource must be separated by the colon (:) delimiter.
Resource_classSpecifies the name of the resource class to which the member resource belongs. The resource andthe resource class must be separated by the colon (:) delimiter.
Resource_nameSpecifies the resource name. One or more resources may be specified along with the resource classto which it belongs. Each resource or set of resources must be preceded by its resource class. Theresource and the resource class must be separated by the colon (:) delimiter.
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
Chapter 2. Reference 63
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
1. To list all the currently-defined resource groups, enter:
lsrg
Output:
Resource Group Names:
resA clusterresA
2. To list all the attributes of the resource group resA, enter:
lsrg -A b -g resA
Output:
Displaying Resource Group Information:All Attributes For Resource Group "resA". Resource Group 1: Name = "resA" MemberLocation = Collocated Priority = 22 AllowedNodes = "node1" NominalState = Online OpState = Offline TopGroup = resA AutomationDetails[CompoundState] = Automation
3. To list all the attributes of the resource group resA in verbose mode, enter:
lsrg -A b -V -g resA
Output:
Starting to list resource group information.lsrg: Executed on Mon Apr 3 15:48:49 2006 at "node1", master node "node1".Displaying Resource Group information:All AttributesFor Resource Group "resA".
Resource Group 1: Name = "resA" MemberLocation = Collocated Priority = 22 AllowedNodes = "node1" NominalState = Online OpState = Offline TopGroup = resA AutomationDetails[CompoundState] = Automation [DesiredState] = Online [ObservedState] = Pending Online [BindingState] = Bound [AutomationState] = Internal [ControlState] = Startable [HealthState] = Not ApplicableCompleted listing resource group information.
4. To list the attributes of the members of resource group resA, enter:
lsrg -m -V -Ab -g resA
64 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Output:
Starting to list member resource information.lsrg: Executed on Mon Apr 3 15:48:49 2006 at "node1", master node "node1".Displaying Member Resource information:for Resource Group "resA".Member Resource 1:Resource:Node [ManagedResource] = IBM.Application:charmMandatory = FalseMemberOf = resAWinSource = NominalLocation = node1AutomationDetails = [10,1,100,2,80,1,0]AutomationDetails[CompoundState] = Automation [DesiredState] = Online [ObservedState] = Pending Online [BindingState] = Bound [AutomationState] = Internal [ControlState] = Startable [HealthState] = Not ApplicableCompleted listing member resource information.
5. To list the persistent attributes of the member resources of resource group resA, enter:
lsrg -m -A p -g resA
Output:
Displaying Member Resource information:for Resource Group "resA".Member Resource 1: Resource:Node[ManagedResource] = IBM.Application:charm Mandatory = False MemberOf = resA
6. To list the persistent attributes of the member resources of a resource group resA using a selectionstring, enter:
lsrg -m -A p -s 'MemberOf == "resA"'
Output:
Displaying Member Resource information:for Resource Group "resA".Member Resource 1: Resource:Node[ManagedResource] = IBM.Application:charm Mandatory = False MemberOf = resA
7. To list the attributes of a managed resource, enter:
lsrg -m
Output:
Displaying Member Resource information:Class:Resource:Node[ManagedResource]Mandatory MemberOf OpState WinSource LocationIBM.Application:WebServer True DemoRG Online Nominal node1 IBM.ServiceIP:WebIP True DemoRG Online Nominal node1
Files
/usr/sbin/rsct/bin/lsrgLocation of the lsrg command.
See Also
The addrgmbr, samctrl, chrel, chrg, chrgmbr, mkrel, mkrg, rmrel, rmrg, rmrgmbr commands.
Chapter 2. Reference 65
The rmccli general information file.
lsrgreq
Name
lsrgreq - Lists the outstanding requests that are applied against the resource groups or managedresources.
The lsrgreq command belongs to a group of commands (rgreq, rgmbrreq, and lsrgreq) which allowan operator to introduce persistent requests into System Automation for Multiplatforms Administrator'sand User's Guide. Using this set of commands the operator can start, stop, cancel, or move resourcegroups and managed resources.
Synopsis
lsrgreq [-h] [-L] [-m] [-l | -t |-d |-D Delimiter] [-g Resource_ group] [-T] [-V]
lsrgreq [-h] [-L] -m [-l |-t |-d |-D Delimiter] [-T] [-V] [-L]Resource_class:Resource[:Node][,Resource[:Node][,...]][Resource_class:Resource[:Node][,Resource[:Node][,...]]]
lsrgreq [-h] [-L] -m [-l |-t |-d |-D Delimiter] -s [-T] [-V] Resource_class:"Selection_String"[Resource_class:"Selection_String" [...]]
Description
The lsrgreq command lists the outstanding requests that are applied against the resource groups ormanaged resources. By using the lsrgreq command, either the active or all the outstanding requestscan be listed. The -m option lists only the action requests on the managed or member resources.Otherwise, the action requests on the resource groups are listed.-h
Help. Writes the command's usage statement to standard output.-g Resource_group
The name of the resource group whose actions are to be listed.-L
Lists all the action requests on the specified resource group or managed resources. If this option isnot specified, then only the active requests are displayed or listed.
-mMember Resources. Lists or displays the actions on the member resources.
-sSpecifies that a selection string is used.
-lLong formatted output. Each attribute is displayed on a separate line, which is the default displayformat.
-tTabular formatted output. Each attribute is displayed on a separate column, one resource per line.
-dSpecifies delimiter-formatted output. The default delimiter is a colon (:). Use the -D option if you wantto change the default delimiter.
-D DelimiterSpecifies delimiter-formatted output that uses the specified delimiter. Use this option to specifysomething other than the default colon (:); for example, when the data to be displayed containscolons. Use this option to specify a delimiter of one or more characters.
-TTrace. Writes the command's trace messages to standard error. For software-service organization'suse only.
66 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
-VVerbose. Writes the command's verbose messages to standard output.
Parameters
Resource_class:"selection_string"The -s option determines this operand. Each selection string must be preceded by a resource class.Resource_class indicates the name of the resource class the selection_string is applied to. Theselection_string and its Resource_class must be separated by colon or ":"delimiter. The specifiedselection string is applied to its corresponding Resource_class attributes to determine which memberresources are to be removed from the Resource_group. The selection string must be enclosed withindouble or single quotation marks. If the selection string contains double quotation marks, enclose theentire selection string in single quotation marks. For example:
• -s IBM.Application:`Name=="testing"`• -s IBM.Application:`Name ?="test"`• -s IBM.Application:`Name like "%"` (For all resources)
Resource_class:Resource[:Node]The member resources specifies one or more member resources whose action requests are to belisted. Resources belonging to different resource classes can also be specified by using this syntax.However, member resources that belong to different classes must be separated by spaces. A memberresource is identified by the Resource_class, Resource), and optionally the Node the resource ison. The Resource_class, Resource, and Node must be separated by a colon. Node is the name ofthe resource class the member resource belongs to. Node is the name of the actual member resourcein its class. The node can be included when trying to act on a fixed member resource. The node and itsresource must be separated by the colon or ":" delimiter. Multiple resources that belong to the sameresource class can also be specified and are separated by a comma:Resource_class:Resource[:Node][,Resource[:Node][,...]] The member resources must exist in the resource group for the requestedaction to take place.
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Chapter 2. Reference 67
Examples
1. To list the active action requests on the resource group RG1, enter:
lsrgreq -g RG1
2. To list the requests for the resource group top-rg, enter:
lsrgreq -L -g top-rg
Output:
Resource Group 1: ResourceGroup = top-rg Priority = High Action = lock Source = Operator NodeList = {} ActiveStatus = Inactive Token = 8f5697eb5f84c0f044995b3d00040a5b UserID = MoveStatus = None
3. To list the requests on all the resources that belong to resource group RG1 in tabular format, enter:
lsrgreq -m -g RG1
Output:
Displaying Member Resource request information:Active RequestsFor Resource Group "RG1": Member Resource 1: Class:Resource:Node[ManagedResource] = IBM.Application:R1 Priority = Force Action = start Source = Operator ActiveStatus = Active
Member Resource 2: Class:Resource:Node[ManagedResource] = IBM.Application:R2 Priority = low Action = start Source = ExtSched ActiveStatus = Active
4. To list all the action requests applied to resource group RG1, enter:
lsrgreq -L -t -g RG1
Output:
Displaying Resource Group request information:All request informationFor Resource Group "RG1".ResourceGroup Priority Action Source NodeList ActiveStatus MoveStatusRG1 low stop ExtSched {} InActive NoneRG1 High start Automation {} InActive NoneRG1 Force stop Operator {} Active None
Files
/usr/sbin/rsct/bin/lsrgreqLocation of the lsrgreq command.
See Also
The addrgmbr, chrg, chrgmbr, lsrg, mkrg, rgreq, rmrg, and rmrgmbr commands.
68 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
lssam
Name
lssam - Lists the defined resource groups and their members in tree format.
Synopsis
lssam [-h|-top] [-g Resource_group] [-s "selection_string"] [-nocolor][-noequ][-nomsg][-V] [-T]
Description
The lssam command lists all resource groups and all resource group members in tree format. Someinformation is color-coded, for example the OpState of a resource that depends on the actual value. Thecolor code indicates whether there are any problems or not. As the color code is not configurable,consider to use a black or white background. If you use a different background color, use the option -nocolor to see all information reported by lssam.
Note: If you receive the following RSCT message, data is pending. One of the next queries will display thecomplete data:
2610-444 Cannot obtain values for some dynamic attributes. 0 attributes are not being monitored. 1 attributes have data pending.
Options
-hHelp. Writes the command's usage statement to standard output.
-g Resource_groupDisplays only the specified top-level resource group and its members in tree format.
-nocolorDisplays output without color-highlighting.
-s "selection_string"Specifies a selection string for the resource group. If the resource group is not a top-level resourcegroup, the selection string must contain the top-level resource group. All selection strings must beenclosed within either double or single quotation marks. If the selection string contains doublequotation marks, enclose the entire selection string in single quotation marks. For example:
-s 'Name == "testing"'-s 'Name ?= "test"'
If the resource group is not a top-level resource group, the selection string must contain thecorresponding top-level resource group. For example:
-s 'Name like "test" || Name like "top-level-rg" '
-topDisplays the output at the top of the screen and refreshes the output every second.
-noequPrint output without equivalencies.
-nomsgPrint output without error messages.
-VPrint resource details and relationships.
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
Chapter 2. Reference 69
Output
[ <OpState> "IBM.ResourceGroup:"<GroupName> ["Request="<RequestStateList>] ["Automation="<AutomationMode>] ["Control="<ControlState>] ["Binding="<BindingState>] "Nominal="<NominalState> [ "|-" <OpState> "IBM.ResourceGroup:"<GroupName> ["Request="<RequestStateList>] ["Automation="<AutomationMode>] ["Control="<ControlState>] ["Binding="<BindingState>] ["Opt="<RecoveryPolicy>] "Nominal="<NominalState> ]* [ "|-" <OpState> <ResourceClass>":"<FixedResourceName>":"<NodeName> ["Request="<RequestStateList>] ["Control="<ControlState>] ["Binding="<BindingState>] ["IP="<IPAddress>] ["MNT="<MountPoint>] ["TimeToStart="<TimeToStart> "TimeToStop="<TimeToStop>] ["Node="<NodeState>] ["Opt="<RecoveryPolicy>] ]* [ "|-" <OpState> <ResourceClass>":"<FloatingResourceName> ["Request="<RequestStateList>] ["Control="<ControlState>] ["Binding="<BindingState>] ["IP="<IPAddress>] ["MNT="<MountPoint>] ["TimeToStart="<TimeToStart> "TimeToStop="<TimeToStop>] ["Opt="<RecoveryPolicy>] [ "|-" <OpState> <ResourceClass>":"<ConstituentResourceName>":"<NodeName> ["Node="<NodeState>] ["Opt="<RecoveryPolicy>] ]+ ]*]*[ <OpState> "IBM.Equivalency:"<EquivalencyName> ["SelectFromPolicy="<SelectFromPolicyList>] [ "|-" <OpState> <ResourceClass>":"<FixedResourceName>":"<NodeName> ["Node="<NodeState>] ]+]*
Interpreting the output:
<OpState> - OpState of group/resource Color-coding scheme: "Unknown" - Blue "Offline" - Blue "Online" - Green "Failed offline" - Red "Stuck online" - Red "Pending online" - Yellow "Pending offline" - Yellow "Ineligible" - Yellow
<GroupName> - Name of the resource group<ResourceClass> - Name of the resource class <FixedResourceName> - Name of a fixed resource<FloatingResourceName> - Name of a floating resource<ConstituentResourceName> - Name of a constituent resource<NodeName> - Name of a node (short host name)
<RequestStateList> - If requests are present, one or more request states with source indicator are shown<RequestState>[":"<SourceIndicator>] [ "("<RequestState>":"<SourceIndicator>[","<RequestState>":"<SourceIndicator> ]+")" ]
<RequestState> - Request action Color-coding scheme: "Online" - Green if inactive, yellow if active "Offline" - Blue if inactive, yellow if active "Lock" - Red "Move" - Not color-coded if inactive, yellow if active
<SourceIndicator> - First letter of the request source: "O" - Operator (if operator request is first in list, this indicator is not shown) "A" - Automation
70 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
"E" - ExtSchedul "U" - Unknown
<AutomationState> - Automation attribute from lssamctrl (in red color) "Manual" - Automation disabled for this domain
<NodeState> - Some states of a node (in red color) "Offline" - Node is offline "Excluded" - Node is excluded (if a node is offline, "Excluded" is not shown)
<ControlState> - Some states of the AutomationDetails ControlState (in yellow color) "StartInhibited" - Start of dependent resource is not satisfactory (only displayed if OpState is Offline and DesiredState is Online) "StopInhibited" - Stop of dependent resource is not satisfactory (only displayed if OpState is Online and DesiredState is Offline) "SuspendedPropagated" - A lock request is propagated to this resource "StartInhibitedBecauseSuspended" - Start of dependent resource is not satisfactory and a lock request is propagated to this resource (only displayed if OpState is Offline and DesiredState is Online) "StopInhibitedBecauseSuspended" - Stop of dependent resource is not satisfactory and a lock request is propagated to this resource (only displayed if OpState is Online and DesiredState is Offline) "MemberInProblemState" - A constituent of the resource, a resource, or a resource group is in a problem state Problem state means that the resource is failed offline or not startable due to another reason. Identify and solve the problem of the resource and enter resetrsrc.
<BindingState> - Some states of the AutomationDetails BindingState (in red color) "Unbindable" - Configuration is incorrect "Sacrificed" - No system available to comply with configuration "Sacrificial" - No system available to comply with configuration
<NominalState> - Nominal State Color-coding scheme: Online - Green Offline - Blue
<EquivalencyName> - Name of the equivalencyThe following information is only displayed if the option -V is specified:
<IPAddress> - IP Address displayed only for class IBM.ServiceIP when option -V is used.<MountPoint> - Mount point displayed only for class IBM.AgFileSystem when option -V is used.<TimeToStart> - Time to start displayed only for class IBM.Test when option -V is used and TimeToStart or TimeToStop value does not equal to default 0 seconds.<TimeToStop> - Time to stop displayed only for class IBM.Test when option -V is used and TimeToStart or TimeToStop value does not equal to default 0 seconds.
<SelectFromPolicyList> - Specifies the policy to be used when making a selection from the Equivalency element.Only displayed when option -V is used.( "ANY" | "ORDERED" ) [ ",Failback" ] [ ",NoFailure" ] [ ",NoControl" ]"ANY" - The member selection has no specific order. This is the default which is not displayed if its the only option."ORDERED" - The member selection starts at the beginning."Failback" - The resources are always started on and will failback to the first member available in the ordered list. Only in combination with ORDERED."NoFailure" - The OpState of resources that have a dependency against the equivalency will not be forced to Failed Offline, if they could not be started within the specified timeout interval."NoControl" - System Automation will neither start nor stop the members of the equivalency but only react to changes of the OpState of these resources.
<RecoveryPolicy> - Specifies the policy which determines how a member failure is recovered. (“LockOnResFailure” | “LockOnAnyFailure”)“LockOnResFailure” - Submits a Lock request on the resource group if the member fails. Automatically recover the member if the node hosting the member fails.“LockOnAnyFailure” - Submits a Lock request on the resource group if the member or the hosting node fails.Note, that the attribute is not displayed if the default value “AutomaticRecovery” is set. In this case a failure is automatically recovered.
Sample: Online IBM.Equivalency:equ1 SelectFromPolicy=ORDERED,FailbackDescription: Equivalency equ1 is online and has the select from policy ORDERED and Failback.
Managed relationships between resources are displayed with arrows when option -V is used. The arrow is displayed on the right side behind the resource tree and starts on the source resource and points to the target resource.The relationship type is displayed with two a character shortcut on the arrow. The following list explains
Chapter 2. Reference 71
the two character shortcut for the relationship types.
"DO" - DependsOn - Specifies a combination of source StartAfter target, target StopAfter source, source ForcedDownBy target, source Collocated to target and target Collocated to source."DA" - DependsOnAny - Specifies a combination of source StartAfter target, target StopAfter source and source ForcedDownBy target."SA" - StartAfter - Specifies that the source resource is to be started after the target resource."SO" - StopAfter - Specifies that the source resource may not be stopped until after the target resource has been brought offline."FD" - ForcedDownBy - Specifies that the source resource must be forced offline in the event that either the target resource goes offline unexpectedly or the target resource itself is forced offline."CO" - Collocated - Specifies that the source resource is always located on the same node as the target resource."AC" - AntiCollocated - Specifies that the source resource is always located on a different node as the target resource."AF" - Affinity - Specifies that the source resource are to be located on the same node as its specified affinity resource if possible."AA" - AntiAffinity - Specifies that the source resource are to be located on a different node as its specified affinity resource if possible."IS" - IsStartable - Specifies that the source resource and its target resources are startable.
Sample:Online IBM.ResourceGroup:samadapter-rg Nominal=Online |- Online IBM.Application:samadapter -. |- Offline IBM.Application:samadapter:p550sa05 | '- Online IBM.Application:samadapter:p550sa06 DO '- Online IBM.ServiceIP:samadapter-ip IP=9.152.135.231 <' -. |- Offline IBM.ServiceIP:samadapter-ip:p550sa05 | '- Online IBM.ServiceIP:samadapter-ip:p550sa06 DOOnline IBM.Equivalency:samadapter-nieq <' |- Online IBM.NetworkInterface:eth0:p550sa06 '- Online IBM.NetworkInterface:eth0:p550sa05Description:Relationship: Source resource IBM.Application:samadapter DependsOn target resource IBM.ServiceIP:samadapter-ipRelationship: Source resource IBM.ServiceIP:samadapter-ip DependsOn target resource IBM.Equivalency:samadapter-nieqFloating resource: IBM.ServiceIP:samadapter-ip has the IP Address 9.152.135.231
Exit Status
0The command ran successfully.
1An error occurred.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
To list all resource groups and their members, type the following command:
lssam
Output:
Online IBM.ResourceGroup:grp1 Nominal=Online '- Offline IBM.Application:res1:node1Offline IBM.ResourceGroup:grp2 Nominal=Offline '- Offline IBM.Application:res2:node2Online IBM.ResourceGroup:grp3 Request=Online Nominal=Offline '- Online IBM.Application:res3 |- Online IBM.Application:res3:node1 '- Failed offline IBM.Application:res3:node2
72 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Files
/usr/sbin/rsct/bin/lssamLocation of the lssam command.
lssamctrl
Name
lssamctrl - Lists already defined System Automation for Multiplatforms control parameters and theirattributes.
Synopsis
lssamctrl [-h] [-A p | d | b] [-l | -t | -d | -D Delimiter] [-T] [-V] [Attr...]
Description
The lssamctrl command lists the control parameter values already set for System Automation forMultiplatforms. If the Attr operand is used, the value of each specified attribute is listed. If the attributeoption -A is specified, the persistent, or dynamic attribute, or both of System Automation forMultiplatforms are listed. The Attr operand, if specified, overrides the -A option. The Attr operand must bea valid attribute of IBM Tivoli System Automation Control Class. When Attr operands are specified, theexact value of each attribute is listed. Otherwise, some of these attribute values are translated to Englishwords.
Options
-hHelp. Writes the command's usage statement to standard output.
-A p | d | bAttribute type. By default only persistent attributes are displayed. To view all the persistent attributesof the member resources, this option must be used with p attribute type.
• p - Displays only persistent attributes.• d - Displays only dynamic attributes.• b - Displays both persistent and dynamic attributes.
For best performance, specify the -A p option.-l
Long formatted output. Each attribute is displayed on a separate line, which is the default displayformat.
-tTabular formatted output. Each attribute is displayed on a separate column, one resource per line.
-dSpecifies delimiter-formatted output. The default delimiter is a colon (:). Use the -D option if you wantto change the default delimiter.
-D DelimiterSpecifies delimiter-formatted output that uses the specified delimiter. Use this option to specifysomething other than the default colon (:); for example, when the data to be displayed containscolons. Use this option to specify a delimiter of one or more characters.
-TTrace. Writes the command's trace messages to standard error. For your software-serviceorganization's use only.
-VWrites the command's verbose messages to standard output.
Chapter 2. Reference 73
ParametersAttr
The name of the attributes whose values are to be displayed. These attributes must be separated byspaces.
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
To list all the currently defined System Automation for Multiplatforms parameters, type the followingcommand:
lssamctrl
Output:
Displaying IBM Tivoli System Automation Control Information:
SAMControl: TimeOut = 60 RetryCount = 3 Automation = Auto ExcludedNodes = {} ResourceRestartTimeOut = 5 ActiveVersion = [3.2.2.0,Mon Jun 2 10:36:54 2008] Enable Publisher = EEZ TraceLevel = 63 ActivePolicy = [] CleanupList = {} PublisherList = {}
Files
/usr/sbin/rsct/bin/lssamctrlLocation of the lssamctrl command.
See Also
The samctrl command.
The rmccli general information file.
74 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
mkequ
Name
mkequ - Makes a resource equivalency.
Synopsis
mkequ [-h] -f data_input_file [-T] [-V]
mkequ [-h] [-p A[,NoFailure | NoControl] | O[,Failback | NoFailure | NoControl]] [-m Minimum_Necessary] [-T] [-V] -S "Static_select_string" Equivalency Resource_class
mkequ [-h] [-p A[,NoFailure | NoControl]] [-m Minimum_Necessary] [-T] [-V] -D"Dynamic_select_string" Equivalency Resource_class
mkequ [-h] [-p A[,NoFailure | NoControl] | O[,Failback | NoFailure | NoControl]] [-m Minimum_Necessary] [-T] [-V] Equivalency Resource_class:Resource_name[:Node][,Resource_name[:Node][,...]]
Description
The mkequ command makes a resource equivalency among the specified resources. The resources mustall be from the same resource class.
Equivalencies and their attribute flags can be specified on the command line as the syntax indicates orfrom a file when the -f option is specified. The value must be of the same data type that is defined forthis resource attribute. Use the lsrsrcdef command to verify the data type and attribute field for eachattribute.
Explicit specification of resource names without selection string is not supported for IPv6–enabledIBM.NetworkInterface equivalency members.
Options
-D "dynamic_select_string"Dynamic Selection String. The specified selection string is saved as the SelectString attribute for theconcerned equivalency. This selection_string is then applied to all resources of the specified resourceclass by the Recovery Manager, to dynamically determine what members are to be included in thespecified equivalency. This option cannot be combined with the Resource_name [:Node] parameter.The selection string must be enclosed within double or single quotation marks. If the selection stringcontains double quotation marks, enclose the entire selection string in single quotation marks. Forexample:
-D 'Name == "testing"'
-D 'Name ?= "test"'
The -D option cannot be combined with the -S option or with an ORDERED SelectFromPolicy (-p O).
-f data-input_fileSpecifies the name of the file that contains equivalency attribute information.
-hWrites the command's usage statement to standard output.
-p A | O [,Failback | NoFailure | NoControl]Specifies the equivalency select-from policy. The value can be:A
Any, which is the default value.O
Ordered. The value cannot be used together with the -D option.
Chapter 2. Reference 75
Optional (comma-separated) values:ANY
The member selection has no specific order, which is the default value, that is not displayed if it isthe only option.
ORDEREDThe member selection starts at the beginning.
FailbackThe resources are always started on the first member, if it is available. Only in combination withORDERED.
NoFailureThe OpState of resources that have a dependency against the equivalency is not forced to FailedOffline, if they cannot be started within the specified timeout interval.
NoControlSystem Automation does not start or stop the members of the equivalency but react only tochanges of the OpState of these resources.
-S "static_select_string"Static Selection String. The specified selection string applies to the specified resource class, todetermine the resources that make up the equivalency. These resources are saved as theMemberShip attribute for the equivalency. This option cannot be combined with the Resource_name[:Node] parameter. The selection string must be enclosed within double or single quotation marks. Ifthe selection string contains double quotation marks, enclose the entire selection string in singlequotation marks. For example:
-S 'Name == "testing"'
-S 'Name ?= "test"'
-S cannot be combined with -D.-m Minimum-Necessary
Minimum Necessary Equivalency. Specifies the minimum necessary members to make an equivalencyvalid. The default value is 1.
-TWrites the trace messages of the command to standard error. For your software service organization'suse only.
-VWrites the verbose messages of the command to standard error.
ParametersEquivalency
Specifies the unique name of the new equivalency to be created. Equivalency names cannot containthe Dollar symbol ($).
Resource_class:Resource_name[:Node]
Specifies one or more resources that are members of the equivalency. All of the resources must befrom the same resource class. An equivalency resource is identified by the resource name(Resource_name), and, optionally, the node (Node) where the resource is located.
Resource names cannot contain the Dollar symbol ($). Resource_name and Node must be separatedby colons. Multiple resources can be specified and are separated by a comma. Resource_class is thename of the resource class the equivalency resource belongs to. The first resource orResource_name[:Node] must be preceded by the Resource_class it belongs to and it must beseparated by the colon (:) delimiter.
Since all resources must be from the same class, the Resource_class is to be specified only once asthe syntax indicates.
76 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
This syntax is not supported for IPv6–enabled IBM.NetworkInterface equivalency members: useselection string syntax instead.
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
7Resource already exists.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
1. To create an equivalency, use the data input file:
a. To generate a template to aid in the defining of these resources in a file, enter:
lsrsrcdef -i IBM.Equivalency >& /tmp/Equ.rdef
b. Edit the file /tmp/Equ.rdef with your preferred text editor: (Enter values for all of the attributes,substituting an appropriate value for the type, or leave it blank if you want the default value.)
c. Run the mkequ command with the file as follows:
mkequ -f /tmp/Equ.rdef
Sample Data Input file for mkequ:
You can enter values for all of the attributes and change the value shown, or remove the line with theattribute if you want the default value.
PersistentResourceAttributes::resource 1: Name = "Equiv" MemberClass = "IBM.NetworkInterface" Membership = "{'eth0:node-name','eth0:node-name'}"resource 2: Name = "Equiv2" MemberClass = "IBM.Application" Membership = "{'App1:node-name','App2:node-name','App3:node-name'}" SelectFromPolicy = "Any" MinimumNecessary = 2 resource 3: Name = "Equiv3" MemberClass = "IBM.Test" SelectString = "Name ?='Test'"
Chapter 2. Reference 77
SelectFromPolicy = "Any" MinimumNecessary = 1
2. To make an equivalency that is called resA with all the members of the resource classIBM.Application, enter:
mkequ -S 'Name like "%"' resA IBM.Application
3. To make an equivalency that is called resA with selected members testerA, testerB, and testerCof the resource class IBM.Application, and set its policy to ordered, enter:
mkequ -p O resA IBM.Application:testerA:node-name,testerB:node-name,testerC:node-name
Node name needs to be indicated because all resources for making the equivalency must be fixed.4. To make an equivalency that is called testerB with selected members of the resource classIBM.Application by using a static select string, enter:
mkequ -S "ResourceType==0" testerB IBM.Application
5. To make an equivalency that is called Jfoo with selected members of the resource classIBM.Application by using a dynamic select string, enter:
mkequ -D "ResourceType==0" Jfoo IBM.Application
6. To make an equivalency that is called netequ with selected members eth0 from nodes node1 andnode2 of resource class IBM.NetworkInterface, and to set its policy to Ordered and Failback,enter:
mkequ -p O,Failback netequ IBM.NetworkInterface:eth0:node1,eth0:node2
Files
/usr/sbin/rsct/bin/mkequLocation of the mkequ command.
data_input_fileSee the examples, and see the man page for Resource_Data_Input file.
See Also
The chequ, chrgmbr, lsequ, mkrel, rmequ commands.
The rmccli general information file.
The Resource_Data_Input file.
mkrel
Name
mkrel - Makes a managed relationship between resources.
Synopsis
mkrel [-h] -f data_input_file [-T] [-V]
mkrel [-h] [-p relationship] [-o condition] -S Source_class[:Resource_name[:Node]] [-s"Source_selection_string"] -G Target_class[:Resource_name[:Node][,Target_class[:Resource_name [:Node][,...]]]] [-g "Target_selection_string"] [-T] [-V] [Managed_Relation]
78 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Description
The mkrel command makes a relationship between resources. The relationship is between a sourceresource and one or more target resources. The source resource must be a managed resource, which iseither a member of a resource group or a resource group. The target resource does not have to be in aresource group.
Managed relationships and their attribute flags can be specified on the command line as the syntaxindicates or from a file when used with the -f option. The value must be the same data type that isdefined for this resource attribute. Use the lsrsrcdef command to verify the data type and attributefield for each attribute.
Although optional, specify a name for the managed relationship.
Options
-o conditionSpecifies an If condition to be used when a Location relationship (Collocated, AntiCollocated, Affinity,or AntiAffinity) or a StartAfter (for the IfPossible condition only) is defined. The value can be a numericvalue or a word (not case-sensitive):0x0000 or NoCondition
Specifies unconditional location relationship.0x0001 or IfOnline
Specifies that the target resource is online.0x0002 or IfOffline
Specifies that the target resource is offline, failed offline, or unknown.0x0003 or IfNotOnline
Specifies that the target resource is not online.0x0004 or IfNotOffline
Specifies that the target resource is not offline or failed offline.0x0005 or IfPossible
Used with the StartAfter relationship. Specifies that the target resource group can be bypassed ifit cannot be bound, in which case it ends up in Sacrificed state and the StartAfter relationship isignored.
-f data-input_fileSpecifies the name of the file that contains managed-relationship attribute information.
-g Target_selection_stringSpecifies the target selection string, which is applied to all resources of the resource class that isspecified by the -G option to determine the targets of the relationship.
If the -g option is used to specify a target selection string, Resource_name and Node must not bespecified for the -G option.
-G Target_class[:Resource_name[:Node]]
Specifies the target resources of the relationship. A target resource is identified by the resource class(Target_class) of the resource, the resource name (Resource_name), and, optionally, the node (Node)at which the resource is located.
Resource names cannot contain the Dollar symbol ($). Target_class, Resource_name, and Node mustbe separated by colons. Multiple target resources can be specified and are separated by commas. Thecolons are required, but omitting Target_class or Resource_name causes the previously specifiedclass or name to be used when multiple target resources are specified.
If the -g option is used to specify a target selection string, Resource_name and Node must not bespecified for the -G option.
-hWrites the command's usage statement to standard output.
Chapter 2. Reference 79
-p relationshipSpecifies the managed relationship to apply. The value can be a numeric value or a word (not case-sensitive):0x0001 or Collocated
Specifies that the source and the target resources are on the same node.0x0002 or AntiCollocated
Specifies that the source and the target resources are on different nodes.0x0003 or Affinity
Specifies that the source resource and its specified affinity resource are on the same node ifpossible.
0x0004 or AntiAffinitySpecifies that the source resource and its specified affinity resource areon different nodes ifpossible.
0x0005 or IsStartableSpecifies that the source and its target resources are startable.
0x0006 or StartAfterSpecifies that the source is to be started after the target resources.
0x0007 or DependsOnSpecifies that the target resources must be online before the source resource is started andincludes an implicit collocation between the source and target resources.
0x0008 or DependsOnAnySpecifies that the target must be online before the source resource is started. It is identical to theDependsOn relationship except that it does not provide the collocated constraint for the startsequence. Therefore the source and target resources can not be started on the same node.
0x0009 or StopAfterSpecifies that the source resource can not be stopped until after the target resource is offline.
0x000A or ForcedDownBySpecifies that the source resource must be forced offline if the target resource goes offlineunexpectedly or the target resource itself is forced offline.
-s Source_selection_string
Specifies the source selection string, which is applied to all resources of the resource class that isspecified by the -S option to determine the source of the relationship. The result of the selectionmust contain only one resource.
If the -s option is used to specify a source selection string, Resource_name and Node must not bespecified for the -S option.
-S Source_class[:Resource_name[:Node]]
Specifies the source resource of the relationship. A source resource is identified by the resource class(Source_class) of the resource, the resource name (Resource_name), and, optionally, the node (Node)at which the resource is located.
Resource names cannot contain the Dollar symbol ($). Source_class, Resource_name, and Node mustbe separated by colons.
If the -s option is used to specify a source selection string, Resource_name and Node must not bespecified for the -S option.
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
80 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
ParametersManaged_Relation
Optional name of the managed relationship. The name of a managed relationship cannot contain theDollar symbol ($).
If there are several managed relationships with the same source resource, specify a name for themanaged relationship. Otherwise, the relationships are consolidated into a single managedrelationship after a policy save and activate action with the sampolicy command.
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
7Resource exists.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
1. To create a new relationship by using the data input file, proceed as follows:
a. To generate a template to aid in the defining of these relationships in a file, enter:
lsrsrcdef -i IBM.ManagedRelationship > /tmp/Rel.rdef
b. Edit the file /tmp/Rel.rdef with your preferred text editor: Enter values for all of the attributes,substituting an appropriate value for the type or leaving it blank if you want the default value.
c. Run the mkrel command with the file as follows:
mkrel -f /tmp/Rel.rdef
Sample Data Input file for mkrel:
You can enter values for all of the attributes and change the value shown in the sample, or remove theline with the attribute if you want the default value.
PersistentResourceAttributes::resource 1: Name = "Rel1" Source = "IBM.ResourceGroup:G2" Target = "IBM.ResourceGroup:G1"Relationship = StartAfterresource 2: Name = "Rel2"
Chapter 2. Reference 81
Source = IBM.Application:A2 Target = "{IBM.NetworkInterface:eth0:saopt02}" Conditional = IfNotOfflineRelationship = collocated
2. To make a relationship that is named myrel for a resource tester that belongs to resource classIBM.Application with target resources from resource class IBM.Application, whoseResourceType is set to one, enter:
mkrel -p collocated -S IBM.Application:tester -G IBM.Application -g "ResourceType==1" myrel
3. To make an Affinity relationship that is called test for a resource tester belonging to resource classIBM.Application with target resource tester1 belonging to resource class IBM.Applicationand target resources Jfoo belonging to resource class IBM.Application, enter:
mkrel -p affinity -S IBM.Application:tester -G IBM.Application:tester1,Jfoo test
4. To define a Collocated relationship that is named myrel for a source resource narten of classIBM.Application to target resources tr0 and en0 of class IBM.ServiceIP, enter:
mkrel -p 1 -S IBM.Application:narten -G IBM.ServiceIP:tr0,:en0 myrel
5. To define a Collocated relationship that is named myrel for a source resource from a selection stringthat is applied to the class IBM.Application with target resources tr0 and en0 of classIBM.ServiceIP, enter:
mkrel -p collocated -S IBM.Application -s 'Name=="narten"' -G IBM.ServiceIP:tr0,:en0 myrel
Files
/usr/sbin/rsct/bin/mkrelLocation of the mkrel command.
data_input_fileSee the examples, and see the man page for Resource_Data_Input file.
See Also
The addrgmbr, chequ, chrel, chrg, chrgmbr, lsrg, mkequ, mkrg, rmequ, rmrel, rmrg, rmrgmbrcommands.
The rmccli general information file.
The Resource_Data_Input file.
mkrg
Name
mkrg - Makes one or more new resource groups.
Synopsis
mkrg [-h] -f data_input_file [-T] [-V]
mkrg [-h] [-l relationship] [-n node_name | -e equiv_name] [-p priority] [-N Owner] [-D Description] [-IInfoLink] [-T] [-V] [-x node1, ...noden] Resource_group [...]
Description
The mkrg command defines (makes) one or more new resource groups that can be monitored andcontrolled by System Automation for Multiplatforms. A resource group can be defined only on an onlinenode in a cluster. A resource group definition defines the following to System Automation forMultiplatforms:
82 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
• Where the resource group is allowed to run.• Relative importance of resource group to other resource groups.• Location relationship among the member resources of the resource group.
New resource groups default to an offline state. This state allows a user or administrator to fully configurethe resource group and its resources before System Automation for Multiplatforms takes control of theresource group.
To allow System Automation for Multiplatforms to monitor and control the resource groups, the resourcegroup must be in Online State or condition. See the chrg command to set this or any other option on anexisting resource group.
The resource group and its attribute option can be specified on the command line as the syntax indicates,or from a file when the -f option is used. The value must be the same data type that is defined for thisresource attribute. Use the lsrsrcdef RMC command to verify the data type and attribute field for eachattribute.
Options
-e equiv_nameSpecifies the equivalency name of the nodes on which the Resource_group can run. This option cannotbe combined with the -n option. The default value is ALL, which implies an equivalency of all nodes inthe cluster.
-f data_input_fileName of the file, which contains resource group attribute information.
-hWrites the command's usage statement to standard output.
-l relationshipSpecifies the location relationship among the members of the resource group. The locationrelationship value can be:0x0000 or None
Specifies that member resources of the resource group can be on any node.0x0001 or Collocated
Specifies that member resources of the resource group are on the same node.The default value is Collocated.
-n node_nameSpecifies the node on which the Resource_group can run. This option cannot be combined with the -eoption. The default value is ALL, which implies all nodes in the cluster.
-p prioritySpecifies the relative importance of this resource group that is compared to other resource groups.Priority can be any integer from 0 - 200: the higher the integer, the higher the priority. The defaultpriority value is 0.
-N OwnerA string with the name of the owner or contact for the group.
-D DescriptionA string describing the purpose of the group.
-I InfoLinkA string that contains the URL of an HTML page, which shows additional information about theresource group.
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
Chapter 2. Reference 83
-x node1, ...nodenSpecifies the excluded node list.
Parameters
Resource_groupThe unique name of the new resource groups to be created. Resource group names cannot containthe Dollar symbol ($).
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
7Resource exists.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
1. To create resource groups by using the data input file, proceed as follows:
a. To generate a template to aid in the defining of these resources in a file, enter:
lsrsrcdef -i IBM.ResourceGroup >& /tmp/RG.rdef
b. Edit the file /tmp/RG.rdef with your preferred text editor: Enter values for all of the attributes,substituting the appropriate value for the type, or remove the line with the attribute if you want thedefault value.
c. Run the mkrg command with the file as follows:
mkrg -f /tmp/RG.rdef
Sample Data Input file for mkrg: You can enter values for all of the attributes and thus change thevalue that is shown in the example, or remove the line with the attribute if you want the default value.
PersistentResourceAttributes::resource 1: Name = "GR1" MemberLocation = "collocated" Priority = "32" resource 2: Name = "GR2" MemberLocation = "none" NominalState = "offline"
84 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
AllowedNode = "node-name1" resource 3: Name = "GR3" MemberLocation = "none" Priority = "2" NominalState = "offline" Description = "Resource group for managing of apache server"
2. To define a new resource group that is called resA with all default values, enter:
mkrg resA
3. To define new resource groups that are called resA and resB with location relationship "none", andallowed node name "cluster1", enter:
mkrg -l none -n cluster1 resA resB
4. To define a new resource group that is called resA with location relationship "Collocated", priorityvalue of 22, and allowed equivalency name "cluster1", enter:
mkrg -l collocated -e cluster1 -p 22 resA
Files
/usr/sbin/rsct/bin/mkrgLocation of the mkrg command.
data_input_file
See Also
The addrgmbr, samctrl, chrg, chrgmbr, lsrg, rmrg, rmrgmbr commands.
The Resource_Data_Input file.
The rmccli general information file.
pidmon
Name
pidmon - Searches the process list for a command string or takes the OpState from a file.
Synopsis
pidmon [-h] [-d debugmode] [-u uid] [-c] command_string
pidmon [-h] [-d debugmode] -f opstate_file
Description
The pidmon command searches the process list for a command string. If the command string was found,the RMC OpState Online is returned. The pidmon command can be used as a generic monitor for theIBM.Application resource class. Optionally the RMC OpState can be taken from a specified file.
Options
-hWrites the command's usage statement to standard output.
-d debugmodeSpecifies the debug mode.
-u uidSpecifies a user ID for the command string search.
Chapter 2. Reference 85
-cCommand string search (default) - the string can contain wildcards such as *; the matching rulesfollow the POSIX function fnmatch().
-fOpState is taken from file.
Parameters
debugmodeCan be one of the following options:1
Write debug messages to syslog.2
Write debug messages to standard output/error.3
Write detailed debug messages to standard output/error and syslog.uid
Searches process list for command string, which belongs to the specified user id. RMC_ OPSTATE_ONLINE is only reported if there is a process with the specified command string and owner of thisprocess is uid.
opstate_filePlain text file that contais just one of the RMC OpStates shown below. The pidmon command readsthis text file and returns OpState from the file.
Exit Status
Against usual command convention pidmon does not return 0 on success or another value on error. Itreturns the RMC OpState. An exit status of 0 means RMC_OPSTATE_UNKNOWN, which indicates an errorin the pidmon command. Valid RMC OpStates:0
RMC_OPSTATE_UNKNOWN1
RMC_OPSTATE_ONLINE2
RMC_OPSTATE_OFFLINE3
RMC_OPSTATE_FAILED_OFFLINE4
RMC_OPSTATE_STUCK_ONLINE5
RMC_OPSTATE_PENDING_ONLINE6
RMC_OPSTATE_PENDING_OFFLINE8
RMC_OPSTATE_INELIGIBLE
Security
This command does not require special permissions.
86 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Examples
1. Searches for the process with the command string '/bin /bash' and returns OpState online (exitstatus 1).
pidmon '/bin/bash/'echo $?1
2. Searches for the process with the command string that contains "java"; there is at least one processwith a command string that contains "java", so pidmon returns the OpState online (exit status 1).
pidmon '*java*'echo $?1
3. pidmon reads myopstate file, which contains only the number '3', and returns OpState failed offline(exit status 3).
pidmon -f myopstateecho $?3
4. Use the pidmon command as a generic monitor command for an IBM.Application resource definition:
lsrsrc -s "Name='syslogd'" IBM.Applicationresource 1: Name = "syslogd" ResourceType = 0 AggregateResource = "0x3fff 0xffff 0x00000000 0x00000000 0x00000000 0x00000000" StartCommand = "/etc/init.d/syslog start" StopCommand = "/etc/init.d/syslog stop" MonitorCommand = "/usr/sbin/rsct/bin/pidmon '/sbin/syslogd'" ....
Files
/usr/sbin/rsct/bin/pidmonLocation of the pidmon command.
See Also
The MonitorCommand attribute of IBM.Application as described under Attributes used byIBM.Application in System Automation for Multiplatforms Administrator's and User's Guide.
prereqSAM
Name
prereqSAM - Checks that all prerequisites for the installation or upgrade of System Automation forMultiplatforms, including the end-to-end automation adapter, are met.
Synopsis
prereqSAM [-d inst_pkg_dir] [-l log_file]
Description
The prereqSAM command checks whether all prerequisites for the installation or upgrade of SystemAutomation for Multiplatforms are met. The command is started by the installSAM command but canalso be run separately. If started separately, you can specify options to run the check although theprereqSAM script is not in the package directory (-d), and to specify that a log file other than the defaultis used (-l). The name of the default log file is /tmp/prereqSAM.<#>.log, where <#> is a sequentialnumber; the highest number identifies the most recent log file.
Chapter 2. Reference 87
Options
-d inst_pkg_dirRun the prerequisites check based on globalization files in the specified directory although theprereqSAM script is not available in the directory. prereqSAM is not dependent on the packages tobe installed but needs the directory for its message files.
-l log_fileLogs information that is generated by the prereqSAM command to the specified log file.
Exit Status
Return codes that are returned by the prereqSAM regardless of whether the command is started by theinstallSAM script or separately.0
The system passed the prerequisite check. The version of the operating system is supported and allprerequisite packages were found installed at the correct version. The log file contains the names andversions of the installed packages.
20An installed package does not have the correct version. The log file contains the names and versionsof the respective packages.
21A package was not found installed.
22The operating system version is not supported.
23The prerequisites check cannot run. A file might be missing. Refer to the log file for a detaileddescription of the problem.
Security
This command does not require root authority.
rgmbrreq
Name
rgmbrreq - Requests for a managed resource to be started, stopped, or canceled.
The command rgmbrreq - belongs to a group of commands (rgreq, rgmbrreq, and lsrgreq) whichallow an operator to introduce persistent requests into System Automation for Multiplatforms. Using thisset of commands the operator can start, stop, cancel, or move resource groups and managed resources.
Synopsis
rgmbrreq [-h] [-p priority] -o action [-S source] [-u userID] [-c comments] [-T] [-V]Resource_class:Resource[:Node][,Resource[:Node][,...]][Resource_class:Resource[:Node][,Resource[:Node][,...]][...]]
rgmbrreq [-h] [-p priority] -o action -s [-S source] [-u userID] [-c comments] [-T] [-V]Resource_class:"Selection_String" [Resource_class:"Selection_String" [...]]
Description
By using the rgmbrreq command, the operator or any originator (source) asks for the managed resourceto be started, stopped, canceled, locked, or unlocked. Start and Stop requests last until explicitlyremoved or canceled by the operator. A request that comes from the same source replaces a formerrequest from that source - that is, it cancels the previous request automatically. A move request is not
88 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
allowed for a managed resource. A stop or a start request can be canceled by the same source thatenabled it.
Lock requests freeze resources in their current state and prevent them from being automated. Lockrequests are persistent. To unlock a resource and to remove the lock request, an unlock request isrequired.
Options
-hHelp. Writes the command's usage statement to standard output.
-p priorityDetermines how important the request is regarding other requests within the resource structure. Thepriority allows System Automation for Multiplatforms to solve conflicting requests for the sameresource.low
Low priority, default value.high
High priority.force
Takes precedence over requests posted with high priority.-o action
The actual action request.start
Sets a request to start the resource. The resource starts if the policy allows it and if no requestwith a higher priority that prevents the resource from being started exists.
stopSets a request to stop the resource. The resource stops if the policy allows it and if no requestwith a higher priority that prevents the resource from being stopped exists.
cancelCancels a previously entered request. The request is identified by the source of the request (-Sparameter) and the resource name.
lockLocks a resource. When the resource is locked, it is frozen in its current state and no longerautomated.
unlockUnlocks a resource.
-sSpecifies that a selection string is used.
-S sourceIdentifies the originator of the request.
• Operator• ExtSched• Automation
Any other value is allowed, but gets the lowest priority. If the source is not specified, "Operator" isused as default source. When the request is canceld, the same source string must be specified. Eachsource can have only one active request of each type against each resource. If the source makes asecond request directly against the resource, it replaces their first request. The source option allowsthe installation to identify the different organizational units and the roles they are playing. Anotherusage is to distinguish between who made or where the request came from, for example from theoperator versus an automation shell script.
Chapter 2. Reference 89
-u userIDThe user or operator ID of the originator of the request, which can be any string. If the string containsblanks, it must be enclosed in quotation marks.
-c commentsA string that represents a remark that might be related to the request. If the string contains blanks, itmust be enclosed in quotation marks. The character semicolon ";" is not allowed in comments.
-TTrace. Writes the command's trace messages to standard error. For your software-serviceorganization's use only.
-VVerbose. Writes the command's verbose messages to standard output.
Parameters
Resource_class:"selection_string"The -s option determines this operand. Each selection string must be preceded by a resource class.Resource_class indicates the name of the resource class the selection_string is applied to. Theselection_string and its Resource_class must be separated by colon or ":"delimiter. The specifiedselection string is applied to its corresponding Resource_class attributes to determine which memberresources are to be removed from the Resource_group. The selection string must be enclosed withindouble or single quotation marks. If the selection string contains double quotation marks, enclose theentire selection string in single quotation marks. For example:
-s IBM.Application:`Name=="testing"`-s IBM.Application:`Name ?="test"`-s IBM.Application:`Name like "%"` (For all resources)
Resource_class:Resource[:Node]The member resources specifies one or more member resources that are to be acted on. Resourcesbelonging to different resource classes can also be specified by using this syntax. However, memberresources that belong to different classes must be separated by spaces. A member resource isidentified by the resource's class (Resource_class), the resource's name (Resource_name), andoptionally the node (Node) the resource is on. The Resource_class, Resource, and Node must beseparated by a colon. Resource_class is the name of the resource class the member resource belongsto. Resource is the name of the actual member resource in its class. The node must be included whentrying to act on a fixed member resource. The node and its resource must be separated by the colonor ":" delimiter. Multiple resources that belong to the same resource class can also be specified andare separated by a comma:Resource_class:Resource[:Node][,Resource[:Node][,...]] The memberresources must exist in the resource group for the requested action to take place.
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
90 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
1. To request a start action on application App1 of IBM.Application, enter:
rgmbrreq -o start IBM.Application:App1
Files
/usr/sbin/rsct/bin/rgmbrreqLocation of the rgmbrreq command.
See Also
The addrgmbr, chrg, chrgmbr, lsrg, lsrgreq, mkrg, rgreq,rmrg, and rmrgmbr commands.
rgreq
Name
rgreq - Requests for a resource group to be started, stopped, canceled, locked, unlocked, or moved.
The rgreq command belongs to a group of commands (rgreq, rgmbrreq, and lsrgreq) which allowan operator to introduce persistent requests into System Automation for Multiplatforms. Using this set ofcommands the operator can start, stop, cancel, lock, unlock, or move resource groups and managedresources.
Synopsis
rgreq [-h] [-p priority] -o action [-S source] [-n node1,....noden] [-u userID] [-c comments] [-T] [-V]Resource_group
Description
The rgreq command is used to send requests against resource groups that are automated by SystemAutomation for Multiplatforms. By sending a request, the originator or source of the request, for example,an operator or the decision engine of System Automation for Multiplatforms, asks that a resource group isstarted, stopped, canceled, locked, unlocked, or moved.
Start and Stop requests are retained until they are explicitly removed or canceled; lock requests areretained until the resource is explicitly unlocked again.
Typically, two requests that are sent by the same originator replace each other. The new requestautomatically cancels the older one. Requests are considered to have the same originator if their Sourceattributes have the same value. Start and Stop requests cancel each other, but Move requests do not.
Since Move and Start or Stop request are of different types, both a Move request and a Start or a Stoprequest from the same source against the same resource can be allowed. For example, request aresource group to start, then to move the resource. When the resource group is moved, the Start requestcan be still be in place. A Move request is automatically removed when the move action is carried out orcanceled by the Recovery RM (IBM.RecoveryRM), or when the move request is canceled by using amovecancel request. Stop and Start requests can be canceled at any time. However, the cancel requestsmust come from the same source as the original Start and Stop requests.
Lock requests freeze resource groups in their current state and prevent them from being automated. Lockrequests are persistent, to unlock a resource group and to remove the lock request an unlock request isrequired.
Chapter 2. Reference 91
Options
-hHelp. Writes the command's usage statement to standard output.
-p priority levelDetermines how important the request is regarding other requests within the resource structure. Thepriority allows System Automation for Multiplatforms to solve conflicting requests for the sameresource. priority level can have one of the following values:low
Low priority. This is the default.high
High priority. Takes precedence over request posted with low priority.force
Takes precedence over request posted with high or low priority.-o action
Specifies the actual action request. It can be one of the following actions:start
Sets a request to start the resource group. The resource group starts if the policy allows it and ifno request with a higher priority that prevents the resource group from being started exists.
stopSets a request to stop the resource group. The resource group stops if the policy allows it and if norequest with a higher priority that prevents the resource group from being stopped exists.
moveMoves the resource group and its members to a different node in the cluster. The process involvesstopping an active set of resources and starting them on different node(s) in a coordinatedfashion.
cancelCancels a previously entered request. The request is identified by the source of the request (-Sparameter) and the resource name. Start and stop requests can only be canceled byusing cancelrequests. Move requests are canceled by using movecancel requests. Lock requests are canceledby using unlock requests.
movecancelCancels a previously entered move request. The request is identified by the name of the resourcegroup.
lockLocks a resource group. When the group is locked, it is frozen in its current state and no longerautomated.
unlockUnlocks a resource group.
-S sourceIdentifies the originator of the request.
• Operator• ExtSched• Automation
Other originators are allowed, but gets the lowest priority. If the source attribute is not specified, thenit defaults to Operator. When the request is cancled, the same source string must be specified. Thereare two types of request. Start and Stop requests are of one type, and the Move request is of anothertype. Each source can have only one active request of each type against each resource. If the sourcemakes a second request directly against the resource, it replaces their first request. The source optionallows the installation to distinguish where the request came from, for example from the operatorversus an automation shell script.
92 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
-n node1,..nodenThe originating nodes. This option can be applied only for a move action. It identifies the nodes tomove the resource group or its underlying resources from. This option is required for an anticollocatedresource group.
-u userIDThe user or operator Id of the originator of the request, which can be any string. If the string containsblanks, it must be enclosed in quotation marks.
-c commentsA string that represents a remark that might be related to the request. If the string contains blanks, itmust be enclosed in quotation marks. The character semicolon ";" is not allowed in comments.
-TTrace. Writes the command's trace messages to standard error. For your software-serviceorganization's use only.
-VVerbose. Writes the command's verbose messages to standard output.
Parameters
Resource_groupThe name of the resource group. The resource goup is the entry point at which the request isintroduced into the resource structure and from which it propagates outwards.
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
1. To move all the resources from node1 in resource group RG1, enter:
rgreq -n node1 -o move RG1
2. To stop all the resources in resource group RG2, enter:
rgreq -o stop RG2
3. To lock all resources in resource group RG2, enter:
Chapter 2. Reference 93
rgreq -o lock RG2
Files
/usr/sbin/rsct/bin/rgreqLocation of the rgreq command.
See Also
The lsrgreq, mkrg, chrg, rmrg, lsrg commands.
rmequ
Name
rmequ - Removes one or more already-defined resource equivalencies.
Synopsis
rmequ [-h] [-i] -s "selection_string" [-T] [-V] [Equivalency [...]]
rmequ [-h] [-i] [-T] [-V] Equivalency [...]
Description
The rmequ command removes one or more resource equivalencies specified by Equivalency parametersor equivalencies derived from selection strings.
Options
-hWrites the command's usage statement to standard output.
-iInteractive. Prompt before removing equivalencies.
-s "selection_string"Specifies the equivalency selection string. This selection_string is applied to all the existingequivalencies when an equivalency parameter is not specified. When equivalency parameters arespecified, then the specified selection string is only applied to the specified equivalency parameters.The selection string must be enclosed within double or single quotation marks. If the selection stringcontains double quotation marks, enclose the entire selection string in single quotation marks. Forexample:
-s 'Name == "testing"'
-s 'Name ?= "test"'
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
ParametersEquivalency
Specifies the name of the defined resource equivalency to be removed. Multiple equivalencies may bespecified, but must be separated by spaces.
94 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Exit Status
0Command has run successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
Security
This command requires root authority, or a user ID with appropriate permissions. (For more information,see System Automation for Multiplatforms Administrator's and User's Guide, section "Setting up non-rootsecurity".)
Examples
1. To remove an equivalency called resA, enter:
rmequ resA
2. To remove equivalencies called resA, resB, and resC, enter:
rmequ resA resB resC
Files
/usr/sbin/rsct/bin/rmequLocation of the rmequ command.
See Also
The chequ, samctrl, lsequ, mkequ commands.
The rmccli General Information file.
rmrel
Name
rmrel - Removes a managed relationship between resources.
Synopsis
rmrel [-h] [-i] -s "selection_string" [-T] [-V]
rmrel [-h] [-i] -S Source_Class[:Resource_name[:Node]] [-s "Source_string"] [-GTarget_Class[:Resource_name[:Node][,Target_class[:Resource_name[:Node][,. ...]]]]][-g "Target__string"][-P Current_relationship] [-O Current_condition] [-T] [-V]
rmrel [-h] [-i] [-T] [-V] Managed_Relation [Managed_Relation ...]
Chapter 2. Reference 95
Description
The rmrel command removes a relationship between resources. The relationship to be removed isdetermined by the source parameter (Source_class [:Resource_name [:Node]]) or by the selection stringwhen it is applied to the relationship itself or the name(s) of the managed relationship(s).
Options
-O Current_conditionSpecifies the condition value to query all defined relationships, in order to find a match. The value canbe the numeric value or the word (not case-sensitive):
• 0x0000 or NoCondition• 0x0001 or IfOnline• 0x0002 or IfOffline• 0x0003 or IfNotOnline• 0x0004 or IfNotOffline• 0x0005 or IfPossible
-g Target_stringThe Target_string is applied to all resources of the resource class specified by the -G option, todetermine the targets of the relationship.
If the -g option is used to specify a target selection string, Resource_name and Node must not bespecified for the -G option.
-G Target_class[:Resource_name[:Node]]
Specifies the target resource to be used with the target query, and any other specified query, to find amatch from all defined relationships. A target resource is identified by the class of the resource(Target_class), the name of the resource ( Resource_name), and optionally the node (Node) on whichthe resource is located. The Resource_class, Resource_name and Node must be separated by a colon.Multiple target resources can be specified and are separated by a comma. The colons are required,but if the Target_class is omitted, the previously-specified class will be used when specifying multipletarget resources.
If the -g option is used to specify a target selection string, Resource_name and Node must not bespecified for the -G option.
-hWrites the command's usage statement to standard output.
-iInteractive. Prompt before removing relationships.
-P Current_relationshipSpecifies the managed relationship value used to query all the defined relationships to find a match.The value can be a numeric value or the word (not case-sensitive):0x0001 or Collocated
Specifies that the source and the target resources are to be located on the same node.0x0002 or AntiCollocated
Specifies that the source and the target resources are to be located on different nodes.0x0003 or Affinity
Specifies that the source resource and its specified affinity resource are to be located on the samenode, if possible.
0x0004 or AntiAffinitySpecifies that the source resource and its specified affinity resource are to be located on differentnodes, if possible.
0x0005 or IsStartableSpecifies that the source and its target resources are startable.
96 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
0x0006 or StartAfterSpecifies that the source is to be started after the target resources.
0x0007 or DependsOnSpecifies that the target resources must be online before the source resource is started andincludes an implicit collocation between the source and target resources.
0x0008 or DependsOnAnySpecifies that the target must be online before the source resource is started. It is identical to theDependsOn relationship except that it does not provide the collocated constraint for the startsequence. Therefore the source and target resources may not be started on the same node.
0x0009 or StopAfterSpecifies that the source resource may not be stopped until after the target resource has beenbrought offline.
0x000A or ForcedDownBySpecifies that the source resource must be forced offline in the event that either the targetresource goes offline unexpectedly or the target resource itself is forced offline.
-s "selection_string"Specifies the selection string. If the -s option is specified without the -S option, the selection stringassociated with it will be applied to all managed relationships of resources. The selection string mustbe enclosed within either double or single quotation marks. If the selection string contains doublequotation marks, enclose the entire selection string in single quotation marks. For example:
-s 'Name == "testing"'
-s 'Name ?= "test"'
-s Source_string
Specifies the source selection string. The Source_string is applied to all resources of the resourceclass specified by the -S option to determine the source of the relationship. The result of theselection may contain one or more resources.
If the -s option is used to specify a source selection string, Resource_name and Node must not bespecified for the -S option.
-S Source_class[:Resource_name[:Node]]
Specifies the source resource of the query. This source resource, with any other query that may bespecified, will be queried against all defined relationship to find a match. A source resource isidentified by the class of the resource (Source_class), the name of the resource (Resource_name), andoptionally the node (Node) on which the resource is located. The Resource_class, Resource_Name andNode must be separated by a colon.
If the -s option is used to specify a source selection string, Resource_name and Node must not bespecified for the -S option.
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
Parameters
Managed_RelationName of the managed relationship to be removed. Multiple relationships can be specified on thecommand line, but have to be separated by spaces.
Chapter 2. Reference 97
Exit Status
0Command has run successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
7Resource already exists.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
1. To remove a relationship for a resource tester that belongs to resource class IBM.Application, enter:
rmrel -S IBM.Application:tester
2. To remove the relationship of a resource by using a selection string, enter:
rmrel -s 'Name == "tester"'
3. To remove a relationship for a source resource resA from a selection string applied to the classIBM.Application, enter:
rmrel -s 'Name=="resA"'-S IBM.Application
4. To remove all relationship for source resources from class IBM.Application:
rmrel -s 'Name like "%"' -S IBM.Application
5. To remove relationship for resources with targets from class IBM.Application with a collocatedrelationship and a specific condition, enter:
rmrel -S IBM.Application:narten -G IBM.Application:ha,:test -P collocated -O 1
6. To remove relationships named narten and resA, enter:
rmrel narten resA
Files
/usr/sbin/rsct/bin/rmrelLocation of the rmrel command.
98 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
See Also
The addrgmbr, chequ, chrel, chrg, chrgmbr, lsrg, mkequ, mkrel, mkrg, rmequ, rmrg, rmrgmbrcommands.
The rmccli General Information file.
rmrg
Name
rmrg - Removes one or more already-defined resource groups.
Synopsis
rmrg [-h] [-i] -s " selection_string" [-T] [-V] [Resource_group ...]
rmrg [-h] [-i] [-T] [-V] Resource_group [...]
Description
The rmrg command removes one or more resource groups specified by the Resource_groupparameter, or that match the specified selection string. The System Automation for Multiplatformsremoves the associated member resources also from the resource group but the member resources willcontinue to exist in the system, which can be verified using lsrsrc command. If any member of theresource groups needs to be deleted is part of a managed relationship between resources, the managedrelationship is also removed by System Automation for Multiplatforms. The resource group must alreadyexist for it to be removed. If the resource group to be removed is still online, the resource group is notremoved.
This implies that all resource groups that are nested within the resource group to be removed are alsoremoved recursively. If you want to prevent contained resource groups from being deleted recursively,proceed as follows:
1. Remove these resource groups as members from the resource group to be removed using thermrgmbr command.
2. Remove the containing resource group.
When the -h option is specified, this command's usage statement is written to standard output. Allverbose messages are also written to standard output.
All trace messages are written to standard error.
Parameters
Resource_groupThe name of the defined resource group to be removed. Multiple resource groups can be specified butmust be separated by spaces.
Options
-hWrites the command's usage statement to standard output.
-iInteractive. Prompt before removing relationships.
-s "selection_string"Specifies the selection string. If the Resource_group parameters are not specified, the selection stringwill be applied to all existing resource groups. The selection string must be enclosed within either
Chapter 2. Reference 99
double or single quotation marks. If the selection string contains double quotation marks, enclose theentire selection string in single quotation marks. For example:
-s 'Name == "testing"'
-s 'Name ?= "test"'
-s 'Name like "%"' (For all resources)
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
Exit Status
0Command has run successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
Security
This command requires root authority, or a user ID with appropriate permissions. (For more information,see System Automation for Multiplatforms , section "Setting up non-root security".)
Examples
1. To remove a resource group called resA, enter:
rmrg resA
2. To remove resource groups called resA, resB, and
resC
, enter:
rmrg resA resB resC
3. To prompt before removing resource groups called resA and resB, enter:
rmrg -i resA resB
4. To remove a resource group called resA using a select string, enter:
rmrg -s 'Name=="resA"'
100 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
5. To remove all resource groups containing the word resA as part of its name, enter:
rmrg -s 'Name ?="resA"'
Files
/usr/sbin/rsct/bin/rmrgLocation of the rmrg command.
See Also
The addrgmbr, samctrl, chrg, chrgmbr, lsrg, mkrg, rmrgmbr commands.
The rmccli General Information file.
rmrgmbr
Name
rmrgmbr - Removes one or more resources from their resource group.
Synopsis
rmrgmbr [-h] [-i] [-T] [-V] -g Resource_group
rmrgmbr [-h] [-i] -s [-T] [-V] [-g Resource_group] "selection string"
rmrgmbr [-h] [-i] -s [-T] [-V] [-g Resource_group] Resource_class:"selection_string"[Resource_class:"selection_string" [...]]
rmrgmbr [-h] [-i] [-T] [-V] [-g Resource_group] Resource_class:Resource_name [:Node][,Resource_name[:Node[,...]] [Resource_class:Resource_name [:Node][,Resource_name[:Node][,...]] [...]]
Description
The rmrgmbr command removes all the member resources of the specified resource group, or only thespecified member resources of the specified resource group, or the member resources that match theselection string but the member resources will continue to exist in the system. System Automation forMultiplatforms ensures that the associated relationship and equivalency are also updated, if possible.When the selection string is the only parameter, then it is applied directly to the IBM.ManagedResourceclass.
A resource name or selection string must be specified with the resource class to which it belongs. Theuser must input the resource class, resource name, and the node number or name if it is a fixed resource.The resource class and the resource name, the resource name and the node must be separated by acolon.
Options
-hWrites the command's usage statement to standard output.
-iInteractive. Prompt before removing relationships.
-g Resource_groupSpecifies the unique name of the resource group from which the member resources are to beremoved.
-sSpecifies that a selection string will be used instead of the resource name.
Chapter 2. Reference 101
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
Parameters
Resource_classSpecifies the name of the resource class to which the member resource belongs. The resource andthe resource class must be separated by the colon (:) delimiter.
Resource_class:Resource_name[:Node]This specifies one or more member resources that are to be removed from the specified resourcegroup. Resources belonging to different resource classes can also be specified using this syntax.However, member resources belonging to different classes must be separated by spaces. A memberresource is identified by the resource's class (Resource_class), the resource's name(Resource_name), and optionally the node (Node) the resource is on. The Resource_class,Resource_Name and Node must be separated by a colon. Resource_class is the name of the resourceclass the member resource belongs to. Resource_name is the name of the actual member resource inits class. The Node may have to be included when trying to remove a fixed resource from the resourcegroup. The Node and its resource must be separated by the colon (:) delimiter.
Multiple resources belonging to the same resource class can also be specified and are separated by acomma. In this case the first resource or Resource_name[:Node] of a resource class must bepreceded by the Resource_class it belongs to and it must be separated by the colon (:) delimiter whilethe remaining resources are separated by a comma. Resource_class:Resource_name[:Node] Themember resources must exist in the resource group for it to be removed.
Resource_class:"selection_string"Selection string. The -s option determines this operand. Each selection string must be preceded by aresource class. Resource_class indicates the name of the resource class the selection_string will beapplied to. The selection_string and it's Resource Class must be separated by the colon (:) delimiter.The specified selection string will be applied to its corresponding resource_class attributes todetermine which member resources are to be removed from the resource_group. The selection stringmust be enclosed within double or single quotation marks. If the selection string contains doublequotation marks, enclose the entire selection string in single quotation marks. For example:
-s 'Name == "testing"'-s 'Name ?= "test"'-s 'Name like "%"' ( For all resources)
Selection_stringSpecifies the selection string. The -s option determines this parameter. When this is the onlyparameter, then the selection string is applied to the member resources. But, when the selectionstring is included with Resource_group, the selection string will be applied to the member resourcesthat belong to the specified resource group. When each of the selection strings are preceded by aresource class, the specified selection string in this case will be applied to its correspondingResource_class attributes, to determine which resources are to be removed from the Resource_group.The selection string must be enclosed within either double or single quotation marks. If the selectionstring contains double quotation marks, enclose the entire selection string in single quotation marks.For example:
-s 'Name == "testing"'
-s 'Name ?= "test"'
-s 'Name like "%"' (For all resources)
102 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
1. To remove a member resource testerA that belongs to resource class IBM.Application from aresource group resA, enter:
rmrgmbr -g resA IBM.Application:testerA
2. To remove member resources testerA, testerB, and testerC that belong to resource classIBM.Application, from resource group resA, enter:
rmrgmbr -g resA IBM.Application:testerA,testerB,testerC
3. To remove member resources testerA and testerB that belong to resource classIBM.Application and fixed resource en0 that belongs to class IBM.ServiceIP, enter:
rmrgmbr IBM.Application:testerA,testerB IBM.ServiceIP:en0
4. To remove selected member resources of the resource class IBM.Application from a resourcegroup resA whose ResourceType is set, enter:
rmrgmbr -s -g resA IBM.Application:"ResourceType==1"
5. To remove all member resources of resource group resA by using a selection string, enter:
rmrgmbr -s 'MemberOf == "resA"'
Files
/usr/sbin/rsct/bin/rmrgmbrLocation of the rmrgmbr command.
See Also
The addrgmbr, chrel, chrg, chrgmbr, lsrel, lsrg, mkrel, mkrg, rmrel, rmrg, commands.
The rmccli General Information file.
Chapter 2. Reference 103
samadapter
Name
samadapter - used to control and monitor the end-to-end automation adapter. The adapter handlesthe communication between a System Automation for Multiplatforms domain and the System AutomationApplication Manager end-to-end automation server.
Synopsis
samadapter start
samadapter stop
samadapter status
samadapter help
Options
startIf the adapter is not running, the option start requests System Automation for Multiplatforms tostart the adapter on the preferred node. The command returns when the request is submitted. If theadapter is not automated, it is started on the node where the request was sent. The exit code is 0 ifthe request was successful.
stopIf the adapter is running, the option stop requests System Automation for Multiplatforms to stop theadapter on the preferred node. The command returns when the request is submitted. If the adapter isnot automated, it is stopped on the node where the request was sent. The exit code is 0 if the requestwas successful.
statusChecks if the adapter is running.
helpWrites the command’s usage statement to standard output.
Parameters
None.
Exit Status
To check the status of the samadapter, use the status option. It delivers the following return codes,0
Unknown. The adapter status cannot be determined.1
Online. The adapter is running.2
Offline. The adapter is not running.
Security
This command requires root authority, or a user ID with appropriate permissions.
Examples
1. To start the adapter, enter the following command:
samadapter start
104 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
2. To stop the adapter, enter the following command:
samadapter stop
Files
/opt/IBM/tsamp/sam/bin/samadapterLocation of the samadapter command.
samcc
Name
samcc - System Automation for Multiplatforms Control Center: Controls the defined resource groupsand their members in tree format.
Synopsis
samcc [-h] [-g Resource_group] [-s "selection_string"] [-nocolor] [-noequ] [-nomsg] [-V] [-T]
Description
The samcc command controls all resource groups and all resource group members in tree format. Someinformation is color-coded, for example the OpState of a resource that depends on the actual value. Thecolor code indicates whether there are any problems or not. As the color code is not configurable,consider to use a black or white background. If you use a different background color, use the option -nocolor to see all information reported by samcc. Line selection and action uses yellow and redhighlighting, even when using option -nocolor. If resource selection and/or actions are anticipated, thebackground color must not be yellow or red.
Note:
If you receive the following RSCT message, data is pending. One of the next queries will display thecomplete data:
2610-444 Cannot obtain values for some dynamic attributes. 0 attributes are not being monitored. 1 attributes have data pending.
Options
-hHelp. Writes the command's usage statement to standard output.
-g Resource_groupDisplays only the specified top-level resource group and its members in tree format.
-nocolorDisplays output without color-highlighting. Line selection and action uses yellow and red highlighting,even when using option -nocolor. If resource selection and/or actions are anticipated, thebackground color must not be yellow or red.
-s "selection_string"Specifies a selection string for the resource group. All selection strings must be enclosed within eitherdouble or single quotation marks. If the selection string contains double quotation marks, enclose theentire selection string in single quotation marks. For example:
-s 'Name == "test-rg" '
If the resource group is not a top-level resource group, the selection string must contain thecorresponding top-level resource group. For example:
-s 'Name like "test%-rg" || Name like "top-level-rg" '
Chapter 2. Reference 105
-noequPrint output without equivalencies.
-nomsgPrint output without error messages.
-VPrint resource details and relationships.
-TWrites the command's trace messages to standard error. For your software service organization's useonly.
Output
The samcc output has the same syntax as the lssam -top command. Refer to the “lssam” on page 69command reference for syntax details. In addition, the samcc command has a menu that is displayed atthe bottom.
The following menu entries are available:Quit – key q
The samcc command ends.Help – key h
The menu toggles between show menu and hide menu.Tree expand or collapse – minus key -, key x, and plus key +
The displayed resource tree can be expanded to show all levels of resources and collapsed to showonly top-level resources. Three different display levels are available.
• Plus (+) expands the displayed resource tree.• Minus (-) collapses the displayed resource tree.• x toggles between expand and collapse displayed resource tree.
Equ on/off – key eToggle the display of equivalencies at the bottom of the resource list.
Verbose on/off – key vToggle the display of relationships and more resource information.
Select/deselect – space barWhen the space bar is pressed before the first/next or last/previous key is pressed, then the first lineis selected. A selected line is highlighted in yellow. When the space bar is pressed after a line wasselected by using the space bar, enter key, first/next, or last/previous key, then the selection of theline is cleared
Actions on/off – Enter keyThe action mode can be entered by using the Enter key after the line is selected. The line in actionmode is highlighted in red. While in action mode the selected line cannot be moved. The action modecan be left by using the Enter key again.
First/next – key j or Down Arrow keyThe first line is selected when the key j or Down Arrow key is pressed. The selected line moves oneline down in the list, if the keyj or key Down Arrow key is pressed again. While in action mode theselected line cannot be moved.
Last/previous – key k or Up Arrow keyThe last line is selected when the key k or key Up Arrow key is pressed. The selected line moves upone line in the list, if the key k or key Up Arrow key is pressed again. While in action mode the selectedline cannot be moved.
Online – key oThe action online generates a start request on the selected resource (Group or Managed resource).This start request has the default priority low and the source operator. The action mode must beactive for the selected resource to use this key.
106 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Offline – key fThe action offline generates a stop request on the selected resource (Group or Managed resource).This stop request has the default priority low and the source operator. The action mode must beactive for the selected resource to use this key.
Cancel – key cThe action cancel cancels a start or stop request on the selected resource (Group or Managedresource). The action mode must be active for the selected resource to use this key.
Move – key mThe action move generates a move request on the selected top-level resource group. The action modemust be active for the selected top-level resource group to use this key.
Reset – key rThe action reset calls the resetrsrc command on the selected resource. This can be used to resetthe Failed Offline OpState of a fixed resource. The action mode must be active for the selectedresource to use this key.
Lock – key lThe action lock generates a lock request on the selected resource (Group or Managed resource). Theaction mode must be active for the selected resource to use this key.
Unlock – key uThe action unlock removes a lock request from the selected resource (Group or Managed resource).The action mode must be active for the selected resource to use this key.
The following output lists all menu key characters. In normal operation, only the key characters aredisplayed which are available for the selected resource. For disabled actions, the key character is notdisplayed.
# samcc .---------------------------------------------------------------------. | IBM Tivoli System Automation for Multiplatforms 2015-05-29 17:09:29 | '---------------------------------------------------------------------' Offline IBM.ResourceGroup:apache-rg Nominal=Offline |+ Offline IBM.ServiceIP:SharedIP '+ Offline IBM.Application:apache-rs Online IBM.Equivalency:NetworkInterfaces |- Online IBM.NetworkInterface:en0 (p6sa27 p6sa28) .---------------------------------------------------------------------. [q]=quit [h]=help [-x+]=tree expand/collapse [e]=equ on/off [v]=verbose on/off [SPACE]=select/deselect [CR]=actions on/off [j]=first/next [k]=last/previous [o]=online [f]=offline [c]=cancel [m]=move [r]=reset [l]=lock [u]=unlock
Exit Status
0The command ran successfully.
1An error occurred.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Installation and Configuration Guide.
Examples
1. Start samcc with option -V: all constituent resources are hidden (default samcc start mode).
# samcc -V .---------------------------------------------------------------------.| IBM Tivoli System Automation for Multiplatforms 2015-05-29 17:09:29 |'---------------------------------------------------------------------'Offline IBM.ResourceGroup:apache-rg Nominal=Offline |+ Offline IBM.Test:SharedFiles TimeToStart=5 TimeToStop=2 <. |+ Offline IBM.Test:SharedIP TimeToStart=5 TimeToStop=2 -. DO<DO '+ Offline IBM.Test:apache-rs TimeToStart=5 TimeToStop=2 | -' -'
Chapter 2. Reference 107
Offline IBM.ResourceGroup:test Nominal=Offline | |+ Offline IBM.Application:A2 | -DO '+ Offline IBM.Application:A3 DO -. <'Online IBM.Equivalency:NetworkInterfaces <' | |- Online IBM.NetworkInterface:en0 (p6sa27 p6sa28) DOOffline IBM.Equivalency:testequ SelectFromPolicy=ANY,NoControl <' |- Offline IBM.Application:A1.---------------------------------------------------------------------. [q]=quit [h]=help [-x+]=tree expand/collapse [e]=equ on/off [v]=verbose on/off [SPACE]=select/deselect [ ]=actions on/off [j]=first/next [k]=last/previous
2. Enter j and then press the Enter key: the first top-level group is selected and action mode is activated.
.---------------------------------------------------------------------.| IBM Tivoli System Automation for Multiplatforms 2015-05-29 17:09:29 |'---------------------------------------------------------------------'Offline IBM.ResourceGroup:apache-rg Nominal=Offline |+ Offline IBM.Test:SharedFiles TimeToStart=5 TimeToStop=2 <. |+ Offline IBM.Test:SharedIP TimeToStart=5 TimeToStop=2 -. DO<DO '+ Offline IBM.Test:apache-rs TimeToStart=5 TimeToStop=2 | -' -'Offline IBM.ResourceGroup:test Nominal=Offline | |+ Offline IBM.Application:A2 | -DO '+ Offline IBM.Application:A3 DO -. <'Online IBM.Equivalency:NetworkInterfaces <' | |- Online IBM.NetworkInterface:en0 (p6sa27 p6sa28) DOOffline IBM.Equivalency:testequ SelectFromPolicy=ANY,NoControl <' |- Offline IBM.Application:A1.---------------------------------------------------------------------. [q]=quit [h]=help [-x+]=tree expand/collapse [e]=equ on/off [v]=verbose on/off [SPACE]=select/deselect [CR]=actions on/off [ ]=first/next [ ]=last/previous [o]=online [f]=offline [c]=cancel [m]=move []=reset [l]=lock [u]=unlock
3. Enter v and then enter the plus sign: all resources are shown with verbose mode turned off.
.---------------------------------------------------------------------.| IBM Tivoli System Automation for Multiplatforms 2015-05-29 17:09:29 |'---------------------------------------------------------------------'Offline IBM.ResourceGroup:apache-rg Nominal=Offline |+ Offline IBM.Test:SharedFiles |- Offline IBM.Test:SharedFiles:p6sa27 '- Offline IBM.Test:SharedFiles:p6sa28 |+ Offline IBM.Test:SharedIP |- Offline IBM.Test:SharedIP:p6sa27 '- Offline IBM.Test:SharedIP:p6sa28 '+ Offline IBM.Test:apache-rs |- Offline IBM.Test:apache-rs:p6sa27 '- Offline IBM.Test:apache-rs:p6sa28Offline IBM.ResourceGroup:test Nominal=Offline |+ Offline IBM.Application:A2 |- Offline IBM.Application:A2:p6sa27 '- Offline IBM.Application:A2:p6sa28 '+ Offline IBM.Application:A3 |- Offline IBM.Application:A3:p6sa27 '- Offline IBM.Application:A3:p6sa28Online IBM.Equivalency:NetworkInterfaces |- Online IBM.NetworkInterface:en0:p6sa27 '- Online IBM.NetworkInterface:en0:p6sa28 Offline IBM.Equivalency:testequ |- Offline IBM.Application:A1:p6sa27 '- Offline IBM.Application:A1:p6sa28.---------------------------------------------------------------------. [q]=quit [h]=help [--x]=tree expand/collapse [e]=equ on/off [v]=verbose on/off [SPACE]=select/deselect [ ]=actions on/off [j]=first/next [k]=last/previous
4. Enter the minus key twice: only top-level resources are shown.
.---------------------------------------------------------------------.| IBM Tivoli System Automation for Multiplatforms 2015-05-29 17:09:29 |'---------------------------------------------------------------------'Offline IBM.ResourceGroup:apache-rg Nominal=OfflineOffline IBM.ResourceGroup:test Nominal=OfflineOnline IBM.Equivalency:NetworkInterfacesOffline IBM.Equivalency:testequ.---------------------------------------------------------------------. [q]=quit [h]=help [x++]=tree expand/collapse [e]=equ on/off [v]=verbose on/off [SPACE]=select/deselect [ ]=actions on/off [j]=first/next [k]=last/previous
108 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Files
/usr/sbin/rsct/bin/samccLocation of the samcc command.
samctrl
Name
samctrl - Sets the System Automation for Multiplatforms control parameters.
Synopsis
samctrl [-h] -m [-f] [-T] [-V] [new_activeversion]
samctrl [-h] [-e PublisherName|-d PublisherName] [-M T|F] [-u a | d | r] [-t Timeout] [-lTrace_level][-r Retry_count] [-o ResourceRestartTimeOut] [-T] [-V] [Node [Node [...]]]
Description
The samctrl command sets the default control parameter values for System Automation forMultiplatforms. This command, when used, must change at least one control parameter for SystemAutomation for Multiplatforms.
Options
-e PublisherNameEnables the named publisher. To enable all publishers, use -e P.
-d PublisherNameDisables the named publisher. To disable all publishers, use -d P. The default value is that allpublishers are disabled.
-fForce Migration. It requires the -m option. A force option (-mf) can be specified whether user insiststo upgrade the code version when the joined System Automation for Multiplatforms daemon count isless than the total defined node count. The installed version number information of the down daemonis lower than the rest of the up daemons.
-hWrites the command's usage statement to standard output.
-mMigration. This option is used to trigger a System Automation for Multiplatforms code versionmigration complete action.
-M T|FT (True)
Manual mode. Deactivates System Automation for Multiplatforms on the cluster. Afterdeactivation, resources are no longer automated and must be started and stopped manually.State changes of resource groups are not reflected in the System Automation Application Manageroperations console. RMC commands must be used to retrieve the current states of the clusterresources.
Use this option in test environments only. It is useful in situations when the execution of a start orstop command must be avoided at all costs.
F (False)Automation mode (default). Reactivates System Automation for Multiplatforms on the cluster.
-u a | d | rSpecifies that one or more nodes are to be added to, removed from, or replaced on the list ofexcluded nodes.
Chapter 2. Reference 109
aAdds one or more specified nodes to the list of excluded nodes for control operations.
dDeletes one or more specified nodes from the list of excluded nodes for control operations.
rReplaces one or more specified nodes with the list of excluded nodes for control operations.
-r Retry_countSpecifies the default number of retries a control operation can perform before the operation isdeclared as failed.
-o ResourceRestartTimeoutResource Restart Timeout value. Specifies the default timeout value (in seconds) before a failedresource is restarted. System Automation for Multiplatforms waits for the specified time before itrestarts the resource on another node.
-t TimeoutSpecifies the default timeout value (in seconds) of a control operation. A control operation is declaredstalled or failed if the operation is not successfully completed within the specified time interval.
-l Trace_levelSets the trace level to control the degree and amount of tracing. The maximum value of 255 results indetailed tracing, while the value 0 suppresses writing various classes of trace entries. The defaultlevel is 31. Change this option only if advised by IBM support.
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
ParametersNode
Specifies the name of one or more nodes that is added, removed, or replaced on the list of excludednodes for control operations. The -u option and its parameter determines the action that is requiredto update the list of excluded nodes.
new_activeversionSpecifies the new active version value for System Automation for Multiplatforms. It requires the -moption.
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
6Resource specified was not found.
110 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
7Resource exists.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
1. Set System Automation for Multiplatforms to be in automated mode, with retries at 4, resource restarttimeout as 5 seconds.
samctrl -M F -r 4 -o 5
2. Exclude some nodes from System Automation for Multiplatforms control:
samctrl -u a narten jarden varten
3. Migrate to the latest version, enter:
samctrl -m
4. To force a migration to the latest version, enter:
samctrl -m -f
5. To enable the Tivoli Enterprise Console® publisher function, enter:
samctrl -e TEC
Files
/usr/sbin/rsct/bin/samctrlLocation of the samctrl command.
See Also
The lssamctrl command.
The lrmccli general information file.
samdiag
Name
samdiag - Requests detailed information about a resource.
Synopsis
samdiag [-h] [-T] [-V] [-x extra_info] -r Resource_handle
samdiag [-h] [-T] [-V] [-x extra_info] -g Resource_group
samdiag [-h] [-T] [-V] [-x extra_info] Resource_class:Resource:[Node]
samdiag [-h] [-T] [-V] [-x extra_info] -e Engine_name
Description
You can request detailed resource information by using this command. You can enter the command onany node where a System Automation for Multiplatforms daemon is active.
The command samdiag provides the following information about a specified resource:
Chapter 2. Reference 111
• Status• Dependencies• Binding constraints• Outstanding actions• Flags and exceptions• Requests and votes• History• Variables
Options
-hWrites the command's usage statement to standard output.
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
-x extra_infoExtra information. This option requests for extra information on the specified resource. The operandextra_info can have the following valid strings:reqs
requests information.votes
votes information.hist
history information.vars
variable information.all
all information.-g Resource_group
The name of the resource group implies that a resource group is specified.-r Resource_handle
Resource handle. This option implies that a resource handle of a resource is specified.-e Engine_name
Engine resource name. This option implies that an engine name of a resource is specified. Theseformats are the engine name formats currently in use:
• Cluster• Resource_name/<type>/Resource_class[/Node]
ClusterThis implies that diagnostic information is requested on the cluster or shared domains that areknown to System Automation for Multiplatforms.
Resource_name/<type>/Resource_class[/Node]This format is the most commonly used engine name format. Here the engine resource is identified bythe resource's name (Resource_name), the <type> of resource, the resource's class (Resource_class),and optionally the node (Node) the resource is on. The Resource_class, Resource_name, and Nodemust be separated by a forward slash ("/"). Resource_class is the name of the Resource_class theresource belongs to. Resource_name is the name of the actual resource in its class. The Node must be
112 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
included when you try to act on a fixed resource. The Node and its resource must be separated by theforward slash or "/" delimiter. Resource <type>ResGroup
For resource groups.Equivalency
For equivalencies.Fixed
For fixed resources.Float
For floating resources.
ParametersResource_class: Resource_name[:Node]
Member Resources. This specifies one resource that is to be acted on. A resource is identified by theresource's class (Resource_class), the resource's name (Resource_name), and optionally the node(Node) the resource is on. Resource_class, Resource_Name, and Node must be separated by a colon.Resource_class is the name of the Resource_class the resource belongs to. Resource_name is thename of the actual resource in its class. The Node must be included when you try to act on a fixedresource. The Node and resource must be separated by the colon or ":" delimiter.
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred due to an underlying error in the command script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred due to a user error.
6Resource specified was not found.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Files
/usr/sbin/rsct/bin/samdiagLocation of the samdiag command.
See Also
The lssamctrl command.
The rmccli general information file.
Chapter 2. Reference 113
samlicm
Name
samlicm - Use this command to install, list, and upgrade the product license or a feature license.
Synopsis
samlicm [-h]
samlicm [-p [XDR|SAP]]
samlicm [-s]
samlicm [-t]
samlicm [-i license_file]
Description
The samlicm command installs, lists, and upgrades the product license for System Automation forMultiplatforms or a feature license. Since every node in the cluster checks for a license, the license mustbe installed on every node in the cluster. Depending on the installation medium, a try-and-buy or fulllicense is already installed during product installation. Use the samlicm command to check your licensestatus or upgrade a try-and-buy license to a full license.
Options
-hWrites the command's usage statement to standard output.
-p [XDR|SAP]Checks for permanent or feature licenses. The result is given as an exit status only.
-sPrints the license status to standard output. Use this option to see when your license expires.
-tTests the license. Use this option to check the installed license.
-i license_fileInstalls or upgrades the product license or feature license with the specified license file. Use the -ioption for both the initial license installation and license upgrade.
Exit Status
0The command ran successfully. Returned for option -p if a permanent license is installed.
1Error occurred during command processing.
2Returned for option -p if a try-and-buy license is installed.
Security
This command requires root authority.
Examples
1. Install a license or upgrade a license:
samlicm -i try_buy.lic
114 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
If everything works fine you, do not get any output from the command. If an error occurs, the errormessage is written to standard error, and the corresponding exit status is returned.
2. Print the license status:
samlicm -s
Sample Output:
The following output indicates that the System Automation for Multiplatforms product license isinstalled.
Note: Product licenses might have no qualifier on the associated 'Product Annotation' line.
Product ID: 101Product Annotation:Creation date: Thu Oct 25 02:00:00 2007Expiration date: Fri Jan 1 00:59:59 2038
The following output indicates that two licenses are installed: the System Automation forMultiplatforms product license, and an Extended Disaster Recovery for Linux on System z License.
lnxxdr43:~ # samlicm -sProduct: IBM Tivoli System Automation for Multiplatforms 3.2Product ID: 101Product Annotation: SA for MP xDR for Linux on System zCreation date: Wed Aug 19 02:00:00 2009Expiration date: Fri Jan 1 00:59:59 2038
Files
/usr/sbin/rsct/bin/samlicmLocation of the samlicm command.
See Also
The IBM License Use Management (LUM) documentation.
samlog
Name
samlog - Collects, formats, merges, and displays System Automation for Multiplatforms-related logs ofa live domain or previously collected ctsnap data.
Synopsis
samlog [-n Node[, Node...]] [-s Source[, Source...]]
[[-d] -t Offset{d|h|m|s}|YYYY-MM-DD[.hh[:mm[:ss]]]
[+Duration{d|h|m|s}|, YYYY-MM-DD[.hh[:mm[:ss]]]]
|all]
[--dir CtsnapDirectory --dom DomainName]
[-r | -e EyecatcherRegexp] [--nocomp] [–T] [–h|--help]
Description
The samlog command collects data from log files, for example trace or trace summary files. Log files canhave various sources in the System Automation for Multiplatforms domain or come from previouslycollected ctsnap data. The time frame for which logs are retrieved can be restricted if you specify eitherrelative time spans or absolute dates. If you enabled trace file spooling, the spooled files are regarded aswell.
Chapter 2. Reference 115
Unless you use the –r option, the logs are formatted to a common format:
• Headers are removed.• Date and time format is unified. The following format is used for the time-stamp: YYYY-MM-DDhh:mm:ss:mmmmmm
– YYYY: year– MM: month– DD: day– hh: hour– mm: minutes– ss: seconds– mmmmmm: microseconds fraction
• Information about the source of the log entries is added to the actual log entries by using the formatSourceCharacterNodeName) . The SourceCharacter is one of the characters that are listed in thedescription of the -s option.
• Actual log entry.
If multiple logs are retrieved, they are merged by their time stamp. To ensure the correct order of mergedlog entries, system time offset differences are compensated. System time offsets of ctsnap data cannotbe determined and are not compensated.
The retrieved, formatted, and merged logs are printed. Logs are printed with a header that includes time,location, and options of the samlog command, and a table with the following information:
• Node name• Compensated system time that is offset between local host and node.• List of all sources that are retrieved by this node.
Note:
1. Concurrent calls of samlog in the same cluster or on the same ctsnap data can fail due to errorscaused by rpttr attempting to log the processed trace files.
2. It is required to enable ithread support of the Perl distribution that is used by RSCT. If a message likeCan't locate threads.pm is displayed, update Perl on every system of your cluster to supportithread.
Options-n Node[,Node...]
Use option –n to specify the nodes from which you want to collect logs. Make sure that the nodenames are the same than the node names listed by lsprnode. The node list consists of comma-separated values without blanks. By default, all nodes that are online in the domain or all nodes thatare located in the ctsnap directory are selected.
-s Source[,Source...]Use option –s to specify the sources from which logs are retrieved. The source list consists of comma-separated source characters or names without any blanks:
• R or IBM.RecoveryRM – to select IBM.RecoveryRM (selected by default)• G or IBM.GblResRM – to select IBM.GblResRM (selected by default)
-dUse option –d to produce detailed output. If this option is set, the complete traces of the resourcemanagers are collected. It is required to use the –t option to restrict the queried time frame, becausethis option retrieves much more data. By default, this option is not set and the trace summaries of theresource managers are collected.
116 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
-t Offset{d|h|m|s}|YYYY-MM-DD[.hh[:mm[:ss]]][+Duration{d|h|m|s}|,YYYY-MM-DD[.hh[:mm[:ss]]]]|all
Use option –t to specify if the time frame is queried either relative to the current time or absolute. Atime frame is defined by start and end time. If you specify only the start time but no end time, thenthe time frame takes until current time.relative
Specify the start date in the past by defining an offset followed by a measuring unit: d - days, h -hours, m - minutes, s - seconds. Optionally, specify the end date by appending + followed by theduration and a measuring unit.
Example:
• 2d, 60 s, 1d+1 h
absoluteSpecify the start date by a portion of a date. Optionally, specify the end date by a portion of a date,which is separated by a comma.
Examples:
• 2010-06-23.08:29:30• 2010-06-23.08• 2010-06-23.12, 2010-06-23.12:30
mixedYou can use a combination of relative and absolute.
Examples:
• 2010-06-23.08:29:00+60 s• 12d,2010-06-22
If the –t option is used with value all, everything is retrieved. If no –t option is specified, the defaultis the last day (1d).
--dir CtsnapDirectoryUse option --dir to apply samlog to previously collected ctsnap data. The CtsnapDirectorymust contain subfolders for each cluster node. These subfolders are named exactly like the nodenames that are listed by lsprnode from which the ctsnap data was collected. They must containthe extracted or uncompressed or non-tared ctsnap data.
Combine the --dir option with --dom.
--dom DomainNameThe command ctsnap stores the logs of all domains that are defined on a node. Use option -dom incombination with the --dir option to specify from which domain you want to retrieve logs. The validdomain names can be found as symbolic links in the /var/ct subfolder of the node folder.
-rUse option –r to retrieve a raw log. If this option is set, reformatting of the log is skipped and theoriginal log is displayed. This option can be used only in combination with a single node which isspecified with the –n option and a single source which is specified with the –s option. The –r optioncannot be combined with the –e option. If the –r option is not set, logs are formatted.
-e EyecatcherRegexpUse option –e to filter logs for specific eye catchers. The EyecatcherRegexp has Perl regularexpressions syntax. The following example provides a limited description of the Perl expressionsyntax:
Wild cards: .=any, \w=word char, \d=digit, \s=white space
Powers: *=0.., +=1.., ?=0..1, {n}=n, {n,}=n.., {n,m}=n..m
Grouping, alternative: AB=A followed by B, (A|B)=[A|B]=A or B
Chapter 2. Reference 117
Only those entries are displayed that match the EyecatcherRegexp.
Note:
1. The time-stamp, node and source prefix are not part of the entry that is checked against theEyecatcherRegexp.
2. Duplicate any backslash in the EyecatcherRegexp value to pass the backslash properly tosamlog.
Example:
• Instead of \s write \\s
The –e option cannot be used in combination with the –r option.
--nocompUse option --nocomp to disable compensation of system time differences on the nodes from whichlogs are retrieved. If this option is set, the original times are preserved. If this option is not set, thesystem time offsets of the node where samlog runs and the nodes which provide logs are determinedand compensated to ensure the correct order of entries in the merged logs.
-TUse option –T to write samlog traces to STDERR.
-h | --helpUse option –h to display the usage syntax.
Exit Status0
The command ran successfully.2
Command stopped due to an error or timeout in an underlying command.3
Command stopped due to user which specify an invalid option.4
Command stopped due to user which specify a bad option value.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Examples
1. To retrieve the merged trace.summaries of IBM.RecoveryRM and IBM.GblResRM on all onlinenodes for the last day, enter:
samlog
2. To display the raw and detailed trace of IBM.GblResRM on node1 within the last 15 minutes, enter:
samlog -n node1 -s G -d -r -t 15m
3. To create a file that is called RecSum in the current directory which contains the merged tracesummaries of IBM.RecoveryRM on node1 and node2 for 10 minutes started 1 hour ago, enter:
samlog -n node1,node2 -s R -t 1h+10m 1>RecSum
118 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
4. To display the samlog trace and create a file /tmp/sum0815 with the trace.summaries ofIBM.RecoveryRM and IBM.GblResRM on all online nodes that are related to Res0815 between startdate 06/21/10 10:00:00 and end date 06/21/10 12:30:00, enter:
samlog -e "Res0815" -t 2010-06-21.10,2010-06-21.12.30 -T 1>/tmp/sum0815
5. To display the merged trace.summaries of IBM.RecoveryRM and IBM.GblResRM on all nodes ofthe domain prod from a previously collected ctsnap directory /tmp/ct_data, enter:
samlog -t all --dir /tmp/ct_data --dom prod
6. To produce a samlog trace file /tmp/samlog.trace, for example, for finding out why the specifiedoptions are not accepted, enter:
samlog -T 2>/tmp/samlog.trace
Files/usr/sbin/rsct/bin/samlog
Location of the samlog command.
See Also
The ctsnap command.
sampolicy
Name
sampolicy - Checks if the policy in an input file is valid, activates the policy from this file, updates thecurrent policy from the input file, and deactivates the current policy. Also saves the current policy to a filein XML format and can retrieve the policy information from this file. For more information, see
Synopsis
sampolicy -h
sampolicy –w Templatefilename
sampolicy –w –m TemplatefilenameNew TemplatefilenameOld
sampolicy [-T] [-V] [-q] [-f] [-forcecreate] -a Filename
sampolicy [-T] [-V] [-q] [-forcecreate] -u Filename
sampolicy [-T] [-V] [-q] [-f] [-forcecreate] -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] [-forcecreate] -a -t Templatefilename
sampolicy [-T] [-V] [-q] [-forcecreate] -u -t Templatefilename
sampolicy [-T] [-V] [-q] [-f] [-forcecreate] -r -t Templatefilename
sampolicy [-T] [-V] [-u] -c -t Templatefilename
sampolicy [-T] [-V] -i -t Templatefilename
Chapter 2. Reference 119
Description
The sampolicy command is a Java utility program that reads the System Automation for MultiplatformsXML policy from an XML document file, parse, validate, and send the configuration requests to theRecoveryRM daemon and other referenced RSCT resource managers (for example GlobalResRM) withinthe RSCT peer domain. The sampolicy command can also be used to save a snapshot of the currentSystem Automation for Multiplatforms configuration to an XML document file.
Options
-hHelp. Writes the command's usage statement to standard output.
-wSAP Central Services high availability policy feature only: Starts the Policy Setup wizard. You mustconfigure the policy pool before you can use the wizard.
-mSAP Central Services high availability policy feature only: Starts the Policy Setup wizard with amigration between an old and a new template file. All values of the old template file are copied to thenew template file and the wizard proceeds based on the new file with the copied values. If othervalues are required in the new template, they are marked in the wizard parameter overview with theflag Missing and a value question.
-TTrace. Writes the command's trace messages to standard error. For your software-serviceorganization's use only.
-VWrites the command's verbose messages to standard output.
-qQuiet mode, no interaction.
-fUses force to remove resources. Use this option with all tasks that remove resources like activate,deactivate, update, or remove. This option removes resources that are not in state offline or failedoffline.
-forcecreateUses force to create resources. Use this option with all tasks that create resources like activate,update, or remove. This option creates user-defined IBM.AgFileSystem resources for alreadyharvested file systems.
-aActivates the policy from a file. All existing resources are deleted.
-dDeactivates the active policy. All existing resources are deleted.
-uUpdates the active policy from a file without stopping any resource. All existing resources are eithermodified or kept unchanged. New resources are added to the policy.
-rUpdates the active policy from a file and removes all resources not in the file. All resources that arenot deleted are not stopped either. This option is like the option -u followed by the deletion of allresources not part of the file.
-sSaves the current configuration in XML format to a file. The file name must contain ASCII charactersonly.
-cChecks if the policy in the input file is valid.
-iRetrieves the policy information from a file.
120 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
-tRuns template processing before any other task is started. When you use this option, the input filemust be a template in XML format. Template processing is described in System Automation forMultiplatforms Administrator's and User's Guide.
ParametersFilename
Name of the file or absolute path of the file name that contains the policy XML. Filename is requiredfor the options -a, -c, -i, -u, and -r. If no file name is provided for the -s option, the default pathis /var/ct/{domain-name}/cfg. The default file name issampolicy<month><day><year><time>.xml. If you specify a file name without a path,sampolicy tries to load the file from the current working directory.
TemplatefilenameName of the file or absolute path of the file name that contains the policy XML template.Templatefilename is required for the option -t and -w. If you specify a file name without a path,sampolicy tries to load the file from the current working directory.
TemplatefilenameNewName of the file or absolute path of the new template file. This parameter is required for option -w -m.If you specify a file name without a path, sampolicy tries to load the file from the current workingdirectory.
TemplatefilenameOldName of the file or absolute path of the old template file that contains values to be merged into a newtemplate file. This parameter is required for option -w -m. If you specify a file name without a path,sampolicy tries to load the file from the current working directory.
Security
This command requires root authority, or a user ID with appropriate permissions.
Examples
1. To activate a policy, enter:
sampolicy -a /usr/xml/myPolicy.xml
2. To deactivate a policy, enter:
sampolicy -d
3. To save the policy to a file, enter:
sampolicy -s /usr/xml/currentpolicy.xml
4. To update a policy from a template, enter:
sampolicy -u -t /usr/xml/myTemplate.xml
Files
/usr/sbin/rsct/bin/sampolicyLocation of the sampolicy command.
Exit Status
0The command completed successfully.
1Command parsing failed.
Chapter 2. Reference 121
2Command processing failed.
3Java run time not found.
samsimul
Name
samsimul - Simulates a series of requests or state changes and displays the expected results.
Synopsis
samsimul [-h][-T][-V] [Input_file_name]
Description
The samsimul command simulates a series of requests against the automation engine or operationalstate changes of individual resources. If an input file name is given, samsimul reads a description of therequests or state changes to be simulated from the specified file. If the input file name is omitted,samsimul reads that description from standard input.
Upon completion of the simulation, samsimul writes the expected results of the simulated requests orstate changes to standard output.
Options
-hWrites the command's usage statement to standard output.
-TWrites the command's trace messages to standard error. For your software-service organization's useonly.
-VWrites the command's verbose messages to standard output.
ParametersInput_file_name
Specifies the name of a file that contains a description of the requests or state changes to besimulated. Each line of the file describes a single request by means of six space-separated values:
1. The name of the resource or resource group to be started, stopped, canceled, moved, orconsidered failed, online, or offline.
2. A sequence number denoting the relative point in time when the request would be submitted.Multiple requests with identical sequence numbers would be submitted simultaneously.
3. A priority code stating the relative importance of the request with regard to other requests withinthe resource structure. Possible values are "low", "high", and "force".
4. An action code denoting the type of request or state change to be simulated by the automationengine. Possible values are "start", "stop", "move", "cancel", "failed", "online", and "offline".
5. An originator code denoting the source of the request. Possible values are "Operator", "ExtSched",and "Automation".
6. A comma-separated list of nodes to which the request or state change applies.
Lines beginning with the "#" character (hash mark) are considered comments instead of request orstate change descriptions. These can be used as annotations and are disregarded by samsimul.Empty lines, including those containing only space or tab characters, may be used to visuallystructure the input file and are disregarded by samsimul.
122 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see System Automation for Multiplatforms Administrator's and User's Guide.
Exit Status
0The command ran successfully.
1Error occurred with RMC.
2Error occurred with CLI script.
3Incorrect flag on command line.
4Incorrect parameter on command line.
5Error occurred with RMC that was based on faulty command line input.
Examples
1. To simulate a resource start and subsequent failure, enter:
samsimul input_file
With input_file containing the following lines:
IBM.ResourceGroup:samba 0 high start Operator node1IBM.Application:samba:samba1 1 high failed Operator node1
These two lines simulate an online request against the samba resources group, followed by a failure ofits first resources. The response should be:
samba/ResGroup/IBM.ResourceGroup 1 offlinesamba1/Fixed/IBM.Application/node1 1 onlinesamba/ResGroup/IBM.ResourceGroup 1 onlinesamba/ResGroup/IBM.ResourceGroup 2 onlinesamba1/Fixed/IBM.Application/node2 1 onlinesamba/ResGroup/IBM.ResourceGroup 2 online
The first column refers to the resource, the second to the step number, and the last to the currentstate. In the first step, the resource group goes from offline to online. Due to the simulated failure ofsamba1 on the first node it goes back to offline, but the failover takes place and samba1 on the secondnode is started.
Files
/usr/sbin/rsct/bin/samsimulLocation of the samsimul command.
See Also
The addrgmbr, samctrl, chrel, chrg, chrgmbr, mkrg, mkrel, rmrel, rmrg, rmrgmbr commands.
The rmccli General Information file.
The Resource_Data_Input file
Chapter 2. Reference 123
samwhy
Name
samwhy - Displays information about errors that are detected by System Automation for Multiplatforms.
Synopsis
samwhy [-dhv] [-t hh[:mm[:ss]] | <#>h|m|s] [Resource_class:Resource_name[:node]]
Description
The command samwhy helps the operator to understand what happened to the applications and it alsoexplains why System Automation for Multiplatforms reacted the way it did. samwhy uses the history ofevents and the history of automation decisions of System Automation for Multiplatforms and provides areadable and easy-to-understand output. The output lists the application failures that are detected bysamwhy in the specified time and logs.
Options-d, --detail
Display detailed error information.-h, -?
Display brief help information.-t TIME
Specify time duration. Available formats:
<#>h|m|s show last <#> hours|minutes|seconds
hh[:mm[:ss]] show last hours:minutes:seconds
-vDisplay build date and version.
--helpDisplay extended help information.
--nocolorDo not use colors in the output.
Exit Status0
The command ran successfully.1
Command stopped due to an error or timeout in an underlying command or due to user, whichspecifíes an invalid option.
Security
This command does not require root authority. For more information, see System Automation forMultiplatforms Administrator's and User's Guide.
Examples
1. Display errors, which occur in the specified time frame:
samwhy -t 20h (last 20 hours)samwhy -t 45m (last 45 minutes)samwhy -t 55s (last 55 seconds)
124 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
samwhy -t 20:45 (last 20 hours and 45 minutes)samwhy -t 20:45:55 (last 20 hours, 45 minutes and 55 seconds)
2. Display error details of the specified resource class, resource, and node:
samwhy -d IBM.Application:Res1:Node1 (resource on this node)samwhy -d IBM.Application:Res1 (aggregate resource)
Files/usr/sbin/rsct/bin/samwhy
Location of the samwhy command.
See Also
The samlog command.
uninstallSAM
Name
uninstallSAM - Uninstalls all components of System Automation for Multiplatforms.
Synopsis
uninstallSAM [-d inst_pkg_dir] [-l log_file]
Description
The uninstallSAM command checks that the domain is offline. All components of System Automationfor Multiplatforms are uninstalled in the proper order, and information about the executed actions arerecorded in a log file. The name of the default log file is /tmp/uninstallSAM.<#>.log, where <#> is asequential number; the highest number identifies the most recent log file. If the domain is online theuninstallation is canceled.
Typically, no options need to be specified. The available options uninstall the component althoughtheuninstallSAM script is not in the package directory (-d). To specify that a log file other than thedefault is used, add the -l option.
Options
-d inst_pkg_dirUninstalls all components based on NLS files in the specified directory although the uninstallSAMscript is not available in the directory. uninstallSAM is not dependent upon the packages to beinstalled, but needs the directory for its message files.
-l log_fileLogs information that is generated by the uninstallSAM command to the specified log file.
--silentSuppress output to the command line.
Exit Status
0The uninstallation completed successfully.
1<package uninstaller> returned a return code other than 0; the return code and thecorresponding message can be found in the log file. <package uninstaller> is:
• AIX: installp• Linux: rpm
Chapter 2. Reference 125
2The peer domain is online. No uninstallation ran.
3uninstallSAM was unable to continue because directories or files were not detected. This returncode also applies if the -d option specifies a directory that does not exist, or if the subdirectory withfiles does not exist.
Security
This command requires root authority.
samnonrootuser
Name
samnonrootuser - samnonrootuser configure local users to run System Automation commands.
Synopsis
samnonrootuser [-h] [-a|-add |-d |--delete] [-V--silent] [-l<log file>] [--local] [--manage group] [ -x| -sa admin] [-g|-group <groupName>] [-gid--gid<groupld>] [<userName>]
Description
The samnonrootuser command configures the user to run System Automation commands, either as'Operator', or as 'Administrator'. In default only the root user is authorized to run System Automationcommands. Running this script adjusts file permissions and RSCT ACL files so that the specified user hasthe appropriate permissions to manage the domain resources.
Options
-hPrint this help.
-a or --addAdd non-root configuration for the specified user. This is the default action for this command.
-d or --delete,Remove non-root configuration for the specified user.
-g or --group <groupName>,The name of the primary group for the specified user account (default: group name = sagroup).
gid <groupId>,The ID of the primary group for the specified user account. (default: group id = 222)
-l <LogFile>,Specify log file name. (default: write no log file).
--local,Run script only on local node. If omitted, the default is to perform changes on all cluster nodes.
--manage-group,Create local UNIX group (if group does not exist) and add specified user to this group. Set group asprimary group for the user. If omitted, the default is to not make any changes to group and user.
-silent,Writes no messages to stdout.
-v,Run script in verbose mode.
-x or --sa-admin,Set ACL permissions for the sa_admin role. If omitted, the default is to set ACL permissions for thesa_operator role.
126 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Parameters
userName
The name of the user account that is configured as non-root cluster user.
Exit Status
0All configurations completed successfully.
1At least one configuration task failed - see print out for details.
Security
This command requires root authority.
Examples
1. To add and authorize user which added to group and node
samnonrootuser -a -l /tmp/user1 --local -x -g groupname username
2. To remove user which is created and added to group
samnonrootuser -d --local -g groupname username
Files
/usr/sbin/rsct/bin/samnonrootuserLocation of the samnonrootuser command.
See Also
The samctrl, chrel, chrg, chrgmbr, lsrg, mkrg, mkrel, rmrel, rmrg, rmrgmbr commands.
The rmccli general information file.
The Resource_Data_Input file
setupAdapterNonRoot
Name
setupAdapterNonRoot.sh configures end-to-end automation adapter to run with a non-root useraccount.
Synopsis
setupAdapterNonRoot.sh [-h] [--local] [--manage-group] [-X| --sa-admin ] [-g| [--group<groupName> username]
Description
The setupAdapterNonRoot configures the SAM adapter to run with a non-root user. It adapts groupownerships and permissions, as well as RSCT security definitions. The command setupadapternonrootmakes the nonrootuser to control and monitor the end-to-end automation adapter. The adapter handlesthe communication between a System Automation for Multiplatforms domain and the System AutomationApplication Manager end-to-end automation server.
Run the script as a user with root permissions:
Chapter 2. Reference 127
Prerequisite checking
It is checked whether a cluster exists, the automation adapter is stopped, and the user account exists. Itis also checked whether the specified group is the primary group of the user account.
Changing group ownerships and permissions
Several files and directory ownerships and permissions need to be changed, because they are initiallycreated for root user access only. For more information, see Changing group ownerships and permissions.
Note: The script changes the group, which owns the file:
/etc/ibm/tivoli/common/cfg/log.properties.
This file might be used by other Tivoli products as well. If one of these products is also run with a non-rootuser account, ensure that the log.properties file is still readable for these products.
Setting appropriate System Automation and RSCT permissions
To allow the non-root user account samadapt to use RSCT Resource Management Control (RMC),permissions must be granted by using the
/var/ct/cfg/ctrmc.acls file
For more information, see Setting appropriate System Automation and RSCT permissions.
Adapting the automation adapter configuration
The non-root user and group are added to the adapter configuration properties. For more information, seeAdapting the automation adapter configuration.
Options
-hPrint this help.
-g or --group<groupName>The name of the primary group for the specified user account.(default: group name = sagroup)
-localRun script only on local node. Optional, if omitted, the default is to perform changes on all clusternodes.
--manage-groupCreate local UNIX group (if group does not exist) and add specified user to this group Set group asprimary group for the user. Optional, if omitted, the default is to not make any changes to group anduser.
-XSet ACL permissions for the sa_admin role. Optional, if omitted the default is to set ACL permissionsfor the sa_operator role.
Security
This command requires root authority, or a user ID with appropriate permissions. For more information,see Setting up non-root user Ids for the command line interface.
Returns
• 0- All configurations completed successfully• 1- At least one configuration task failed - see print out for details• 2- Prerequisites not satisfied - see print out for details
128 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Examples
1. Configure SA MP adapter to run with non-root user "saoperator" and group "sagroup" ("sagroup"already exists).
Prerequisites
User "saoperator" and group "sagroup" exist.
"sagroup" is the primary group for user "saoperator.
setupAdapterNonRoot.sh -g sagroup saoperator
Result:
Configured SA MP adapter non-root user "saoperator" on all cluster nodes.2. Configure SA MP adapter to run with non-root user "saoperator" and group "sagroup" ("sagroup" does
not exist).
Prerequisites
User "saoperator" exists.
setupAdapterNonRoot.sh --manage-group -g sagroup saoperator.
Result:
Group "sagroup" is created on all cluster nodes.
User "saoperator" is added to group "sagroup" on all cluster nodes.
sagroup" is set as primary group for user "saoperator" on all cluster nodes.
Configured SA MP adapter non-root user "saoperator" on all cluster nodes.3. Remove SA MP adapter non-root user configuration
Prerequisites
SA MP adapter non-root user is configured
AIX:
# setupAdapterNonRoot.sh -g system root
Linux:
# setupAdapterNonRoot.sh -g root root
Result:
SA MP adapter non-root user configuration is removed on all cluster nodes.
Files:
/opt/IBM/tsamp/sam/bin/setupAdapterNonRoot.sh
Location of the setupAdapterNonRoot.sh command.
Using expressionsThe information in this section is for advanced users who want to:
• Modify predefined expressions.• Select resources.• Filter audit log records by compiling and running a complex mathematical expression against a set of
values.
Permissible data types, operators, and operator order of precedence are described below. RMC usesthese functions to match a selection string against the persistent attributes of a resource and toimplement the evaluation of an event expression or a rearm expression.
Chapter 2. Reference 129
An expression is similar to a C language statement or the WHERE clause of an SQL query. It is composedof variables, operators, and constants. The C and SQL syntax styles may be intermixed within a singleexpression. The following table relates the RMC terminology to SQL terminology:
RMC SQL
attribute name column name
select string WHERE clause
operators predicates, logical connectives
resource class table
SQL Restrictions
SQL syntax is supported for selection strings, with the following restrictions:
• Only a single table may be referenced in an expression.• Queries may not be nested.• The IS NULL predicate is not supported because there is no concept of a NULL value.• The period (.) operator is not a table separator (for example, table.column). Rather, in this context, the
period (.) operator is used to separate a field name from its containing structure name.• The pound sign (#) is hard-coded as the escape character within SQL pattern strings.• All column names are case-sensitive.• All literal strings must be enclosed in either single or double quotation marks. Bare literal strings are not
supported because they cannot be distinguished from column and attribute names.
Supported Base Data Types
The term variable is used in this context to mean the column name or attribute name in an expression.Variables and constants in an expression may be one of the following data types that are supported by theRMC subsystem:
Symbolic Name Description
CT_INT32 Signed 32-bit integer
CT_UINT32 Unsigned 32-bit integer
CT_INT64 Signed 64-bit integer
CT_UINT64 Unsigned 64-bit integer
CT_FLOAT32 32-bit floating point
CT_FLOAT64 64-bit floating point
CT_CHAR_PTR Null-terminated string
CT_BINARY_PTR Binary data - arbitrary-length block of data
CT_RSRC_HANDLE_PTR Resource handle - an identifier for a resource that is uniqueover space and time (20 bytes)
Structured Data Types
In addition to the base data types, aggregates of the base data types may be used as well. The firstaggregate data type is similar to a structure in C in that it can contain multiple fields of different datatypes. This aggregate data type is referred to as structured data (SD). The individual fields in thestructured data are referred to as structured data elements, or simply elements. Each element of astructured data type may have a different data type which can be one of the base types in the precedingtable or any of the array types discussed in the next section, except for the structured data array.
130 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
The second aggregate data type is an array. An array contains zero or more values of the same data type,such as an array of CT_INT32 values. Each of the array types has an associated enumeration value(CT_INT32_ARRAY, CT_UINT32_ARRAY). Structured data may also be defined as an array but isrestricted to have the same elements in every entry of the array.
Data Types That Can Be Used for Literal Values
Literal values can be specified for each of the base data types as follows:Array
An array or list of values may be specified by enclosing variables or literal values, or both, withinbraces {} or parentheses () and separating each element of the list with a comma. For example: { 1, 2,3, 4, 5 } or ( "abc", "def", "ghi" ).
Entries of an array can be accessed by specifying a subscript as in the C programming language. Theindex corresponding to the first element of the array is always zero; for example, List [2] referencesthe third element of the array named List. Only one subscript is allowed. It may be a variable, aconstant, or an expression that produces an integer result. For example, if List is an integer array, thenList[2]+4 produces the sum of 4 and the current value of the third entry of the array.
Binary DataA binary constant is defined by a sequence of hexadecimal values, separated by white space. Allhexadecimal values comprising the binary data constant are enclosed in double quotation marks.Each hexadecimal value includes an even number of hexadecimal digits, and each pair of hexadecimaldigits represents a byte within the binary value. For example:
"0xabcd 0x01020304050607090a0b0c0d0e0f1011121314"
Character StringsA string is specified by a sequence of characters surrounded by single or double quotation marks (youcan have any number of characters, including none). Any character may be used within the stringexcept the null '\0' character. Double quotation marks and backslashes may be included in strings bypreceding them with the backslash character.
Floating TypesThese types can be specified by the following syntax:
• A leading plus (+) or minus (-) sign• One or more decimal digits• A radix character, which at this time is the period (.) character• An optional exponent specified by the following:
– A plus (+) or minus (-) sign– The letter 'E' or 'e'– A sequence of decimal digits (0-9)
Integer TypesThese types can be specified in decimal, octal, or hexadecimal format. Any value that begins with thedigits 1-9 and is followed by zero or more decimal digits (0-9) is interpreted as a decimal value. Adecimal value is negated by preceding it with the character '-'. Octal constants are specified by thedigit 0 followed by 1 or more digits in the range 0-7. Hexadecimal constants are specified by a leading0 followed by the letter x (uppercase or lowercase) and then followed by a sequence of one or moredigits in the range 0-9 or characters in the range a-f (uppercase or lowercase).
Resource HandleA fixed-size entity that consists of two 16-bit and four 32-bit words of data. A literal resource handleis specified by a group of six hexadecimal integers. The first two values represent 16-bit integers andthe remaining four each represent a 32-bit word. Each of the six integers is separated by white space.The group is surrounded by double quotation marks. The following is an example of a resourcehandle:
Chapter 2. Reference 131
"0x4018 0x0001 0x00000000 0x0069684c 0x00519686 0xaf7060fc"
Structured DataStructured data values can be referenced only through variables. Nevertheless, the RMC commandline interface displays structured data (SD) values and accepts them as input when a resource isdefined or changed. A literal SD is a sequence of literal values, as defined in “Data Types That Can BeUsed for Literal Values” on page 131, that are separated by commas and enclosed in square brackets.For example, ['abc',1,{3,4,5}] specifies an SD that consists of three elements: (a) the string 'abc', (b)the integer value 1, and (c) the three-element array {3,4,5}.
Variable names refer to values that are not part of the expression but are accessed while running theexpression. For example, when RMC processes an expression, the variable names are replaced by thecorresponding persistent or dynamic attributes of each resource.
The elements of a structured data value can be accessed by using the following syntax:
<variable name>.<element name>
For example, a.b
The variable name is the name of the table column or resource attribute, and the element name is thename of the element within the structured data value. Either or both names may be followed by asubscript if the name is an array. For example, a[10].b refers to the element named b of the 11thentry of the structured data array called a. Similarly, a[10].b[3] refers to the fourth element of thearray that is an element called b within the same structured data array entry a[10].
How Variable Names Are Handled
Variable names refer to values that are not part of an expression but are accessed while running theexpression. When used to select a resource, the variable name is a persistent attribute. When used togenerate an event, the variable name is a dynamic attribute. When used to select audit records, thevariable name is the name of a field within the audit record.
A variable name is restricted to include only 7-bit ASCII characters that are alphanumeric (a-z, A-Z, 0-9)or the underscore character (_). The name must begin with an alphabetic character. When the expressionis used by the RMC subsystem for an event or a rearm event, the name can have a suffix that is the '@'character followed by 'P', which refers to the previous observation.
Operators That Can Be Used in Expressions
Constants and variables may be combined by an operator to produce a result that in turn may be usedwith another operator. The resulting data type or the expression must be a scalar integer or floating-pointvalue. If the result is zero, the expression is considered to be FALSE; otherwise, it is TRUE.
Note: Blanks are optional around operators and operands unless their omission causes an ambiguity. Anambiguity typically occurs only with the word form of operator (that is, AND, OR, IN, LIKE, etc.). Withthese operators, a blank or separator, such as a parenthesis or bracket, is required to distinguish the wordoperator from an operand. For example, aANDb is ambiguous. It is unclear if this is intended to be thevariable name aANDb or the variable names a, b combined with the operator AND. It is actuallyinterpreted by the application as a single variable name aANDb. With non-word operators (for example, +,-, =, &&, etc.) this ambiguity does not exist, and therefore blanks are optional.
Table 3 on page 132 provides a summary of the set of operators that can be used in strings:
Table 3. Operators that can be used in strings
Operator Description Left DataTypes
Right DataTypes
Example Notes®
+ Addition Integer,float Integer,float "1+2" results in 3 None
- Subtraction Integer,float Integer,float "1.0-2.0" results in -1.0 None
* Multiplication Integer,float Integer,float "2*3" results in 6 None
132 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Table 3. Operators that can be used in strings (continued)
Operator Description Left DataTypes
Right DataTypes
Example Notes®
/ Division Integer,float Integer,float "2/3" results in 1 None
- Unary minus None Integer,float "-abc" None
+ Unary plus None Integer,float "+abc" None
.. Range Integers Integers "1..3" results in 1,2,3 Shorthand forall integersbetween andincluding thetwo values
% Modulo Integers Integers "10%2" results in 0 None
| Bitwise OR Integers Integers "2|4" results in 6 None
& Bitwise AND Integers Integers "3&2" results in 2 None
~ Bitwisecomplement
None Integers ~0x0000ffff results in0xffff0000
None
^ Exclusive OR Integers Integers 0x0000aaaa^0x0000ffffresults in 0x00005555
None
>> Right shift Integers Integers 0x0fff>>4 results in0x00ff
None
<< Left shift Integers Integers "0x0ffff<<4" results in0xffff0
None
==
=
Equality All but SDs All but SDs "2==2" results in 1
"2=2" results in 1
Result is true(1) or false (0)
!=
<>
Inequality All but SDs All but SDs "2!=2" results in 0
"2<>2" results in 0
Result is true(1) or false (0)
> Greater than Integer,float Integer,float "2>3" results in 0 Result is true(1) or false (0)
>= Greater than orequal
Integer,float Integer,float "4>=3" results in 1 Result is true(1) or false (0)
< Less than Integer,float Integer,float "4<3" results in 0 Result is true(1) or false (0)
<= Less than orequal
Integer,float Integer,float "2<=3" results in 1 Result is true(1) or false (0)
=~ Pattern match Strings Strings "abc"=~"a.*" results in 1 Right operandis interpretedas an extendedregularexpression
Chapter 2. Reference 133
Table 3. Operators that can be used in strings (continued)
Operator Description Left DataTypes
Right DataTypes
Example Notes®
!~ Not patternmatch
Strings Strings "abc"!~"a.*" results in 0 Right operandis interpretedas an extendedregularexpression
=?
LIKE
like
SQL patternmatch
Strings Strings "abc"=? "a%" results in 1 Right operandis interpretedas a SQLpattern
!?
NOT LIKE
not like
Not SQL patternmatch
Strings Strings "abc"!? "a%" results in 0 Right operandis interpretedas a SQLpattern
|<
IN
in
Contains any All but SDs All but SDs "{1..5}|<{2,10}" results in1
Result is true(1) if leftoperandcontains anyvalue fromright operand
><
NOT IN
not in
Contains none All but SDs All but SDs "{1..5}><{2,10}" resultsin 1
Result is true(1) if leftoperandcontains novalue fromright operand
&< Contains all All but SDs All but SDs "{1..5}&<{2,10}" resultsin 0
Result is true(1) if leftoperandcontains allvalues fromright operand
||
OR
or
Logical OR Integers Integers "(1<2)||(2>4)" results in1
Result is true(1) or false (0)
&&
AND
and
Logical AND Integers Integers "(1<2)&&(2>4)" resultsin 0
Result is true(1) or false (0)
134 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Table 3. Operators that can be used in strings (continued)
Operator Description Left DataTypes
Right DataTypes
Example Notes®
!
NOT
not
Logical NOT None Integers "!(2==4)" results in 1 Result is true(1) or false (0)
Default precedence of operatorsWhen integers of different signs or size are operands of an operator, standard C style casting is implicitlyperformed. When an expression with multiple operators is evaluated, the operations are performed in theorder defined by the precedence of the operator. The default precedence can be overridden by enclosingthe portion or portions of the expression to be evaluated first in parentheses ().
For example, in the expression "1+2*3", multiplication is normally performed before addition to producea result of 7. To evaluate the addition operator first, use parentheses as follows: "(1+2)*3". This producesa result of 9. Table 4 on page 135 shows the default precedence rules. All operators in the same table cellhave the same or equal precedence.
Table 4. Default preference rules when using operators
Operators Description
. Structured data element separator
~
!
NOT
not
-
+
Bitwise complement
Logical not
Unary minus
Unary plus
*
/
%
Multiplication
Division
Modulo
+
-
Addition
Subtraction
<<
>>
Left shift
Right shift
Chapter 2. Reference 135
Table 4. Default preference rules when using operators (continued)
Operators Description
<
<=
>
>=
Less than
Less than or equal
Greater than
Greater than or equal
==
!=
=?
LIKE
like
!?
=~
!~ ?=
|
IN
in
NOT IN
not in
Equality
Inequality
SQL match
SQL not match
Reg expr match
Reg expr not match
Reg expr match (compat)
Contains any
Contains none
Contains all
& Bitwise AND
^ Bitwise exclusive OR
| Bitwise inclusive OR
&& Logical AND
|| Logical OR
, List separator
Pattern Matching
Two types of pattern matching are supported; extended regular expressions and that which is compatiblewith the standard SQL LIKE predicate. This type of pattern may include the following special characters:
136 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
• The percentage sign (%) matches zero or more characters.• The underscore (_) matches exactly one character.• All other characters are directly matched.• The special meaning for the percentage sign and the underscore character in the pattern may be
overridden by preceding these characters with an escape character, which is the pound sign (#) in thisimplementation.
Examples of Expressions
Some examples of the types of expressions that can be constructed follow:
1. The following expressions match all rows or resources that have a name which begins with 'tr' andends with '0', where 'Name" indicates the column or attribute that is to be used in the evaluation:
Name =~'tr.*0'Name LIKE 'tr%0'
2. The following expressions evaluate to TRUE for all rows or resources that contain 1, 3, 5, 6, or 7 in thecolumn or attribute that is called IntList, which is an array:
IntList|<{1,3,5..7}IntList in (1,3,5..7)
3. The following expression combines the previous two so that all rows and resources that have a namebeginning with 'tr' and ending with '0' and have 1, 3, 5, 6, or 7 in the IntList column or attribute willmatch:
(Name LIKE "tr%0")&&(IntList|<(1,3,5..7))(Name=~'tr.*0') AND (IntList IN {1,3,5..7})
Coding for XML policy
When specifying expressions in an XML file which may be used as input for the sampolicy command,some characters shown in the following table must be specified in such a way that they are treated asoperators instead as XML control characters.
Table 5. Specifying expressions in an XML file
Character specified in XML like
& &
< <
> >
" "
Policy XML referenceThis chapter describes the XML elements, sub-elements, and attributes that are supported for SystemAutomation for Multiplatforms automation policies.
The following table shows in which version of System Automation for Multiplatforms particular XMLelements became available.
Table 6. Availability of XML elements by product version
XML elementFirst supported in System Automation forMultiplatforms version
<recoveryPolicy> as Attribute of <Members> 3.2.2
Chapter 2. Reference 137
Table 6. Availability of XML elements by product version (continued)
XML elementFirst supported in System Automation forMultiplatforms version
<Options> as sub-element of<IBM.AgFileSystemAttributes>
3.2.1.3
<ConcurrentGroup> 3.1.0.5
<CleanupCommand> as sub-element of<IBM.ApplicationAttributes>
3.1.0.5
<CleanupCommandTimeout> as sub-element of<IBM.ApplicationAttributes>
3.1.0.5
<CleanupNodeList> as sub-element of<IBM.ApplicationAttributes>
3.1.0.5
<CleanupNode> as sub-element of<IBM.ApplicationAttributes>
3.1.0.5
<ProcessCommandString> as sub-element of<IBM.ApplicationAttributes>
3.1.0.5
<MonitorUserName> as sub-element of<IBM.ApplicationAttributes>
3.1.0.5
<NetPrefix> as sub-element of<IBM.ServiceIPAttributes>
3.1.0.1
<AutomationPolicyTemplate>, <var>, and<include>
2.3
<IBM.AgFileSystemAttributes> 2.2.0.1
IBM.AgFileSystem as class value 2.2.0.1
<ClassAttributesReference> as sub-element of<ConstituentResource>
2.2.0.1
All other tags 2.1
In this chapter, the following information is provided for each XML element that is currently supported:Name
The name and a short description of the element.Examples
One or more examples showing how the element is used.Attributes
Descriptions of the element's attributes.Contexts
Children: a list of elements the element can contain.Occurrence
The possible number occurrences of the element.
When you create an XML file, it is recommended to use the official XML policy file templateSAMTemplate.xml located in the /usr/sbin/rsct/samples/policy directory. To use the template,copy the file to your working directory and rename it according to your file naming conventions.
When you create an XML template file, used for template processing, it is recommended to use the officialXML policy file template SAMTopLevelTemplate.xml located in the /usr/sbin/rsct/samples/policy directory. To use the template, copy the file to your working directory and rename it according toyour file naming conventions.
138 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
To create an XML policy file, you can use any commercial, shareware, or free-ware XML or ASCII editorthat allows you to save the file in UTF-8 format. XML files in any other format will be rejected by the policychecker.
If you use an XML editor to create the XML policy file, the editor will create the basic XML policy templatefor you. Additionally, most XML editors have a validation function that ensures that your XML codeconforms to the relevant schema. When you want to use these functions, you must ensure that the XMLeditor knows where to find the relevant schema. The schema for the System Automation forMultiplatforms policy is defined in the files SAMPolicy.xsd and SAMSimpleTypes.xsd. They arelocated in the directory /usr/sbin/rsct/samples/policy. The schema for the System Automationfor Multiplatforms policy template is defined in the files SAMPolicyTemplate.xsd andSAMSimpleTypes.xsd. They are located in the directory /usr/sbin/rsct/samples/policy.
XML special charactersThe characters "&", "<",">", and " " " cannot be used directly for XML property values. If you want to usethese characters, you have to use the replacement text as specified in Table 7 on page 139
Table 7. XML special characters
Character Replacement text
& &
< <
> >
" "
AutomationPolicyTemplateThis topic describes the AutomationPolicyTemplate XML element and provides usage examples.
The AutomationPolicyTemplate element is the starting element of the XML policy template definition andencompasses all other elements.
Example
<AutomationPolicyTemplate productID="SAM" version="4.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 SAMPolicyTemplate.xsd "> <PolicyInformation> <PolicyName>template</PolicyName> <AutomationDomainName>%%domain_name%%</AutomationDomainName> <PolicyToken>1.0</PolicyToken> <PolicyDescription>this is a top-level template policy</PolicyDescription <PolicyAuthor>admin</PolicyAuthor> </PolicyInformation>
<var name="domain_name" value="myDomain"/> <var name="hostname1" value="node1"/> <var name="hostname2" value="node2"/> <var name="network_tiebreaker_IP_address" value="1.23.45.100"/> <var name="name_prefix" value="tsa"/> <var name="ip_address" value="1.23.45.110"/> <var name="ip_mask" value="255.255.255.0"/> <var name="receive_port" value="199"/> <var name="network_interface1" value="eth0"/> <var name="network_interface2" value="eth1"/> <var name="control_script1" value="/usr/bin/policies/ctrl1"/> <var name="control_script2" value="/usr/bin/policies/ctrl2"/>
<include>application1-policy.xml</include> <include>application2-policy.xml</include> <!-- <include>application3-policy.xml</include> -->
</AutomationPolicyTemplate>
Chapter 2. Reference 139
Attributesversion
Mandatory. It identifies the minimum version of Tivoli System Automation which is required to applythis policy XML. The maximum number of characters supported is 32.
xmlnsMandatory, fixed value, "http://www.ibm.com/TSA/Policy.xsd". It identifies the default name spacefor the XML schema.
xmlns:xsiMandatory, fixed value, "http://www.w3.org/2001/XMLSchema-instance". It identifies the XMLschema format for this policy XML.
xsi:schemaLocationMandatory, fixed value, "http://www.ibm.com/TSA/Policy.xsd SAMPolicyTemplate.xsd ". It identifiesthe XML schema. The XML schema contains the syntax rules for a valid XML policy file.
product IDMandatory, fixed value, "SAM". It identifies the kind of policy contained in the AutomationPolicyelement.
ContextsChildren:
PolicyInformation, var , include, ControlInformation
Occurrence
varThe var element provides the possibility to define a variable name and an accompanying value. Whentemplate processing is performed, all occurrences of the value of a variable's name attribute (surroundedby %% characters) within an XML file are replaced with the value of the variable's value attribute.
Example
<AutomationDomainName>%%domain_name%%</AutomationDomainName><var name="domain_name" value="myDomain"/>
Result:
<AutomationDomainName>myDomain</AutomationDomainName>
Attributesname
Mandatory. String value that may appear within an XML file and is replaced with the correspondingvalue of the value attribute during template processing.
valueMandatory. String value that contains the replacement string for the value of the name attribute.
ContextsChildren:
None
Occurrence
0 to multiple times.
140 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
includeThe include element provides the possibility to include XML files that contain one AutomationPolicyelement.
Optional element. The files are then included during template processing. It can contain the full path to afile to be included. It has a maximum of 1024 characters.
Note that the included AutomationPolicy element cannot contain a PolicyInformation sub-element.
Example
<include>/usr/admin/application1-policy.xml</include>
Attributes
None
ContextsChildren:
None
Occurrence
0 to multiple times.
AutomationPolicyThis topic describes the AutomationPolicy XML element, which is the starting element of the XMLpolicy definition, and provides usage examples.
The AutomationPolicy element encompasses all other elements in the XML policy definition.
Example
<AutomationPolicy productID="SAM" version="4.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 SAMPolicy.xsd"> <PolicyInformation> <PolicyName>XML-saved policy</PolicyName> <AutomationDomainName>xdr43</AutomationDomainName> <PolicyToken>1.1.1</PolicyToken> <PolicyDescription>this is the description of the policy -------- 2006 02/23 andersen initial version --------- </PolicyDescription> <PolicyAuthor>Peter Andersen</PolicyAuthor> </PolicyInformation>......</AutomationPolicy>
Attributesversion
Mandatory. It identifies the minimum version of System Automation for Multiplatforms which isrequired to apply this policy XML. The maximum number of characters supported is 32.
xmlnsMandatory, fixed value, http://www.ibm.com/TSA/Policy.xsd. It identifies the default namespace for the XML schema.
xmlns:xsiMandatory, fixed value, http://www.w3.org/2001/XMLSchema-instance. It identifies the XMLschema format for this policy XML.
Chapter 2. Reference 141
xsi:schemaLocationMandatory, fixed value, http://www.ibm.com/TSA/Policy.xsd SAMPolicy.xsd . It identifiesthe XML schema. The XML schema contains the syntax rules for a valid XML policy file.
product IDMandatory, fixed value, "SAM". It identifies the kind of policy contained in the AutomationPolicyelement.
ContextsChildren:
PolicyInformation, ControlInformation, Resource, MoveGroup, ConcurrentGroup,ConstituentResource, ResourceGroup, Relationship, Equivalency,ResourceReference, IBM.AgFileSystemAttributes, IBM.ApplicationAttributes,IBM.ServiceIPAttributes, IBM.TestAttributes, IBM.TieBreaker
PolicyInformationThe PolicyInformation element uses the sub-elements listed in this topic to provide an identification ofthe policy.
Mandatory element.
Note that if you use an AutomationPolicyTemplate, the element PolicyInformation must appear as sub-element of the AutomationPolicyTemplate; it may not appear as sub-element of any includedAutomationPolicy.
Example
<PolicyInformation> <PolicyName> First SAfMP Policy </PolicyName> <AutomationDomainName> Friendly </AutomationDomainName> <PolicyToken> 1.0.1 </PolicyToken> <PolicyAuthor> Michael Atkins </PolicyAuthor> <PolicyDescription> This document contains the policy for Friendly Domain.
Change History: ------------------------------------------------------ Date Name Description ------------------------------------------------------ 01/12/05 Michael Atkins Initial Policy ------------------------------------------------------ </PolicyDescription></PolicyInformation>
Attributes
None
ContextsChildren:
PolicyNameMandatory. Assigns a name to the policy.
AutomationDomainNameMandatory. Specifies the System Automation for Multiplatforms cluster name to which this policyapplies.
PolicyTokenMandatory. Versioning tag defined by the user.
PolicyAuthorOptional. Shows the name of the policy’s author.
142 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
PolicyDescriptionOptional. It may, for example, contain comments like the purpose of the policy XML.
Occurrence
Once.
ControlInformationThe ControlInformation XML element sets the control parameters displayed in the Children section.
Optional element. For System Automation for Multiplatforms, it sets the same parameters as in the“samctrl” on page 109 command.
Example
<ControlInformation> <Timeout>20</Timeout> <RetryCount>5</RetryCount> <ResourceRestartTimeout>30</ResourceRestartTimeout></ControlInformation>
Attributes
None
ContextsChildren:
TimeoutOptional. It specifies the default timeout interval for System Automation for Multiplatformscontrol operations in seconds. Valid values are numbers from 1 to 360. The default value for thiselement is 60.
RetryCountOptional. It specifies the default number of retries an System Automation for Multiplatformscontrol operation can perform before it is treated as failed. Valid values are numbers between 1and 10. The default is 3.
ExcludedNodeDeprecated. Tolerated for compatibility reasons, but ignored since release 3.1.0.3.
ResourceRestartTimeoutOptional. It specifies the timeout in seconds before a failed resource is restarted. Its default is 5and the allowed values are 2 to 360.
EnablePublisherDeprecated. Tolerated for compatibility reasons, but ignored since release 3.1.
Occurrence
0 to 1
ResourceThe Resource XML element describes fixed resources.
Optional element. It is referenced from the elements ResourceGroup, Equivalency, or Relationship.
Example
<Resource name="xdrerpdlnxxdr31" class="IBM.Application" node="lnxxdr31"> <ClassAttributesReference> <IBM.ApplicationAttributes name="Application1"/>
Chapter 2. Reference 143
</ClassAttributesReference></Resource>
Attributes
nameMandatory, user defined. It has a maximum of 64 characters.
nodeMandatory. Name of the node on which the resource runs. It has a maximum of 256 characters.
classMandatory. It can be one of the values IBM.AgFileSystem, IBM.Application, IBM.ServiceIP, orIBM.Test.
These attributes make up an unique key. The ResourceGroup element must use this key to refer to theresource.
ContextsChildren:
ClassAttributesReferenceMandatory. It contains the name of the IBM.AgFileSystemAttributes, IBM.ApplicationAttributes,IBM.ServiceIPAttributes, or IBM.TestAttributes element whose attribute values are to be used forthe resource.
Occurrence
0 to multiple times.
MoveGroupThis topic describes the MoveGroup XML element and provides usage examples.
Optional element. It describes floating resources within the System Automation for Multiplatformsenvironment.
Example
<MoveGroup name="DB2" class="IBM.Application"> <ClassAttributesReference> <IBM.ApplicationAttributes name="Application2"/> </ClassAttributesReference> <Members> <ConstituentResource name="DB2" class="IBM.Application" node="lnxxdr10" /> <ConstituentResource name="DB2" class="IBM.Application" node="lnxxdr11" /> </Members></MoveGroup>
Attributes
nameMandatory, user defined. It identifies the floating resource and has a maximum of 64 characters. Itmust be equal to the names of the ConstituentResource elements.
classMandatory. It can be one of the values IBM.AgFileSystem, IBM.Application, IBM.Test, orIBM.ServiceIP.
These attributes make up the unique key of a move group. A Relationship element must use this key torefer to this move group.
144 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
ContextsChildren:
ClassAttributesReferenceOptional. It contains the name of the IBM.AgFileSystemAttributes, IBM.ApplicationAttributes,IBM.ServiceIPAttributes, or IBM.TestAttributes element whose attribute values are to be used forthose constituents of the move group that do not have their own ClassAttributesReference.
MembersOptional. Members elements can only be constituent resources. For more information, see“ConstituentResource” on page 146.ConstituentResource
It references members of a floating or concurrent resource. The classes IBM.Application,IBM.ServiceIP, IBM.AgFileSystem, and IBM.Test are allowed.
Occurrence
0 to multiple times.
ConcurrentGroupThis topic describes the ConcurrentGroup XML element and provides usage examples.
Optional element. It describes concurrent resources within the System Automation for Multiplatformsenvironment.
Example
<ConcurrentGroup name="apache" class="IBM.Application"> <ClassAttributesReference> <IBM.ApplicationAttributes name=""apache-attributes"/> </ClassAttributesReference> <Members> <ConstituentResource name="apache" class="IBM.Application" node="server1"/> <ConstituentResource name="apache" class="IBM.Application" node="server2"/> </Members></ConcurrentGroup>
Attributes
nameMandatory, user defined. This attribute identifies the concurrent resource. It has a maximum of 148characters. The names of the ConstituentResource member elements must be equivalent to the nameof the ConcurrentGroup.
classMandatory. Possible values are IBM.Application or IBM.Test. These attributes are a unique key of aConcurrentGroup. A relationship element uses this key to refer to this ConcurrentGroup element.
ContextsChildren:
ClassAttributesReferenceOptional. It contains the name of the IBM.ApplicationAttributes or IBM.TestAttributes element,whose attribute values are used for those constituents of the ConcurrentGroup that do not havetheir own ClassAttributesReference. The element has a maximum of 64 characters.
MembersOptional. Members elements can only be constituent resources.ConstituentResource
It references members of a floating or concurrent resource. The classes IBM.Application andIBM.Test are allowed. See “ConstituentResource” on page 146.
Chapter 2. Reference 145
Occurrence
0 to multiple times.
ConstituentResourceThis topic describes the ConstituentResource XML element and provides usage examples.
Optional element. It must be used to describe members of a MoveGroup (floating resources) orConcurrentGroup (concurrent resources).
Examples
Example 1:
<ConstituentResource name="DB2" class="IBM.Application" node="lnxxdr10"/>
Example 2:
<ConstituentResource name="xdrerpdlnxxdr31" class="IBM.Application" node="lnxxdr31"> <ClassAttributesReference> <IBM.ApplicationAttributes name="Application1"/> </ClassAttributesReference></ConstituentResource>
Attributes
nameMandatory, user defined. It must be equal to the name of the MoveGroup or ConcurrentGroupelement as shown in the example section of the MoveGroup or ConcurrentGroup element description.It has a maximum number of 64 characters.
nodeMandatory. Name of the node on which the resource runs. It has maximum number of 256 characters.
classMandatory. It can be one of the values IBM.AgFileSystem, IBM.Application, IBM.Test, orIBM.ServiceIP. For ConcurrentGroup it can be one of the values IBM.Application or IBM.Test.
These attributes make up the unique key of a constituent resource. A MoveGroup or ConcurrentGroupelement must use this key to refer to the resource.
ContextsChildren:
ClassAttributesReferenceOptional. For MoveGroup it contains the name of the IBM.AgFileSystemAttributes,IBM.ApplicationAttributes, IBM.ServiceIPAttributes, or IBM.TestAttributes element whoseattribute values are to be used for the constituent resource. For ConcurrentGroup it contains thename of the IBM.ApplicationAttributes, or IBM.TestAttributes element whose attribute values areto be used for the constituent resource.
The element must be specified when no ClassAttributesReference element is referenced in theconstituent's MoveGroup or ConcurrentGroup. It must also be specified to override the attributesettings in the move or concurrent group's ClassAttributesReference element for the constituentresource.
Occurrence
0 to multiple times.
146 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
ResourceGroupThis topic describes the ResourceGroup XML element and provides usage examples.
Optional element. It describes groups of resources within the System Automation for Multiplatformsenvironment.
Example
<ResourceGroup class="IBM.ResourceGroup" name="erpdgroup"> <DesiredState>Online</DesiredState> <InfoLink>www.ibm.com/TSA/xDR</InfoLink> <Priority>100</Priority> <Members> <Resource name="xdrerpd" class="IBM.Application" node="lnxxdr31" mandatory="true"/> </Members></ResourceGroup>
Attributes
nameMandatory, user defined. It identifies the groups of resources and has a maximum of 64 characters.
classMandatory. It has the fixed value IBM.ResourceGroup.
These attributes make up the unique key of a resource group. A Relationship element must use this key torefer to this resource group.
ContextsChildren:
DesiredStateOptional. Defines the operation state the resource should obtain in the end. System Automationfor Multiplatforms tries to start and keep all resources in a resource group to this state. Validstates are:
• Offline: the resource should be stopped (This is the default value).• Online: the resource should be started.
DescriptionOptional. Provides more information about the resource. See “Description” on page 158 fordetails about the Description element.
OwnerOptional. Provides the name of the resource owner. See “Owner” on page 158 for details aboutthe Owner element.
InfoLinkOptional. Provides a link where more information can be found. See “InfoLink” on page 159 fordetails about the InfoLink element.
MembersOptional. See “Members” on page 157 for details about the Members element. The sub-elementMembers has the following sub-elements:Resource
It references fixed resources for the classes IBM.Application, IBM.ServiceIP, and IBM.Test.ResourceReference
It references RSCT IBM.AgFileSystem resources.MoveGroup
It references a floating resource.
Chapter 2. Reference 147
ConcurrentGroupIt references a concurrent resource.
ResourceGroupIt references an inner resource group.
MemberLocationOptional. It specifies the default location of resources in the resource group. Allowed values areNone and Collocated. Collocated is the default.
PriorityOptional. It specifies the priority of this resource group in relation to other resource groups. Thissub-element is used to resolve conflicts. Its default is 0 and the allowed values are 0 to 200.
AllowedNodeOptional. It specifies the set of nodes the resources of a resource group are allowed to run on.Allowed values are All, a name of one node or the name of an equivalency of nodes. All is thedefault.
ExcludedNodeOptional. It specifies one entry of the list of excluded nodes. This element may occur up to ntimes. Its maximum number of characters is 256.
Occurrence
0 to multiple times.
RelationshipThis topic describes the Relationship XML element and provides usage examples.
Optional element. It describes the relationships between resources in a cluster.
Examples
<Relationship name="MoveGroupStartAfterResource1"> <Source> <MoveGroup name="movegroupname" class="IBM.Application"/> </Source> <Target> <Resource name="resource1" class="IBM.Application" node="node1"/> </Target> <Type>StartAfter</Type></Relationship>
<Relationship name="Resource2CollocatedResource1"> <Source> <ResourceGroup name="resourcegroup2" class="IBM.ResourceGroup"/> </Source> <TargetClass>IBM.Application</TargetClass> <TargetSelectString>ResourceType==1</TargetSelectString> <Type>Collocated</Type></Relationship>
Attributes
nameOptional but recommended. Not required as the Relationship element may not be referenced by anyother XML element. However, if there are several managed relationships with the same sourceresource, then it is recommended to specify a name for the managed relationship. Otherwise therelationships will be consolidated into one managed relationship after a policy save and restoreaction.
It has a maximum of 64 characters.
148 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
ContextsChildren:
TypeMandatory. Describes the relationships used for defining the start/stop behaviors and the locationrelationships. For more information, see the command “mkrel” on page 78.
ConditionOptional. Can be specified for all location relationships except IsStartable. The IfPossiblecondition is only valid for relationships of type StartAfter. For more information, see the command“mkrel” on page 78.
SourceOptional. A Relationship element must contain a source which can be specified either by naming aspecific source resource or by specifying a selection. The source resource can be specified by thisSource element.
The source of a relationship may be a fixed resource, resource group, concurrent group, resourcereference, or move group. The Source resource must be a member of a resource group.
The selection can be specified by using the sub-elements SourceClass and SourceSelectStringdescribed further down in this list.
SourceClassOptional. It is mutually exclusive with Source and it is required with SourceSelectString. It has amaximum number of 64 characters.
SourceSelectStringOptional. It is mutually exclusive with Source and it is required with SourceClass. It has amaximum number of 1024 characters.
TargetOptional. A Relationship element must contain a Target which can either be specified by namingone target resource or by specifying a selection. The target resource can be specified by thisTarget sub-element. Target may be a fixed resource, a resource group, a resource reference, amove group, a concurrent group, or an equivalency.
The selection can be specified by using the sub-elements TargetClass and TargetSelectStringdescribed further down in this list.
TargetClassOptional. It is mutually exclusive with Target and it is required with TargetSelectString. It has amaximum number of 64 characters.
TargetSelectStringOptional. It is mutually exclusive with Target and it is required with TargetClass. It has a maximumnumber of 1024 characters.
Occurrence
0 to multiple times.
EquivalencyThe equivalency element describes a collection of resources providing the same functionality.
Optional element. An equivalency consists of a set of fixed resources from the same resource class.
Examples
<Equivalency name="NetworkInterfaces" class="IBM.Equivalency"> <Members> <ResourceReference name="Ref-eth0-lnxxdr01" /> <ResourceReference name="Ref-eth0-lnxxdr02" /> <ResourceReference name="Ref-eth0-lnxxdr03" /> </Members> <MinimumNecessary>2</MinimumNecessary>
Chapter 2. Reference 149
</Equivalency>
<Equivalency name="DynamicNI" class="IBM.Equivalency"> <DynamicSelectString>Name like "eth%"</DynamicSelectString> <MemberClass>IBM.NetworkInterface</MemberClass> <MinimumNecessary>3</MinimumNecessary></Equivalency>
Attributes
nameMandatory, user defined. The string in this attribute identifies the Equivalency element. It hasmaximum number of 64 characters.
classMandatory. It has the fixed value IBM.Equivalency.
These attributes make up the unique key of an equivalency. A Relationship element must use this key torefer to this equivalency.
ContextsChildren:
MemberClassOptional. The MemberClass element determines the class of all members of the equivalency. It ismutually exclusive with the Members element. It is required with the elementsDynamicSelectString and StaticSelectString. MemberClass has a maximum number of 64characters.
DynamicSelectStringOptional. It is mutually exclusive with the element Members and StaticSelectString, and it isrequired with the element MemberClass if no StaticSelectString is specified. It dynamicallydetermines which resources are contained within the Equivalency. If matching resources arecreated after the Equivalency has been created, they are dynamically added to the Equivalency.Maximum number of characters supported is 1024.
StaticSelectStringOptional. It is mutually exclusive with the elements Members and DynamicSelectString and isrequired with the element MemberClass if no DynamicSelectString is specified. It determineswhich resources are contained within the Equivalency. Maximum number of characters supportedis 1024. For more information on how to specify select strings, see the System Automation forMultiplatforms Administrator's and User's Guide.
MembersOptional. Specifies a fixed resource or a resource reference multiple times. It is mutually exclusivewith the elements MemberClass,StaticSelectString and DynamicSelectString. See “Members” onpage 157. The sub-element Members has the following sub-elements:Resource
It references fixed resources for the classes IBM.Application, IBM.ServiceIP, and IBM.Test.ResourceReference
It references RSCT resources for the classes IBM.NetworkInterface, IBMAgFileSystem, orIBM.PeerNode.
MinimumNecessaryOptional. It specifies the minimum necessary number of members to make an equivalency valid.The default is 1. Valid numbers are from 0 to 100.
SelectFromPolicyOptional. Specifies the policy to be used when making a selection from the Equivalency element.Allowed values are Ordered and Any:
• The default value is Any. "Any" means no specific order.
150 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
• Ordered means that the selection starts at the beginning. Ordered may not be used togetherwith DynamicSelectString.
Additional, optional values are Failback, NoFailure and NoControl:
• They can only be used in conjunction with the value Any or Ordered.• Failback means that the resources are always started on the first member, if it is available. The
value Failback can only be used in conjunction with the value Ordered.• When the value NoFailure is specified, the OpState of resources that have a dependency against
the equivalency will not be forced to Failed Offline, if they could not be started within thespecified timeout interval.
• NoControl means that System Automation will neither start nor stop the members of theequivalency but only react to changes of the OpState of these resources.
The optional additional values are specified as described in the following example:
<SelectFromPolicy>Any,NoControl</SelectFromPolicy><SelectFromPolicy>Ordered,Failback,NoControl</SelectFromPolicy>
Occurrence
0 to multiple times.
ResourceReferenceThis topic describes the ResourceReference XML element and provides usage examples.
Optional element. It is used for resources that are outside the management scope of System Automationfor Multiplatforms: for example, RSCT resources like IBM.NetworkInterface, or automatically harvestedresources of the class IBM.AgFileSystem.
Example
<ResourceReference name="eth0"> <ReferencedResource> <Name>eth0</Name> <Class>IBM.NetworkInterface</Class> <Node>lnxxdr01</Node> </ReferencedResource></ResourceReference>
Attributes
nameMandatory. The string in this attribute identifies the ResourceReference element. It must be uniqueand has a maximum of 64 characters. A Relationship or Equivalency element must use this name torefer to the resource.
ContextsChildren:
ReferencedResourceMandatory. Describes a resource outside this XML. It consists of these elements:Name
Mandatory. It specifies the actual name of the resource. It has a maximum number of 64characters.
NodeMandatory. It specifies the location of the resource. It has a maximum number of 256characters.
For floating resources, the Node element is empty.
Chapter 2. Reference 151
ClassMandatory. It describes the type of the resource. It has a maximum number of 64 characters
Occurrence
0 to multiple times.
IBM.AgFileSystemThe IBM.AgFileSystem element is used to specify the attribute values for user-defined storageresources of class IBM.AgFileSystem.
Optional element. An IBM.AgFileSystem element can be referenced in multiple Resource,ConstituentResource, or MoveGroup elements to assign the attributes values to the resources.
Note that automatically harvested file system resources can only be specified as referenced resources inResourceReference elements and that their attributes cannot be set in a policy.
Example
<IBM.AgFileSystem name="FileSystem1"> <DeviceName>/dev/sda3</DeviceName> <Vfs>ext2</Vfs> <MountPoint>/nfs-mount</MountPoint> <PreOnlineMethod>0</PreOnlineMethod></IBM.AgFileSystem>
Attributes
nameMandatory. Must be unique and can have a maximum of 64 characters.
The name can be used in one or multiple Resource, ConstituentResource, or MoveGroupelements to assign the values defined in the particular IBM.AgFileSystem element to theseresources. The name is only used in XML policy handling, not as an actual name within the cluster.
Contexts
The sub-elements listed below can be used to set the attribute values for user-definedIBM.AgFileSystem resources. For a detailed description of the attributes, see RSCT AdministrationGuide, SA22-7889.
Children:DeviceName
Mandatory. String value. It has a maximum of 1024 characters.Vfs
Mandatory. String value. It has a maximum of 1024 characters.MountPoint
Optional. String value. It has a maximum of 1024 characters.PreOnlineMethod
Optional. Integer value between 0 and 3. Default is 0.ProtectionMode
Optional. Allowed values are 0 and 1. Default is 1.
• 0 : Resource is non-critical.• 1 : Resource is critical. If the resource is critical, IBM.ConfigRM decides whether the resource
can be started as requested. A critical resource can never be online on more than one node at atime.
OptionsOptional. String value. It has a maximum of 1024 characters.
152 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Occurrence
0 to multiple times.
IBM.ApplicationThis topic describes the IBM.Application XML element and provides usage examples.
Optional element. It is used to specify the attributes of a resource of the class IBM.Application.
Example
<IBM.Application name="Application1"> <StartCommand>/usr/sbin/rsct/bin/xdrstarterpd</StartCommand> <StopCommand>/usr/sbin/rsct/bin/xdrstoperpd</StopCommand> <MonitorCommand>/usr/sbin/rsct/bin/xdrmonitorerpd</MonitorCommand> <StartCommandTimeout>10</StartCommandTimeout> <StopCommandTimeout>10</StopCommandTimeout> <RunCommandsSync>0</RunCommandsSync> <UserName>root</UserName></IBM.Application>
Attributes
nameMandatory. Must be unique and has a maximum of 64 characters. A Resource,ConstituentResource, ConcurrentGroup, or MoveGroup element can refer to this name.
Contexts
See the System Automation for Multiplatforms Administrator's and User's Guide for a detailed descriptionof the following elements.
Children:StartCommand
Mandatory. String value. It has a maximum of 1024 characters.StopCommand
Mandatory. String value. It has a maximum of 1024 characters.MonitorCommand
Mandatory. String value. It has a maximum of 1024 characters.UserName
Mandatory. String value. It has a maximum of 1024 characters.StartCommandTimeout
Number of seconds the StartCommand can run before it is stopped with killpg(). It alsospecifies the time after which the resource is expected to be online. The default value is 5seconds.
StopCommandTimeoutNumber of seconds the StopCommand can run before it is stopped with killpg(). It alsospecifies the time after which the resource is expected to be online. The default value is 5seconds.
MonitorCommandTimeoutNumber of seconds the MonitorCommand can run before it is stopped with killpg(). Thedefault value is 5 seconds.
MonitorCommandPeriodThe value specifies the time period (seconds) between the invocations of the MonitorCommand.This period starts after the prior invocation completes. The default value is 10 seconds.
RunCommandsSyncOptional. RunCommandsSync is an integer between 0 and 255. Default is 1.
Chapter 2. Reference 153
ProtectionModeOptional. Allowed values are 0 and 1. Default is 0.
• 0 : Resource is non-critical.• 1 : Resource is critical. If the resource is critical, IBM.ConfigRM decides whether the resource
can be started as requested. A critical resource can never be online on more than one node at atime.
CleanupCommandOptional. String value. It has a maximum of 1024 characters. Reserved for future use.
CleanupCommandTimeoutOptional. Positive integer value with a default of 10, if the cleanup command is set. Reserved forfuture use.
CleanupNodeListOptional. It is the parent element for multiple optional CleanupNode elements. At least oneCleanupNode element must be specified. Reserved for future use.
CleanupNodeOptional subelement of CleanupNodeList. It specifies one entry of the list of node names forwhich the cleanup command of this resource is allowed to run. This element may occur up to ntimes. Its maximum number of characters is 256. Reserved for future use.
ProcessCommandStringOptional. If the command strings of processes in the process table are not empty, then they arecompared with the string specified in ProcessCommandString. If the command strings match, theresource state is online. String value. It has a maximum of 1024 characters.
MonitorUserNameOptional. The monitor command runs in the security context of the user ID specified inMonitorUserName. If this attribute is empty, the user ID specified in UserName is taken instead.String value. It has a maximum of 1024 characters.
Occurrence
0 to multiple times.
IBM.ServiceIPThis topic describes the IBM.ServiceIP XML element and provides usage examples.
Optional. This element is used to specify the attributes of a resource of the class IBM.ServiceIP.
Examples
Example 1: IPv4 IP address
<IBM.ServiceIP name="ServiceIPOne"> <IPAddress>9.164.178.1</IPAddress> <NetMask>255.255.255.0</NetMask> <ProtectionMode>0</ProtectionMode></IBM.ServiceIP
Example 2: IPv6 IP address
<IBM.ServiceIP name="IBM.ServiceIP.S2" > <IPAddress>fd00:9:152:48:4020:ffff:21:218</IPAddress> <NetPrefix>70</NetPrefix> <ProtectionMode>1</ProtectionMode></IBM.ServiceIP>
154 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Attributes
nameMandatory. Must be unique and has a maximum of 64 characters. A Resource, ConstituentResource,or MoveGroup element can refer to this name.
Contexts
See the System Automation for Multiplatforms Administrator's and User's Guide for a detailed descriptionof the following elements.
Children:IPAddress
Mandatory. String value. For IPv4, the IP address must be specified in dotted decimal notation; forexample, 9.152.80.251. For IPv6, you can use the standard formats for IPv6 addresses; forexample, 2001:db8::1428:57ab. Note that for IPv6, link-local addresses are not allowed for thisattribute.
NetMaskOptional. String value. Must be a Netmask specified in dotted decimal notation. NetMask is onlyvalid for IPv4 addresses. For IPv6 addresses, use the NetPrefix attribute.
NetPrefixOptional. Integer value between 0 and 128. This attribute specifies the netprefix value of the IPv6address given in the IPAddress attribute and thus is only valid for IPv6 addresses. It replaces theNetMask attribute for IPv6. This attribute takes integer values only; for example, 80. Do notspecify a forward slash or other characters in front of the number value.
ProtectionModeOptional. Allowed values are 0 and 1. Default is 1.
• 0 : Resource is non-critical.• 1 : Resource is critical. If the resource is critical, IBM.ConfigRM decides whether the resource
can be started as requested. A critical resource can never be online on more than one node at atime.
Occurrence
0 to multiple times.
IBM.TestThis topic describes the IBM.Test XML element and provides usage examples.
Optional. It is used to specify the attributes of a resource of the class IBM.Test.
Example
<IBM.TestAttributes name="TestOne"> <TimeToStart>15</TimeToStart> <WriteToSyslog>0</WriteToSyslog></IBM.TestAttributes>
Attributes
nameMandatory. Must be unique and has a maximum of 64 characters. A Resource, ConstituentResource,or MoveGroup element can refer to this name.
Contexts
See the System Automation for Multiplatforms Administrator's and User's Guide for a detailed descriptionof the following elements.
Chapter 2. Reference 155
Children:ForceOpState
Deprecated. Tolerated for compatibility reasons, but ignored since release 3.1.TimeToStart
Optional. Positive integer value. Amount of time (in seconds) before a test resource changes itsoperational state from pending online to online after receiving a start command. The default valueis 0, indicating that the resource goes online immediately.
TimeToStopOptional. Positive integer value. Amount of time (in seconds) before a test resource changes itsoperational state from pending offline to offline after receiving a stop command. The default valueis 0, indicating that the resource goes offline immediately.
WriteToSyslogOptional. The default is 0, and the allowed values are either 0 or 1.
• 0 : Events are not written to the syslog.• 1 : Events are written to the syslog.
Occurrence
0 to multiple times.
IBM.TieBreakerThis topic describes the IBM.TieBreaker XML element and provides usage examples.
Optional. It is used to specify the attributes of a resource of the class IBM.TieBreaker.
Example
<IBM.TieBreaker name="BreakIt" class="IBM.TieBreaker"> <Type>SCSI</Type> <DeviceInfo>ID=4 LUN=0</DeviceInfo> <HeartbeatPeriod>7</HeartbeatPeriod> <NodeInfoList> <NodeInfo node="lnxxdr10" info="HOST=0 CHAN=0"/> <NodeInfo node="lnxxdr10" info="HOST=2 CHAN=2"/> </NodeInfoList></IBM.TieBreaker>
Attributes
nameMandatory. The string in this attribute identifies the IBM.TieBreaker element. It has maximumnumber of 64 characters.
classMandatory. It has the fixed value IBM.TieBreaker.
These attributes make up the unique key of an IBM.TieBreaker. This element cannot be referenced.
ContextsChildren:
TypeMandatory. Allowed values are Operator, Fail, SCSI, ECKD, EXEC, and DISK.
PreReserveWaitTimeOptional. Non-negative integer value, the default is 0.
PostReserveWaitTimeOptional. Non-negative integer value, the default is 0.
156 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
ReleaseRetryPeriodOptional. Non-negative integer value, the default is 0.
HeartbeatPeriodOptional. Non-negative integer value, the default is 0.
DeviceInfoOptional. String value. It has a maximum of 1024 characters.
ReprobeDataOptional. String value. It has a maximum of 1024 characters.
NodeInfoListOptional. Occurs 0 or once, and consists of 0 to n NodeInfo elements.NodeInfo
Contains the node attribute and an info attribute. The maximum number of characterssupported is 1024 for both attributes.
ActiveOptional, type Boolean, valid values are true and false, default is false. Only one instance of anIBM.TieBreaker element may have the value true for this element. This one is theIBM.TieBreaker that is activated in the cluster via the command:
chrsrc -c IBM.PeerNode OpQuorumTieBreaker="name"
Occurrence
0 to multiple times.
MembersThis topic describes the Members XML element and provides usage examples.
The Members element must be used within a resource group, a concurrent group, and within a movegroup. It may also be used within an equivalency.
Note that if used within a resource group, this element can have the attributes shown under 'Attributes'.
Example
<ResourceGroup class="IBM.ResourceGroup" name="db2-group"> <DesiredState>Online</DesiredState> <InfoLink>www.ibm.com/TSA/xDR</InfoLink> <Members> <MoveGroup name="db2floating" class="IBM.Application" selectFromPolicy="Any"> </Members> <AllowedNode>ALL</AllowedNode></ResourceGroup>
Attributesmandatory
Optional. Allowed values for this attribute are true and false, true is the default. Every resource that ismandatory must be online in order to get the whole group online.
selectFromPolicyOptional. The selectFromPolicy attribute can only be set for members that are move groups orconcurrent groups. It specifies the policy used to select a member from the member list of a move orconcurrent group.
Note: The selectFromPolicy attribute is ignored if the group member is a harvestedIBM.AgFileSystem resources.
Possible values:
Chapter 2. Reference 157
AnyNo specific order needs to be observed.
OrderedDefault value. The selection starts at the beginning.
Ordered has the additional value Failback for move groups only.
FailbackOptional. The resources always start with the first member, if this member is available. Theelement Failback can only be used with the element Ordered. For example:
<SelectFromPolicy>Ordered,Failback</SelectFromPolicy>
recoveryPolicyOptional. Can be used to specify the RecoveryPolicy attribute that defines how a member failure isrecovered. Possible values:AutomaticRecovery
Automatically recover from the failure. This is the default.LockOnResFailure
Submit a Lock request on the resource group if the member fails. Automatically recover themember if the node hosting the member fails.
LockOnAnyFailureSubmit a Lock request on the resource group if the member or the hosting node fails.
Contexts
None.
DescriptionThis topic describes the Description XML element and provides usage examples.
Optional element. It may contain comments like ASCII text describing the purpose of the element whereit is embedded. It has a maximum number of 1024 characters.
This element can be used only as sub-element within the ResourceGroup element. It can occur 0 timesor once under one parent element
Example
<Description> FixedResource - This is the error reporting daemon of xDR </Description>
Attributes
None.
Contexts
None.
OwnerThis topic describes the Owner XML element and provides usage examples.
Optional element. It may contain contact information about the owner of the element where it isembedded. This element can be used only as sub-element within the ResourceGroup element. Thiselement may occur 0 times or once under one parent element. It has a maximum number of 1024characters.
158 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Example
<Owner>Paul Meyer</Owner>
Attributes
None.
Contexts
None.
InfoLinkThis topic describes the InfoLink XML element and provides usage examples.
Optional element. It specifies the URL of a HTML page which shows additional information about theelement where it is embedded. This element can be used only as sub-element within theResourceGroup element. This element may occur 0 times or once under one parent element. It has amaximum number of 1024 characters.
Example
<ResourceGroup class="IBM.ResourceGroup" name="db2-group"> <DesiredState>Online</DesiredState> <InfoLink>www.ibm.com/TSA/xDR</InfoLink> <AllowedNode>ALL</AllowedNode></ResourceGroup>
Attributes
None.
Contexts
None.
Example XML policyThis section shows an example XML policy for the resource group WebServerGroup that is depicted inFigure 2 on page 159. The resource group comprises the three move groups "apache1", "local_mount",and "ha-ip-adress", and the harvested file system resource "harvestedFS".
Figure 2. WebServerGroup resource group
<?xml version="1.0" encoding="UTF-8"?><AutomationPolicy productID="SAM" 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 SAMPolicy.xsd ">
Chapter 2. Reference 159
<PolicyInformation> <PolicyName>WebServer-Policy</PolicyName> <AutomationDomainName>clustername</AutomationDomainName> <PolicyToken>1.0.0</PolicyToken> <PolicyDescription>this is the policy for the WebServer </PolicyDescription> <PolicyAuthor>authorname</PolicyAuthor> </PolicyInformation>
<ConstituentResource name="apache1" class="IBM.Application" node="node1" /> <ConstituentResource name="apache1" class="IBM.Application" node="node2" />
<ConstituentResource name="local_mount" class="IBM.AgFileSystem" node="node1" > <ClassAttributesReference> <IBM.AgFileSystemAttributes name="FileSystem1"/> </ClassAttributesReference> </ConstituentResource> <ConstituentResource name="local_mount" class="IBM.AgFileSystem" node="node2" />
<ConstituentResource name="ha-ip-address" class="IBM.ServiceIP" node="node1" /> <ConstituentResource name="ha-ip-address" class="IBM.ServiceIP" node="node2" />
<IBM.ApplicationAttributes name="Application1"> <StartCommand>/PATH-TO-SCRIPT/apache start</StartCommand> <StopCommand>/PATH-TO-SCRIPT/apache stop</StopCommand> <MonitorCommand>/PATH-TO-SCRIPT/apache status</MonitorCommand> <UserName>root</UserName> <MonitorCommandPeriod>5</MonitorCommandPeriod> <MonitorCommandTimeout>4</MonitorCommandTimeout> <StartCommandTimeout>10</StartCommandTimeout> <StopCommandTimeout>10</StopCommandTimeout> <RunCommandsSync>1</RunCommandsSync> </IBM.ApplicationAttributes>
<IBM.AgFileSystemAttributes name="FileSystem1"> <DeviceName>/dev/DEVICE1</DeviceName> <MountPoint>/MOUNTPOINT1</MountPoint> <Vfs>ext3</Vfs> <ProtectionMode>1</ProtectionMode> </IBM.AgFileSystemAttributes>
<IBM.AgFileSystemAttributes name="FileSystem2"> <DeviceName>/dev/DEVICE2</DeviceName> <MountPoint>/MOUNTPOINT2</MountPoint> <Vfs>ext3</Vfs> <ProtectionMode>1</ProtectionMode> </IBM.AgFileSystemAttributes>
<IBM.ServiceIPAttributes name="ServiceIP1"> <IPAddress>10.10.10.15</IPAddress> <NetMask>255.255.255.0</NetMask> <ProtectionMode>1</ProtectionMode> </IBM.ServiceIPAttributes>
<MoveGroup name="apache1" class="IBM.Application"> <ClassAttributesReference> <IBM.ApplicationAttributes name="Application1"/> </ClassAttributesReference> <Members> <ConstituentResource name="apache1" class="IBM.Application" node="node1" /> <ConstituentResource name="apache1" class="IBM.Application" node="node2" /> </Members> </MoveGroup>
<MoveGroup name="local_mount" class="IBM.AgFileSystem"> <ClassAttributesReference> <IBM.AgFileSystemAttributes name="FileSystem2"/> </ClassAttributesReference> <Members> <ConstituentResource name="local_mount" class="IBM.AgFileSystem" node="node1" /> <ConstituentResource name="local_mount" class="IBM.AgFileSystem" node="node2" /> </Members> </MoveGroup>
<MoveGroup name="ha-ip-address" class="IBM.ServiceIP"> <ClassAttributesReference> <IBM.ServiceIPAttributes name="ServiceIP1"/> </ClassAttributesReference> <Members> <ConstituentResource name="ha-ip-address" class="IBM.ServiceIP" node="node1" /> <ConstituentResource name="ha-ip-address" class="IBM.ServiceIP" node="node2" /> </Members>
160 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
</MoveGroup>
<ResourceGroup class="IBM.ResourceGroup" name="WebServerGroup"> <DesiredState>Online</DesiredState> <InfoLink>www.apache.com</InfoLink> <Members> <MoveGroup name="apache1" class="IBM.Application"/> <MoveGroup name="local_mount" class="IBM.AgFileSystem"/> <MoveGroup name="ha-ip-address" class="IBM.ServiceIP"/> <ResourceReference name="harvestedFS"/> </Members> </ResourceGroup>
<Relationship name="apache1DependsOnLocal_mount"> <Source> <MoveGroup name="apache1" class="IBM.Application"/> </Source> <Target> <MoveGroup name="local_mount" class="IBM.AgFileSystem"/> </Target> <Type>DependsOn</Type> <Condition>None</Condition> </Relationship>
<Relationship name="apache1DependsOnHa-ip-address"> <Source> <MoveGroup name="apache1" class="IBM.Application"/> </Source> <Target> <MoveGroup name="ha-ip-address" class="IBM.ServiceIP"/> </Target> <Type>DependsOn</Type> <Condition>None</Condition> </Relationship>
<ResourceReference name="harvestedFS"> <ReferencedResource> <Class>IBM.AgFileSystem</Class> <Name>23f45d546</Name> <Node></Node> </ReferencedResource> </ResourceReference>
</AutomationPolicy>
Chapter 2. Reference 161
162 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Chapter 3. Messages
This chapter is for any user who is responsible for diagnosing problems related to System Automation forMultiplatforms.
System Automation for Multiplatforms messagesThis topic lists the messages that are generated by System Automation for Multiplatforms and describessolutions for each of these messages.
Prefix 26212621-001
2621-001Attribute"attribute_name" cannot bespecified whendefining a newresource.
Explanation
An error occurred whenan attribute that can notbe used in defining aresource has beenspecified.
Operator response
Specify only theattributes which can bespecified in defining theresource.
2621-002
2621-002Attribute"attribute_name" appears inrequest morethan once.
Explanation
An error occurred as thesame attribute is usedmultiple times.
Operator response
Use the attribute onlyonce.
2621-003
2621-003 Classname"class_name" isnot recognized
by this resourcemanager.
Explanation
An internal error occurredwhen attempting tocreate an RCCP for a classwhich does not exist.
Operator response
Check IBM ElectronicSupport for additionalinformation - http://www.ibm.com/support/entry/portal/
2621-004
2621-004 Couldnot initializecontrol point forclass"class_name".
Explanation
An internal error occurredwhen attempting tocreate an RCCP for theclass.
Operator response
Check IBM ElectronicSupport for additionalinformation - http://www.ibm.com/support/entry/portal/
2621-005
2621-005Attribute"attribute_name" must bespecified whendefining a newresource.
Explanation
This error was detectedwhen a mandatoryattribute is excluded indefining a resource.
Operator response
Use "lsrsrcdef <classname>" to check theattribute properties,include all mandatory(ReqdForDefine)attributes.
2621-006
2621-006Unrecognizedresource classid:resource_class_id.
Explanation
An error occurred whileextracting the class infofor this class id.
Operator response
If a resource handle isused, check if it is correct.Otherwise, check IBMElectronic Support foradditional information -http://www.ibm.com/support/entry/portal/
2621-007
2621-007 Timeout waiting forresourceenumerationresponses forthe
IBM.PeerNodeclass.
Explanation
A time out error occurredwhile waiting for peernodes enumerationregistration response.
Operator response
Check if the RMC andConfigRM are running(use "lssrc -a" command).If either of the subsystemis inoperative, consult theRMC/ConfigRM userguides to check how torestart the non-operational subsystem.
2621-008
2621-008 Failedto updateresourcebecause ofconfigurationdata replicationerrors.
Explanation
An error occurred whilereplicating data.
Operator response
Retry the operation. If theproblem continues,report to your softwareservice organization.
2621-009
2621-009Command notallowed -IBM.RecoveryR
© Copyright IBM Corp. 2006, 2020 163
M notinitialized.
Explanation
The resource manager isnot yet initialized toperform client's request.
Operator response
Wait for initialization andretry the command.
2621-010
2621-010Command notallowed -IBM.RecoveryRM not inconfigurationquorum.
Explanation
The cluster is probablyrunning with severalIBM.RecoveryRMdaemons failure. Theoperation needs thequorum ofIBM.RecoveryRMdaemons online.
Operator response
Try to restart the failedIBM.RecoveryRMdaemons to bring backthe configuration quorum.
2621-011
2621-011Command notallowed - nodefailedconfigurationdata replication.
Explanation
The node had failedupdating theconfiguration data - cannot perform the client'srequest.
Operator response
Retry the operation. If theproblem continues,
report to your softwareservice organization.
2621-012
2621-012Command notallowed -configurationdatareplacement inprocess.
Explanation
The system is intransition to a newconfiguration data - cannot perform the client'srequest.
Operator response
Retry the operation. If theproblem continues,report to your softwareservice organization.
2621-013
2621-013Command notallowed -replication cannot be started.
Explanation
An error occurred ininitializing the replicationprocess.
Operator response
Retry the operation. If theproblem continues,report to your softwareservice organization.
2621-014
2621-014Command notallowed - one ormore relatedresource groupsare online.
Explanation
An error was generatedwhile changing amanaged resource,resource group, orrelationship which
involves one or moreonline resource groups.
Operator response
Before changing theresource, the resourcegroups have to be offline.
2621-015
2621-015 Failedto get resourceclass persistentattributes forclass"class_name".
Explanation
An error was returnedwhile querying the classto get its persistentattributes.
Operator response
Check if the resourcemanager to which theclass belongs to isoperational. If theresource manager isinoperative, consult itsuser guide to check howto restart.
2621-016
2621-016 Failedto get definitionof resourcepersistentattributes forclass"class_name".
Explanation
An error was returnedwhile querying a resourceto get its persistentattributes.
Operator response
Check if the resourcemanager to which theclass belongs to isoperational. If theresource manager isinoperative, consult itsuser guide to check howto restart.
2621-017
2621-017 Timeout waiting forattribute queryresponses forthe"class_name"class.
Explanation
A time out error occurredwhile waiting for attributequery response fromRMC.
Operator response
Check if the resourcemanager to which theclass belongs to isoperational. If theresource manager isinoperative, consult itsuser guide to check howto restart.
2621-018
2621-018 Errorencounteredwhen callingfunction"function_name". return code =return_code
Explanation
An error condition wasreturned when thisfunction was invoked.
Operator response
This is an internal error,report it to your softwareservice organization.
2621-019
2621-019 Timeout waiting forresponse ofeventregistrationwith resourcehandle.
Explanation
A time out error occurredwhile waiting for aresponse on an event
164 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
registration with resourcehandle.
Operator response
Check if the RMC and theresource manager for theresource are running (use"lssrc -a" command). Ifeither of the subsystem isinoperative, consult thecorresponding user guideto check how to restartthe non-operationalsubsystem.
2621-020
2621-020Resource has aninvalid resourceclass name"resource_class_name".
Explanation
The referenced resourceclass name is not found.
Operator response
Use "lsrsrc" command todisplay the supportedresource classes. Correctthe class name and retrythe operation.
2621-021
2621-021Resource doesnot exist.
Explanation
The referenced resourceis not found.
Operator response
Use "lsrsrc class_name"to display all resourceswith in a class.
2621-022
2621-022Resourceencounterseventregistrationerror. The errormessage is:[error_message]
Explanation
An error message wasreturned by the RMC inresponse to an eventregistration for aresource.
Operator response
Check the error messageand take the appropriatemeasure. Restart theRMC and the resourcemanager if they are notrunning.
2621-023
2621-023Resource RCPnot found
Explanation
An internal error wasdetected while a controlpoint for a resource wasnot found.
Operator response
Check IBM ElectronicSupport for additionalinformation - http://www.ibm.com/support/entry/portal/
2621-024
2621-024 Timedout waiting forresourceenumerationresponses fortheIBM.PeerDomain class.
Explanation
A time out error occurredwhile waiting for peerdomains enumerationregistration
Operator response
Check if the RMC andConfigRM are running(use "lssrc -a" command).If either of the subsystemis inoperative, consult theRMC/ConfigRM user
guides to check how torestart the non-operational subsystem.
2621-025
2621-025 Value"input_parameter_value"provided forinput parameter"input_parameter_name" inSubmitRequestaction is notvalid.
Explanation
Value provided for aninput parameter inSubmitRequest action isnot valid
Operator response
Check value provided forinput parameter ofSubmitRequest action.Correct the value andretry the action
2621-026
2621-026 Thisfunctionality isnot supportedby currentactive version ofthe cluster.
Explanation
The cluster is in co-existence or migrationmode. The current activeversion does not supportthe functionality.
Operator response
Retry after migration iscompleted.
2621-027
2621-027 Thereis no previousrequest fromsource[source_name].Cancellationfailed.
Explanation
Cancellation of request isreceived but there is noprevious request from thespecified source.
Operator response
Check value provided forsource of SubmitRequestaction. Correct the valueand retry the action
2621-028
2621-028Command notallowed -completemigration actionin process.
Explanation
The system is intransition to a new activecode version level - cannot perform the client'srequest.
Operator response
Retry the operation. If theproblem continues,report to your softwareservice organization.
2621-029
2621-029Request tomove can not begranted as thereis already amove requeston the resource.
Explanation
Request to move can notbe granted as there isalready a move requeston the same resourcegroup.
Operator response
Wait for five minutes andRetry the operation.
2621-030
2621-030 Timedout waiting forquery persistentclass attribute
Chapter 3. Messages 165
requestresponses fortheIBM.PeerNodeclass.
Explanation
A time out error occurredwhile waiting for peernode QuorumTyperegistration
Operator response
Check if the RMC andConfigRM are running(use "lssrc -a" command).If either of the subsystemis inoperative, consult theRMC/ConfigRM userguides to check how torestart the non-operational subsystem.
2621-031
2621-031Command notallowed - newconfigurationinitialization isin progress.
Explanation
The system is intransition to a newconfiguration initialization- can not perform theclient's request.
Operator response
Retry the operation. If theproblem continues,report to your softwareservice organization.
2621-032
2621-032Command notallowed -IBM.RecoveryRM not inoperationalquorum.
Explanation
The cluster is running in atiebreaker situation with
no operational quorumestablished yet.
Operator response
A tiebreaker must be setup in order to grantoperational quorum incase of a cluster split.
2621-050
2621-050Resource groupname"resource_group_name" alreadydefined.
Explanation
An error was detectedwhile an existing resourcegroup name is used todefine a new resourcegroup.
Operator response
Use an unique name andretry the command.
2621-051
2621-051Resource grouphas an invalidallowed node asthe equivalencymembers do notbelong toIBM.PeerNode.
Explanation
The AllowedNode of thedefined resource groupcomes from anequivalency whoseMemberClass attribute isnot IBM.PeerNode.
Operator response
Correct the problem andretry the operation.
2621-052
2621-052Resource groupmemberlocation isincompatiblewith its outerresource group.
Explanation
The MemberLocationattribute of the innerresource group isincompatible with itsouter resource group.
Operator response
Correct the problem andretry the operation.
2621-053
2621-053Resource groupmemberlocation isincompatiblewith itsmembersrelationships.
Explanation
The MemberLocationattribute of the resourcegroup is incompatiblewith a defined locationsensitive (Collocated,DependsOn, etc )managed relationship.The resource group mayhave one or moremembers participating inthe conflictedrelationship.
Operator response
Fix the locationcompatibility problemeither by changing theattribute or therelationship or both.
2621-054
2621-054Resource grouppriority must bebetween 0 and200.
Explanation
The priority valuespecified by the user isnot valid.
Operator response
Specify a priority with inthe valid range 0 and 200.
2621-055
2621-055Resource grouppriorityresource_group_priority exceedsthe priorities ofouter resourcegroups.
Explanation
An error was detected ina nested resource groupwhere an inner resourcegroup has a higherpriority than an outerresource group.
Operator response
Reset the priority so thatouter resource group hasthe same or higherpriority than an innerresource group, and retrythe command.
2621-056
2621-056Resource grouphas an invalidvalue forattributeMemberLocation: invalid_value.
Explanation
The value entered forattribute MemberLocationis invalid.
Operator response
Define resource groupwith a valid value forattributeMemberLocation.
2621-057
2621-057Resource grouphas an invalidvalue forattributeNominalState:invalid_value.
166 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Explanation
The value entered forattribute NominalState isinvalid.
Operator response
Enter a valid value forattribute NominalState.
2621-058
2621-058Resource groupnesting levelexceeds themaximum of 50levels.
Explanation
The resource groupsnesting level can notexceed maximum of 50levels.
Operator response
Reduce the resourcegroups nesting level.
2621-059
2621-059 NodeID %1$llu cannot be found.
Explanation
A node id inSubmitRequest resourceaction does notcorrespond to a node incluster
Operator response
Check value of node id.Correct the value andretry the action
2621-060
2621-060ExcludedList isnot supportedfor ResourceGroup in thecurrent activeversion of thecluster.
Explanation
The cluster is in co-existence or migration
mode. The current activeversion does not supportthe ExcludedList attributefor Resource Groups.
Operator response
Retry after migration iscompleted.
2621-061
2621-061Resource grouphas an invalidExcludedList asall or some of itsmembers do notbelong to thecurrent cluster.
Explanation
The ExcludedList of thedefined resource has atleast one of its membersor nodes that do notbelong in the currentcluster.
Operator response
Correct the problem andretry the operation.
2621-062
2621-062 Anode specifiedin move actionis not in theallowed nodelist of resourcegroup.
Explanation
Resource group is beingrequested to move awayfrom a node it is notallowed.
Operator response
Check value provided forinput parameter ofSubmitRequest action.Correct the value andretry the action
2621-063
2621-063 Theresource groupis not in online
state and cannot be moved.
Explanation
Resource group beingrequested to move is notin online state.
Operator response
Check target of moverequest. Correct thetarget and retry theaction.
2621-064
2621-064 Nodename list notspecified whenmoving a non-collocatedresource group.
Explanation
A list of node names tomove resources awayfrom must be specifiedwhen moving a non-collocated resourcegroup.
Operator response
Retry the command withnode name list specified.
2621-065
2621-065Resource group"resource_group" cannot bebrought online -Empty Tree.
Explanation
The specified resourcegroup cannot be broughtonline because it did nothave any resources thatcould be brought online.
Operator response
Add a real resource to thegroup and then bring itonline.
2621-066
2621-066Resource group
can not bemoved as it isnot a top-levelresource group.
Explanation
The specified resourcegroup cannot be movedbecause it is not a top-level resource group.
Operator response
Issue the move requestagainst a top-levelresource group.
2621-067
2621-067Resource groupcan not bemoved as itcontains at leastone fixedresource.
Explanation
The specified resourcegroup cannot be movedbecause it contains atleast one fixed resource.
Operator response
Rethink the needs tomove this resource group.
2621-068
2621-068Subscription isnot supportedfor ResourceGroup in thecurrent activeversion of thecluster.
Explanation
The cluster is in co-existence or migrationmode. The current activeversion does not supportthe Subscription attributefor Resource Groups.
Operator response
Retry after migration iscompleted.
Chapter 3. Messages 167
2621-069
2621-069 Thisattribute is notsupported forResource Groupin the currentactive version ofthe cluster.
Explanation
The cluster is in co-existence or migrationmode. The current activeversion does not supportthis attribute forResource Groups.
Operator response
Retry after migration iscompleted.
2621-070
2621-070Requests arenot supportedfor ResourceGroup in thecurrent activeversion of thecluster.
Explanation
The cluster is in co-existence or migrationmode. The current activeversion does not supportthe Requests attribute forResource Groups.
Operator response
Retry after migration iscompleted.
2621-071
2621-071 Valueof attributeRequests:invalid_value forresource groupis not valid.
Explanation
The value entered forattribute Requests isinvalid.
Operator response
Define resource groupwith a valid value forattribute Requests.
2621-072
2621-072Concurrentresourcescannot bemembers ofresource groupswith collocatedmembershiplocation.
Explanation
Concurrent resources arerendered unstartable asmembers of a resourcewith collocatedmembership location; themembership locationattribute of the groupmust be changed.
Operator response
Consider changing themembership location ofthe group.
2621-073
2621-073Concurrentresourcescannot be groupmembers withfailback policyenabled.
Explanation
Concurrency conflictswith the failback policy.Do not set failback policybit for concurrentresources.
Operator response
Do not set the failbackpolicy bit.
2621-074
2621-074 Thefailback policyvalue is notvalid for non-mandatorygroup members.
Explanation
Automated failback fornon-mandatory groupmembers would pose therisk of loops and thus isnot valid. Use failbackonly for mandatory groupmembers.
Operator response
Do not set the failbackpolicy bit.
2621-075
2621-075 Themove actioncannot succeedwith the currentconfiguration.
Explanation
The move action cannotsucceed with the currentconfiguration.
Operator response
Check the currentconfiguration to find outwhy move is not possible.
2621-076
2621-076 Themove action isrejectedbecause thetarget group isonly allowed torun on a singlenode.
Explanation
The move action isrejected because thetarget group is onlyallowed to run on a singlenode.
Operator response
Consider changing theallowed node parameter,so that the group can runon at least a second node.
2621-077
2621-077Resource name"resource_name
" is longer than64 characters.
Explanation
The name of this resourceis longer than 64characters.
Operator response
Consider choosing ashorter name and retrythe command.
2621-078
2621-078 Oneof the outergroups had alower prioritythan an innergroup whenadding resourcegroup s innerresource groupname, 2s outerresource groupname asmember ofgroup %s.
Explanation
If an outer resourcegroup has a lower prioritythan any of its direct orindirect members, theresource placementalgorithm yieldsundeterministic results.
Operator response
Check the resourceconfiguration beforeretrying the operation
2621-079
2621-079Detectedmembershiploop whenadding resourcegroup s innerresource groupname, 2s outerresource groupname asmember ofgroup %s.
168 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Explanation
Making an outer resourcegroup a direct or indirectmember of itself rendersthe resourceconfiguration unusable.
Operator response
Check the resourceconfiguration beforeretrying the operation
2621-101
2621-101Managedresource cannotbe in more thanone resourcegroup, alreadyin"resource_group_name".
Explanation
An error was detectedwhen a resource thatalready exists as amanaged resource wasattempted to be includedin the same or anotherresource group.
Operator response
Retry the operation withcorrect parameters.
2621-102
2621-102Managedresource has aninvalid resourcehandle.
Explanation
A resource manager hasresponded back with aninvalid resource handle.
Operator response
Check IBM ElectronicSupport for additionalinformation - http://www.ibm.com/support/entry/portal/
2621-103
2621-103Managed
resource"resource_name" does not havecontrolinterface.
Explanation
An error was generatedwhile it was detected thatresource class does notsupport the controlinterface.
Operator response
Check the attributes ofthe resource class. Addonly the resources whoseOpState can be changed.
2621-104
2621-104Managedresource'sresource group"resource_group_name" doesnot exist.
Explanation
A dangling managedresource is detectedwhose resource groupdoes not exist any more.
Operator response
Check IBM ElectronicSupport for additionalinformation - http://www.ibm.com/support/entry/portal/
2621-105
2621-105Managedresource has aninvalid resourceclass id %x.
Explanation
The referenced managedresource class has aninvalid class id.
Operator response
Use "lsrsrcdef -c class-name" to display the
correct class id. Use thecorrect class name andretry the operation.
2621-106
2621-106Managedresource has aninvalid resourcetyperesource_type.
Explanation
A managed resource caneither be fixed or floatingtype. An error occurred asan invalid typed resourcewas used.
Operator response
Correct the problem andretry the operation.
2621-107
2621-107Managedresource is afixed resource,but is notdefined on anynode.
Explanation
An error was generatedas a fixed managedresource was not foundon any node.
Operator response
Either remove theresource from theresource group or modifytype as floating.
2621-108
2621-108Resourcegroup's memberlocation isincompatiblewith its outerresource group.
Explanation
The MemberLocationattribute of the innerresource group is
incompatible with itsouter resource group.
Operator response
Correct the problem andretry the operation.
2621-109
2621-109Managedresource is afixed resource,but is definedonnumber_of_nodes nodes.
Explanation
An error was generatedas a fixed resource wasdefined on multiplenodes.
Operator response
Either remove theresource from theresource group or modifythe node list or changetype to floating.
2621-110
2621-110 Cannot findresource classinformation formanagedresource.
Explanation
An error was generatedwhen enumerating theclass information for aresource.
Operator response
Verify that the correctclass name was used. Iferror continues, report toyour software serviceorganization.
2621-111
2621-111Resource groupcan not be amember ofitself.
Chapter 3. Messages 169
Explanation
A managed resource(resource group) can notbe nested within itself.
Operator response
Retry the operation withcorrect parameters.
2621-112
2621-112 Valueof attributeMandatory:invalid_value formanagedresource is notvalid.
Explanation
The value entered forattribute Mandatory isinvalid.
Operator response
Define managed resourcewith a valid value forattribute Mandatory.
2621-113
2621-113Managedresource"resource_name" is the target ofa resource inanother tree.
Explanation
A managed resource cannot be the target of twoindependent resourcegroups. The error wasgenerated due to theviolation of thisconstraint.
Operator response
Remove the conflict andretry the operation.
2621-114
2621-114Managedresource"resource_name" can not bedefined in anequivalency.
Explanation
An error was generatedwhen a managedresource was beingincluded as a member ofan equivalency.
Operator response
Define the equivalencyonly with resources thatare not defined asmanaged resources.
2621-115
2621-115Managedresource is froman invalid class.
Explanation
A resource designated asmanaged has a resourcehandle that does notbelong to the referencedclass.
Operator response
Correct the class nameand retry the operation.
2621-116
2621-116Resource doesnot havedynamicattribute -OpState.
Explanation
An error was generatedwhile it was detected thatresource class does nothave the dynamicattribute - OpState.
Operator response
Check dynamic attributesof the resource class. Addonly the resources whichhas OpState.
2621-117
2621-117 Cannot changesource managedresource whilethere aretargets.
Explanation
An error was generatedwhile trying to change thesource of a relationshipwhen the relationship hasone or more targets.
Operator response
Remove the relationshipand recreate a new onewith appropriate source.
2621-118
2621-118 Cannot change theresource handleof a managedresource.
Explanation
A managed resourcealways represents theresource for which it wascreated.
Operator response
Remove the memberrepresenting themanaged resource fromthe resource group andadd a new member thatpoints to the correctresource.
2621-119
2621-119Resource groupdoes not exist.
Explanation
An error was generatedwhen a non-existentresource group wasreferenced.
Operator response
Check the valid resourcegroups using "lsrg"command. Retry theoperation using correctresource group.
2621-120
2621-120Operationtemporarilydisallowed, asresource
registration is inprogress.
Explanation
Previous attempt toregister for resourceevents failed. Whiledaemon is retrying theregistration, somefunctionalities is notavailable.
Operator response
Correct the registrationproblem, then retry theoperation.
2621-121
2621-121 Valueof attributeSelectFromPolicy: invalid_valuefor managedresource is notvalid.
Explanation
The value entered forattributeSelectFromPolicy isinvalid.
Operator response
Define managed resourcewith a valid value forattributeSelectFromPolicy.
2621-122
2621-122SelectFromPolicy is notsupported forManagedresources in thecurrent activeversion of thecluster.
Explanation
The cluster is in co-existence or migrationmode. The current activeversion does not supportthe SelectFromPolicyfeature for managedresources.
170 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Operator response
Retry after migration iscompleted.
2621-123
2621-123Subscription isnot supportedfor ManagedResource in thecurrent activeversion of thecluster.
Explanation
The cluster is in co-existence or migrationmode. The current activeversion does not supportthe Subscription attributefor Managed Resource.
Operator response
Retry after migration iscompleted.
2621-124
2621-124Requests arenot supportedfor ManagedResource in thecurrent activeversion of thecluster.
Explanation
The cluster is in co-existence or migrationmode. The current activeversion does not supportthe Requests attribute forManaged Resource.
Operator response
Retry after migration iscompleted.
2621-125
2621-125 Valueof attributeRequests:invalid_value formanagedresource is notvalid.
Explanation
The value entered forattribute Requests isinvalid.
Operator response
Define managed resourcewith a valid value forattribute Requests.
2621-126
2621-126Instances arenot supportedfor ManagedResource in thecurrent activeversion of thecluster.
Explanation
The cluster is in co-existence or migrationmode. The current activeversion does not supportthe Instances attributefor Managed Resource.
Operator response
Retry after migration iscompleted.
2621-128
2621-128Attribute notsupported forManagedResource in thecurrent activeversion of thecluster.
Explanation
The cluster is in co-existence or migrationmode. The current activeversion does not supportthe attribute for ManagedResource.
Operator response
Retry after migration iscompleted.
2621-150
2621-150Managedrelationship has
a sourceresource that isnot a managedresource.
Explanation
An error was detectedwhen a non-managedresource was used as thesource of a managedrelationship. The sourcemust be a managedresource.
Operator response
Correct the problem, andretry the operation.
2621-151
2621-151Managedrelationship hasa targetresource that isnot valid.
Explanation
An error was generatedas an invalid or non-existent resource wasused as the target of amanaged relationship.
Operator response
Correct the problem andretry the operation.
2621-152
2621-152Managedrelationshipname"relationship_name" alreadydefined.
Explanation
A managed relationshipwith this name wasalready defined.
Operator response
Use an unique name andretry the operation.
2621-153
2621-153Managedrelationshiptarget specifiedmore than once.
Explanation
An error was generatedas a resource was usedmore than once as thetarget of a managedrelationship.
Operator response
Correct the problem andretry the operation.
2621-154
2621-154Managedrelationship hasan invalid value0 for attribute -Relationship.
Explanation
A new managedrelationship was beingdefined with no (NONE)relationship value.
Operator response
Define managedrelationship with a validvalue for relationship.
2621-155
2621-155Managedrelationshipsource definedas targetresource.
Explanation
An error condition wasdetected. A managedrelationship's source andtarget can not be thesame.
Operator response
Remove source resourcefrom the target, and retrythe operation.
Chapter 3. Messages 171
2621-156
2621-156Managedrelationshipconflicts with apreviouslydefinedrelationship.
Explanation
A new relationship wasdefined which conflictswith a previously definedlocation sensitive or ordersensitive relation.
Operator response
Remove the conflict andretry the operation.
2621-157
2621-157Managedrelationshipduplicates apreviouslydefinedrelationship.
Explanation
An error was generateddue to re-definition of arelationship.
Operator response
Define only one instanceof a relationship.
2621-158
2621-158Managedrelationship hasa source ortarget that isnot of anallowed class.
Explanation
The resource from thisclass can't be the sourceor target of the definedrelationship.
Operator response
Correct the source ortarget resource and retrythe operation.
2621-159
2621-159Managedrelationship isnot consistentwith source'sresource groupmemberlocation.
Explanation
A conflict was detected inlocation association ofthe relationship.
Operator response
Check the source'sMemberLocation attributeand correct the problem.
2621-160
2621-160Managedrelationshipintroducescircularrelationshipfrom a resourceback to itself.
Explanation
For StartAfter orDependsOn, orDependsOnAnyrelationship, a circulardependency wasdetected which maycreate a deadlock.
Operator response
Remove the circulardependency and retry theoperation.
2621-161
2621-161SpecifiedRelationshipattribute forManagedrelationship isnot supportedby currentactive version ofthe cluster.
Explanation
The cluster is in co-existence or migrationmode. The current activeversion does not supportthe specified relationshipattribute.
Operator response
Retry after migration iscompleted.
2621-162
2621-162Managedrelationshipcould/cannot becreated becausethe specifiedtarget resource"target resourcename" is anempty resourcegroup.
Explanation
Empty resource groupscan't be a target of thedefined relationship.
Operator response
Add members to resourcegroup and retry theoperation.
2621-163
2621-163DependsOnAnymanagedrelationshipwith aconcurrentresource assource or targetor anequivalency astarget is notvalid.
Explanation
An error was generatedas a DependsOnAnymanaged relationshipwas about to be\ createdwith a concurrentresource as target or
source or an equivalencyas\ target.
Operator response
Correct the problem andretry the operation.
2621-200
2621-200Equivalencyname"equivalency_name" alreadydefined.
Explanation
An equivalency with thisname was alreadydefined.
Operator response
Use an unique name andretry the operation.
2621-201
2621-201Equivalencymembershipmust either beexplicitlyenumerated orspecified with aselect string.
Explanation
An error was generatedwhile both a select stringand an enumerated set ofresource handles areused to defineequivalency membership.
Operator response
Use either enumerationor select string (not both)and retry the operation.
2621-202
2621-202Equivalency hasan invalid selectstring.
Explanation
User entered an invalidselect string.
172 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Operator response
Correct the problem,especially check theattribute name and value.Retry the operation.
2621-203
2621-203Equivalency hasan invalidmember.
Explanation
An error condition wasdetected as anequivalency member wasfound which was either amanaged resource or didnot belong to the sameclass as other members.
Operator response
Correct the problem andretry the operation.
2621-204
2621-204Equivalency ofnodes hasinvalid member.
Explanation
A node in an equivalencydo not belong toIBM.PeerNode class.
Operator response
Correct the problem andretry the operation.
2621-205
2621-205Equivalency hasmembersbelonging todifferentresourceclasses.
Explanation
An error was detected inan equivalency members.Resources within theequivalency are fromdifferent classes. Allresources within the anequivalency must be fromthe same class.
Operator response
Correct the problem andretry the operation.
2621-206
2621-206Equivalencymembershiphas a duplicatedresource handle"resource_handle".
Explanation
Two members of anequivalency has the sameresource handle.
Operator response
Remove one and thenretry the operation.
2621-207
2621-207Equivalencymembershiphas resourcehandlescontainingmultiple classids (class_id1and class_id2).
Explanation
An error was generatedwhile defining anequivalency. Tworesource members withinthe equivalency are fromdifferent classes. Allresources within the anequivalency must be fromthe same class.
Operator response
Correct the problem andretry the operation.
2621-208
2621-208Equivalencyneed to specifyboth selectstring and avalid resourceclass name.
Explanation
An error was generatedwhile an invalid resourceclass name was used withthe dynamic select string.
Operator response
Correct the class nameand retry the operation.
2621-209
2621-209 Cannot findresource classinformation forequivalency"equivalency_name".
Explanation
An error was generatedwhile enumerating theclass information for themember class.
Operator response
This may be an internalerror, report to yoursoftware serviceorganization.
2621-210
2621-210Resource class"resource_class_name" is invalidfor equivalency.
Explanation
A resource from this classis not valid for thisequivalency. Class id maybe different from othermembers.
Operator response
Use the resources fromthe same class to correctthe problem.
2621-211
2621-211Resource classmay not bechanged in anequivalencywithout
replacing themembers.
Explanation
An error was generatedwhile user was trying tochange the MemberClassattribute value of anequivalency which hasmembers (may be from adifferent class).
Operator response
Remove the membersbefore changing theMemberClass.
2621-212
2621-212ManagedResource"equivalency_name" can not be amember of anEquivalency.
Explanation
An error was generatedas a managed resourcewas placed as a memberof this equivalency.
Operator response
Add only the resourcesthat are not member ofany resource group.
2621-213
2621-213 AManagedResource referenced asan AllowedNodemay not changeits class.
Explanation
Error was detected asclass of a managedresource referenced as anAllowedNode waschanged.
Operator response
Remove the errorcondition and retry.
Chapter 3. Messages 173
2621-214
2621-214Resource classmay not bechanged for anequivalency ifthere aremembers.
Explanation
An error was generatedwhile user was trying tochange the MemberClassattribute value of anequivalency which hasmembers (may be from adifferent class).
Operator response
Remove the membersbefore changing theMemberClass.
2621-215
2621-215 Aselection Policyother than ANYis invalid with aselection string.
Explanation
An error was generatedwhile parsing anequivalency definitionwith selection stringwhere the selectionpolicy was not ANY.
Operator response
Change the selectionpolicy to ANY and retrythe operation.
2621-216
2621-216Minimum valuemust between 1and 100.
Explanation
An error was generatedwhile an invalidMinimumNecessaryattribute value wasentered by the user.
Operator response
Use a valid value from 1 -100 and retry thecommand.
2621-217
2621-217Equivalencycontains nomemberresource
Explanation
This error messageindicates that anIBM.Equivalencyresource is defined with aNULL select string, and anempty membership list.
Operator response
Define an equivalencywith either a select stringor a non-emptymembership list
2621-218
2621-218Floatingresource withresource handle"resource_handle" can not be amember ofEquivalency"Equivalency_name".
Explanation
Floating resources are notallowed to be a memberof an equivalency.
Operator response
Add only fixed orconstituents resources asmembers ofequivalencies.
2621-219
2621-219Subscription isnot supportedfor Equivalencyin the currentactive version ofthe cluster.
Explanation
The cluster is in co-existence or migrationmode. The current activeversion does not supportthe Subscription attributefor Equivalency.
Operator response
Retry after migration iscompleted.
2621-300
2621-300 Nodespecified byresourcehandles forexcluded nodescould not befound.
Explanation
The excluded nodescontains one or morenodes that are notdefined in IBM.PeerNoderesource class.
Operator response
Correct the problem andretry the operation.
2621-301
2621-301 Inputto the"class_action_name" action isnot valid.
Explanation
A class action activationrequest is received whichcontains structured datawith invalid elements.
Operator response
Correct the problem andretry the operation.
2621-302
2621-302attribute"invalid_value"has an invalid orout of rangevalue.
Explanation
During the process ofattempting to add orchange attribute values, itwas discovered that thevalue is either invalid orout of range.
Operator response
Correct the problem andretry the operation.
2621-303
2621-303 Theautomationengine is notinitialized.
Explanation
The decision engine is notinitialized.
Operator response
Wait for five minutes andretry the operation.
2621-304
2621-304Invalid action,RecoveryRM isnot inReplaceConfigmode.
Explanation
An invalid restoreconfiguration optionentered.
Operator response
Correct the problem andretry the operation.
2621-305
2621-305Feature notenabled,RecoveryRM iseither running indown graded ormigration mode.
Explanation
A feature option that cannot be activated isentered.
174 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Operator response
Complete migration to anappropriate version level.
2621-306
2621-306 Inputto the"CompleteMigration" action isnot valid. OurIVN isincompatible tothisNewActiveVersion:"active_version"
Explanation
The NewActiveVersionrelease name isincompatible to thecurrent installedRecoveryRM daemonversion.
Operator response
Correct the problem andretry the operation.
2621-307
2621-307 Inputto the"CompleteMigration" action isnot valid. Therange ofNewActiveVersion is betweenversion"1.1.1.0" andversion"256.256.256.256" - "version"
Explanation
The value of theNewActiveVersionrelease name is invalid. Itneeds to be within therange of "1.1.1.0" and"256.256.256.256".
Operator response
Correct the problem andretry the operation.
2621-308
2621-308 Inputto the"CompleteMigration" action isnot valid.NewActiveVersion("new_active_version") cannotbe higher thanIVN("installed_version") or lowerthan currentAVN ("3$scurrent_active_version").
Explanation
The value of theNewActiveVersionrelease name is invalid. Itcannot lower than thecurrent active versionnumber or higher thaninstalled version number.
Operator response
Correct the problem andretry the operation.
2621-309
2621-309Command notallowed asdaemon doesnot have a validlicense.
Explanation
The command beingissued is not allowed torun on this daemon as avalid license is notinstalled.
Operator response
Install a valid license andretry the operation.
2621-310
2621-310Cannot performthe"CompleteMigration" action.Current joined
RecoveryRMdaemonmember count(daemon_member_count) isdifferent thanthe total nodecount(total_node_count). Use forceoption ("-f") tooverride.
Explanation
Since not all theRecoveryRM daemons areup and running, wecannot start the migrationcomplete action.
Operator response
Make sure that all theRecoveryRM daemons areup and running or use theforce option ("-f") to startthe migration completeaction.
2621-311
2621-311Publisher is notsupported in thecurrent activeversion of thecluster.
Explanation
The cluster is in co-existence or migrationmode. The current activeversion does not supportthe Publisher feature.
Operator response
Retry after migration iscompleted.
2621-312
2621-312License file"license_file_name" does notexist.
Explanation
The license file to beinstalled does not exist.
Operator response
Find the correct locationof the license file to beinstalled, and retry theoperation.
2621-313
2621-313Configurationcommand notallowed -daemon is inreplaceconfigurationmode.
Explanation
The command beingissued is not allowed inreplace configurationmode.
Operator response
Wait for the completion ofreplace configurationaction.
2621-314
2621-314 Inputto the"CompleteMigration" action isnot valid.Current RSCTactive versionnumber isincompatible tothisNewActiveVersion: "version"
Explanation
The current RSCT activeversion number isincompatible to theselected newRecoveryRM daemonactive version number.
Operator response
Correct the problem andretry the operation.
2621-315
2621-315attribute"attribute_name" has an invalid
Chapter 3. Messages 175
value"invalid_value".
Explanation
During the process ofattempting to add orchange attribute values, itwas discovered that thespecified value is invalidor out of range.
Operator response
Correct the problem andretry the operation.
2621-316
2621-316IBM.RecoveryRM publisherconfigurationfile "file_name"not found.
Explanation
IBM.RecoveryRMpublisher configurationfile not found. Thispublisher cannot beenabled.
Operator response
Fix the problem with thepublisher configurationfiles and enable thispublisher by using the'samctrl -e <publisher>'command.
2621-317
2621-317IBM.RecoveryRM publisherconfigurationfile "file_name"syntax error inline numberline_number.
Explanation
IBM.RecoveryRMpublisher configurationfile syntax error. Thispublisher cannot beenabled.
Operator response
Fix the problem with thepublisher configurationfiles and enable thispublisher by using the'samctrl -e <publisher>'command.
2621-318
2621-318IBM.RecoveryRM publisherconfigurationfile not found.The specifiedconfigurationfile"ConfigPath=config_file" is notvalid in thepublisherconfigurationfile "file_name"for thepublisher name"publisher_name".
Explanation
IBM.RecoveryRMpublisher configurationfile not found. Thispublisher cannot beenabled.
Operator response
Fix the problem with thepublisher configurationfiles and enable thispublisher by using the'samctrl -e <publisher>'command.
2621-319
2621-319IBM.RecoveryRM publisherconfigurationfile syntax error.Parameter"parameter" notfound inpublisherconfigurationfile "file_name"for thepublisher name
"publisher_name".
Explanation
IBM.RecoveryRMpublisher configurationfile syntax error. Thispublisher cannot beenabled.
Operator response
Fix the problem with thepublisher configurationfiles and enable thispublisher by using the'samctrl -e <publisher>'command.
2621-320
2621-320IBM.RecoveryRM publisherconfigurationfile syntax error.Same publishername foundmultiple timesin publisherconfigurationfile "file_name"with thepublisher name"publisher_name".
Explanation
IBM.RecoveryRMpublisher configurationfile syntax error. Thispublisher cannot beenabled.
Operator response
Fix the problem with thepublisher configurationfiles and enable thispublisher by using the'samctrl -e <publisher>'command.
2621-321
2621-321IBM.RecoveryRM publisherconfigurationfile syntax error.Too many
publishersfound inpublisherconfigurationfile "file_name".A maximum(number) ofmax_number_publisherspublishers issupported.
Explanation
IBM.RecoveryRMpublisher configurationfile syntax error. Thispublisher cannot beenabled.
Operator response
Fix the problem with thepublisher configurationfiles and enable thispublisher by using the'samctrl -e <publisher>'command.
2621-322
2621-322 Thecommand"samctrl -e|-d<publisher>"failed on themaster node.Ensure that allpublisherconfigurationfiles have thesame content onall nodes. Thesyslog on themaster nodemay containmore details.detailed_msg
Explanation
During the process ofattempting to add orchange a publisher, it wasdiscovered that thespecified publisher namecannot be set.
176 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Operator response
Correct the problem andretry the operation.
2621-323
2621-323IBM.RecoveryRM publisherconfigurationfile "file_name"does not containpublisher name"publisher_name".
Explanation
IBM.RecoveryRMpublisher not found. Thispublisher cannot beenabled.
Operator response
Fix the problem with thepublisher configurationfiles and enable thispublisher by using the'samctrl -e <publisher>'command.
2621-324
2621-324IBM.RecoveryRM publisherconfigurationfile syntax error.Publisher namedoes not followsyntax rules inpublisherconfigurationfile "file_name"for thepublisher name"publisher_name". Publishername length:1-8, Publishername validcharacters:'0'-'9', 'A'-'Z','a'-'z' and '_'.
Explanation
IBM.RecoveryRMpublisher configurationfile syntax error. Thispublisher cannot beenabled.
Operator response
Fix the problem with thepublisher configurationfiles and enable thispublisher by using the'samctrl -e <publisher>'command.
2621-325
2621-325IBM.RecoveryRM publisherconfigurationfile "file_name"does not containa validpublisher name.
Explanation
IBM.RecoveryRMpublisher not found. Thispublisher cannot beenabled.
Operator response
Fix the problem with thepublisher configurationfiles and enable thispublisher by using the'samctrl -e <publisher>'command.
2621-326
2621-326IBM.RecoveryRM publisher"publisher_name" alreadyenabled.
Explanation
Disable publisher beforeenabling it again.
Operator response
Disable one publisher byusing the 'samctrl -d<publisher>' command.
2621-327
2621-327IBM.RecoveryRM publisherinfrastructure isbusy, sochanges are notallowed.
Explanation
One of the publishermodules is busy sendingdata.
Operator response
Consider waiting, beforetrying again to changingthe active publisher list.
2621-328
2621-328Adapter startdelayed,currentlycluster has noOperationalQuorum.Adapter startwill continuewhenOperationalQuorum isavailable.
Explanation
There is no OperationalQuorum in your cluster.
Operator response
You need to addOperational Quorum toyour cluster.
2621-750
2621-750 SAevent withunknownreason indomain"domain_name".
Explanation
An unknown problem wasreported.
Operator response
Check IBM ElectronicSupport for additionalinformation - http://www.ibm.com/support/entry/portal/
2621-751
2621-751 SAdetected statuschange for
domain"domain_name".
Explanation
The state for thisautomation domain haschanged, or the quorumstate for this automationdomain has changed.
Operator response
Verify that the domainand all its nodes are inthe expected state.
2621-753
2621-753 SAautomationmanager startedsuccessfully indomain"domain_name".
Explanation
The automation managerstarted.
Operator response
No action required.
2621-754
2621-754 SAautomationmanagerstoppedsuccessfully indomain"domain_name".
Explanation
The automation managerstopped.
Operator response
Verify that the automationmanager is intended to bestopped.
2621-755
2621-755 SAdetected aconfigurationpolicy refresh indomain
Chapter 3. Messages 177
"domain_name".
Explanation
A new policy has beenactivated for thisautomation domain.
Operator response
Verify that the action isintended for thisautomation domain.
2621-756
2621-756 SAdetected a newconfiguration indomain"domain_name".
Explanation
A new resource,relationship or requestwas created.
Operator response
No action required.
2621-758
2621-758 SAdetected adeletedconfiguration indomain"domain_name".
Explanation
A resource, relationshipor request was deleted.
Operator response
No action required.
2621-759
2621-759 SAdetected astatus change ofresource"resource_name" in domain"domain_name".
Explanation
The common observed,desired, operational, orcompound state changed.
Operator response
Verify that the new stateis the expected state.
2621-760
2621-760 SAenabled thepublisher"publisher_name" in domain"domain_name".
Explanation
The publisher started.
Operator response
No action required.
2621-761
2621-761 SAdisabled thepublisher"publisher_name" in domain"domain_name".
Explanation
The publisher stopped.
Operator response
Verify that the publisheris intended to be stopped.
2621-770
2621-770 SAstartedautomationoperation forresource group"resource_name" in domain"domain_name".
Explanation
This resource will bestarted or stopped undercontrol of SystemAutomation.
Operator response
No action required.
2621-771
2621-771 SAcompletedautomationoperation forresource group"resource_name" in domain"domain_name".
Explanation
This resource wassuccessfully started orstopped under control ofSystem Automation.
Operator response
No action required.
2621-772
2621-772 SAdetected thatthe system"system_name"switched intomaintenancemode by anoperatorcommand indomain"domain_name".
Explanation
The resources defined onthis system are no longerunder control of SystemAutomation.
Operator response
Verify that this system isintended to be switchedinto maintenance mode.
2621-773
2621-773 SAdetected thatthe system"system_name"switched backto automationmode by anoperatorcommand in
domain"domain_name".
Explanation
The resources defined onthis system are nowunder control of SystemAutomation.
Operator response
Verify that this system isintended to be switchedinto automation mode.
2621-775
2621-775 SAsuspendedautomation forresource"resource_name" in domain"domain_name".
Explanation
An operator requestedsuspending automationfor this resource.
Operator response
If required, resumeautomation for thisresource.
2621-776
2621-776 SAresumedautomation forresource"resource_name" in domain"domain_name".
Explanation
An operator requestedresuming automation forthis resource.
Operator response
If required, suspendautomation for thisresource.
178 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
2621-778
2621-778 SAset the resource"resource_name" online asrequested indomain"domain_name".
Explanation
System Automation hasset the resource onlinesuccessfully.
Operator response
No action required.
2621-779
2621-779 SAset the resource"resource_name" offline asrequested indomain"domain_name".
Explanation
System Automation hasset the resource offlinesuccessfully.
Operator response
No action required.
2621-780
2621-780 SAdetected thatthe system"system_name"joined thedomain"domain_name".
Explanation
A system joined thecluster.
Operator response
No action required.
2621-781
2621-781 SAdetected thatthe system"system_name"
left the domain"domain_name".
Explanation
A system left the cluster.
Operator response
Verify that this system isintended to leave thecluster.
2621-784
2621-784 SAdetected awarning indomain"domain_name". The resource"resource_name" has beendegraded.
Explanation
The resource has beendegraded.
Operator response
Inspect the individualstatus fields of thisresource.
2621-785
2621-785 SAdetected awarning indomain"domain_name". The resource"resource_name" has aperformanceproblem.
Explanation
The resource has aperformance problem.
Operator response
Investigate why theresource respondsslowly.
2621-786
2621-786 SAdetected awarning in
domain"domain_name". The resource"resource_name" has problemscaused by adependency toanotherresource.
Explanation
An automation operationon the specified resourcecannot be performedbecause it depends onanother resource whichprevents the operation.
Operator response
Make sure that one of thesystems where theresource is defined isonline.
2621-788
2621-788 SAdetected aproblem indomain"domain_name". No onlinesystem found tostart resource"resource_name" based on theconfiguration.
Explanation
No online system foundto start the resourcebased on theconfiguration.
Operator response
Verify that all nodes are inthe intended state.
2621-789
2621-789 SAdetected aproblem indomain"domain_name". The resource"resource_name" cannot be set
to the requestedstate.
Explanation
An automation operationon the specified resourcecannot be performed.
Operator response
Inspect the individualstatus fields of thisresource.
2621-790
2621-790 SAdetected aproblem indomain"domain_name". The resource"resource_name" needs amanual reset bythe operator.
Explanation
An automation operationon the specified resourcecannot be performed.
Operator response
Fix the configuration ofthis resource and resetthe automation resource.
2621-791
2621-791 SAdetected aproblem indomain"domain_name". The resource"resource_name" has problemscaused by aoffline system.
Explanation
The resource hasproblems caused by aoffline system.
Operator response
Inspect the system statusof this resource.
Chapter 3. Messages 179
2621-792
2621-792 SAdetected aproblem indomain"domain_name". Theoperationalquorum is lost.
Explanation
The operational quorumis lost.
Operator response
Inspect the clusterstatus.
2621-793
2621-793 Node"node_name"cannot be madeoffline. SystemAutomationManager reportsthat there areresources onlineon this node.
Explanation
Stopping systemautomation on this nodeis prevented because ofrunning resources.
Operator response
There are resourcesonline on this node, thatmust be stopped prior tostopping the systemautomation.
2621-794
2621-794 Nodecan be madeoffline.
Explanation
Stopping systemautomation is notprevented on this node.
Operator response
There are no controllableresources online on thisnode.
2621-795
2621-795 SAdetected thatthe automationis disabled indomain"domain_name"by an operatorcommand.
Explanation
The resources defined onthis cluster are no longerunder control of SystemAutomation.
Operator response
Verify that this cluster isintended to run withautomation turned off.
2621-796
2621-796 SAdetected thatthe automationis enabled indomain"domain_name"by an operatorcommand.
Explanation
The resources defined onthis cluster are now undercontrol of SystemAutomation.
Operator response
Verify that this cluster isintended to run withautomation turned on.
Prefix 2621Tiebreaker2621-400
2621-400Tiebreaker isdefined for
domainDomainName
Explanation
Tiebreaker is defined andcan be activated.
Operator response
No action required.
2621-401
2621-401Tiebreaker isactivated fordomainDomainName
Explanation
The tiebreaker isactivated and ready togive one group leaderquorum in case of acluster split.
Operator response
No action required.
2621-402
2621-402 NodeNodeName indomainDomainNameinitiallyreserved thetiebreaker
Explanation
The node exclusivelyreserved the tiebreakerresource. This is theinitial tiebreakerreservation after clustersplit.
Operator response
No action required.
2621-403
2621-403Tiebreakerreleased ondomainDomainName
Explanation
The release operationsucceeded.
Operator response
No action required.
2621-404
2621-404Heartbeatoperationsucceeded
Explanation
Heartbeat operationexecuted successfully.
Operator response
No action required.
2621-405
2621-405 A notsuccessfulreturn code wasreturned by CAPI functionfunctionName.Warning details:warningDetails.
Explanation
The processing wasinterrupted by this errorbut it can continue.
Operator response
Check the syslog ifadditional errors haveoccurred if you think thismessage should not beseen. Note that such anerror message is notnecessarily an indicationof a real problem.Depending on the kind oferror, some of thesewarnings can be safelyignored.
2621-406
2621-406Tiebreakerreserveoperation failedon domaindomainName.
Explanation
The node failed to getquorum. This is not anerror, it may be due to the
180 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
fact that some other nodehas quorum.
Operator response
No action required.
2621-450
2621-450 The CAPI functionfunctionNamereturned anerror. Errordetails:errorDetails.
Explanation
The processing wasinterrupted by this errorand can not continue.
Operator response
Check the syslog ifadditional errors haveoccurred. Resolve theerrors.
2621-451
2621-451Invalid value fortiebreakerparameterparameterName:parameterValue.
Explanation
The specified value forthe tiebreaker parameteris ignored.
Operator response
Fix the tiebreakerdefinition.
2621-452
2621-452Missingtiebreakerparameter:parameterName.
Explanation
A required parameter wasnot specified.
Operator response
Add the requiredparameter to the tiebreaker definition.
2621-453
2621-453Unknowntiebreakerparameter:parameterName.
Explanation
The specified parameteris not defined.
Operator response
Fix the tiebreakerdefinition.
2621-454
2621-454Missing valuefor tiebreakerparameterparameterName.
Explanation
A value for the specifiedparameter is missing.
Operator response
Add the missing optionvalue to the tie breakerdefinition.
2621-455
2621-455UnknowntiebreakeroperationoperationName.
Explanation
The operation is notknown to the tiebreakerimplementation.
Operator response
The operation is issued byIBM.ConfigRM. CheckIBM Electronic Supportfor additional information- http://www.ibm.com/support/entry/portal/
2621-456
2621-456UnsupportedtiebreakeroperationoperationName.
Explanation
The operation is notsupported by thistiebreaker.
Operator response
Check IBM ElectronicSupport for additionalinformation - http://www.ibm.com/support/entry/portal/
2621-457
2621-457Missingtiebreakeroperation
Explanation
A tiebreaker operation isnot specified.
Operator response
The operation is issued byIBM.ConfigRM. CheckIBM Electronic Supportfor additional information- http://www.ibm.com/support/entry/portal/
2621-458
2621-458 Failedto define thetiebreaker ondomaindomainName.
Explanation
The verify operation ofthe tiebreaker failed.
Operator response
Check the syslog foradditional messages andfix the problem.
2621-459
2621-459 Failedto release thetiebreaker on
domaindomainName.
Explanation
The release operationfailed
Operator response
Fix the NFS server setupand try to manuallyremove the reserve file incase it still exists.
2621-460
2621-460 Failedto activate thetiebreaker ondomaindomainName.
Explanation
The activate operation ofthe tiebreaker failed
Operator response
Check the syslog foradditional messages andfix the problem.
2621-461
2621-461Tiebreakerheartbeatoperation failedon domaindomainName.
Explanation
The node with quorumfailed to renew itsquorum.
Operator response
No action required.
2621-462
2621-462 Out ofmemory.
Explanation
A system request toallocate dynamic memoryfailed.
Chapter 3. Messages 181
Operator response
Make sure that the serverhas enough memory andthat there is noapplication which is usingexcessive memory, forexample due to a memoryleak.
2621-463
2621-463 RSCTAPI returned anerror: details.
Explanation
A problem occurred inRSCT clusterinfrastructure.
Operator response
Check IBM ElectronicSupport for additionalinformation - http://www.ibm.com/support/entry/portal/
2621-464
2621-464Timeoutexecuting thefollowingcommand:commandString.Abortingtiebreakerexecution.
Explanation
Executing the commandfailed due to timeout.
Operator response
Check your environmentand investigate why thecommand was not able toterminate in time.
2621-500
2621-500 NodeNodeName indomainDomainNamesuccessfullychallengedquorum on NFStiebreaker
Explanation
The node exclusivelyreserved the NFStiebreaker resource. Thenode exclusively reservesthe NFS tiebreakerresource, becauseanother node lost quorumbefore.
Operator response
No action required.
2621-501
2621-501 NFStiebreakerterminated ondomaindomainName
Explanation
Because of an operatorrequest to deactivate theNFS tiebreaker, it hasbeen terminated.
Operator response
No action required.
2621-502
2621-502Problemunmounting theNFS quorumserver directoryon nodenodeName,domaindomainName:details.
Explanation
A call to unmount the NFSquorum server directoryfailed.
Operator response
Processing continues.This problem does notdirectly affect the NFStiebreaker. To avoidfuture problems whichare related to this,analyze the root cause ofthe problem.
2621-503
2621-503 NFStiebreaker traceinformation:Details
Explanation
This is detailedinformation enabled bythe Log=2 parameter ofthe samtb_nfs EXECtiebreaker.
Operator response
No action required.
2621-504
2621-504 NodeNodeName indomainDomainNametook initialquorum on NFStiebreaker
Explanation
The node exclusivelyreserved the NFStiebreaker resource aftercluster split.
Operator response
No action required.
2621-505
2621-505 Startof validation.The followingNFS tiebreakerrelatedmessages untilmessage2621-506 do notrefer to actualtiebreakeroperations, butonly to thevalidation oftiebreakerfunctionality.
Explanation
The NFS tiebreakervalidate operationexecutes some of thenormal tiebreakerinstallation for testingpurposes which may
generate messages aspart of normalprocessing. As anexample, one node in thecluster will show the2621-504 message.
Operator response
No action required.
2621-506
2621-506 Endof tiebreakervalidation.
Explanation
The NFS tiebreakervalidate operationterminated. This meansthat the following 2621messages are generatedin a different context thanthe messages embracedby 2621-505 and2621-506 messages.
Operator response
No action required.
2621-550
2621-550Problemoccurredmounting theNFS quorumserver directorydirectoryNameon nodenodeName,domaindomainName.
Explanation
A call to mount the NFSquorum server directoryfailed.
Operator response
Check your installation.Try to manually mount adirectory of your NFSquorum server. Check theNFS tiebreaker relatedtroubleshootinginformation of the SA MPdocumentation.
182 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
2621-551
2621-551Problemaccessing theNFS quorumserver directorydirectoryNameon nodenodeName,domaindomainName:details.
Explanation
Failed to write to or readfrom the NFS quorumserver directory.
Operator response
Try to manually accessthe NFS quorum serverdirectory. Check the NFStiebreaker relatedtroubleshootinginformation of the SA MPdocumentation.
2621-552
2621-552 NFSenvironmentcannot be usedby the NFStiebreaker:reason.
Explanation
A health check founderrors using the NFS v4server. All NFS tiebreakeroperations fail until theNFS server and/or theNFS client is fixed and theNFS tiebreaker isreactivated. In case theNFS server was startedwithin 90 seconds, it isnormal that the validateoperation fails as an NFSserver refuses to acceptlocks during the 90second grace period.
Operator response
Fix the NFS installationand re-activate the NFStiebreaker.
2621-553
2621-553 Failedto read test filefrom NFSquorum serverdirectorydirectoryName.
Explanation
The NFS environmentcannot be used becauseit is not possible to readsimple files from the NFSquorum server directory.
Operator response
Check the log. If you wantto see additional traceinformation, add theLog=2 parameter to theNFS tiebreaker definition.Fix the NFS installationand re-activate the NFStiebreaker.
2621-554
2621-554 Filelock operationtimed out onnode nodeName,domaindomainName.
Explanation
The node which reservedthe NFS tiebreaker failedto get exclusive writeaccess for the reservefile.
Operator response
Check if there is a stalefile lock owned by a nodethat failed after the lockoperation.
Prefix 26222622-001
program_name:2622-001 Not arecognized flag:flag.
Explanation
The flag or combination offlags passed to<program_name> waseither an unsupported
flag or an invalidcombination of flags.
Operator response
Refer to the Usagestatement which lists thevalid flag. Correct thecommand and re-enter.
2622-002
program_name:2622-002 Flag"flag" is notallowed withtheunsupportedoperand"operand".
Explanation
The operand passed withthe flag was anunsupported or invalidoperand or combinationof operands.
Operator response
Refer to the Usagestatement which lists thevalid operand. Correct thecommand and re-enter.
2622-003
program_name:2622-003 Thecombination offlags "flag" and"flag oroperand" is notallowed.
Explanation
The combination of thespecified flags or flag andoperand is not allowed.
Operator response
Either choose a differentflag or do not enter theoperand. Refer to theUsage statement whichlists the valid valid flag,operands, and flagoperand combinations.
2622-004
program_name:2622-004 The
"flag" flag isrequired.
Explanation
The indicated flag mustbe specified when usingthis command.
Operator response
Check the commandsyntax and issue thecommand again.
2622-005
program_name:2622-005 The"flag" flagrequires anoperand.
Explanation
The indicated flag mustbe specified with anoperand when using thiscommand.
Operator response
Check the commandsyntax and issue thecommand again.
2622-006
program_name:2622-006 Thereare no resourcegroups defined.
Explanation
There were no ResourcesGroups.
Operator response
Add Resources Groups.
2622-007
program_name:2622-007 Thereare no memberresourcesdefined.
Explanation
There were no memberResources.
Chapter 3. Messages 183
Operator response
Add member resources togroups.
2622-008
program_name:2622-008 Not avalid number ofoperands.
Explanation
<program_name> wascalled with an invalidnumber of operands.
Operator response
Refer to the Usagestatement which lists thevalid operand. Correct thecommand and re-enter.
2622-009
program_name:2622-009 AnunexpectedRMC erroroccurred. TheRMC returncode wasrmc_return_code.
Explanation
A call to an RMC CLIscript returned anunexpected error.
Operator response
Check to see if RMC isoperational and retry thecommand.
2622-010
program_name:2622-010error_exitreceived anunexpectedreturn codereturn_code.
Explanation
All SAM return codesshould be converted to anappropriate SAM CLI(command line interface)return code. The actualAPI return code or other
internal subroutine returncode is printed. It istreated as a severe errorand processing of thecommand stops.
Operator response
This is an internal scripterror and should notoccur. Check IBMElectronic Support foradditional information -http://www.ibm.com/support/entry/portal/
2622-011
program_name:2622-011 Thespecifiedselection string"selection_string" did not matchany resourcegroups.
Explanation
The specified selectionstring did not match anyresource groups.
Operator response
Check the selection stringand issue the commandagain.
2622-012
program_name:2622-012 Theresource group"resource_group" already exists.
Explanation
The resource groupspecified already exists.
Operator response
Check the resource groupname and issue thecommand again.
2622-013
program_name:2622-013 Theresource group"resource_group" does not exist.
Explanation
The specified resourcegroup name does notexist.
Operator response
Check the resource groupname and issue thecommand again.
2622-014
program_name:2622-014 Theresource"resource_name" not found inthe class"resource_class".
Explanation
The resource specifieddoes not belong in thespecified class.
Operator response
Check the resource andclass name combinationand issue the commandagain.
2622-015
program_name:2622-015 Noneof the resourceswith thespecified typesexists in theirrespectiveclasses.
Explanation
All the resourcesspecified were not foundin their respective classes
Operator response
Make sure the resourceswith the specified typesare part of their classesand then re-entercommand.
2622-016
program_name:2622-016 Noresources werefound with the
selection string"selection_string" from the class"resource_class".
Explanation
No resources were foundusing the specifiedselection string.
Operator response
Check the class name andselection stringcombination and thenissue the command again.
2622-017
program_name:2622-017Resource"resource"already existsas a Member ofGroup"resource_group".
Explanation
Resource already exist asa member resource.
Operator response
No action required.
2622-018
program_name:2622-018Resource"resource" is nota memberresource ofResource Group"resource_group".
Explanation
Resource is not amember resource of thespecified resource group.
Operator response
May be required to addthis resource to thespecified resource group.
184 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
2622-019
program_name:2622-019 All ofthe specifiedresources arealreadymanagedresources.
Explanation
All member resourcesalready exist as amanaged Resource.
Operator response
No action required.
2622-020
program_name:2622-020 Noneof the resourcesspecified arememberresources ofresource group"resource_group".
Explanation
All member resourcesdon't exist for thespecified resource group.
Operator response
Add these resources asmember resources.
2622-021
program_name:2622-021Multiple entriesof the flag flagnot allowed.
Explanation
User had entered thesame flag with operandsmore than once.
Operator response
Re-enter the commandwith only one occurrenceof the concerned flag.
2622-022
program_name:2622-022 Noneof the resources
specified aremanagedresources.
Explanation
None of the resourcesspecified exist asmanaged resources.
Operator response
Check resources and re-enter with validresources.
2622-023
program_name:2622-023Resource"resource" is nota managedresource.
Explanation
Specified resource is nota managed resource.
Operator response
Check Resources and re-enter with validresources.
2622-024
program_name:2622-024 Eitherflag "flag1" or"flag2" or"flag2" isrequired withthe -N flag.
Explanation
One the three flags arerequired when usingcurrent flag.
Operator response
Add the required flags tothe command and tryagain.
2622-025
program_name:2622-025 Thespecified sourceresource"source_resourc
e" does notexist.
Explanation
The specified sourceresource name does notexist in the specifiedclass.
Operator response
Check the resource nameand class namecombination and thenissue the command again.
2622-026
program_name:2622-026 Thespecified sourceselection string"source_string"did not matchany resource.
Explanation
The specified sourceselection string did notmatch any resource in thespecified class.
Operator response
Check the selection stringor class namecombination and thenissue the command again.
2622-027
program_name:2622-027 Morethan onerelations werefound with thesame name"source_resource".
Explanation
More than one relationswas returned for thesource when theoperation only requiresone relationship.
Operator response
Make the query morespecific and issue thecommand again.
2622-028
program_name:2622-028 Namechange notallowed formore than onerelations thatmatched from"query".
Explanation
The selection string orquery returned more thanone source resource.Relation name has to beunique.
Operator response
Check the selection stringor query and issue thecommand again.
2622-029
program_name:2622-029 Thespecifiedequivalency"equivalency"already exists.
Explanation
Specified equivalencyalready exists.
Operator response
Re-enter the commandwith an equivalency namethat does not alreadyexist.
2622-030
program_name:2622-030 Thespecifiedequivalency"equivalency"does not exist.
Explanation
Specified equivalencydoes not exist.
Chapter 3. Messages 185
Operator response
Make sure theequivalency name alreadyexist, re-issue thecommand.
2622-031
program_name:2622-031 Thenode"node_name"does not exist inthe cluster.
Explanation
The node specified doesnot belong in the cluster.
Operator response
Check the node name andissue the command again.
2622-032
program_name:2622-032Resource"resource_name" of resourceclass"class_name" isnot from theallowed nodesfor resourcegroup"Resource_group_name".
Explanation
Member resource is notfrom the allowed nodesfor the new resourcegroup.
Operator response
Member resources mustbe part of the allowednode list of resourcegroup.
2622-033
program_name:2622-033Resource Group"resource_group" has nomemberresources.
Explanation
The specified resourcegroup name does notcontain any memberresources.
Operator response
Check the resource groupname and issue thecommand again.
2622-034
program_name:2622-034 Noresource groupswere found thatmatched thespecified query.
Explanation
No existing resourcegroups matched thespecified Query.
Operator response
Check the resource groupname and issue thecommand again.
2622-035
program_name:2622-035 Nomemberresources werefound thatmatched thespecified query.
Explanation
No existing memberresources matched thespecified query.
Operator response
Check the selection stringor resource group nameand issue the commandagain.
2622-036
program_name:2622-036actual_error_message
Explanation
Display the error messagefrom lsrsrc-api.
Operator response
Check the error Messagefor appropriate action.
2622-037
program_name:2622-037Invalid usererror. Thereturn code wasreturn Code
Explanation
SAM command lineinterface user Error.
Operator response
Check the error messagerfor appropriate action.
2622-038
program_name:2622-038 Noresources werefound. Thereturn code wasreturn Code
Explanation
No resources were found.
Operator response
Check the error messagefor appropriate action.
2622-039
program_name:2622-039 Noresources werespecified forclassclass_name
Explanation
No resources werespecified for the class inthe command line.
Operator response
Repeat the commandwith resources associatedwith the specified class.
2622-040
program_name:2622-040Multipleresources of thesame type werematched forresource"resource_name" from class"resource_class"
Explanation
Multiple resources of thesame resource type werefound for the specifiedresource.
Operator response
Make sure only oneresource is matched withsame Type and then re-enter the command.
2622-041
program_name:2622-041 Noresources wereentered forresource class"resource_class".
Explanation
Resources were notentered with thecommand for thespecified class.
Operator response
Enter the resources andretry the command.
2622-042
program_name:2622-042 Noselection stringwas entered forresource class"resource_class".
Explanation
Selection string was notentered with thecommand for thespecified class.
186 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Operator response
Enter the resources andretry the command.
2622-061
program_name:2622-061 Thespecifiedresource groupinput file"input_file_name" does notexist.
Explanation
Specified resource filename was not found.
Operator response
Make sure the resourcegroup file name exist, re-enter the command.
2622-062
program_name:2622-062 Failedto createresource groupsfrom thespecifiedresource groupinput file"input_file_name".
Explanation
Failed to create resourcegroups from the specifiedresource file.
Operator response
Correct the associatederror with this and, re-enter the command.
2622-063
program_name:2622-063 Noneof the nodesspecified existsin the cluster.
Explanation
The specified nodenames do not exist in thecluster.
Operator response
Check the node namesand issue the commandagain.
2622-081
program_name:2622-081 Noneof the specifiedresource groupswere found orcould not beremoved.
Explanation
None of the specifiedresource group orselection string matchedany existing resourcegroups or some of themjust couldn't be removed.
Operator response
Check the message thatpreceded this messagefor the actual cause, ifresource groups alreadyexists.
2622-082
program_name:2622-082Resource group"resource_group" does not existor could not beremoved.
Explanation
The specified resourcegroup was not found oreven if it was found it justcouldn't be removed.
Operator response
Check the message thatpreceded this messagefor the actual cause, ifresource group alreadyexists.
2622-083
program_name:2622-083ResourceGroups matchedby the specifiedselection string
"selection_string" could not beremoved or didnot exist.
Explanation
The specified selectstring did not match anyexisting group or even if itwas found it just couldn'tbe removed.
Operator response
Check the message thatpreceded this messagefor the actual cause, ifresource group alreadyexists.
2622-101
program_name:2622-101 Mustchangeattributes ofresource group"resource_group".
Explanation
At least one of theresource group attributesmust be changed whenusing chrg command.
Operator response
Enable the appropriateoptions to changerequired attributes ofresource group.
2622-102
program_name:2622-102Cannot changename of morethan oneresource group.
Explanation
Can only change name ofone resource group at atime.
Operator response
Repeat the commandwith only one resourcegroup.
2622-103
program_name:2622-103 Noneof the specifiedresource groupswere found orcould not bechanged.
Explanation
None of the specifiedresource group orselection string matchedany existing resourcegroups or some of themjust couldn't be changed.
Operator response
Check the message thatpreceded this messagefor the actual cause, ifresource groups alreadyexists.
2622-104
program_name:2622-104Resource Group"resource_group" does not existor could not bechanged.
Explanation
The specified resourcegroup was not found oreven if it was found it justcouldn't be changed.
Operator response
Check the message thatpreceded this messagefor the actual cause, ifresource group alreadyexists.
2622-105
program_name:2622-105Allowed node ofResource Group"resource_group" could not be
Chapter 3. Messages 187
changed to node"node_name".
Explanation
The specified resourcegroup's allowed nodecould not be changed tothe specified nodebecause its members arenot from this node.
Operator response
Specify a node orequivalency that containsall the nodes of theresource groupsmembers.
2622-106
program_name:2622-106Allowed node ofResource Group"resource_group" could not bechanged to theequivalency"equiv_name".
Explanation
The specified resourcegroup's allowed nodecould not be changed tothe specified equivalencybecause its members arenot from the nodes in theequivalency.
Operator response
Specify a node orequivalency that containsall the nodes of theresource groupsmembers.
2622-107
program_name:2622-107Allowed node ofall the specifedresource groupscould not bechanged.
Explanation
The specified resourcegroup's allowed node
could not be changed tothe specified equivalencyor node because itsmembers are not fromthe node or nodes in theequivalency.
Operator response
Specify a node orequivalency that containsall the nodes of theresource groupsmembers.
2622-108
program_name:2622-108 Thespecified node"excluded_node" does not existin the list.
Explanation
The specified node namedoes not exist in theexcluded node list.
Operator response
Check the node name andissue the command again.
2622-109
program_name:2622-109 Thespecified node"excluded_node" already existsin the list.
Explanation
The specified node namealready exists in theexcluded node list.
Operator response
Check the node name andissue the command again.
2622-110
program_name:2622-110 Noneof the nodesspecified existsin the list.
Explanation
The specified nodenames do not exist in theexcluded node list.
Operator response
Check the node namesand issue the commandagain.
2622-111
program_name:2622-111 Noneof the nodesspecified existsin the cluster.
Explanation
The specified nodenames do not exist in thecluster.
Operator response
Check the node namesand issue the commandagain.
2622-112
program_name:2622-112 Allthe nodesspecifiedalready exists inthe list.
Explanation
All the nodes specifiednodes already exist in theexcluded node list.
Operator response
Check the node namesand issue the commandagain.
2622-113
program_name:2622-113 Toomany groupswere specifiedto change to thenewExcludedList.
Explanation
Only one group name canbe specified to change
the excluded node listattribute.
Operator response
Check the group nameand issue the commandagain.
2622-121
program_name:2622-121 Noresources wereentered forresource class"resource_class".
Explanation
Resources were notentered with thecommand for thespecified class.
Operator response
Enter the resources andretry the command.
2622-122
program_name:2622-122 NoSelection stringentered forResource class"resource_class".
Explanation
Selection string was notentered with thecommand for thespecified class.
Operator response
Enter the selection stringand retry the command.
2622-123
program_name:2622-123 Noneof the specifiedmemberresources arefrom theallowed nodesfor resourcegroup"resource_group".
188 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Explanation
All of the specifedresources are not in theallowed node list of thenew resource group.
Operator response
Member resources mustbe part of the allowednode list of resourcegroup.
2622-124
program_name:2622-124 Thespecifiedmanagedresource inputfile"input_file_name" does notexist.
Explanation
Specified resource filename was not found.
Operator response
Make sure the managedresource file name exist,re-enter the command.
2622-125
program_name:2622-125 Failedto createresources fromthe specifiedmanagedresource inputfile"input_file_name".
Explanation
Failed to create resourcesfrom the specifiedresource file.
Operator response
Correct the associatederror with this and, re-enter the command.
2622-126
program_name:2622-126 Noneof the nodes
specified existsin the cluster.
Explanation
The specified nodenames do not exist in thecluster.
Operator response
Check the node namesand issue the commandagain.
2622-127
program_name:2622-127 Fixedresource"resource_name" is not allowedto have anExcludedList.
Explanation
The specified fixedresource can not bemoved, therefore pointless to carry anExcludedList.
Operator response
Add all the fixedresources without anExcludedList.
2622-128
program_name:2622-128 Noneof the specifiedmanagedresources werecreated.
Explanation
None of the specifiedmanaged resources werecreated because theywere fixed resources.
Operator response
Add all the fixedresources without anExcludedList or Policy.
2622-141
program_name:2622-141 Noresources were
entered forresource class"resource_class".
Explanation
Resources were notentered with thecommand for thespecified class.
Operator response
Enter the resources andretry the command.
2622-142
program_name:2622-142 Noselection stringwas entered forresource class"resource_class".
Explanation
Selection string was notentered with thecommand for thespecified class.
Operator response
Enter the resources andretry the command.
2622-161
program_name:2622-161 Mustchangeattributes ofmemberresources.
Explanation
At least one of themember resourceattributes must bechanged when usingchrgmbr command.
Operator response
Enable the appropriateoptions to changerequired attributes ofresource group.
2622-162
program_name:2622-162 Noresources wereentered forresource class"resource_class".
Explanation
Resources were notentered with thecommand for thespecified class.
Operator response
Enter the resources andretry the command.
2622-163
program_name:2622-163 Noselection stringwas entered forResource class"resource_class".
Explanation
Selection string was notentered with thecommand for thespecified class.
Operator response
Enter the resources andretry the command.
2622-164
program_name:2622-164 Noneof the specifiedmemberresources arefrom theallowed nodesfor resourcegroup"resource_group".
Explanation
All of the specifedresources are not in theallowed node list of thenew resource group.
Chapter 3. Messages 189
Operator response
Member resources mustbe part of the allowednode list of resourcegroup.
2622-165
program_name:2622-165 Thespecified node"excluded_node" does not existin the list.
Explanation
The specified node namedoes not exist in theexcluded node list.
Operator response
Check the node name andissue the command again.
2622-166
program_name:2622-166 Thespecified node"excluded_node" already existsin the list.
Explanation
The specified node namealready exists in theexcluded node list.
Operator response
Check the node name andissue the command again.
2622-167
program_name:2622-167 Noneof the nodesspecified existsin the list.
Explanation
The specified nodenames do not exist in theexcluded node list.
Operator response
Check the node namesand issue the commandagain.
2622-168
program_name:2622-168 Noneof the nodesspecified existsin the cluster.
Explanation
The specified nodenames do not exist in thecluster.
Operator response
Check the node namesand issue the commandagain.
2622-169
program_name:2622-169 Allthe nodesspecifiedalready exists inthe list.
Explanation
All the nodes specifiednodes already exist in theexcluded node list.
Operator response
Check the node namesand issue the commandagain.
2622-170
program_name:2622-170 Toomany resourceswere specifiedto change to thenewExcludedList.
Explanation
Only one resource can bespecified to change theexcluded node listattribute.
Operator response
Check the resource countand issue the commandagain.
2622-171
program_name:2622-171 Fixed
resource"resource_name" is not allowedto have anExcludedList orPolicy.
Explanation
The specified fixedresource can not bemoved, therefore pointless to carry anExcludedList orSelectFromPolicy.
Operator response
Change all the fixedresources without anExcludedList or Policy.
2622-172
program_name:2622-172 Noneof the specifiedmanagedresources werecreated.
Explanation
None of the specifiedmanaged resources werecreated because theywere fixed resources.
Operator response
Change all the fixedresources without anExcludedList or Policy.
2622-181
program_name:2622-181 Thespecified Sourceresourcesource_resourceis not a memberresource.
Explanation
specified SourceResource is not amember resource.
Operator response
Make sure the source is amember resource, thenre-issue the command.
2622-182
program_name:2622-182 Thespecified sourceresourcematched fromselection string"source_string"is not a memberresource.
Explanation
specified source resourcematched from selectionstring is not a memberresource.
Operator response
Make sure the source is amember resource, thenre-issue the command.
2622-183
program_name:2622-183Source resource"source_resource" alreadyexists.
Explanation
Source resource cannotalready exist whencreating it.
Operator response
Use chrel to makechanges to therelationships related tothis source resource.
2622-184
program_name:2622-184Source resourcematched fromselection string"sourceresource"already exists.
190 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Explanation
Source resource cannotalready exist whencreating it.
Operator response
Use chrel to makechanges to the relationsrelated to this sourceresource.
2622-185
program_name:2622-185 Noneof the specifiedsourceresourcesExists.
Explanation
There were no sourceresources.
Operator response
No action required.
2622-186
program_name:2622-186 Noneof the specifiedtarget resourcesExists.
Explanation
There were no targetresources.
Operator response
No action required.
2622-187
program_name:2622-187 Morethan one sourceresources werematched for"source".
Explanation
More than one sourcewas matched forspecified source name.
Operator response
No action required.
2622-188
program_name:2622-188 Morethan one sourceresource werematched usingselection string"selection_string" on class_nameclass .
Explanation
More than one sourcewas matched with sourceselection string.
Operator response
No action required.
2622-189
program_name:2622-189Specifiedcondition is notallowed withthe relationship"relationship".
Explanation
Only locate-withrelationships are allowedto have conditions.
Operator response
No action required.
2622-190
program_name:2622-190 Thespecifiedmanagedrelationshipinput file"input_file_name" does notexist.
Explanation
Specified managedresource file name wasnot found.
Operator response
Make sure the managedrelationship file nameexist, re-enter thecommand.
2622-191
program_name:2622-191 Failedto createresources fromthe specifiedrelationshipinput file"input_file_name".
Explanation
Failed to create resourcesfrom the specifiedrelationship input file.
Operator response
Correct the associatederror with this and, re-enter the command.
2622-201
program_name:2622-201 Norelationshipsmatched thequery"source_query."
Explanation
Source query did notmatch any existingrelationships.
Operator response
Check the query and re-run the command.
2622-202
program_name:2622-202 Thereare norelationshipsdefined forsource "source"matched fromselection string"selection_string".
Explanation
Source resource mustalready have arelationship defined.
Operator response
Use mkrel to makerelationships related tothis source resource.
2622-203
program_name:2622-203 Noneof the specifiedtarget resourcesexists.
Explanation
There were no targetresources.
Operator response
No action required.
2622-204
program_name:2622-204 Noneof the specifiedtarget resourceshaverelationshipswith the source.
Explanation
The specified targetresources were notrelated to the source.
Operator response
Re-enter the commandwith existing targetresources for the source.
2622-205
program_name:2622-205 All ofthe specifiedtarget resourcesalready haverelationshipswith the source.
Explanation
All specified targetresources already haverelationship with thesource.
Operator response
Re-enter the commandwith target resources that
Chapter 3. Messages 191
don't already exist for thesource.
2622-206
program_name:2622-206Target resourcetarget_resourcealready hasrelationshipwith the source.
Explanation
Target resource alreadymaintains relationshipwith the Source.
Operator response
Use the delete targetresource option toremove targets or donothing.
2622-207
program_name:2622-207Target resource"target_resource" does not haveany relationshipwith the source.
Explanation
Target resource does notmaintain any relationshipwith the Source.
Operator response
Use mkrel to makerelationships related tothis source resource.
2622-208
program_name:2622-208 Atleast onechange must bemade to therelationship.
Explanation
No changes wererequested by thecommand.
Operator response
Use chrel to change oneor more attributes of therelations related to thissource resource.
2622-209
program_name:2622-209 Thereare no relationsdefined forsourcesmatched fromselection string"selection_string".
Explanation
Selection string did notmatch a relationship.
Operator response
Use mkrel to makerelationships related tothis source resource.
2622-210
program_name:2622-210 Theselection string"selection_string" did not matchanyrelationships.
Explanation
Selection string did notmatch a relationship.
Operator response
Re-enter command withstring that will match atleast a relationship.
2622-211
program_name:2622-211 Themanagedrelation"managed_relation" does notexist as arelationship.
Explanation
The managed relationspecified does not exist.
Operator response
Re-enter command withan existing managedrelationship.
2622-212
program_name:2622-212 Noneof the queriedtarget resourcesExists.
Explanation
The target resources usedto query the relationshipsdo not exist.
Operator response
No action required.
2622-213
program_name:2622-213 Noneof the specifiedsourceresourcesexists.
Explanation
There were no sourceresources.
Operator response
No action required.
2622-214
program_name:2622-214Specifiedcondition is notallowed withthe relationship"relationship".
Explanation
Only locationrelationships are allowedto have conditions.
Operator response
No action required.
2622-221
program_name:2622-221 Norelationshipsmatched the
query"source_query."
Explanation
Source query did notmatch any existingrelationships.
Operator response
Check the query and re-run the command.
2622-222
program_name:2622-222 Thereare norelationshipsdefined forsource resource"source"matched fromselection string"selection_string".
Explanation
Source resource mustalready have arelationship defined.
Operator response
Use mkrel to makerelationships related tothis source resource.
2622-223
program_name:2622-223 Thereare norelationshipsdefined for anyof the specifiedsourceresources.
Explanation
Source resource mustalready have arelationship defined.
Operator response
Use mkrel to makerelationships related tothis source resource.
192 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
2622-224
program_name:2622-224 Theselection string"selection_string" did not matchany managedrelations.
Explanation
Selection string did notmatch any managedrelations.
Operator response
Re-enter the commandwith string that will matchat least one managedrelations.
2622-225
program_name:2622-225 Noneof the specifiedrelation"relation_names" exists.
Explanation
All the managed relationsspecified does not exist.
Operator response
Re-enter the commandwith at least one existingmanaged relations.
2622-226
program_name:2622-226 Noneof the specifiedqueried targetresourcesexists.
Explanation
The target resources usedto query the relationshipsdo not exist.
Operator response
No action required.
2622-227
program_name:2622-227 Noneof the specifiedsource
resourcesexists.
Explanation
There were no sourceresources.
Operator response
No action required.
2622-228
program_name:2622-228Relationship"relation_name"does not exist orcould not beremoved.
Explanation
Specified relationshipwas not found or even if itwas found it just couldn'tbe removed.
Operator response
Check the message thatpreceded this messagefor the actual cause ifalready exists.
2622-229
program_name:2622-229 Noneof the specifiedRelationshipswere found orcould not beremoved.
Explanation
None of the specifiedrelationships or selectionstring matched anyexisting relationships orsome of them justcouldn't be removed.
Operator response
Check the message thatpreceded this messagefor the actual cause.
2622-261
program_name:2622-261 Thespecified
logicdeck file"logicdeck_filename" with the"option_flag"flag does notexist.
Explanation
The specified logic deckfile name does not existin the specified location.
Operator response
Check the logic deck filename and issue thecommand again.
2622-262
program_name:2622-262 Atleast onechange must bemade to theSAM Controls.
Explanation
No changes wererequested by thecommand.
Operator response
Use appropriate samctrlflags to change one ormore sam controlsattributes.
2622-263
program_name:2622-263 Thespecified node"excluded_node" does not existin the list.
Explanation
The specified node namedoes not exist in theexcluded node list.
Operator response
Check the node name andissue the command again.
2622-264
program_name:2622-264 Thespecified node
"excluded_node" already existsin the list.
Explanation
The specified node namealready exists in theexcluded node list.
Operator response
Check the node name andissue the command again.
2622-265
program_name:2622-265 Noneof the nodesspecified existsin the list.
Explanation
The specified nodenames do not exist in theexcluded node list.
Operator response
Check the node namesand issue the commandagain.
2622-266
program_name:2622-266 Noneof the nodesspecified existsin the cluster.
Explanation
The specified nodenames do not exist in thecluster.
Operator response
Check the node namesand issue the commandagain.
2622-267
program_name:2622-267 Allthe nodesspecifiedalready exists inthe list.
Chapter 3. Messages 193
Explanation
All the nodes specifiednodes already exist in theexcluded node list.
Operator response
Check the node namesand issue the commandagain.
2622-268
program_name:2622-268Specifiedengine actionfailed.
Explanation
Specified engine actionfailed to processsuccessfully.
Operator response
No action required.
2622-269
Program_name:2622-269Migration actionfailed withreturn code"return_code".
Explanation
Specified Migration actionfailed to processsuccessfully.
Operator response
No action required.
2622-270
Program_name:2622-270Install LicenseAction failedwith return code"return_code".
Explanation
Install License actionfailed to processsuccessfully.
Operator response
No action required.
2622-271
program_name:2622-271Specifiedlicense file"FileName" doesnot exist.
Explanation
License file could not befound at specifiedlocation.
Operator response
Re-enter the commandwith a valid file name.
2622-272
program_name:2622-272Specifiedpublisher"publisher_name" is notenabled.
Explanation
Publisher is not in the listof lssamctrlEnablePublisher.
Operator response
Re-enter the commandwith a valid publisher.
2622-273
Program_name:2622-273 Postmigration script"script_name"failed withreturn code"return_code".
Explanation
Specified post migrationscript failed to processsuccessfully.
Operator response
No action required.
2622-281
program_name:2622-281 Thespecifiedequivalencyinput file
"input_file_name" does notexist.
Explanation
Specified equivalency filename was not found.
Operator response
Make sure theequivalency file nameexist, re-enter thecommand.
2622-282
program_name:2622-282 Noresources wereentered forresource class"resource_class".
Explanation
Resources were notentered with thecommand for thespecified class.
Operator response
Enter the resources andretry the command.
2622-283
program_name:2622-283 NoSelection stringwas entered forResource class"resource_class".
Explanation
Selection string was notentered with thecommand for thespecified class.
Operator response
Enter the resources andretry the command.
2622-284
program_name:2622-284 TheattributeSelectFromPolic
y does not allowany other valuethan Any ifoption"option_flag" isset.
Explanation
Selection string was notentered withSelectFromPolicy Any.
Operator response
Retry making equivalencywith SelectFromPolicyAny.
2622-285
program_name:2622-285 Failedto createresources fromthe specifiedequivalencyinput file"input_file_name".
Explanation
Failed to create resourcesfrom the specifiedequivalency input file.
Operator response
Correct the associatederror with this and, re-enter the command.
2622-286
program_name:2622-286 All ofthe specifedmembers forequivalency"equivalency_name" are floatingresources.
Explanation
All of the specifiedmembers are floatingresources, but as a rulefor equivalency they cannot be included as amembers of anequivalency
194 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Operator response
Add at least a fixedresources as a member ofan equivalency.
2622-301
program_name:2622-301 Theequivalency"equivalency"already has aSelectStringdefined.
Explanation
There is already aSelectString definedtherefore won't allow anadd or delete function.
Operator response
Try using the overwritefunction for command.
2622-302
program_name:2622-302 Nochanges weremade to theequivalency"equivalency".
Explanation
Specified equivalency didnot change.
Operator response
Re-enter the commandbased on the informationthat preceded this error.
2622-303
program_name:2622-303 Atleast onechange must bemade to theequivalency"equivalency".
Explanation
Must make a changewhen using thiscommand.
Operator response
Specify a change to theequivalency when issuingthe command.
2622-304
program_name:2622-304 Noresources wereentered forresource class"resource_class".
Explanation
Resources were notentered with thecommand for thespecified class.
Operator response
Enter the resources andretry the command.
2622-305
program_name:2622-305 Noselection stringwas entered forresource class"resource_class".
Explanation
Selection string was notentered with thecommand for thespecified class.
Operator response
Enter the resources andretry the command.
2622-306
program_name:2622-306 Policyother than Anyis not allowedwith option"option_flag".
Explanation
Selection string was notentered withSelectFromPolicy Any.
Operator response
Retry changingequivalency with PolicyAny.
2622-307
program_name:2622-307Equivalency"equivalency"does not exist orcould not bechanged.
Explanation
Specified equivalencywas not found or even if itwas found it just couldnot be changed.
Operator response
Check the message thatpreceded this messagefor the actual cause if italready exists.
2622-308
program_name:2622-308 All ofthe specifedmembers forequivalency"equivalency_name" are floatingresources.
Explanation
All of the specifiedmembers are floatingresources, but as a rulefor equivalency they cannot be included as amembers of anequivalency. Themembers will not beupdated and will be leftalone.
Operator response
Add at least a fixedresources as a member ofan equivalency.
2622-321
program_name:2622-321 Noneof the specifiedequivalencies
were found orcould not beremoved.
Explanation
None of the specifiedequivalencies were foundor just could not beremoved.
Operator response
Check the message thatpreceded this messagefor the actual cause.
2622-322
program_name:2622-322Equivalency"equivalency"does not exist orcould not beremoved.
Explanation
Specified equivalencywas not found or even if itwas found it just couldnot be removed.
Operator response
Check the message thatpreceded this messagefor the actual cause if italready exists.
2622-323
program_name:2622-323 Theselection string"selection_string" did not matchanyequivalencies.
Explanation
The specified selectionstring did not match anyequivalencies.
Operator response
Check the equivalencyselect string and issue thecommand again.
Chapter 3. Messages 195
2622-341
program_name:2622-341 Norelationshipsmatched thequery"source_Querry."
Explanation
Source query did notmatch any existingrelationships.
Operator response
Check the query and re-run the command.
2622-342
program_name:2622-342 Thereare norelationshipsdefined thatmatched fromselection string"selection_string".
Explanation
Selection string did notmatch to an existingrelationship.
Operator response
Use mkrel to make thisrelationships.
2622-343
program_name:2622-343 Themanagedrelation"selection_string" does not exist.
Explanation
The managed relationspecified does not exist.
Operator response
Re-enter command withan existing managedrelationship.
2622-344
program_name:2622-344 There
are norelationshipsdefined.
Explanation
There are no managedrelations currentlydefined.
Operator response
Re-enter command withan existing managedrelationship.
2622-345
program_name:2622-345 Thespecified targetselection string"target_string"did not matchany resource.
Explanation
The specified targetselection string did notmatch any resource in thespecified class.
Operator response
Check the selection stringor class namecombination and issuethe command.
2622-346
program_name:2622-346 Thespecified targetresources"target_resource" does not exist.
Explanation
The specified resourcewas not found in thespecified class.
Operator response
Check the resource andissue the command again.
2622-347
program_name:2622-347 Noneof the specifiedqueried target
resourcesexists.
Explanation
The Target resourcesused to query therelationships does notexist in the relationship.
Operator response
No action required.
2622-348
program_name:2622-348 Noneof the specifiedrelationshipsexists.
Explanation
None of the relationshipsspecified exists.
Operator response
No action required.
2622-349
program_name:2622-349 Noneof the specifiedsourceresourcesExists.
Explanation
There were no sourceresources.
Operator response
No action required.
2622-361
program_name:2622-361 Thereare noequivalenciesdefined thatmatched fromselection string"selection_string".
Explanation
No equivalenciesmatched the select string.
Operator response
No action required.
2622-362
program_name:2622-362 Theequivalency"equivalency"does not exist.
Explanation
The equivalency specifieddoes not exist.
Operator response
Re-enter command withan existing equivalency.
2622-363
program_name:2622-363 Thereare NoEquivalenciesdefined.
Explanation
There are noequivalencies currentlydefined.
Operator response
Re-enter command aftercreating an existingequivalency.
2622-381
Program_name:2622-381 ListLicense Actionfailed withreturn code"return_code".
Explanation
List License action failedto process successfully.
Operator response
No action required.
2622-401
program_name:2622-401 Noresources wereentered forresource class"resource_class".
196 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Explanation
Resources were notentered with thecommand for thespecified class.
Operator response
Enter the resources andretry the command.
2622-402
program_name:2622-402Samdiag actionfailed withreturn code"error_code".
Explanation
Samdiag action failed toacquire information onspecified resource.
Operator response
Refer to related errormessages or return codeand then rerun commandbased on thosemessages.
2622-403
program_name:2622-403Resourcehandle"resource_handle" could not beresolved.
Explanation
Resource handle used toacquire information couldnot be resolved to anactual resource.
Operator response
Enter resource handlesthat exist.
2622-421
program_name:2622-421Samcfg actionfailed withreturn code"error_code".
Explanation
Samcfg action failed forthe specified reason.
Operator response
Refer to related errormessages or return codeand then rerun commandbased on thosemessages.
2622-422
program_name:2622-422Specified file"resource_handle" is not in theSAMConfigurationfile format.
Explanation
File associated with thecommand does not seemto be the format designedfor SAM Configuration.
Operator response
Correct the format of fileif possible and re-runcommand with file again.
2622-423
program_name:2622-423InvalidCommand"Command" infile "FileName".
Explanation
Command found inconfiguration file is notvalid.
Operator response
Correct the entry in fileand then re-run thecommand again.
2622-424
program_name:2622-424Specified file"FileName" notfound.
Explanation
Configuration file couldnot be found at thespecified location.
Operator response
Enter the correct path forthe file and re-run thecommand.
2622-425
program_name:2622-425 Noneof the clustersare online onthis node.
Explanation
None of the clustersdefined on this node areonline.
Operator response
Bring this node online in acluster,and re-run thecommand.
2622-426
program_name:2622-426Specified file"FileName" doesnot exist.
Explanation
Restore file could not befound at specifiedlocation.
Operator response
Re-enter the commandwith a valid file name.
2622-427
program_name:2622-427Specified file"FileName" didnot contain anySAMcommands.
Explanation
Restore file were missingSAM commands.
Operator response
Re-enter the commandwith a valid file namecontaining SAMcommands.
2622-428
program_name:2622-428 Timedout waiting foruser promptwhile restoringfrom file"FileName".
Explanation
User did not respond in90 secs when promptedto continue restoration.
Operator response
Re-enter the commandbut respond as whenprompted promptly.
2622-429
program_name:2622-429 Erroropeningspecified file"FileName":Error.
Explanation
Specified file could not beopened.
Operator response
Re-enter the commandafter the problemindicated by the error isresolved.
2622-441
program_name:2622-441Samdvs actionfailed withreturn code"error_code".
Explanation
Samdvs action failed toacquire information onspecified resource.
Chapter 3. Messages 197
Operator response
Refer to related errormessages or return codeand then rerun commandbased on thosemessages.
2622-442
program_name:2622-442 Thespecified inputfile"input_filename" does not exist.
Explanation
Specified DVS input filewas not found at thespecified location.
Operator response
Make sure the DVS fileexists, then re-enter thecommand.
2622-443
program_name:2622-443 Thespecified outputfile"DVS_Outputfile" already existand was notoverwritten.
Explanation
Specified DVS Output filealready exist at thespecified location andwas not overwritten.
Operator response
Make sure the DVS filedon't exist or isoverwritten whenprompted, then re-enterthe command.
2622-444
program_name:2622-444 Thespecified file"filename"failed to openwith return code"return_code".
Explanation
Specified DVS file failedto open.
Operator response
Retry the command withthe trace option to findthe error messagesindicating the reason forthis failure. Fix it ifpossible then re -enterthe command.
2622-445
program_name:2622-445 Thespecified file"filename"failed to closewith return code"return_code".
Explanation
Specified DVS file failedto close.
Operator response
Retry the command withthe trace option to findthe error messagesindicating the reason forthis failure. Fix it ifpossible then re-enter thecommand.
2622-446
program_name:2622-446Writing to thespecified file"filename"failed withreturn code"return_code".
Explanation
Specified DVS file failedwhen attempted to bewritten .
Operator response
Retry the command withthe trace option to findthe error messagesindicating the reason forthis failure. Fix it if
possible then re-enter thecommand.
2622-461
program_name:2622-461 Mustbe a moveaction.
Explanation
This must a Move action.
Operator response
Re-enter the request as amove action.
2622-462
program_name:2622-462"node_name"name is not avalid nodename.
Explanation
The specified node nameis not valid node.
Operator response
Repeat the commandwith a valid node name.
2622-463
program_name:2622-463request actionon resourcegroup failedwith return code"error_code".
Explanation
Request action on thespecified resource groupfailed.
Operator response
Refer to related errormessages or return codeand then rerun commandbased on thosemessages.
2622-481
program_name:2622-481 Mustbe a moveaction.
Explanation
This must a Move action.
Operator response
Re-enter the request as amove action.
2622-482
program_name:2622-482"node_name"name is not avalid nodename.
Explanation
The specified node nameis not valid node.
Operator response
Repeat the commandwith a valid node name.
2622-483
program_name:2622-483request actionon managedresources failedwith return code"error_code".
Explanation
Request action on thespecified managedresources failed.
Operator response
Refer to related errormessages or return codeand then rerun commandbased on thosemessages.
2622-484
program_name:2622-484 Noresources wereentered forresource class"resource_class".
Explanation
Resources were notentered with the
198 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
command for thespecified class.
Operator response
Enter the resources andretry the command.
2622-485
program_name:2622-485 NoSelection stringentered forResource class"resource_class".
Explanation
Selection string was notentered with thecommand for thespecified class.
Operator response
Enter the selection stringand retry the command.
2622-486
program_name:2622-486 Moveaction is notallowed formanagedresources.
Explanation
Move Action is notallowed when requestedon a managed resource.
Operator response
Move can only be appliedto a resource group.
2622-501
program_name:2622-501 Noresources wereentered forresource class"resource_class".
Explanation
Resources were notentered with thecommand for thespecified class.
Operator response
Enter the resources andretry the command.
2622-502
program_name:2622-502 Noselection stringwas entered forresource class"resource_class".
Explanation
Selection string was notentered with thecommand for thespecified class.
Operator response
Enter the resources andretry the command.
2622-503
program_name:2622-503 Listrequest actionfailed withreturn code"error_code".
Explanation
List request action on thespecified managedresources failed.
Operator response
Refer to related errormessages or return codeand then rerun commandbased on thosemessages.
2622-519
program_name:2622-519 Noonline domainfound.
Explanation
No online domain and noonline node found.
Operator response
Start domain.
2622-521
program_name:2622-521 Foundfields_foundsimulation datafields wherefields_expectedwere expectedat file_name lineline_number.
Explanation
A line in the simulationinput contains more orless data fields than arerequired.
Operator response
Add the missing or deletethe extra data field(s) andretry the command.
2622-522
program_name:2622-522Invalid prioritycode "priority"found atfile_name lineline_number.Valid values are"low", "high",and "force".
Explanation
A line in the simulationinput contains an invalidpriority code.
Operator response
Correct the erroneouspriority code and retry thecommand.
2622-523
program_name:2622-523Invalid actioncode "action"found atfile_name lineline_number.Valid values are"noop", "start","stop", "move","cancel","failed",
"online", and"offline".
Explanation
A line in the simulationinput contains an invalidaction code.
Operator response
Correct the erroneousaction code and retry thecommand.
2622-524
program_name:2622-524 Nosimulation inputdata found infile_name.
Explanation
The simulation input doesnot contain any non-comment, non-emptylines.
Operator response
Retry the command,submitting validsimulation data as input.
2622-525
program_name:2622-525samsimul actionfailed withreturn code"error_code".
Explanation
samsimul action failed tosubmit the simulationinput data and retrievesimulation results.
Operator response
Refer to related errormessages or return codeand then rerun command\n based on thosemessages.
2622-526
program_name:2622-526Unexpectedoutput when
Chapter 3. Messages 199
runningsamsimulaction.
Explanation
samsimul action failed toreturn an output of theexpected format.
Operator response
This is an internal scripterror and should notoccur. Check IBMElectronic Support foradditional information -http://www.ibm.com/support/entry/portal/
2622-541
program_name:2622-541 Noresource groupsdefined orcluster isoffline!
Explanation
Currently no resourcegroups defined or thecluster is offline.
Operator response
Define resource groups orturn the cluster online.
2622-561
program_name:2622-561 Nojava runtimefound atjava_path.
Explanation
The java runtime was notfound at the expectedlocation.
Operator response
Verify the installation hasbeen successful andverify the userid hassufficient access rights tothe location.
2622-562
program_name:2622-562 No
domain isonline.
Explanation
The program cannot beexecuted, because noonline domain is found.
Operator response
Start the domain. Thenissue the command again.
2622-572
program_name:2622-572Incorrect optionspecifiedoption_specified.
Explanation
The option specified isnot valid.
Operator response
Use a valid option asshown in the usagestatement and rerun thecommand.
2622-573
program_name:2622-573Command notfoundcommand.
Explanation
The command was notfound when the programtried to call it.
Operator response
Verify that the installationhas been successful.
2622-574
program_name:2622-574 Toplevel XML filenot found atfile_path.
Explanation
The top level XML file wasnot found at the expectedlocation.
Operator response
Verify the installation hasbeen successful andverify the userid hassufficient access rights tothe location.
2622-575
program_name:2622-575Specifiedproperties filenot foundfile_path.
Explanation
The specified propertiesfile was not found.
Operator response
Verify the specifiedproperties file and verifythe userid has sufficientaccess rights.
2622-576
program_name:2622-576Creating domainvia mkrpdomaincommandfailed.
Explanation
The program tried tocreate a domain via thecommand mkrpdomain.This command failed.
Operator response
Check the related errormessages and try toresolve the problem.Then rerun the program.
2622-577
program_name:2622-577Calling thesampolicycommandfailed.
Explanation
The program tried to callthe command sampolicy.This command failed.
Operator response
Check the related errormessages and try toresolve the problem.Then rerun the program.
2622-578
program_name:2622-578Removingdomain viarmrpdomaincommandfailed.
Explanation
The program tried toremove a domain via thecommand rmrpdomain.This command failed.
Operator response
Check the related errormessages and try toresolve the problem.Then rerun the program.
2622-579
program_name:2622-579Starting domainviastartrpdomaincommandfailed.
Explanation
The program tried to starta domain via thecommand startrpdomain.This command failed.
Operator response
Check the related errormessages and try toresolve the problem.Then rerun the program.
2622-580
program_name:2622-580Preparingdomain viapreprpnodecommandfailed.
200 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Explanation
The program tried toprepare a domain via thecommand preprpnode.This command failed.
Operator response
Check the related errormessages and try toresolve the problem.Then rerun the program.
2622-581
program_name:2622-581Domain doesnot exist.
Explanation
The program tried toremove a domain thatdoes not exist.
Operator response
Verify that you enteredthe correct domain name.
2622-582
program_name:2622-582Domain doesalready exist.
Explanation
The program tried tocreate a domain that doesalready exist.
Operator response
No action required.
2622-583
program_name:2622-583Domain isoffline andcannot beremoved.
Explanation
The program tried toremove a domain that isoffline.
Operator response
Start the domain. Thenissue the command again.
2622-584
program_name:2622-584 Notable to write tofile file_path.
Explanation
The program was not ableto write to its outputdirectory.
Operator response
Verify the userid hassufficient rights.
2622-585
program_name:2622-585eezautomatecommandfailed.
Explanation
The program tried to callthe commandeezautomate. Thiscommand failed.
Operator response
Check the related errormessages and try toresolve the problem.Then issue the commandagain.
2622-591
program_name:2622-591 Noonline domainfound.
Explanation
No online domain and noonline node found.
Operator response
Start domain.
2622-592
program_name:2622-592Invalid optionvalue:
option_name"option_value"
Explanation
The specified option isnot valid.
Operator response
Use a valid option asshown in the usagestatement and rerun thecommand.
2622-593
program_name:2622-593Invalid usage ofoptions:option_list
Explanation
The specifiedcombination of options isnot valid.
Operator response
Use a valid combinationof options as shown in theusage statement andrerun the command.
2622-594
program_name:2622-594 Oneor more optionsare missing:option_list
Explanation
The specified optionrequires addtionaloptions.
Operator response
Use a valid set of optionsas shown in the usagestatement and rerun thecommand.
2622-595
program_name:2622-595Command"command"failed withreturn codereturn_code.
Explanation
Execution of commandfailed.
Operator response
Use option -T to getfurther information aboutthe problem.
2622-596
program_name:2622-596Command"command"timed out aftersecondsseconds.
Explanation
Execution of commandtimed out.
Operator response
Use option -T to getfurther information aboutthe problem.
2622-597
program_name:2622-597Missingrequiredinfrastructure:infrastructure
Explanation
Infrastructure forexecution of samlog ismissing.
Operator response
Provide requiredinfrastructure.
2622-611
program_name:2622-611 ErrorTest Message.
Explanation
Error Test Message.
Operator response
Nothing to do.
Chapter 3. Messages 201
2622-612
program_name:2622-612Invalid option:option_value
Explanation
The specified option isnot valid.
Operator response
Use a valid option asshown in the usagestatement and rerun thecommand.
2622-613
program_name:2622-613Invalid timeformat:time_format_value
Explanation
The specified time formatis not valid.
Operator response
Use a valid time format asshown in the usagestatement and rerun thecommand.
2622-614
program_name:2622-614Command:failing_command failed
Explanation
The samwhy programcalled a command thatfailed.
Operator response
Rerun the samwhycommand adding theoption --debug andanalyze the output.
2622-615
program_name:2622-615 Noactive peerdomain found
Explanation
No active peer domainwas found.
Operator response
The samwhy programneeds an active peerdomain to run. Start apeer domain and rerunthe command.
2622-616
program_name:2622-616 Tracespoolingconfigurationdiffers betweenresource_manager1 andresource_manager2 on nodenodename
Explanation
The trace spoolingconfiguration must beidentical for everyresource manager onevery node.
Operator response
Correct the trace spoolingconfiguration and rerunthe command.
2622-617
program_name:2622-617 Tracespoolingconfigurationdiffers betweennodenodename1 andnodenodename2
Explanation
The trace spoolingconfiguration must beidentical on every node.
Operator response
Correct the trace spoolingconfiguration and rerunthe command.
2622-618
program_name:2622-618Command:failing_command failed withoutput:command_output
Explanation
The samwhy programcalled a command thatfailed.
Operator response
Analyze the output andtry to fix the problem,then rerun the samwhycommand.
2622-901
program_name:2622-901Attributes andArguments aremismatched.
Explanation
Arguments are missingfor some of the attributesin the input file.
Operator response
Repeat the command byupdating the input file.
2622-902
program_name:2622-902 Donot specifyattributeattribute whendefiningresourceresource_classrow: row.
Explanation
Arguments are missingfor some of the attributesin the input file.
Operator response
Repeat the command byupdating the input file.
2622-903
program_name:2622-903 Errorprocessingattributeattribute_namevalue"attribute_value".
Explanation
The value for thisparticular attribute is notvalid. See the precedingerror message foradditional details.
Operator response
Verify the data type forthis particular attributeusing the lsrsrcdefcommand. Verify andcorrectly specify thevalue so that it isappropriate for this datatype. For example, if thedata type is an array, thevalues must be enclosedwithin curly braces { }.See the appropriatecommand man page andthe man page for theResource Data Input Filefor valid syntax values.
2622-904
program_name:2622-904Requiredargumentargument_nameargument name(SD elementname) forresourceresource_classname of theresource classmust bespecified.
Explanation
The specified commandarguments for thisresource class and thiscommand must bespecified.
202 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Operator response
Run lscmdargdefcommand to see the listof argument names anddata types expected asinput for this command.
2622-905
program_name:2622-905 Noresources wereentered forresource class"resource_class".
Explanation
Resources were notentered with thecommand for thespecified class.
Operator response
Enter the resources andretry the command.
2622-906
program_name:2622-906 Failedto create someor all resourcesfrom Input file"input_file_name".
Explanation
Failed to create some orall resources from inputfile for specified class.
Operator response
Check the file data,correct if possible and re-run command.
2622-907
program_name:2622-907 Fixedresourceresource onnodenode_name isnot a managedresource.
Explanation
Specified fixed resourceis not a managedresource.
Operator response
Check Resources and re-enter with validresources.
2622-908
program_name:2622-908Resource"resource_name" of resourceclass"class_name" isnot from theallowed nodesfor the Topresource group"Top_Resource_group_name".
Explanation
Member resource is notfrom the allowed nodesfor the new resourcegroup's top most group.
Operator response
Member resources mustbe part of the allowednode list of resourcegroup and its top mostgroup.
2622-909
program_name:2622-909 AConsumer isrequired for theSpecifiedsubscription"Subscription".
Explanation
Specified Subscription ismissing the consumer.
Operator response
Re-enter subscriptionwith a valid Consumer.
2622-910
program_name:2622-910 The
event family"event_family"specified withthe subscription"subscription" isnot supported.
Explanation
Specified Subscriptioncontains an invalid eventfamily value.
Operator response
Re-enter subscriptionwith a valid event family.
2622-911
program_name:2622-911 Theevent filter"event_filter"specified withthe subscription"subscription" isnot supported.
Explanation
Specified Subscriptioncontains an invalid eventfilter value.
Operator response
Re-enter subscriptionwith a valid event filter.
2622-912
program_name:2622-912Consumer"consumer" canbe specifiedmore than oncefor the sameresource.
Explanation
Only one subscription perconsumer is allowed to aresource.
Operator response
Re-enter subscriptionwithout any duplicateconsumer.
2622-913
program_name:2622-913Subscription"subscription"already exist asa subscription.
Explanation
Specified subscriptionalready exist for thespecified resource.
Operator response
No action required.
2622-914
program_name:2622-914Subscription"subscription"can be found.
Explanation
Specified subscriptiondoes not exist for thisresource, thereforecannot be removed.
Operator response
No action required.
2622-915
program_name:2622-915 Noneof thesubscriptionspecified existsin the list.
Explanation
The specifiedsubscriptions do not existin the subscription list.
Operator response
Check the subscriptionsand issue the commandagain.
2622-916
program_name:2622-916 AlltheSubscriptionsspecifiedalready exists inthe list.
Chapter 3. Messages 203
Explanation
All the specifiedsubscriptions alreadyexist in the subscriptionlist.
Operator response
Check the subscriptionnames and issue thecommand again.
2622-917
program_name:2622-917 Whenspecifying aselect-frompolicy, thecombination ofvalues options isnot allowed.
Explanation
The combination of thespecified option is notallowed.
Operator response
Either choose a differentoption or do not enter the
operand. Refer to theUsage statement whichlists the valid valid flag,operands, and flagoperand combinations.
2622-918
program_name:2622-918 Whenspecifying aselect-frompolicy, either ofthe values "A"or "O" isrequired.
Explanation
One of the specifiedvalues must be providedwhen specifying a select-from policy.
Operator response
Either choose one of thegiven values or do notspecify a policy. Refer tothe Usage statementwhich lists the valid validflag, operands, and flagoperand combinations.
Prefix 26612661-001
2661-001Attribute"attribute_name" cannot bespecified whendefining a newresource.
Explanation
While attempting tocreate an Applicationresource, an attributewas encountered that isnot allowed to be defined.
Operator response
Do not specify thisattribute whenattempting to create anApplication resource.
2661-002
2661-002 Thevalue of theMonitorCommandPeriod
attribute mustbe greater orequal to thevalue of theMonitorCommandTimeoutattribute.
Explanation
While attempting tocreate or change anApplication resource, acombination ofMonitorCommandPeriodandMonitorCommandTimeout attributes wasencountered that is notvalid.
Operator response
Correct the value foreither theMonitorCommandPeriod
or theMonitorCommandTimeout attribute, such that theMonitorCommandPeriodis greater or equal to theMonitorCommandTimeout.
2661-003
2661-003 Classname"class_name" isnot recognizedby this resourcemanager.
Explanation
The Resource Managerdoes not recognize thenamed resource class asbelonging to it. This iseither an internal error orindicates a corruptedRMC configuration.
Operator response
Check IBM ElectronicSupport for additionalinformation - http://www.ibm.com/support/entry/portal/
2661-004
2661-004 Couldnot initializecontrol point forclass"class_name".
Explanation
The Resource Managerwas unable to create andinitialize RCCP for thenamed resource class.
Operator response
Make sure the system hasplenty of resources(paging space,available /var file systemspace, and so on).
2661-005
2661-005 Thevalue of theMonitorCommandPeriodattribute must
be greater than0.
Explanation
While attempting tocreate or change anApplication resource, aMonitorCommandPeriodattribute wasencountered that is lowerthan zero.
Operator response
Correct the value for theMonitorCommandPeriodattribute to be greaterthan 0.
2661-006
2661-006 Thestart commanddid notcompletesuccessfully,exit code is theexit value fromthe startcommand.Stdout = stdoutgenerated by thestart commandStderr = stderrgenerated by thestart command
Explanation
In response to a requestto bring a resource online,the associated startcommand was executedbut it did not completesuccessfully. The exitcode, stderr and stdoutare listed in the errormessage.
Operator response
Attempt to correct theproblems identified bythe output from thecommand and retry theoperation.
2661-007
2661-007 Thestop commanddid not
204 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
completesuccessfully,exit code is theexit value fromthe stopcommand.Stdout = stdoutgenerated by thestop commandStderr = stderrgenerated by thestop command
Explanation
In response to a requestto take a resource offline,the associated stopcommand was executedbut it did not completesuccessfully. The exitcode, stderr and stdoutare listed in the errormessage.
Operator response
Attempt to correct theproblems identified bythe output from thecommand and retry theoperation.
2661-008
2661-008 Thevalue of theResourceTypeattribute mustbe 0, 1 or 2.
Explanation
While attempting tocreate or change anApplication resource, aResourceType attributewas encountered that isnot valid.
Operator response
Correct the value for theResourceType attributeto be either 0 (for fixedresources), 1 (for floatingresources) or 2 (forconcurrent resources).
2661-009
2661-009 Thevalue of the
RunCommandsSync attributemust smallerthan 256.
Explanation
While attempting tocreate or change anApplication resource, aRunCommandsSyncattribute wasencountered that is notvalid.
Operator response
Correct the value for theRunCommandsSyncattribute to be either 0(for "fire and forget" ofstart/stop commands) or1 (starting/stoppingresources will wait for thecompletion of start/stopcommands) as well asvarious other valuecombinations.
2661-010
2661-010 Theuser namespecified is notvalid or does notexist.
Explanation
While attempting tocreate or change anApplication resource, auser name wasencountered that is notvalid or does not exist.
Operator response
Correct the user name orensure that the username is defined on eachtarget node where theresource is to exist.
2661-011
2661-011 Thecommandspecified forattribute theattribute namethat thecommand in
error is specifiedfor is NULL, nota absolute path,does not exist orhas insufficientpermissions tobe run.
Explanation
While attempting tocreate or change anApplication resource, acommand string for thespecified attribute wasencountered that is notvalid. The command iseither a NULL string, isnot an absolute path,does not exist or hasinsufficient permissionsto be run.
Operator response
Correct the value to beone a valid command onall the target nodes orensure that the specifiedcommand exists on alltarget node and has theproper permissions.
2661-012
2661-012 Thespecifiednetmask "thespecifiednetmask inerror" is notvalid.
Explanation
While attempting tocreate or change aServiceIP resource, aninvalid value for theNetMask attribute wasencountered.
Operator response
Correct the value to beone of the validrepresentations forspecifying a netmasksuch as xxx.xxx.xxx.xxx oran empty string in whichcase the netmask will be
inherited from thenetwork interface that itis activated on.
2661-013
2661-013 Thespecified IPaddress "thespecified IPaddress in error"is not valid.
Explanation
While attempting tocreate or change aServiceIP resource, aninvalid value for theIPAddress attribute wasencountered.
Operator response
Correct the value to beone of the validrepresentations forspecifying an IP addresssuch as xxx.xxx.xxx.xxx.
2661-014
2661-014 Thenetworkinterfacespecified for usein bringing an IPaddress onlinedoes not exist oris not valid.
Explanation
The resource managerwas requested to bring anIP address online and thespecified supportingresource (a networkinterface) does not existor is not usable.
Operator response
Chose a differentsupporting resource touse in the online request.
2661-015
2661-015 Themaximumnumber ofaliases arealready activeon network
Chapter 3. Messages 205
interfaceinterface_name.
Explanation
The resource managerwas requested to bring anIP address online but thespecified interface to beused already has themaximum number ofaliases active.
Operator response
Either deactivate somealiases or chose anotherinterface to be used forthis service IP address.
2661-016
2661-016 Thereset commanddid notcompletesuccessfully,exit code is theexit value fromthe resetcommand.Stdout = stdoutgenerated by thereset commandStderr = stderrgenerated by thereset command
Explanation
In response to a requestto reset a resource, theassociated resetcommand was executedbut it did not completesuccessfully. The exitcode, stderr and stdoutare listed in the errormessage.
Operator response
Attempt to correct theproblems identified bythe output from thecommand and retry theoperation.
2661-017
2661-017 Thestart commandtimed out, exit
code is the exitvalue from thestart command.Stdout = stdoutgenerated by thestart commandStderr = stderrgenerated by thestart command
Explanation
In response to a requestto bring a resource online,the associated startcommand was run but itexceeded the time limitand was ended. The exitcode, stderr and stdoutare listed in the errormessage.
Operator response
Attempt to correct theproblems identified bythe output from thecommand and retry theoperation.
2661-018
2661-018 Thestop commandtimed out, exitcode is the exitvalue from thestop command.Stdout = stdoutgenerated by thestop commandStderr = stderrgenerated by thestop command
Explanation
In response to a requestto take a resource offline,the associated stopcommand was run but itexceeded the time limitand was ended. The exitcode, stderr and stdoutare listed in the errormessage.
Operator response
Attempt to correct theproblems identified by
the output from thecommand and retry theoperation.
2661-019
2661-019 Thereset commandtimed out, exitcode is the exitvalue from thereset command.Stdout = stdoutgenerated by thereset commandStderr = stderrgenerated by thereset command
Explanation
In response to a requestto reset a resource, theassociated resetcommand was run but itexceeded the time limitand was ended. The exitcode, stderr and stdoutare listed in the errormessage.
Operator response
Attempt to correct theproblems identified bythe output from thecommand and retry theoperation.
2661-020
2661-020 Thevalue specifiedfor the attributenamedProtectionModemust be either 0or 1.
Explanation
An invalid value wasspecified for the attributenamed ProtectionMode.
Operator response
Correct the valuespecified and retry theoperation.
2661-021
2661-021 Thecommand usedto monitor the
resource did notcompletesuccessfully,exit code is theexit value fromthe monitorcommand.Stdout = stdoutgenerated by themonitorcommandStderr = stderrgenerated by themonitorcommand
Explanation
While monitoring theoperational state of aresource, the associatedmonitor command wasexecuted but it did notcomplete successfully.The exit code, stderr andstdout are listed in theerror message.
Operator response
Attempt to correct theproblems identified bythe output from thecommand and retry theoperation.
2661-022
2661-022 Thecommand usedto monitor theresource timedout, exit code isthe exit valuefrom the monitorcommand.Stdout = stdoutgenerated by themonitorcommandStderr = stderrgenerated by themonitorcommand
Explanation
While monitoring theoperational state of aresource, the associatedmonitor command was
206 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
run but it exceeded thetime limit and wasstopped. The exit code,stderr and stdout arelisted in the errormessage.
Operator response
Attempt to correct theproblems identified bythe output from thecommand and retry theoperation.
2661-023
2661-023 TheIP addressspecified is thebase addressfor a networkinterface andthereforecannot be used.
Explanation
The address specified isalready the base IPaddress for a networkinterface which makes itinvalid for use as aservice IP address.
Operator response
Choose a different IPaddress and retry theoperation.
2661-024
2661-024 Theresource"resource_name" cannot bedeleted becauseit is online.
Explanation
The resource cannot bedeleted because it isonline.
Operator response
Make sure the resource isoffline and retry theoperation or delete theresource forcefully withthe Force=1 parameter.
2661-025
2661-025 Theoperationcannot becompletedbecause one ormore resourcesfrom theresource classname class isonline.
Explanation
The operation (stop node,stop domain or removedomain) cannot becompleted because oneor more resources areonline on the targetnode(s).
Operator response
Make sure the resource isoffline and retry theoperation.
2661-026
2661-026Invalidparameterformat passedto theconfigCoordinationAll action forresource classresource classname.
Explanation
The configCoordinationAllaction was received bythe RM for the indicatedclass but the input formatis not valid or notsupported.
Operator response
Check IBM ElectronicSupport for additionalinformation - http://www.ibm.com/support/entry/portal/
2661-027
2661-027 Anonline or offlineoperation is notvalid when the
resource is inthe failed offlinestate.
Explanation
An online or offlineoperation was targeted toa resource that is in thefailed offline state. This isnot a valid request. Theonly control operationthat is permitted in thefailed offline state isreset.
Operator response
Perform the resetoperation against theresource and then retrythe online or offlineoperation. The command'resetrsrc' can be used toreset a resource.
2661-028
2661-028Receiver of theSendEIFevent isnot online, ornot aconstituentresource.
Explanation
An internal error of theGblResRM.
Operator response
Check IBM ElectronicSupport for additionalinformation - http://www.ibm.com/support/entry/portal/
2661-029
2661-029Resourcereceived a startcommand but isalready inpending onlinestate.
Explanation
An online operation wastargeted to a resourcethat is in the pending
online state. This is not avalid request. The onlycontrol operation that ispermitted in the pendingonline state is reset.
Operator response
Perform the resetoperation against theresource and then retrythe online operation. Thecommand 'resetrsrc' canbe used to reset aresource.
2661-030
2661-030Resourcereceived a stopcommand, butis already inpending offlinestate.
Explanation
An offline operation wastargeted to a resourcethat is in the pendingoffline state. This is not avalid request. The onlycontrol operation that ispermitted in the pendingoffline state is reset.
Operator response
Perform the resetoperation against theresource. The command'resetrsrc' can be used toreset a resource.
2661-031
2661-031 Thecleanupcommand timedout, exit code isthe exit valuefrom the cleanupcommand.Stdout = stdoutgenerated by thecleanupcommandStderr = stderrgenerated by thecleanupcommand
Chapter 3. Messages 207
Explanation
In response to a requestto cleanup a resource, theassociated cleanupcommand was run but itexceeded the time limitand was ended. The exitcode, stderr and stdoutare listed in the errormessage.
Operator response
Attempt to correct theproblems identified bythe output from thecommand and retry theoperation.
2661-032
2661-032 Thecleanupcommand didnot completesuccessfully,exit code is theexit value fromthe cleanupcommand.Stdout = stdoutgenerated by thecleanupcommandStderr = stderrgenerated by thecleanupcommand
Explanation
In response to a requestto cleanup a resource, theassociated cleanupcommand was executedbut it did not completesuccessfully. The exitcode, stderr and stdoutare listed in the errormessage.
Operator response
Attempt to correct theproblems identified bythe output from thecommand and retry theoperation.
2661-033
2661-033 Themove complete
command timedout, exit code isthe exit valuefrom the movecompletecommand.Stdout = stdoutgenerated by themove completecommandStderr = stderrgenerated by themove completecommand
Explanation
In response to a requestto complete a move, theassociated movecomplete command wasrun but it exceeded thetime limit and was ended.The exit code, stderr andstdout are listed in theerror message.
Operator response
Attempt to correct theproblems identified bythe output from thecommand and retry theoperation.
2661-034
2661-034 Themove completecommand didnot completesuccessfully,exit code is theexit value fromthe movecompletecommand.Stdout = stdoutgenerated by themove completecommandStderr = stderrgenerated by themove completecommand
Explanation
In response to a requestto complete a move, theassociated move
complete command wasexecuted but it did notcomplete successfully.The exit code, stderr andstdout are listed in theerror message.
Operator response
Attempt to correct theproblems identified bythe output from thecommand and retry theoperation.
2661-035
2661-035 Themove cancelcommand timedout, exit code isthe exit valuefrom the movecancelcommand.Stdout = stdoutgenerated by themove cancelcommandStderr = stderrgenerated by themove cancelcommand
Explanation
In response to a requestto cancel a failed move,the associated movecancel command was runbut it exceeded the timelimit and was ended. Theexit code, stderr andstdout are listed in theerror message.
Operator response
Attempt to correct theproblems identified bythe output from thecommand and retry theoperation.
2661-036
2661-036 Themove cancelcommand didnot completesuccessfully,exit code is theexit value from
the move cancelcommand.Stdout = stdoutgenerated by themove cancelcommandStderr = stderrgenerated by themove cancelcommand
Explanation
In response to a requestto cancel a failed move,the associated movecancel command wasexecuted but it did notcomplete successfully.The exit code, stderr andstdout are listed in theerror message.
Operator response
Attempt to correct theproblems identified bythe output from thecommand and retry theoperation.
2661-037
2661-037 Atleast one of theentries of theCleanupList isnot valid.
Explanation
While attempting tocreate or change anApplication resource, aCleanupList attribute withan invalid entry wasencountered.
Operator response
Correct the invalid entryof the CleanupListattribute.
2661-038
2661-038 MovePrepare,Complete,Cancel andCleanup actionscannot beissued against
208 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
aggregateresources.
Explanation
The attempt to issue oneof the above mentionedactions against anaggregate resource wasrejected.
Operator response
Run the action against theconstituents of theaggregate resource.
2661-039
2661-039IBM.Applicationstart/stopcommand timedout. Resourcename:resource_name
Explanation
The Resource Managerkilled the start/stopcommand because it didnot return within thespecified timeframe.
Operator response
Check the time the start/stop command needs tocomplete. Adapt theStartCommandTimeout/StopCommandTimeoutattribute if necessary.
2661-040
2661-040IBM.Applicationmonitorcommand timedout. Resourcename:resource_name
Explanation
The Resource Managerkilled the monitorcommand because it didnot return within thespecified commandtimeout.
Operator response
Check the time themonitor command needsto complete. Adapt theMonitorCommandTimeout attribute if necessary.
2661-041
2661-041IBM.Applicationhealthcommand timedout. Resourcename:resource_name
Explanation
The Resource Managerkilled the healthcommand because it didnot return within thespecified commandtimeout.
Operator response
Check the time the healthcommand needs tocomplete. Adapt theHealthCommandTimeoutattribute if necessary.
2661-042
2661-042IBM.Applicationcould not runthe monitorcommand.Resource name:resource_name
Explanation
The Resource Managercould not run the monitorcommand because it isnot accessible or hasinsufficient permissions.
Operator response
Check that the ResourceManager can access themonitor command duringoperation even if theresource itself is offline.
2661-043
2661-043IBM.Applicationreceived reset
request.Resource name:resource_name
Explanation
IBM.Application resourcereceived a reset requesteither by automation orby manual resetrsrccommand.
Operator response
If the reset comes fromautomation, check theapplication resource.Maybe one of the pendingoperational states lasttoo long and automationtries to recover thisapplication errorcondition.
2661-044
2661-044IBM.ServiceIPassignedaddress todevice. IPaddress:ip_address
Explanation
IBM.ServiceIP assignedIP address to networkinterface.
Operator response
IBM.ServiceIPsuccessfully assigned anIP address to a networkinterface.
2661-045
2661-045IBM.ServiceIPfailed to assignaddress todevice. IPaddress:ip_address
Explanation
IBM.ServiceIP failed toassign IP address tonetwork interface.
Operator response
Check your ServiceIPaddress setup. Make surethe IP address can beassigned to the networkdevice. Take careIBM.ServiceIP can eitherautomatically choose adevice or it is connectedto an equivalency ofnetwork interfaces.
2661-046
2661-046IBM.ServiceIPremovedaddress. IPaddress:ip_address
Explanation
IBM.ServiceIP removedIP address from networkinterface.
Operator response
IBM.ServiceIPsuccessfully removed anIP address from anetwork interface.
2661-047
2661-047IBM.ServiceIPfailed to removeaddress. IPaddress:ip_address
Explanation
IBM.ServiceIP failed toremove an IP addressfrom network interface.
Operator response
Check your IP addresssetup. Remove theServiceIP address withthe ifconfig command.
2661-048
2661-048IBM.Applicationfailed toterminate ahanging monitorcommand forresource
Chapter 3. Messages 209
resource_namedue to a glibcbug.
Explanation
IBM.Application could notterminate a hangingmonitor command.
Operator response
This bug is caused by awell known glibc bug.
2661-049
2661-049Invalidparameterformat passedto the actionname action forresource classresource classname.
Explanation
The action was receivedby the RM for theindicated class but theinput format is not validor not supported.
Operator response
Check the action'sparameters according tothe action's definition.
2661-050
2661-050Invalid securitytoken for theregisterPIDsaction againstresourceresource name.
Explanation
The action was receivedby the RM for theindicated class but thesecurity token for settingthe resource state is notvalid
Operator response
Check the security tokenwhich was sent to theresource with its startcommand.
2661-051
2661-051Cannot runcommand namecommand forresourceresource nameon node nodename, becausethis node isdown.
Explanation
The action was receivedby the RM for theindicated class but thecommand could not berouted to the target nodebecause this node isdown.
Operator response
Check the status of thenode that is targetted bythe command.
2661-052
2661-052 Theresource"resource_name" cannot bedeleted becauseits operationalstate isunknown.
Explanation
The resource cannot bedeleted because itsoperational state isunknown.
Operator response
Make sure the resource isoffline and retry theoperation or delete theresource forcefully withthe Force=1 parameter.
2661-053
2661-053 Thevalue specified
for the attributeResourceTypemust be either 0or 1.
Explanation
An invalid value wasspecified for the attributeResourceType.
Operator response
Correct the valuespecified and retry theoperation.
2661-054
2661-054Specifying pidprobing is notallowed whentheProcessCommandString isempty.
Explanation
An invalid value wasspecified for the attributeRunCommandsSync
Operator response
Correct the valuespecified and retry theoperation.
2661-055
2661-055Attribute"attribute_name" is notavailable forSystemAutomation inversions lowerthan 3.2.
Explanation
While attempting tocreate an Application
resource, an attributewas encountered that isnot allowed to be definedin this version of SystemAutomation.
Operator response
Do not specify thisattribute whenattempting to create anApplication resource.
2661-056
2661-056AttributeCleanupCommandTimeout isnot allowed tobe 0 whenCleanupCommand is set.
Explanation
An invalid value wasspecified for the attributeCleanupCommandTimeout.
Operator response
orrect the value specifiedand retry the operation.
2661-057
2661-057 Thevalue specifiedfor the attributeSetHealthStatemust be in therange [0 - 33].
Explanation
An invalid value wasspecified for the attributeSetHealthState.
Operator response
Correct the valuespecified and retry theoperation.
Prefix 26622662-001
2662-001Attribute"attribute_name" cannot bespecified when
defining a newresource.
210 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Explanation
While attempting tocreate an Applicationresource, an attributewas encountered that isnot allowed to be defined.
Operator response
Do not specify thisattribute whenattempting to create anApplication resource.
2662-002
2662-002Attribute"attribute_name" appears in arequest morethan once.
Explanation
An attribute appears in arequest more than once.
Operator response
Specify an attribute in arequest only once.
2662-003
2662-003 Classname"class_name" isnot recognizedby this resourcemanager.
Explanation
The Resource Managerdoes not recognize thenamed resource class asbelonging to it. This iseither an internal error orindicates a corruptedRMC configuration.
Operator response
Check IBM ElectronicSupport for additionalinformation - http://www.ibm.com/support/entry/portal/
2662-004
2662-004 Couldnot initializecontrol point for
class"class_name".
Explanation
The Resource Managerwas unable to create andinitialize RCCP for thenamed resource class.
Operator response
Make sure the system hasplenty of resources(paging space,available /var file systemspace, and so on).
2662-005
2662-005Attribute"attribute_name" must bespecified whendefining a newresource.
Explanation
The ResourceManagerwas unable to create theresource because amandatory attribute wasnot defined.
Operator response
Make sure to specifiy thisattribute during creationof the resource.
2662-006
2662-006 Thevalue of theattribute mustbe 0 or 1.
Explanation
The value of this attributemust be 0 or 1.
Operator response
Change the attribute to 0or 1.
2662-007
2662-007 Thevalue of theResourceTypeattribute mustbe 0, 1 or 2.
Explanation
While attempting tocreate or change anApplication resource, aResourceType attributewas encountered that isnot valid.
Operator response
Correct the value for theResourceType attributeto be either 0 (for fixedresources), 1 (for floatingresources) or 2 (forconcurrent resources).
2662-008
2662-008 Thetime in theStart/Stop/Move attributemust be >= 0and < 600 (10min)
Explanation
The specified value forthis attribute is not withinthe allowed range.
Operator response
Specifiy a value between0 and 600.
2662-009
2662-009 Thevalue ofForceOpStatemust be a validrmc opstate(0,1,2,3,4,5,6,8)
Explanation
The specified value doesnot match a valid rmcopstate.
Operator response
Specifiy on of thefollowing opstates0,1,2,3,4,5,6,8.
2662-010
2662-010Resource doesnot supportmove protocol
Explanation
The resource received amove action but does notsupport the moveprotocol.
Operator response
Do not move theresource.
2662-011
2662-011Resourcecannot bemoved becauseit is not anaggregateresource
Explanation
The resource received amove action but is not anaggregate resource. Onlyaggregate resources canbe moved.
Operator response
Do not move theresource.
2662-012
2662-012Resource not inmove stateNONE whenprepare actionreceived
Explanation
The resource received amove prepare action butis not in move state none.
Operator response
Check if another action isin progress. Wait until therunning action iscomplete. Issue therequest again.
2662-013
2662-013Resource not inmove stateREADY whencomplete actionreceived
Chapter 3. Messages 211
Explanation
The resource received amove complete action butis not in move stateready.
Operator response
Check if another action isin progress. Wait until therunning action iscomplete. Issue therequest again.
2662-014
2662-014Complete/Cancel action orcleanup isalready inprogress
Explanation
The requested process isalready running.
Operator response
Wait until the action iscomplete.
2662-015
2662-015Prepare actionis already inprogress
Explanation
The requested process isalready running.
Operator response
Wait until the action iscomplete.
2662-016
2662-016Resource not inREADY orFAILED statewhen cancelaction received
Explanation
The resource received amove cancel action but isnot in move state ready orfailed.
Operator response
Check if another action isin progress. Wait until therunning action iscomplete. Issue therequest again.
2662-017
2662-017Attribute"attribute_name" cannot bespecified whendefining a newresource.
Explanation
While attempting tocreate a Test resource, anattribute wasencountered that is notallowd to be defined.
Operator response
Do not specify thisattribute whenattempting to create aTest resource.
2662-018
2662-018Wrong inputspecified for theaction.
Explanation
An internal error of theTestRM.
Operator response
Check IBM ElectronicSupport for additionalinformation - http://www.ibm.com/support/entry/portal/
2662-019
2662-019IBM.Testreceived anonline request.Resource name:resource_name
Explanation
IBM.Test resourcereceived an onlinerequest.
Operator response
IBM.Test successfullystarted.
2662-020
2662-020IBM.Testreceived anoffline request.Resource name:resource_name
Explanation
IBM.Test resourcereceived an offlinerequest.
Operator response
IBM.Test successfullystopped.
2662-021
2662-021IBM.Testreceived a resetrequest.Resource name:resource_name
Explanation
IBM.Test resourcereceived a reset request.
Operator response
IBM.Test successfullyreset.
2662-022
2662-022IBM.Test isonline.Resource name:resource_name
Explanation
IBM.Test is online.
Operator response
IBM.Test has beensuccessfully started.
2662-023
2662-023IBM.Test isoffline.Resource name:resource_name
Explanation
IBM.Test is offline.
Operator response
IBM.Test has beensuccessfully stopped.
2662-024
2662-024IBM.TestOpState hasbeen forced.Resource name:ResourceNameForceOpState
Explanation
IBM.Test OpState hasbeen forced.
Operator response
IBM.Test OpState hasbeen successfully forced.
2662-025
2662-025IBM.TestMoveState hasbeen forced.Resource name:ResourceNameForceMoveState
Explanation
IBM.Test MoveState hasbeen forced.
Operator response
IBM.Test MoveState hasbeen successfully forced.
212 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
sampolicy messagesThis topic lists the messages that are generated by the sampolicy command and start with the prefixSAMP. The sampolicy command may also generate messages starting with the prefix EEZ.
These messages are listed in the IBM Tivoli System Automation Application Manager Reference andProblem Determination Guide.
Prefix SAMPSAMP0001E An 'IOException' was caught in
method methodName of classclassName. The received messagewas message.
Explanation
The processing was interrupted by this exception andcannot complete.
System action
The task is ended.
Operator response
Try to resolve the problem described in the exceptionmessage and resubmit the command.
SAMP0002E The specified policy policyLocationis not valid.
Explanation
The policy is not valid. You cannot perform any taskwith this policy.
System action
The current task ends.
Operator response
Try to make the policy valid by analyzing the errormessages following this message. Then resubmit thecommand.
SAMP0003E Not able to create an object oftype Object-type. The name of thetree-node is node-name.
Explanation
There is a problem when building an internal object ofthe input XML.
System action
The current task ends.
Operator response
Check for related messages that may describe the rootcause of the problem.
SAMP0004E Not able to retrieve the policyinformation.
Explanation
The policy information cannot be retrieved becausethe policy is not valid.
System action
The current task ends.
Operator response
Try to make the policy valid by analyzing all the errormessages.
SAMP0005E Received errors when trying toactivate the policy.
Explanation
Policy activation task resulted in errors.
System action
The activation task ends.
Operator response
Analyze the error messages and try to resolve theproblem.
SAMP0006E The specified policy file policyFilecannot be found.
Explanation
The policy cannot be loaded from this location.
System action
The current task ends.
Operator response
Verify the policy XML file name and its path.
Chapter 3. Messages 213
SAMP0007E Original Parser Exception:exceptionMessage
Explanation
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 todeactivate the current policy.
Explanation
Policy deactivation resulted in errors.
System action
The deactivation task ends.
Operator response
Analyze the error messages and try to resolve theproblem.
SAMP0009E Received errors when trying tocheck the policy.
Explanation
Policy check task resulted in errors.
System action
The check task ends.
Operator response
Analyze the error messages and try to resolve theproblem.
SAMP0010E Received errors when trying tosave the current policy.
Explanation
Policy save task resulted in errors.
System action
The save task ends.
Operator response
Analyze the error messages and try to resolve theproblem.
SAMP0011E The resource with nameresourceName and classclassName was found as memberof 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 mostone group element in this policy.
SAMP0012E The resource with nameresourceName and classclassName was found as memberof an equivalency and of a group.
Explanation
A resource cannot be member of a group and of anequivalency.
System action
This policy is not valid and cannot be activated.
Operator response
Check that each resource is only member of either agroup or an equivalency.
SAMP0013E The specified membermemberName was found multipletimes in the same <groupForm>groupName .
Explanation
All <Members> child elements must be unique in onegroup.
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 was found as memberof itself.
214 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Explanation
A group cannot be member of itself.
System action
This policy is not valid.
Operator response
Check that no group is member of itself in this policy.
SAMP0015E The resource group with nameresourceGroupName has a nestinglevel of more than 50.
Explanation
The nesting level of a resource group is limited to 50.
System action
This policy is not valid and cannot be activated.
Operator response
Reduce the nesting level of this group and resubmitthe command.
SAMP0016E An 'Exception' was caught inmethod methodName of classclassName. The received messagewas message.
Explanation
The processing was interrupted by this exception andcannot complete.
System action
The task is ended.
Operator response
Try to resolve the problem described in the exceptionmessage and resubmit the command.
SAMP0017E The relationship with the sourcewith name sourceName and typetype has a target with the samekey.
Explanation
A relationship cannot have the same source andtarget.
System action
This policy is not valid and cannot be activated.
Operator response
Correct the relationship and resubmit the command.
SAMP0018E The relationship source with namesourceName and class sourceClassis not a resource group normember of a resource group.
Explanation
A relationship source must either be a resource groupor member of a resource group.
System action
This policy is not valid and cannot be activated.
Operator response
Correct the relationship and resubmit the command.
SAMP0019E An error occurred in methodmethodName of class className.Error details details.
Explanation
The processing was interrupted by this error andcannot complete.
System action
The task is ended.
Operator response
Try to resolve the problem described in the errordetails and resubmit the command.
SAMP0020E The specified <Relationship> withthe <Type> relationType , the<Source> with the name sourceand the <Target> with the nametarget 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 isspecified in this policy.
SAMP0021E An 'UTFDataFormatException' wascaught in method methodName of
Chapter 3. Messages 215
class className. The receivedmessage was message.
Explanation
The processing was interrupted by this exception andcannot complete.
System action
The task cannot be performed.
Operator response
Ensure the correct data format of the policy documentby only using editors which create UTF-8 conformdocuments.
SAMP0022E A <Element> can only containeither a <subElement1> or a<subElement2>.
Explanation
It is not allowed to specify both kinds of sub-elementsfor this element.
System action
This policy cannot be activated.
Operator response
Check that at only one of the conflicting sub-elementsis specified in this policy.
SAMP0023E A <Element> that contains a<subElement1> must also containa <subElement2>.
Explanation
It is not allowed to specify only one of these sub-elements for this element.
System action
This policy cannot be activated.
Operator response
Check that both sub-elements are specified in thispolicy.
SAMP0024E A <Element> that contains a<subElement1> must also containa <subElement2> or a<subElement3>.
Explanation
It is not allowed to specify only one of these sub-elements for this element.
System action
This policy cannot be activated.
Operator response
Check that both sub-elements are specified in thispolicy.
SAMP0025E The <Element> with the namereferenceName refers to a resourcethat does not exist on the cluster.
Explanation
Every resource that is referenced within the policymust exist in the cluster.
System action
This policy cannot be activated.
Operator response
Create the resource on the cluster then resubmit thecommand.
SAMP0026E The node with the namenodeName does not exist on thecluster.
Explanation
Every node that is referred to within the policy mustexist in the cluster.
System action
This policy cannot be activated.
Operator response
Correct the value of the node in the policy thenresubmit the command.
SAMP0027E The node with the namenodeName is not online in thecluster.
Explanation
Every node that is referred to within a resourceattribute must be online in the cluster.
System action
This policy cannot be activated.
216 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Operator response
Correct the value of the node in the policy or make thenode online then resubmit the command.
SAMP0028E The value domainName of theelement <elementName> does notconform to the real name of thecluster actualDomainName .
Explanation
The name of the cluster specified in the policy must beequal to the real name.
System action
This policy cannot be activated.
Operator response
Correct the value in the policy then resubmit thecommand.
SAMP0029E The specified element <element>with the name groupNamecontains a member with adifferent name memberName .
Explanation
For this kind of group all <Members> child elementsmust have the same name as the group itself.
System action
This policy is not valid.
Operator response
Check that the groups name is equal to all <Members>child elements names in this policy.
SAMP0030E The specified element <element>was found more than once.
Explanation
Only zero or one element of this type is allowed in thepolicy.
System action
This policy cannot be activated.
Operator response
Check that at most one element of this type isspecified in the policy.
SAMP0031E The specified element<childElement> was found more
than once as child element of<parentElement>.
Explanation
Only zero or one element of this type is allowed.
System action
This policy cannot be activated.
Operator response
Check that at most one element of this type isspecified in this policy.
SAMP0032E The specified element<childElement> was found morethan once as child element of<parentElement> with the nameparentName .
Explanation
Only zero or one element of this type is allowed in thisgroup.
System action
This policy cannot be activated.
Operator response
Check that at most one element of this type isspecified in this group in this policy.
SAMP0033E The value value of the element<allowedNode> does not exist as anode, nor is an equivalency withthis name defined.
Explanation
This value must either be a node or the name of anequivalency.
System action
This policy is not valid and cannot be activated.
Operator response
Correct the policy and resubmit the command.
SAMP0034E The element <element> with thename equivalencyName cannot betarget of a location relationship.
Chapter 3. Messages 217
Explanation
A location relationship cannot have a target element ofthat kind.
System action
This policy is not valid and cannot be activated.
Operator response
Correct the relationship and resubmit the command.
SAMP0035E The element <element> with thevalue elementValue can only beused with a location relationshipexcept the relationship of the typeisStartableType .
Explanation
A condition is not allowed for this kind of relationship.
System action
This policy is not valid and cannot be activated.
Operator response
Correct the relationship and resubmit the command.
SAMP0036E The element <element> with thename elementValue has gotmembers that are not from thesame resource class.
Explanation
All members of an equivalency must be from the sameresource class.
System action
This policy is not valid and cannot be activated.
Operator response
Correct the equivalency and resubmit the command.
SAMP0037E The connection to the backendfailed because the followingexception occurred: exception
Explanation
An exception occurred when trying to perform anoperation on the backend.
System action
The policy cannot be activated.
Operator response
Analyze the exception description and try to correctthe problem.
SAMP0038E The element <tie-breaker> withthe name name is set to activealthough at least one otherelement of this kind is set toactive, too.
Explanation
Only one such element is allowed to be active.
System action
The policy cannot be activated.
Operator response
Ensure there is at most one active element of this kindin the policy and resubmit the command.
SAMP0039E The specified element <element>with the value value of thesubelement <subelement1> cannotcontain a subelement<subelement2> as well.
Explanation
For this kind of element some subelements are notallowed for certain subelement values.
System action
This policy is not valid.
Operator response
Remove the invalid subelement or change the value ofthe other subelement and resubmit the command.
SAMP0040E An IOException was caught whentrying to write the policy to the filefilename . The exception messagewas: 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 enoughdisk space available then resubmit the command.
218 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
SAMP0041E Exception occurred when trying tovalidate the selection stringselectString . Either the selectionstring is not valid or theconnection to the backend failed.Exception message was:exception.
Explanation
An exception occurred when trying to validate theselection string.
System action
The policy cannot be activated.
Operator response
Ensure the selection string is valid. Analyze theexception description and try to correct the problem.
SAMP0042E The <Element> with the namereferenceName has an invalidvalue for the subelement <Sub-Element>.
Explanation
<ResourceReference> elements may not have one ofthe following values for their <Class> subelement:IBM.Application, IBM.ServiceIP, IBM.Test .
System action
This policy cannot be activated.
Operator response
Correct the subelement value then resubmit thecommand.
SAMP0043E The <Element> with the type valueis not allowed on a value system.
Explanation
The processing was interrupted by this error andcannot complete.
System action
This policy cannot be activated.
Operator response
Correct the value then resubmit the command.
SAMP0044E A <Element> must either contain a<Subelement> or a <Subelement>.
Explanation
The processing was interrupted by this error andcannot complete.
System action
This policy cannot be activated.
Operator response
Correct the element then resubmit the command.
SAMP0045E An IOException was caught whentrying to read from the includedpolicy file filename . The exceptionmessage was: exception-message.
Explanation
The file could not be read.
System action
The active task ends.
Operator response
Ensure the file does exist and the userid used for thecommand has sufficient access rights then resubmitthe command.
SAMP0046E The syntax of the input policy filefilename is invalid. The line inerror is: invalid line.
Explanation
The input policy file contains an invalid line.
System action
The active task ends.
Operator response
Correct the invalid line in the input file then resubmitthe command.
SAMP0047E Variable referenced within lineinvalid line not found in top-levelXML file. Variable is referencedwithin file: inputfilename .
Explanation
The input policy contains a variable that is not definedin the top-level XML file.
System action
The active task ends.
Chapter 3. Messages 219
Operator response
Add the variable to the top-level XML file thenresubmit the command.
SAMP0048E The policy created from the top-level file policyLocation is notvalid. The resulting policy can befound in the temporary file temp-filename.
Explanation
The resulting policy is not valid. You cannot performany task with this policy.
System action
The current task ends.
Operator response
Try to make the policy valid by analyzing the errormessages following this message. Then resubmit thecommand.
SAMP0049E An error occurred in class:className method: methodName.The resource resourceName couldnot be defined. There was noexception, but the define call didnot return any object either.
Explanation
The current process was interrupted by this exceptionand cannot complete.
System action
The policy activation process stops and will return withthis error message.
Operator response
Check if this resource was described properly in theXML policy document and restart the activation.
SAMP0050E An error occurred in class:className method: methodName.The resource resourceName couldnot be defined. The receivedexception was exception
Explanation
The process was interrupted by this exception andcannot complete.
System action
The policy activation process stops and will notcomplete.
Operator response
Check if this resource was described properly in theXML policy document and restart the activation.
SAMP0051E An error occurred in class:className method: methodName.The resource resourceName couldnot be added to the resourcegroup groupName. The receivedexception was exception
Explanation
The process was interrupted by this exception andcannot complete.
System action
The policy activation process stops and will notcomplete.
Operator response
Try to solve the problem described in the exceptionmessage and resubmit the command.
SAMP0052E An error occurred in class:className method: methodName.The resource group groupNamecould not be set to the desiredstate state. The received exceptionwas exception
Explanation
The process was interrupted by this exception andcannot complete.
System action
The policy activation process stops and will notcomplete.
Operator response
Try to solve the problem described in the exceptionmessage and resubmit the command.
SAMP0053E An error occurred in class:className method: methodName.The resource resourceName couldnot be undefined. The receivedexception was exception
220 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Explanation
The reason could be that the resource is not Offline orFailedOffline or the resource might have been deletedbefore by internal commands.
System action
The policy activation or deactivation will continue.
Operator response
Check if the resource still exists. Analyze the exceptionand try to resubmit the command.
SAMP0054E An error occurred in class:className method: methodName.The resource resourceName couldnot be identified and located. Thiscan be caused by an exception orthe resource could not be found.Therefore the resourceresourceName cannot be added tothe resource group groupName.The received exception wasexception
Explanation
The process was interrupted by this exception andcannot complete.
System action
The policy activation process stops and will notcomplete.
Operator response
Try to solve the problem described in the exceptionmessage and resubmit the command.
SAMP0055E An error occurred in class:className method: methodName.The resource group groupNamecould not be identified andlocated. This can be caused by anexception or the resource couldnot be found. Therefore theresource group groupName cannotbe set to the state state. Thereceived exception was exception
Explanation
The process was interrupted by this exception andcannot complete.
System action
The policy activation process stops and will notcomplete.
Operator response
Try to solve the problem described in the exceptionmessage and resubmit the command.
SAMP0056E An error occurred in class:className method: methodName.The resource resourceName couldnot be identified and located. Thiscan be caused by an exception orthe resource could not be found.Therefore the resourceresourceName cannot be created,because it requires resourceresourceName. The receivedexception was exception
Explanation
The process was interrupted by this exception andcannot complete.
System action
The policy activation process stops and will notcomplete.
Operator response
Try to solve the problem described in the exceptionmessage and resubmit the command.
SAMP0057E An error occurred in class:className method: methodName.The resource resourceName couldnot be identified and located. Thiscan 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 byinternal commands.
System action
The current process will continue.
Operator response
Check if the resource still exists. Analyze the exceptionand try to resubmit the command.
Chapter 3. Messages 221
SAMP0058E An error occurred in class:className method: methodName.The resource resourceName couldnot be identified and located. Thiscan be caused by an exception orthe resource could not be found.Therefore the resourceresourceName cannot be modified.The received exception wasexception
Explanation
The process was interrupted by this exception andcannot complete.
System action
The current process will continue.
Operator response
Check if the resource still exists. Analyze the exceptionand try to resubmit the command.
SAMP0059E An error occurred in class:className method: methodName.The resource resourceName couldnot be modified. There was noexception, but the define call didnot return any object either.
Explanation
The current process was interrupted by this exceptionand cannot complete.
System action
The policy activation process stops and will return withthis error message.
Operator response
Check if this resource was described properly in theXML policy.
SAMP0060E An error occurred in class:className method: methodName.The resource resourceName couldnot be modified. The receivedexception was exception
Explanation
The current process was interrupted by this exceptionand cannot complete.
System action
The policy activation process stops and will return withthis error message.
Operator response
Check if this resource was described properly in theXML policy and restart the activation.
SAMP0061E An error occurred in class:className method: methodName.The IBM.TieBreaker resourceresourceName could not beidentified and located. Thereceived exception was exception
Explanation
The current process was interrupted by this exceptionand cannot complete.
System action
The policy activation process stops and will return withthis error message.
Operator response
Check if this resource was described properly in theXML policy and restart the activation.
SAMP0062E An error occurred in class:className method: methodName.The active IBM.TieBreakerresource could not be identifiedand located. Therefore theIBM.TieBreaker resourceresourceName could not bemodified or created. The receivedexception was exception
Explanation
The current process was interrupted by this exceptionand cannot complete.
System action
The policy activation process stops and will return withthis error message.
Operator response
Check if this resource was described properly in theXML policy and restart the activation.
SAMP0063E An error occurred in class:className method: methodName.The IBM.TieBreaker resourceresourceName could not be set to
222 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
active. The received exceptionwas exception
Explanation
The current process was interrupted by this exceptionand cannot complete.
System action
The policy activation process stops and will return withthis error message.
Operator response
Check if this resource was described properly in theXML policy and restart the activation.
SAMP0064E An error occurred in class:className method: methodName.The subscription from consumerconsumer to resourceresourceName has failed. Thereceived exception was exception
Explanation
The current process was interrupted by this exceptionand cannot complete.
System action
The policy activation process stops and will return withthis error message.
Operator response
Check if this resource was described properly in theXML policy and restart the activation.
SAMP0065E The attempt to update the currentautomation policy failed becauseerrors 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 toresolve the problem.
SAMP0066E The <element> with the nameelementName contains a memberthat has an invalid valueclassName for its attribute class.
Explanation
For this kind of element the value of the class attributemust be equal for all its members.
System action
This policy cannot be activated.
Operator response
Check that all members have the correct value for theclass attribute.
SAMP0067E An error occurred in class:className method: methodName.The resource resourceName couldnot be removed from the resourcegroup groupName. The receivedexception was exception
Explanation
The process was interrupted by this exception andcannot complete.
System action
The policy activation process stops and will notcomplete.
Operator response
Try to solve the problem described in the exceptionmessage and resubmit the command.
SAMP0068E The specified resource group withthe name name contains amember that is a <subelement>.This is only allowed for resourcegroups that have a value of valuefor the subelement<subelement1>.
Explanation
Resource groups that are collocated cannot haveconcurrent members.
System action
This policy is not valid.
Operator response
Remove the invalid member or change the value of thesubelement and resubmit the command.
SAMP0070E An error occurred in class:className method: methodName.
Chapter 3. Messages 223
Explanation
The current process was interrupted by this exceptionand cannot complete.
System action
The policy deactivation process stops and will returnwith this error message.
Operator response
Try to submit the command again.
SAMP0071E An error occurred in class:className method: methodName.
Explanation
The current process was interrupted by this exceptionand cannot complete.
System action
The policy save process stops and will return with thiserror message.
Operator response
Try to submit the command again.
SAMP0072E Failed to set information about theactivated policy file name:fileName, the error message is:error-message.
Explanation
The actual activation of the policy was successful, butsaving its name and time failed.
System action
The name of the file of the activated policy and theactivation time was not saved.
Operator response
Try to submit the command again.
SAMP0073E Failed to set information aboutdeactivating a policy. The errormessage 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 notsaved.
Operator response
Try to submit the command again.
SAMP0074E The <Element> element with thename elementName must contain a<Subelement> subelement,because it describes an IPv6address.
Explanation
The required subelement is missing. The processingwas interrupted by this error and cannot complete.
System action
This policy cannot be activated.
Operator response
Correct the element then resubmit the command.
SAMP0075E The <Element> element with thename elementName contains botha <Subelement> subelement and a<Subelement> subelement.
Explanation
It is not allowed to specify both subelements. Theprocessing was interrupted by this error and cannotcomplete.
System action
This policy cannot be activated.
Operator response
Correct the element then resubmit the command.
SAMP0076E The <Element> element with thename elementName contains a<Subelement> subelement that istoo large.
Explanation
The processing was interrupted by this error andcannot complete.
System action
This policy cannot be activated.
224 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Operator response
Correct the element then resubmit the command.
SAMP0077E The <Element> element with thename elementName contains a linklocal address.
Explanation
The processing was interrupted by this error andcannot complete.
System action
This policy cannot be activated.
Operator response
Correct the element then resubmit the command.
SAMP0078E The <Element> element with thename elementName contains amulticast address.
Explanation
The processing was interrupted by this error andcannot complete.
System action
This policy cannot be activated.
Operator response
Correct the element then resubmit the command.
SAMP0079E The <Element> element is notsupported with the current ActiveVersion avn.
Explanation
The processing was interrupted by this error andcannot complete.
System action
This policy cannot be activated.
Operator response
Correct the element or update the Active Version thenresubmit the command.
SAMP0080E The activation task was not able todelete all existing resources. Thereason for this is shown in theprevious messages.
Explanation
Deletion of existing resources failed. The processingwas interrupted by this error and cannot complete.
System action
The activation task ends.
Operator response
If the reason for the failure is that some resource isnot Offline respectively Failed Offline then you mayretry the command using the force option -f.
SAMP0081E The deactivation task was not ableto delete all existing resources.The reason for this is shown in theprevious messages.
Explanation
Deletion of resources failed. The processing wasinterrupted by this error and cannot complete.
System action
The deactivation task ends.
Operator response
If the reason for the failure is that some resource isnot Offline respectively Failed Offline then you mayretry the sampolicy command using the force option -f.
SAMP0082E The update task was not able todelete all existing resources. Thereason for this is shown in theprevious messages.
Explanation
Deletion of existing resources failed. The processingwas interrupted by this error and cannot complete.
System action
The update task ends.
Operator response
If the reason for the failure is that some resource isnot Offline respectively Failed Offline then you mayretry the command using the force option -f.
SAMP0083E The value value of the var elementwith name name is either not validfor the specified type type or didnot pass the extended valuecheck.
Chapter 3. Messages 225
Explanation
The value specified needs to be of the specified typeand pass the extended value check.
System action
This policy is not valid and cannot be activated.
Operator response
Correct the value and resubmit the command.
SAMP0084E The value attribute of the varelement with name name must notbe empty.
Explanation
The value attribute must not be empty.
System action
This policy is not valid and cannot be activated.
Operator response
Specify a value and resubmit the command.
SAMP0085E The attribute attribute value of theinclude element that points to filefile must not be empty.
Explanation
The attribute value must not be empty.
System action
This policy is not valid and cannot be activated.
Operator response
Specify a value and resubmit the command.
SAMP0086E At least on of the value attributesof the nested var elements ofvaroption element with namename is not valid for the specifiedtype.
Explanation
The value specified needs to be of the specified type.
System action
This policy is not valid and cannot be activated.
Operator response
Correct the value and resubmit the command.
SAMP0087E The element attribute value of thevar element with name name mustnot be empty.
Explanation
The attribute value must not be empty.
System action
This policy is not valid and cannot be activated.
Operator response
Specify a value and resubmit the command.
SAMP0088E The dynSelString attribute of thevar element with name name mustnot contain only one var name.
Explanation
There must be more than one var name in thedynSelString attribute.
System action
This policy is not valid and cannot be activated.
Operator response
Specify two var names separated by , and resubmit thecommand.
SAMP0089E At least one var that is referencedin the dynSelString attribute of thevar element with name name doesnot exist.
Explanation
The var elements referenced in the dynSelStringattribute must exist for the policy.
System action
This policy is not valid and cannot be activated.
Operator response
Specify two var names separated by , and resubmit thecommand.
SAMP0090E The var element referenced in themulti attribute of the includeelement that points to file namedoes not exist.
226 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Explanation
A var element that is referenced in a multi attributevalue must exist for the policy.
System action
This policy is not valid and cannot be activated.
Operator response
Remove the include element or change the value ofthe multi attribute to an existing var; then resubmit thecommand.
SAMP0091E Two include elements must notpoint to the same file: file.
Explanation
Two include elements must not point to one and thesame xml file.
System action
This policy is not valid and cannot be activated.
Operator response
Remove one include element or change the xml file itpoints to; then resubmit the command.
SAMP0092E If the enumeration attribute is setto value=choice, the attributevalidValues must also be specifiedand vice versa. The var elementwith name name does containeither only enumeration=choice orvalidValue.
Explanation
If you set the enumeration attribute to value=choice,the validValues attribute must also be specified. If youspecify the validValue attribute, you must set theenumeration attribute to value=choice.
System action
This policy is not valid and cannot be activated.
Operator response
Either specify both values or remove the specifiedenumeration=choice/validValues attribute. Resubmitthe command.
SAMP0093E At least one of the entries of thevalidValues attribute value doesnot match the specified typeattribute value and/or the
min/max attribute values of thevar element with name name.
Explanation
All entries of the validValues attribute value mustcomply with the specified type attribute value and orthe min/max attribute values.
System action
This policy is not valid and cannot be activated.
Operator response
Correct the validValues attribute value and resubmitthe command.
SAMP0094E At least one var that is referencedin the multi attribute of theinclude element that points to thexml file file does not exist.
Explanation
The var elements referenced in the multi attributemust exist for the policy.
System action
This policy is not valid and cannot be activated.
Operator response
Specify existing var names separated by , andresubmit the command.
SAMP0095E The value attribute of thevaroption element with namename must not be empty.
Explanation
The value attribute must not be empty.
System action
This policy is not valid and cannot be activated.
Operator response
Specify either yes or no and resubmit the command.
SAMP0096E There is no valid license availablefor the policy you are trying toactivate.
Explanation
The policy you are trying to activate requires aseparate license that is currently not installed.
Chapter 3. Messages 227
System action
This policy cannot be activated without the missinglicense.
Operator response
Install the license and resubmit the command.
SAMP0097E The value of the max attribute issmaller than the value of the minattribute for the var element withname name.
Explanation
The value of the max attribute must be greater than orequal to the value of the min attribute.
System action
This policy is not valid and cannot be activated.
Operator response
Correct the min and max attribute values and resubmitthe command.
SAMP0098E For a var element with attributeenumeration=array, each valuemust have the same number ofsub-values as specified in the varname. The var element with namename does not comply to this rule.
Explanation
For a var element with attribute enumeration=array,the attribute name contains multiple sub-elements,separated by ||. Like for var elements with attributeenumeration=list, multiple values can be specified,each separated by ,, However, each value must havethe same number of sub-values as the attribute name,also separated by ||. Example: The var name isvarOne||varTwo. A valid value entry would bevalueOne_1||valueTwo_1,valueOne_2||valueTwo_2
System action
This policy is not valid and cannot be activated.
Operator response
Correct the number of sub-values and resubmit thecommand.
SAMP0099E For an include element withattribute matrix specified, the firstvar name value of the matrix mustpoint to a var with attribute refset, the second var name value
must point to a var element ofenumeration type multilist. Theinclude element that points to thexml file name does not comply tothis rule.
Explanation
The matrix attribute of an include element mustcontain exactly two values, the first one pointing to avar with attribute ref set, the second value pointing toa var element of enumeration type multilist.
System action
This policy is not valid and cannot be activated.
Operator response
Correct the values of the matrix attribute and resubmitthe command.
SAMP0100E For a var element with attributeref used, the attribute valuePrefixmust be set as well. The varelement with name name does notcomply to this rule.
Explanation
For a var element that has the attribute ref set, thevaluePrefix attribute must also be set.
System action
This policy is not valid and cannot be activated.
Operator response
Add the valuePrefix attribute.
SAMP0101E For a var element withenumeration multilist, the typeattribute must not be boolean. Thevar element with name name doesnot comply to this rule.
Explanation
For a var element that has the attribute enumerationset to multilist, the type attribute must not be set toboolean.
System action
This policy is not valid and cannot be activated.
Operator response
Correct the type attribute.
228 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
SAMP0102E The var element with name namehas a different number of valuesthan the var elements with thenames name. This is not valid.
Explanation
All var elements that are referenced in a multiattribute of an include element must have the samenumber of values. All but the first var elements thatare referenced in a matrix attribute of an includeelement must have the same number of values.
System action
This policy is not valid and cannot be activated.
Operator response
Specify the same number of values for each of the varelements.
SAMP0103E Sampolicy template processingwas stopped because no policypool is configured.
Explanation
Sampolicy template processing requires a configuredpolicy pool. If no policy pool is defined, templateprocessing cannot be performed.
System action
This policy cannot be processed.
Operator response
Use the cfgsamadapter configuration utility toconfigure a policy pool.
SAMP0104E This policy template is not thelatest version. This policy cannotbe processed using the sampolicywizard. The current version of thispolicy is version, the minimumversion for this policy is version.
Explanation
A policy with an earlier version than the latestsupported needs to be migrated to the latest versionusing the wizard.
System action
This policy is not valid and cannot be activated.
Operator response
Use the sampolicy wizard migrate option to migratethe current policy to the latest version.
SAMP0105E Sampolicy template processingwas stopped because theconfiguration file for the policypool could not be read. Thefollowing exception occured:exception
Explanation
Sampolicy template processing requires a configuredpolicy pool. If the configuration file for the policy poolcannot be read, template processing cannot beperformed.
System action
This policy cannot be processed.
Operator response
Analyse the message of the exception and ensure thatthe configuration file exist and is readable.
SAMP0106E Sampolicy template processingwas stopped because the policypool directory dir either does notexist or is not writable.
Explanation
Sampolicy template processing requires a configuredpolicy pool. This directory must exist and be enabledfor read and write operations. If the policy pool doesnot exist or is not enabled for read and write, templateprocessing cannot be performed.
System action
This policy template file cannot be processed.
Operator response
Ensure that the policy pool directory exist and isenabled for read and write.
SAMP0107E This policy template is not thelatest version. This policy cannotbe processed using the sampolicywizard. The current version of thispolicy is version, the minimumversion for this policy is version.
Chapter 3. Messages 229
Explanation
A policy with an earlier version than the latestsupported needs to be manual migrated to the latestversion using the wizard.
System action
This policy is not valid and cannot be activated.
Operator response
Use the sampolicy wizard to reinsert all values fromthe current policy to the latest version.
SAMP0500W The policy contains no resourcegroup.
Explanation
The policy is valid, but without a resource group thereis no automation active.
System action
Processing continues.
Operator response
Ensure this is what you want to do. Otherwise changethe policy to contain at least one resource group andresubmit the command.
SAMP0501W An 'Exception' was caught inmethod methodName of classclassName. The received messagewas message.
Explanation
The processing was interrupted by this exception but itcan continue.
System action
Processing continues.
Operator response
Try to resolve the problem described in the exceptionmessage.
SAMP0502W The two <Relationship> elementswith <Type> StartAfter and<Type> StopAfter were found withthe same <Source> with the namesource and <Target> with thename target .
Explanation
The two <Relationship> elements with <Type>StartAfter and <Type> StopAfter should not have thesame <Source> and <Target>. With this configurationthe <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 StartAftertogether with StopAfter is the following: 1. The<Source> of the StartAfter is the <Target> of theStopAfter. 2. The <Target> of the StartAfter is the<Source> of the StopAfter.
SAMP0503W All members of the group with thename groupName should becollocated, because the group ispart of a location relationship or ofa relationship of the typedependsOnType . Set the value ofthe groups tag <memberLocation>to collocatedValue .
Explanation
For these kinds of relationships all members of asource or target group should be collocated.
System action
Application continues.
Operator response
Check that all members of this group are collocated inthis policy.
SAMP0504W The specified <Relationship> with<Type> relationType and <Source>with the name Sourcename and<Target> with the name Targetwas found in a loop.
Explanation
<Relationship> elements of the same <Type> whereone <Relationship> element <Target> is the next<Relationship> element <Source> should not form aloop.
System action
Application continues.
230 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Operator response
Check that the <Relationship> elements are notdefined as loop in this policy.
SAMP0505W A <Relationship> with the <Type>relationType was found that haslinked more than 100 resources.
Explanation
The numbers of resources linked by a relationship islimited to 100.
System action
Application continues.
Operator response
Reduce the number of resources linked by therelationship.
SAMP0506W The specified element <element>with the value value of thesubelement <subelement1> shouldnot contain a subelement<subelement2> as well. Thissubelement is ignored.
Explanation
For this kind of element some subelements are notsupported for certain subelement values.
System action
Application continues. Subelement is ignored.
Operator response
Remove the invalid subelement or change the value ofthe other subelement.
SAMP0507W The resource group with nameresourceGroupName has linkedmore than 100 resources.
Explanation
The numbers of resources linked by a resource groupis limited to 100.
System action
Application continues.
Operator response
Reduce the number of resources linked by this group.
SAMP0508W An error occurred in methodmethodName of class className.Error details details.
Explanation
The processing was interrupted by this error but it cancontinue.
System action
Processing continues.
Operator response
Try to resolve the problem described in the errordetails.
SAMP0509W A non-critical error occurred inmethod methodName of classclassName during activation of anew policy. Error details details.
Explanation
The processing was interrupted by this error but it cancontinue.
System action
Activation continues.
Operator response
Try to resolve the problem described in the errordetails. Try to activate the policy again and check if theerror still occurs.
SAMP0510W A non-critical error occurred inmethod methodName of classclassName during deactivation ofthe current policy. Error detailsdetails.
Explanation
The processing was interrupted by this error but it cancontinue.
System action
Deactivation continues.
Operator response
Try to resolve the problem described in the errordetails. Try to deactivate the policy again and check, ifthe error still occurs.
SAMP0511W A non-critical error occurred inmethod methodName of class
Chapter 3. Messages 231
className during saving of thecurrent policy. Error detailsdetails.
Explanation
The processing was interrupted by this error but it cancontinue.
System action
Saving process continues.
Operator response
Try to resolve the problem described in the errordetails. Resubmit the save command and check if theerror still occurs.
SAMP0512W The resource group member nameis specified with the invalidattribute combination of non-mandatory and value .
Explanation
For this kind of element this combination of attributevalues is invalid.
System action
Processing continues.
Operator response
Correct the invalid value and resubmit the command.
SAMP0513W Resource group groupName is stillnot offline and cannot be removed.
Explanation
The update/remove task tried to offline the resourcesthat shall be removed. But at least one resource still isonline.
System action
The processing was interrupted by this error andcannot complete.
Operator response
Try to resolve the problem described in the errordetails. Resubmit the update/remove command andcheck, if the error still occurs.
SAMP0514W The name of the resourceresourceName exceeds theallowed length.
Explanation
A resource was detected in the domain, whose nameexceeds the allowed length.
System action
Processing continues.
Operator response
It is recommended to change the resource name to avalue that does not exceed the allowed length. Thenresubmit the command.
SAMP1000I Usage: sampolicy -h sampolicy [-T][-V] [-q] [-f] [-forcecreate] -afilename sampolicy [-T] [-V] [-q] [-forcecreate] -u filename sampolicy[-T] [-V] [-q] [-f] [-forcecreate] -rfilename sampolicy [-T] [-V] [-q] [-f] -d sampolicy [-T] [-V] -s[filename] sampolicy [-T] [-V] [-u] -c filename sampolicy [-T] [-V] -ifilename sampolicy [-T] [-V] [-q] [-f] [-forcecreate] -a -ttemplatefilename sampolicy [-T] [-V] [-q] [-forcecreate] -u -ttemplatefilename sampolicy [-T] [-V] [-q] [-f] [-forcecreate] -r -ttemplatefilename sampolicy [-T] [-V] [-u] -c -t templatefilenamesampolicy [-T] [-V] -i -ttemplatefilename sampolicy [-T] [-V] -w templatefilename sampolicy[-T] [-V] -w -mtemplatefilenameNewtemplatefilenameOld
Explanation
System action
Operator response
SAMP1001I The specified policy policyLocationis valid.
Explanation
The policy is valid and can be activated.
System action
Processing continues.
232 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Operator response
No action required.
SAMP1002I The policy has the following policyinformation:
Explanation
This is the information for the policy.
System action
Processing continues.
Operator response
No action required.
SAMP1003I The policy has been activatedsuccessfully.
Explanation
The policy is now active in the domain.
System action
Processing continues.
Operator response
No action required.
SAMP1004I The activation task ends.
Explanation
The policy is not going to be activated because theuser did not confirm this action.
System action
Processing ends.
Operator response
No action required.
SAMP1005I The activation task ends.
Explanation
The automation policy could not be activated.
System action
Processing ends.
Operator response
No action required.
SAMP1006I The current policy was saved tofile filename.
Explanation
System action
Operator response
SAMP1007I The automation policy wasdeactivated successfully.
Explanation
There is now no policy active in the domain.
System action
Processing continues.
Operator response
No action required.
SAMP1008I Template processing failed. Theactive task ends.
Explanation
Template processing failed and therefore the activetask cannot complete successfully.
System action
Processing ends.
Operator response
No action required.
SAMP1009I The automation policy wasupdated successfully.
Explanation
The current automation policy was updated with thenew policy.
System action
Processing continues.
Operator response
No action required.
SAMP1010I The update task ends because youdid not confirm the action.
Chapter 3. Messages 233
Explanation
The current automation policy can only be updated ifyou confirm the update action.
System action
Processing ends.
Operator response
No action required.
SAMP1011I The attempt to update the currentautomation policy failed.
Explanation
The current automation policy could not be updated.
System action
Processing ends.
Operator response
No action required.
SAMP1100I Starting to check policypolicyLocation.
Explanation
System action
Operator response
SAMP1101I Starting to load policy.
Explanation
System action
Operator response
SAMP1102I Retrieving policy info ofpolicyLocation.
Explanation
System action
Operator response
SAMP1103I Are you sure you want to activatea new automation policy? Yes (y)or No (n) ?
Explanation
System action
Operator response
SAMP1104I Deactivation will remove allresources which can be createdvia policy activation. Deactivationwill not change any resources ofthe class IBM.TieBreaker Are yousure you want to deactivate thecurrent automation policy? Yes (y)or No (n) ?
Explanation
System action
Operator response
SAMP1105I Please enter the root password:
Explanation
System action
Operator response
SAMP1106I Now calling the backend in orderto retrieve all data needed.
Explanation
System action
Operator response
SAMP1107I Now calling the backend in orderto activate the policy.
Explanation
System action
234 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Operator response
SAMP1108I Now calling the backend in orderto deactivate the policy.
Explanation
System action
Operator response
SAMP1109I Removed resources successfully.
Explanation
System action
Operator response
SAMP1110I Created and changed resourcessuccessfully.
Explanation
System action
Operator response
SAMP1111I Are you sure you want to updatethe current automation policy? Yes(y) or No (n) ?
Explanation
System action
Operator response
SAMP1112I At least one resource that shall beremoved is not offline yet. Do youwant to continue waiting? Yes (y)or No (n) ?
Explanation
System action
Operator response
End-to-end automation adapter messagesThis section lists the messages which are generated by the plug-in of the end-to-end automation adapterand have the prefix SAMA. The adapter command may also generate messages with the prefix EEZ.
These messages are listed in the IBM Tivoli System Automation Application Manager Reference andProblem Determination Guide.
Prefix EEZAEEZA0001E Syntax error on line line number
Explanation
A syntax error has occurred in the configuration file,for example a leading = on a line.
System action
The automation adapter stops.
Operator response
Analyze the configuration file for invalid syntax.
EEZA0002E Wrong datatype in key the key.Expected the desired type, foundvalue the value that was found
Explanation
The value of the given key cannot be interpreted as thedesired type. For example, the system expected aboolean value but found the string hello.
System action
The automation adapter stops.
Operator response
Analyze the configuration file for invalid key/valuepairs.
EEZA0003E The key the key that was not foundwas not found and no defaultvalue was given
Chapter 3. Messages 235
Explanation
The system attempted to retrieve a value from theconfiguration file that did not exist and no defaultvalue was given.
System action
The automation adapter stops.
Operator response
Supply a value for the key in the configuration file.
EEZA0004E Integer out of bounds in key thekey . Expected value between thelower bound expected and theupper bound expected, found thevalue parsed
Explanation
The system expected an integer value between thegiven bounds (inclusive) for the given key, but found avalue outside these bounds.
System action
The automation adapter stops.
Operator response
Supply a value within the given bounds for the key.
EEZA0006E Cannot create an instance of theclass because class not found:class name
Explanation
The automation adapter cannot load the class.
System action
The automation adapter rejects the request.
Operator response
Check whether the class name is valid and is availablein the corresponding classpath.
EEZA0007E Cannot create an instance of theclass because method not found:class name
Explanation
The automation adapter can load the class but cannotcreate an instance.
System action
The automation adapter rejects the request.
Operator response
Check whether the class is valid.
EEZA0008E Cannot create an instance of theclass because of an unknownerror: class name
Explanation
The automation adapter cannot load the class orcreate an instance.
System action
The automation adapter rejects the request.
Operator response
Check whether the class is valid and analyze theattached original exception.
EEZA0009E Invocation of adapter plug-infailed: plug-in=plug-in name,method=method name,internalRetcode=internal returncode, taskRetcode=task returncode
Explanation
The automation adapter client API was called toexecute a task on the remote adapter. The call failed.There are three error categories: The client suffers anerror on the connection or the execution of the taskwithin the automation adapter backend failed orexecution failed in the automation adapter plug-in.
System action
Execution of the remote task failed.
Operator response
Analyze the return code description. If it is an internalerror, check IBM Electronic Support for additionalinformation - http://www.ibm.com/support/entry/portal/
EEZA0010E Request expires before theadapter passes it to the adapterplug-in. Timeout period is timeoutvalue seconds
236 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Explanation
All requests have an associated expiration date. Therequest is scheduled to an execution thread thatdetected that the expiration time had expired.
System action
The automation adapter rejects the request.
Operator response
Analyze the reason (for example, high working load).Increase the timeout period if necessary.
EEZA0011E The backend programspecification is invalid
Explanation
The backend program is not a Java program or theJava program name was not specified.
System action
The automation adapter rejects the request.
Operator response
Check the program that called the automation adapterclient API.
EEZA0012E Invalid parameter list
Explanation
The automation adapter detected a request that isassociated with an invalid parameter list.
System action
The automation adapter rejects the request.
Operator response
Check the program that called the automation adapterclient API.
EEZA0013E Authentication for user ID username was unsuccessful
Explanation
The request is associated with an user ID andpassword that have been validated unsuccessfully.
System action
The automation adapter rejects the request.
Operator response
Check whether the user ID is authorized for thesystem and check the security policy.
EEZA0014E The original exception original-class needs to be transported tothe remote caller
Explanation
An exception from an underlying component needs tobe transported to the remote caller.
System action
None.
Operator response
Analyze the original exception attached with thismessage.
EEZA0015E Method not supported: name of themissing method
Explanation
The automation adapter detected an unknown methodname. The list of all valid method names is defined inthe EEZAdapterInteraction interface.
System action
The automation adapter rejects the request.
Operator response
Check IBM Electronic Support for additionalinformation - http://www.ibm.com/support/entry/portal/
EEZA0017E Request not supported: name ofthe unsupported request
Explanation
The automation adapter plug-in does not support thespecified request.
System action
The request might be rejected depending on thebehavior of the plug-in.
Operator response
Check if the automation domain supports this type ofrequest.
EEZA0022E Adapter client is unable to connectto the adapter at host:port due to
Chapter 3. Messages 237
exception: the exception that wascaught
Explanation
The automation adapter client cannot connect to theserver at the given host and port. The originalexception 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 a directory.
System action
The automation adapter stops.
Operator response
Correct the configuration file.
EEZA0024E EIF sender and receiver must notbe equal
Explanation
The EIF configuration parameters are not allowed topoint to each other.
System action
The automation adapter stops.
Operator response
Correct the configuration file.
EEZA0025E Cannot find the plug-inconfiguration file: configuration filename
Explanation
The master configuration file contains the name of aplug-in configuration file that cannot be found.
System action
The automation adapter stops.
Operator response
Correct the configuration file.
EEZA0026E No plug-in configuration file wasspecified
Explanation
The master configuration file must contain at least oneplug-in configuration file.
System action
The automation adapter stops.
Operator response
Correct the configuration file.
EEZA0027E Cannot load configuration file:configuration file name
Explanation
The specified configuration file cannot be loaded.
System action
The automation adapter stops.
Operator response
Correct the configuration file.
EEZA0028E Plug-in configuration file does notcontain all mandatory parameters:configuration file name
Explanation
The specified configuration file does not contain allmandatory parameters. The plug-in is not used.
System action
The automation adapter does not deploy the plug-in.
Operator response
Correct the configuration file.
EEZA0029E Cannot create the first instance ofthe plug-in class: class name
Explanation
An attempt was made to create the first instance ofthe plug-in during initialization. Creation failed.
238 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
System action
The automation adapter does not deploy the plug-in.
Operator response
Correct the configuration file.
EEZA0030E Cannot set up event subscriptionlist for plug-in configuration file:plug-in configuration file name
Explanation
The specification of the EIF event classes in the plug-in configuration file is invalid.
System action
The automation adapter does not deploy the plug-in.
Operator response
Correct the configuration file.
EEZA0031E Cannot load configuration filefrom: plug-in configuration filename
Explanation
The automation adapter cannot load the specifiedconfiguration file because either no configuration fileor an invalid one was specified.
System action
The automation adapter stops.
Operator response
Check whether the name of the configuration file iscorrect.
EEZA0032E Initialization of the adapterfailedoriginal exception
Explanation
An error occurred in the initialization step of theautomation adapter.
System action
The automation adapter stops.
Operator response
Analyze the associated exception. If there is noexception text for this message, try to find additionalmessages that were sent previously.
EEZA0033E Unable to create type of factorySocketFactory
Explanation
The automation adapter server or client cannot createa socket factory for remote contact.
System action
The automation adapter client cannot create aconnection or the automation adapter server cannotreceive connections.
Operator response
Analyze the reason using previous messages.
EEZA0036E The adapter suffered anunexpected interruption: originalexception
Explanation
The automation adapter waits for a terminationcommand. An unexpected interruption occurred.
System action
The automation adapter stops.
Operator response
Analyze original exception.
EEZA0037E The adapter stops runningbecause no plug-in has beensuccessfully initialized
Explanation
At least one plug-in must have been successfullyinitialized otherwise the automation adapter stops.
System action
The automation adapter stops.
Operator response
Analyze previous messages and exceptions issued bythe failing plug-in.
EEZA0038E A (SSL) socket configuration erroroccurred: exception text
Explanation
An error occurred during the loading or processing of(SSL) socket-related configuration data. An SSL
Chapter 3. Messages 239
handshake exception will only be reported duringinitial contact.
System action
The automation adapter client cannot create aconnection or the automation adapter server cannotreceive connections.
Operator response
Analyze the exceptions text. Check the SSLconfiguration file if necessary.
EEZA0039E Not all data was read from socket:number of bytes read bytes read,number of bytes expected bytesexpected to be read
Explanation
The incoming request has a length in bytes, but not allbytes can be read.
System action
The automation adapter rejects the request.
Operator response
Check why the socket connection was broken whiletransfering data.
EEZA0040E The adapter client cannotestablish connection to theadapter: string representation ofthe connection
Explanation
Opening the connection failed. A request cannot besent to the automation adapter. The stringrepresentation of the connection contains detailsabout the connection.
System action
The automation adapter frontend failed.
Operator response
Analyze the connection information.
EEZA0041E The adapter client cannot invokean adapter request:InternalRC=internal return code,TaskRC=task return code
Explanation
A connection to the automation adapter has beensuccessfully established. The automation adapterfrontend might have sent a request to the automationadapter but the request failed. If the internal or taskreturn codes are not applicable (n/a), some otherunexpected exception occurred.
System action
The automation adapter frontend failed.
Operator response
Analyze the internal and task return codes (seeEEZA0009E for an explanation of the return codes).
EEZA0042E The adapter has thrown a remoteexception: InternalRC=internalreturn code, TaskRC=task returncode. The original message was:message text
Explanation
A connection to the automation adapter has beensuccessfully established. The automation adapterfrontend has sent a request to the automation adapterbut the plug-in has thrown an exception.
System action
None.
Operator response
Analyze the internal and task return codes (seeEEZA0009E for an explanation of the return codes).
EEZA0043E A required command lineparameter is missing
Explanation
One of the required command line parameters ismissing (such as -start, -stop or -terminate).
System action
The automation adapter frontend failed.
Operator response
Specify the required command-line parameters and tryagain.
EEZA0045E The adapter cannot establish aserver socket due to illegalarguments: exception text
240 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Explanation
The automation adapter cannot establish a receiverthread and cannot accept incoming connections.
System action
The automation adapter stops.
Operator response
Analyze the configuration file for invalid IP address.
EEZA0047E The adapter is unable to acceptconnections due to socketexception exception
Explanation
An exception occurred as the automation adapter wasabout to accept an incoming connection.
System action
The automation adapter stops.
Operator response
Analyze the exception text.
EEZA0051W Termination of the adapter faileddue to exception: error message
Explanation
The attempt to stop the receiver thread failed becausean exception occurred.
System action
None.
Operator response
Analyze the exception text.
EEZA0052E Cannot create an in-storage EIFconfiguration file: exception text
Explanation
An instance of the Java class ByteArrayInputStreamcannot be created or written.
System action
The automation adapter stops.
Operator response
This is probably an internal error. The exception textmight give the reason for the problem.
EEZA0053E Missing argument for commandline parameter the parameter
Explanation
A required argument for a command line parameter(such as -start) is missing. For example, AdapterCmd -start would be wrong, because -start requires anargument. A correct example would be: AdapterCmd -start com.ibm.ing.saplugin.INGXPluginInvocation.
System action
Processing of this command ends.
Operator response
Check the documentation for information about validcommand line arguments and their parameters.
EEZA0055E Remote Contact inactivitythreshold exceeded: elapsedseconds=elapsed secondsthreshold=threshold
Explanation
The automation adapter calculates the elapsed timesince the last synchronous request was received. Theautomation adapter stops itself if this time exceedsthe number specfied in the parameter eez-remote-contact-activity-interval-seconds. Any incoming eventis used as a trigger for the calculation.
System action
The automation adapter stops.
Operator response
You might want to increase the number of secondsspecified by parameter eez-remote-contact-activity-interval-seconds. Setting this parameter to 0 (zero)means it never expires.
EEZA0056I Initial contact was enabled andthe connection to the managementserver has been established
Explanation
The parameter eez-initial-contact was set to true andthe automation adapter attempted to connect themanagement server. The handshake to themanagement server was successful.
System action
None.
Chapter 3. Messages 241
Operator response
No action required.
EEZA0057E The connection to themanagement server cannot beestablished
Explanation
The automation adapter stops attempting to connectthe management server because the timeout intervalis over.
System action
The automation adapter stops.
Operator response
You might want to increase the number of minutesspecified by parameter eez-initial-contact-retry-interval-minutes. Specify the value 0 (zero) in order toretry forever.
EEZA0058E The plug-in has not been deployedor is not yet started: name of theJava plug-in class
Explanation
An attempt was made by the automation server toissue a request to the automation adapter against anunknown plug-in or a plug-in that has not beenstarted.
System action
The automation adapter rejects the request.
Operator response
Check the plug-in configuration file on the automationadapter site for the parameter plugin-impl-class.Compare it with the plugin class name specified in themessage. If there is a mismatch an installationproblem might be the reason for the problem. Analyzefurther adapter messages e.g. EEZA0115I.
EEZA0059E An internal error occurred
Explanation
The automation adapter detected an internal error.
System action
None.
Operator response
Check IBM Electronic Support for additionalinformation - http://www.ibm.com/support/entry/portal/
EEZA0060I The termination of the adapter isdelayed for duration of the delay inseconds seconds
Explanation
Stopping the automation adapter is delayed for a shortwhile until it has sent the appropriate domain leaveevents. You can configure the duration of this delaywith the eez-stop-delay-seconds parameter.
System action
The automation adapter attempts to send domainleave events.
Operator response
No action required.
EEZA0061E Unable to bind a socket to addresseez-remote-contact-hostname atport eez-remote-contact-port.Reason: message of the exception
Explanation
The automation adapter was unable to use thisaddress or port. Possible causes of the problem are: 1)The port is already in use by another program. 2) Theaddress could not be assigned.
System action
The automation adapter stops.
Operator response
Make sure that no program uses this port (that is, anautomation adapter that is already running). If anotherprogram needs this port, then configure theautomation adapter to use another port (with the eez-remote-contact-port parameter in the masterconfiguration file). Ensure that the address is valid.
EEZA0062I The start command of theautomation plug-in name of theJava plug-in class was successful
Explanation
The selected automation plug-in was successfullystarted.
242 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
System action
The automation adapter has started the automationplug-in.
Operator response
No action required.
EEZA0063I The stop command of theautomation plug-in name of theJava plug-in class was successful
Explanation
The selected automation plug-in was successfullystopped.
System action
The automation adapter has stopped the automationplug-in.
Operator response
No action required.
EEZA0064I The termination command for theadapter was successful
Explanation
The automation adapter was successfully stopped.
System action
The automation adapter stops.
Operator response
No action required.
EEZA0070E The host name eez-remote-contact-hostname is unknown
Explanation
The automation adapter was unable to resolve thehost name.
System action
The automation adapter stops.
Operator response
Specify a valid host name.
EEZA0071E The domain name is either null orempty
Explanation
The plug-in returned an invalid domain name since itsis either null or empty.
System action
The plug-in cannot be started.
Operator response
Specify a valid domain name in the plug-inconfiguration file.
EEZA0100I The adapter has been started
Explanation
This is the first of a sequence of three messages untilthe automation adapter is ready. The automationadapter starts initialization and will try to connect tothe management server if eez-initial-contact=true.
System action
None.
Operator response
No action required.
EEZA0101I The adapter is active
Explanation
The automation adapter becomes active after aconnection has been successfully established to themanagement server. The automation adaptercontinues initialization, finds and starts up all plug-ins.
System action
None.
Operator response
No action required.
EEZA0102I The adapter is ready
Explanation
The automation adapter startup sequence is complete.
System action
None.
Operator response
No action required.
Chapter 3. Messages 243
EEZA0103I The adapter is stopping
Explanation
An internal or an external stop command has beenreceived.
System action
The automation adapter is about to stop.
Operator response
No action required.
EEZA0104I The adapter has been stopped
Explanation
The automation adapter termination is complete. Allpossible stop delay periods are over. The processstops immediately.
System action
The automation adapter has stopped.
Operator response
No action required.
EEZA0105I The adapter has been stopped dueto a failure, rc=return code
Explanation
The automation adapter stopped because an erroroccurred. All possible stop delay periods are over. Theprocess stops immediately.
System action
The automation adapter stops.
Operator response
Search for error messages that were issued previously.On z/OS return code 28 might be caused due to the64-bit JVM. You should use the 32-bit JVM instead. Ifa stop command has been issued against the adapter,while the adapter is trying to establish an inital contactto the management server, the adapter will stop withreturn code 12 or 13 indicating that the adapter wasnot able to establish an inital contact within the timeperiod before the stop command was received. Seealso message EEZA0057E.
EEZA0111I The plug-in is starting: name of theJava plug-in class
Explanation
The automation adapter has already successfullycreated an instance of the plug-in class and will nowcall function INIT_DOMAIN.
System action
None.
Operator response
No action required.
EEZA0112I The plug-in has been started:name of the Java plug-in class
Explanation
The automation adapter plug-in has successfullyinitialized the domain (INIT_DOMAIN).
System action
None.
Operator response
No action required.
EEZA0113I The plug-in is stopping: name ofthe Java plug-in class
Explanation
The automation adapter will call plug-in functionTERM_DOMAIN.
System action
None.
Operator response
No action required.
EEZA0114I The plug-in has been stopped:name of the Java plug-in class
Explanation
The automation adapter plug-in has successfullystopped the domain (TERM_DOMAIN).
System action
None.
Operator response
No action required.
244 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
EEZA0115I The plug-in startup failed: name ofthe Java plug-in class
Explanation
This message might follow after EEZA0111I, but theattempt to start the plug-in via function INIT_DOMAINfailed. The automation adapter plug-in will not bestarted automatically.
System action
The plug-in will be disabled. A join event was not sent.
Operator response
You might want to restart the plug-in using theautomation adapter start command. Analyze furtherplug-in messages.
EEZA0116I The status of the event senderchanged: Address=Address,Port=Port, Status=Status
Explanation
This message occurs if the status of the EIFconnection changed. The reason could be that a newEIF 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.
System action
None.
Operator response
No action required.
EEZA9991E The message file is not installed
Explanation
The English message file must be available.
System action
The automation adapter stops.
Operator response
Make sure that the message file is in the class path.
EEZA9992E EEZAdapterLogger is not available
Explanation
The automation adapter logging component has notbeen initialized.
System action
The automation adapter stops. Other processes usingthe automation adapter client API will be unable towrite messages into log and trace files.
Operator response
Check IBM Electronic Support for additionalinformation - http://www.ibm.com/support/entry/portal/
High availability policies messagesThis section lists the messages which are generated by the SAP, NFS and Oracle high availability policiesand have the prefix SAMS.
Prefix SAMS
SAMS0001E No online domain found.
Explanation
Only online domains will be harvested.
Operator response
Start the domain you want to activate the policy forand run harvesting again.
SAMS0002E No nodes found.
Explanation
No nodes found using the command lsrpnode.
Operator response
Ensure that you run the harvesting command in adomain with at least one node.
SAMS0003E Found more than one SAPSID:SAPSID
Explanation
Harvesting found more than one SAPSID. Automaticharvesting is not possible.
Chapter 3. Messages 245
Operator response
Specify one of the available SAPSIDs manually usingthe edit value function of the wizard
SAMS0004E No SAPSID found.
Explanation
No SAPSID found on the system.
Operator response
Ensure that SAP is installed in the directory /usr/sap.
SAMS0005E Invalid number of parametersspecified. Parameter parameter ismissing.
Explanation
Harvesting cannot be executed successfully ifparameters are missing.
Operator response
Ensure that you have specified all previous parametersin the policy template and rerun the harvesting.
SAMS0006E The SAP version SAP version is notsupported.
Explanation
This SAP version cannot be harvested.
Operator response
Ensure that a supported SAP version is installed.
SAMS0007E No valid SAP version found.
Explanation
No valid SAP version information found using the disp+work command as SAPADMIN.
Operator response
Ensure that SAP is installed properly.
SAMS0008E No instance directory found forinstance type on node node name.
Explanation
No SAP instance directory found.
Operator response
Ensure that SAP is installed properly.
SAMS0009E More than one instance directoryfound for instance type.
Explanation
More than one instance directory found. This is an SAPconfiguration error.
Operator response
Ensure that SAP is installed properly.
SAMS0010E No resources of ResourceType=1and class IBM.AgFileSystem found
Explanation
No resources of ResourceType=1 and classIBM.AgFileSystem found.
Operator response
Ensure that you have configured a shared disk that isrepresented as IBM.AgFileSystem.
SAMS0011E No network interfaces found
Explanation
No network interfaces found. Searched for all externalnetwork interfaces except loopback interfaces.
Operator response
Ensure that you have configured at least one externalnetwork interface.
SAMS0012E More than one hostname found forthe SAP instance instance name.Select one of these hostnames:hostnames
Explanation
More than one hostname found. Select one of thehostnames found.
Operator response
For your policy, select one of the hostnames found.
SAMS0013E No hostname found for the SAPinstance instance name.
Explanation
No virtual hostname found.
Operator response
Ensure that the SAP instance has a profilefile /usr/sap/<SAPSID>/SYS/profile.
246 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
SAMS0014E More than one instance directoryfound for instance name. Selectone of the instance numbers of thedirectories found: instancedirectories
Explanation
More than one instance directory found.
Operator response
Select one of the instance numbers of the listedinstance directories.
SAMS0015E More than one Application Serverinstance directory found for nodenode name, the instancedirectories are: instancedirectories. This cannot beharvested. Enter all requiredinstance directories manually
Explanation
More than one instance directory found on a node.
Operator response
Enter all required instance directories manually.
SAMS0016E For at least one of the specifiedIBM.AgFileSystem names, neitherthe SysMountPoint nor theMountPoint attribute is definedand therefore cannot beharvested.
Explanation
In order to harvest a mountpoint for a givenIBM.AgFileSystem name, either the attributeSysMountPoint or MountPoint needs to be defined.
Operator response
Define the SysMountPoint or the MountPoint attributeaccording to the documentation.
SAMS0017I The following network interfacesare available on your local system:
Explanation
The network interfaces which are currently availableon your local system are displayed in the linesfollowing this message.
Operator response
Proceed as requested by the policy setup wizard.
SAMS0018I The following node type nodeshave been defined in the displayedorder:
Explanation
Displays the nodes which are currently defined. Thenodes which are currently defined are displayed in thelines following this message.
Operator response
Proceed as requested by the policy setup wizard.
SAMS1001I Start successfully finished forprocess name process.
Explanation
Displays successful start execution for the specifiedprocess.
Operator response
No action required.
SAMS1002E Start failed for process nameprocess.
Explanation
Displays failed start for the specified process.
Operator response
Analyse error log for process and retry start.
SAMS1003I Stop successfully finished forprocess name process.
Explanation
Displays successful stop execution for the specifiedprocess.
Operator response
No action required.
SAMS1004E Stop failed for process nameprocess with flagSA_RESET=SA_RESET flag.
Explanation
Displays failed stop for the specified process.
Operator response
Analyse error log for process.
SAMS1005E Incorrect action Action specified.
Chapter 3. Messages 247
Explanation
The parameter Action is incorrect.
Operator response
Use correct parameter action (start, stop or status).
SAMS1006E Script name is running on anunsupported operating system:Operating system
Explanation
Script is not supported on this operating system.
Operator response
Do not use this script on this operating system.
SAMS1007I Start instance successfullyfinished for instance profile nameinstance profile.
Explanation
Displays successful start execution for the specifiedinstance.
Operator response
No action required.
SAMS1008E Start instance failed for instanceprofile name instance profile.
Explanation
Displays failed start for the specified instance.
Operator response
Analyse error log for this instance and retry start.
SAMS1009I Stop instance successfullyfinished for instance profile nameinstance profile.
Explanation
Displays successful stop execution for the specifiedinstance.
Operator response
No action required.
SAMS1010E Stop instance failed for instanceprofile name instance profile withflag SA_RESET=SA_RESET flag.
Explanation
Displays failed stop for the specified instance.
Operator response
Analyse error log for this instance.
SAMS1011I SAP command "SAP commandname" starts now for instanceprofile name instance profile.
Explanation
The specified command will be started now.
Operator response
No action required.
SAMS1012I SAP command "SAP commandname" successfully finished forinstance profile name instanceprofile. Command output: SAPcommand output
Explanation
The specified command successfully ends.
Operator response
No action required.
SAMS1013E SAP command "SAP commandname" failed with rc return_codefor instance profile name instanceprofile. Command output: SAPcommand output
Explanation
The specified command failed.
Operator response
Analyse error log for this instance.
SAMS1014E Command "command name" failedwith rc return_code. Commandoutput: command output
Explanation
The specified command failed.
Operator response
Analyse error log for this instance.
SAMS1015E HDB system replication mode didnot switch to primary after
248 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
takeover command completed.Current system replication mode:system replication mode
Explanation
The takeover did not finish successful.
Operator response
Analyse error log for this instance.
SAMS1201I NFS server start - in start section
Explanation
NFS server start in progress
Operator response
No action required.
SAMS1202I NFS server start - IP address: TCPIP not found in DNS, trying /etc/hosts.
Explanation
The TCP IP adress was not found in DNS, trying /etc/hosts.
Operator response
No action required.
SAMS1203I NFS server start - IP address: TCPIP not found in /etc/hosts, usingthe IP address for rpc.statd.
Explanation
The TCP IP adress was not found in /etc/hosts, usingthe IP address for rpc.statd.
Operator response
No action required.
SAMS1204I NFS server start, attempting tostart daemons - start attemptnumber: The number of the NFSserver start attempt.
Explanation
Attempting to start daemons on NFS server start
Operator response
No action required.
SAMS1205I NFS server started
Explanation
NFS server started
Operator response
No action required.
SAMS1207I NFS server stop, attempting tostop daemons
Explanation
Attempting to stop daemons on NFS server stop
Operator response
No action required.
SAMS1208I NFS server stopped
Explanation
NFS server stopped
Operator response
No action required.
SAMS1209I NFS server is Offline
Explanation
NFS server is Offline
Operator response
No action required.
SAMS1210I NFS server is Online
Explanation
NFS server is Online
Operator response
No action required.
SAMS1211I NFS Server start order issued
Explanation
NFS Server start order issued
Operator response
No action required.
SAMS1212I NFS Server started
Explanation
NFS Server started
Chapter 3. Messages 249
Operator response
No action required.
SAMS1213I NFS Server stop order issued
Explanation
NFS Server stop order issued
Operator response
No action required.
SAMS1214I NFS Server stopped
Explanation
NFS Server stopped
Operator response
No action required.
SAMS1215I NFS server start - return code: Thereturn code of the NFS server startscript.
Explanation
The NFS start script will return 1 for error or 0 for asuccessful start attempt
Operator response
No action required.
SAMS1216I NFS server stop - return code: Thereturn code of the NFS server stopscript.
Explanation
The NFS stop script will return 1 for error or 0 for asuccessful stop attempt
Operator response
No action required.
SAMS1251E File /etc/exports does not exist oris not readable; cannot determineif filesystem Mount point which isexportonline needs to beexported...
Explanation
File /etc/exports does not exist or is not readable;cannot determine if the filesystem needs to beexported.
Operator response
Check whether /etc/exports does exist and hassufficient file permissions.
SAMS1252E Error: Incorrect parameter ActionUsage description
Explanation
Incorrect usage of parameter 'Action'
Operator response
Use a correct parameter regarding to the usagedescription
SAMS1253E NFS server start - File /etc/init.d/nfslock not found, cannot startNFS server
Explanation
File /etc/init.d/nfslock not found, can not start NFSserver.
Operator response
Check whether /etc/exports does exist and hassufficient file permissions.
SAMS1301I Starting Database Oracle systemID.
Explanation
Starting Database.
Operator response
No action required.
SAMS1302I Database Oracle system ID alreadystarted.
Explanation
The database is already started
Operator response
No action required.
SAMS1303W Database Oracle system IDpossibly left running when systemwent down, i.e. due to a systemcrash.
Explanation
The database possibly left running when system wentdown, i.e. due to a system crash.
250 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Operator response
No action required.
SAMS1304W Database Oracle system ID NOTstarted.
Explanation
The database is not started
Operator response
No action required.
SAMS1305I Database Oracle system IDstarted.
Explanation
Database started.
Operator response
No action required.
SAMS1306I Database Oracle system ID startedafter finish of backup.
Explanation
Database started after finish of backup.
Operator response
No action required.
SAMS1307I Stopping Database Oracle systemID.
Explanation
Stopping Database.
Operator response
No action required.
SAMS1308I Database Oracle system ID shutdown.
Explanation
Database shut down.
Operator response
No action required.
SAMS1309W Database Oracle system ID couldnot be shut down.
Explanation
Database could not be not shut down by SystemAutomation.
Operator response
Ensure that the database is in the proper state which isrequired for this operation. Ensure that the databasecan be shut down by System Automation.
SAMS1310I Listener Listener name start rc:Return code
Explanation
Action START returned the return code for the listener.
Operator response
No action required.
SAMS1311I going to kill listener identified byprocess string: Command line
Explanation
Using given process string to kill listener.
Operator response
No action required.
SAMS1312I Listener Listener name kill processrc: Return code
Explanation
Action KILL returned the return code for the listener.
Operator response
No action required.
SAMS1313I Listener Listener name stop rc:Return code
Explanation
Action STOP returned the return code for the listener.
Operator response
No action required.
SAMS1351E Can not find init file for DatabaseOracle system IDDatabase Oracle system ID NOTstarted.
Explanation
Can not find init file for the database.
Chapter 3. Messages 251
Operator response
Check whether Oracle home directory has beenspecified correctly during policy setup.
SAMS1352E Error: Incorrect parameter Action
Explanation
The parameter Action is incorrect
Operator response
Use correct parameter action (start, stop or status)
SAMS1401E SA MP cluster connector -Required cluster commandcluster_command is missing.
Explanation
A command required for SA MP cluster connector isnot available.
Operator response
Make sure that SA MP is installed and configuredcorrectly.
SAMS1401I SA MP cluster connector loadedsuccessfully. SA MP version:sa_mp_version
Explanation
SA MP cluster connector initialization has beensuccessful.
Operator response
No action required.
SAMS1402E SA MP cluster connector - SA MPdomain does not exist or is offline.
Explanation
A SA MP domain does not exist or is in status Offline.
Operator response
Make sure that an online SA MP domain exists.
SAMS1402I SA MP cluster connector - Noresource found for SID: sap_sidInstance number:instance_number
Explanation
SA MP cluster connector could not find an automatedresource for the given SID and instance number.
Operator response
No action required.
SAMS1403E SA MP cluster connector - Failed toretrieve SA MP version.
Explanation
SA MP cluster connector could not determine SA MPversion.
Operator response
Make sure that an online SA MP domain exists.
SAMS1403I SA MP cluster connector invokedwith Action: connector_actionResource: resource Cluster Action:cluster_action Output: output_fileSID: sap_sid Instance number:instance_number Node:cluster_node
Explanation
SA MP cluster connector has been invoked with theparameters specified.
Operator response
No action required.
SAMS1404E SA MP cluster connector - Errorinvoking Action: action. Invalidvalue "value" for parameter"parameter"
Explanation
SA MP cluster connector could not execute specifiedaction, because of invalid parameter value.
Operator response
Make sure that the parameter value is valid.
SAMS1404I SA MP cluster connector Action:connector_function returned withrc: return_code
Explanation
SA MP cluster connector finished processing.
Operator response
No action required.
252 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Extended disaster recovery (xDR) feature messagesRetrieve details, like explanation or operator response, for messages which are generated by theextended disaster recovery (xDR) feature.
xDR messages have the prefix SAMX. Descriptions of these messages are not documented here, but youcan retrieve them by using the command xdrhelpmsg with the following syntax:
xdrhelpmsg SAMXnnnnn
Adapter messages
Prefix SAMASAMA0001E Failed to load library: lib, message
is: message.
Explanation
Loading a library failed. Either the library or aprerequisite library is not available.
System action
The automation adapter will not start.
Operator response
Try to identify which library cannot be loaded using thefollowing steps. Use 'find -name' to find the library.Use 'ldd library' to determine which library is notavailable.
SAMA0002E Domain domain went offline andthe automation adapter isstopped.
Explanation
An event indicated that the domain went offline. Theautomation adapter can only operate with a domainthat is online. Therefore, the automation adapter isstopped.
System action
The automation adapter does not accept any furtherrequests. The automation adapter is stopped.
Operator response
If the automation adapter is automated no action isrequired and it will be restarted when the domaincomes back online. If the automation adapter is notautomated, restart it using command 'samadapterstart' after the domain has become online. Use thecommand 'samadapter status' to find out if theautomation adapter is automated.
SAMA0003E Request request must not beapplied on an automated adapterresource resource.
Explanation
Automated resources that control the adapter cannotaccept such a request because it prevents correctautomation of the samadapter. For example,requesting the samadapter to become 'Offline' willcause the domain to become unreachable from theIBM System Automation Application Manager end-to-end automation server.
System action
The request was not performed.
Operator response
Use only supplied scripts 'samadapter start' and'samadapter stop' to control the samadapter from oneof the nodes in the SAMP domain.
SAMA0004E Request request failed on resourceresource with message: message.
Explanation
The request could not be performed on the resource.The reason may be found in the message.
System action
The request was not performed.
Operator response
Examine the message for the reason why the requestfailed.
SAMA0005E Unable to build command fromrequest request for resourceresource.
Chapter 3. Messages 253
Explanation
The request could not be built for the resource. Thereason may be that the command is not allowed onthis type of resource.
System action
The request was not performed.
Operator response
Check IBM Electronic Support for additionalinformation - http://www.ibm.com/support/entry/portal/
SAMA0006E Failed to reset resource resource,message is: message.
Explanation
An error occurred when trying to reset the resourcethat was marked non recoverable. The reason may befound in the message.
System action
The request to reset the resource was not performed.
Operator response
Examine the message for the reason why the resetfailed.
SAMA0007E Failed to obtain members of groupresource, message is: message.
Explanation
An error occcured when trying to obtain the membersfor resource. The reason may be found in the message.
System action
Due to the error no members contained in theresource were returned.
Operator response
Examine the message for the reason why obtainingcontained resource failed.
SAMA0008E Failed to get top level resources,message is: message.
Explanation
An error occurred when trying to obtain resources thatare not contained in other resources. The reason maybe found in the message.
System action
Due to the error no resources were returned.
Operator response
Examine the message for the reason why obtaining toplevel resource failed.
SAMA0010E Failed to exclude node node fromautomation, message is message.
Explanation
An error occurred when trying to exclude the nodefrom automation. The reason may be found in themessage.
System action
Excluding the node was not performed.
Operator response
Examine the message for the reason why excludingthe node failed.
SAMA0011E Failed to unsubscribe resourceresource, message is message.
Explanation
An error occurred when trying to remove thesubscription for the resource. The reason may befound in the message.
System action
The subscription may not have been removed.
Operator response
Examine the message for the reason why removing thesubscription failed.
SAMA0013E Failed establish a session,message is message.
Explanation
Trying to establish an RMC session with the backendfailed. Therefore, the request cannot be satisfied.
System action
No session with RMC is established.
Operator response
Examine the message to find out why the RMC sessionfailed.
254 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
SAMA0016E Failed to include node node intoautomation, message is message.
Explanation
An error occurred when trying to include the node intoautomation. The reason may be found in the message.
System action
Including the node was not performed.
Operator response
Examine the message for the reason why including thenode failed.
SAMA0018E Failed to subscribe resourceresource, message is message.
Explanation
An error occurred when requesting a subscription forthe resource. The reason may be found in themessage.
System action
The subscription has not been made.
Operator response
Examine the message for the reason why requestingthe subscription failed.
SAMA0019E Failed to obtain details for domaindomain, message is message.
Explanation
The domain was retrieved successfully, but trying toobtain associated class information failed. The reasonmay be found in the message.
System action
The information for the domain is missing.
Operator response
Examine the message for the reason why obtaining theadditional information failed.
SAMA0020E Failed to validate resource: grp.
Explanation
The resource for which a request was made does notexist.
System action
The request is not performed
Operator response
Use list commands to verify that the resource exists. Ifit does not exist, the resource had been removed. If itexists the request should be repeated.
SAMA0022E Failed to get resourcerelationships, message ismessage.
Explanation
An error occurred when trying to get relationshipsbetween resources. The reason may be found in themessage.
System action
No relationships were returned.
Operator response
Examine the message for the reason why the requestfailed.
SAMA0023E Failed to lookup resources,message is message.
Explanation
An error occurred when trying to identify resources.The reason may be found in the message.
System action
No resource were returned.
Operator response
Examine the message for the reason why the requestfailed.
SAMA0024E Failed to get resources based onfilter: filter, message is: message.
Explanation
An error occurred when trying to get resources basedon a filter. The reason may be found in the message.
System action
No filtered resource were returned.
Operator response
Examine the message for the reason why the requestfailed.
Chapter 3. Messages 255
SAMA0025E Failed to get the parent resourcefor resource, message is message.
Explanation
An error occurred when trying to get parent of theresource. The reason may be found in the message.
System action
The parent resource was not returned.
Operator response
Examine the message for the reason why the requestfailed.
SAMA0026E Failed to get the resources on nodenode, message is message.
Explanation
An error occurred when trying to get the resourcesthat can run on the node. The reason may be found inthe message.
System action
No resources on that node were returned.
Operator response
Examine the message for the reason why the requestfailed.
SAMA0027E Failed to refresh resources,message is message.
Explanation
An error occurred when trying to refresh resources.The reason may be found in the message.
System action
No resource were refreshed.
Operator response
Examine the message for the reason why the requestfailed.
SAMA0028E Failed to get nodes of the domain,message is message.
Explanation
An error occurred when trying to get the nodes in thedomain. The reason may be found in the message.
System action
No nodes were returned.
Operator response
Examine the message for the reason why the requestfailed.
SAMA0029E Failed to get nodes from anequivalency, message is message.
Explanation
An error occurred when trying to get the nodes from anequivalency. The reason may be found in the message.
System action
No nodes were returned.
Operator response
Examine the message for the reason why the requestfailed.
SAMA0033E Failed to get nodes excluded fromautomation, message is message.
Explanation
An error occurred when trying to get the nodes that areexcluded from automation. The reason may be foundin the message.
System action
No nodes were returned.
Operator response
Examine the message for the reason why the requestfailed.
SAMA0034E Failed to enable event publishingin first-level automation manager,message is message.
Explanation
The reason for failing to enable publishing may be aninoperative IBM.RecoveryRM. Details may be found inthe message.
System action
Event publishing was not enabled.
Operator response
Examine the message for the reason why enablingevent publishing failed.
256 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
SAMA0035E Adapter stops because domaindomain is going offline.
Explanation
The adapter was notified by an event that the domainis going offline. The adapter cannot continue to exist ifthe domain is offline. Therefore, the adapter isstopped.
System action
The adapter is stopped.
Operator response
If the domain went offline unexpectedly determine thereason. The domain can be restarted using command'startrpmdomain <domain-name>'. If the domain isonline and the adapter is automated it will restartautomatically. Otherwise, issue command'samadapter start' to restart the adapter.
SAMA0036E Request request is notimplemented.
Explanation
The request is currently not supported
System action
The request is not performed
Operator response
Check if a more recent version of the automationadapter is available that supports the request.
SAMA0037E No domain that is online wasdetected. Automation adapter isstopped.
Explanation
No online domain was found or an error occurredwhen trying to query the domain. The automationadapter can only operate with a domain that is online.Therefore, the automation adapter is stopped.
System action
The automation adapter does not accept any furtherrequests. The automation adapter is stopped.
Operator response
If the automation adapter is automated no action isrequired and it will be restarted when the domaincomes back online. If the automation adapter is notautomated, restart it using command 'samadapter
start' after the domain has become online. Use thecommand 'samadapter status' to find out if theautomation adapter is automated.
SAMA0038E Request request on resourceresource returned with code:return-code, and error message:error.
Explanation
The request returned with a non-zero return codewhich indicates that it has not been successfullyperformed. The reason may be found in the message.
System action
The request was not performed.
Operator response
Examine the message for the reason why the requestfailed.
SAMA0039E Request request on resourceresource returned without result.
Explanation
The request did not respond with return code andmessage.
System action
Most likely the request was not performed.
Operator response
If the error persists examine the log for othermessages around that time.
SAMA0040E Log in for user ID user failed for anunknown reason, message is:message
Explanation
The user ID and password validation could not beperformed because PAM returned with an error.
System action
NO requests will be accepted for this user ID.
Operator response
Examine the message. Try to log in again. Make sure tospecify the user ID and password in the correct casebecause the entries are case-sensitive.
Chapter 3. Messages 257
SAMA0041E Log in for user ID user failed,message is: message
Explanation
The user ID and password failed validation on thenode where the log in was performed.
System action
NO requests will be accepted for this user ID.
Operator response
Examine the message. Try to log in again. Make sure tospecify the user ID and password in the correct casebecause the entries are case-sensitive.
SAMA0042E Log in for user ID user failed,because the user account expired,message is: message
Explanation
The user account is expired.
System action
The request was not performed.
Operator response
Have the system administrator change the expirationdate of the user account.
SAMA0043E Log in for user ID user failed,because the password expired,message is: message
Explanation
The password is expired. Have the systemadministrator change the expiration date.
System action
The request was not performed.
Operator response
Have the password changed.
SAMA0044E Programming error detected,message is error-message.
Explanation
The automation adapter detected an error that cannotbe handled.
System action
A request may not have been processed.
Operator response
Check IBM Electronic Support for additionalinformation - http://www.ibm.com/support/entry/portal/
SAMA0045E Failed to get nodes for resourcegroup resource, message ismessage.
Explanation
An error occurred when trying to get nodes on whichthe resource group can run. The reason may be foundin the message.
System action
The nodes were not returned.
Operator response
Examine the message for the reason why the requestfailed.
SAMA0046E Resource group resource is alreadyonline on node node.
Explanation
Trying to start a resource group failed, because it isalready online on that node. The state of the resourcegroup was offline at the time when Request online wasselected, but had changed to online when the requestwas tried to process.
System action
The online request is not performed, because theresource group is already online.
Operator response
Since the goal was to have the resource group onlineon the node, no further action is required.
SAMA0047E Resource group resource is alreadyonline on node online-node andtherefore cannot be started onnode requested-node.
Explanation
Trying to start a resource group on a specific nodefailed, because it is already online on another node.
258 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
System action
The online request is not performed.
Operator response
Check on which node the resource group is online. Ifthe resource group must be online on another node,first bring offline on the node where it is online. Thenrepeat the online request on the other node.
SAMA0048E Adapter stops because domaindomain is going offline.
Explanation
The adapter was notified by an event that the domainrepresented by the cluster services had been stopped.The adapter cannot continue to exist on a node wherethe cluster services have been stopped. Therefore, theadapter is stopped.
System action
The adapter is stopped.
Operator response
If the cluster services stopped unexpectedlydetermine the reason. The cluster services can berestarted using smitty hacmp. If the cluster servicesare startedthe adapter is automated it will restartautomatically. Otherwise, issue command 'hacadapterstart' to restart the adapter.
SAMA0049E No domain that is online wasdetected. Automation adapter isstopped.
Explanation
The domain represented by the cluster services wasnot found online or an error occurred trying to trying toquery the domain. The automation adapter can onlyoperate with a domain that is online. Therefore, theautomation adapter is stopped.
System action
The automation adapter does not accept any furtherrequests. The automation adapter is stopped.
Operator response
If the automation adapter is automated by HACMP noaction is required and it will be restarted when thedomain comes back online. If the automation adapteris not automated, restart it using command'hacadapter start. Use command 'hacadapter status' tofind out if the automation adapter is automated.
SAMA0050E Request request is not allowed,because domain cluster hasSubState: substate. SubState:STABLE is required.
Explanation
The request can only be performed if the domain(cluster) is in SubState: STABLE.
System action
The automation adapter does not accept the request.
Operator response
Wait until the domain has reached SubState: STABLE.To check the SubState in the IBM System AutomationApplication Manager end-to-end automation serverselect the domain and inspect the Cluster-SubState intab Additional Info. Select Refresh all beforeinspecting the Cluster-SubState again. If the SubStatedoes not change to STABLE within reasonable timeuse smitty hacmp > Problem determination to resolvethe condition.
SAMA0051E Request request on resourceresource has already beensubmitted and is currently beingperformed.
Explanation
The request is pending in its execution and thereforewill not be submitted again.
System action
The request was not performed.
Operator response
Wait for the pending command to complete. Statechanges in the resource may indicated that it hascompleted. If the log requires attention, view the logto see if the request failed.
SAMA0052E Deactivating the currentautomation policy failed with errormessage: error.
Explanation
The request to deactivate the currently activeautomation policy returned with an error.
System action
The policy was not deactivated correctly.
Chapter 3. Messages 259
Operator response
Examine the message for the reason why the policycould not be deactivated. Use View log on the domainto find additional error messages.
SAMA0053E Activating automation policy fromfile file failed with error message:error.
Explanation
The request to activate the automation policy returnedwith an error.
System action
The policy was not activated.
Operator response
Examine the message for the reason why the policycould not be activated. Use View log on the domain tofind additional error messages.
SAMA0054E Automation policy request requestcannot be performed becausepolicy request current-req is inprogress.
Explanation
The automation policy request cannot be performedbecause another request is still in progress.
System action
The policy request has been rejected.
Operator response
Wait for the current policy request to finish. Use Viewlog on the domain to find additional information onpolicy request results.
SAMA0055E Request request must not beapplied on an automated adapterresource resource.
Explanation
Automated resources that control the adapter cannotaccept such a request because it prevents correctautomation of the hacadapter. For example, bringingthe hacadapter 'Offline' will cause the domain tobecome unreachable from the operations console.
System action
The request was not performed.
Operator response
Use only supplied scripts 'hacadapter start' and'hacadapter stop' to control the adapter from one ofthe 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 the currentlyactive policy failed.
System action
No information about the currently active policy can beprovided.
Operator response
Evaluate the error message. Try to submit thecommand 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 that path and name exists.
SAMA0058E No automation policies areavailable in policy pool directoryfor automation domain domain.
Explanation
There are no policy files in the policy pool directory.
System action
No policies are listed.
Operator response
Verify the policy pool contains policy files before tryingto work with a policy.
SAMA0059E The policy file policyFile for thecurrently active policy cannot befound.
260 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Explanation
The active policy once was successfully activated fromthe file. But currently the file cannot be found.
System action
The currently active policy could not be checked,because the file was not found. Therefore, the policyinformation is incomplete.
Operator response
If the file had been accidently removed, use command'sampolicy -s filename' to save the policy. Otherwisemove the file to the path, or use cfgsamadapter tocorrect the policy pool path and activate the policyfrom there.
SAMA0060E Trying to replicate policy filefileName from local nodelocalNode on remote nodesremoteNodes failed. The originalerror was: errMessage .
Explanation
An error occurred when attempting to replicate apolicy file on remote nodes. See original error fordetails.
System action
See original error for details.
Operator response
See original error for details.
SAMA0061E Trying to store policy file fileNameon local node localNode failed. Theoriginal error was: errMessage .
Explanation
An error occurred when attempting to store a policyfile locally. See original error for details.
System action
The attempt to store the policy file locally failed. Nopolicy file was created.
Operator response
Check if there is enough space on the local node. Seeoriginal error for details.
SAMA0062E The policy file fileName on nodelocalNode could not be found.
Explanation
The policy file does not exist in the policy pooldirectory.
System action
No policy file was read.
Operator response
Make sure that the policy file exists in the policy pooldirectory.
SAMA0063E A move request is not allowed onresource group rsourcegroupbecause it is contained in anotherresource group.
Explanation
A move requests is only allowed on a resource groupwhich is not contained in any other resource group.
System action
The move request is not performed.
Operator response
If possible, move the top-level-resource group inwhich the resource group is contained.
SAMA0064E Trying to delete policy filefileName on remote nodesremoteNodes failed. The originalerror was: errMessage .
Explanation
An error occurred when attempting to delete a policyfile on remote nodes.
System action
The current task ends.
Operator response
See original error for details.
SAMA0065E Deleting policy file fileName is notallowed, because the policy iscurrently activated.
Explanation
The file of the currently active policy cannot bedeleted.
Chapter 3. Messages 261
System action
The policy file is not deleted.
Operator response
Deactivate the current policy. Then try to delete thefile.
SAMA0066E The location of the automationpolicy pool was not specified onnode node.
Explanation
The Policy pool location was not specified in theconfiguration dialog.
System action
The operation is canceled.
Operator response
Use the configuration dialog 'cfgsamadapter' to specifya 'Policy pool location', which is the directory whereautomation policy files are stored for activation. If apolicy from that location is shown as active policy, itmay have been activated from another node in thedomain, where the policy pool exists. Make sure theconfiguration and policies are copied to all other nodesin the domain.
SAMA0500W Event of type type are notprocessed in this 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 of the automationadapter is available that supports this type of event.
SAMA0501W Closing session failed.
Explanation
An error was encountered, when the session with RMCwas closed.
System action
The session may not have been closed.
Operator response
No action required.
SAMA0502W Unable to locate resource withname: name, class: class, node:node.
Explanation
The resource identified in an event by name, class, andnode could not be found.
System action
The resource is not updated with event information.
Operator response
Check if the resource exists. Verify the status of theresource.
SAMA0503W Automation mode on domaindomain has changed from mode1to mode2.
Explanation
The automation mode can be Auto (resources areautomated) or Manual (resources are only monitored).
System action
None.
Operator response
Check if the automation mode has been modifiedintentionally.
SAMA0504W The location of the automationpolicy pool location was not foundon node node.
Explanation
When trying to show the list of available policies, thePolicy pool location was not found on the node wherethe adapter currently runs.
System action
No policies for activation are provided.
Operator response
Use the configuration dialog 'cfgsamadapter' to specifya 'Policy pool location', which is the directory whereautomation policy files are stored for activation. If apolicy from that location is shown as active policy, itmay have been activated from another node in the
262 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
domain, where the policy pool exists. Make sure thepolicies are copied to all other nodes 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 successfully activated fromthe file from a path that is not the configured policypool.
System action
The currently active policy is not added to the list ofpolicies in the policy pool.
Operator response
If the file had been activated, use command'sampolicy -a filename' move the file to the policy pooland activate the policy again from the policy path.Otherwise, use cfgsamadapter to correct the policypool path to the file path of the currently active policy.
SAMA0610I Command reset from non-recoverable error has beenperformed on resource resource onbehalf of user userid.
Explanation
A user found a resource flagged with non-recoverableerror by automation which means the resource is notautomated until a user issued the reset.
System action
The reset has been issued to the resource.
Operator response
No action is required. You can verify in the IBM SystemAutomation Application Manager end-to-endautomation server if the resource is no more in error.
SAMA0611I Command request has beenperformed on resource resourcewith return code: return-code onbehalf of user userid withcomment: comment.
Explanation
A user has issued a command that requests a changeof the resource state. This command is beingperformed by automation on the indicated resource.
System action
The command has been issued to the resource.
Operator response
No action is required. You can verify in the IBM SystemAutomation Application Manager end-to-endautomation server if the resource changed its state.
SAMA0612I Node node has been excluded fromautomation on behalf of useruserid.
Explanation
A user has requested to exclude the node fromautomation. See 'System action below'.
System action
Resources on that node are stopped by automation.Then automation tries to restart the resources onother nodes in the domain.
Operator response
No action is required. You can verify in the IBM SystemAutomation Application Manager end-to-endautomation server if the resources had been restartedon other nodes in the domain, or that their new state isacceptable.
SAMA0613I Node node has been included intoautomation on behalf of useruserid.
Explanation
A user has requested to include the node intoautomation. See 'System action below'.
System action
Once the node has been included into automation,automation may try to start resources on the node.
Operator response
No action is required. You can verify in the IBM SystemAutomation Application Manager end-to-endautomation server if resources are automated on theincluded node.
SAMA0614I A request to move resource groupresource away from nodes nodehas been performed with returncode: return-code on behalf of useruserid with comment: comment.
Chapter 3. Messages 263
Explanation
A user has issued a request to move a resource groupaway from one or more nodes. The command is beingperformed by automation.
System action
The move request has been issued to the resource.
Operator response
No action is required. You can verify in the IBM SystemAutomation Application Manager end-to-endautomation server if the resource was moved.
SAMA0615I A request to move resource groupresource to node node has beenperformed with return code:return-code on behalf of useruserid with comment: comment.
Explanation
A user has issued a request to move a resource groupto another node. The command is being performed byautomation.
System action
The move request has been issued to the resource.
Operator response
No action is required. You can verify in the IBM SystemAutomation Application Manager end-to-endautomation server if the resource was moved.
SAMA0616I Node node has been excluded fromautomation on behalf of useruserid with comment: comment.
Explanation
A user has requested to exclude the node fromautomation. See 'System action below'.
System action
Resources on that node are stopped by automation.Then automation tries to restart the resources onother nodes in the domain.
Operator response
No action is required. You can verify in the operationsconsole if the resources had been restarted on othernodes in the domain, or that their new state isacceptable.
SAMA0617I Node node has been included intoautomation on behalf of useruserid with comment: comment.
Explanation
A user has requested to include the node intoautomation. See 'System action below'.
System action
Once the node has been included into automation,automation may try to start resources on the node.
Operator response
No action is required. You can verify in the operationsconsole if resources are automated on the includednode.
264 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Using IBM Support Assistant
IBM Support Assistant is a free, standalone application that you can install on any workstation. IBMSupport Assistant saves you time searching product, support, and educational resources and helps yougather support information when you need to open a problem management record (PMR) or ElectronicTracking Record (ETR), which you can then use to track the problem.
You can then enhance the application by installing product-specific plug-in modules for the IBM productsyou use. The product-specific plug-in for Tivoli System Automation for Multiplatforms provides you withthe following resources:
• Support links• Education links• Ability to submit problem management reports• 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:
• Go to the IBM Support Assistant Web Site: http://www.ibm.com/software/support/isa/• Download the installation package for your platform. Note that you will need to sign in with an IBM user
ID and password (for example, a MySupport or developerWorks user ID). If you do not already have anIBM user ID, you may complete the free registration process to obtain one.
• Uncompress the installation package to a temporary directory.• Follow the instructions in the Installation and Troubleshooting Guide, included in the installation
package, to install the IBM Support Assistant.
To install the plug-in for Tivoli System Automation for Multiplatforms, complete these steps:
1. Start the IBM Support Assistant application. IBM Support Assistant is a Web application that isdisplayed 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 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.
© Copyright IBM Corp. 2006, 2020 265
266 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
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 in other countries.Consult your local IBM representative for information on the products and services currently available inyour area. Any reference to an IBM product, program, or service is not intended to state or imply that onlythat IBM product, program, or service may be used. Any functionally equivalent product, program, orservice that does not infringe any IBM intellectual property right may be used instead. However, it is theuser's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not give you any license to these patents. You can sendlicense 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 purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information 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 material available for it are provided byIBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or anyequivalent agreement between us.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual PropertyDepartment 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 other country where suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.
© Copyright IBM Corp. 2006, 2020 267
Any references in this information to non-IBM Web sites are provided for convenience only and do not inany manner serve as an endorsement of those Web sites. The materials at those Web sites are not part ofthe materials for this IBM product and use of those Web sites is at your own risk.
If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Trademarks• IBM, the IBM logo, ibm.com, AIX, DB2, developerWorks, HACMP, NetView, Tivoli, Tivoli Enterprise,
Tivoli Enterprise Console, WebSphere, and z/OS are trademarks of International Business MachinesCorporation in the United States, other countries, or both. IBM Redbooks and the IBM Redbooks logoare registered trademarks of IBM.
• Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks ortrademarks of Adobe Systems Incorporated in the United States, other countries, or both.
• Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.
• Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States,other countries, or both.
• Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.• Red Hat and all Red Hat-based trademarks are trademarks or registered trademarks of Red Hat, Inc., in
the United States and other countries.• UNIX is a registered trademark of The Open Group in the United States and other countries.• Other company, product, and service names may be trademarks or service marks of others.
268 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Index
Aabout this guide xiadapter messages 253addrgmbr 32audience of this guide xiautomation manager 1AutomationPolicy 141AutomationPolicyTemplate XML element 139
Bbase data types, supported 130binder 2blanks, use of in expressions 132
Ccfgsamadapter 35chequ 37chrel 40chrg 45chrgmbr 48commands
gather information 7installSAM 51rmrgmbr 101RSCT 30samlog 124
ConcurrentGroup XML element 145ConstituentResource XML element 146ControlInformation XML element 143
Ddata types
base 130structured 130used for literal values 131
debut data 3Description XML element 158
Ee-mail address xiienvironment variable
setting 31Equivalency XML element 149error analysis 12expressions
operators for 132pattern matching supported in 136using 129
Hhigh availability policies
generated messages 245highlighting xi
IIBM.AgFileSystem
creating 22IBM.AgFileSystemAttributes XML element 152IBM.Application
resource 22IBM.Application XML element 153IBM.ServiceIP XML element 154IBM.Test 155IBM.TieBreaker XML element 156include XML element 141InfoLink XML element 159installSAM 51installSAM command 51internal resource states 2ISO 9000 xii
Llogic deck 2lsequ 53lsrel 57lsrg 61lsrgreq 66lssam 69lssamctrl 73
MMembers XML element 157messages
generated by high availability policies 245generated by sampolicy 213generated by the automation adapter 235prefix 2621 163prefix 2622 163prefix 2661 163prefix 2662 163prefix EEZA 235prefix SAMP 213prefix SAMS 245
Messages2621-001 1632621-002 1632621-003 1632621-004 1632621-005 1632621-006 1632621-007 163
Index 269
Messages (continued)2621-008 1632621-009 1632621-010 1642621-011 1642621-012 1642621-013 1642621-014 1642621-015 1642621-016 1642621-017 1642621-018 1642621-019 1642621-020 1652621-021 1652621-022 1652621-023 1652621-024 1652621-025 1652621-026 1652621-027 1652621-028 1652621-029 1652621-030 1652621-031 1662621-032 1662621-050 1662621-051 1662621-052 1662621-053 1662621-054 1662621-055 1662621-056 1662621-057 1662621-058 1672621-059 1672621-060 1672621-061 1672621-062 1672621-063 1672621-064 1672621-065 1672621-066 1672621-067 1672621-068 1672621-069 1682621-070 1682621-071 1682621-072 1682621-073 1682621-074 1682621-075 1682621-076 1682621-077 1682621-078 1682621-079 1682621-101 1692621-102 1692621-103 1692621-104 1692621-105 1692621-106 1692621-107 1692621-108 169
Messages (continued)2621-109 1692621-110 1692621-111 1692621-112 1702621-113 1702621-114 1702621-115 1702621-116 1702621-117 1702621-118 1702621-119 1702621-120 1702621-121 1702621-122 1702621-123 1712621-124 1712621-125 1712621-126 1712621-128 1712621-150 1712621-151 1712621-152 1712621-153 1712621-154 1712621-155 1712621-156 1722621-157 1722621-158 1722621-159 1722621-160 1722621-161 1722621-162 1722621-163 1722621-200 1722621-201 1722621-202 1722621-203 1732621-204 1732621-205 1732621-206 1732621-207 1732621-208 1732621-209 1732621-210 1732621-211 1732621-212 1732621-213 1732621-214 1742621-215 1742621-216 1742621-217 1742621-218 1742621-219 1742621-300 1742621-301 1742621-302 1742621-303 1742621-304 1742621-305 1742621-306 1752621-307 1752621-308 1752621-309 175
270 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Messages (continued)2621-310 1752621-311 1752621-312 1752621-313 1752621-314 1752621-315 1752621-316 1762621-317 1762621-318 1762621-319 1762621-320 1762621-321 1762621-322 1762621-323 1772621-324 1772621-325 1772621-326 1772621-327 1772621-328 1772621-400 1802621-401 1802621-402 1802621-403 1802621-404 1802621-405 1802621-406 1802621-450 1812621-451 1812621-452 1812621-453 1812621-454 1812621-455 1812621-456 1812621-457 1812621-458 1812621-459 1812621-460 1812621-461 1812621-462 1812621-463 1822621-464 1822621-500 1822621-501 1822621-502 1822621-503 1822621-504 1822621-505 1822621-506 1822621-550 1822621-551 1832621-552 1832621-553 1832621-554 1832621-750 1772621-751 1772621-753 1772621-754 1772621-755 1772621-756 1782621-758 1782621-759 1782621-760 1782621-761 178
Messages (continued)2621-770 1782621-771 1782621-772 1782621-773 1782621-775 1782621-776 1782621-778 1792621-779 1792621-780 1792621-781 1792621-784 1792621-785 1792621-786 1792621-788 1792621-789 1792621-790 1792621-791 1792621-792 1802621-793 1802621-794 1802621-795 1802621-796 1802622-001 1832622-002 1832622-003 1832622-004 1832622-005 1832622-006 1832622-007 1832622-008 1842622-009 1842622-010 1842622-011 1842622-012 1842622-013 1842622-014 1842622-015 1842622-016 1842622-017 1842622-018 1842622-019 1852622-020 1852622-021 1852622-022 1852622-023 1852622-024 1852622-025 1852622-026 1852622-027 1852622-028 1852622-029 1852622-030 1852622-031 1862622-032 1862622-033 1862622-034 1862622-035 1862622-036 1862622-037 1862622-038 1862622-039 1862622-040 1862622-041 186
Index 271
Messages (continued)2622-042 1862622-061 1872622-062 1872622-063 1872622-081 1872622-082 1872622-083 1872622-101 1872622-102 1872622-103 1872622-104 1872622-105 1872622-106 1882622-107 1882622-108 1882622-109 1882622-110 1882622-111 1882622-112 1882622-113 1882622-121 1882622-122 1882622-123 1882622-124 1892622-125 1892622-126 1892622-127 1892622-128 1892622-141 1892622-142 1892622-161 1892622-162 1892622-163 1892622-164 1892622-165 1902622-166 1902622-167 1902622-168 1902622-169 1902622-170 1902622-171 1902622-172 1902622-181 1902622-182 1902622-183 1902622-184 1902622-185 1912622-186 1912622-187 1912622-188 1912622-189 1912622-190 1912622-191 1912622-201 1912622-202 1912622-203 1912622-204 1912622-205 1912622-206 1922622-207 1922622-208 1922622-209 1922622-210 192
Messages (continued)2622-211 1922622-212 1922622-213 1922622-214 1922622-221 1922622-222 1922622-223 1922622-224 1932622-225 1932622-226 1932622-227 1932622-228 1932622-229 1932622-261 1932622-262 1932622-263 1932622-264 1932622-265 1932622-266 1932622-267 1932622-268 1942622-269 1942622-270 1942622-271 1942622-272 1942622-273 1942622-281 1942622-282 1942622-283 1942622-284 1942622-285 1942622-286 1942622-301 1952622-302 1952622-303 1952622-304 1952622-305 1952622-306 1952622-307 1952622-308 1952622-321 1952622-322 1952622-323 1952622-341 1962622-342 1962622-343 1962622-344 1962622-345 1962622-346 1962622-347 1962622-348 1962622-349 1962622-361 1962622-362 1962622-363 1962622-381 1962622-401 1962622-402 1972622-403 1972622-421 1972622-422 1972622-423 1972622-424 197
272 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Messages (continued)2622-425 1972622-426 1972622-427 1972622-428 1972622-429 1972622-441 1972622-442 1982622-443 1982622-444 1982622-445 1982622-446 1982622-461 1982622-462 1982622-463 1982622-481 1982622-482 1982622-483 1982622-484 1982622-485 1992622-486 1992622-501 1992622-502 1992622-503 1992622-519 1992622-521 1992622-522 1992622-523 1992622-524 1992622-525 1992622-526 1992622-541 2002622-561 2002622-562 2002622-572 2002622-573 2002622-574 2002622-575 2002622-576 2002622-577 2002622-578 2002622-579 2002622-580 2002622-581 2012622-582 2012622-583 2012622-584 2012622-585 2012622-591 2012622-592 2012622-593 2012622-594 2012622-595 2012622-596 2012622-597 2012622-611 2012622-612 2022622-613 2022622-614 2022622-615 2022622-616 2022622-617 2022622-618 2022622-901 202
Messages (continued)2622-902 2022622-903 2022622-904 2022622-905 2032622-906 2032622-907 2032622-908 2032622-909 2032622-910 2032622-911 2032622-912 2032622-913 2032622-914 2032622-915 2032622-916 2032622-917 2042622-918 2042661-001 2042661-002 2042661-003 2042661-004 2042661-005 2042661-006 2042661-007 2042661-008 2052661-009 2052661-010 2052661-011 2052661-012 2052661-013 2052661-014 2052661-015 2052661-016 2062661-017 2062661-018 2062661-019 2062661-020 2062661-021 2062661-022 2062661-023 2072661-024 2072661-025 2072661-026 2072661-027 2072661-028 2072661-029 2072661-030 2072661-031 2072661-032 2082661-033 2082661-034 2082661-035 2082661-036 2082661-037 2082661-038 2082661-039 2092661-040 2092661-041 2092661-042 2092661-043 2092661-044 2092661-045 2092661-046 209
Index 273
Messages (continued)2661-047 2092661-048 2092661-049 2102661-050 2102661-051 2102661-052 2102661-053 2102661-054 2102661-055 2102661-056 2102661-057 2102662-001 2102662-002 2112662-003 2112662-004 2112662-005 2112662-006 2112662-007 2112662-008 2112662-009 2112662-010 2112662-011 2112662-012 2112662-013 2112662-014 2122662-015 2122662-016 2122662-017 2122662-018 2122662-019 2122662-020 2122662-021 2122662-022 2122662-023 2122662-024 2122662-025 212EEZA0001E235EEZA0002E235EEZA0003E235EEZA0004E236EEZA0006E236EEZA0007E236EEZA0008E236EEZA0009E236EEZA0010E236EEZA0011E237EEZA0012E237EEZA0013E237EEZA0014E237
Messages (continued)EEZA0015E237EEZA0017E237EEZA0022E237EEZA0023E238EEZA0024E238EEZA0025E238EEZA0026E238EEZA0027E238EEZA0028E238EEZA0029E238EEZA0030E239EEZA0031E239EEZA0032E239EEZA0033E239EEZA0036E239EEZA0037E239EEZA0038E239EEZA0039E240EEZA0040E240EEZA0041E240EEZA0042E240EEZA0043E240EEZA0045E240EEZA0047E241EEZA0051W241EEZA0052E241EEZA0053E241EEZA0055E241EEZA0056I241EEZA0057E242EEZA0058E242
274 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Messages (continued)EEZA0059E242EEZA0060I242EEZA0061E242EEZA0062I242EEZA0063I243EEZA0064I243EEZA0070E243EEZA0071E243EEZA0100I243EEZA0101I243EEZA0102I243EEZA0103I244EEZA0104I244EEZA0105I244EEZA0111I244EEZA0112I244EEZA0113I244EEZA0114I244EEZA0115I245EEZA0116I245EEZA9991E245EEZA9992E245SAMA0001E253SAMA0002E253SAMA0003E253SAMA0004E253SAMA0005E253SAMA0006E254SAMA0007E254SAMA0008E254SAMA0010E254
Messages (continued)SAMA0011E254SAMA0013E254SAMA0016E255SAMA0018E255SAMA0019E255SAMA0020E255SAMA0022E255SAMA0023E255SAMA0024E255SAMA0025E256SAMA0026E256SAMA0027E256SAMA0028E256SAMA0029E256SAMA0033E256SAMA0034E256SAMA0035E257SAMA0036E257SAMA0037E257SAMA0038E257SAMA0039E257SAMA0040E257SAMA0041E258SAMA0042E258SAMA0043E258SAMA0044E258SAMA0045E258SAMA0046E258SAMA0047E258SAMA0048E259SAMA0049E259
Index 275
Messages (continued)SAMA0050E259SAMA0051E259SAMA0052E259SAMA0053E260SAMA0054E260SAMA0055E260SAMA0056E260SAMA0057E260SAMA0058E260SAMA0059E260SAMA0060E261SAMA0061E261SAMA0062E261SAMA0063E261SAMA0064E261SAMA0065E261SAMA0066E262SAMA0500W262SAMA0501W262SAMA0502W262SAMA0503W262SAMA0504W262SAMA0505W263SAMA0610I263SAMA0611I263SAMA0612I263SAMA0613I263SAMA0614I263SAMA0615I264SAMA0616I264SAMA0617I264
Messages (continued)SAMP0001E213SAMP0002E213SAMP0003E213SAMP0004E213SAMP0005E213SAMP0006E213SAMP0007E214SAMP0008E214SAMP0009E214SAMP0010E214SAMP0011E214SAMP0012E214SAMP0013E214SAMP0014E214SAMP0015E215SAMP0016E215SAMP0017E215SAMP0018E215SAMP0019E215SAMP0020E215SAMP0021E215SAMP0022E216SAMP0023E216SAMP0024E216SAMP0025E216SAMP0026E216SAMP0027E216SAMP0028E217SAMP0029E217SAMP0030E217SAMP0031E217
276 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Messages (continued)SAMP0032E217SAMP0033E217SAMP0034E217SAMP0035E218SAMP0036E218SAMP0037E218SAMP0038E218SAMP0039E218SAMP0040E218SAMP0041E219SAMP0042E219SAMP0043E219SAMP0044E219SAMP0045E219SAMP0046E219SAMP0047E219SAMP0048E220SAMP0049E220SAMP0050E220SAMP0051E220SAMP0052E220SAMP0053E220SAMP0054E221SAMP0055E221SAMP0056E221SAMP0057E221SAMP0058E222SAMP0059E222SAMP0060E222SAMP0061E222SAMP0062E222
Messages (continued)SAMP0063E222SAMP0064E223SAMP0065E223SAMP0066E223SAMP0067E223SAMP0068E223SAMP0070E223SAMP0071E224SAMP0072E224SAMP0073E224SAMP0074E224SAMP0075E224SAMP0076E224SAMP0077E225SAMP0078E225SAMP0079E225SAMP0080E225SAMP0081E225SAMP0082E225SAMP0083E225SAMP0084E226SAMP0085E226SAMP0086E226SAMP0087E226SAMP0088E226SAMP0089E226SAMP0090E226SAMP0091E227SAMP0092E227SAMP0093E227SAMP0094E227
Index 277
Messages (continued)SAMP0095E227SAMP0096E227SAMP0097E228SAMP0098E228SAMP0099E228SAMP0100E228SAMP0101E228SAMP0102E229SAMP0103E229SAMP0104E229SAMP0105E229SAMP0106E229SAMP0107E229SAMP0500W230SAMP0501W230SAMP0502W230SAMP0503W230SAMP0504W230SAMP0505W231SAMP0506W231SAMP0507W231SAMP0508W231SAMP0509W231SAMP0510W231SAMP0511W231SAMP0512W232SAMP0513W232SAMP0514W232SAMP1000I232SAMP1001I232SAMP1002I233
Messages (continued)SAMP1003I233SAMP1004I233SAMP1005I233SAMP1006I233SAMP1007I233SAMP1008I233SAMP1009I233SAMP1010I233SAMP1011I234SAMP1100I234SAMP1101I234SAMP1102I234SAMP1103I234SAMP1104I234SAMP1105I234SAMP1106I234SAMP1107I234SAMP1108I235SAMP1109I235SAMP1110I235SAMP1111I235SAMP1112I235SAMS0001E245SAMS0002E245SAMS0003E245SAMS0004E246SAMS0005E246SAMS0006E246SAMS0007E246SAMS0008E246SAMS0009E246
278 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
Messages (continued)SAMS0010E246SAMS0011E246SAMS0012E246SAMS0013E246SAMS0014E247SAMS0015E247SAMS0016E247SAMS0017I247SAMS0018I247SAMS1001I247SAMS1002E247SAMS1003I247SAMS1004E247SAMS1005E247SAMS1006E248SAMS1007I248SAMS1008E248SAMS1009I248SAMS1010E248SAMS1011I248SAMS1012I248SAMS1013E248SAMS1014E248SAMS1015E248SAMS1201I249SAMS1202I249SAMS1203I249SAMS1204I249SAMS1205I249SAMS1207I249SAMS1208I249
Messages (continued)SAMS1209I249SAMS1210I249SAMS1211I249SAMS1212I249SAMS1213I250SAMS1214I250SAMS1215I250SAMS1216I250SAMS1251E250SAMS1252E250SAMS1253E250SAMS1301I250SAMS1302I250SAMS1303W250SAMS1304W251SAMS1305I251SAMS1306I251SAMS1307I251SAMS1308I251SAMS1309W251SAMS1310I251SAMS1311I251SAMS1312I251SAMS1313I251SAMS1351E251SAMS1352E252SAMS1401E252SAMS1401I252SAMS1402E252SAMS1402I252SAMS1403E252
Index 279
Messages (continued)SAMS1403I252SAMS1404E252SAMS1404I252
mkequ 75mkrel 78mkrg 82modifying predefined expressions 129MoveGroup XML element 144
Ooperator precedence 135operators available for use in expressions 132Owner XML element 158
Ppattern matching supported in expressions 136pidmon 85policies, high availability
generated messages 245Policy XML reference 137PolicyInformation XML element 142precedence of operators 135predefined expressions
modifying 129prereqSAM 87prerequisite knowledge for this guide xiproblem analysis 16publications xi
RRelationship XML element 148Resource XML element 143ResourceGroup XML element 147ResourceReference XML element 151rgmbrreq 88rgreq 91rmequ 94rmrel 95rmrg 99rmrgmbr 101rmrgmbrg command 101RSCT
related information xiiRSCT command 30
Ssamadapter 104samcc 105samctrl 109samdiag 111samlicm 114samlog 115samlog command 124samnonrootuser 126sampolicy 119
samsimul 122samwhy 124select string 129setupAdapterNonRoot.sh 127SQL
restrictions 130SQL syntax 129stack dump 6structured data types 130system log 4
Ttrace data 3trademarks 268troubleshooting 1
UuninstallSAM 125using select strings in expressions 129
Vvar XML element 140variable names 132
Wwhat's new
4.1 xiii
XxDR messages 253XML
special characters 139XML elements
AutomationPolicyTemplate 139availability by product version 137ConcurrentGroup 145ConstituentResource 146ControlInformation 143Description 158Equivalency 149IBM.AgFileSystemAttributes 152IBM.ApplicationAttributes 153IBM.ServiceIP 154IBM.TieBreaker 156include 141InfoLink 159Members 157MoveGroup 144Owner 158PolicyInformation 142Relationship 148Resource 143ResourceGroup 147ResourceReference 151var 140
XML policycoding 137example 159
280 Tivoli System Automation for Multiplatforms: Tivoli System Automation for Multiplatforms V4.1: ReferenceGuide
IBM®
Part Number:Product Number: 5724-M00
SC34-2700-04
(1P) P
/N: