Compaq BASIC for OpenVMS
Alpha and VAX Systems
User Manual

DECLARE INTEGER CONTANT A = "ABC"

User Action: Supply a numeric constant.

NUMIS_NEE, numeric expression is required
Explanation: ERROR---The program contains a string expression in a context that requires a numeric expression, for example, WHILE A$.
User Action: Supply a numeric expression.

NUMVARREQ, numeric variable required
Explanation: ERROR---A nonnumeric variable was found with a numeric data type.
User Action: Specify a numeric variable.

OBJFAIL, failure in loading object file
Explanation: FATAL---In the VAX BASIC Environment, either an attempt was made to load a non BASIC object module, or the compiler could not find the object file referenced by a CALL statement or EXTERNAL FUNCTION reference.
User Action: If the object file resides in the Common Run-Time Library, you must link the program at DCL level. If the object file is in a user-supplied library, use the DCL LIBRARY command to install the missing object module. You can load only VAX BASIC object modules.

ONENOTWHE, ON ERROR not allowed in WHEN block or handler
Explanation: ERROR---An ON ERROR statement has been found in a WHEN block or an associated error handler.
User Action: Remove the ON ERROR statement from the WHEN block or associated error handler.

OPEEXPNOT, operator expected, not found
Explanation: ERROR---A compiler directive contains an invalid lexical expression that has a right parenthesis immediately followed by a lexical identifier.
User Action: Correct the lexical expression.

OPEMUSFOL, operator must follow right parenthesis
Explanation: ERROR---The program contains an incorrect lexical expression.
User Action: Correct the lexical expression.

OPENIN, error opening <file-name> as input
Explanation: ERROR---An error was detected in attempting to open a file for input.
User Action: Make sure the file specification is correct.

OPENOUT, error opening <file-name> as output
Explanation: ERROR---An error was detected in attempting to open a file for output.
User Action: Supply a valid file specification, or take corrective action based on the associated message.

OPNCLAVAL, OPEN clause <clause> value greater than <number>
Explanation: ERROR---An OPEN statement contains a RECORDSIZE, FILESIZE, EXTENDSIZE, WINDOWSIZE, BLOCKSIZE, BUCKETSIZE, or BUFFER clause whose argument is too large.
User Action: Supply a smaller value for the argument.

OPNDUPCLA, duplicate OPEN clause
Explanation: WARNING---An OPEN statement contains more than one clause of the same type.
User Action: Remove one of the clauses.

OPNILLCLA, <clause> is an unsupported OPEN clause
Explanation: ERROR---An OPEN statement specifies invalid attributes for the file, for example, CLUSTERSIZE on OpenVMS systems, or uses the keyword COMMON in an I/O clause.
User Action: Substitute valid attributes for the file or remove the COMMON keyword.

OPNINCCLA, <keyword> keyword is inconsistent with file organization
Explanation: ERROR---An OPEN statement contains a clause that is not appropriate for the specified file organization, for example, opening a relative file with the ACCESS APPEND clause.
User Action: Remove the inconsistent clause.

OPTBASMUS, OPTION BASE must be before array declarations
Explanation: ERROR---A program compiled with the /ANSI_STANDARD qualifier contains an OPTION BASE statement that lexically follows an array declaration.
User Action: Move the OPTION BASE statement so that it lexically precedes the array declaration.

OPTCLACON, OPTION clause occurs more than once
Explanation: ERROR---The OPTION statement contains a duplicate clause, for example, specifying the default integer size as both BYTE and LONG.
User Action: Remove one of the clauses.

OPTNOTALL, OPTIONAL not allowed on EXTERNAL PICTURE
Explanation: ERROR---An attempt was made to specify the OPTIONAL keyword on an EXTERNAL PICTURE declaration. This is not allowed because OPTIONAL parameters should be used for calling non BASIC procedures only.
User Action: Remove the OPTIONAL keyword from the EXTERNAL PICTURE declaration.

