LSCD Debugger Messages

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:

   LSCD[num] [message text]
For invalid syntax messages, see SAS/C Debugger User's Guide and Reference, which contains descriptions of the commands that are supported by the debugger. A brief description of the commands is also provided by the SAS/C Debugger help system.

LSCD Messages

000

An invalid command name was specified. (Enter ? for a list of valid command names).

Explanation

A command was entered but was not a valid debugger command.

002

{mono The argument specified for the ON/BREAK/TRACE/IGNORE/QUERY command is not valid.

Explanation

An invalid argument was specified.

004

ON expects a single command or a command list within braces.

Explanation

An on command was issued with more than one deferred command without braces.

005

Section-name and ) should follow (.

Explanation

A left parenthesis was found, but the next token was not a name or an opening parenthesis was found that was not followed by a closing parenthesis.

007

The function-name or section-name argument should be "calls", "entry", "return", "*" or a line-number range.

Explanation

An invalid on command was entered. The syntax begins

on name [ calls | entry | entry | * | line-number ]

008

There is invalid text, "[text]", after the end of the when clause.

Explanation

A when clause was entered with text after the expression argument.

009

The [command] command without arguments is only valid in an ON command list. The command is ignored.

Explanation

A [command] command was entered without any arguments. This format is supported only as an operand to the on command where [command] values include break and trace.

010

The expression specified is incomplete.

Explanation

A whatis command was issued, but the expression specified was not complete.

011

"[keyword]" is not a valid keyword for the [command] command.

Explanation

The following table lists the valid keywords for each of the commands that accept a keyword argument.
   [command]   [keyword]

                                                            
  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                                
                                                             

013

[name-type] name has been truncated to [len] characters.

Explanation

An 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.

014

End of range ([eor]) cannot be less than start ([sor]).

Explanation

A drop, enable, or disable command was entered, but the operands specified, [start-of-range]:[end-of-range] with [end-of-range]<[start-of-range], are not supported.

015

Invalid TYPE/cast specified.

Explanation

While parsing a cast expression, invalid syntax was found.

016

An integer must follow the COUNT keyword.

Explanation

An on command was issued with the count clause, but count was not followed by an integer.

017

The syntax specified for the [command] command is not valid.

Explanation

The [command] command was issued, but was not valid. Additional messages are generally issued that further explain the problem.
[command] values:
install, drop, enable, disable, monitor, print, auto, config, define, exec, percent (%), help, undefine, system, browse, log

018

[command] has not been installed as a user command. It already exists.

Explanation

An install [command] command was issued, but [command] already exists.

019

End-of-input occurred before continuation was completed.

Explanation

While reading a line a continuation character was encountered, but no continuation input was found.

020

Logical input line cannot exceed 312 characters - input discarded.

Explanation

A line longer than 312 chars was read from either a CLIST, EXEC, stack, or user input. The input is discarded.

021

An invalid TYPE/cast was specified: a right parenthesis is missing.

Explanation

While parsing a type or cast expression, invalid syntax was found. Either a right parenthesis or a colon was missing.

022

A length of 0 may not be specified as the number of bytes to be DUMPed.

Explanation

A dump command was issued that specified a length of zero.

023

There is an invalid symbol in the specified list.

Explanation

Operands in a list must be separated by commas, but a comma was not found where expected.

024

Only a non-zero number of bytes may be specified.

Explanation

A copy command was issued that either did not specify the number of bytes, or specified zero bytes to copy.

025

The when clause specified is not valid.

Explanation

An on command was issued that specified an invalid when clause.

026

There is invalid text, "[text]", after the end of a valid expression.

Explanation

A when expression was specified that had extra text.

027

Nested braces are not allowed in a list.

Explanation

While parsing a list of items, an apparent nested brace was found. This is not supported.

029

Only plain types and enum types can be specified with a value list.

Explanation

A COPY command was entered, but a plain type or enum type was not specified with a value list.

030

Missing function-name, section-name, or hook / event specification.

Explanation

A required name or specification is missing.

031

Continue input line ...

Explanation

While reading a line, a continuation symbol was encountered before the end of line.

Action

Continue entering the input line.

032

unsigned/signed float is an invalid type.

Explanation

While parsing a cast expression, an unsigned or signed float type was found.

033

unsigned/signed double is an invalid type.

Explanation

While parsing a cast expression, an unsigned or signed double value was found.

034

The following input in the buffer has been discarded: [input]

Explanation

The debugger decided to flush the input line as shown in the next message.

035

An invalid command name was specified.

Explanation

A command was entered, but it was not a valid debugger command.

038

A range may not be specified in full-screen mode.

Explanation

A list command was issued that specified a line number range, but only a starting line is allowed in full-screen mode.

039

The [command] command without parameters is invalid.

Explanation

The auto, config, window, or log command was issued without parameters.

Action

Specify a valid parameter.

041

A section-name must follow a '('.

Explanation

A list command was entered with an open parenthesis. This indicates the specification of a section-name, but a section-name was not found.

042

A ')' must follow a section-name.

Explanation

A list command was issued with an open parenthesis and a section-name, but a closing parenthesis was not found.

043

An integer or '*' must follow a function-name or a parenthesized section-name.

Explanation

A list function-name | (section-name) command was issued, but it was not followed by a line number specification.

044

A ':' must follow an integer if a line-number range is to be specified.

Explanation

A 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.

045

An integer or a signed positive integer must follow a ':'

Explanation

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.

046

An integer must follow a '+' or a '-'

Explanation

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.

047

A signed positive integer must follow a ':'

Explanation

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.

048

A signed integer must follow a ':'

Explanation

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.

049

The first argument of the LIST command is invalid.

Explanation

A list command was entered with invalid arguments.

050

A line number of 0 is invalid.

Explanation

A list 0 command was issued, but the first line in a file is 1, not zero.

051

The [command] command is not supported under OpenEdition.

Explanation

The [command] command was entered under OpenEdition, but this command is not supported. Commands not supported include: percent (%), config, dbinput, dblog, keys, transfer, watch, and window.

052

Record read from DBGIN longer than 256.

Explanation

Logical Record length of DBGIN is greater than 256.

Action

Ensure that the file that is associated with DBGIN has a logical record length of less than or equal to 256.

053

Identifier truncated to [size] characters.

Explanation

While parsing an expression, a token was found with more than [size] characters. The specified identifier was truncated.

054

The following input has been discarded: [line]

Explanation

The debugger decided to flush the input line [line].

055

Cannot PRINT "[var]" as the dimension of the array is not available.

Explanation

A print command was entered with the array variable [var], but the dimension was not specified.

056

A comma is missing or there are too few function arguments.

Explanation

For a function specified in an expression, either a comma is missing or there are too few arguments.

057

A right parenthesis is missing or there are too many function arguments.

Explanation

For a function specified in an expression, either a right parenthesis is missing or there are too many arguments.

Action

See the definition of the function for the proper argument list.

059

A left parenthesis must follow the function name.

Explanation

A parenthesis must follow a function name in a specified expression.

060

A function name cannot be obtained: please supply it.

Explanation

While parsing a line number specification, a current function name could not be determined. An explicit function name specification is required.

061

The function-name / signal-name has been truncated to 8 characters.

Explanation

A hook command was issued, and the specified name has been truncated to 8 characters.

062

The config file can only be changed if the configuration is being saved.

Explanation

To change the configuration filename, the configuration save value must be 'Y'.

063

The [command] command cannot be specified in the profile.

Explanation

The command [command] is not supported in the profile. Commands that are supported include: abort, auto, break, config, define, disable, drop, enable, help, question mark (?) commands, ignore, install, log, on, percent (%) commands, query, set, system, trace, rsystem, undef, user, and window.

Action

Remove the command [command] from the profile.

064

Command's arguments, if any, are not processed.

Explanation

An entered command's arguments are ignored. This is usually because of the failure of the command to be processed.

066

End of profile/file: an incomplete ON command has been discarded.

Explanation

An incomplete on command was entered during debugger initialization.

067

The ON command has been discarded.

Explanation

An attempt to perform an on command failed.

068

The [command] command can only be issued from a Rexx exec or Clist.

Explanation

The dbinput and dblog commands can only be issued from an EXEC or CLIST.

069

Prompt length may not exceed "[prompt-length]" characters.

Explanation

A dbinput command was issued that specified a prompt, but that prompt string was longer than [prompt-length].

070

The DBINPUT command gets input from the terminal when the debugger is prompting for terminal input.

Explanation

A dbinput command has been encountered and the debugger is is now waiting for input.

Action

Enter data.

071

Valid RESUME must be followed by no parameters, a function-name, a non-zero line-number, or both.

Explanation

A resume command was issued with invalid parameters.

072

Key definition text exceeds maximum allowed.

Explanation

A keys command was entered but the definition text is greater than the limit.

074

A TRANSFER command without arguments is ignored.

Explanation

A transfer command was issued, but arguments are required.

076

The "signal"/"signals" keyword can only be specified with IGNORE.

Explanation

A signal keyword was specified on a hook or query command, but it is only supported on an ignore command.

077

Invalid syntax specified. Valid syntax is "IGNORE SIG.... signal"

Explanation

An invalid ignore command was issued.

078

Only an integer may follow a STEP or CONTINUE command.

Explanation

A step or continue command was issued with a non-integer argument.

079

Unable to open an input file to the terminal - DBINPUT fails.

Explanation

A dbinput command was encountered, but the debugger was unable to open the terminal input file. dbinput ends without obtaining user input.

080

The only valid prefix command is 'd' to drop a watch.

Explanation

A prefix command other than d was entered on a line that had a watch. The only valid command is d[rop].

081

A section-name cannot be greater than 7 characters.

Explanation

A name was entered with a length greater than 7 characters.

082

Out of memory - command(s) ignored.

Explanation

During execution of a command, a storage allocation failed. The command does not execute.

083

Out of memory - scrounging around, end ASAP.

Explanation

An attempt to malloc storage failed. The debugger is now using a limited number of preallocated buffers.

Action

Do something that might free debugger storage or terminate the debugging session.

084

Out of memory - debugger file cannot be read.

Explanation

While reading a debugger file, an out of memory condition was experienced. The debugger file is unusable.

085

An invalid symbol follows the EXIT command.

Explanation

The exit command was entered with a keyword operand that was not nodrop. The exit command is ignored.

086

An invalid keyword has been specified to the STORAGE command.

Explanation

A storage command was entered with an invalid keyword.

087

Unable to read from the terminal - DBINPUT fails.

Explanation

A 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.

088

Missing/invalid LINESIZE value.

Explanation

An auto command was issued with an invalid linesize value.

089

Continue ON command list definition...

Explanation

An on command has been entered, but is not complete. Enter the rest of the command.

090

The expression specified is invalid.

Explanation

While parsing an expression, invalid syntax was found.

091

A "=" must separate the source from the target in an ASSIGN command.

Explanation

An assign command was issued with an inappropriate equals sign. The format is
ASSIGN var=value

092

A "," must separate the operands of the COPY command.

Explanation

The operands to the copy command must be separated with commas.

093

An invalid delimiter follows a valid command - the command is not executed.

Explanation

A syntactically correct assign, copy, or return statement was entered with trailing characters.

094

The syntax specified for the function call is not valid.

Explanation

While parsing a builtin debugger function, invalid syntax was found.

095

The string is too long or is not terminated.

Explanation

While processing a token, either a string that was not terminated or a string that was too long was found.

096

EXEC / CLIST variable name is longer than 256 characters.

Explanation

While reading text from the input stream, an EXEC or CLIST name with a length greater than 256 characters was found.

097

The Termin window is not wide enough for the prompt - prompt truncated.

Explanation

A prompt command was issued, but the Termin window is not wide enough to display the prompt text. The prompt is truncated.

098

End of line number range cannot be less than the start.

Explanation

A line range specification was used where the end-of-range specification was less than the start-of-range specification.

099

Could not set desired scope.

Explanation

A scope command was entered, but the specified scope is not in the current call path.

100

# followed by a null / undefined macro name.

Explanation

While parsing an expression, a pound sign (#) was found, followed by an invalid macro name.

101

A format specification may not be specified with this TRANSFER keyword.

Explanation

A transfer command was issued with an invalid format. Acceptable formats include: offset, address, value, or lineno.

102

A LOG file has not been specified. Logging has not been turned on.

Explanation

A log start command was issued, but a log file had not been specified.

Action

Define a log file with the log file command.

103

Right bracket does not follow valid subscript.

Explanation

A right bracket was expected in an expression, but it was not found.

104

Out of memory - overwriting debugger memory, end ASAP!!!

Explanation

An attempt to malloc memory failed for a request that is larger than the preallocated debugger memory pool.

Action

Terminate use of the debugger now.

105

Invalid text follows valid KEYS keyword.

Explanation

A keys command was issued followed by invalid text.

106

Invalid PF key number: valid numbers are 1-24.

Explanation

A keys command was issued with an invalid PF key number. PF keys are limited to the range 1-24.

107

Syntax is: KEYS DEFINE n "text".

Explanation

A keys command was issued with an invalid syntax.

108

Cannot drop a non-existent watch.

Explanation

A drop command was issued for a line that does not have a watch.

110

Invalid syntax for color/attribute specification.

Explanation

A window color command was issued with an invalid color specification.

111

The Command, Log, Source, and Status windows may not be closed.

Explanation

A window close command was issued for a window that may not be closed.

112

This command is valid only in full-screen mode.

Explanation

A browse command was issued, while in line mode.

113

The WINDOW sub-command "[subcmd]" may not be specified in the profile.

Explanation

A window [subcmd] command was issued in the profile, but this subcommand is not supported from the profile.

114

Placeholder replacement not successful.

Explanation

This happens either during placeholder replacement while expanding a macro or from an expr command. Is is usually accompanied by LSCD124, LSCD125, or LSCD126.

115

Placeholder replacement not successful: valid expression not found.

Explanation

During placeholder replacement, an invalid expression was found.

116

Placeholder replacement not successful: input buffer overflow.

Explanation

During placeholder replacement, more space was needed than was available for expansion.

117

Commands to continue execution may not be issued when the [window] window is in this state.

Explanation

The command entered is ignored when the Termout or Termin window requires attention. Commands not supported include: continue, step, go, runto, resume, and goto.

Action

Resolve the pending terminal input or output event to be able to issue these commands.

118

This command may not be issued when the [window] window is in this state.

Explanation

The command entered is ignored when the Termout or Termin window requires attention. Commands not supported include: exec, and window off.

Action

Resolve the pending terminal input or output event to be able to issue these commands.

119

One or more missing right parentheses assumed to complete expression.

Explanation

While parsing an expression, it was found to be missing at least one right parenthesis.

120

This WINDOW sub-command may not be specified in the configuration file.

Explanation

A window command was found in a configuration file, but the specified subcommand can not be issued from this file.

121

Only KEYS/WINDOW commands may be specified in the configuration file.

Explanation

While reading the configuration file, a command other than the keys or window command was found.

122

This CONFIG sub-command may not be specified in the profile.

Explanation

The 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.

124

The cursor is not in any window.

Explanation

A window command or text was entered, but the cursor was not in any window.

125

The cursor is not in valid window area.

Explanation

A window command or text was entered, but the cursor was not in a valid window area.

126

The extracted line is too long.

Explanation

The text entered was too long.

127

A maximum of 40 watches is permitted.

Explanation

A watch command was entered, but the maximum number of defined watches is 40.

128

A format cannot be specified for "dump" style watches.

Explanation

A watch command was issued that specified dump, but it also specified a format. This is not supported.

129

This [sub-cmd] sub-command may only be specified in the profile.

Explanation

A window [sub-cmd] command was issued, but the intercepts, memory, and config sub-commands may be specified only in the profile.

131

The format specification is invalid or causes a buffer overflow.

Explanation

While formatting a string, either an invalid format was found, or a buffer overflow occurred.

132

The debugger is entered due to signal [signal], abend code [code].

Explanation

An abend [code] in the program being debugged has occurred, causing signal [signal] to be received.

133

RESUME may be issued only when the program is stopped at either a line hook or an epilog hook.

Explanation

A 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.

134

Cannot RESUME. [explanation]

Explanation

A resume command was issued to resume in a function that is not in the current calling stack.

135

Unable to locate line within specified function. Not RESUMEd.

Explanation

A resume function-name line-number command was issued, but the specified line number does not appear in the specified function.

136

Unable to locate line within current function. Not RESUMEd.

Explanation

A resume line-number command was issued, but the specified line number does not appear in the current function.

137

Writing to storage report output file [filename]. [errno]

Explanation

An attempt to write a storage report record to file [filename] failed. [errno] will be non-blank if an error number was provided.

138

Return code of SYSTEM [command]: [rc].

Explanation

A system [command] command was issued, but the [command] returned a non-zero return code [rc].

139

Debugger forcing program termination.

Explanation

An error occurred during debugger initialization. The debugger terminates.

141

There is insufficient memory for the debugger to start up.

Explanation

During debugger initialization, it was determined that there is not enough storage to start the debugger. The debugger terminates.

142

Debugger unrecoverable internal error.

Explanation

The debugger encountered an internal error. The debugger terminates.

Action

Contact SAS/C Technical Support.

143

Debugger recoverable internal error. Traceback follows:

Explanation

The debugger encountered an internal error that it can recover from.

Action

Contact SAS/C Technical Support.

144

Not enough functions in calling sequence. Enter WHERE to display traceback.

Explanation

A transfer command or a scope command was issued but a function was specified that is not in the current calling segment. WHERE will show the current sequence.

145

Save areas overlaid - traversal of calling sequence stopped.

Explanation

An overlay was detected while traversing the call chain.

Action

Use the storage command to assist in locating the overlay.

146

Cannot evaluate expression. [expression]

Explanation

The specified expression [expression] is invalid, or multiple expressions were specified.

147

WHATIS does not support this type.

Explanation

A 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.

Action

148

[message]

Explanation

An error occurred during execution of a COPY, MONITOR, or WHATIS command. [message] describes the error.

149

Cannot create debugger temporary file.

Explanation

A file open failed for the debugger temporary file.

150

Debugger temporary file may have run out of space.

Explanation

While writing a debugger virtual page to the scratch file, an error occurred. 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. On MVS, 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)
On CMS, allocate a bigger read-write minidisk.

151

Cannot evaluate WHEN condition "[condition]". [message] Debugger will BREAK. ON commands, if any, are not executed.

Explanation

An invalid when condition has been encountered. Execution stops and any specified on commands are ignored.

152

Cannot find function "[function]" in file "[filename]".

Explanation

An attempt to find function [function] in file [filename] failed. This should not be possible with a complete debugger file.

Action

Contact SAS/C Technical Support.

153

Message buffer overflowed while processing expression.

Explanation

During the evaluation of an expression, the message buffer would not hold all message text.

154

No debugger macro variable defined for "[macro-name]".

Explanation

A define macro-name was issued, but there is not a macro named [macro-name].

155

Macro redefinition. Old definition was: [old-macro-def].

Explanation

A define macro-name "new-macro-def" was entered. macro-name already existed with a definition of [old-macro-def]. The previous macro definition is replaced by the specified definition.

156

No debugger macro variable defined for "[macro-name]".

Explanation

An undef macro-name was issued, but there is not a macro named [macro-name].

157

TRANSFER not performed due to a memory access exception.

Explanation

A transfer command failed due to a memory access exception.

158

Cannot evaluate expression. [expression]

Explanation

A transfer command was entered with an invalid expression specified.

159

"[variable]" is not a scalar: cannot TRANSFER.

Explanation

A transfer command was issued, but the specified variable is not scalar.

160

TRANSFER (DUMP / STR) expression should be of pointer type.

Explanation

A transfer, variable, dump, or str command was issued, but expression specified was not a pointer.

161

TRANSFER (DUMP / STR) string too long - insufficient memory.

Explanation

A transfer, dump, or str command was issued, but the expression specified was too long.

162

TRANSFER not performed: REXX/CLIST variable name "[variable]" or value "[variable]" is invalid.

Explanation

A transfer command was issued, but either the specified REXX or CLIST variable name or the value is invalid.

163

TRANSFER not performed: REXX/CLIST environment not active.

Explanation

A transfer command was issued, but there was no REXX or CLIST exec running.

164

TRANSFER not performed: environment does not have support for TSO CLIST variable interface.

Explanation

A transfer command was issued, but the execution environment does not have support for the CLIST variable interface.

165

TRANSFER not performed: (execshv) code [rc].

Explanation

A transfer command was issued, but execshv returned a non-zero return code [rc].

166

TRANSFER not performed. [explanation]

Explanation

A transfer command was issued, but it was not performed, as indicated by [explanation]. Where [explanation] is one of the following strings:

167

Storage [storage_begin]:[storage_end] freed. Monitor(s) dropped:

Explanation

The storage at location [storage_begin] through [storage_end] has been freed through the freeing of heap storage. All monitors that reference this storage are dropped.

168

Load module [loadm] unloaded. Monitor(s) dropped:

Explanation

The storage for a load module [loadm] has been freed as the result of the module being unloaded. All monitors that reference this storage are dropped.

169

Cannot evaluate "[expr]". [desc]

Explanation

A monitor command was issued, but the specified expression could not be evaluated because of [desc].

170

This type of expression cannot be monitored.

Explanation

A 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.

171

The debugger profile "[profname]" execution failed, return code [profrc]. [errno]

Explanation

The debugger profile [profname] returned a non-zero return code.

172

System REXX interface failed. [errno-text]

Explanation

A call to a REXX function failed because of an error in the REXX interaction.

173

Cannot process EXEC command - not interactive.

Explanation

The execution of an EXEC/CLIST was not attempted because it was not running in TSO.

174

Cannot process EXEC or % command - not interactive.

Explanation

The execution an EXEC/CLIST was not attempted because it was not running in TSO.

175

EXEC command failed. Return code: [code]

Explanation

On CMS, EXEC returned a non-zero return code [code].

176

EXEC or % command failed. Return code: [code]

Explanation

On MVS, an EXEC/CLIST returned a non-zero return code [code].

177

Return code: [code]. Future invocation of CLISTs/EXECs may not work.

Explanation

An error occurred during the execution of a CLIST/EXEC that may cause future invocations to fail.

178

Line was too long and discarded: [text]...

Explanation

During the fetch of a line to execute, it was discovered that the line was too long.

179

Unable to open debugger input file.

Explanation

An attempt to open the debugger input file (DBGIN) failed.

180

Ddname "[ddn]" not allocated. Enter "[ddn]" data set names.

Explanation

DDname [ddn] is not allocated, and you are prompted for the dataset name.

Action

Enter the corresponding data set name to be opened with this DDname.

181

Ddname "[ddn]" not allocated.

Explanation

DDname [ddn] was not allocated after the user prompt. Either an invalid data set name was specified or no input was specified.

182

Unable to open debugger log file. See preceding runtime messages for details.

Explanation

A log append command was entered, but for the log file failed to open.

183

Cannot list source. [explanation]

Explanation

A list command was issued, but the source could not be listed. The [explanation] should give a description of the problem encountered.

184

Cannot scroll back [line-count] lines - scrolling to the top.

Explanation

The debugger attempted to scroll back [line-count] lines, but that would scroll the source before the first line. The debugger stops scrolling at the top of the file.

185

[line] line of range is set to 1.

Explanation

A list command was issued with invalid start or end values. The described range value is set to 1. [line] is First or Last.

186

No listing - last line of range ([last]) less than first line of range ([first]).

Explanation

A 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.

187

Source file "[filename]" is empty.

Explanation

The source file [filename] did not contain any source.

188

*** End of source ***

Explanation

Indicates the normal end of the source code.

189

End of source on line [linenum].

Explanation

A list command was issued that specified a starting line greater than the last line of the file, [linenum].

190

Ignoring member [member name] specified in DBGSRC definition.

Explanation

The DDname DBGSRC is defined and a member name was specified in that definition. The member name will be ignored. Specification of a member name is not supported.

191

The debugger file for this compilation is not available - cannot list source.

Explanation

A list command was issued (perhaps implicitly on entry to a function), and the debugger file could not be found.

Action

If the debug source is accessible, use 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.

192

fopen unsuccessful. See preceding runtime messages for details.

Explanation

A file open was attempted, but failed. Other messages should indicate the cause of this problem. Preceding messages may not be present for HFS files.

193

Full-screen initialization failed: [expl].

Explanation

While processing a window on command, the initialization of the full-screen environment failed for reason [expl]. Line-mode will be used.

194

[hgt] window height is greater than the maximum height allowed for the window [window]. Set to [max].

Explanation

A config command was issued for a window [window], but a height [hgt] was specified that is greater than the maximum allowed for that window, and was reset to maximum [max].

195

[window] window height is less than minimum ([num]). Set to [num].

Explanation

When displaying a window an invalid height was entered. The minimum size is used.

196

[window] window row position is invalid for height specified. Set to [row].

Explanation

When displaying a window, the specified row would not allow all of the window to be displayed. Row [row] is used.

197

[window] window width is greater than the maximum width allowed for the window ([wid]). Set to [max].

Explanation

When displaying a window, a width was specified that was greater than allowed for this window. [max] is used as a width.

198

[window] window width is less than minimum ([wid]). Set to [min].

Explanation

When displaying a window, a width was specified that was less than allowed for this window. [min] is used as a width.

199

[col] window column position is invalid for width specified. Set to [val].

Explanation

A window config command was issued that specified a position that was invalid for the width of the window. An appropriate adjusted position [val] will be used.

200

Zero / Multiple windows of this name are present - use <> to point.

Explanation

A 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.

201

Unable to reopen basic window. Continue debugging in line mode.

Explanation

A window command command was issued, but the debugger was unable to open the window. Debugging will continue in line mode.

202

This WINDOW cannot be OPENed/CLOSEd.

Explanation

A 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).

