1    /ABORT

    Marks the specified tasks for termination. Termination occurs
    at the next allowable point after a specified task resumes
    execution.

    For HP Ada tasks, the effect is identical to executing an Ada
    abort statement for the tasks specified and causes these tasks
    to be marked as abnormal. Any dependent tasks are also marked for
    termination.

    For POSIX threads threads, use the following command:

    PTHREAD tset -c thread-number

    You can get help on POSIX threads debugger commands by typing
    PTHREAD HELP.

    See the Guide to the POSIX Threads Library for more information
    about using the POSIX threads debugger.

2    /ACTIVE

    Makes the specified task the active task, which is the task that
    runs when a STEP, GO, CALL, or EXIT command executes. This causes
    a task switch to the new active task and makes that task the
    visible task. The specified task must be in either the RUNNING or
    READY state. When using /ACTIVE, you must specify one task.

    For POSIX threads programs or HP Ada on Alpha programs, use
    one of the following alternatives:

    o  For query-type actions, use the SET TASK/VISIBLE command.

    o  To gain control of execution, use a strategic placement of
       breakpoints.

    o  Use the PTHREAD tset -a thread-number command.

    You can get help on POSIX threads debugger commands by typing
    PTHREAD HELP.

    See the Guide to the POSIX Threads Library for more information
    about using the POSIX threads debugger.

3    /ALL

    Applies the SET TASK command to all tasks.

4    /HOLD

       /HOLD
       /NOHOLD (default)

    When the event facility is THREADS, use the
    PTHREAD tset -h thread-number or the PTHREAD tset -n thread-num
    command.

    Controls whether a specified task is put on hold. The /HOLD
    qualifier puts a specified task on hold.

    Putting a task on hold prevents a task from entering the RUNNING
    state. A task put on hold is allowed to make other state
    transitions; in particular, it can change from the SUSPENDED
    to the READY state.

    Putting a task on hold prevents a task from entering the RUNNING
    state. A task put on hold is allowed to make other state
    transitions; in particular, it can change from the SUSPENDED
    to the READY state.

    A task already in the RUNNING state (the active task) can
    continue to execute as long as it remains in the RUNNING state,
    even though it is put on hold. If the task leaves the RUNNING
    state for any reason (including expiration of a time slice, if
    time slicing is enabled), it will not return to the RUNNING state
    until released from the hold condition.

    You can override the hold condition and force a task into the
    RUNNING state with the SET TASK/ACTIVE command even if the task
    is on hold.

    The /NOHOLD qualifier releases a specified task from hold.

    You can get help on POSIX threads debugger commands by typing
    PTHREAD HELP.

    See the Guide to the POSIX Threads Library for more information
    about using the POSIX threads debugger.

5    /PRIORITY

       /PRIORITY=n

    When the event facility is THREADS, use the PTHREAD
    tset -s thread-number command.

    Sets the priority of a specified task to n, where n is a decimal
    integer from 0 to 15. This does not prevent the priority from
    later changing in the course of execution, for example, while
    executing an Ada rendezvous or

    Sets the priority of a specified task to n, where n is a decimal
    integer from 0 to 15. This does not prevent the priority from
    later changing in the course of execution, for example, while
    executing an Ada rendezvous or POSIX threads synchronization
    event. This qualifier does not affect a task's scheduling policy.

    You can get help on POSIX threads debugger commands by typing
    PTHREAD HELP.

    See the Guide to the POSIX Threads Library for more information
    about using the POSIX threads debugger.

6    /VISIBLE

    Makes the specified task the visible task, which is the task
    whose call stack and register set are the current context for
    looking up symbols, register values, routine calls, breakpoints,
    and so on. Commands such as EXAMINE are directed at the visible
    task. The /VISIBLE qualifier does not affect the active task.
    When using /VISIBLE, you must specify one task.