OPTOUTSEQ, OPTION statement out of sequence
Explanation: ERROR---The OPTION statement is either: 1) not the first statement in a main program, or 2) not the first statement following the SUB or FUNCTION statement.
User Action: Move the OPTION statement so that it is either the first statement in the main program or the first statement following the SUB or FUNCTION statement in the subprogram.

ORGUNDREQ, ORGANIZATION UNDEFINED requires FOR INPUT clause
Explanation: ERROR---The program opens a file with ORGANIZATION UNDEFINED, but does not specify FOR INPUT.
User Action: Specify FOR INPUT in the OPEN statement. You cannot create a file with an undefined file organization.

OVFCHKSUP, OVERFLOW checking supported only for INTEGER and DECIMAL
Explanation: ERROR---Overflow checking was specified for a floating-point data type in: 1) a compiler command, 2) a qualifier to the DCL BASIC command, or 3) an OPTION statement.
User Action: Specify overflow checking only for INTEGER or DECIMAL data types or both.

OVRNOLINE, <keyword> overrides NOLINE
Explanation: WARNING---The program: 1) was compiled with /NOLINES and 2) uses a keyword that requires line number information. For example, ERL and RESUME with a line number both require that the program be compiled with /LINES.
User Action: None. If you use a keyword that requires line number information, VAX BASIC automatically overrides the /NOLINE qualifier.

PAREXPFOR, <n> parameters expected for <routine>
Explanation: ERROR---The CALL or invocation of a routine specifies a different number of parameters than the number specified when the routine was declared.
User Action: Change the number of parameters to match the number declared.

PARINCPRE, parameter <name> inconsistent with previous declaration or reference
Explanation: ERROR---An external subprogram or DEF function declaration specifies a data type for one of the parameters that is different than the data type the SUB, FUNCTION, or DEF statement specifies.
User Action: Change the specified data type in either the declaration or the SUB, FUNCTION, or DEF statement so that the data types agree.

PARMODCHA, mode for parameter <n> of routine <name> changed to match declaration
Explanation: INFORMATION---The data type specified in a routine invocation does not match that of the routine declaration. BASIC issues this message only if the data-type conversion results in a parameter that cannot be modified by the routine that was invoked.
User Action: Make the data-type specifications in the declaration and the invocation match.

PARMODNOT, mode for parameter <n> of routine <name> not as declared
Explanation: ERROR---The CALL or invocation of a routine specifies a string argument for a parameter that was specified as a numeric when the routine was declared, or vice versa.
User Action: Change the string parameter to numeric, or vice versa.

PARNOTENT, parenthesis illegal, entire array required context
Explanation: ERROR---Parenthesis are used to specify an entire array in a context where an entire array is always required.
User Action: Remove the empty parenthesis from the entire array reference.

PARSTRNOT, parameter <n> of <type> structure not as declared
Explanation: ERROR---The actual parameter list in subprogram CALL or an invocation specifies an entire array where the subprogram declaration specified a simple variable or vice versa.
User Action: Change the actual parameter list to match the declared parameter list or vice versa.

PARTYPREQ, parameter type specification required with /EXPLICIT
Explanation: ERROR---In a program compiled with /TYPE=EXPLICIT, no data-type keyword is specified for a parameter.
User Action: Supply a data-type keyword for the parameter. There are no default data types when you compile a program with /TYPE=EXPLICIT.

PASMECDEF, passing mechanism not allowed for DEF
Explanation: ERROR---A DEF function declaration specifies a passing mechanism for a parameter.
User Action: Remove the passing mechanism clause.

PASMECDIS, passing mechanism disagrees with declaration
Explanation: ERROR---The CALL or invocation of a routine specifies a different passing mechanism for a parameter than that specified when the routine was declared.
User Action: Remove the BY clause specified in the CALL or invocation; BASIC automatically passes parameters with the passing mechanism specified when the routine was declared.

PASMECNOT, passing mechanism not allowed for <item>
Explanation: ERROR---A program specifies a passing mechanism in a context other than the invocation or declaration of an external subprogram.
User Action: Remove the passing mechanism clause.

