HP XP Racks - Manual (Page 301)

The following is an example of the coding in the file that defines the
information to be collected.
Figure 7-1 Coding Example of a File that Defines the Information to
be Collected
Rules for coding a file that defines the information to be collected
• Use an absolute path to specify a directory or file whose
information is to be collected. If you use a relative path to specify
a directory or file, that directory or file will be searched for only
within the directory in which the DLMgetras utility was executed,
and the files found will be collected.
• Do not specify a directory that contains the directory to which the
collected information is output. If you specify this directory, the
DLMgetras utility will run indefinitely.
• Lines beginning with the hash mark (#) are handled as comment
lines.
• If the hash mark (#) is encountered anywhere other than at the
beginning of a line, it is assumed to be part of the path name.
• Only one file or directory can be specified per line.
• The root directory (/) cannot be specified.
• When a directory is specified, the DLMgetras utility collects all the
files in that directory, including files contained in the directory's
subdirectories. If no files are found in a specified directory, the
utility does not perform file collection for that directory and does
not create a directory for it in the destination directory.
• Set up the specified file or directory so that it can be read by users
with root permissions. The DLMgetras utility can only obtain
information for a file or directory that can be read.
-h
Displays the format of the DLMgetras utility.
Note
• Because DLMgetras first stores error information in the specified output
directory before compressing, ensure that information collection areas
allocated are of adequate size.
• If the specified directory to which collected information is output already
exists, an overwrite confirmation message is displayed. Responding by
Utility Reference
7-7
Hitachi Dynamic Link Manager (for AIX) User Guide