ISO8859-19 7l V I $EAj03?.Q4-8)LFT;Q$8vY@ 6JB *!B"M 2#: $C %P &I P'* ($ )] *U H+X ,A - 9.N X/7 0F 15 &2= \7: 8H 9TA sB8~C5D#EEF;WG<HDI;J;QK1L/M5 I%UoPIC`5  A /Z t J VJWJ~VP qaBXOrL^OS3O:^w c_ :- GTe=w{1hTE]L EValidating Smart Assist for WebSphere MQ application idsmart assist for WebSphere MQ Application id=%1$s is not in the range [a-z][A-z][0-9]_completion of validating smart Assist for WebSphere MQ applicaton id=%1$sValidating WebSphere MQ server nodessmart assist for WebSphere MQ server has nodes=%1$s as repetitiveModifying WebSphere MQ server configuration %1$sChecking if the WebSphere MQ is already configured.WebSphere MQ server with application is %1$s already configuredListing the configured MQMs on local node %1$sThere were no MQ managers created on local node %1$sAdding WebSphere MQ server configuration %1$sThe name of %1$s provided is not valid, and it is: %2$sService IP label %1$s can not be resolvedservice label %1$s already defined in the PowerHA SystemMirror configurationAdding WebSphere MQ server Resource Group %1$s to PowerHA SystemMirror configurationFailed while adding WebSphere MQ server Resource Group %1$sAdding WebSphere MQ server Application %1$s to PowerHA SystemMirror configurationFailed while adding WebSphere MQ server Application %1$sAdding WebSphere MQ server Application monitor %1$s to PowerHA SystemMirror configurationFailed while adding WebSphere MQ server Application monitor %1$sAdding WebSphere MQ serveice IP to Resource Group %1$sFailed while adding WebSphere MQ service IP to Resource Group %1$sThere were no Unconfigured Queue Managers.Adding WebSphere MQ Resource Configuration to HACMPsa_metadata ODMFailed while Adding WebSphere MQ server configuration to HACMPsa_metadata ODMFailed while adding WebSphere MQ VG to Resource Group %1$sGenerating verify script for WebSphere MQ server configuration %1$sFailed while Generating verify script for WebSphere MQ server configuration %1$sRemoving WebSphere MQ server %1$s from PowerHA SystemMirror configurationResource Group count %1$s not found in ODMResource Group %1$s not found in ODMFailed while deleting Application monitor %1$s for changing WebSphere MQ server configurationFailed while deleting Application for changing WebSphere MQ server configuration %1$sFailed while deleting Resource Group %1$s for changing WebSphere MQ server configurationFailed while deleting WebSphere MQ server configuration from ODM.creating Service IP label %1$sNo suitable PowerHA SystemMirror network is defined to create service IP labelError while adding service IP label %1$s to netowk %2$sGenerating verify Header for WebSphere MQ server Application name %1$sGenerating verify Script for WebSphere MQ server %1$sPushing the verification scripts to other node %1$s is failedconfiguring WebSphere MQ server using manual configurationNo value is specified for Primary Node property in WebSphere MQ xml fileFailed while deleting service IP %1$s for changing WebSphere MQ server configurationWMQ_SERVERThe specified Queue Manager: %1$s is already configured.The Specified Queue Manager: %1$s is not exist/valid.The given XML file:%1$s is invalid.configuration information for the:%1$s is not found on the node:%2$s.The MQM user id on node: %1$s is not same as on local node.The MQM group id on node: %1$s is not same as on local node.The installed MQ version is different or Not installed on node:%1$s.Failed while removing the Custom verification method: %1$s.Error while adding the custom verification method for:%1$s.Failed: 'mqm' user does not exist in 'mqm' group.adding the custom verification method for:%1$s.Adding WebSphere MQ service IP to Resource Group %1$sStarting the WebSphere MQ server with Queue Manager %1$s and user as %2$sSuccessfully started the WebSphere MQ server with Queue Manager %1$s and user as %2$sFailed starting the WebSphere MQ server with Queue Manager %1$s and user as %2$sStopping the WebSphere MQ server with Queue Manager %1$s and user as %2$sMonitoring WebSphere MQ server configuration for Queue Manager %1$sQueue Manager %1$s is activeQueue manager %1$s is still starting up, it is activeQueue manager %1$s is not activeFinding WebSphere MQ listeners associated with Queue Manager %1$sSuccessfully found WebSphere MQ listeners: %1$sFailed while finding WebSphere MQ listeners associated with Queue Manager %1$s.For more details, refer log file %2$sStarting the WebSphere MQ listener %1$s associated with Queue Manager %2$sSuccessfully started the WebSphere MQ listener %1$s associated with Queue Manager %2$sWebSphere MQ listener %1$s associated with Queue Manager %2$s is already up and runningFailed while starting the WebSphere MQ listener %1$s associated with Queue Manager %2$s. The Queue Manager might be down or stopped.Stopping the WebSphere MQ listener %1$s associated with Queue Manager %2$sSuccessfully stopped the WebSphere MQ listener %1$s associated with Queue Manager %2$sWebSphere MQ listener %1$s associated with Queue Manager %2$s is already stoppedFailed while stopping the WebSphere MQ listener %1$s associated with Queue Manager %2$s. The Queue Manager might be down or stopped.Configuring application monitor for each WebSphere MQ listener associated with Queue Manager %1$sAdding listener monitor %1$s to PowerHA SystemMirror configurationFailed while adding listener monitor %1$s to PowerHA SystemMirror configurationSuccessfully configured application monitors for all the WebSphere MQ listeners associated with Queue Manager %1$sMonitoring the WebSphere MQ listener %1$s associated with Queue Manager %2$sWebSphere MQ listener %1$s associated with Queue Manager %2$s is up and runningWebSphere MQ listener %1$s associated with Queue Manager %2$s is not up and runningNo Listeners were provided in WebSphere MQ xml fileValidating the listeners provided in WebSphere MQ xml fileProvided listener(s): %1$s are not defined in WebSphere MQ server configuration. Available WebSphere MQ listeners associated with Queue Manager %2$s are: %3$sThere are no WebSphere MQ listeners defined for Queue Manager %1$s. Proceeding with WebSphere MQ server configuration without listeners.Failed to find the WebSphere MQ listeners. Ensure that WebSphere MQ Server is up and running to discover the listeners.ERROR: Ensure WebSphere MQ Server is up and running before trying to modify the MQ Server instance.Select a WebSphere MQ ManagerAdd a WebSphere MQ Manager Highly Available Resource GroupApplication NameWebSphere MQ Manager NamePrimary NodeTakeover Node(s)Service InterfaceModify a WebSphere MQ Manager Highly Available Resource GroupAdd a WebSphere MQ server Highly Available Resource Group, SMIT panel configures WebSphere MQ server operating system cluster configuration. The following information must be provided for each added instance * Application Name * WebSphere MQ server instance name * Primary cluster node for WebSphere MQ server Takeover node(s) for WebSphere MQ server * Service Insterface Specify the name for the collection of PowerHA SystemMirror component that represent WebSphere MQ server. The name is limited to 64 characters and cannot contain spaces. Select the node(s) name(s) which can be used by the WebSphere MQ RG as a fallover or secondary node(s). Specify the service interface can be used by MQ client to connect to the MQ server. Specifies the name of the WebSphere MQ server instance to be highly available its prefilled. Select the Primary/Home Node name for the WebSphere MQ highly available RG. Modify a WebSphere MQ server Highly Available Resource Group SMIT panel configures WebSphere MQ server, operating system cluster configuration.