ISO8859-1 0N1   ?$  Y TTZUTgM [ _ {O D 7ch2S%"y:#+I#f##'$B$jJ$k%&})-F).N)u)2)))* * * * n+ ;2.2j3) ]3G<7@<E<~=)=2== > @?] 1? =?@.@4@>6@sP@W@rASA fBY lB 5C- -Cc CwC*D!D"mD9WDnDaEn!EE E E E E RGDHUHE)HxHNI>>IyIJF]JK,K-K.xK/~KL'L(L)L* L+!8L"8L#CM.$YMr%M&PM'dN$(<N)N*JN /U]^^1x^Q4^^` /a &aK ,ar a 9aa$bCb9 b})b,b|b!cr c,cc)dOd&e/e;$ek[e,e *f!fD"?f#g$yg%ha&+i&'iR(5iY)i* i+i,i-j .j/ky l-l.GlLUl lll5l Dm0 ?ru lrx"x#x$Ix%|o}} |~u F~ 9 Y <<yG) 9en\2 wp }tu  & '42\Bl r Ps P P 6f3Q#GNAF8 ?2N4(SYZC jd85>>Y})(yes)|(no)|(on)|(off)|(unknown)|(true)|(false)|(allow node management request)%1$s: 2651-002 Could not find %2$s in the node database. Run lsnode without any arguments to see the list of valid node names. %1$s: 2651-003 Could not find one or more of the following nodes in the database: %2$s. Run lsnode without any arguments to see the list of valid node names. %1$s: 2651-004 Could not find one or more of the specified nodes in the database. Run lsnode without any arguments to see the list of valid node names. %1$s: 2651-005 Nodegroup %2$s is empty (does not have any nodes in it). Run nodegrp or nodegrp -W to see the definition of the nodegroup. (unreachable)|(alive)|(unconfigured)%1$s: 2651-006 The attribute name pattern specified did not match any node attributes. Run lsnode -l to see a list of valid attribute names. Usage: lsnode [-i | -s | -p | -a attr,attr,... [-x] | -A] [-l | -F | -X file | -d delim | -D delim] [-S] [-H] [-h] [-v|-V] {-w "selectstr" | [-N nodegroups] [-f file] [[-n] node_list]} -i Display ip addresses. Not valid with -l. -s Display the short hostname. Not valid with -l. -p Display the ping status of each node. -a Display the specified comma-separated attribute(s). -A Display all attributes. -P Display node user-defined properties instead of attributes. -l Display in long format. -F Display in a format suitable for a nodedef file. -X Generates a XML nodedef file. -D, -d Delimiter that should be used to separate items. -x Do not display the node name at the beginning of each row. -w Display the nodes that match this select string "where" clause. -N Display nodes that are in this comma-separated list of node groups -f Display nodes listed in this file (use "-" for stdin). -S Sort output by the 1st attribute displayed in each row (default). -H Display attributes from the IBM.Host resource class on each node. -v, -V Verbose mode. -h Display this usage information. [-n] The list of nodes to list information about. %1$s: 2651-089 The module %2$s is required for this action and could not be found. %1$s: 2651-007 Nodegroup %2$s not found. Run nodegrp to see a list of valid nodegroups. %1$s: 2651-008 Cannot add nodes to a group that has the where clause of the select string set. Use nodegrp -w to change the definition of the dynamic nodegroup. %1$s: 2651-009 Cannot remove nodes from a group that has the where clause of the select string set. Use nodegrp -w to change the definition of the dynamic nodegroup. %1$s: 2651-010 Cannot set the where clause of a group that has a node list defined. Use nodegrp -a or nodegrp -x to change the definition of the static nodegroup. %1$s: 2651-011 Cannot display the where clause of the select string because it is not set for %2$s. It is most likely a static nodegroup. Try omitting the -W option. %1$s: 2651-012 %2$s specified nodegroup(s) not found. Run nodegrp to see a list of valid nodegroups. %1$s: 2651-013 Ignoring the -g option because it cannot be specified on a group that already exists. (If you need to change the group from validate to non-validate, delete the group and recreate it with the -g option.) %1$s: 2651-014 With this option you must specify exactly two groups separated by a space. %1$s: 2651-015 Error opening file %2$s to read group definitions. Message from system: %3$s. %1$s: 2651-016 Improper format in group file %2$s in the following line: %3$s Run nodegrp -L to see the expected format. %1$s: 2651-017 Nodegroup %2$s already exists - not overwriting it. %1$s: 2651-039 Currently, you cannot add both sub-groups and exclusions to a nodegroup. (One or the other is valid.) This is a limitation that will be relaxed in a future release. Usage: nodegrp {-p|-a node_list|-n node_list|-x node_list|-D|-l|-L|-f file |-w selectstr|-W|-s node|-h}[-d delim] [-g] [-v|-V] [group ...] nodegrp {-I | -S} group1 group2 -p Prints the membership of one or more groups. -a Adds nodes to a group, creating the group if necessary. -n Replaces the current group membership with the given nodes. -x Removes nodes from a group. -D Deletes one or more groups. -l List all defined node groups. -L List the definition of some or all groups. -f A file that contains groups to be defined. Use the -L format. -w The select string "where" clause to use for a dynamic group. -W Display the select string "where" clause of the given group. -s Search - display all the groups that contain this node. -d The delimiter that should be used to separate displayed. -g The names in the group are generic names, not necessarily nodes. -S Display the members in the 1st group that are not in the 2nd group -I Display the intersection of the 2 groups specified. -v or -V Verbose mode. -h Display usage information. group ... The group or groups to be acted on. %1$s: The node(s) %2$s are not members of group %3$s. %1$s: 2651-090 Node groups can not contain blanks. Change the group names and rerun this command. %1$s: 2651-092 Node %2$s belongs to the following node groups %3$s. Remove the node from these groups. %1$s. Environment Variable CSM_CFM_DELETE_FILES is set. Usage: createnode [-h] [-v|-V] {-f file | hostname|ipaddr ...} [attr=value ...] -v or -V Verbose mode. -h Display this usage information. -f file Specifies a file that contains a list of nodes names. If the file name is "-", then the list is read from stdin. The file can contain multiple lines and each line can have one or node names, separated by spaces or commas. hostname|ipaddr ... Creates one or more nodes in the ManagedNode table. The node names are distinguished from the attr=val pairs that follow because they do not have an equal sign in them. This argument can be combined with the -f option. attr=value ... Specifies attributes that should be set when creating the nodes. Each attr=value pair should have no spaces, or the parts containing spaces should be quoted. A null value can be specified by "attr=". %1$s: 2651-018 The following node(s) already exists in the ManagedNode table: %2$s. Specify node names that do not already exist. Run lsnode to see a list of existing nodes. %1$s: 2651-019 At least one node name must be specified. %1$s: 2651-020 Improper form specified for an attribute=value argument. %1$s: 2651-021 No nodes matched the specified select string. Run lsnode to see a list of hostnames, or lsnode -l to see the attribute values. %1$s: 2651-061 File not found: "%2$s". %1$s: 2651-099 The Mode attribute may not be changed from Managed to MinManaged for %2$s. You must remove %3$s and use definenode to redefine the node with Mode set to MinManaged. Follow the procedure in the CSM Administrative Guide for changing a Linux Node from Managed to MinManaged mode. No changes will be made to this node. %1$s: 2651-100 The Mode attribute may not be changed to MinManaged for %2$s, because the operating system is AIX. MinManaged nodes are only supported on Linux. No change will be made to this node. Usage: chnode [-h] [-v|-V] [-P] {-a | -w selectstr | [-f file ] [-N nodegroups] [[-n] node_list]} attr=value ... -w Change the nodes that match this select string "where" clause. -a Change all the nodes. -f Change nodes listed in this file (use "-" for stdin). -N Change nodes that are in this comma-separated list of node groups. -P Change node user-defined properties instead of attributes. -v | -V Verbose mode. -h Display this usage information. [-n] One or more nodes to change in the ManagedNode table. attr=value Attributes that should be changed for the node(s). Cannot find command %1$s in nodes: %2$s, skip them from target nodes. %1$s: 2651-093 The -u flag can not be specified for the diskless nodes: %2$s. %1$s. Environment Variable CSM_CFM_DELETE_FILES is set. Warning: The node %1$s will be removed from the cluster. But it still is used as an install server by the following nodes: %2$s. Please run the chnode or definenode command to correct the InstallServer attribute for those nodes. Warning: The node %1$s will be removed from the cluster. But it still is used as an install server by many nodes. Please run the chnode or definenode command to correct the InstallServer attribute for those nodes. Usage: rmnode [-h] [-v|-V] [-u] [--force] {[-f file] [-N nodegroups] [[-n] node_list]} -v | -V Verbose mode. -h Display this usage information. -f file Specifies a file that contains a list of nodes names. If the file name is "-", then the list is read from stdin. The file can contain multiple lines and each line can have one or more node names or node ranges, separated by spaces or commas. -u Perform cleanup on the nodes being removed. The cleanup will include the removal of CSM log files and, in some cases, the uninstalling of CSM packages. It will not include the uninstalling of any open source prerequisites or software packages that were automatically installed with the operating system. --force Remove the node by force even if the node is the install server of other nodes in the cluster. -N nodegroups Specifies a nodegroup or a comma-separated list of node groups on which to run the command. [-n] node_list The list of nodes to list information about. Can be a comma or space separate list of hostnames or node ranges. (See the noderange man page for information on node ranges.) This can be combined with -N and -f. If this is the last argument specified, the -n is optional. %1$s: 2660-001 The --force option is not valid on the HMC. %1$s: 2660-002 The node %2$s can not be removed because it is being used as an install server by the following nodes: %3$s. If you want to remove it by force, please use the --force option. %1$s: 2660-003 The node %2$s can not be removed because it is being used as an install server by many nodes. If you want to remove it by force, please use the --force option. Usage: mgmtsvr [-h] [-v | -V] [-k] [-n nodename] [-N] [host | -d] -d Delete the management server entry. -n nodename Hostname that the CSM management server knows this node by. Normally the user does not need to specify this option. It is used internally by installnode and makenode to ensure correct operation even when name resolution of the hostname value on the node results in a different name than the management server knows it by. This argument is only valid when a hostname or ipaddr for the management server is also specified. -N Display the value for the local nodename along with the management server. This argument is only valid when a hostname or ipaddr for the management server is not specified. -k Re-exchange the public keys with the management server also. -v | -V Verbose mode, including messages from the DBI layer. -h Display this usage information. host The hostname or IP address of the CSM management server that will be managing this node. If no host is specified (and -d is not specified) the current setting will be displayed. In this case, the exit status can be examined to distinguish between nodes and the management server as follows: 0: this is only a node and the mgmt svr value is set 11: this is only a node and the mgmt svr value is not set 21: this is a mgmt svr and a node and the mgmt svr value is set to itself 22: this is a mgmt svr and a node and the mgmt svr value is set to another mgmt svr 23: this is a mgmt svr and a node and the mgmt svr value is not set 31: this is only a mgmt svr 101: this is neither a mgmt svr or a node This node does not currently have a CSM management server managing it. %1$s (This node is also the CSM management server for itself.) %1$s (This node is also the CSM management server for other nodes.) This machine is a CSM management server and a node, but the node does not currently have a CSM management server managing it. This machine is a CSM management server. Management server: %1$s, Local node name: %2$s %1$s: 2651-023 This machine is neither a CSM management server or node. To make this machine a CSM management server, install csm.server. To make this machine a node, install csm.client. %1$s: 2651-024 The management server value cannot be set or removed. This machine is not a CSM node. A hostname or -d can only be specified on a machine that has csm.client installed. %1$s: 2651-040 The %2$s daemon did not start or is not running. %1$s: 2651-041 ManagementServer %2$s is Invalid. There are multiple management servers defined for this node: Resolving names in the specified node list... %1$s: 2651-027 Cannot resolve %2$s to a host name. %1$s: 2651-028 Cannot resolve %2$s to an IP address. %1$s: 2651-029 Exit code %2$s from command: %3$s Error message from cmd: %4$s %1$s: 2651-030 Error opening file %2$s to read node list. Message from system: %3$s. %1$s: 2651-031 Could not find nodegroup %2$s in the database. Run nodegrp -l to see a list of valid nodegroups. %1$s: 2651-032 Could not find one or more of the following nodegroups in the database: %2$s. Run nodegrp -l to see a list of valid nodegroups. %1$s: 2651-033 Internal error in NodeUtils.listNodeAttrs() - SkipResolve set, but Res2Unres not set. %1$s: 2651-052 You cannot run CSM commands on this machine, since it is an inactive CSM management server. %1$s: 2651-066 Touch of file %2$s failed with: %3$s %1$s: 2651-067 Could not fork child process. Running Command: %1$s %1$s: 2651-095 CSM license has expired or has not been accepted. Run csmconfig -L if you have installed a new release. (yes)|(no)|(unlimited)%1$s: 2651-035 Bad value given for the %2$s option. The value must be one of the following: yes, no, 1, 0. %1$s: 2651-036 The specified remote shell (%2$s) does not exist or is not executable. %1$s: 2651-037 Invalid cluster type and model specified: %2$s. It must be specified in the format ####-###. %1$s: 2651-038 Cannot access key file %2$s. Check that it exists and is readable by this user. (Mixed)|(Events)|(Polling)|(None)You have requested to enable CSM to use Kerberos Version 5 remote commands. The automatic setup of Kerberos is not supported on Management Servers running SuSE/SLES. You must setup your Kerberos server and client, create the CSM principal %1$s, and store the CSM principal keytab in %2$s. Alternately, you can run kinit and obtain your own ticket-granting-ticket before running CSM scripts. We will default the value of SetupKRB5 to 4. %1$s: 2651-042 Error while setting up KRB5. See additional messages shown above. %1$s: 2651-043 You must be root userid to run setup KRB5 commands. %1$s: 2651-062 You cannot change the HAMode attribute, it is used internally by CSM. The license agreement has been accepted. A try and buy license is already installed. Run csmconfig without arguments to see the expiration date of the license. A full license is already installed. Not installing the try and buy license. License agreement not accepted - can not install license key. %1$s: 2651-063 Bad value given for the %2$s option. The value must be one of the following: Mixed,Events,Polling,None. %1$s: 2651-064 The setup of the Kerberos server is only supported if AIX and AIX Network Authentication Services (NAS) are installed. %1$s: 2651-065 Bad value given for the %2$s attribute. The value must be between 0 and 15. %1$s: 2651-074 The value for NetworkInstallProtocol "%2$s" is not supported. The supported values are "nfs" or "http". %1$s: 2651-075 The value for SetupNetworkInstallProtocol "%2$s" is not supported. The supported values are yes, no, 1 and 0. %1$s: 2660-005 The specified TFTP package (%2$s) does not match the supported value (%3$s), Please install it and start TFTP service manually. %1$s: 2660-006 Attribute %2$s is a read-only attribute. %1$s: 2660-007 The %2$s option is not valid on the HMC. %1$s: 2660-008 Attribute %2$s is a read-only attribute on the HMC. %1$s: 2660-009 The SyncCmd attribute %2$s is not valid on %3$s. Setting SyncCmd to %4$s. %1$s. %1$s: 2660-010 CSM license has expired. You need to obtain a Full CSM license. The Hardware Control Resource Manager must be stopped and restarted for the changes to take effect. %1$s: 2660-017 Please specify a Full CSM license key file. Usage: csmconfig [-u yes|no] [-m cluster-type-model] [-p PowerStatusMode] [-s cluster-serialnum] [-r remote-shell-path] [-R yes|no] [-t tftp-package] [-K [0-15]] [-v] [-c] [-h] [attr=value [attr=value...]] csmconfig [-v] [-c] [-d] -P attr=value [attr=value...] csmconfig [-v] [-c] -d attribute csmconfig [-v] [-c] -V csmconfig [-v] [-c] -L [license-key-file] csmconfig [-v] [-c] -Z -u Should DMSRM accept unexpected requests to manage machines. -m Set the cluster type and model. This value is used for service. -p Set the mode for retrieving node power status. -s Set the cluster serial number. This value is used for service. -r The remote shell command path that CSM should use. -t The TFTP RPM package that CSM should use (default is tftp-hpa). -R Should CSM automatically set up remote shell security. -K Should CSM automatically set up security for Kerberos remote cmds. -P Set/display user-defined properties instead of attributes. -d Display just this one attribute value. -V Display the current CSM version installed on the management server -c Copy the CSM command binaries into /csminstall/csm. -L Provide a new license key file (ECF) to CSM. -Z Display the license agreement for a full license. -v Verbose mode. -h Display this usage information. attr=value Specific attributes to change in the IBM.DmsCtrl class. Usage: csmbackup [-h] [-v | -V] [-d directory] [-r Resource] [-f filename] -h Display this usage message -v | -V Verbose Mode -d directory Directory where CSM data will be written too. For example if you specified the directory /tmp/csm then CSM data would stored in /tmp/csm/ -f filename Filename that should contain a list of files that you want to to be backed up with the rest of CSM. For example, if you wanted to save /etc/hosts and /etc/dhcpd.conf then you could create a file called /tmp/mybakdata and the contents would be two lines: /etc/dhcpd.conf /etc/hosts This data would then be backed up with the other CSM files. -r Resource csmbackup will only back up a specific CSM resource class or file if you use the -r flag followed by 1 resource class or a file containing a list of files (like -f) The arguments that may be used are the following: Sensor - Backs up the information found in the IBM.Sensor class EventResponse - Backs up EventResponses (Those Responses found in the command lsresponse as well as scripts used by the ERRM Responses.) Condition - Backs up information found in the command lsresponse. Association - Backs up information regarding the mapped Conditions and Responses that are currently configured ManagedNode - Backs up data stored in the lsnode command. nodegroups - Backs up nodegroup information. DmsCtrl - Backs up information that is stored in csmconfig DeviceHwCtrl - Backs up the hardware control devices. DeviceGroup - Backs up the hardware control device groups. - If the -r option is followed by the name of a file that exits, then csmbackup will backup the contents of that file. Copying Kickstart Templates... Copying AutoYAST Templates... Creating backup directory %1$s The following files/directories should be manually backed up by the user to ensure that CSM has been completely saved: Please read %1$s for CSM backup/restore information Usage: csmrestore [-h] [-v | -V ] [-d directory] -h display this usage message -v |-V Verbose Mode -d directory Directory where CSM data will be read from. For example if you specified the directory /tmp/csm then the command csmbackup should have been run with the -d flag specifying /tmp/csm. It does not appear that the directory %1$s has any CSM backup data. Please run csmbackup to backup data before running csmrestore to restore data. There were no ERRM scripts/programs to restore Files under %1$s will not be restored %1$s was not found and will not be restored Restoring node definitions... Remove all existing nodes to restore saved nodes? (Y/N): Not restoring saved nodes Node definitions have been restored Remove all existing nodegroups to restore saved nodegroups? (Y/N): Not restoring saved nodegroups Nodegroup definitions have been restored Restoring RMC Event/Response information... IBM Event/Response information will not be restored because one or more of the following files were missing: %1$s %2$s %3$s Restoring kickstart templates... Restoring AutoYAST templates... Restoring CSM user customization scripts... There are several files in the %1$s directory that contain information on the state of the system when it was backed up. You may find it useful to look at these files. They include: Restoring hardware device definitions... Remove all existing hardware devices to restore saved hardware devices? (Y/N): Not restoring saved hardware devices Hardware device definitions have been restored Restoring hardware device groups... Remove all existing hardware device groups to restore saved hardware device groups? (Y/N): Not restoring saved hardware device groups Hardware device groups have been restored Warning: The OS or CSM version does not match the current version of the management server which is running %1$s %2$s %3$s and CSM version %4$s. Restoring %1$s backed up on %2$s %3$s %4$s CSM version %5$s... Warning: Some new predefined nodegrps created in CSM 1.4.1 release are missing after you restored nodegrps that were backed up in prior release. You should run predefined-nodegroups command to add them back. Least-privilege (LP) information will not be restored because one or more of the following files were missing: %1$s %2$s There are some install template files need to be restored, the default install template files on this management server may be overridden, do you want to restore the install template files? (Y/N):Not restoring saved install template files %1$s Backing up CSM data, this could take a few minutes. CSM backup data completed. Restore of CSM data completed. Copying install templates... Restoring install templates... %1$s: 2651-096 Free space in %2$s's filesystem %3$s is less than 1%. Free some space by removing %4$s, or specify a directory in a different filesystem, and then rerun the command. %1$s: 2651-097 Free space in %2$s's filesystem %3$s is less than 1 MB. Free some space by removing %4$s, or specify a directory in a different filesystem, and then rerun the command. %1$s: 2651-098 Space in %2$s's filesystem %3$s has been exhausted. Free some space by removing %4$s, or specify a directory in a different filesystem, and then rerun the command. off|on|unknown|not configuredHostname|HWControlPoint|Status|PowerStatus|Network-Interfaces|LCD1|LCD2Online|Offline|Failed-Offline|Stuck-Online|Pending-Online|Pending-Offline|Mixed|ErrorNot AvailableThere are no nodes currently defined in the cluster. Usage: csmstat [-h] [-S] [-d delimiter] [-a | [-n node_list ] [-N nodegroups ]] [-s selection_string] [-l] -h Displays this usage information. -a Displays the attribute information for all nodes. -s selection_string Selects which attributes you wish to display based on column headers. -S Sorts output first by hardware control point and then by host name. -l Displays LCD/LED values. -d delim The delimiter that should be used to separate the items displayed for a group. A newline separates groups. -n node_list Specifies a comma or space-separated list of node names to display attribute information. Space-separated node names must be inside double quotes. For information about specifying node ranges, see the noderange man page. -N ndgrp Displays the nodes that are in the nodegroups specified. The nodegroup is evaluated by the nodegrp command. Multiple nodegroups can be separated by commas or spaces (if the list is quoted). %1$s: 2660-004 %2$s is not a valid option for a select string Usage: hwdevgrp { -h | -f file | -L | -p | -a device_list | -d device_list | -x device_list | -D devicegroup | -l | -w selectstr | -W | -s devicename } [-g] [-v|-V] [-m delim] [group] hwdevgrp {-I | -S} group1 group2 -p Prints the membership of one or more groups. -a Adds devices to a group, creating the group if necessary. -d Replaces the current group membership with the given devices. -x Removes devices from a group. -D Deletes one or more groups. -l List all defined device groups. -L List the definition of some or all groups. -f A file that contains groups to be defined. Use the -L format. -w The select string "where" clause to use for a dynamic group. -W Display the select string "where" clause of the given group. -s Search - display all the groups that contain this device. -m The delimiter that should be used to separate displayed. -g The names in the group are generic names, not necessarily devices. -S Display the members in the 1st group that are not in the 2nd group -I Display the intersection of the 2 groups specified. -v or -V Verbose mode. -h Display usage information. group ... The group or groups to be acted on. Usage: createdevice [-h] [-v|-V] {-f file | name ...} [attr=value ...] -v or -V Verbose mode. -h Display this usage information. -f file Specifies a file that contains a list of device names. If the file name is "-", then the list is read from stdin. The file can contain multiple lines and each line can have one or device names, separated by spaces or commas. name ... Creates one or more devices in the DeviceHwCtrl table. The device names are distinguished from the attr=val pairs that follow because they do not have an equal sign in them. This argument can be combined with the -f option. attr=value ... Specifies attributes that should be set when creating the devices. Each attr=value pair should have no spaces, or the parts containing spaces should be quoted. A null value can be specified by "attr=". %1$s: 2651-044 Cannot remove devices from a group that has the where clause of the select string set. Use hwdevgrp -w to change the definition of the dynamic devicegroup. %1$s: 2651-045 Cannot set the where clause of a group that has a device list defined. Use hwdevgrp -a or hwdevgrp -x to change the definition of the static devicegroup. %1$s: 2651-046 Cannot display the where clause of the select string because it is not set for %2$s. It is most likely a static devicegroup. Try omitting the -W option. %1$s: 2651-047 Improper format in group file %2$s in the following line: %3$s Run hwdevgrp -L to see the expected format. %1$s: 2651-048 Devicegroup %2$s already exists - not overwriting it. %1$s: 2651-049 Cannot add devices to a group that has the where clause of the select string set. Use hwdevgrp -w to change the definition of the dynamic devicegroup. %1$s: 2651-053 Error opening file %2$s to read device list. Message from system: %3$s. %1$s: 2651-054 At least one device name must be specified. %1$s: 2651-055 Could not find %2$s in the device database. Run lshwdev without any arguments to see the list of valid device names. %1$s: 2651-056 Could not find one or more of the following devices in the database: %2$s. Run lshwdev without any arguments to see the list of valid device names. %1$s: 2651-057 Could not find one or more of the specified devices in the database. Run lshwdev without any arguments to see the list of valid device names. %1$s: 2651-058 No devices matched the specified select string. Run lshwdev to see a list of device names, or lshwdev -l to see the attribute values. %1$s: 2651-059 No nodes or devices found %1$s: 2651-060 The following device(s) already exists in the DeviceHwCtrl table: %2$s. Specify device names that do not already exist. Run lshwdev to see a list of existing devices. %1$s: The device(s) %2$s are not members of group %3$s. Usage: lshwdev [-i | -s | -p | -a attr,attr,... [-x] | -A] [-l | -F | -X file | -L delim] [-S] [-h] [-v|-V] {-w "selectstr" | [-D devicegroups] [-f file] [[-d] device_list]} -i Display ip addresses. Not valid with -l. -s Display the short hostname. Not valid with -l. -p Display the ping status of each device. -a Display the specified attribute(s). -A Display all attributes. -P Display device user-defined properties instead of attributes. -l Display in long format. -F Display in a format suitable for a devicedef file. -X Generates a XML devicedef file. -L The delimiter that should be used to separate the items. -x Do not display the device name at the beginning of each row. -w Display devices that match this select string "where" clause. -D Display devices in this comma-separated list of device groups. -f Display devices listed in this file (use "-" for stdin). -S Sort the output by the 1st attribute in each row (default). -v or -V Verbose mode. -h Display this usage information. [-d] The list of devices to list information about. %1$s: 2651-091 Device groups can not contain blanks. Change the group names and rerun this command. %1$s: 2651-094 Device %2$s belongs to the following device groups %3$s. Remove the device from these groups. %1$s. Environment Variable CSM_CFM_DELETE_FILES is set. Usage: chhwdev [-h] [-v|-V] [-P] {-a | -w selectstr | [-f file] [-D devicegroups] [[-d] device_list]} attr=value ... -w Change the devices that match this select string "where" clause. -a Change all the devices. -f Change the devices listed in this file (use "-" for stdin). -D Change devices in this comma-separated list of device groups. -P Change device user-defined properties instead of attributes. -v | -V Verbose mode. -h Display this usage information. [-d] One or more devices to change in the DeviceHwCtrl table. attr=value Attributes to be changed for the device(s). Usage: rmhwdev [-h] [-v|-V] [-f file] [-D devicegroups] [[-d] device_list] -v | -V Verbose mode. -h Display this usage information. -f file Specifies a file that contains a list of device names. If the file name is "-", then the list is read from stdin. The file can contain multiple lines and each line can have one or more device names, separated by spaces or commas. -D devicegroups Specifies a devicegroup or a comma-separated list of device groups on which to run the command. -d device_list The list of devices to remove. Can be a comma or space-separated list of device names. This can be combined with -D and -f. If this is the last argument specified, the -d is optional. %1$s: 2651-050 Could not find devicegroup %2$s in the database. Run hwdevgrp -l to see a list of valid devicegroups. %1$s: 2651-051 Could not find one or more of the following devicegroups in the database: %2$s. Run hwdevgrp -l to see a list of valid devicegroups. %1$s: 2651-068 Can not open file %2$s.Please check if environment variable PROBE_IGNPRBFILE is set to a correct file name. You did not specify any probes, therefore probemgr will run all probes. If you want to continue, please type Y or y:You did not specify any probes, therefore probemgr will run all probes in the default directory and %1$s. If you want to continue, please type Y or y:2651-069 Can not open directory %1$s. 2651-070 Can not close directory %1$s. 2651-071 Can not open this file for writing %1$s. File created: %1$s. 2651-085 mkresource --mkfile requires as input. 2651-086 The directory name %1$s is not valid. Only IBM.Condition, IBM.Association, IBM.EventResponse and IBM.Sensor are supported. %1$s %1$s: 2660-000 Timeout when polling RMC or required resource managers required. Do you want to update all predefined resources even if they are unlocked? (Y/N) Usage: mkresources [-h][-v|-V] [-f|-r|--mkfile ::|--mkall] [--all|--dir |--resfile ] [--install][-t ] --all Create all resources found under /opt/csm/install/resources. --dir directory Only create resources found under . --resfile Specify the resource definition file. -v|-V Verbose mode. -h Display this usage information. --install The userid for Sensor resources will not be verified. --mkfile :: Create a .pm file for the specified (already existing) resources. --mkall Create .pm files for all existing resources. -f Force the update of resources that already exist, even if they are not locked. -r Removes the predefined resources. -t timeout Number of seconds to wait for RMC and required resource managers to come up. Setting timeout to zero indicates no RMC status checking. Default is 180 seconds. 2651-072 %1$s: The stanza file %2$s cannot be found. 2651-073 %1$s: Cannot run the command %2$s, %3$s. 2660-011 %1$s: User %2$s does not have sufficient privilege to run this command. Usage: csmlicutil [--help] csmlicutil stanza_file This command is used by CSM to scan and update Licensed Internal Code. %1$s: 2660-012 An error was encountered while opening this file: %2$s. %1$s: 2660-013 The stanza file %2$s contains no code scan or update commands. %1$s: 2660-014 The file %2$s cannot be used from this directory. %1$s: 2660-015 The file %2$s cannot be a symbolic link. %1$s: 2660-016 The file %2$s is owned by an unauthorized user. Usage: itlmgen [-h] itlmgen -f product_information_file [-i] [-v|-V] -h Display usage information to standard output. -f Specify product information file path and file name. -i Specify that only generate inventory signature files. -v, -V Verbose mode. %1$s: 2651-087 Product information file must be specified by using -f option. %1$s: 2651-076 Can not open file %2$s. %1$s: 2651-077 No product name for product %2$s in product information file %3$s. %1$s: 2651-078 Item %2$s of product "%3$s" is missing in product information file %4$s. Usage: setWebSMClientDownload [-h] setWebSMClientDownload [--lang language] [--docroot dir] [-v | -V] -h Display usage information to standard output. --lang language Setup WebSM client download pages in specified language. --docroot dir Specify webserver document root directory. -v or -V Verbose messages. %1$s: 2651-079 Could not remove some WebSM client download files. %1$s: 2651-080 WebSM client download RPM %2$s is not installed. Install RPM before running this command. %1$s: 2651-081 Can not install Apache2 webserver RPMs. %1$s: 2651-082 Can not setup WebSM client download. %1$s: 2651-083 Can not link files for WebSM client download. %1$s: 2651-084 Can not obtain the setting of document root directory for the webserver. WebSM client download setup is finished.