(Subsystem 165)

This is an invalid address or caller has insufficient capabilities to access it.

The address validation routines detected an error while checking the indicated address.

Check the address. If invalid, pass a valid address. Remember to make sure the space ID for long pointers is correct. If additional capabilities are required, increase caller capabilities or reduce protection on target address.

This is an invalid BREAKPOINT INDEX; it is out of range for valid BREAKPOINTS.

The breakpoint index is out of range of valid breakpoints.

Provide a valid breakpoint index.

The SINGLE STEP COUNT is invalid.

A negative single step value was passed.

Provide a positive value.

An NM BREAKPOINT (not in the DEBUG TABLE) is at that address.

An NM breakpoint was found at the indicated address. Since the breakpoint was not found in the system debug tables, it must be a breakpoint from some other subsystem or placed in the code by the programmer.

Pick another location to set a DEBUG breakpoint since DEBUG will not set a breakpoint on another breakpoint.

The BREAKPOINT INDEX could not be found in the BREAKPOINT TABLE.

The breakpoint index specified is not in the breakpoint tables.

List the current breakpoints and use an index of an existing breakpoint.

A BREAKPOINT already exists at the indicated address; can't set another.

The caller tried to set an NM breakpoint where they had already set one. Complete information about the breakpoint existing at the location is returned in the INFO parameter.

Pick a different place to set the NM breakpoint. Delete the existing breakpoint and then set the new one.

The BREAKPOINT is owned by another process; can't clear it.

The caller tried to delete an NM breakpoint which he did not own.

Specify an NM breakpoint which the caller set. Grant the user PM capabilities so they may delete other people's breakpoints.

The DATA BUFFER is too small to hold the indicated number of bytes.

The user requested a data transfer that is larger than the size of the passed buffer.

Increase the size of the buffer or request less data.

