Debugging commands

Use debugging commands to view queues and process stacks.

Table 1.
Command name Action Syntax
debug postmortem export The debug postmortem export command exports the postmortem archive to the FTP or SFTP Server you specify.
The Management server does not require that you specify an export file name; however, as a best practice, you should include the Management server serial number, date, and timestamp. If you do not specify an export file name, the Management server exports a file named postmortem.tar.gz.
Note: Do not use reserved words in the user name, host name, or file name. Reserved words include: ftp, sftp, postmortem, debug, export, ibm, port, user, and file.
 FTP Syntax: debug postmortem export ftp <hostname> [port <number>][user <user>][file <filename> ]
where:
  • hostname is the name of the FTP Server.
  • number is the port number to use to connect to the FTP Server.
  • user is the username that is used to log in to the FTP Server.
  • filename is the name of the file that stores the postmortem archive.
For example:
  • debug postmortem export ftp 192.168.1.2 user user1 file logs/B2XXW56_04152005_172341.tgz
  • debug postmortem export ftp ftpserver.yourcompany.com user user1 file logs/B2XXW56_04152005_172341.tgz
SFTP Syntax: To export the postmortem by using an SSH File Transfer Protocol, use the following SFTP syntax.
Note: When you export a postmortem file to an SFTP server, you must specify a user name. Anonymous logins are not allowed with SFTP.
debug postmortem export sftp <hostname> [port <number>] user <user> [file <filename> ]
where:
  • hostname is the name of the SFTP Server.
  • number is the port number to use to connect to the SFTP Server.
  • user is the username that is used to log in to the SFTP Server.
  • filename is the name of the file that stores the postmortem archive.
For example:
  • debug postmortem export sftp 192.168.1.2 user user1 file logs/B2XXW56_04152005_172341.tgz
  • debug postmortem export sftp ftpserver.yourcompany.com user user1 file logs/B2XXW56_04152005_172341.tgz
debug postmortem generate fulllogs The debug postmortem generate fulllogs command generates a postmortem archive of all the Management server logs, which includes new logs in addition to archived logs, and possibly several stacks that are generated by previously running the debug show stack command.

The postmortem archive remains on the Management server until you reissue the command. When you issue this command, the Management server generates a new archive that overwrites the previous postmortem archive.

 debug postmortem generate fulllogs
debug postmortem generate newlogs The debug postmortem generate newlogs command generates a postmortem archive of all the latest Management server logs and possibly several stacks that are generated by previously running the debug show stack command.

The postmortem archive remains on the Management server until you reissue the command. When you reissue this command, the Management server generates a new archive that overwrites the previous postmortem archive.

 debug postmortem generate newlogs
debug show stacks The debug show stacks command displays current runtime stack traces. debug show stacks
debug system Use the debug system command to start and stop the Management server run time. When you issue the debug system stop command, all running orchestration jobs are canceled and the Management server does not process any new orchestration jobs. debug system {start|stop }
debug tail file The debug tail file command displays log file contents as they are added to the log. debug tail file<filename>
debug top The debug top command dynamically displays process status. debug top