PASWITNO, <name> has a passing mechanism specified with no parameter list
Explanation: WARNING---A CALL statement, external function reference, or EXTERNAL statement specifies a BY clause but does not specify a formal parameter list.
User Action: Remove the BY clause or supply a parameter list.

PATNOTREC, path name does not specify a CDD/Repository record
Explanation: ERROR---The %INCLUDE directive contains an invalid path name for a record definition.
User Action: Supply a valid path name for a record definition.

PICWHINOT, exit from PICTURE while not in PICTURE
Explanation: ERROR---An EXIT PICTURE statement was found in a module that is not a PICTURE subprogram.
User Action: Remove the EXIT PICTURE statement.

PLACENODESIGN, placeholders illegal without /DESIGN=PLACEHOLDERS
Explanation: ERROR---A placeholder occurred in the source file and the /DESIGN=PLACEHOLDERS option was not specified.
User Action: Recompile the program and specify the qualifier.

PLACENODOT, repetition of pseudocode placeholders not allowed
Explanation: ERROR---A pseudocode placeholder was syntactically incorrect.
User Action: You should remove the trailing periods following the pseudocode placeholder.

PLACENOEXE, placeholders detected---source cannot be executed
Explanation: ERROR---The source code for a RUN command in immediate mode contained at least one placeholder, therefore it could not be executed.
User Action: You should remove the placeholders from the source code and reissue the command.

PLACENOOBJ, placeholders detected---no object produced
Explanation: INFORMATION---The program contained one or more placeholders and therefore no object module was created.
User Action: Remove the placeholders from the source code.

PLACEUNMAT, unmatched placeholder delimiter
Explanation: ERROR-- A placeholder was syntactically incorrect because the number of opening and closing brackets did not match.
User Action: First, make sure that the placeholder does not span multiple source lines. Second, add or remove brackets until they are appropriately paired.

PLACEWRDOT, invalid placeholder repetition
Explanation: ERROR---A list placeholder was syntactically incorrect. Three periods were expected.
User Action: Add trailing periods until there are three periods following the placeholder.

POIREQONE, POINTS output requires at least 1 X,Y point
Explanation: ERROR---You do not specify a point in the POINT graphic output statement.
User Action: Specify a minimum of 1 point in the POINT graphic output statement.

POSGTRTAR, starting position greater than target length
Explanation: ERROR---The starting value in the MID statement is greater than the length of the string.
User Action: Correct the value to be less than or equal to the length of the string.

PRELOGNAM, previous logical name assignment replaced
Explanation: INFORMATION---The specified logical name already existed. The new equivalence name replaces the old one.
User Action: None.

PRICDDERR, prior severe CDD/Repository error
Explanation: ERROR---There have been one or more severe CDD/Repository errors, and this may be the reason for the following errors.
User Action: Recompile the program after correcting the first errors related to CDD/Repository.

PRIUSICLA, PRINT USING clause must be a string expression
Explanation: ERROR---A PRINT USING statement specifies a numeric format string.
User Action: Supply a valid format string.

PRIUSICON, PRINT USING conflicts with RECORD clause
Explanation: ERROR---A PRINT USING statement contains a RECORD clause.
User Action: Remove the RECORD clause or use the PRINT statement instead of PRINT USING.

PROSTRNES, program structures nested too deeply
Explanation: FATAL---The program contains too many nested block constructs, for example, DEF function definitions.
User Action: Reduce the number of nested block constructs.

PROTOOBIG, program too big to compile
Explanation: FATAL---The program is too big.
User Action: Recode the program as two or more modules.

PROWHINOT, exit from PROGRAM while not in a main program
Explanation: ERROR---An EXIT PROGRAM statement was found in a program unit that is not a main program.
User Action: Use the type of EXIT appropriate to the program unit.

QUALERR, unknown qualifier <name>
Explanation: ERROR---An attempt was made to enter an invalid qualifier to a SET, LOCK, or COMPILE command.
User Action: Enter the SET, LOCK, or COMPILE command with the correct qualifier.

RADNOTSUP, radix not supported
Explanation: ERROR---A literal constant specifies a radix. For example, in the following DECLARE statement, H is an invalid radix specifier:

10 DECLARE LONG CONSTANT A = H"111"

User Action: Specify a valid radix. See the Compaq BASIC for OpenVMS Alpha and VAX Systems Reference Manual for a list of the radices BASIC allows.

REAACCINC, READ access inconsistent with FOR OUTPUT
Explanation: ERROR---An OPEN statement specifies FOR OUTPUT and ACCESS READ.
User Action: FOR OUTPUT specifies that a new file is created; ACCESS READ specifies that the program can only read the file. If you want to create a new file, remove the ACCESS READ clause; if you want read-only access to a file, specify FOR INPUT.

READERR, error reading <file-name>
Explanation: ERROR---An error was detected in attempting to read a file.
User Action: Supply a valid file specification or take corrective action based on the associated message.

REAWITDAT, READ without DATA statement
Explanation: ERROR---The program contains a READ statement and there are no DATA statements.
User Action: Supply a DATA statement or remove the READ statement.

RECENTARR, RECORD entire array must not have subfields specified
Explanation: ERROR---A RECORD component reference specifies an array before the end of the component path, for example, A::B(,)::C.
User Action: Remove the erroneous reference.

RECFILTOO, <field-name> from CDD/Repository has FILL too large
Explanation: ERROR---The total size of a CDD/Repository record is greater than 65,535 bytes.
User Action: Reduce the size of the record.

RECKEYQAD, entire RECORD or GROUP must be 8 bytes in length
Explanation: ERROR---The user attempts to specify an entire RECORD or GROUP name in a key value field on a GET or FIND statement and the size of the structure does not match the size of the QUADWORD.
User Action: When specifying a quadword key, use an 8-byte RECORD or GROUP; otherwise, specify the name of an elementary item in the RECORD or GROUP.

RECNOTBY, record may not be passed BY <mechanism>
Explanation: ERROR---The program attempts to pass a record to a subprogram using either the BY VALUE or BY DESC parameter-passing mechanism.
User Action: Remove the passing mechanism, or specify BY REF. BASIC programs can pass records only by reference.

RECNOTDEF, record type <name> not defined
Explanation: ERROR---The program declares an instance of a user data type, but this type was not defined in the program module.
User Action: Define the data type with a RECORD statement.

RECOVEMAP, RECORDSIZE overflows MAP
Explanation: ERROR---An OPEN statement contains both a RECORDSIZE clause and a MAP clause, and the RECORDSIZE clause is larger than the MAP.
User Action: Make the RECORDSIZE the same as the MAP size.

RECRECDEF, recursive RECORD definition of type <name>
Explanation: ERROR---The program contains two or more RECORD statements that reference each other.
User Action: Change the program so that the RECORD statements do not point at each other.

RECTOBIGL, record too big from module <mod-name> in text library <text-lib-name>
Explanation: ERROR---the text library module specified in a %INCLUDE directive contains a record longer than 255 bytes.
User Action: Extract the module from the text library, edit it to remove any records longer than 255 bytes, and replace the module in the text library.

RECTOOBIG, record too big from INCLUDE directive file
Explanation: ERROR---The file specified in a %INCLUDE directive contains a record longer than 255 bytes.
User Action: Edit the file to remove any records longer than 255 bytes.

RECTOOLAR, RECORD too large. Limit is 65,535 bytes
Explanation: ERROR---The components of a RECORD definition add up to more than 65,535 bytes, or 32,767 bytes if the RECORD is used as an array component.
User Action: Reduce the size of the RECORD definition.

REMARRREF, entire REMAPPED array <name> cannot be passed BY REF
Explanation: ERROR---The program attempts to pass an array declared in a MAP DYNAMIC statement to an external subprogram by reference.
User Action: Entire remapped arrays must be passed by descriptor. Specify the BY DESC passing mechanism either in the EXTERNAL declaration or the subprogram invocation.

REMNOTALL, REM statement not allowed in programs without line numbers
Explanation: ERROR---A REM statement has been found in a program without line numbers.
User Action: Remove the REM statement.