203

Full-screen mode is on.

Explanation

A window on command was issued, but this debugging session is already in full-screen mode.

204

Unable to determine initial working directory, ".cdebugrc" not processed.

Explanation

The directory for the "run command" file could not be found.

205

This WINDOW subcommand is not valid in this window.

Explanation

A window command was issued, but is not valid for the specified window.

206

Full-screen window open(s) failed - switching to line mode.

Explanation

During execution of a window open command, the opening of the window failed. Line-mode will be used.

207

Insufficient memory specified for [window] window - amount ignored.

Explanation

A window open command was issued for the [window] window, but the memory size for the window was not sufficient. [window] is Browse, Command, Log, or Source. The specified value is ignored.

Action

Specify a memory size of at least the height of the window * 255.

208

Window limit reached: cannot open another window.

Explanation

A window open command was issued but the maximum number of subwindows have already been opened.

Action

Close a currently open window.

209

[sev] detected by [mod]: [errcd].

Explanation

A [sev] (Error or Warning) was detected by module [mod].

210

Insufficient memory for the [window] window - unable to allocate [size] bytes.

Explanation

A window command for the [window] window was issued, but [size] bytes of storage could not be allocated.

211

Line too long.

Explanation

A request to write a line to the log was attempted, but the line is too long.

212