A CM BREAKPOINT already exists at that address (it's not in DEBUG TABLES!)

A CM breakpoint was found at the indicated address. Since the breakpoint was not found in the system debug tables, it must be a breakpoint from some other subsystem or placed in the code by the programmer.

Pick another location to set a DEBUG breakpoint since DEBUG will not set a breakpoint on another breakpoint.

The procedure could not find the CM BREAKPOINT in the BREAKPOINT TABLE; can't clear it.

The CM breakpoint index specified is not in the breakpoint tables.

List the current CM breakpoints and use an index of an existing breakpoint.

There is a BREAKPOINT already set there.

The caller tried to set a CM breakpoint where they had already set one. Complete information about the breakpoint existing at the location is returned in the INFO parameter.

Pick a different place to set the CM breakpoint. Delete the existing breakpoint and then set the new one.

The END ADDRESS is bigger than START, or SIDs don't match in DATA BREAK ADDRESS.

The caller specified a range of address that cross a space boundary or is not an ascending range.

Specify a correct address range.

The DATA BREAKPOINT INDEX could not be found in the BREAKPOINT TABLE.

The DATA breakpoint index specified is not in the breakpoint tables.

List the current DATA breakpoints and use an index of an existing breakpoint.

A DATA BREAKPOINT already exists somewhere in the specified range; can't ARM.

The caller tried to set a DATA breakpoint where they had already set one. Complete information about the breakpoint existing at the location is returned in the INFO parameter.

Pick a different place to set the DATA breakpoint. Delete the existing breakpoint and then set the new one.

The DATA BREAKPOINT is owned by another process; can't clear it.

The caller tried to delete a data breakpoint which he did not own.

Specify a DATA breakpoint which the caller set. Grant the user PM capabilities so they may delete other peoples' breakpoints.

The TARGET PIN is invalid or cannot be found in the DEBUG TABLES.

The system breakpoint PIN SYS_BP_PIN was specified and is invalid for the desired function. Specified PIN is not being monitored by the caller. Specified PIN does not exist at all in the debug tables.

Provide a correct PIN number.

The procedure could not find the PIN in BREAKPOINT TABLE; can't ARM LOWER PRIV trap.

A process attempted to stop at a place for which it had insufficient capabilities. An attempt was made to arm the LOWER PRIV trap, stopping the process at the proper time. The trap could not be armed.

None.

No STATE found for the indicated PIN; can't ARM the LOWER PRIV trap.

A process attempted to stop at a place for which it had insufficient capabilities. An attempt was made to arm the LOWER PRIV trap, stopping the process. The trap could not be armed.

None.

The maximum number of BREAKPOINTS for your process has been reached.

Each debug user is allowed a maximum fixed number of breakpoints. That limit has been reached for the calling process.

Delete some existing breakpoints.

You are not a DEBUG user (see the documentation on how to use DEBUG routines).

The caller has not identified himself as a debug user by calling the debug_user_setup routine.

Call the debug_setup_user procedure.

You are not monitoring that PIN; can't REMOVE/DISARM event.

Probable cause is corruption of the internal debug tables.

Kill all processes using DEBUG and retry the desired operation. Reboot the system. Call your Hewlett-Packard Representative if the problem persists.

Your user must have PRIV capabilities for this function.

A request to perform an operation which required the user to hav PM capabilities was issued. Possibilities include: writing register data is not allowed without PM; resuming execution at a new location requires PM.

Grant the user PM capability.

You may not resume that PIN; someone else has control over it.

Same as for Message Content.

Provide a correct PIN number.

DEBUG cannot be run on this system; DEBUG system start up code failed.

Debug was not successfully initiated at system boot time. It is not available.

Reboot the system. If the problem persists, call your Hewlett-Packard Representative.

The procedure could not locate the DEBUGGER GLOBAL DATA area.

DEBUG could not allocate storage to maintain its own local data storage. This could be due to lack of disk space for virtual memory.

Verify that there is free virtual memory disk space.

The actual INSTRUCTION for that address is not in the BREAKPOINT TABLE.

The indicated address does not exist in the debug tables as an address where an NM breakpoint is set.

None.

The PIN is not accessible to you (not a CHILD or you don't have PRIV mode).

A PIN number was specified that is not a child of the caller.

Grant the caller PM capabilities. Use a PIN that is a child of the caller.

The procedure could not find the STATE INFORMATION (ISM) for the indicated process.

An interrupt marker (ISM) for the indicated PIN could not be found in the debug tables. The ISM is needed to alter a process's register state and to arm the branch taken trap.

Make sure you are using the correct PIN number.

The procedure could not allocate the object needed to store DEBUG GLOBAL DATA.

VSM returned a bad status from a create_object call made while initializing the debugger.

Make sure there is sufficient free disk space for virtual memory.

This is an invalid PIN number; it is out of range for the valid PINS.

Same as message content.

Provide a valid PIN.

This address is inaccessible to you; insufficient privilege or access rights.

The VSM "probe" routine returned an error status. This is caused by an undefined address or an address to which the caller does not have access.

Make sure the address is valid.

The PIN was not found in the DEBUG TABLES; can't RESUME the process.

While trying to resume a process at a newly specified address, the interrupt marker for the process could not be located in the debug tables.

Call the resume routine without specifying a new resume address.

The PIN is invalid; you may not specify your own PIN.

The caller's PIN was specified as the target of the request function.

Specify a PIN other than your own.

SINGLE STEPPING is currently controlled by another PIN; can set SS counter.

An attempt was made to single step a process whose single step counter is controlled by another process.

Do not single step the process or try later when the current owner of the single step counter is finished with it.

The PIN was not found in the DEBUG TABLES; can't set SS counter.

While attempting to single step a process, the process's interrupt marker could not be found in the system debug tables.

None.

The DEBUG TABLES are full; try again later.

The global system debug table is full.

Wait for the number of debug users to decrease. Delete breakpoints, turn off traps (all these free table space).

The indicated PIN does not exist.

The indicated PIN did not exist when the request was made.

Specify a valid PIN.

A compiler generated TRACE BREAKPOINT is already set at that location.

While attempting to set an NM breakpoint, one of several compiler-generated breakpoints was found at the indicated address.

Choose a different address at which to set the breakpoint. Recompile the program without the option that caused the special breakpoints to be inserted. Relink the program, specifying the ";NODEBUG" option.

The TARGET PIN is invalid for the specified TRACE event.

The system breakpoint PIN was specified as the target of the trace event request.

Use a PIN other than the system breakpoint PIN.

The TRACE event is currently owned by another process; can't ARM it.

The caller tried to set a trace event that has already been set.

None.

The TRACE event is currently owned by another process; can't DISARM it.

The caller tried to disarm a trace event which he did not own.

Specify a trace event which the caller set. Grant the user PM capabilities so they may disarm other peoples' trace events.

Invalid TRAP ID.

An unknown or unsupported trap ID was specified.

Use a valid trap ID.

The trap is not currently ARMED.

A request was made to disarm a trap that was not armed.

Specify a trap that is armed.

The PIN was not found in the DEBUG TABLES; can't ARM the trap.

While attempting to arm a trap, the interrupt marker for the specified process could not be found in the debug tables.

None.

WARNING** The PIN was not found in the DEBUG TABLES; can't clear T bit in PSW for PIN.

While attempting to disarm a trap, the interrupt marker for the specified process could not be found in the debug tables.

None.

This trap is currently owned by another process; can't ARM it.

The caller tried to set a trace event that has already been set.

None.

This trap is currently owned by another process; can't DISARM it.

The caller tried to disarm a trace event which he did not own.

Specify a trace event which the caller set. Grant user PM capabilities so they may disarm other peoples' trace events.

You cannot set BREAKPOINTS on GATE instructions; sorry.

The address specified for an NM breakpoint corresponds to a precision architecture gateway page. Breakpoints may not be set on gateway pages.

None.

Dual BPs within the same node must have identical count values.

Another CM breakpoint was set that has a corresponding translated NM breakpoint which maps to the same NM node point. In such situations, the breakpoint "COUNT" must be identical.

Provide the same COUNT value as the existing breakpoint at the node point. Delete the existing breakpoint before trying to set this one.

Dual BPs within the same node must have identical comment strings.

Another CM breakpoint was set that has a corresponding translated NM breakpoint which maps to the same NM node point. In such situations, the breakpoint COMMAND STRING values must be identical.

Provide the same COMMAND STRING value as the existing breakpoint at the node point. Delete the existing breakpoint before trying to set this one.

An escape occurred while reading REGS from the ISM.

While trying to read/write register values to an interrupt marker, an expected error was detected. The result of the operation is undefined.

None.

Accessing NL.PUB.STS requires that you are in PRIV mode.

An attempt was made to access the system NL by a user without PM capability.

Grant the user PM capability.

Accessing SL.PUB.SYS requires that you are in PRIV mode.

An attempt was made to access the system SL by a user without PM capability.

Grant the user PM capability.

The actual CM INSTRUCTION for that address is not in the breakpoint table.

The indicated address does not exist in the debug tables as an address where an CM breakpoint is set.

None.

A DATA BREAK TRP occurred which DEBUG did not arm.

Someone else has set a trap bit on a page in the page table.

None.