ISO8859-1 " 9' \)  / & & " * I % t B " ! ; "$ ^% $ )   & 3& Z 0  ' !  2< O1 - ! " #  $,%G&_'y(9)5*0+@),,j-<.//00Q51*28345#6*37^8<~9:;< =>,{?F@cAxSB?C DEF3GDHaI%J"KL5M.NKO gP$tQ R+ST-U!)VKW+fXYZ&[ \]F^!_9`;a =b Jc6Wde!fghhiYjmklmn op3q4r7s Lt$WuU|vMw x%7y[]z%{|}/~Lb]x   ?  , B K [ t   & & *! !8 !G!Q!Z !c!p!!,!! ! !"  ""&";'"J"r!" "! "" "#"$ "% "&#' #"(#0)##A*##e+#,#-#. #/#0&#1$2($3$G4$$g5$6$72$8"$9%:%; %<%*=%0>%8?%? %P)%m%[%&& &3%&J&p "& R&U'M'e(B()8g)+A =+ ," M, - \-:.9I.t8.:.'/2C/Z0/B/<00OG0o(0=0>11]1B23: 4!b4""5#5*$_5%66&6'+7u(N7)l7*N8]+P9,L9-o:J.:/5;X0>;1Y;2<'3U<4=5=67>b7F>8?9V@:3A;B <ZB=Cn>XD3?E@G"AnGB6HCnHUDLHE3IFhIEGIH JVI(KdJLK%MLYNM ON6P*O8PaPPQ`QDR\Q0965-001: Cannot backup %s. 0965-002: Cannot change %s owner. Cannot change working directory to %s. Cannot discover nodes from %s, skipping. 0965-003: Cannot create %s. 0965-004: Cannot create RBAC authorization %s. 0965-005: Cannot create RBAC role %s. 0965-006: Cannot create directory %s. 0965-007: Cannot create filesystem on %s. 0965-008: Cannot create log file %s. 0965-009: Cannot create logical volume %1$s in volume group %2$s. 0965-010: Cannot create SSH keys. 0965-011: Cannot create user %s. Cannot create XML element for node %s, skipping this node. 0965-012: Cannot create XML parser. 0965-013: %1$s: Cannot execute %2$s. 0965-014: Cannot list directory %s. 0965-015: Cannot mount filesystem on %s. 0965-016: Cannot open %s. 0965-017: Cannot open file %s. 0965-018: Cannot open %s for reading. 0965-019: Cannot open %s for writing. Cannot open log file %s. 0965-020: Cannot open XML schema definition %s. 0965-021: Cannot parse %s. Cannot redirect standard error output. Cannot redirect standard output. Cannot remove directory %s. Collect interrupted during phase %1$s of collect type %2$s. Collect type "%1$s" done, see results in "%2$s". ============== Status report: ============== UNREACHABLE IGNORED SUCCEEDED FAILED (%d) Cannot run %1$s phase %2$s for %3$s (fork). Creating missing user. Ignoring node type '%s'. Trying '%s'...%1$s@%2$s is already in hosts database, use -F to force. %1$s@%2$s is not in hosts database, use -F to force. Initializing access to '%1$s' on host '%2$s'... Cannot initialize access to '%1$s' on host '%2$s' (error %3$d). Removing access to '%1$s' on host '%2$s'... Cannot remove access to '%1$s' on host '%2$s' (error %3$d). Directory %s is not referenced by any collect. Directory %1$s does not exist for collect %2$s. 0965-022: The cdat directory path is not defined. Please, run 'cdat init' first. Discovering nodes managed by %1$s@%2$s... Document %s does not match XML schema, trying anyway... Done. Enter %1$s@%2$s's password: File %s already exists, replace it?File %1$s does not exist for collect %2$s Is the collect for IBM support?Invalid PMR '%s', format should be 'PMR#,BRANCH#,COUNTRY#'. 0965-023: %s is missing. Location: %s lpar idmachine idUsage: cdat access -h cdat access [-dF] [-u User] -n Type:[User@]Node ... cdat access [-dF] [-u User] -f File ... Usage: cdat check -h cdat check [-d] Usage: cdat delete -h cdat delete -p PMR cdat delete Id Usage: cdat discover-nodes -h cdat discover-nodes [-a|-w] [-f File] -n Type:[User@]Node ... Usage: cdat init -h cdat init [-c [-g VGName] [-s FSSize]] [-d Directory] [-l LVName] [-u User] Usage: cdat list-nodes -h cdat list-nodes [-f File ...] Usage: cdat collect -h cdat collect [-gqv] [-i Id] [-p PMR] [-m Comment] [-u User] -t Type ... -n Type:[User@]Node ... cdat collect [-gqv] [-i Id] [-p PMR] [-m Comment] [-u User] -t Type ... -f File ... Usage: cdat show -h cdat show [-v] cdat show [-v] Id cdat show [-v] -p PMR cdat show [-v] -n [Host] Usage: cdat sub-command [options] Available sub-commands: init Initialize the repository show Display the content of the repository check Check consistency of the repository delete Remove collects from the repository discover-nodes Find LPARs or WPARs from a list of HMCs or LPARs list-nodes Display the list of configured nodes access Manage remote nodes authentication collect Collect data from remote nodes list-types Display the list of supported collect types archive Create a compressed archive of collects Collect %s does not have any associated directory. No collect found for id %s. No collect found for PMR %s. 0965-026: No matching collect found. 0965-027: No nodes to connect to. 0965-028: Password mismatch. 0965-029: Password cannot be less than 7 characters. Please enter a password for the collect user: Please enter a PMR number: PMR: %s Re-enter the collect user password: Remove collect %s from XML file?Remove collect %s and associated directory?Remove directory %s?Removing directory %s from the repository... See file %s for detailed status. Skipping invalid node %s. Unsupported node type %1$s, skipping %2$s. timezonetype0965-030: Unknown sub-command: '%s'. Updating %s. userThe collect user will be created with the same password on all nodes. Waiting for cleanup... yn (y/n) [n]: (y/n) [y]: Usage: cdat list-types -h cdat list-types [-v] List of available collect types: Repository: %s Local user: %s 0965-031: File %s has invalid permissions. Please fix it. It should be readable/writable by owner only. Checking user %s...Checking directory %s...Checking for SSH...found Checking for SSH keys...generated created Creating filesystem on existing logical volume %s. Creating logical volume %1$s in volume group %2$s...Checking XML file...not found 0965-032: Cannot switch to user %s. 0965-033: Directory %1$s already exists, please run '%2$s' to repair the repository. 0965-034: The cdat local user is not defined. Please, run 'cdat init' first. Cannot connect to %s. 0965-035: -d needs an absolute path. Usage: cdat archive -h cdat archive [-f File] -p PMR cdat archive -f File Id 0965-036: Cannot create README file. 0965-037: Cannot archive %s. 0965-038: Cannot compress %s. Compressed archive successfully created at %s. Repository repaired. Repository is valid. Another instance of the cdat command is running. Please wait until this instance terminates. mandatoryoptionaldefault=%spass-through options: %s Cluster Data Aggregation ToolCreate the RepositoryLocationLocal cdat userCreate a logical volume? Volume group Logical volume Size of logical volumeNo initializationThis operation cannot be performed ...You must create cdat repository first.Cancel and select "Create the Repository".Discover NodesNode typeHostnameFilename Write modeManage Remote NodesList the Remote NodesAdd a Remote NodeChange/Show Characteristics of a Remote NodeRemove a Remote NodeNode filenameType of nodeRemote user nameRemote nodeSelected Remote NodeNode to removeAdd a Remote Node and Initialize AccessDefault remote user nameInitialize Access to Remote NodesCollect Data from Remote NodesCollect namePMR numberCommentCollect type ParametersDisplay Repository ContentsVerbose mode?Ordered by node?Delete Collects from the RepositoryCheck Consistency of the RepositoryCorrect file if needed?List the Collect Typesno,yesRemote nodesArchive CollectsComment (if any - for the remote node)Manage Scheduled CollectsRemove a Remote Node and Suppress AccessSuppress Access to Remote NodesExtend file systems if space needed?List All Collects ScheduledSchedule a CollectChange/Show Characteristics of a Scheduled CollectRemove a Collect from the ScheduleMinuteHourDay of monthMonthWeekdayForce?Append,OverwriteSelected hostname not found Cannot rename hostname, already existing Type enter to continue. A value must be specified in the entry field for either "Node filename" or "Remote nodes". Cannot add hostname, already existing Unsupported user name Cannot add collect, already existing Selected collect not found Bad syntax in crontab time fields Creates and initializes the Cluster Data Aggregation Repository. The Cluster Data Aggregation Repository is where data collected from remote nodes is stored.Specifies the location where the Cluster Data Aggregation Repository will be created.Specifies the user name that will be used to run collects on the Cluster Data Aggregation master node. This user will be created if it does not already exist.Specifies whether a Logical Volume should be created to hold the Cluster Data Aggregation Repository.Specifies the name of the Volume Group where the Logical Volume should be created. It is useless if you do not want to create a logical volume.Specifies the name of the Logical Volume to create to hold the Cluster Data Aggregation Repository. It is useless if you do not want to create a logical volume.Specifies the initial size of the Logical Volume to create. It is useless if you do not want to create a logical volume. You can specify the size in Megabyte or Gigabyte by respectively adding M or G. Otherwise you specify the number of partitions. For example, type 500M for 500 MB, 3G for 3 GB, 100 for 100 PP. You can use m instead of M or g instead of G.Discovers logical partitions managed by a Hardware Management Console or Integrated Virtualization Manager, or workload partitions managed by a logical partition.Specifies the type of node (can be either HMC, VIOS or LPAR).Specifies the host name of the Hardware Management Console, the VIOS including an Integrated Virtualization Manager or the LPAR that manages workload partitions.Specifies the file name in which the list of nodes discovered will be stored.Specifies whether the list of nodes discovered should be appended to the specified file or if it should replace existing list of nodes. Nevertheless, in any case, a node is added only once in the file.Manages files containing list of nodes and initializes or suppresses access to remote nodes.Lists Remote Nodes from a file containing a list of nodes.Specifies the file name from which the list of nodes should be retrieved.Adds a Remote Node to a file containing a list of nodes.Specifies the file name to which the node should be added.Specifies the type of node to be added.Specifies the user name that should be used to connect to the node.Specifies the host name of the node to be added.Changes or Shows the Characteristics of a Remote Node from a file.Specifies the file name in which the node should be changed.Specifies the new type of node.Specifies the new user name that should be used to connect to the node.Specifies the new host name of the node.Removes a Remote Node from a file containing a list of nodes.Specifies the file name from which the node should be removed.Adds a Remote Node to a file containing a list of nodes and initializes access to this remote node. It creates a user on the remote node if neededRemoves a Remote Node from a file containing a list of nodes, suppresses authentication information on this remote node and possibly the corresponding remote user. It removes what has been previously set up by the access initialization operation on remote nodes.Specifies the node hostname of which properties should be changed.Pre-exchanges authentication information with remote nodes. This is necessary in order to avoid entering passwords during a collect. If needed, this operation creates the cdat user on the remote nodesSpecifies the remote user name for which authentication should be managed. This is used as the default user name if no user names are set in the specified file.Specifies the file name containing the list of nodes and users for which access should be managed.Performs collects on remote nodes.Specifies the user name that should be used to connect to the specified remote nodes. This is used as the default user name if no user names are set in the specified file.Specifies the file name containing the list of nodes and users on which to perform the collect.Specifies a name for the collect. If no name is specified, a default name will be generated. This can be used to overwrite the result of a previous collect.Specifies a PMR (Problem Management Record) number to associate with this collect. This can be used to group several collects together under the same PMR number.Specifies a comment describing the collect.Specifies that more status information should be displayed during the collect.Specifies the type of collect that should be performed. You can provide a list of types separated by commas.Specifies parameters for the collect. These parameters depend on the type of collect selected. To see the list of supported parameters, select the "List the Collect Types" menu item or select the "Collect type" entry field and press F4. If you provide a list of types, you can provide as many groups of parameters separated by commas.Displays the list of collects stored in the Cluster Data Aggregation Repository.Specifies the name of the collect for which information should be displayed.Specifies that only the collects with the specified PMR (Problem Management Record) number should be displayed.Specifies that more information should be displayed about collects. This will display for each collect the list of nodes on which the collects was performed.Specifies that collects should be displayed by nodes.Removes collects from the Cluster Data Aggregation Repository.Specifies the name of the collect to remove from the Cluster Data Aggregation Repository.Specifies the PMR (Problem Management Record) associated with the collects to remove from the Cluster Data Aggregation Repository.Checks and possibly repairs the structure of the Cluster Data Aggregation Repository.Specifies that inconsistencies found in the Cluster Data Aggregation Repository should be repaired. User will be asked for confirmation before any changes are made to the Repository.Displays the list of configured collect types. In addition to default collect types, user-specified collect types will be searched in the CDAT_TYPES environment variable.Specifies that collect type usages should be displayed.Specifies the list of nodes (separated by commas) on which to perform the collect. You can specify the list of node by selecting from a list. If the list is empty, the collect is performed on all nodes listed in the file specified by the "Node filename" field. Example: LPAR:root@mylpar,HMC:hscroot@myhmc,VIOS:padmin@myviosThe Cluster Data Aggregation Tool allows you to gather system dumps, traces, perfpmr data, etc from remote nodes onto a central location (called "Repository").Specifies the list of nodes (separated by commas) on which the specified user should be created. You can specify the list of node by selecting from a list. If the list is empty, user creation is performed on all nodes listed in the file specified by the "Node filename" field. Example: LPAR:root@mylpar,HMC:hscroot@myhmc,VIOS:padmin@myviosSpecifies comments associated with the remote node.UnusedSpecifies the list of nodes (separated by commas) for which authentication should be established. You can specify the list of node by selecting from a list. If the list is empty, authentication is established on all nodes listed in the file specified by the "Node filename" field. Example: LPAR:root@mylpar,HMC:hscroot@myhmc,VIOS:padmin@myviosSuppresses authentication information on remote nodes and possibly the corresponding remote user. It removes what has been previously set up by the access initialization operation on remote nodes.Specifies the list of nodes (separated by commas) for which authentication should be suppressed. You can specify the list of node by selecting from a list. If the list is empty, authentication is suppressed on all nodes listed in the file specified by the "Node filename" field. Example: LPAR:root@mylpar,HMC:hscroot@myhmc,VIOS:padmin@myviosIndicates whether you want the system to extend the repository file system if more space is needed during collect processing. YES instructs the system to extend the repository file system as necessary. NO instructs the system NOT to extend the repository file system. If you choose NO and the system runs out of disk space during processing, a system message displays and the collect cannot be completedCreates a compressed archive containing collected data for a given collect or PMR number. This can be used to send collected data off-site.Specifies the file name of the compressed archive. Notice that a ".tar.Z" suffix is appended to the file name.Specifies the name of the collect you want to archive.Specifies that only the collects with the specified PMR (Problem Management Record) number should be archived.Displays the list of scheduled collects recorded in the cdat user cron file.Adds a periodic collect in the cdat user cron file.Specifies a name for the collect. This name identifies the scheduled collect in the cdat user cron file.Specifies the minute(s) when the collect will be performed. You can specify a list of minutes separated by commas. Use "man crontab" for more explanations or examples.Specifies the hour(s) when the collect will be performed. You can specify a list of hours separated by commas. You can specify a range, two numbers separated by a dash. An * (asterisk) means all the hours of the day. Use "man crontab" for more explanations or examples.Specifies the day(s) in the month when the collect will be performed (from 1 to 31). You can specify a list of days separated by commas. You can specify a range, two numbers separated by a dash. An * (asterisk) means all the days of the month. Use "man crontab" for more explanations or examples.Specifies the month(s) when the collect will be performed. You can specify a list of months separated by commas. You can specify a range, two numbers separated by a dash. An * (asterisk) means all the months of the year. Use "man crontab" for more explanations or examples.Specifies the day(s) in the week when the collect will be performed (from 1 to 7). You can specify a list of days separated by commas. You can specify a range, two numbers separated by a dash. An * (asterisk) means all the days of the week. Use "man crontab" for more explanations or examples.Changes one or more attributes of a periodic collect recorded in the cdat user cron file.Specifies the list of nodes (separated by commas) on which to perform the collect. If the list is empty, the collect is performed on all nodes listed in the file specified by the "Node filename" field. Example: LPAR:root@mylpar,HMC:hscroot@myhmc,VIOS:padmin@myviosManages the cdat user cron file for periodic collects.Removes a periodic collect from the cdat user cron file.Displays the list of configured collect types. In addition to default collect types, user-specified collect types will be searched under the /var/adm/ras/cdat directory.Specifies whether this operation should be forced even if the node is already in hosts database.Specifies whether this operation should be forced even if the node is not in hosts database.