No continuation line.

Explanation

An attempt was made to write a line to the log that indicated that there was a continuation line, but no continuation line was found.

213

Line [num] is not in any function - the request is ignored.

Explanation

A command was issued that specified a non-existent line number [num].

214

Multiple "r" commands may not be specified.

Explanation

Multiple runto line commands were entered.

Action

Enter only one runto command at a time.

215

Both "g" and "r" prefix commands may not be simultaneously specified.

Explanation

The g (goto) and r (runto) prefix commands were specified simultaneously. This is not supported.

216

Unable to popup window to process error: "[msg]". Change is ignored.

Explanation

An attempt to display a popup window failed. The original message is [msg].

217

Prefix-area commands may not be entered when no source is displayed.

Explanation

A prefix-area command is entered when there is no source displayed.

218

{mono Length of input line is greater than 255 characters. It is truncated to 255 characters.

Explanation

A line of input text is entered, but is longer than is supported.

219 Input is not being prompted for at this time.

Explanation

Text was entered in the Termin window, but no input was expected.

220

Unable to open the termin window. Input intercept disabled.

Explanation

An attempt was made to open the Termin window for input, but the Termin window could not be opened. Input will be taken from stdin.

221

Unable to open the termout window. Output intercept disabled.

Explanation

An attempt was made to open the Termout window for output, but the Termout window could not be opened. Output will be sent to stdout.

222

Discarding input in [window] window.

Explanation

Input text was entered in an output window. The input is discarded.

223

Debugger file line-numbers do not correspond to source.

Explanation

A command was issued, and in the evaluation of that command, it was determined that the debug and source files did not match. This many indicate that the source file has been modified since the last compilation.

224

Section-name [section name] was not compiled DEBug (-d). There are no "hooks" in the code, and there is no debugger file available.

Explanation

In an attempt to read the debugger file, it was determined that the code had not been compiled with the debug option. This file cannot be debugged with the debugger.

Action

Recompile the module, specifying the debug option.

225

No debugger file - open failed, see runtime messages for details.

Explanation

The debugger file was not found. Preceding messages may not be present when opening HFS files.

Action

If the modules were compiled using the 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.

226

Debugger file "[filename]" is invalid and not used.

Explanation

While reading a debugger file, it was determined that the file was invalid. The debugger file is not loaded.

Action

Recreate the debugger file.

227

Debugger file "[filename]" is from Release 5.00 or before, which is not supported by this debugger.

Explanation

While reading a debugger file, it was determined that the file was generated by a Release 5.00 or earlier compiler, which is not supported by this level of the debugger. The debugger file is not loaded.

Action

Recompile the source with a more current level of the the compiler.

228

Debugger file [filename] was not created in the same compilation as the object ([filename]).

Explanation

On CMS, while reading a cached debug file, it was determined that the debug file did not have the same timestamp as the object deck. No other debugger file exists. The file is not debuggable.

Action

Recreate or locate the current debugger file.

229

Debugger file for section name [section name] was not created in the same compilation as the object ([filename]).

Explanation

On MVS, while reading a cached debug file, it was determined that the debug file did not have the same timestamp as the object deck. No other debugger file exists. The file is not debuggable.

Action

Recreate or locate the current debugger file.

231

Dump terminated due to a memory access exception at ??.

Explanation

A dump command was issued, but a memory access exception occurred. Dumping stops.

232

Cannot evaluate "[expression]". [msg]

Explanation

Could not evaluate [expression]. The reason is stated in [msg].

233

Memory access exception at [address] while determining string length.

Explanation

A dump command was issued, and an access exception occurred when loading the string length.

234

"[operand]" must be of address type.

Explanation

A dump command was issued, but the operand specified was was not an address type.

235

A count may not be specified for an expression of this type.

Explanation

A print command was issued with a count, but a count cannot be specified with this data type.

236

Support for specifying a "TAG" type within parentheses after the expression to be printed has been dropped. Use casts to achieve a similar result.

Explanation

In previous releases (prior to 5.50) it was possible to specify a TAG after an expression. Now, simply cast the value to the appropriate type.

237

A "COUNT" may not be specified if the output is redirected to the Print window - the "COUNT" is ignored.

Explanation

A 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.

238

Unable to access "[var]" due to a memory access exception.

Explanation

During the access of the bit-field, pointer, function, arithmetic, array, or enum variable [var], an access exception occurred.

239

A number must follow the '-' or '+'.

Explanation

A scope command was issued with a + or - that was not followed by an integer.

240

A maximum of 1000 C macro expansions per line are allowed.

Explanation

More than 1,000 C macros were invoked in a single line.

241

C macro expansion caused input buffer overflow.

Explanation

Output from macro expansion caused an overwrite of the input buffer.

242

Cannot load special character table - default values used.

Explanation

An attempt to load the special character table (l$dcst) failed. A default of a one-to-one mapping is used.

243

No debugger macro defined for [macro].

Explanation

A debugger macro was invoked, but not found.

244

A maximum of 1000 macro expansions per line are allowed.

Explanation

More than 1,000 macros were invoked in a single line.

Action

245

Debugger macro expansion caused input buffer overflow.

Explanation

While expanding a macro, the resulting text caused an overflow of the input buffer.

246

No Configuration file specified.

Explanation

A config save command was issued, but no configuration file has been specified.

Action

Use the config file command to specify a configuration file.

247

Open failed for [filename].

Explanation

A storage or config save command was issued, but the output file [filename] could not be opened.

For storage, the file is designated as follows:

CMS:
cms: pgmname DBGSTG A
OE:
ddn:DBGSTG
MVS:
if ddn:DBGSTG is defined, the ddn is used, otherwise, dsn:userid.pgmname.DBGSTG is used.
For config save, the configuration file is specified with the config file command. On CMS, this filename is named DBCONFIG. On MVS, it is named either the specified filename or first-level-qualifier. CDEBUG.CONFIG(name).

248

No requests in list.

Explanation

A drop all or drop last command was issued, but there are no current requests to drop.

249

No request applies specifically to this location.

Explanation

An enable or disable command was issued, but there was nothing to modify.

250

Multiple requests apply to this location. '[request]' not performed.

Explanation

An enable (e) or disable (d) command was entered, but multiple requests apply to this location. The intended request must be specified.

251

Request number [num] already disabled.

Explanation

A disable command was entered, but the request number [num] had already been disabled.

252

Request number [num] does not exist.

Explanation

A disable or drop command was issued specifying a request number [num] that did not exist.

253

Last request already disabled.

Explanation

A disable last command was issued, but the last entry had already been disabled.

254

Request number [num] already enabled.

Explanation

An enable command was issued specifying a request number [num] that was already enabled.

255

Last request already enabled.

Explanation

An enable last command was issued, but the last request was already enabled.

256

[req] not installed. An identical request ([num]) already exists.

Explanation

A continue command was issued, but an identical request (request number [num]) already exists.

257

[req] not installed. A similar request ([num]) already exists. However, COUNT has been changed to [cnt].

Explanation

A continue command was issued, but request [num] already exists. The number of continue requests has been increased to [cnt].

258

Type of "[variable]" (target) is invalid for the [command] command.

Explanation

If [command] is 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.

259

A null list was specified: the [command] command will not change the target.

Explanation

If [command] is 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.

260

Assignment of a list to a scalar is invalid.

Explanation

An assign aggregate-type-expression=value-list command was issued, but aggregate-type-expression is a scalar-type-expression.

261

Cannot "[command]" class/struct/union type to scalar type.

Explanation

A [command] command was issued attempting to assign a class, struct, or union typed variable to a scalar variable.

262

Can only assign a structure/union declared with the same tag in the same compilation.

Explanation

An assign command was issued that specified structures or unions that were not declared with the same tag.

263

Need a list or class/struct/union to initialize a class/struct/union.

Explanation

An assign command was issued that specified either class, struct, or union but the assignment value was not a class, structure, or a union.

264

Ignoring excess item(s) in list.

Explanation

While processing in a list specified on an 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.

265

Type of "[expression]" (source) is invalid for the [command] command.

Explanation

A [command] was issued that specified an [expression] that is invalid for the command.

266

Need a list to initialize an array in a structure.

Explanation

An assign command attempted to assign a value to an array in a structure. A list must be specified.

267

Assigning a list to a scalar element of an array is not valid.

Explanation

An assign command attempted to assign a list to a scalar element. A scalar must be specified.

268

This version of the debugger does not support debugger files from Release [rel].

Explanation

A debugger file from Release [rel] was found, but is not supported.

Action

Use an appropriate level of the debugger, or recompile at the current level.

269

Memory access exception resulted when performing assignment / copy.

Explanation

The storage address specified on either the source or destination in an 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.

270

Source and target sizes are unequal.

Explanation

A copy command was issued and the specified source and target are not the same size.

271

[target] type of aggregate is invalid - simple type or enum type should be specified.

Explanation

A copy command was issued with an invalid target, where [target] is Implied target or Target.

273

The RETURN command may not be issued at this kind of hook.

Explanation

A return command may not be issued at this line in the function.

274

A List may not be specified for a function returning a scalar.

Explanation

A return command was issued that specified a list, but this function returns a scalar.

275

The RETURN command may not be issued at a SIGNAL.

Explanation

A return command may not be issued at this time.

276

A Return value may not be specified for a function returning void.

Explanation

A return command was issued with a value specified. This is not allowed for a function that returns void.

277

No return value specified for function returning int. Return is performed.

Explanation

A RETURN command was issued that did not specify a return value, but this function should return an int. The return is executed using the value in register 15 as an undefined int return value.

278

A Return value must be specified.

Explanation

A return command was issued that did not specify a return value but a return value needs to be specified.

279

Cannot RETURN class/struct/union to a function returning a scalar.

Explanation

A return command was issued attempting to return a class, struct, or union when the function should be returning a scalar.

280

The return value is not used by the caller - the RETURN is not performed.

Explanation

Because the return value is not used, the return value is not performed.

281

No debugger file is available for function [function].

Explanation

There is no debugger file for this function.

Action

If the function is a user compilable function, recompile with debugging information enabled, and invoke the debugger again. If a debug file does exist, issue the set search debug= command followed by a list command to attempt to reload the debugger file.

282

fputs() error while writing to configuration file [filename].

Explanation

An error occurred while writing to the configuration file [filename].

283

A missing or invalid % format [format] is specified.

Explanation

A print command was issued that specified more than one format, but only one format is allowed.

284

Format specification may not be specified for structures, but is used for all fields in the structure.

Explanation

A print command was issued that specified a format specification. It is ignored.

285

The function has no parameters.

Explanation

A 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.

286

Memory access exception resulted while accessing area to be monitored.

Explanation

During the evaluation of a monitor command, a storage access exception was recognized while referencing the area to be monitored. The monitor is not set.

287

Long message has been truncated.

Explanation

The debugger is attempting to print a message greater than its message buffer length. This is an internal error in the debugger. The message is truncated.

Action

Contact SAS/C Technical Support.

288

Not running in interactive mode - help not available.

Explanation

A help command was entered, but help is available only when running interactively.

289

DBGHELP must be allocated for access to the help system. The debugger could not execute the L$DBHELP CLIST to automatically allocate DBGHELP.

Explanation

A help command was entered, but the L$DBHELP CLIST did not complete successfully.

290

The Help key (PF[num]) cannot be redefined using a KEYS DEFINE command; instead, use the KEYS HELP command.

Explanation

The keys define command was issued attempting to set the Help key.

291

[Command | Log] line has been truncated - lines in the [window] window cannot exceed 251 characters

Explanation

A command was entered that exceeded 251 characters. Either the command line or a log line has been truncated.

293

No entry for "[text]" in the help system.

Explanation

A help command was issued, but [keyword] was not found.

294

Terminal width ([term]) exceeds "[max]" columns. Problems may occur.

Explanation

The width of the terminal exceeds [max]. Display results are not predictable.

295

Unable to access the help system.

Explanation

A help command was issued, but the help file could not be opened.

296

The ISPF environment is not active.

Explanation

A pfkey that is assigned to ISPF was pressed, but ISPF is not active.

297

The Help key cannot be assigned to ISPF.

Explanation

An attempt was made to assign the help key to ISPF. There must be a valid Help key.

Action

To assign the specified pfkey to ISPF, first reassign another, non-ISPF key to be the help key, then the specified key can be reassigned.

298

A key assigned to ISPF cannot be made the Help key.

Explanation

An attempt was made to assign the help function to a key already assigned to ISPF.

300

Insufficient memory to hold macro name longer than [cnt] characters - the macro has been discarded.

Explanation

While reading the preprocessor symbols, a macro name was encountered with a length greater than [cnt]. The macro cannot be used in the debugger session.

301

The configuration has been written out to [filename].

Explanation

A config save command was issued and the configuration was successfully written to file [filename].

302

The debugger file [filename] is not complete.

Explanation

While reading a debugger file, the end of file occurred before all sections of the debug file were found.

303

Source file has shrunk to [num] lines (from [num] lines) after the debugger first opened it.

Explanation

While trying to read a line from the source, an error occurred. This usually means that the source file has been replaced since the first time this source was loaded.

Action

Restart the debugger session. If this does not solve the problem, and the source was not replaced, then it is probably an internal debugger error.

304

More than "[max]" browse windows cannot be simultaneously open.

Explanation

Only [max] browse windows can be opened at the same time.

305

A debugger file is not available: cannot set breakpoints on lines in function [function].

Explanation

An attempt to open the debugger file was unsuccessful.

Action

Issue the appropriate set search debug command to locate the debugger files, and issue the list command to reattempt the loading of the debugger file.

306

Cannot set a breakpoint as function [function] is split across source files.

Explanation

The debugger does not support functions that start in one source file and end in a different source file.

307

Cannot set a breakpoint on line [num] as function [function] starts on line [start-num] and ends on line [end-num].

Explanation

An attempt was made to set a breakpoint at a line number outside the line-number range of the function.

308

Cannot set a breakpoint on line [num] of function "[function]" as there is no code generated for this line.

Explanation

An attempt was made to set a breakpoint at a line with no code.

309

Debugging a function in section-name [sname] ...

Explanation

Specifies the section name that was being debugged when the following errors were discovered. Other messages will be issued after LSCD309. Please see messages LSCD359 and LSCD363.

310

Forcing a break as the debugger could not install a line hook breakpoint. The request with the invalid line number should be dropped.

Explanation

A break func nnn command was entered, but the line did not exist. A dummy break was installed.

311

Could not open debugger startup file "[filename]". [errno_text].

Explanation

Could not open the "run command" file. Note that the file has different filenames according to operating system:
CMS:
//cms: cdebug rc *
MVS:
If DD DBGRC is allocated, then the DD is used; otherwise,
dsn: userid.cdebug.rc
OE:
//hfs:login-directory/.cdebugrc

312

After a function name, only an integer and a ')' can follow a '('.

Explanation

The function name is incorrectly specified.

313

A function name specified within double qoutes is invalid.

Explanation

The function name is incorrectly specified. It is probably a C++ specification that is incorrect.

314

AUTO EXTNAME cannot be changed when the AUTO CXX is option is on.

Explanation

An auto extname command was issued, but the extended name support cannot be changed while the cxx option is on.

315

Could not resolve function name "[function]" using merged debugger files.

Explanation

The name that was specified was not found in any of the loaded routines.

316

There is just one instance of function name [func] in the merged debugger files - the subscript is ignored.

Explanation

A function name [func] was specified with a subscript, but there is only one function with that name. The subscript specification has no meaning.

317

A function subscript of zero may not be specified in this command.

Explanation

A function name was specified in a command, but a subscript of zero was also specified. Zero is not supported.

318

Only C macros with no arguments are supported by the debugger.

Explanation

Parms were specified with a C macro, but parms are not supported.

319

Cannot access auto variables from a lexically enclosing function.

Explanation

An attempt was made to reference an automatic variable from an invalid scope.

320

Invalid type of expression for a reference type RETURN.

Explanation

A return command was issued, but a reference type must be specified.

321

Cannot access members from a lexically enclosing class.

Explanation

An attempt was made to reference a number from an invalid scope.

322

Using this particular instance of the class for monitor purposes.

Explanation

While debugging a class member function, a 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.

323

The ASSIGN command may not be used with an object which has, or an object whose member has, a base class.

Explanation

An assignment can only be made to a base class.

324

Requests on all instances of an overloaded function may only be set on "calls", "entry", or "return" type hooks.

Explanation

An on command specified a hook of other than call, entry, or return (or *) for an overloaded function that is not supported.

325

The RETURN command may not be used to return an object which has, or an object whose member has, a base class.

Explanation

A 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.

326

Memory access exception accessing virtual base class [class].

Explanation

An access exception occurred while processing a monitor event that attempted to access the virtual base class [class].

327

Out of memory - command output is not complete.

Explanation

An attempt to write a message failed, probably because of an out-of-storage condition. If this message was a result of a command, the command may or may not have executed successfully.

328

Classes are inherited: address/offset translation performed: [address] --> [offset].

Explanation

A conversion between pointers or member pointers of different related classes was performed. This message documents the change in object addresses or in member pointer offsets.

329

The RETURN command may not be used to return an object which is returned using a copy constructor.

Explanation

A return command was issued that specified a copy constructor. This is not supported.

330

Invalid / inconsistent type of expression for a reference type RETURN.

Explanation

A return command was issued that specified a reference type that was inconsistent with the function definition.

Action

Look at the function definition.

331

Only a pointer to a member or zero can be assigned to a pointer to a member.

Explanation

An invalid source expression was supplied on an assign command.

332

Unable to perform the ASSIGN command. [reason]

Explanation

An assign command was entered, but could not be performed because of [reason].

333

The "function_name:" prefix is no longer supported. The SCOPE command may be used to provide similar, though enhanced, functionality.

Explanation

An old form of function_name: was used in an expression to provide for scoping, but this form is no longer supported.

334

Could not find function "[function]" in calling sequence. Enter WHERE to display traceback.

Explanation

A scope command was issued, but the specified functions were not in the calling sequence. The command where indicates the calling sequence.

335

Could not perform the command as there is no log file defined.

Explanation

A log capture or log file command was entered, but there is no log file.

336

The current log file is [filename].

Explanation

A log file command was entered. The current file is [filename].

337

The log buffer is currently empty.

Explanation

A log capture command was entered, but there are no lines to capture.

338

Error writing log file. Output logging has been turned off.

Explanation

An error occurred while writing to the log file. Writing to the log file is terminated.

339

The WINDOW FIND command is not supported in the [window] window.

Explanation

A window find command was issued for window [window], but this window does not support the find command.

340

Cannot find search string: [str]

Explanation

A window find command was issued, but the search string [str] was not found.

341

Treating "[name]" as a C function name...

Explanation

A hook was issued, using [name] as a C name.

342

"[variable]" is not in scope.

Explanation

A browse command was issued, but the location specified was not addressable in the current scope.

343

A subscript after the function name is not valid in this context.

Explanation

A function name with a subscript was specified, but a subscript is not valid on this command.

344

The name of the file to be browsed has not been specified.

Explanation

A browse command was entered, but the no file has been specified.

345

A pointer to a member can only be assigned to a pointer to a member.

Explanation

An invalid target expression was supplied on an assign command.

346

The signal occurred at offset [address] which is greater than the size of the function ([address]).

Explanation

A signal occurred at an offset that is outside the function.

347

"[expr]" is an expression of type void and cannot be PRINTed.

Explanation

A print command was issued that specified a value [expr] that evaluated to a type void. There is nothing to print.

348

Underflow in floating-point constant.

Explanation

During the conversion of a text value to a floating-point constant, an underflow occurred.

349

Overflow in floating-point constant.

Explanation

During the conversion of a text value to a floating-point constant, an overflow occurred.

350

Couldn't find template "[template]" in the [name] list.

Explanation

A set search file-tag-"template" command was issued, but the specified template, or templates, to remove were not found.

Action

Issue a 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 Software: Changes and Enhancements, Release 6.50 for information about the set search command.

351

An invalid conversion specifier has been specified in a template. Invalid text begins at "[text]".

Explanation

In a set search command, a template was specified that contained the invalid conversion specifier [text].

Action

Correct the template specification. See SAS/C Software: Changes and Enhancements, Release 6.50 for a description of search templates.

352

A [specifier] conversion specifier must be followed by another conversion specifier.

Explanation

In a 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.

Action

Correct the template specification. See SAS/C Software: Changes and Enhancements, Release 6.50 for a description of search templates.

353

The "[specifier]" conversion specifier can only be used for a compilation on [system].

Explanation

A conversion specifier of %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] that is being debugging. Where [system] is either MVS or CMS, the current template is skipped and processing continues with the next template.