REPLACE, assuming <operator(s)> replaced by <operator>
Explanation: ERROR---The program contains a syntax error. BASIC found incorrect or multiple operators where another single operator makes more sense, for example, 10 A == B. Compilation continues so that other errors can be detected. The actual program line remains unchanged and no object file is produced.
User Action: Examine the line carefully to discover the error. Change the program line to correct the syntax error.

REQNUMEXP, <item> requires a numeric expression
Explanation: ERROR---The program contains a string expression in a context requiring a numeric expression.
User Action: Supply a numeric expression.

REQSTREXP, <item> requires string expression
Explanation: ERROR---The program contains a numeric expression in a context requiring a string expression, for example, the file specification in an OPEN statement or the default file specification in a DEFAULTNAME clause.
User Action: Supply a string expression.

RESABOCON, RESEQUENCE aborted due to conditional compilation
Explanation: ERROR---A resequenced program contains a %IF-%THEN-%ELSE-%END-%IF directive.
User Action: Remove the %IF-%THEN-%ELSE-%END-%IF directive.

RESABOSYN, RESEQUENCE aborted due to syntax error
Explanation: ERROR---A RESEQUENCE operation was terminated because the program was not syntactically correct.
User Action: Correct the syntax error and retry the RESEQUENCE operation.

RESATTINC, result attributes inconsistent with prior declaration
Explanation: ERROR---An external or DEF function declaration specifies a data type for the function's result, which is different from the data type the DEF or FUNCTION statement specifies.
User Action: Change the specified data type in either the declaration or the DEF or FUNCTION statement so that the data types agree.

RESINCLIN, RESEQUENCE cannot be used if INCLUDE files reference line numbers
Explanation: ERROR---The current program references an INCLUDE file that contains line number references, for example, GOTO.
User Action: Remove the %INCLUDE directive. BASIC cannot resequence lines in an INCLUDE file.

RESLINGTR, RESEQUENCE cannot generate line numbers greater than 32,767
Explanation: ERROR---The RESEQUENCE command specified an interval or starting point that would have created a line number greater than 32,767.
User Action: Reduce the interval or the starting point.

RESNOTWHE, RESUME not allowed in WHEN block or handler
Explanation: ERROR---A RESUME statement has been found in a WHEN block or an associated error handler.
User Action: Remove the RESUME statement from the WHEN block or associated error handler.

RESORDLIN, RESEQUENCE cannot change the order of or delete lines
Explanation: ERROR---The RESEQUENCE command specifies invalid source program changes.
User Action: Supply a valid RESEQUENCE command.

RETCONMUS, RETRY and CONTINUE must appear in error handlers
Explanation: ERROR---A RETRY or CONTINUE statement is not in an error handler associated with a WHEN block protected region.
User Action: Remove the RETRY or CONTINUE statement.

RFAEXPREQ, RFA expression required
Explanation: ERROR---A GET BY RFA statement contains an expression that is not of the RFA data type.
User Action: Supply a valid RFA expression.

RFANOTALL, RFA not allowed in this context
Explanation: ERROR---The program attempts to use an RFA expression in an arithmetic expression or other invalid context.
User Action: Remove the RFA expression. You can use the RFA data type only in file I/O, in an assignment statement, or in a comparison.

ROUSUPDEC, ROUNDing supported only for DECIMAL
Explanation: ERROR---Rounding was specified for a non-DECIMAL data type in: 1) a compiler command, 2) a qualifier to the BASIC DCL command, or 3) an OPTION statement.
User Action: Specify rounding only for the DECIMAL data type.

RPTCOUMUS, repeat count must be positive numeric
Explanation: ERROR---A FILL item specifies a nonnumeric or negative repeat count, for example, FILL(A$) or FILL(-3).
User Action: Supply a valid repeat count.

SCAFACINH, SCALE factor inhibits optimization
Explanation: INFORMATION---This error is reported only when the /SETUP qualifier is in effect. Specifying a scale factor prevents optimization of the compiler-generated code.
User Action: Compile the program without specifying a scale factor.

