18.6 Notes
-
You must have specified the ADBDIR environment variable before you can execute the adbinfoget command.
-
The adbinfoget command can be executed regardless of the status of the HADB server. However, to execute the command with the -g option specified, make sure that the HADB server is running.
-
If the adbinfoget command terminates abnormally, a work directory (adbinfoXXXXXXXXXX, where XXXXXXX is the date and time when the adbinfoget command was executed) might remain under the troubleshooting-information files output directory. If this occurs, use the OS's rm command to delete the work directory.
-
OS commands are executed as an extension of the adbinfoget command. If execution of such an OS command fails, an error message is output to the standard error output. In such a case, check the error message, eliminate the cause of the error, and then re-execute the adbinfoget command.
-
HADB commands (such as adbls commands) are executed as an extension of the adbinfoget command. If execution of such an HADB command fails, an error message is output to the standard error output or to a message log file. In such a case, check the error message, eliminate the cause of the error, and then re-execute the adbinfoget command.
-
Do not execute the adbinfoget command while the adbinit command is executing. If the adbinfoget command is executed at such a time, any command that is executed as an extension of the adbinit or adbinfoget command might terminate abnormally, or invalid troubleshooting information might be collected.
-
Depending on the information specified in the server definition, it might take a very long time to collect the detailed version of the troubleshooting-information files. To cancel collection of troubleshooting-information files that is underway, terminate the adbinfoget command's process by, for example, pressing the Ctrl+C keys or using the OS's kill command. You can then execute the adbinfoget command with the -l option specified to collect only the mail and light versions.