Action

Use a conversion specifier appropriate for the compiling operating system.

354

The "[specifier]" conversion specifier cannot be used when there is no file name available.

Explanation

A defined conversion specifier was used in a 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.

Action

Either define the original filename or use a section name.

355

Compilation with section name "[section name]" is pre-Release 5.00C and not supported by this debugger.

Explanation

The level of the compiler used with the executed code is not supported by this version of the debugger.

356

Source files compiled on [os1] cannot be debugged on [os2] without using SET SEARCH [type] commands to access files.

Explanation

When compiling on one operating system [os1] and debugging on another operating system [os2], because of file name convention differences, the set 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.

Action

Issue the set search command to identify the files necessary for the debugger. See SAS/C Software: Changes and Enhancements, Release 6.50 for information about the set search command.

357

This format of the debugger file name is not supported: [filename].

Explanation

Either the original filename [filename] could not be made into the CMS filename format, and a trace for the debug file had been enabled, or the [filename] has invalid opening and closing parentheses. The member name must be preceded by an open parenthesis, and followed by only one closed parenthesis. In either situation, the open file processing is terminated.

Action

None, unless this error is unexpected, then issue a set search debug ? command and examine the returned templates and original filename displayed in this message.

358

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.

Explanation

The level of the compiler used to compile the source being debugged is incompatible with the use of templates in the definition of set search and set cache commands.

Action

If the debugger fails to find the files for debugging, then either recompile the modules using a more recent compiler, or make sure that files still reside in the same datasets as when they were compiled.

359

Tried to open [type] type file [where] "[filename]". [error-info].

Explanation

There are two possible explanations. A [type] filename, either the original filename or one that was generated from a template that was specified with the SET SEARCH [type] command or the SET CACHE (if [where] is "in cache") command, may not have been opened because of [error-info], and tracing for this file type had been enabled. Otherwise, an open of a [type] file was attempted and failed because of [error-info] and tracing for the file type had been enabled. In either case, processing continues with the next template.

Action

See Appendix 2, "ERRNO Values", for the various errno values that can be returned from file open if this error is not expected.

360

Debugger recoverable internal error. Inconsistent value: [value]. Traceback follows:

Explanation

An internal error has occurred in the debugger. The value [value] is inconsistent with earlier debugger logic. The requested function is not executed. An execution traceback follows.

Action

Contact SAS/C Technical Support.

361

Debugger recoverable internal error. Inconsistent values: 1: [num], 2: [num]. Traceback follows:

Explanation

An internal error has occurred in the debugger. The value [values] are inconsistent with earlier debugger logic. The requested function is not executed. An execution traceback follows.

Action

Contact SAS/C Technical Support.