SCAFILMUS, ANALYSIS file must be random access---no ANA file produced
Explanation: WARNING--- The file specification on the /ANALYSIS_DATA qualifier specifies a nonrandom access device; therefore, no analysis data file will be produced. BASIC ignores the /ANALYSIS_DATA qualifier and continues compilation.
User Action: Specify a random access device on the file specification on the /ANALYSIS_DATA qualifier.

SCALE0, scale factor used is 0 for single precision
Explanation: WARNING---An attempt was made to set the SCALE factor while in single precision.
User Action: Set the precision to /DOUBLE. You cannot use scaling when in single precision.

SCANOTANS, /ANALYSIS_DATA qualifier not allowed with /ANSI
Explanation: ERROR---The /ANALYSIS_DATA qualifier conflicts with the /ANSI_STANDARD qualifier.
User Action: Specify either the /ANALYSIS_DATA qualifier or the /ANSI_STANDARD qualifier, but not both.

SCAOUTRAN, SCALE is out of range. Valid is 0 to 6.
Explanation: ERROR---The OPTION statement specifies a scale factor that is not from 0 to 6, inclusive.
User Action: Supply a valid scale factor.

SEQERR, attempt to sequence over existing statement
Explanation: ERROR---A SEQUENCE command specifies a starting line number that already exists in the BASIC source program in memory.
User Action: Specify a starting line number higher than any existing line or delete the old statement before using the SEQUENCE command.

SEVERRSCA, please submit an SPR ---- internal error in SCA support
Explanation: FATAL---A severe error has been detected in the SCA support in the BASIC compiler. If you recompile your program without the /ANALYSIS_DATA qualifier, this error should no longer occur.
User Action: Please submit a software problem report (SPR) with the source code of a small program that produces the error.

SEVINTERR, severe internal error has been detected. Submit an SPR.
Explanation: FATAL---An error has been detected in the BASIC compiler.
User Action: Please submit a software problem report (SPR) with the source code of a small program that produces this error.

SHRNOTAVL, Unable to access the shareable image <name>
Explanation: ERROR---The shareable image is not available on your system.
User Action: Install the correct version of the required shareable image.

SPANOSPA, SPAN is inconsistent with NOSPAN
Explanation: WARNING---An OPEN statement specifies both SPAN and NOSPAN.
User Action: Remove one of the clauses.

SPELL, assuming <item> intended to be the keyword: <keyword>
Explanation: ERROR---The program contains a syntax error. BASIC assumes that a keyword has been misspelled, and compilation continues so that other errors can be detected. The actual program line remains unchanged and no object file is produced.
User Action: Examine the line carefully to discover the error. Change the program line to correct the syntax error.

SPENUMEXC, specified numeric exceeds valid character code
Explanation: ERROR---A quoted literal of type character (C) contains a value outside the valid range, for example, '300'C.
User Action: Use a valid ASCII value.

STACKOVF, stack frame overflow for variables
Explanation: ERROR---The program requires too much space for dynamic variables.
User Action: Reduce the number of dynamic variables or place some of the variables in a MAP or COMMON.

STANOTALL, statement not allowed within a PICTURE definition
Explanation: ERROR -- The statement you specified is not allowed in a PICTURE definition.
User Action: Remove the statement from the PICTURE definition.

STARISNEE, star (*) is needed in DEF, not "/"
Explanation: ERROR---The program contains a statement that starts with DEF/.
User Action: Change the DEF/ to DEF*.

STRARRNOT, string array not ANSI
Explanation: INFORMATION---A program compiled with the /ANSI_STANDARD qualifier contains a string array.
User Action: Remove the string array.

STRCONEXP, string constant expression is too long
Explanation: ERROR---The program contains a DECLARE STRING CONSTANT statement where the value assigned to the constant exceeds the maximum number of characters allowed for string constant expressions. The maximum length of a string constant expression at compile time is 498 characters.
User Action: Change the string constant to a string variable and assign the string expression to the variable at run time.

STRCONREQ, string constant required
Explanation: ERROR---The program contains a numeric expression in a context that requires a string expression, for example: