This chapter documents messages generated by the SAS/C Debugger. Each message contains the message text, an explanation of the message, system information, and the action needed to correct the error, if applicable.
Debugger diagnostic messages have the following form:
LSCDmessage-number message-textFor invalid syntax messages, see SAS/C Debugger User's Guide and Reference, which contains descriptions of the commands that are supported by the debugger. The SAS/C Debugger help system also provides brief descriptions of the commands.
An invalid command name was specified. (Enter ? for a list of valid command names).
The argument specified for the ON/BREAK/TRACE/IGNORE/QUERY command is not valid.
ON expects a single command or a command list within braces.
on command was issued with more than one deferred command
without braces.
Section-name and ) should follow (.
The function-name or section-name argument should be "calls", "entry", "return", "*" or a line-number range.
on command was entered. The syntax begins
on name [ calls | entry | return | * | line-number ]
There is invalid text, "text", after the end of the when clause.
when clause was entered with text after the
expression argument.
The command command without arguments is only valid in an ON command list. The command is ignored.
on command where
command values include break and trace.
The expression specified is incomplete.
whatis command was issued, but the expression specified
was not complete.
"keyword" is not a valid keyword for the command command.
| Command | Keywords |
auto |
cmacros | nocmacros,
cxx | nocxx,
dumpabs | nodumpabs,
echo | noecho,
exececho | noexececho,
extname | noextname,
id | noid,
japan | nojapan,
linesize, list | nolist,
nullptr | nonullptr,
wrap | nowrap |
config |
file, save |
log |
append, capture, file, start,
stop |
set |
search, cache |
name-type name has been truncated to length characters.
install, define, or
undefine command was issued that specified
either a user command,
an EXEC or CLIST, or a macro with a name that was too long.
User commands have a
limit of 40 characters and EXECs, CLISTs, macros have a limit
of 8 characters.
End of range (end-of-range) cannot be less than start (start-of-range).
drop, enable, or disable command was entered,
but the operands
specified, start-of-range:end-of-range with end-of-range less than start-of-range, are not supported.
Invalid TYPE/cast specified.
An integer must follow the COUNT keyword.
on command was issued with the count clause,
but count was
not followed by an integer.
The syntax specified for the command command is not valid.
install, drop, enable, disable,
monitor, print, auto, config,
define, exec, percent (%), help,
undefine, system, browse,
log
command has not been installed as a user command. It already exists.
install command command was issued, but command already exists.
End-of-input occurred before continuation was completed.
Logical input line cannot exceed 312 characters - input discarded.
An invalid TYPE/cast was specified: a right parenthesis is missing.
type or
cast expression, invalid syntax was found.
Either a right parenthesis or a colon was missing.
A length of 0 may not be specified as the number of bytes to be DUMPed.
dump command was issued that specified a length of zero.
There is an invalid symbol in the specified list.
Only a non-zero number of bytes may be specified.
copy command was issued that either
did not specify the number
of bytes, or specified zero bytes to copy.
The when clause specified is not valid.
on command was issued that specified an
invalid when clause.
There is invalid text, "text", after the end of a valid expression.
when expression was specified that had extra text.
Nested braces are not allowed in a list.
Only plain types and enum types can be specified with a value list.
COPY command was entered, but a plain type or
enum type was not
specified with a value list.
Missing function-name, section-name, or hook / event specification.
Continue input line ...
unsigned/signed float is an invalid type.
unsigned or signed float
type was found.
unsigned/signed double is an invalid type.
unsigned or
signed double value was found.
The following input in the buffer has been discarded: input
An invalid command name was specified.
A range may not be specified in full-screen mode.
list command was issued that specified a line
number range, but
only a starting line is allowed in full-screen mode.
The command command without parameters is invalid.
auto, config,
window, or log command was issued without parameters.
A section-name must follow a '('.
list command was entered with an
open parenthesis. This indicates
the specification of a section-name, but a
section-name
was not found.
A ')' must follow a section-name.
list command was issued with an
open parenthesis and a section-name, but a closing parenthesis
was not found.
An integer or '*' must follow a function-name or a parenthesized section-name.
list function-name | (section-name) command was
issued, but it was not followed by a line number
specification.
A ':' must follow an integer if a line-number range is to be specified.
list command was issued and was
followed by another number.
If a line number range was desired, it must be specified with
a colon between the starting line number and the ending line
number. Line number ranges are used only in line mode.
An integer or a signed positive integer must follow a ':'
list command was issued that specified
a starting line number followed by a colon. The debugger
expects a line number range, and an ending line number
must be specified after the colon. Line number ranges are used only
in line mode.
An integer must follow a '+' or a '-'
list command was specified with
starting line number followed by a colon and
then either a plus sign or a minus sign.
An integer must
follow the sign specification to indicate a
range of lines.
This form of the
list command is only used in line mode.
A signed positive integer must follow a ':'
list command was issued with a line range
specification that gave a positive start-of-range
and a negative end-of-range.
Since the start-of-range is
positive, the end-of-range must be positive also.
A signed integer must follow a ':'
list command was issued with a line range
specification that gave a negative start-of-range, but
it did not use a signed integer for the end-of-range.
Since the start-of-range was specified as a signed
integer, the end-of-range must also be a signed integer.
The first argument of the LIST command is invalid.
list command was entered with invalid arguments.
A line number of 0 is invalid.
list 0 command was issued, but the first line
in a file is 1, not
zero.
The command command is not supported under .
%),
config, dbinput, dblog,
keys, transfer, watch, and window.
Record read from DBGIN longer than 256.
DBGIN is greater than 256.
Identifier truncated to size characters.
The following input has been discarded: line
Cannot PRINT "variable" as the dimension of the array is not available.
print command was entered with the array variable variable,
but the dimension was not specified.
A comma is missing or there are too few function arguments.
A right parenthesis is missing or there are too many function arguments.
A left parenthesis must follow the function name.
A function name cannot be obtained: please supply it.
The function-name / signal-name has been truncated to 8 characters.
hook command was issued, and the specified name has
been truncated to 8 characters.
The config file can only be changed if the configuration is being saved.
Y.
The command command cannot be specified in the profile.
abort drop on undef auto enable query user break help set window config ignore system define install trace disable log rsystem
%) commands
?) commands
Command's arguments, if any, are not processed.
End of profile/file: an incomplete ON command has been discarded.
on command was entered during debugger
initialization.
The ON command has been discarded.
on command failed.
The command command can only be issued from a Rexx exec or Clist.
dbinput and dblog commands can only be
issued from an EXEC or
CLIST.
Prompt length may not exceed "prompt-length" characters.
dbinput command was issued that specified a prompt, but that
prompt string was longer than prompt-length.
The DBINPUT command gets input from the terminal when the debugger is prompting for terminal input.
dbinput command has been encountered and the debugger is
is now waiting for input.
Valid RESUME must be followed by no parameters, a function-name, a non-zero line-number, or both.
resume command was issued with invalid parameters.
Key definition text exceeds maximum allowed.
keys command was entered
but the definition text is greater than the limit.
A TRANSFER command without arguments is ignored.
transfer command was issued, but arguments are required.
The "signal"/"signals" keyword can only be specified with IGNORE.
signal keyword was specified on a
hook or query command, but it
is only supported on an ignore command.
Invalid syntax specified. Valid syntax is "IGNORE SIG.... signal"
ignore command was issued.
Only an integer may follow a STEP or CONTINUE command.
step or continue command was
issued with a non-integer
argument.
Unable to open an input file to the terminal - DBINPUT fails.
dbinput command was encountered, but the debugger was
unable to open the terminal input file.
dbinput ends without obtaining user input.
The only valid prefix command is 'd' to drop a watch.
d was entered on a line that
had a watch.
A section-name cannot be greater than 7 characters.
Out of memory - command(s) ignored.
Out of memory - scrounging around, end ASAP.
malloc storage failed. The debugger is
now using a limited number of preallocated buffers.
Out of memory - debugger file cannot be read.
An invalid symbol follows the EXIT command.
exit command was entered with a keyword operand that was
not nodrop.
The exit command is ignored.
An invalid keyword has been specified to the STORAGE command.
storage command was entered with an invalid keyword.
Unable to read from the terminal - DBINPUT fails.
dbinput command was encountered, and the input terminal
file was successfully opened, but the debugger was unable
to read from the terminal.
dbinput ends without obtaining user input.
Missing/invalid LINESIZE value.
auto command was issued with an invalid linesize
value.
Continue ON command list definition...
on command has been entered, but is not complete.
Enter the rest of the command.
The expression specified is invalid.
A "=" must separate the source from the target in an ASSIGN command.
assign command was issued with an inappropriate equals sign.
The format is
ASSIGN var=value
A "," must separate the operands of the COPY command.
copy command must be
separated with commas.
An invalid delimiter follows a valid command - the command is not executed.
assign, copy, or
return statement
was entered with trailing
characters.
The syntax specified for the function call is not valid.
The string is too long or is not terminated.
EXEC / CLIST variable name is longer than 256 characters.
The Termin window is not wide enough for the prompt - prompt truncated.
prompt command was issued, but the Termin window is
not wide enough to display the prompt text.
The prompt is truncated.
End of line number range cannot be less than the start.
Could not set desired scope.
scope command was entered, but the specified scope is not
in the current call path.
# followed by a null / undefined macro name.
A format specification may not be specified with this TRANSFER keyword.
transfer command was issued with an invalid format.
Acceptable formats include: offset,
address, value, or lineno.
A LOG file has not been specified. Logging has not been turned on.
log start command was issued, but a log file had not
been specified.
log file command.
Right bracket does not follow valid subscript.
Out of memory - overwriting debugger memory, end ASAP!!!
malloc memory failed for a request that is
larger than the preallocated debugger memory pool.
Invalid text follows valid KEYS keyword.
keys command was issued followed by
invalid text.
Invalid PF key number: valid numbers are 1-24.
keys command was issued with an invalid
PF key number. PF keys are limited to
the range 1-24.
Syntax is: KEYS DEFINE n "text".
keys command was issued with an invalid syntax.
Cannot drop a non-existent watch.
drop command was issued for a line that does not have a
watch.
Invalid syntax for color/attribute specification.
window color command was
issued with an invalid color specification.
The Command, Log, Source, and Status windows may not be closed.
window close command was issued for a window that may not
be closed.
This command is valid only in full-screen mode.
browse command was issued, while in line mode.
The WINDOW subcommand "subcommand-name" may not be specified in the profile.
window subcommand-name command was issued in the profile, but this
subcommand is not supported from the profile.
Placeholder replacement not successful.
expr
command. Is is usually accompanied by LSCD124, LSCD125, or
LSCD126.
Placeholder replacement not successful: valid expression not found.
Placeholder replacement not successful: input buffer overflow.
Commands to continue execution may not be issued when the window-name window is in this state.
continue, step,
go, runto, resume, and goto.
This command may not be issued when the window-name window is in this state.
exec, and window off.
One or more missing right parentheses assumed to complete expression.
This WINDOW subcommand may not be specified in the configuration file.
window command was found in a configuration file, but the
specified subcommand can not be issued from this file.
Only KEYS/WINDOW commands may be specified in the configuration file.
keys or window command was found.
This CONFIG subcommand may not be specified in the profile.
window config command was found while parsing the profile.
Processing of the profile continues.
The config file command can be issued from a PROFILE; however,
a window config command is not legal in a PROFILE.
The cursor is not in any window.
The cursor is not in valid window area.
The extracted line is too long.
A maximum of 40 watches is permitted.
watch command was entered, but the maximum number of defined
watches is 40.
A format cannot be specified for "dump" style watches.
watch command was issued that specified
dump, but it also
specified a format. This is not supported.
The subcommand-name subcommand may only be specified in the profile.
window subcommand-name command was issued that can only be specified
in the profile: intercepts, memory, or config.
The format specification is invalid or causes a buffer overflow.
The debugger is entered due to signal signal-name, ABEND code code.
RESUME may be issued only when the program is stopped at either a line hook or an epilog hook.
resume command was issued, but this can be issued only
on a function line or a function return, an exit, or at a line that a
user-supplied break caused the program to stop.
Cannot RESUME. explanation
resume command was issued to resume in a function that
is not in the current calling stack.
Unable to locate line within specified function. Not RESUMEd.
resume function-name line-number command was issued,
but the
specified
line number does not appear in the specified function.
Unable to locate line within current function. Not RESUMEd.
resume line-number command was issued, but the specified
line number does not appear in the current function.
Writing to storage report output file file-name. error-number
Return code of SYSTEM command: return-code.
system command command was issued, but the command returned a
non-zero return code return-code.
Debugger forcing program termination.
There is insufficient memory for the debugger to start up.
Debugger unrecoverable internal error.
Debugger recoverable internal error. Traceback follows:
Not enough functions in calling sequence. Enter WHERE to display traceback.
Save areas overlaid - traversal of calling sequence stopped.
Cannot evaluate expression. expression
WHATIS does not support this type.
whatis command was entered for an unsupported type.
whatis
only supports: constants, arithmetics, classes, bit fields,
enumerations, pointers, arrays, addresses, memory pointer,
pointers to characters, references, and functions.
message-text
message-text describes the error.
Cannot create debugger temporary file.
Debugger temporary file may have run out of space.
The debugger allocates a temporary file during debugger execution. When debugging large programs, it may be necessary to increase the size of this temporary file. Under OS/390, to increase the size of the file, before invoking the debugger, allocate a file with a DDname of SYSTMPDB. An example follows:
ALLOC F(SYSTMPDB) NEW SPACE(100) TRACKS UNIT(VIO)Under CMS, allocate a bigger read-write minidisk.
Cannot evaluate WHEN condition "WHEN-condition". message-text Debugger will BREAK. ON commands, if any, are not executed.
when condition has been encountered.
Execution stops and any specified on commands are ignored.
Cannot find function "function-name" in file "file-name".
Message buffer overflowed while processing expression.
No debugger macro variable defined for "macro-name".
define macro-name was issued, but there is not a macro
named macro-name.
Macro redefinition. Old definition was: old-macro-definition.
define macro-name "new-macro-def" was entered.
macro-name already existed with a definition of
old-macro-definition.
The previous macro definition is replaced by the specified
definition.
No debugger macro variable defined for "macro-name".
undef macro-name was issued, but there is not a macro
named macro-name.
TRANSFER not performed due to a memory access exception.
transfer command failed due to a memory access exception.
Cannot evaluate expression. expression
transfer command was entered with an
invalid expression specified.
"variable" is not a scalar: cannot TRANSFER.
transfer command was issued, but the specified variable is
not scalar.
TRANSFER (DUMP / STR) expression should be of pointer type.
transfer, variable, dump, or str
command was issued, but the expression specified was not a pointer.
TRANSFER (DUMP / STR) string too long - insufficient memory.
transfer, dump, or str command was issued, but
the expression specified was too long.
TRANSFER not performed: REXX/CLIST variable name "variable" or value "variable" is invalid.
transfer command was issued, but either the specified
REXX or CLIST variable name or the value is invalid.
TRANSFER not performed: REXX/CLIST environment not active.
transfer command was issued, but there was no REXX or
CLIST exec running.
TRANSFER not performed: environment does not have support for TSO CLIST variable interface.
transfer command was issued, but the execution environment
does not have support for the CLIST variable interface.
TRANSFER not performed: (execshv) code return-code.
transfer command was issued, but
execshv returned a non-zero
return code return-code.
TRANSFER not performed. explanation
transfer command was issued, but it was not performed, as indicated
by explanation. Where explanation is one of the following
strings:
"The variable name variable was not found."
"" accompanied by LSCD0163
"Not enough memory to complete operation."
"C library function execshv, internal error."
"" (null string)
Storage storage-begin:storage-end freed. Monitor(s) dropped:
Load module module-name unloaded. Monitor(s) dropped:
Cannot evaluate "expression". description
monitor command was issued, but the specified expression
could not be evaluated because of description.
This type of expression cannot be monitored.
monitor command was issued specifying an expression that
cannot be monitored. The expression must evaluate to an arithmetic,
class variable, a bit-field, an enumeration, or pointer.
The debugger profile "profile-name" execution failed, return code return-code. error-number
System REXX interface failed. error-text
Cannot process EXEC command - not interactive.
Cannot process EXEC or % command - not interactive.
EXEC command failed. Return code: code
EXEC or % command failed. Return code: code
Return code: code. Future invocation of CLISTs/EXECs may not work.
Line was too long and discarded: text...
Unable to open debugger input file.
Ddname "DD-code" not allocated. Enter "DD-code" data set names.
Ddname "DD-code" not allocated.
Unable to open debugger log file. See preceding runtime messages for details.
log append command was entered, but for the
log file failed to open.
Cannot list source. explanation
list command was issued, but the source could not be listed.
The explanation should give a description of the problem encountered.
Cannot scroll back line-count lines - scrolling to the top.
line line of range is set to 1.
list command was issued with invalid start or end values.
The described range value is set to 1. line is First or
Last.
No listing - last line of range (last-line) less than first line of range (first-line).
list command specifying a range was issued
but the last line was less than the first line.
The last line of a range must be greater than the first line of a range.
Source file "file-name" is empty.
*** End of source ***
End of source on line line-number.
list command was issued that specified a starting line greater than
the last line of the file, line-number.
Ignoring member member-name specified in DBGSRC definition.
The debugger file for this compilation is not available - cannot list source.
list command was issued
(perhaps implicitly on entry to a function),
and the debugger file could not be found.
set search commands that locate
the debug and source files. Then, issue the list command
to indicate to the debugger that the debug file and the source file should
be reloaded.
fopen unsuccessful. See preceding runtime messages for details.
Full-screen initialization failed: explanation.
window on command, the initialization of
the full-screen environment failed for reason explanation.
Line-mode will be used.
window-height window height is greater than the maximum height allowed for the window window-name. Set to maximum-value.
config command was issued for a window window-name, but a
height window-height was
specified that is greater than the maximum allowed for that
window, and was reset to maximum maximum-value.
window-name window height is less than minimum (window-height). Set to minimum-value.
window-name window row position is invalid for height specified. Set to row-number.
window-name window width is greater than the maximum width allowed for the window (window-width). Set to maximum-value.
window-name window width is less than minimum (window-width). Set to minimum-value.
column-position window column position is invalid for width specified. Set to column-number.
window config command was issued that specified a
position that was
invalid for the width of the window.
An appropriate adjusted position column-number will be used.
Zero / Multiple windows of this name are present - use <> to point.
window command was issued that specified a window name,
but there are either no windows with this name, or there are multiple
windows with this name.
Unable to reopen basic window. Continue debugging in line mode.
window command command was issued, but the debugger
was unable to open the window.
Debugging will continue in line mode.
This WINDOW cannot be OPENed/CLOSEd.
window open or window close
command was issued for a window
that cannot be opened or closed. This includes the Command,
Log, Source, and Status windows that may not be closed (or opened).
Full-screen mode is on.
window on command was issued, but this debugging session is
already in full-screen mode.
Unable to determine initial working directory, ".cdebugrc" not processed.
This WINDOW subcommand is not valid in this window.
window command was issued, but is not valid for the specified
window.
Full-screen window open(s) failed - switching to line mode.
window open command, the opening of the
window failed.
Line-mode will be used.
Insufficient memory specified for window-name window - amount ignored.
window open command was issued for the window-name window, but
the memory size for the window was not sufficient.
window-name is Browse, Command, Log, or Source.
The specified value is ignored.
Window limit reached: cannot open another window.
window open command was issued but the maximum number
of subwindows have already been opened.
severity detected by module-name: error-code.
Insufficient memory for the window-name window - unable to allocate size bytes.
window command for the window-name window was issued, but
size bytes of storage could not be allocated.
Line too long.
No continuation line.
Line line-number is not in any function - the request is ignored.
Multiple "r" commands may not be specified.
runto line commands were entered.
runto command at a time.
Both "g" and "r" prefix commands may not be simultaneously specified.
g (goto) and r
(runto) prefix commands were specified simultaneously.
This is not supported.
Unable to popup window to process ERROR: "message-text". Change is ignored.
Prefix-area commands may not be entered when no source is displayed.
Length of input line is greater than 255 characters. It is truncated to 255 characters.
Input is not being prompted for at this time.Unable to open the termin window. Input intercept disabled.
stdin.
Unable to open the termout window. Output intercept disabled.
stdout.
Discarding input in window-name window.
Debugger file line-numbers do not correspond to source.
Section-name section-name was not compiled DEBug (-d). There are no "hooks" in the code, and there is no debugger file available.
debug option.
This file cannot be debugged with the debugger.
debug option.
No debugger file - open failed, see runtime messages for details.
debug option and the debug files
are accessible, issue a
set search command to
identify the location of the files and the issue the
list
command.
Debugger file "file-name" is invalid and not used.
Debugger file "file-name" is from Release 5.00 or before, which is not supported by this debugger.
Debugger file file-name was not created in the same compilation as the object (file-name).
Debugger file for section name section-name was not created in the same compilation as the object (file-name).
Dump terminated due to a memory access exception at ??.
dump command was issued, but a memory access exception
occurred.
Dumping stops.
Cannot evaluate "expression". message-text
Memory access exception at address while determining string length.
dump command was issued, and an access exception
occurred when loading the string length.
"operand" must be of address type.
dump command was issued, but the operand specified was
was not an address type.
A count may not be specified for an expression of this type.
print command was issued with a count, but a count cannot
be specified with this data type.
Support for specifying a "TAG" type within parentheses after the expression to be printed has been dropped. Use casts to achieve a similar result.
TAG after an expression. Now, simply cast the value to the
appropriate type.
A "COUNT" may not be specified if the output is redirected to the Print window - the "COUNT" is ignored.
print command was issued that specified a
count. This is
not supported when the output is being directed to the
Print window.
The count is ignored.
Unable to access "variable" due to a memory access exception.
enum variable variable,
an access exception occurred.
A number must follow the '-' or '+'.
scope
command was issued with a + or -
that was not followed by
an integer.
A maximum of 1000 C macro expansions per line are allowed.
C macro expansion caused input buffer overflow.
Cannot load special character table - default values used.
l$dcst) failed.
A default of a one-to-one mapping is used.
No debugger macro defined for macro-name.
A maximum of 1000 macro expansions per line are allowed.
Debugger macro expansion caused input buffer overflow.
No Configuration file specified.
config save command was issued, but no configuration file
has been specified.
config file command to specify a configuration file.
Open failed for file-name.
storage or config save command was issued,
but the output file file-name could not
be opened.
For the storage command, the file is designated as follows:
cms: progam-name DBGSTG A
ddn:DBGSTG
ddn:DBGSTG is defined, that DDname is used;
otherwise, dsn:user-ID.program-name.DBGSTG is used.
config save command,
the configuration file is specified with the
config file command. Under CMS, this filename is named DBCONFIG. Under OS/390, it is named either the
specified filename or first-level-qualifier.CDEBUG.CONFIG(name).
No requests in list.
drop all or drop last command was issued, but there
are no current requests to drop.
No request applies specifically to this location.
enable or disable command was issued, but there was nothing
to modify.
Multiple requests apply to this location. 'request' not performed.
enable (e) or
disable (d) command was entered, but
multiple requests apply to this location. The intended
request must be specified.
Request number request-number already disabled.
disable command was entered, but the specified request
number had already
been disabled.
Request number request-number does not exist.
disable or drop command was issued specifying
a request number that did not exist.
Last request already disabled.
disable last command was issued,
but the last entry
had already been disabled.
Request number request-number already enabled.
enable command was issued specifying a
request number that was already enabled.
Last request already enabled.
enable last command was issued, but the last
request was already enabled.
request not installed. An identical request (request-number) already exists.
continue command was issued, but an identical request
(request number request-number) already exists.
request not installed. A similar request (request-number) already exists. However, COUNT has been changed to new-count.
continue command was issued, but request request-number
already exists. The number of continue requests has been
increased to new-count.
Type of "variable" (target) is invalid for the command command.
assign,
an attempt was made to give variable a value with
the assign command; however, variable was not an appropriate
type.
If command is copy,
an attempt was made to copy to variable with
the copy command. The variable must be an address.
A null list was specified: the command command will not change the target.
assign,
an assign aggregate-type-expression=value-list
command was issued, but
value-list was empty.
An empty value-list is not accepted.
If command is copy,
a copy destination,{list}
command was issued, but {list}
was empty. An empty list is not accepted.
Assignment of a list to a scalar is invalid.
assign aggregate-type-expression=value-list
command was issued, but aggregate-type-expression
is a scalar-type-expression.
Cannot "command" class/struct/union type to scalar type.
class, struct, or union
typed variable to a scalar variable.
Can only assign a structure/union declared with the same tag in the same compilation.
assign command was issued that specified
structures or unions
that were not declared with the same tag.
Need a list or class/struct/union to initialize a class/struct/union.
assign command was issued that specified
either class, struct, or union
but the assignment value was not a
class, structure, or a union.
Ignoring excess item(s) in list.
assign command,
more items were found to be assigned than existed in the
destination expression.
The excess items are ignored, and command processing continues as
as if the excess items were not present.
Type of "expression" (source) is invalid for the command command.
Need a list to initialize an array in a structure.
assign command attempted to assign a value to an array in a
structure. A list must be specified.
Assigning a list to a scalar element of an array is not valid.
assign command attempted to assign a list to a
scalar element.
A scalar must be specified.
This version of the debugger does not support debugger files from Release release-number.
Memory access exception resulted when performing assignment / copy.
assign or copy command was invalid.
It is possible that a storage overlay occurred
for those sections of the
assign or copy that did not cause the access exception.
Source and target sizes are unequal.
copy command was issued and the specified source and
target are not the same size.
target-type type of aggregate is invalid - simple type or enum type should be specified.
copy command was issued with an invalid target, where
target-type is Implied target or Target.
The RETURN command may not be issued at this kind of hook.
return command may not be issued at this line
in the function.
A List may not be specified for a function returning a scalar.
return command was issued that specified a list, but
this function returns a scalar.
The RETURN command may not be issued at a SIGNAL.
return command may not be issued at this time.
A Return value may not be specified for a function returning void.
return command was issued with a value specified.
This is not allowed for a function that returns void.
No return value specified for function returning int. Return is performed.
int return value.
A Return value must be specified.
return command was issued that did not specify a return value
but a return value needs to be specified.
Cannot RETURN class/struct/union to a function returning a scalar.
return command was issued attempting to return a
class, struct, or union
when the function should be returning
a scalar.
The return value is not used by the caller - the RETURN is not performed.
return value is
not performed.
No debugger file is available for function function-name.
set search debug= command followed by a
list command to attempt to reload the
debugger file.
fputs() error while writing to configuration file file-name.
A missing or invalid % format format-name is specified.
print command was issued that specified more than one format,
but only one format is allowed.
Format specification may not be specified for structures, but is used for all fields in the structure.
print command was issued that specified a format specification.
It is ignored.
The function has no parameters.
print command was issued that did not specify any operands at a
function entry. The default print command at a function entry is
to print the function parameter, but this function has no
parameters.
Memory access exception resulted while accessing area to be monitored.
monitor command, a storage access
exception was recognized while referencing the area to be monitored.
The monitor is not set.
Long message has been truncated.
Not running in interactive mode - help not available.
help command was entered, but help is available only
when running interactively.
DBGHELP must be allocated for access to the help system. The debugger could not execute the L$DBHELP CLIST to automatically allocate DBGHELP.
help command was entered, but the L$DBHELP CLIST did
not complete successfully.
The Help key (PFkey-number) cannot be redefined using a KEYS DEFINE command; instead, use the KEYS HELP command.
keys define command was issued attempting to set
the Help key.
[Command | Log] line has been truncated - lines in the window-name window cannot exceed 251 characters
No entry for "text" in the help system.
help command was issued, but keyword was
not found.
Terminal width (terminal-width) exceeds "maximum-value" columns. Problems may occur.
Unable to access the help system.
help command was issued, but the help file could not
be opened.
The ISPF environment is not active.
The Help key cannot be assigned to ISPF.
A key assigned to ISPF cannot be made the Help key.
help function to a key
already assigned to ISPF.
Insufficient memory to hold macro name longer than max-size characters - the macro has been discarded.
The configuration has been written out to file-name.
config save command was issued and the configuration
was successfully written to file file-name.
The debugger file file-name is not complete.
Source file has shrunk to new-number lines (from old-number lines) after the debugger first opened it.
More than "maximum-value" browse windows cannot be simultaneously open.
A debugger file is not available: cannot set breakpoints on lines in function function-name.
set search debug command to locate the debugger
files, and issue the list command to reattempt the loading of the
debugger file.
Cannot set a breakpoint as function function-name is split across source files.
Cannot set a breakpoint on line line-number as function function-name starts on line start-line and ends on line end-line.
Cannot set a breakpoint on line line-number of function "function-name" as there is no code generated for this line.
Debugging a function in section-name section-name ...
Forcing a break as the debugger could not install a line hook breakpoint. The request with the invalid line number should be dropped.
break func nnn command was entered, but the line did
not exist. A dummy break was installed.
Could not open debugger startup file "file-name". error-text.
//cms: cdebug rc *
dsn:userid.cdebug.rc
//hfs:login-directory/.cdebugrc
After a function name, only an integer and a)can follow a(.
A function name specified within double quotes is invalid.
AUTO EXTNAME cannot be changed when the AUTO CXX is option is on.
auto extname command was issued, but the
extended name support cannot be changed while
the cxx option is on.
Could not resolve function name "function-name" using merged debugger files.
There is just one instance of function name function-name in the merged debugger files - the subscript is ignored.
A function subscript of zero may not be specified in this command.
Only C macros with no arguments are supported by the debugger.
Cannot access auto variables from a lexically enclosing function.
Invalid type of expression for a reference type RETURN.
return command was issued, but a reference type must
be specified.
Cannot access members from a lexically enclosing class.
Using this particular instance of the class for monitor purposes.
monitor
command specified a non-static member variable; for example,
m of the same class as the "this" argument.
The variable that is contained in the current "this" instance; for
example, "this->m", is the one that is monitored.
The ASSIGN command may not be used with an object which has, or an object whose member has, a base class.
Requests on all instances of an overloaded function may only be set on "calls", "entry", or "return" type hooks.
on command specified a hook of other than
call, entry, or
return (or *) for an overloaded function
that is not supported.
The RETURN command may not be used to return an object which has, or an object whose member has, a base class.
return command was issued that specified an object, and
either the object or a member of the object has
a base class. This is not supported.
Memory access exception accessing virtual base class class-name.
Out of memory - command output is not complete.
Classes are inherited: address/offset translation performed: address --> offset.
The RETURN command may not be used to return an object which is returned using a copy constructor.
return command was issued that specified a copy constructor.
This is not supported.
Invalid / inconsistent type of expression for a reference type RETURN.
return command was issued that specified a reference type
that was inconsistent with the function definition.
Only a pointer to a member or zero can be assigned to a pointer to a member.
assign command.
Unable to perform the ASSIGN command. explanation
assign command was entered, but could not be performed
because of explanation.
The "function_name:" prefix is no longer supported. The SCOPE command may be used to provide similar, though enhanced, functionality.
function_name: was used in an expression
to provide for scoping, but this form is no longer supported.
Could not find function "function-name" in calling sequence. Enter WHERE to display traceback.
where indicates the calling sequence.
Could not perform the command as there is no log file defined.
log capture or
log file command was entered,
but there is no log file.
The current log file is file-name.
log file command was entered. The current file is file-name.
The log buffer is currently empty.
log capture command was entered, but there are no lines
to capture.
Error writing log file. Output logging has been turned off.
The WINDOW FIND command is not supported in the window-name window.
window find command was issued for window window-name, but
this window does not support the find command.
Cannot find search string: string
window find command was issued, but the search string string
was not found.
Treating "name" as a C function name...
"variable" is not in scope.
browse command was issued, but the location specified
was not addressable in the current scope.
A subscript after the function name is not valid in this context.
The name of the file to be browsed has not been specified.
browse command was entered, but the no file has
been specified.
A pointer to a member can only be assigned to a pointer to a member.
assign command.
The signal occurred at offset address which is greater than the size of the function (address).
"expression" is an expression of type void and cannot be PRINTed.
print command was issued that specified a value expression
that evaluated to a type void. There is nothing to print.
Underflow in floating-point constant.
Overflow in floating-point constant.
Couldn't find template "template-name" in the template-list list.
set search file-tag -"template"
command was issued, but the specified template, or templates, to remove were not found.
set search file-tag ?
to see a list of the current
templates for the named file, and check the specification
of the template.
See SAS/C Debugger User's Guide and Reference
for information about the set search command.
An invalid conversion specifier has been specified in a template. Invalid text begins at "text".
set search command, a template was specified that
contained the invalid conversion specifier text.
A specifier-value conversion specifier must be followed by another conversion specifier.
set search command, a %l or %u conversion
specifier
was used in a template, but it was not followed by another conversion
specifier. The %l and
%u conversion specifiers cause the
replacement text case for the conversion specifier immediately following
them to be converted to either uppercase or lowercase. As a result,
they must always be followed by a second conversion specifier.
The "specifier-value" conversion specifier can only be used for a compilation on system-name.
%ddname or
%membername
was specified in a template on a
set search or set cache command,
but the file was not compiled on the system-name that is being
debugging. Where system-name is either OS/390 or CMS,
the current template is skipped and processing continues with
the next template.
The "specifier-value" conversion specifier cannot be used when there is no file name available.
set search
or set cache command, but the original filename had
not been specified. %sname is the only valid
conversion specifier when the original filename is not specified.
The current template is skipped and processing continues with
the next template.
Compilation with section name "section-name" is pre-Release 5.00C and not supported by this debugger.
Source files compiled on system-1 cannot be debugged on system-2 without using SET SEARCH search-type commands to access files.
set search search-type command should be used
to indicate to the debugger how to correlate the names
used in the compile to the names on the destination host.
set search command to identify the files
necessary for the debugger.
See SAS/C Debugger User's Guide and Reference
for information about the set search command.
This format of the debugger file name is not supported: file-name.
set search debug ? command
and examine the returned templates and original filename
displayed in this message.
The template approach to search for files using the SET SEARCH and SET CACHE commands cannot be used with files compiled with this version of the compiler.
set search and set cache commands.
Tried to open file-type type file where "file-name". error-info.
in cache), may not have been opened
for the reasons indicated in error-info,
and tracing for this file type had been enabled.
Debugger recoverable internal error. Inconsistent value: value. Traceback follows:
Debugger recoverable internal error. Inconsistent values: 1: value-1, 2: value-2. Traceback follows:
The "specifier-value" conversion specifier can only be used in templates for file-type type files.
userinclude,
the %ddname conversion specifier can only be specified
for user include templates in the set search userinclude
statement. Command processing ends.
set search command.
file-type type file "file-name" found.
set search command was successfully opened and
tracing was enabled for this type.
File processing continues.
set search file-tag ?
determine the current template, and either change the template
or rename the associated files to correspond to the currently
defined template.
See SAS/C Debugger User's Guide and Reference
for information about the set search command.
Tried to open DEBUG type CACHE file "file-name". error-info. The debugger will not use the cache mechanism for this compilation.
set cache command.
Tried to write to DEBUG type CACHE file "file-name". reason. The debugger will not use the cache mechanism for this compilation.
Tried to remove "file-parts". error-info.
The time-stamp of the debugger file (file-name) in CACHE is different from the time-stamp of the object code (file-name). The cache file will not be used.
The debugger file in "file-name" will be copied to the CACHE location "location".
Debugger unrecoverable internal error. Inconsistent value: value.
Debugger unrecoverable internal error. Inconsistent values: 1: value-1, 2: value-2.
Debugger unrecoverable internal error. Inconsistent values: 1: value-1, 2: value-2, 3: value-3.
The target of the command command, "target-type", is not in the address space of the program.
assign
or copy, can only be used to
modify variables in the current address space.
The debugger is terminating due to lost communication connection with remote subject program.
PRINT not performed due to a memory access exception.
The RSYSTEM command is not supported by the environment of the program being debugged.
The Debugger command "command" failed with return code return-code.
RSYSTEM command "command" return code is return-code.
Unable to set default search templates.
set search templates.
No executable profile "file-name" found.
.cdebug.
No transaction name specified.
DBUG command
in the command line.
The transaction name transaction-name is invalid or has not been defined to CICS.
CEMT INQUIRE TRANSACTION(transaction-name)
An EXEC CICS INQUIRE TRANSACTION transaction-name command failed with response code code.
The program program-name has not been defined to CICS.
The program program-name is disabled.
CEMT SET PROGRAM program-name ENABLEOtherwise, contact your CICS system administrator for further assistance.
The program program-name can not be loaded by CICS.
An EXEC CICS LOAD command for program program-name failed with response code code.
Application has not been linked with a SAS/C Release 6.00 or higher resident library.
EXEC CICS SEND MAP map-name failed with response code code.
An 'EXEC CICS SEND TEXT FROM message-text' command failed with response code code.
file-tag type files: TRACE is status and the search list is empty.
set search file-tag ?
command. Otherwise, see messages 391,
392, and 393
The status value for TRACE is either on or off.
file-tag type files: TRACE is status and the search list contains:
set search file-tag ? command,
if the list of file templates is not empty, then this message will
be displayed followed by a LSCD392 or LSCD393 message
(if file-tag is debug),
then a series of LSCD392 messages. The TRACE is either
on or off.
(There is no CACHE specified.)
set search debug ? command, if a cache file
has not been specified, this message will be displayed. See
messages 391, 393,
and 394 for more information.
set cache command.
See Debugger User's Guide and Reference
for information on specifying a cache.
(CACHE is "file-name".)
set search debug ? command, a cache file
has been specified as file-name.
See messages 391, 392,
and 394 for more information.
set cache= command.
See SAS/C Debugger User's Guide and Reference
for information on specifying a cache.
"template"
set search file-tag ?
command, if the list of file templates is not empty, then a series of
these messages will be displayed preceded by message 392.
set search file-tag =|+|- "template"
command.
string
dblog command was encountered specifying the displayed
string.
macro-name macro-text
define * or define macro-name command was entered.
Macro-name represents the defined macro name, and macro-text represents
the replacement text for that macro.
No debugger macro variables defined.
define * command was entered to display all defined macros,
but there are no macros currently defined.
break on name-1 - context of name-2.
Dimension of array "array-name" is not known.
sizeof(array-name) was specified
in an expression, but the
dimension of that array is not known.
Cannot apply sizeof to name type "type".
sizeof(name) was specified in an expression, but the
name specified was of type function or bitfield
which is not supported with sizeof.
Type of "type" is invalid for the "operation" operation.
"name" is not an lvalue.
Cannot take the address of "name".
Cannot apply & to the bit-field / enumeration constant "name".
Computational error involving the "operation" operations with operands "operand-1" and "operand-2"
Subtraction cannot be performed: pointers "pointer-1" and "pointer-2" point to objects of different sizes (size-1 and size-2).
Types of "variable-1" and "variable-2" are invalid for subtraction.
The only constant that can be compared with a member pointer is 0.
"name" is not a scalar.
Type of "operand-1" and/or "operand-2" is invalid for the "operation" operation.
One of "operand-1" and "operand-2" should be of pointer type and the other of integer type.
Only an identifier can precede the "::" operator.
::.
Cannot cast non-scalar type "name".
Casting to type is not allowed.
"variable" is not a pointer to a member.
.* or ->* was specified in an expression, but the
pointer specified was not a pointer to a class member.
The operator ".*" or "->*" is invalid for "variable".
.* or ->* was specified in an expression, but the
object addressed is not a class member.
Memory access exception accessing virtual function table pointed to by "variable".
.* or ->* was specified in an expression, but the
object address variable is not valid.
Pointer to member, "variable", is NULL.
.* or ->* was specified in an expression, but the
object address variable is NULL.
The operator operator cannot be applied to "variable".
. or -> was specified in an expression, but the
operation is not valid for the specified variable.
Only one level of "::" following a "." or "->" is supported.
. or -> was specified in an expression, with multiple
:: operators, but only one is supported.
Only an identifier may follow a ".", "->", or "::".
., ->, or :: was specified in an expression,
but the
operand following the given operation was not an identifier.
Memory access exception dereferencing pointer to member "member-name".
Memory access exception accessing reference "variable".
Cannot obtain the "value" of "variable" as it is not an lvalue.
Memory access exception accessing "variable".
No user commands have been installed.
install * command was issued to list all user commands,
but none were found.
Listing source from file-name
Resuming execution in function function-name.
resume function command was issued and execution is
resumed in function function-name.
Resuming execution in function function-name.
resume function-name lineno
command was issued and execution is
resumed in function function-name.
MONITOR not installed, MONITOR monitor-name already exists.
monitor command was issued when monitor monitor-name
already exists for
the specified variable.
"monitor-name"
Monitor hit: monitor-number *
. MONITOR variable-name (inactive)
" " (recursive)
" " LIBRARY IN (name) PRINT WHERE
new-bitfield was old-bitfield
: uninitialized will be appended to
old-bitfield. Note also
that if an access exception occurs while examining the bitfield, the
word IMPOSSIBLE will appear.
new-value was old-value
new-value was old-value
Pointer in class class-name to virtual base class base-class has been corrupted.
base | virtual base ...printed above....
When printing a normal base, you get
base tag-name {base-contents}
When printing a virtual base, you get
virtual base tag-name {base-contents}
If the virtual base was already printed, you get
virtual base tag-name ...printed above...
base | virtual base ...printed above....
base tag-name {base-contents}
When printing a virtual base:
virtual base tag-name {base-contents}
If the virtual base was already printed, you get:
virtual base tag-name ...printed above...
Command not processed as there are function-count functions named function-name:
function-index function-name
PF key definitions:
key list command was issued. This is the heading for
the list of function key definitions.
key-number action
key list command was issued, and action is the action
when PF key key-number is pressed.
The current configuration file is file-name.
config file command was issued, and the new configuration file
is file-name
line line-number: no suffix allowed for 'g'
g was entered for line line-number with a suffix,
but suffixes are not allowed on the g prefix command.
line line-number: invalid prefix command
b (break),
d (disable), e (enable),
g (goto and resume),
q (query), r (runto),
and t (trace).
module not in calling sequence MODULE: module-name number
invalid line number LINE: line-number
Invalid value value. Enter value:
Invalid value value. Enter value:
Formats begin with a '%' FORMAT format-name:
Invalid hex value. value value:
invalid expression specified EXPR expression:
when expression was entered that was invalid.
Set system breakpoint at location to activate the ESCAPE command.
escape command.
C-macro "original-macro" replaced by "replacement-macro".
An EXEC CICS RECEIVE MAP [map] command failed with response code code.
A putenv() for some debugger environment variable failed.
command (command-length) as exec
Copyright © 2001 by SAS Institute Inc., Cary, NC, USA. All rights reserved.