362

The "[specifier]" conversion specifier can only be used in templates for [type] type files.

Explanation

When [type] is not userinclude, the conversion specifier of %ddname can only be specified for user include templates in the set search userinclude statement. Command processing ends.

Action

Specify a valid template. See SAS/C Software: Changes and Enhancements, Release 6.50 for information about the set search command.

363

[type] type file "[filename]" found.

Explanation

A filename generated in a template specified for the file type [type] in a set search command was successfully opened and tracing was enabled for this type. File processing continues.

Action

If a successful open was unexpected for this template, use 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 Software: Changes and Enhancements, Release 6.50 for information about the set search command.

364

Tried to open DEBUG type CACHE file "[filename]". [errno_text]. The debugger will not use the cache mechanism for this compilation.

Explanation

A cache filename had been specified, but could not not be created.

Action

Specify a valid cache name. See SAS/C Software: Changes and Enhancements, Release 6.50 for information about the set cache command.

365

Tried to write to DEBUG type CACHE file "[filename]". [expl]. The debugger will not use the cache mechanism for this compilation.

Explanation

While attempting to copy the debugger file to cache, an error occurred due to [expl]. The cache file will not be used for this debugger file.

366

Tried to remove "[parts]". [error-info].

Explanation

While reading in a debugger file, an error occurred that caused the debugging information to be considered invalid, but the attempt to free the parts of the file that had been read failed.

