ISO8859-1[?P\]^ _`ab cd 'e3fQg4mh ijklmno7pUqsrst%uvwxy%z<{R|c}~(/ 1;J^p  *-$X"},1"T2 7 D3P*0A*7fb*14&;[7/OfOmL$Hqm(4 v:I/-311H-z_Sei 8 ] 4!e!O7!=!."+""Z$"}F"'"=#y#O(##+$-$:O$h $$j$%a*%q1%3%&&4&.&c"'< '_F'$'+',(6(E.(|!(Z(2)()[)*+},t- -B.HD.+.Y.]/VH/H/w0F0\1M2?2]$2.2$2$3+3;3g3[4o<4!55*5 %6 :6 "6 7 +7b78Q8i8/8'889-9$9R(9m09/99:;5<('$>j( >)H>*'>+'?!,N?I-1?.*?/1?0,@'1#@T29@x3Q@41A5A661AU7$A8=A9%A:B;&B!<"BH=(Bk>B?B@BA.BBC CACD1C`EKCF#CG%DH+D(I0DTJDK$DLDMhDNjE>OMEPHEQFF@R9FS<FT.FUUG-V=GW>GXJHY>HKZ6H[8H\-H]GI(^BIp_BI`2Ia'J)b2JQcjJdGKeeL7fHLgMLhAM4iPMvjOMkMNl Nem=Nn&NoNpNqOr0Os6OFt&O}uOv)Ow"Ox8Py5PJz5P{"P|$P}FP~QEQ^QwQ'Q&Q(Q'R!*RI{RtR7SGS#T<T,#TiTTTjTeU?9UFU`V&fVXVEWG4WWWWX)X'XF;XnXCXOY DYZOYoY<Z_EZOZZ[2N[F[\#{\]ML]>^]^Y<^=^_2Q_BA__`taXSab!c(cdse4#eGfggfhhfi)jTjHTj3j9k&{k` kklme(n8nCn|oopqJZqrE.r-s/s=(sm=s$ss|tvtXu ue4u(v,evUPvLw LwY-w1w{xbxExy+yzfk{-{|{=|e7|.|.} X}9R} }=}/~0~`0~ ~~~QWjbOw ^ 0& W O K-WypBoY#KdE5T,scY:+Oo{` RLGathering cluster information, which may take a few minutes... Node IDRun Time Parameters: Debug LevelFormat for hacmp.outTakeover for inactive nodeHost uses NIS or Name ServerSecurity ModeOwned Resources: FilesystemsFilesystems Consistency CheckFilesystems Recovery MethodFilesystems/Directories to be exported (NFSv2/NFSv3)Volume GroupsConcurrent Volume GroupsDisksGMVG Replicated ResourcesGMD Replicated ResourcesPPRC Replicated ResourcesERCMF Replicated ResourcesSVC PPRC Replicated ResourcesTRUECOPY Replicated ResourcesSRDF Replicated ResourcesApplication ServersMiscellaneous DataAuto Discover/Import of Volume GroupsInactive Takeover9333 Disk FencingSSA Disk FencingTake Over Resources: Take over from node idDynamic Node PriorityService IP LabelFilesystems to be NFS mountedNetwork For NFS MountFilesystems mounted before IP configuredUsage: %s [-g group] [-n nodename] [-d odmdir] Resource Group NameNode RelationshipParticipating Node Name(s)Node NameResource GroupParticipating NodesSite RelationshipStartup PolicyFallover PolicyFallback PolicyDelayed Fallback TimerOnline On Home Node OnlyOnline On First Available NodeOnline On All Available NodesOnline Using Distribution PolicyFallover To Next Priority Node In The ListFallover Using Dynamic Node PriorityBring Offline (On Error Node Only)Never FallbackFallback To Higher Priority Node In The ListPrefer Primary SiteOnline On Either SiteOnline On Both SitesignoreUse forced varyon for volume groups, if necessary%1$s: Startup policy 'Online On All Available Nodes' can have only 'Bring Offline (On Error Node Only)' as fallover policy and 'Never Fallback' as fallback policy. %s: no shared %s defined. Node %ld is not configured. NameStart ScriptStop ScriptNode %ld's Server ODM is different from local one. Usage: %s [-c] [-h] [-n name] [-d odmdir] ODM resources on two shared nodes do not agree. Invalid field name. Usage: %s [-g group] [-e] [-c] [-f field] [-d odmdir] [-q query] Usage: %s [-c] [-h] [-n name] [-o odmdir] ERROR: The distributed and non-distributed resource groups cannot be configured on the same network. %1$s: Resource Group %2$s does not exist. Priority must be in the range of 0 - 100 percent Warning: %s is not in the NAME=VALUE pattern! Skip. Usage: %s -g group [-d odmdir] NAME=VALUE [NAME=VALUE ...] %1$s: Colons are not allowed in resource group fields. %1$s: Error: The length of the %2$s is > %3$d. %s: The use of Concurrent Volume Groups requires the CLVM LPP to be installed. WARNING : A Network For NFS Mount was specified, but no Filesystems to NFS mount have been specified. Dynamic Node Priority not available for Resource Groups with Startup Policy 'Online On All Available Nodes'. ERROR: Shared service IP '%1$s' does not exists or not properly configured. ERROR: Shared service IP label '%1$s' does not belong to a HACMPnetwork NFS mount / Filesystem: %1$s is incorrectly specified. Please specify as /NFS_Mount_Point;/Local_Filesystem. ERROR: The specified NFS mount point: %1$s for local filesystem: %2$s is not a full path. All filesystems must be specified in full. ERROR: The specified local filesystem: %1$s for NFS mount point: %2$s is not a full path. All filesystems must be specified in full. %1$s: Resource Group '%2$s' with a Startup Policy '%3$s' does not support Concurrent Volume Groups. Only the Resource Groups with 'Online On All Available Nodes' as startup policy support Concurrent Volume Groups. %1$s: Resource Group '%2$s' with a Startup Policy '%3$s' does not support SSA Disk Fencing. Only the Resource Groups with 'Online On All Available Nodes' as startup policy support SSA Disk Fencing. %1$s: Invalid resource in resource group '%2$s'. The Distributed Resource Groups cannot support Concurrent Resources. %1$s: Dynamic Node Priority Policy '%2$s' does not exist. %1$s: "%2$s" is an undefined GeoMirror device. %1$s: "%2$s" is an undefined PPRC pair name. %1$s: "%2$s" is an undefined ERCMF VolumeSet name. %1$s: "%2$s" is an undefined SVC PPRC pair name. %1$s: "%2$s" is an undefined TRUECOPY pair name. %1$s: "%2$s" is an undefined SRDF pair name. %1$s: Resource Group '%2$s' with startup_policy 'Online Using Distribution Policy' requires a Service IP Label when the global distribution policy is set to 'network'. %1$s: Resource Group '%2$s' with Node Relationship '%3$s' does not support a Service IP Label. %1$s: Resource Group '%2$s' with Node Relationship '%3$s' does not support any types of filesystems. %1$s: Resource Group '%2$s' with Node Relationship '%3$s' does not support non-concurrent volume groups. Could not find working or valid IP address for node %s. %1$s: Resource Group '%2$s' with Node Relationship '%3$s' does not support Inactive Takeover %1$s: Delayed Fallback Timer '%2$s' does not exist. %1$s: Resource Group '%2$s' with Node Relationship '%3$s' does not support delayed fallback timers. Auto Discover/Import of Volume Groups was set to true. Gathering cluster information, which may take a few minutes. %1$s: Could not retrieve cluster information. %1$s: Cannot open temp file %2$s. %1$s: Cannot remove temp file %2$s. %1$s: Volume group %2$s cannot be specified as a shared volume group. It is a member of resource group %1$s. Importing volume group %1$s to the following node(s): %2$s WARNING: Major number %1$s is not available on all the nodes in the resource group. Major number %2$s will be used. See %1$s for more detailed information. %1$s: Insufficient memory. %1$s: Error determining major number type. %1$s: %2$s is not a shareable volume group. %1$s: A node by node migration is in progress on the following node(s): %2$s. Could not perform all imports. No ODM values were changed. %1$s: File %2$s should contain data harvested for Auto Discover/Import of Volume Groups, but it is empty. Initializing.. Collecting information from local node... Collecting information from all cluster nodes... %1$s:Could not collect information from node %2$s. Processing... Storing information in file %1$s:Problem accessing the configuration file %2$s. No volume group information is known. You can discover the volume groups by going to the 'Discover PowerHA SystemMirror-related Information from Configured Nodes' panel, or type in the name of desired volume group. Resource Group name %s not found. FATAL ERROR: Ran out of memory! %s: Resource Group %s already exists. Duplicate entries not allowed. %s: Unrecognized node relationship. %s: Too many characters in node name list. %1$s: %2$s is not an existing node or site. %1$s: Too many characters (64 max) in node name %2$s. %s: Too many nodes (8 max) in node name list. %1$s: Duplicate Node Name: %2$s. Usage: %s -g resource_group -r relationship -s site_relationship [-o odmdir] -n nodes ... %s: Unrecognized site relationship, using ignore. %1$s: Resource Group %2$s has resources configured. Configured resources must be deleted in order to change the resource group behavior policies. %1$s: ERROR: Startup policy 'Online On All Available Nodes' can have only 'Bring Offline (On Error Node Only)' as fallover policy and 'Never Fallback' as fallback policy. WARNING: Resource Groups with 'Bring Offline (On Error Node Only)' as fallover preference when the startup preference is not 'Online On All Available Nodes' could allow resources to become unavailable during error conditions. ERROR: Invalid configuration. Resource Groups with 'Bring Offline (On Error Node Only)' as fallover preference when the startup preference is not 'Online On All Available Nodes' allow resources to become unavailable during the error conditions. ERROR: Invalid configuration. Resource Groups with Startup Policy 'Online Using Distribution Policy' can have Only 'Never Fallback' as Fallback Policy ERROR: Invalid Configuration. Resource groups with a site policy of 'Online On Both Sites' can only have a startup policy of 'Online On All Available Nodes' ERROR: Invalid Configuration. Resource groups with a startup policy of 'Online On All Available Nodes' can only have a site policy of 'Online on Both Sites' %1$s: Server %2$s already exists. Duplicate entries not allowed. Usage: %s -s server-name -b start-script -e stop-script [-d odmdir] server name '%s' cannot contain any spaces ERROR: Minimum number of CPUs must be less than or equal to the Desired number of CPUs. ERROR: Minimum amount of memory must be less than or equal to the Desired amount of memory. ERROR: Minimum amount of memory must be specified in 256 MB increments. ERROR: Desired amount of memory must be specified in 256 MB increments. You cannot use CUoD resources without acknowledging that there might be extra costs due to usage of the CUoD license. Dynamic LPAR and CUoD resource provisioning for this application server already exists. Please use the "Change/Show Dynamic LPAR and CUoD Resources for Applications" or "Remove Dynamic LPAR and CUoD Resources for Applications" to edit it. Usage: %s -n CS DLC name [-p port name] [-l linkstation name] [-v service path] [-o odmdir] %1$s: Communication Link %2$s already exists. Duplicate entries not allowed. %1$s: Only %2$ld CS DLC profiles may be made Highly Available. %s: The object name %s is too long. %s: Duplicate group name entries not allowed. %s: Unrecognized node relationship. %s: Unrecognized site relationship. %s: Too many characters in node name list. %1$s: Resource Group %2$s has resources configured. Configured resources must be deleted in order to change the node relationship. %1$s: Resource Group %2$s has resources configured. Configured resources must be deleted in order to change the site relationship. Usage: %s -g resource_group [-o odmdir] [-G new_name] [-r relationship] (-n node_name ...) Group name [%1$s] should not be more than %2$ld characters. %1$s: Group name %2$s not found. WARNING: The resource group %1$s is configured in resource group dependency configuration. The new name will be updated automatically in the resource group dependency configurations. %1$s: The resource group %2$s is configured in the resource group dependency configuration. Please delete the group from the dependency configuration prior to changing the group. %1$s: Node Name %2$s does not exist. Usage: %s -n node [-d odmdir] NAME=VALUE [NAME=VALUE ...] %1$s: Server name %2$s not found. Usage: %s -o old_server_name -c min_cpu -C desired_cpu -r min_mem -R desired_mem -u use_cod_or_not -U [-s server_name] [-b start_script] [-e stop_script] [-d odmdir] server name '%s' cannot contain any spaces Usage: %s -n HA Comm Link name [-p port name] [-l linkstation name] [-v service path] [-o odmdir] godm_init(%s): failed. godm_mount_class(%1$s): %2$s godm_get_list: %s Usage: %s [-c] [-q criteria] -n nodename class Unable to retrieve disks from node %s. No disks retrieved. Usage: %s -g resource_group Unable to retrieve filesystems from node %s. No filesystems retrieved. Usage: %s [-g resource_group | -n | -s] %s: Resource Group not configured or not found. Unable to retrieve volume groups from node %s. No volume groups retrieved. Usage: cllsvg [-g resource group] [-v] [-n] [-c or -s] [-S] -v display only active VGs -n display the nodes that share each VG -s display shared VGs currently in resource groups -c display concurrent VGs currently in resource groups -g display VGs for one resource group -S display VGs available to be shared Specify -c or -s, but not both. Other arguments can be specified in any combination. If niether -c nor -s is specified, then both shared and concurrent VGs are listed. %s: Resource Group not found. %1$s: Group name %2$s removed from HACMPgroup Class. Usage: %s -g resource_group [-o odmdir] %1$s: ERROR: The resource group %2$s is configured in the resource group dependency configuration. Please delete the group from the dependency configuration prior to removing the group. Usage: %s [-d odmdir] [-g group] Usage: %s [-d odmdir] server-name or 'All' Application server [%s] does not exist. Usage: %s [-o odmdir] Communication Link name or 'All' Communication Link [%s] does not exist. usage:clresgrp -a|-d|-c -g group_name -n resource_name [-m new_resource_name] -t type clresgrp():Error in claddgrpres(): clresgrp(): Unknown option [%s] add_res_grp(): Invalid data: Group [%1$s], Resource [%2$s], Type [%3$s] add_res_grp():Error in add_res_grp(): del_res_grp():Error in add_res_grp(): Invalid data: Group [%1$s], Resource [%2$s], New Resource [%3$s], Type [%4$s] add_group_odm(): Could not find object with [%s] update_group_odm(): Invalid criteria [%s] update_group_odm():Error in update_group_odm(): update_group_odm(): No objects deleted [%s] del_group_odm(): Cannot malloc: %s del_group_odm(): Could not find object with [group = %s] Usage: %s -n nodename -c class -s odmdir1 -t odmdir2 -q criteria [-f field1 ...] Unable to retrieve logical volumes from node %s. No logical volumes retrieved. Usage: %s [-g resource_group | -c | -s] [-n][-v] Usage: %s -n node [-c] [-d odmdir] Usage: %s [-g resource_group] [-o objdir] [-c | -h -f field] No mem allocated for first parameter Node list empty cannot malloc memory for return value cllspfile(): no dir name provided clls_snapshot():Not valid dir name [%s] Invalid parameters Cannot alloc memory: %s Invalid node name [%s] odm_err_func():[%1$s] error in function [%2$s]HTY Service IP LabelHTY SERVICE LABEL cannot be specified without a SERVICE IP LABEL %s: Service IP Label not found for HTY addr:'%s. Hty boot address not allowed for the SERVICE IP LABEL or HTY SERVICE LABEL Usage: %s [-g resource_group] [-n] get_secmode: odm_get_list() failed! Multiple security modes set for node [%s] Failure in opening a shell socket on node %1$s. Connections ServicesHighly Available Communication LinksFast Connect ServicesWARNING : Fast Connection services and Connections Services Cannot coexist in the same Resource Group. ERROR : Fast Connection services and AIX Connections Services Cannot coexist in the same Resource Group. %1$s failure: The parameter "%2$s" takes not more than %3$d characters. %1$s failure: The parameter "%2$s" should start with an Alphabet. %1$s failure: The parameter "%2$s" contains invalid characters. %1$s failure: The parameter "%2$s" cannot be a Keyword. %1$s failure: The parameter "%2$s" contains "." character. %1$s failure: Failed to open the "%2$s" file. %s failure: The application monitor name must match an existing application server. %s failure: An application monitor named %s already exists. %s failure: Monitor type must be either "process" or "user." %s failure: No two processes in the process list can have the same name. %s failure: For process monitoring, there must be one owner. %s failure: The parameter "%s" takes a single value. %s failure: The parameter "%s" must be zero or larger. %s failure: The parameter "%s" is required. %s failure: The failure action must be either "notify" or "fallover." %s failure: The monitor type must be either "user" or "process." %s failure: For "%s" monitoring, the parameter "%s" is required. %s failure: The parameter "%s" is not supported. %s failure: Unexpected argument "%s." %s failure: The ODM directory %s does not exist. %s failure: Configuring notify action for resource groups is allowed only under PowerHA SystemMirror sites configuration. The notify action for resource groups will prevent the cluster manager from automatically moving a failed resource groups to its peer site during an error. This configuration will have no effect on intra-site fallover of a resource group. %s warning: "%s" monitoring chosen, so the parameter "%s" is ignored. %s warning: Since multiple processes are to be monitored, the parameter "INSTANCE_COUNT" must be 1. %s warning: Only one value of parameter "%s" is allowed. Will use %s. %s warning: The parameter "INSTANCE_COUNT" must be at least 1: Will use 1. %s warning: The parameter "%s" was not specified. Will use %s. %s warning: No "RESTART_METHOD" was specified. Using the server start method. %s warning: No "CLEANUP_METHOD" was specified. Using the server stop method. %s warning: The parameter "%s" was not specified. Using the value of "%s." %s: Setting the ODM path to %s Usage: %s [-d ODMDIR] name=value [name='value1 value2']... name can be name, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, or %s. Usage: %s [-d odmdir] name1[ name2[ name3]]... Usage: %s [-d odmdir] [-c] [-h] [-H] [-t type] [name] %s: The monitor "%s" does not exist. %s: Monitor "%s" was removed. %s: No application monitors were found. %s: Bad monitor type "%s" found. %s: The monitor is of type "%s," not "%s" as expected. %s: The "restart_interval" is too short: using %s. %s exiting because of errors. The ODM is unchanged. %s: No application server found. %s: Non-unique application server. #Name:Description:Device:Start_sync:Stop_sync:Start_script:Stop_script Description = [%s] Device name = [%s] Start script = [%s] Stop script = [%s] Synchronous tape start processing. Synchronous tape stop processing. Asynchronous tape start processing. Asynchronous tape stop processing. Usage: %s [-c] [-h] [-n name] [-o odmdir] Usage: %s -n tape resource [-d device] [-s (0|1) ] [-S (0|1)] [-D description] [-p start script] [-P stop script] [-o ODM] Usage: %s -n tape resource [-N new tape resource name] [-d device] [-s (0|1) ] [-S (0|1)] [-D description] [-p start script] [-P stop script] [-o ODM] Usage: %s [-o odmdir] ( [-n] Tape Resource Name | -A ) %s: Tape Resource [%s] already exists. Duplicate entries not allowed. Tape Resource [%s] does not exist. %s: The object name [%s] is too long. Maximum length is %ld %s: Tape Resource name is required %s: Can not open ODM Shared Tape Resources#No tape resources exist. %s: Illegal name [%s]. Names must begin with a letter, and consist of only letters, digits, '_', and '-'. %s: Illegal name [%s]. Names must begin with a letter, and consist of only letters, digits, and '_'. Usage: %s -n [-c | -C] [-f] [-g The volume group named %s on node %s has different name %s on node %s Usage: %s -n NPP-name [-D NPP-description] -v resource-variable -c condition [-d ODM-directory] Usage: %s -n name [-N new_name] [-D description] -v resource_variable -c condition [-d ODM_directory] %1$s: Dynamic Node Priority Policy %2$s already exists. Duplicate entries not allowed. %1$s: Dynamic Node Priority Policy %2$s contains invalid characters. Usage: %s [ -s | -S | NPP_name ] [-d ODM_directory] Description = [%s] Resource Variable = [%s] condition = [%s] NPP [%s] does not exist. No Dynamic Node Priority Policies exist. Usage: %s {...} NPP %s is part of resource group %s and cannot be deleted. NPP [%s] has been deleted! %1$s: ERROR: Monitors are not supported for resources of type %2$s %1$s: ERROR: The resource to monitor must match an existing cluster resource. %1$s: warning: Definition for %2$s does not exist, will create it. %1$s: failure: Monitor type must be "process", "user" or "selective_fallover" %1$s: warning: For "%2$s" resources the only supported options are "%3$s" and "%4$s", all others are ignored. %1$s failure: For "%2$s" the parameter "%3$s" is required. %1$s: changing existing entry for %2$s, old value = %3$s, new = %4$s %1$s failure: Monitor type must be "process", "user" or "selective_fallover". %1$s information: Parameter "%2$s" was not specified for "%3$s", it will be created now. %1$s: Updating application monitoring configuration with new server name %2$s %1$s: Updating resource group configuration with new server name %2$s ERROR: Invalid HACMPsite configuration detected. The site configuration must have two sites defined, one as primary site for a resource group and other as a secondary site. ERROR: Site [%1$s] is defined as the Primary Site for the Resource Group. Node [%2$s] does not belong to the Primary Site. ERROR: Site [%1$s] is defined as the Secondary Site for the Resource Group. Node [%2$s] does not belong to the Secondary Site. %s failure: The invocation type must be one of: startup, longrunning, both ERROR: Dependencies for RG '%s' Circular list is detected: %s ERROR: Dependencies for RG '%s' Too many levels, number of supported levels = %d List is: %s Resource group '%s' has the following child resource groups Resource group '%s' has the following parent resource groups Monitor Name(s)Monitor %1$s will not be used until it is associated with an application server. Warning: %1$s is not an application server. Ignoring this value. Resource Group %s has been configured for serial acquisition and release. Only Resource Groups with 'ignore' as the Inter-Site Management Policy can be configured for parallel acquisition or release.%1$s: Application monitor %2$s has a non-zero restart count, but no restart method was specified. The start script %3$s from application server %4$s will be used as the restart method. %1$s: WARNING: NFS mounts were specified for the resource group '%2$s', however no NFS exports have been specified. %1$s: ERROR: A service label must be specified if NFS exports have been specified. %1$s: WARNING: At least one IP label is missing from the previous synchronized configuration. This may cause a service interruption to NFS clients. In addition to that, this Resource Group, %2$s, must be taken offline before performing the next synchronization. %1$s: WARNING: At least one cross mount was mounted on NFSv4 exports of '%2$s'. This configuration change may remove NFSv4 exports causing the cross mount(s) to be unavailable. %1$s: WARNING: At least one cross mount was mounted on NFSv2/NFSv3 exports of '%2$s'. This configuration change may remove NFSv2/NFSv3 exports causing the cross mount(s) to be unavailable. %1$s: WARNING: A Stable Storage Path was specified for Resource Group %2$s, but no NFSv4 exports were specified. The Stable Storage Path will be ignored. %1$s: ERROR: The Stable Storage Path, %2$s, must be stored in a filesystem that is managed by this Resource Group. %1$s: WARNING: The Stable Storage Path has changed from the previous synchronized configuration. This change may cause the NFSv4 server to lose important client state needed for a clean fallover. Resource Group '%2$s' should be be brought offline before performing the next synchronization. %1$s: ERROR: Failed to verify the validity of the Stable Storage Path. %1$s: WARNING: Stable Storage was not specified for the Resource Group '%2$s'. The use of Stable Storage is highly recommended with NFSv4 exports since it is used to store NFSv4 client state to facilitate a clean fallover. %1$s: WARNING: Stable Storage is part of the NFS exports. This is strongly discouraged as it may lead to accidental NFSv4 metadata corruption. %1$s failure: The name "%2$s" is reserved and can not be used for user defined application monitors. %1$s failure: Following attributes can not be changed for the "%2$s" application monitor. RESOURCE_TO_MONITOR MONITOR_METHOD INVOCATION Change was attempted on at least one of the above attributes.%1$s failure: The name "%2$s" is reserved and can not be used for user defined application monitors. %s: The monitor "%s" can not be removed. ERROR: The application server name '%1$s' is reserved. Please select another name. ERROR: The application server name '%1$s' is reserved. Please select another name. ERROR: The application server '%1$s' is read-only. ERROR: The application server '%1$s' may not be deleted. The resource group '%1$s ERROR: The resource group '%2$s' has WPAR attribute set. WPAR function is supported only on AIX. WPAR Name%1$s ERROR: The resource group '%2$s' does not contain a 'Service Label' resource but has 'WPAR Name' set. To run a resource group in a WPAR, a 'Service Label' must be added to the resource group. %1$s ERROR: The resource group '%2$s' contains a 'Tape Resource=%3$s' resource and has 'WPAR Name' set. Tape resources are currently not supported for a WPAR-enabled resource group %1$s ERROR: The resource group '%2$s' has Startup Policy='Online On All Available Nodes' and has the 'WPAR Name' property set. Concurrent resource groups cannot be WPAR-enabled. ERROR: cmd '%1$s' failed with rc '%2$s' Attempting to undo WPAR related changes made so far.... %1$s ERROR: Failed to add an internal WPAR application Server to enable WPAR for resource group '%2$s'. Contact IBM support team for resolving this problem. %1$s ERROR: Failed to add an internal WPAR application monitor to enable WPAR for resource group %2$s. Contact IBM support team for resolving this problem. %1$s FATAL ERROR: There was a fatal internal error and the PowerHA SystemMirror configuration data may not be in consistent state anymore. You may have to restore a snapshot copy before you continue further or contact IBM support for help. %1$s ERROR: Failed to remove an internal WPAR application Server to enable WPAR for resource group '%2$s'. Contact IBM support team for resolving this problem. %1$s ERROR: Failed to remove an internal WPAR application monitor to enable WPAR for resource group %2$s. Contact IBM support team for resolving this problem. ERROR: Nodes specified under primary and secondary sites belong to the same site [%1$s]. ERROR: The specified WPAR Name '%1$s' for resource group %2$s is invalid. Please use the pick list to select a valid WPAR Name or leave the field blank. Filesystems/Directories to be exported (NFSv4)Filesystem/Directory for NFSv4 Stable Storage%1$s: Memory allocation failed for %2$s class. Failed updating internal topology data. ERROR: Managed system name '%1$s' cannot contain any spaces. ERROR: %1$s must be zero or larger. # Resource Group File System %1$s: The node list contains %2$s nodes which exceeds the limit of %3$s nodes. Specify fewer nodes for this resource group. %1$s: The specified %2$s: %3$s is %4$d characters which exceeds the limit of %5$d characters. Specify a shorter name. %1$s: ERROR: Invalid character found in field "%2$s" %3$s ";"(semicolon) not allowed %1$s: Resource Group %2$s has resources configured. The resource group must be offline in order to change a resource group's behavioral polices. There are no Application Servers currently defined. Processing units value %1$s is invalid. The minimum processing units, %1$d.%2$d, must be greater than the desired processing units, %3$d.%4$dAt least %1$d virtual processors must be present for %2$d.%3$d processing units At most %1$d virtual processors can be used with %2$d.%3$d processing units The minimum processing units, .%1$d, is too small. It must be at least .10 ERROR: Userdefined Resource %1$s is invalid ERROR: Userdefines Resource Type %1$s is invalid %1$s warning: The parameter "%2$s" value specified is greater than the Maximum allowed timeout value. will use "%3$5ld." %1$s warning: The parameter "%2$s" was specified as zero or less than zero. will use "%3$5ld." %1$s: Dynamic Node Priority Policy is '%2$s'.No SDNP script provided %1$s[%2$d]: ERROR: Resource group %3$s cannot be converted to 'Online on All Available Nodes' because the resource group already contains volume group %4$s %1$s[%2$d]: ERROR: Resource group %3$s cannot be converted to 'Online on All Available Nodes' because the resource group already contains service label %4$s %1$s[%2$d]: ERROR: Resource group %3$s cannot be converted from 'Online on All Available Nodes' because the resource group already contains concurrent volume group %4$s Usage: %s -s server-name -b start-script -e stop-script [-d odmdir] [-O start-option] [-m monitor_name(s)] %1$s: Application controller %2$s not found. Usage: %1$s -o old_server_name -c min_cpu -C desired_cpu -r min_mem -R desired_mem -u use_cod_or_not -U [-s server_name] [-b start_script] [-e stop_script] [-d odmdir] [-O start-option] Application controller name '%1$s' cannot contain any spaces ERROR: The application controller '%1$s' is read-only. Application controller '%1$s' does not exist. There are no application controllers defined. ERROR: The application controller name '%1$s' is reserved. Please select another name. %1$s: Application controller %2$s already exists. Duplicate entries not allowed. Startup modeERROR: The application controller '%1$s' may not be deleted. Usage: %s [-c] [-h] [-m] [-n name] [-d odmdir] GENERIC XD Replicated Resources%1$s: "%2$s" is an undefined Mirror Group name. Raw Disks Disk Error Management? %1$s: INFORMATION: Monitor %2$s does not exist. You must define the monitor before associating it with an application controller. %1$s: INFORMATION: Monitor %2$s is already configured to monitor controller %3$s %1$s: Updating the application monitoring configuration with the new application controller name, "%2$s". %1$s: Updating the resource group configuration with the new application controller name, "%2$s". %1$s: INFORMATION: No monitor is associated with application controller %2$s . %1$s failure: The parameter restart method must be specified when restart count is non-zero. %1$s: Provided SDNP Script %2$s does not exist %1$s: ERROR: Invalid value found in field "%2$s": %3$s File system name must use absolute path; must start with "/" (forward slash). %1$s failure: Invalid character found in field "%2$s" "-"(dash) not allowed %1$s: Dynamic Node Priority Policy is '%2$s' and an SDNP scriptspecified. %1$s: ERROR: The parameter "%2$s" has value %3$d and it must be a value between %4$s. %1$s: WARNING: Monitor Retry Count cannot be tuned when Monitor Mode is StartUp. Setting it to Default value 0. %1$s: WARNING: Critical resource group %2$s is being deleted. Another resource group must be defined as critical before performing verification and synchronization. ERROR: Invalid Configuration. Fallover using Dynamic Node Priority is not supported when sites are configured. %1$s: ERROR : Stable Storage was not specified for the Resource Group '%2$s'. Stable Storage is required with NFSv4 exports since it is used to store NFSv4 client state to facilitate a clean fallover. WARNING: The resource group %1$s is configured for backup. Updating the name in Backup Profile configuration failed. Manually update the information using command: WARNING: The resource group %1$s is configured for backup. Deleting from the Backup Profile configuration failed. Manually delete the entry using command: %1$s: INFORMATION: Monitoring for application controller %2$s is disabled. Application process '%1$s' does not appear to be in absolute format. Application process '%1$s' does not appear to exist. CPU usage monitor interval '%1$d' is not in valid range of 1 minute to 120 minutes. CPU usage monitor interval '%1$s' is not an integer. Provide an integer value in range of 1 minute to 120 minutes. CPU usage monitor interval is empty. Provide an integer value in range of 1 minute to 120 minutes. ERROR: %1$s: Dynamic Node Priority Policy "%2$s" with sites is not supported. Dynamic Node Priority Policy is allowed only for user defined policy scripts when sites are configured. %s failure: Enable AM logging must be either "Y" or "N." %1$s: ERROR: Resource group '%2$s' is part of an Online on Same Dependency along with group '%3$s'.Resource group '%2$s' is configured with fallback timer '%4$s', but resource group '%2$s' is not.All resource groups in an Online on Same Node dependency must have the same fallback timer configured. %1$s: Application controller %2$s already exists. Choose a different name for the application controller %3$s. %s warning: The parameter "%s" was not specified or specified with 0. Using the value of "%s." %1$s warning: "%2$s" is specified with 0. Setting "%3$s" with default value %4$s.