Table 1 and Table 2 outline the pdbx subcommands described in this chapter. Complete syntax information for all these subcommands is also provided under the entry for the pdbx command in Appendix A, "Parallel environment tools commands".
The debugger supports most of the familiar dbx subcommands, as well as some additional pdbx subcommands. In pdbx, command context refers to a setting that controls which task(s) receive the subcommands entered at the pdbx command prompt.
pdbx subcommands can either be context sensitive or context insensitive. The debugger directs context sensitive subcommands to just the tasks in the current command context. Command context has no bearing on context insensitive commands, which control overall debugger behavior, and are generally processed on the home node only. These include subcommands for setting help and other information, and ending a pdbx session.
You can set the command context on a single task or a group of tasks as described in Setting command context.
Table 1. Context Insensitive pdbx Subcommands
| This subcommand: | Is used to: | For more information see: |
| alias [alias_name string] | Set or display aliases. | Creating, removing, and listing command aliases |
| attach <[all | task_list]> | Attach the debugger to some or all the tasks of a given poe job. | "Attach mode" |
| detach | Detach pdbx from all tasks that were attached. This subcommand causes the debugger to exit but leaves the poe application running. | "Exiting pdbx" |
| dhelp [dbx_command] | Display a brief list of dbx commands or help information about them. | Accessing help for dbx subcommands |
| group <action> [group_name] [task_list] | Manipulate groups. The actions are add, change, delete, and list. To indicate a range of tasks, enter the first and last task numbers, separated by a colon or dash. To indicate individual tasks, enter the numbers, separated by a space or comma. | Grouping tasks |
| help [subject] | Display a list of pdbx commands and topics or help information about them. | Accessing help for pdbx subcommands |
| on <[group | task]> [command] | Set the command context used to direct subsequent commands to a specific task or group of tasks. This subcommand can also be used to deviate from the command context for a single command without changing the current command context. | Setting the current command context |
| quit | End a pdbx session. | Exiting pdbx |
| source <cmd_file> | Execute pdbx subcommands from a specified file.
| Reading subcommands from a command file |
| tasks [long] | Display information about all the tasks in the partition. | Displaying tasks and their states |
| unalias alias_name | Remove a command alias specified by the alias subcommand. | Creating, removing, and listing command aliases |
Table 2. Context Sensitive pdbx Subcommands
| This Subcommand: | Is used to: | For more information see: |
| delete <[event_list | * | all]> | Remove breakpoints and tracepoints set by the stop and trace subcommands. To indicate a range of events, enter the first and last event numbers, separated by a colon or a dash. To indicate individual events, enter the number(s), separated by a space or comma. | Deleting pdbx events |
| dbx <dbx_command> | Issue a dbx subcommand directly to the dbx sessions
running on the remote nodes. This subcommand is not intended for casual
use. It must be used with caution, because it circumvents the
pdbx server which normally manages communication between the user
and the remote dbx sessions. It enables experienced
dbx users to communicate directly with remote dbx
sessions, but can cause problems as pdbx will have no knowledge of
the communication that transpired.
| the online PE manual page for pdbx. This manual page also appears in Appendix A, Parallel environment tools commands. |
| hook | Regain control over an unhooked task. | Unhooking and hooking tasks |
| list [line_number | line_number, line_number | procedure] | Display lines of the current source file, or of a procedure. | Displaying source |
| load <program> [program_arguments] | Load a program on each node in the current context. This can only be issued once per task per pdbx session. pdbx will look for the program in the current directory unless a relative or absolute pathname is specified. | Loading the partition with the load subcommand |
| print <[expression | procedure]> | Print the value of an expression, or run a procedure and print the return code of that procedure. | Viewing program variables |
| status [all] | Display a list of breakpoints and tracepoints set by the stop and trace subcommands in the current context. If "all" is specified, all events, regardless of context are shown. | Checking event status |
| stop | Set a breakpoint for tasks in the current context. Breakpoints are stopping places in your program that halt execution. | Setting breakpoints |
| trace | Set a tracepoint for tasks in the current context. Tracepoints are places in your program that, when reached during execution, cause the debugger to print information about the state of the program. | Setting tracepoints |
| unhook | Unhook a task or group of tasks. Unhooking allows the task(s) to run without intervention from the debugger. | Unhooking and hooking tasks |
| where | Display a list of active procedures and functions. | Viewing program call stacks |
| <Ctrl-c> | Regain debugger control when some tasks in the current context are running. This causes a pdbx subset prompt to be displayed, which allows a subset of the pdbx function to be performed. | Context switch when blocked |