367

The time-stamp of the debugger file ([filename]) in CACHE is different from the time-stamp of the object code ([filename]). The cache file will not be used.

Explanation

While reading in a debug file from cache, it was determined that the date of the object code was different from the cache and a non-cached debugger file exists, so it will be used instead of the cached version. The cached debug file is ignored.

368

The debugger file in "[filename]" will be copied to the CACHE location "[location]".

Explanation

A debugger file was opened, and a cache file is defined, so the debugger file will be copied to the cache.

369

Debugger unrecoverable internal error. Inconsistent value: [value].

Explanation

An internal error has occurred in the debugger. The value [value] is inconsistent with earlier debugger logic. The requested function is not executed. An execution traceback follows.

Action

Contact SAS/C Technical Support.

370

Debugger unrecoverable internal error. Inconsistent values: 1: [num], 2: [num].

Explanation

An internal error has occurred in the debugger. The value [values] are inconsistent with earlier debugger logic. The requested function is not executed. An execution traceback follows.

Action

Contact SAS/C Technical Support.

371

Debugger unrecoverable internal error. Inconsistent values: 1: [num], 2: [num], 3: [num].

Explanation

An internal error has occurred in the debugger. The values are inconsistent with earlier debugger logic. The requested function is not executed. An execution traceback follows.

Action

Contact SAS/C Technical Support.

372

The target of the [command] command, "[target]", is not in the address space of the program.

Explanation

The specified variable [target] is not addressable in this address space. The [command], assign or copy, can only be used to modify variables in the current address space.

373

The debugger is terminating due to lost communication connection with remote subject program.

Explanation

The debugger has lost communications with the program being debugged. The debugger exits, and the state of the program being debugged is unknown.

374

PRINT not performed due to a memory access exception.

Explanation

While formatting a string, a memory access exception was encountered.

375

The RSYSTEM command is not supported by the environment of the program being debugged.

Explanation

This environment does not support the remote debugging system.

Action

See SAS/C Software: Changes and Enhancements, Release 6.50 for more information on the use of remote debugging.

376

The Debugger command "[command]" failed with return code [rc].

Explanation

A debugger command was issued, but failed with return code [rc].

377

RSYSTEM command "[command]" return code is [rc].

Explanation

A remote debugger command [rcmd] was issued, but returned a non-zero return code [rc].

378

Unable to set default search templates.

Explanation

During debugger initialization, a failure occurred while setting the default set search templates.

379

No executable profile "[filename]" found.

Explanation

For OpenEdition, no debugger profile was found. The filename for OpenEdition is .cdebug.

380

No transaction name specified.

Explanation

No transaction name was specified in the command line. The transaction name for the program to be debugged must be specified after 'DBUG' in the command line.

Action

Run the debugger again, specifying the transaction name that is associated with the program to be debugged.

381

The transaction name [transaction] is invalid or has not been defined to CICS.

Explanation

The transaction name given in the command line could not be found.

Action

Make sure that the transaction name is defined to CICS and is spelled correctly. You may be able to issue the following CICS command to verify that the transaction has been defined: CEMT INQUIRE TRANSACTION([transaction])

382

An EXEC CICS INQUIRE TRANSACTION [transaction] command failed with response code [code].

Explanation

CICS has returned an unexpected response code to an EXEC CICS INQUIRE TRANSACTION command. Some of the possible response codes include INVREQ and NOTAUTH.

Action

For the response code diagnostics and further explanation, see IBM publication CICS System Programming Reference. If the response code is NOTAUTH, then you may have to contact your site's CICS system administrator to obtain authority to issue this command.

383

The program [program] has not been defined to CICS.

Explanation

The program that is associated with the transaction that you are trying to debug has not been defined to CICS.

Action

Make sure that the program name is defined to CICS and is spelled correctly, and that the transaction definition points to the correct program name. You may be able to issue this CICS command to verify that the program has been defined: CEMT INQUIRE PROGRAM[program] Otherwise, contact your CICS system administrator for further assistance.

384

The program [program] is disabled.

Explanation

The program that is associated with the transaction that you are trying to debug has been marked as 'disabled' by CICS.

Action

To make the program available for use, you may be able to issue the following CICS command: CEMT SET PROGRAM [program] ENABLE Otherwise, contact your CICS system administrator for further assistance.

385

The program [program] can not be loaded by CICS.

Explanation

The program that is associated with the transaction that you are trying to debug has been correctly defined, but CICS is unable to load the program.

Action

Make sure that the program exists in a dataset that appears in the CICS DFHRPL library concatenation. Contact your CICS systems programmer for further assistance.

386

An EXEC CICS LOAD command for program [program] failed with response code [code].

Explanation

The program that is associated with the transaction that you are trying to debug failed to load.

Action

See the IBM CICS documentation for the response code diagnostics. If the response code is NOTAUTH, then a resource security check has failed. Contact your CICS system administrator for further assistance.

387

Application has not been linked with a SAS/C Release 6.00 or higher resident library.

Explanation

The program cannot be debugged because it was link-edited with an older version of the SAS/C resident library that does not support debugging under CICS.

Action

Relink the program to be debugged with a 6.00 or higher release of the SAS/C resident library, and then rerun the debugger.

388

EXEC CICS SEND MAP [map] failed with response code [code].

Explanation

The SAS/C debugger front-end transaction attempted to issue an EXEC CICS SEND MAP command that failed with the indicated response code.

Action

See IBM publication CICS Application Programming Reference for the response code diagnostics. Contact your CICS system administrator for further assistance.

389

An 'EXEC CICS SEND TEXT FROM [message]' command failed with response code [code].

Explanation

The SAS/C debugger front-end transaction attempted to issue an EXEC CICS SEND TEXT command to display an error message and the command failed with the specified CICS response code.

Action

See IBM publication CICS Application Programming Reference for the response code diagnostics. Contact your CICS system administrator for further assistance.

390

[file-tag] type files: TRACE is [status] and the search list is empty.

Explanation

In response to a set search file-tag ? command, if the list of file templates is empty, then this message will be displayed. Otherwise, see LSCD391, LSCD392, and LSCD393. The TRACE is either on or off.

391

[file-tag] type files: TRACE is [status] and the search list contains:

Explanation

In response to a 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.

392

(There is no CACHE specified.)

Explanation

In response to a set search debug ? command, if a cache file has not been specified, this message will be displayed. See LSCD391, LSCD393, and LSCD394 for more information.

Action

If desired, a cache file can be specified with cross-development debugging using the set cache command. See SAS/C Software: Changes and Enhancements, Release 6.50 for information on specifying a cache.

393

(CACHE is "[filename]".)

Explanation

In response to a set search debug ? command, a cache file has been specified as [filename]. See LSCD391, LSCD392, and LSCD394 for more information.

Action

If desired, the cache file can be eliminated with the set cache= command. See SAS/C Software: Changes and Enhancements, Release 6.50 for information on specifying a cache.

394

"[template]"

Explanation

In response to a 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 LSCD392.

Action

Templates can be modified, added, or removed with the set search file-tag =|+|- "template" command.

395

[string]

Explanation

A dblog command was encountered specifying the displayed [string].

396

[macroname] [macrotext]

Explanation

A define * or define [macroname] command was entered. [macroname] represents the defined macro name, and [macrotext] represents the replacement text for that macro.

397

No debugger macro variables defined.

Explanation

A define * command was entered to display all defined macros, but there are no macros currently defined.

398

break on [name1] - context of [name2].

Explanation

A hook was encountered but in another context.

399

Dimension of array "[array-name]" is not known.

Explanation

sizeof([array-name]) was specified in an expression, but the dimension of that array is not known.

400

Cannot apply sizeof to [name] type "[type]".

Explanation

sizeof([name]) was specified in an expression, but the [name] specified was of [type] function or bitfield which is not supported with sizeof.

401

Type of "[type]" is invalid for the "[oper]" operation.

Explanation

An expression was specified using an operand of type [type], but that type cannot be used with the [oper] operation.

402

"[name]" is not an lvalue.

Explanation

[name] was specified in an expression, but it cannot be used as an lvalue.

403

