HP 3000 Manuals HP 3000 Manuals
Numbered Error Messages ( 219 - 1118 )
---------------------------------------------------------------------------------------
219 MESSAGE Line referenced is not an IN DATASET statement.
CAUSE In the SEARCH, SORT, DBGET, DBPUT, and DBUPDATE statements, a
line was referenced that was not an IN DATASET or PACKFMT
statement, but should be.
ACTION Add the missing statement.
---------------------------------------------------------------------------------------
233 MESSAGE Data base not open.
CAUSE The database being accessed has not been opened.
ACTION Open the database.
---------------------------------------------------------------------------------------
234 MESSAGE Improper dataset linkage in a THREAD statement.
CAUSE Data sets specified in a THREAD IS statement can be linked
together either by a path number or a variable name. The
program has not linked the data sets in either way.
ACTION Correct the linkage or use the default one.
---------------------------------------------------------------------------------------
235 MESSAGE No WORKFILE is active.
CAUSE No WORKFILE is specified during the execution of the SORT or
SEARCH statement.
ACTION Define the workfile by using a WORKFILE IS statement.
---------------------------------------------------------------------------------------
236 MESSAGE Unable to find the item in the IN DATASET list.
CAUSE The SORT statement cannot locate the key in any of the IN
DATASET statements referenced.
ACTION Add the key used in an IN DATASET statement.
---------------------------------------------------------------------------------------
238 MESSAGE Improper PATH or LINK specified in a THREAD statement.
CAUSE The PATH must be a valid path defined in the database schema
and the LINK variable, if used, must be the same data type as
the key.
ACTION Use the correct PATH number or LINK variable.
---------------------------------------------------------------------------------------
239 MESSAGE Workfile has wrong file type or open mode.
CAUSE A WORKFILE must be a binary file and opened for read and write.
One of these conditions is not satisfied.
ACTION Correct the file type or open mode.
---------------------------------------------------------------------------------------
240 MESSAGE Line referenced is not a THREAD IS statement.
CAUSE A THREAD IS statement is not being referenced in a SORT/SEARCH
operation.
ACTION Add the missing THREAD IS statement.
---------------------------------------------------------------------------------------
241 MESSAGE Workfile record size not long enough for thread list.
CAUSE The workfile's record size is too short.
ACTION Make sure the record size of a workfile is at least N 32-bit
words (or 2N 16-bit words) long; where N is the number of
datasets in the thread.
---------------------------------------------------------------------------------------
242 MESSAGE String variables not allowed in WORKFILE.
CAUSE Only numbers can be written into a workfile.
ACTION If a string is being written to a workfile, something is wrong
in the program, possibly between HP Business BASIC/XL and the
database. Check the program for errors and delete the string
from the output list.
---------------------------------------------------------------------------------------
243 MESSAGE The workfile is empty for a FILTER or SORT ONLY statement.
CAUSE The workfile is empty when a FILTER or SORT ONLY statement is
encountered.
ACTION Create the workfile first before these statements are executed.
---------------------------------------------------------------------------------------
244 MESSAGE Thread list contains more than 10 data sets.
CAUSE A maximum of 10 data sets is allowed in a thread.
ACTION Reduce the number of data sets in the thread.
---------------------------------------------------------------------------------------
245 MESSAGE Improper sort key used.
CAUSE Only simple variables can be used as key. Other types of
variables, such as array elements or substrings will result in
this error.
ACTION Change the key to use only simple variables.
---------------------------------------------------------------------------------------
246 MESSAGE The SORTINIT intrinsic failed during SORT.
CAUSE The SORT statement encountered some system level problem.
ACTION Use the CCODE function to check the condition code returned by
SORTINIT and consult the SORT-MERGE/XL General Users Guide for
an explanation of the error condition.
---------------------------------------------------------------------------------------
250 MESSAGE BEGIN REPORT does not reference a REPORT HEADER statement.
CAUSE The statement referenced by BEGIN REPORT is not a REPORT
HEADER.
ACTION Make sure BEGIN REPORT reference a REPORT HEADER statement.
---------------------------------------------------------------------------------------
251 MESSAGE Report Writer is already active.
CAUSE A Report Writer has been executed more than once or more than
one report was active at one time.
ACTION Only one active Report is allowed at any one time. Stop the
active Report before starting another one.
---------------------------------------------------------------------------------------
252 MESSAGE Duplicate Report Writer Section statement with line {line
number}.
CAUSE 1. A Report Writer Section which may only be defined once
within a report has been defined more than once.
2. Two or more HEADER N or TRAILER N statements use the same
value for N, resulting in two sections with the same level
number.
ACTION 1. Remove or consolidate sections so that only one such
section is defined in the report.
2. Change HEADER level values and TRAILER level values so that
each level is used only once.
---------------------------------------------------------------------------------------
253 MESSAGE Duplicate Report Writer Block statement.
CAUSE 1. More than one of the following occurs in a report
definition: PRINT DETAIL IF, GRAND TOTALS, PAGE LENGTH, PAUSE
AFTER, SUPPRESS PRINT AT, SUPPRESS PRINT FOR, LEFT MARGIN
2. TOTALS ON occurs in both a HEADER and a TRAILER section
with the same level number, or more than one TOTALS ON
statement occurs within one section.
3. Two or more BREAK WHEN or BREAK IF statements are defined
at the same level number.
ACTION 1. Remove the duplicate statements.
2. Consolidate the TOTALS ON statements for a section into one
statement. Include this in either the HEADER or TRAILER
statement, but not both.
3. All BREAK statements must specify different levels. Change
the level numbers to ensure that each BREAK WHEN and BREAK IF
statement refers to a unique level.
---------------------------------------------------------------------------------------
254 MESSAGE 1. Blank lines specified are larger than page size.
2. Blank lines value out of the range 0 to 255.
CAUSE These are both Report Writer errors:
1. Blank_top or blank_bottom values are greater than the
page_length value on the PAGE LENGTH statement.
2. Blank_top or blank_bottom values on the PAGE LENGTH
statement are out of range.
ACTION 1. (Blank_top + blank_bottom) must be < page_length.
2. Use a value in the range 0 to 255.
---------------------------------------------------------------------------------------
255 MESSAGE 1. Unacceptable value for Report Writer expression.
2. Subscript of report writer built-in function is out of
range.
CAUSE 1. A page_number expression is less than zero for one of the
following statements: PAUSE AFTER, PAUSE EVERY, SUPPRESS FOR,
SET PAGENUM. Or, a PAGE LENGTH < 0 or > 32767 was specified
(maximum XL page length: 2147483647).
2. Out-of-range subscript for one of the Report Writer
built-in functions:NUMBREAK, NUMDETAIL, RWINFO.
ACTION 1. Use a page_number value >= zero.
2. Consult the reference manual for the legal subscript range.
---------------------------------------------------------------------------------------
256 MESSAGE 1. Left margin too close to right margin of output file.
2. Left margin too close to right margin of COPY ALL OUTPUT
file.
CAUSE These are all Report Writer errors:
An attempt has been made to make the distance between the left
margin and the right margin less than the size of an output
field item.
ACTION The number of characters between the left margin and the right
margin must be set to at least the width of an output field
item. An output field item is initially 20 characters wide,
but can be set to 15.
---------------------------------------------------------------------------------------
257 MESSAGE 1. Report Writer statement illegal when a report is not active.
2. Attempt to evaluate report writer built-in when no report
active.
3. Report Writer operation outside the scope of an active
report.
CAUSE An attempt has been made to execute a report writer statement
or function which may not be executed when a report was not
active. Or, it may be that a report is active, but the
statement or function in question does not appear in the
subunit in which the report is active.
ACTION These statements and functions may only be executed when a
report is active. The BEGIN REPORT statement activates a
report. If the report is active in another subunit then you
can put the report and the statement or function which caused
the error in the same subunit, or the desired information can
be computed in the report subunit and passed to the other
subunit.
---------------------------------------------------------------------------------------
258 MESSAGE Effective page size too small.
CAUSE This indicates that the Report Writer blank line specifications
at the top and bottom of the page plus the number of lines in
the page header and page trailer sections is too large for the
size of page you are using.
ACTION Adjust the line specification on the PAGE LENGTH, PAGE HEADER,
or PAGE TRAILER statements so that at least three lines are
left on the page after subtracting out blank top, blank bottom,
header size, and trailer size.
---------------------------------------------------------------------------------------
259 MESSAGE Illegal execution of a Report Description section statement.
CAUSE All GOSUB statements activated from a Report Writer section
have not returned before the end of the section has been seen.
The end of the report writer section is marked by the execution
of any Report Section statement (HEADER, END REPORT
DESCRIPTION).
ACTION The program logic must be changed so that all GOSUBs have been
RETURNed from before the next report section statement is
executed.
---------------------------------------------------------------------------------------
260 MESSAGE Insufficient space for printed output within the current page.
CAUSE 1. There are no lines left on the page for Report Writer
output before the PAGE TRAILER or bottom blank lines are
printed.
2. The PAGE TRAILER prints more lines than are reserved.
ACTION 1. Check the size of the PAGE. Make sure that all Report
Section statements use the WITH <number> LINES clause, and that
the number of lines includes all output produced by the Report
Section. Make sure that DETAIL LINE uses the WITH clause and
that it includes all output which may occur before the next
DETAIL LINE or Report Section. Output from PRINT, PRINT USING,
and COPYFILE is considered report output. DISP, DISP USING,
DISP, and all Business BASIC system output (such as CAT, error
messages) are not considered report output.
2. Change the number of lines reserved in the WITH clause, or
change the number of lines printed by the PAGE TRAILER section.
---------------------------------------------------------------------------------------
261 MESSAGE Left margin specified is less than 1 or greater than printer
width.
CAUSE 1. LEFT MARGIN is set to 0 or less.
2. LEFT MARGIN is too close to the right margin for output
device.
3. LEFT MARGIN is too close to the right margin of COPY ALL
OUTPUT device.
ACTION 1. Set value to at least 1.
2. Set value to (at most) one tab stop (20 characters) from
the right margin.
3. LEFT MARGIN must also be at least one tab stop less than
the device size of the COPY OUTPUT device. Change the value of
left margin, turn off COPY ALL OUTPUT, or change the size of
COPY device.
---------------------------------------------------------------------------------------
264 MESSAGE Level number is out of the range 1 through 9.
CAUSE 1. The level number is less than zero or greater than nine in
one of the following: HEADER, TRAILER, BREAK WHEN, BREAK IF,
SUPPRESS PRINT AT.
2. The level number out of range in TRIGGER BREAK.
ACTION 1. If a constant is used, change the report definition to use
levels 1 thru 9. If an expression is used, this error is
reported during BEGIN REPORT execution. Verify that all level
number expressions return 0-9. (Level zero cause statement to
be ignored.)
2. Check value used by TRIGGER BREAK. Modify program logic or
TRIGGER BREAK statement to use 1-9.
---------------------------------------------------------------------------------------
265 MESSAGE (GRAND) TOTALS statement not active at the level requested.
CAUSE 1. There is no GRAND TOTALS statement in the report and
TOTAL(0,n) is used.
2. TOTAL(L,N) is used, but there is no TOTALS ON statement at
level L.
ACTION 1. Add a GRAND TOTALS statement, or change the TOTAL built-in
function to use a defined level.
2. Add a TOTALS statement at level L, or change the TOTAL
built-in function to use a defined level.
---------------------------------------------------------------------------------------
266 MESSAGE Sequence parameter out of range for (GRAND) TOTALS at desired
level.
CAUSE TOTAL(L, N) is used, but fewer than N expressions are being
totalled at level L.
ACTION Count the number of expressions defined at level L and change
the TOTAL call to ensure N does not exceed this number or add
more expressions to the TOTALS ON or GRAND TOTALS statement.
---------------------------------------------------------------------------------------
267 MESSAGE WITH number LINES value is negative or greater than page size.
CAUSE 1. The WITH value is less than zero.
2. The WITH value is larger than defined page size.
ACTION 1. Change the WITH clause to use zero or more lines. Check
expressions to ensure that negative numbers are not being used.
2. The WITH value may not be larger than first value to the
PAGE LENGTH command, unless PAGE LENGTH 0 is used. Change the
WITH clause and check expressions used in the WITH clause.
Check PAGE LENGTH command for correct page size specification.
---------------------------------------------------------------------------------------
268 MESSAGE OLDCV($) at requested level does not have a BREAK WHEN active.
CAUSE OLDCV(L) or OLDCV$(L) is being used, but level L does not have
a BREAK WHEN statement.
ACTION If level L exists, add a BREAK WHEN statement, or change a
BREAK IF statement into a BREAK WHEN statement. Check the
value of level to ensure the correct level is being indicated.
---------------------------------------------------------------------------------------
269 MESSAGE OLDCV($) function does not match control variable data type.
CAUSE 1. OLDCV(L) has been used with a string control variable.
2. OLDCV$(L) has been used with a numeric control variable.
ACTION Make sure that level L is the desired level. Change program
logic to ensure that the correct type is being checked.
---------------------------------------------------------------------------------------
270 MESSAGE Cannot redirect or copy output while a report is active.
CAUSE A SEND OUTPUT or COPY ALL OUTPUT statement was executed after
an active report started printing report output.
ACTION Redirect or start copying output before any report output. The
following statements will start report output: DETAIL LINE,
TRIGGER BREAK, TRIGGER PAGE BREAK, and END REPORT.
Alternatively, delay redirection or copy until the report has
ended (after END REPORT or STOP REPORT).
---------------------------------------------------------------------------------------
271 MESSAGE 1. Statement illegal during DETAIL LINE or page break
processing.
2. Statement illegal during page break processing.
CAUSE These are all Report Writer errors:
1. A DETAIL LINE or TRIGGER BREAK statement has been
encountered while a DETAIL LINE or TRIGGER BREAK statement is
executing.
2. A TRIGGER PAGE BREAK has been encountered while a page
break is being performed.
ACTION 1. Program logic must be changed such that only one DETAIL
LINE or TRIGGER BREAK statement executes at a time.
2. Program logic must be changed so that TRIGGER PAGE BREAK
does not execute while the PAGE HEADER or PAGE TRAILER section
is active.
---------------------------------------------------------------------------------------
272 MESSAGE END REPORT may not be executed while any report section is
active
CAUSE An END REPORT statement is encountered while a report section
(such as HEADER or REPORT TRAILER) is executing.
ACTION Program logic must be change so that END REPORT does not
execute during any break or page break processing.
Alternatively, use STOP REPORT to stop the report immediately.
---------------------------------------------------------------------------------------
273 MESSAGE STOP REPORT is already executing.
CAUSE A STOP REPORT statement is encountered during the processing of
a STOP REPORT statement.
ACTION Program logic must be changed to ensure that only one STOP
REPORT statement is executed at once.
---------------------------------------------------------------------------------------
284 MESSAGE Buffer for block read of JOINFORM is too small.
CAUSE The buffer in the call to bb_block_read is not large enough.
ACTION The buffer must be large enough to hold all characters from all
fields on the form plus one byte per field.
---------------------------------------------------------------------------------------
285 MESSAGE Form file inconsistent, possibly corrupted.
CAUSE When JOINEDIT needs to make several writes to a JOINEDIT form
file to complete an operation it marks the file "inconsistent"
before the first write and "consistent" after the last one has
been completed successfully. This is done because JOINEDIT
might abort after the first write but before the last one.
This protects against an internally inconsistent form file
being considered consistent.
ACTION There may be little that can be done in this case. Call HP for
assistance in piecing together your form file. It is helpful
to know what changes were made since the last time the form
file was consistent.
---------------------------------------------------------------------------------------
286 MESSAGE Error when writing to form. Form possibly not displayed
correctly.
CAUSE After displaying a form, BASIC does a cursor position check to
see if the cursor is where it should be after display of the
form. If it is not in the expected position then this error
occurs.
ACTION There are several reasons for this problem, such as a corrupted
form or a terminal that does not have enough memory to display
the form.
---------------------------------------------------------------------------------------
287 MESSAGE No input fields in form.
CAUSE The program has tried to read data from a form, but there are
no input fields on that form.
ACTION The form must have an input field for input to occur.
---------------------------------------------------------------------------------------
288 MESSAGE No output fields in form.
CAUSE The program has tried to write data to a form, but there are no
output fields on that form.
ACTION For output to occur while a form is active, there must be an
output field in the form. The exception to this is the LDISP
statement. See the JOINFORM appendix for an explanation of how
LDISP works when a JOINFORM form is active.
---------------------------------------------------------------------------------------
289 MESSAGE Output too long for output field {field_number}.
CAUSE This indicates that an output statement has tried to display a
value which is too long to fit in the current output field of
the active JOINFORM form.
ACTION The field must be made larger or the data smaller. The largest
field size is 80 characters.
---------------------------------------------------------------------------------------
291 MESSAGE Illegal operation inside form.
CAUSE The LENTER statement cannot be executed when the cursor is
located within the currently-active JOINFORM form.
ACTION Before executing the LENTER statement, use the CURSOR statement
to position the cursor to a location outside of the form.
---------------------------------------------------------------------------------------
292 MESSAGE Attempt to read past last input field of form.
CAUSE The input field pointer is undefined because all the fields on
the form have already been read.
ACTION Use the CURSOR IFLD(input_field_number) statement to position
the input field pointer to the desired field.
---------------------------------------------------------------------------------------
293 MESSAGE Attempt to write past last output field of form.
CAUSE The output field pointer is undefined because all the fields on
the form have already been written.
ACTION Use the CURSOR OFLD(output_field_number) statement to position
the output field pointer to the desired field.
---------------------------------------------------------------------------------------
294 MESSAGE Operation only allowed when a joinform is active.
CAUSE The IFLD, OFLD and CFLD clauses of the CURSOR statement are not
legal when a JOINFORM form is not active. The bb_block_read
routine cannot be called when a JOINFORM form is not active.
ACTION Use the OPEN FORM statement to activate a form.
---------------------------------------------------------------------------------------
295 MESSAGE Field number of CURSOR statement does not exist.
CAUSE There is no field on the form with the cursor field number
indicated by the IFLD, CFLD, or OFLD item on the CURSOR
statement.
ACTION Check your form definition (possibly by using JOINEDIT) to
determine the field number of the field you want the cursor to
be on.
---------------------------------------------------------------------------------------
296 MESSAGE Form not found in formsfile.
CAUSE An attempt to open a JOINFORM form failed because no form with
that name exists in the specified form file.
ACTION Make sure the formfile and formname are specified in the
correct order, "formname:formfile". Use JOINEDIT to display or
print the directory of forms in the formfile.
---------------------------------------------------------------------------------------
297 MESSAGE Found invalid data in formsfile.
CAUSE The name of the JOINFORM in the directory of the currently open
JOINFORM file does not match the name in the header of the
actual JOINFORM. The JOINFORM file has probably been corrupted.
ACTION Re-create the JOINFORM file using the JOINFORM editor to
salvage as much of the uncorrupted form information as
possible.
---------------------------------------------------------------------------------------
298 MESSAGE Input field "input_field" too long for variable "item_number".
CAUSE The value of a JOINFORM field, input_field, was assigned to a
string variable that is too short. The string variable is the
item_number variable specified in a variable list following
either an INPUT or ENTER statement.
ACTION Declare the length of the string variable to be greater than
its currently declared length.
ACTION Use a substring specifier following the variable in the
variable list. For example, 10 INPUT A$[1].
---------------------------------------------------------------------------------------
299 MESSAGE Numeric data expected in input field "input_field" for variable
"item_number".
CAUSE The value of the input field, numbered input_field, of the
currently displayed JOINFORM is not numeric. The item_number
variable in the variable list following an INPUT or ENTER
statement is numeric, so the non-numeric value cannot be
assigned.
ACTION Reenter a numeric value in the appropriate field in the
JOINFORM.
---------------------------------------------------------------------------------------
320 MESSAGE Invalid item name in PREDICATE statement.
CAUSE The value of the item name at the time of execution of the
PREDICATE statement is the null string.
ACTION Ensure that the value of the string expression that represents
the name of the database item to lock in the specified data set
is correct.
---------------------------------------------------------------------------------------
321 MESSAGE Invalid relational operator in PREDICATE statement.
CAUSE Run-Time: The only valid relational operators in a WITH clause
of a PREDICATE statement are one of:
=
>=
<=
Use of any other relational operators will cause an error.
ACTION Use only one of the above relation operators.
---------------------------------------------------------------------------------------
322 MESSAGE Predicate string too short for the predicate elements.
CAUSE The data set and item information that is being packed into the
predicate string is greater in length than the maximum length
declared for the string variable.
ACTION Increase the length of the string variable that is to be the
predicate string for the DBLOCK statement by declaring the
string with a length greater than 18 characters or increasing
the length of the already declared string.
---------------------------------------------------------------------------------------
323 MESSAGE Improper data set or base name used.
CAUSE String data set parameter specifying the data set name for a
BASIC statement that interfaces with TurboIMAGE exceeds the
maximum length of 16 characters.
ACTION Check the string to be certain that is less than 16 characters
in length before using the name as a data set name in a BASIC
TurboIMAGE statement.
---------------------------------------------------------------------------------------
324 MESSAGE Buffer not long enough for information returned by DBMS.
CAUSE If this error occurs with a DBGET the input buffer into which
the information in the database is to be transferred was too
short for the information actually written to the buffer. As a
result, the values of other program variables cannot be
guaranteed.
If this error occurs with a DBINFO the return string to which
the information is to be returned is too short for the
information actually written to the buffer. As a result, the
values of other program variables cannot be guaranteed.
ACTION Rewrite the program increasing the size of the input buffer or
return string. Recovery using ON DBERROR during program
execution is not advised because of possible program data
corruption.
CAUSE The return message string for the DBMESSAGE statement is not
the minimum length required for the call to the TurboIMAGE
library routine.
ACTION Rewrite the program, increasing the size of the string variable
used with the RETURN clause of the DBERROR statement.
---------------------------------------------------------------------------------------
800 MESSAGE Data Base Management System error "error_number".
CAUSE A TurboIMAGE database error with the error number,
"error_number", has occurred.
ACTION Look up "error_number" in the TurboIMAGE/XL Database Management
System and take the appropriate action. Additional information
can be made available in the program by use of the ON DBERROR
statement in conjunction with the DBINFO statement.
---------------------------------------------------------------------------------------
900 MESSAGE Error 2: Memory overflow.
Error 2: Not enough data space available for the local
variables.
Error 51: The file is not currently open.
Error 52: Improper group.account specifier.
Error 53: Improper file name.
Error 54: Duplicate file name.
Error 55: Permanent directory overflow.
Error 56: File does not exist.
Error 58: Operation inconsistent with file type or device
type.
Error 59: End of file found.
Error 62: File is protected, wrong lockword/password
specified.
Error 92: Cannot access file because file is being accessed
or is accessed exclusively.
Error 93: Operation inconsistent with file open mode.
Error 131: Device unavailable.
Error 134: Unit not ready or online.
CAUSE See the description corresponding to the respective error
number.
ACTION See the description corresponding to the respective error
number.
---------------------------------------------------------------------------------------
905 MESSAGE Improper fileset specified.
CAUSE An illegal file_set argument has been passed to the CAT
command.
ACTION Check the Accessing Files Programmer's Guide for a description
of file set specifications. Or, enter the MPE XL help system
and ask for help on the PARMS of the LISTF command.
---------------------------------------------------------------------------------------
906 MESSAGE Improper filetype specified in CATALOG.
CAUSE The argument to the TYPE parameter of the CAT command is not
legal. It is longer than five characters.
ACTION In CAT File_set$;TYPE=Type$ the Type$ string must not be longer
than five characters.
---------------------------------------------------------------------------------------
910 MESSAGE Improper operating system filename.
CAUSE The filename specified is not a legal MPE filename.
ACTION Consult the Accessing Files Programmer's Guide for information
on forming filenames.
---------------------------------------------------------------------------------------
911 MESSAGE Invalid lockword specified.
CAUSE An invalid file lockword was supplied.
ACTION A lockword must have no more than eight characters, beginning
with an alphabetic character and followed alphanumeric
characters. Check that the specified lockword has these
characteristics.
---------------------------------------------------------------------------------------
912 MESSAGE CATALOG's work-file size has been exceeded.
CAUSE The CATALOG command directs the output from the MPE :LISTF
command to a temporary file. This message appears when the
file is not large enough for the number of files involved.
ACTION Create a larger LISTF temporary file with:
:FILE LISTF;REC=-68,64,F,ASCII;DISC=nnnnn,32;NOCTL;TEMP
where nnnnn is a number large enough to hold the :LISTF output.
The default value of nnnnn is 10000. To create a file large
enough to do a CATALOG on a given number of files,nr_files, use
the following:
nnnnn >=nr_files+(CEIL(nr_files/53)*5)+2
---------------------------------------------------------------------------------------
913 MESSAGE Short real overflow during conversion from Compatibility Mode
short real data.
CAUSE The range of Native Mode (IEEE) short real data is smaller than
the range of Compatibility Mode (MPE/V) short real data.
ACTION If the data is in a BASIC DATA file then the conversion utility
can be used to convert between REAL types. If the data is in a
database then either use Compatibility Mode BASIC to read the
data or manual conversion of the database will be required. If
the data is internal to the program then changing the target
variable to REAL may solve the problem.
---------------------------------------------------------------------------------------
914 MESSAGE Short real underflow during conversion from Compatibility Mode
short real data.
CAUSE The range of Native Mode (IEEE) short real data is smaller than
the range of Compatibility Mode (MPE/V) short real data.
ACTION If the data is in a BASIC data file then the conversion utility
can be used to convert between REAL types. If the data is in a
database then either use Compatibility Mode BASIC to read the
data or manual conversion of the database will be required. If
the data is internal to the program then changing the target
variable to REAL may solve the problem.
---------------------------------------------------------------------------------------
915 MESSAGE Real overflow during conversion to Compatibility Mode Real
data.
CAUSE The range of Native Mode (IEEE) real data is larger than the
range of Compatibility Mode (MPE/V) REAL data.
ACTION This value can't be represented as a CM real value. Your
program logic might allow the largest and smallest CM real
values to be used to represent NM values that are out of CM
real range.
---------------------------------------------------------------------------------------
916 MESSAGE Real underflow during conversion to Compatibility Mode Real
data.
CAUSE The range of Native Mode (IEEE) real data is larger than the
range of Compatibility Mode (MPE/V) REAL data.
ACTION This value can't be represented as a CM real value. Your
program logic might allow the CM values closest to zero to be
used to represent NM values that are out of CM real range.
---------------------------------------------------------------------------------------
917 MESSAGE NM-specific real value, such as NaN and Infinity, occurs while
converting to CM real value.
CAUSE NM real values (such as NaN - "Not a Number", and infinity)
have no corresponding value in CM real representation.
ACTION If NaN occurs then check the logic of the program that produced
it. If infinity occurs, then see if the logic of your program
permits the maximum or minimum representable real to be used in
place of infinity.
---------------------------------------------------------------------------------------
1101 MESSAGE New line number not between 1 and 999999.
CAUSE A line number has been typed (or created by AUTO) that is not
within the legal range for line numbers.
ACTION Line numbers must be in the range: 1 to 999999.
---------------------------------------------------------------------------------------
1102 MESSAGE SYSTEM MESSAGE {number}.
CAUSE {number} identifies an operating system error that occurred
during execution of a SYSTEM command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1103 MESSAGE Number is incomplete.
CAUSE This occurs during execution of the :RUN command. The
SYSTEMRUN command has a parameter of the form:
keyword=% or keyword=-
An octal number should follow the "%" and "-".
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1104 MESSAGE Entrypoint name is missing.
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1105 MESSAGE Entrypoint name has more than 15 characters in it.
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1106 MESSAGE First character in entrypoint name is not a letter.
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1107 MESSAGE Program name's File name is missing.
CAUSE This occurs during execution of the :RUN command. No program
file name was given to the SYSTEMRUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1108 MESSAGE Program name's File name longer than 8 characters.
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1109 MESSAGE First character in Program name's File name is not a letter.
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1110 MESSAGE Missing equals sign after the keyword {keyword}.
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1111 MESSAGE Missing quote after "{INFO | XL} =".
CAUSE This occurs during execution of the :RUN command or SYSTEMRUN
command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1112 MESSAGE Missing ending quote of {INFO | XL | UNSAT} string.
CAUSE This occurs during execution of the :RUN command or SYSTEMRUN
command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1113 MESSAGE {keyword} requires a number.
CAUSE This occurs during execution of the :RUN command or SYSTEMRUN
command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1114 MESSAGE {keyword} must be less than or equal to {number}.
CAUSE This occurs during execution of the :RUN command or SYSTEMRUN
command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1115 MESSAGE {keyword} must be greater than or equal to {number}.
CAUSE This occurs during execution of the :RUN command or SYSTEMRUN
command. The value given for parameter of the RUN command is
less than the minimum value allowed for that parameter.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1116 MESSAGE Missing semicolon.
CAUSE This occurs during execution of the :RUN command or SYSTEMRUN
command. The :RUN arguments must be separated by ";".
ACTION See the appropriate operating system reference manual for more
information. For example,
10 SYSTEMRUN "report.utils;lib=g;maxdata=10000"
---------------------------------------------------------------------------------------
1117 MESSAGE No Help available on that {topic | subtopic}.
CAUSE The HELP system does not contain information about the topic
requested.
ACTION Make sure that the request is correct. If it is correct,
submit a Service Request for inclusion of help for that topic.
---------------------------------------------------------------------------------------
1118 MESSAGE {INFO, XL or UNSAT} string exceeds the maximum allowance.
CAUSE 1. The MPE INFO string is too long.
2. The XL="list" string is too long.
3. The UNSAT="list" string is too long.
ACTION 1. The MPE INFO string must be 200 characters or less.
2. The XL="list" string cannot be longer than 80 characters.
3. The UNSAT="list" string cannot be longer than 31
characters.
---------------------------------------------------------------------------------------