Cannot take the address of "[name]".

Explanation

[name] was specified in an address expression, but it is a constant or the size of an object, and an address cannot be generated.

404

Cannot apply & to the bit-field / enumeration constant "[name]".

Explanation

[name] was specified in an address expression, but it is a bit-field or an enumeration, and an address cannot be generated.

405

Computational error involving the "[oper]" operations with operands "[operand1]" and "[operand2]"

Explanation

During the evaluation of the [oper] operation, an exception occurred involving operands [operand1] and [operand2].

406

Subtraction cannot be performed: pointers "[ptr1]" and "[prt2]" point to objects of different sizes ([size1] and [size2]).

Explanation

A subtraction operation was specified using two pointers, [ptr1] and [ptr2], but they address objects of differing sizes [size1] and [size2]. This is not supported.

407

Types of "[var1]" and "[var2]" are invalid for subtraction.

Explanation

A subtraction operation was specified using two values, [var1] and [var2], but they are of types that do not support subtraction.

408

The only constant that can be compared with a member pointer is 0.

Explanation

A comparison operation was specified using a non-zero constant, but a pointer can only be compared to 0.

409

"[name]" is not a scalar.

Explanation

A logical AND or OR expression was specified, but one of the specified operands was not a scalar.

410

Type of "[oper1]" and/or "[oper2]" is invalid for the "[operation]" operation.

Explanation

A binary expression was specified using operands [oper1] and [oper2], but the type of one of the operands is not vaid for the [operation] operation.

411

One of "[oper1]" and "[oper2]" should be of pointer type and the other of integer type.

Explanation

A pointer addition expression was specified, but one of the specified operands should be a pointer and one should be an integer.

412

Only an identifier can precede the "::" operator.

Explanation

Something other than a name precedes the ::.

413

Cannot cast non-scalar type "[name]".

Explanation

The debugger does not support casting of non-scalars.

414

Casting to [type] is not allowed.

Explanation

The debugger does not support casting to [type].

415

"[var] is not a pointer to a member.

Explanation

A .* or ->* was specified in an expression, but the pointer specified was not a pointer to a class member.

416

The operator ".*" or "->*" is invalid for "[var]".

Explanation

A .* or ->* was specified in an expression, but the object addressed is not a class member.

417

Memory access exception accessing virtual function table pointed to by "[var]".

Explanation

A .* or ->* was specified in an expression, but the object address [var] is not valid.

418

Pointer to member, "[var]", is NULL.

Explanation

A .* or ->* was specified in an expression, but the object address [var] is NULL.

419

The [operator] operator cannot be applied to "[var]".

Explanation

A . or -> was specified in an expression, but the operation is not valid for the specified variable.

420

Only one level of "::" following a "." or "->" is supported.

Explanation

A . or -> was specified in an expression, with multiple :: operators, but only one is supported.

421

Only an identifier may follow a ".", "->", or "::".

Explanation

A ., ->, or :: was specified in an expression, but the operand following the given operation was not an identifier.

422

Memory access exception dereferencing pointer to member "[member]".

Explanation

During an attempt to convert a pointer to a member, an access exception occurred that indicates an invalid pointer.

423

Memory access exception accessing reference "[var]".

Explanation

During an attempt to convert an object to the referenced type, an access exception occurred indicating an invalid pointer.

424

Cannot obtain the "value" of "[var]" as it is not an lvalue.

Explanation

The specified variable [var] does not have a value appropriate for fetching. It must be lvalue capable.

425

Memory access exception accessing "[var]".

Explanation

During an attempt to obtain the actual value of [var], an access exception occurred indicating an invalid pointer.

426

No user commands have been installed.

Explanation

An install * command was issued to list all user commands, but none were found.

427

Listing source from [file]

Explanation

Line mode only. Indicates the file where the source is coming from, but none were found.

428

Resuming execution in function [func].

Explanation

A resume function command was issued and execution is resumed in function [func].

429

Resuming execution in function [func].

Explanation

A resume function-name lineno command was issued and execution is resumed in function [func].

430

MONITOR not installed, MONITOR [mon] already exists.

Explanation

A monitor command was issued when monitor [mon] already exists for the specified variable.

431

"[mon]"

Explanation

A monitored variable was modified and this message is printed as a result of recognizing that monitor event. This message is somewhat variable with the following values sometimes being present:

432

[bitfield_n] was [bitfield_o]

Explanation

A monitored bitfield was modified with a new value of [bitfield_n] and an old value of [bitfield_o]. If the bitfield was previously initialized, a tag of : uninitialized will be appended to [bitfield_o]. Note also that if an access exception occurs while examining the bitfield, the word IMPOSSIBLE will appear.

433

[dumped_n] was [dumped_o]

Explanation

A monitored field was modified with a new value of [dumped_n] and an old value of [dumped_o].

434

[value_n] was [value_o]

Explanation

A monitored field was modified with a new value of [value_n] and an old value of [value_o].

435

Pointer in class [class] to virtual base class [baseclass] has been corrupted.

Explanation

The internal pointer that is used to implement access to a virtual base has changed. This pointer never changes in the normal life of an object.

436

base | virtual base ...printed above....

Explanation

These are used when printing out a base class as part of a containing class. When printing a normal base, you get: base <tagname> {<base contents>} When printing a virtual base: virtual base <tagname> {<base-contents>} If the virtual base was already printed, you get: virtual base <tagname> ...printed above...

437

base | virtual base ...printed above....

Explanation

These are used when printing out a base class as part of a containing class. When printing a normal base, you get: base <tagname> {<base contents>} When printing a virtual base: virtual base <tagname> {<base-contents>} If the virtual base was already printed, you get: virtual base <tagname> ...printed above...

438

Command not processed as there are [cnt] functions named [func]:

Explanation

A function name was specified without a subscript, but there are [cnt] functions with name [func], a subscript must be specified.

Action

Reissue the command selecting the correct instance of the function.

439

[fi] [func]

Explanation

Displays the various instances of a particular function [func] along with the indices ([fi])to use when referencing a function instance with the debugger.

440

PF key definitions:

Explanation

A key list command was issued. This is the heading for the list of pfkey definitions.

441

[pfnum] [action]

Explanation

A key list command was issued, and [action] is the action when pf key[pfnum] is pressed.

442

The current configuration file is [filename].

Explanation

A config file command was issued, and the new configuration file is [filename]

443

line [num]: no suffix allowed for 'g'

Explanation

A prefix command g was entered for line [num] with a suffix, but suffixes are not allowed on the g prefix command.

444

line [num]: invalid prefix command

Explanation

A prefix command was entered for line [num], but it was not valid.

Action

Valid prefix commands are: b (break), d (disable), e (enable), g (goto and resume), q (query), r (runto), and t (trace).

445

module not in calling sequence MODULE: [mod] [num]

Explanation

A prefix command was entered with a module name, but the module [mod] is not in the current calling sequence.

446

invalid line number LINE: [num]

Explanation

A prefix command was entered with a line number [num] that is out of the range for this module.

447

Invalid [val] value. Enter value:

Explanation

An invalid character value [val] was entered.

Action

Enter a valid value.

448

Invalid [val] value. Enter value:

Explanation

An invalid decimal value [val] was entered.

Action

Enter a valid value.

449

Formats begin with a '%' FORMAT [format]:

Explanation

An invalid format was entered.

450

Invalid hex value. value [val]:

Explanation

An invalid hexadecimal value [val] was entered.

451

invalid expression specified EXPR [expr]:

Explanation

A when expression was entered that was invalid.

452

Set system breakpoint at [location] to activate the ESCAPE command.

Explanation

This message is issued at debugger initialization and indicates that a system breakpoint can be set at the specified location to enable the escape command.

453

C-macro "[orig]" replaced by "[repl]".

Explanation

The C-macro [orig] has been replaced with [repl].

454

An EXEC CICS RECEIVE MAP [map] command failed with response code [code].

Explanation

The SAS/C debugger front-end transaction attempted to issue an EXEC CICS RECEIVE MAP command and the command failed with the specified CICS response code.

Action

See the IBM CICS documentation for the response code diagnostics. Contact your CICS system administrator for further assistance.

455

A putenv() for some debugger environment variable failed.

Explanation

The SAS/C debugger front-end transaction calls putenv() to save the environment variables that are used by the remote debugger. One of these calls failed.

Action

The run time library should have produced a diagnostic message on the stderr transient data queue that describes the error condition that caused the putenv() to fail. Locate that message and proceed accordingly.

456

[command] ([length]) as [exec]

Explanation

Command [command] has been replaced with [exec].

Copyright (c) 1998 SAS Institute Inc. Cary, NC, USA. All rights reserved.