Whenever RATS detects an error, it displays an error message describing the problem. Where possible, these messages provide you with specific information about the error.

 

Each error message begins with an error code: a one-, two-, or three-letter code indicating the general type of error, plus a numeric code identifying the specific error. For example, general syntax errors begin with the code “SX”, syntax errors involving options have the code “OP” (for OPtion), and errors involving linear regressions begin with the code “REG”. 

 

Below is a complete listing of RATS error and warning messages. This includes some suggested causes and remedies.

 

Syntax Errors

Syntax errors probably appear most often. These occur while RATS is reading a line (as opposed to errors which occur as RATS is trying to execute a line it has read successfully). Syntax errors generally mean that RATS couldn’t make sense of the line it was processing. Missing parentheses, misspelled instruction or option names, illegal characters, and incorrectly entered numbers are some common causes of syntax errors.

 

RATS displays two lines of information: the error message, and then the portion of the line which caused the error, enclosed in >>>> and <<<< symbols. RATS only prints the line up to the point at which the error occurred. It will display a maximum of 20 characters, counting back from the point of the error.

 

For example, suppose you tried the following:

 

set trendsq 1 50=t^2

 

This should have at least one blank space between the end parameter (50) and the =. Because that space is missing, RATS will produce the following error message:

 

Error SX15. Trying to Store Into Constant or Expression

>>>>set trendsq 1 50=t<<<<

 

As you can see, RATS stopped processing the line immediately after it detected the illegal assignment operation.

 

RATS often needs to look one character ahead to identify particular operators. For instance, if it sees an =, it must check the next character to see if the operator is ==. Thus, the true culprit may be one character before the one shown.

 

If the reason for a syntax error isn’t immediately obvious, check the entire line, not just the point at which RATS stopped reading the line. RATS can often interpret the actual mistake in a way that allows it to go on reading a few more characters from the line.

 

For instance,

 

data (unit=input)  / gnpdata          

 

produces the error

 

Error SX11. Identifier INPUT Is Not Recognizable

>>>>data (unit=input)<<<<

 

RATS reads all the way to the right parenthesis before it generates the error, but the problem is actually the (illegal) blank space between DATA and the left parenthesis that starts the option field. This blank causes RATS to interpret (UNIT=INPUT) as the start parameter, rather than as the option field. It is legal to use an expression like this for start. However, INPUT is not a recognizable variable name, so RATS produces the error message.

Other Types of Errors

Once RATS has successfully interpreted the line, it does not echo back the characters on the line. All you will see is the error message.

 

Show Last Error

If you are just typing in instructions one at a time, it will be clear which instruction caused the problem. Find it, fix it and re-execute the corrected line (hit <Enter>). However, if you select a block of lines and execute, the problem could be with any of the selected lines. If it’s a syntax error, you might be able to figure out where the problem is by matching up the echoed characters, but that won’t help if it’s an execution error. In that case, try the Edit—Show Last Error operation, which will position the cursor on the instruction line that generated the error.

 

Complete Listing

This appendix lists all of the error and warning messages that RATS can produce. Many of these are largely self-explanatory. However, for some of the more common errors, especially those that can have fairly obscure causes, we have tried to provide suggestions to help you resolve the problem.

 

The messages are grouped by type. Each error has a unique error code consisting of 1 to 3 letters followed by a number, indicating the general type of error. For example, basic syntax errors begin with the letters SX, while errors related to Vector Autoregressions begin with the VAR.
 

Many of the messages will include detailed information about the specific cause of that error. For example, if you try to multiply a 3 × 3 matrix with a 4 × 4 matrix, RATS would produce the error:

 

## MAT2. Matrices with Dimensions 3 x 3 and 4 x 4 Involved in * Operation

 

In the listing below, information that varies depending on the context of the error (such as the specific dimensions involved in the MAT2 error show above) are enclosed in << and >>. Where possible, we indicate the type of information that RATS will display in an actual error message. For example, <<name>> means that RATS will display the name of a variable, instruction, option, etc., while <<data type>> indicates that it will display a data type, such as SERIES or REAL.

 

Some of the error messages end with a question, such as “Did you forget to SOURCE?”. Note that these only suggest a possible cause for the error.

 

Finally, note that a number of these error messages are obsolete, and thus will never be generated by a current version of RATS. We include them here only because they are still present in the error message file used by RATS (RATSERRS.MSG).

General Syntax Errors

SX1       Identifier <<name>> is Already in use as a(n) <<data type>>

You’ve tried to re-declare an existing variable as a different type. Use a different name for the variable, or clear the memory and re-start.

 

SX2       Expected << " or ' >> to Terminate String               

SX3       Expected a Label/Identifier

SX4       Expected Blank or Tab Here

SX5       Expected = Here

SX6       Expected ) Here

SX7       ( Must Follow Immediately After Function Name

Don’t put a blank space between a function name and the “(“. For example, use %ran(1.0), not %ran (1.0).

 

SX8       <<data type>> is not an Aggregate Data Type

SX9       <<data type>> is not a Basic Data Type

SX10      ] Expected After Type Declaration

SX11      Identifier <<name>> is Not Recognizable. Incorrect Option Field or Parameter Order?

Don’t put a space between an instruction name and an option field. For example: use print(nodates), not print (nodates). Check for misspelled names.

 

SX12      Expected a Variable Name Here

SX13      “<<name>>” Is Not a Valid RATS Variable Name

See “Variable Names” for details on what RATS accepts as valid variable names.

 

SX14      Ill-formatted number

SX15      Trying to Store into Constant or Expression. Called Parameter by Value?

If a PROCEDURE parameter is called by value, you cannot change the value stored in that variable. If necessary, call the parameter by address instead.

 

SX16      Missing Operand or Adjacent Operators

Be sure to put at least one space before the equal sign in a SET instruction. For example, use set x =t and not set x=t.

 

SX17      Missing Operator or Adjacent Operands

The SX17 can occur if you refer to “N(entry)” where N is a series number—use “([series] N)(entry)” instead. In a SET or FRML expressions, you can use lag notation: “N{0}”

 

SX18      Dates Must be a:b or a:b:c

Don’t forget to separate the year and period (or the year, month, and day) in a date expression with colons, such as: 1999:3:1.

 

SX19      This Character is Illegal Here

SX20      Expected <<character>> Here

SX21      A <<character>> Here is Unneeded or Unexpected

SX22      Expected Type <<data type>>, Got <<data type>> Instead

An expression may be returning a different data type than the declared type of the variable you are setting, or you are using a variable of a type other than that expected by the instruction (such as using a REAL variable as the series parameter on SET).

 

SX23      Expected Variable/Element of Type <<type>>, Got Expression Instead

SX24      Expected Dimension Field Here

When using DIMENSION, don’t put a space between a variable name and the left parentheses. For example, use dim xmat(10,10), not dim xmat (10,10).

 

SX25      Logical Operators are .EQ./.NE./.LE./.LT./.GE./.GT./.AND./.OR./.NOT.

SX26      Matrix Constructed with ||...|| has Too Complicated a Type

SX27      Illegal Combination of Data Types for Operation

SX28      <<{ or }>> For Lags Used In Improper Manner

SX29      Need a } to End the Lag Field

SX30      Characters After End of Expression

SX31      Expression to Left of , Has No Effect (year,period is obsolete notation)

SX32      Expected */ To End Block Comment

SX33      Expression is Too Complicated. Break into Parts?

SX34      Need ||...|| to delimit matrix
 

Errors Related to Instruction Names or Usage

I1        Expected Instruction - <<string>> Is Not Recognizable As One

I2        Expected Instruction Here

The most common cause of these two errors are mis-spelled instruction names. If you are doing an INPUT, READ, or DATA(UNIT=INPUT) instruction, you may also have provided more data than the INPUT instruction is expecting, causing RATS to try to interpret a line of data as a new instruction.

 

I3        Instruction Format Should Be <<instruction format>>

I4        <<instruction>> Requires RATS Pro Version

I5        RATS Linear Doesn’t Include Instruction <<instruction>>

I6        <<instruction>> Required X Windows Version

 

Errors Involving Instruction Parameters

P1        / For Parameter Pairs Should Be Followed by Space

If using the “/” symbol for the default range, make sure you have a space before and after the “/”.

 

P2        Second Half of Parameter Pair Is Absent

If you supply a value for a start parameter, you must also supply a value for the end parameter (use “*” for either parameter to use the default value for that parameter).

 

P3        Instruction <<instruction>> Requires Parameter <<parameter>>

P4        <<parameter string>> is Invalid - Choose From <<list of choices>>

P5        <<parameter choice>> Cannot Be Used with <<parameter choice>>

 

Errors Related to Options

OP1       Looking For Option Field or White Space. This Character Is Unexpected.

OP2       Expected , to Separate Options  or ) to End Option Field

Use a comma to separate each option in an option field, and close the option field with a right parenthesis.

 

OP3       This Instruction Does Not Have An Option <<option>>

OP4       The Option <<option>> Is Already Set By This Instruction

You have probably listed the same option twice.

 

OP5       Form NO<<option>> is Not Permitted For Option <<option>>

OP6       Expected Option Here

OP7       <<argument>> Is Not One of the Choices for Option <<option>>

OP8       Option <<option>> Needs = Here

OP9       Options <<option>> and <<option>> May Not Be Used Together

OP10      Instruction <<instruction>> Requires Option <<option>>

If you have problems with an option field, carefully check the syntax and the list of options for that instruction.

Errors Involving Supplementary Cards

SC1       Expected Supplementary Card (# ....) Here

SC2       Require Supplementary Card Field <<name>> (Position <<number>>)

SC3       Expected <<number>> Entries on Supplementary Card, Got Only <<number>>

SC4       Can’t Use / or * On This Type of Supplementary Card

SC5       Use of * Illegal At This Location

SC6       Need a LIST Instruction to Use CARDS

SC7       LIST Needs At Least <<number>> Entries, Had Only <<number>>

 

Errors Involving Data Series

SR1       ALLOCATE Instruction Needed Before Series or Equations Can Be Used

SR2       FREQUENCY Instruction Needed Before Complex Series Can Be Used

You must do an ALLOCATE instruction before defining or using real-valued series, and you must use do a FREQUENCY instruction before defining or using complex-valued series. If you are using procedures that work with series, you may need to do your ALLOCATE instruction before SOURCEing in the procedure.

 

SR3       Tried to Use Series Number <<number>>, Only <<number>> Are Available

SR4       Tried To Use Series Number <<number>> (-series n1 n2 triples are no longer legal)

SR5       <<writing/using>> Range <<entry>> to <<entry>> of Series <<series>> (Incorrect start,end or SMPL)

SR6       Missing a Necessary Parameter. Check Instruction Syntax

SR7       Block with <<number>> Elements is Too Big for This Version of RATS

SR8       Badly Formed TO triple

SR9       High TO Low Range: <<entry>> TO <<entry>> Is Illegal

SR10      Missing Values And/Or SMPL Options Leave No Usable Data Points

This can occur if you try to apply an operation to a series that contains no data, or try to run an estimation where all observations are dropped because of missing values in one or more series. Check all of the series involved using TABLE or PRINT. Watch for transformations, such as taking logs or roots of negative numbers, that can eliminate data. Make sure you are not trying to start an estimation too early in the sample range. For non-linear estimation, check for valid initial conditions for all parameters, make sure you aren’t taking logs or roots of negative numbers, etc.

 

SR11      Illegal range, start = <<entry>> , end = <<entry>>. Are your parameters correct?

SR13      Need to Include an Entry Range. No Previous Instruction Has Set the Default.

If you don’t use an ALLOCATE (which is now optional, rather than required), you will need to specify an explicit ending period on the first instruction in your program that uses series (usually a DATA instruction). Otherwise, you will get this error.

 

SR14      <<description>> Range on Series <<series>>.

You are trying to use a series which has no data.

Regression/Estimation Problems

REG1      Cannot Execute Unless Preceded by a Completed Regression

REG2      LINREG(CMOM) First Requires CMOM/MCOV without CORR, CENTERED or MATRIX option

REG3      <<instruction>> Fails - No Prior Regression or Regression Was Different Size

REG4      Variable <<name>> is Not in the Prior Regression

REG5      Variable <<name>> is Not in the Prior CMOMENT

REG6      Matrix <<name>> Is Singular. Check for Collinearity in First <<number>> <<rows or columns>>

REG7      Variance is Zero

REG8      No Instruments Available. Use an INSTRUMENT instruction first

REG9      Model is Underidentified - <<number>> Parameters To Estimate and Only <<number>> Instruments

REG10     First <<number>> Instruments Are Linearly Dependent Over Regression Range

REG11     Regression Position <<number>> Should Be Between 1 and <<number>>

REG12     SIGMA Is Singular/Not PSD At Row <<number>>. Too Many Equations for Data Set Size?

For SUR/NLSYSTEM estimation, you must have more usable time periods than equations.

 

REG13     Singular Regressions - Check for Collinearity among Rows 1 to <<number>>.

REG14     Unsatisfactory Initial Estimates. Setting Last MA to 0.

REG15     Series <<name>> Has All <<ZERO or NONZERO>> Values Over Estimation Range. Are You Using Zero-NonZero Coding?

REG16     Initial regression uses all the degrees of freedom

REG17     Either use series list parameters or SCRATCH option.

REG18     METHOD=CORC/MAXL Cannot Be Used With Gaps/Missing Values. Switching to HILU/SEARCH

This is just a warning that RATS is switching to a different estimation method for the AR1 instruction due to missing values in the sample range.

 

REG19     Need at least <<number>> Autocovariances. Adding 0’s at end of COVARIANCES series

REG20     ITERATE/BOXJENK Cannot Be Used with Gaps/Missing Values

ARIMA estimation methods (other than BOXJENK with MAXL) cannot be applied if there are any missing values in the estimation range. If you didn’t expect to have missing values, check the start and end dates used for the regression, and use PRINT to check the data. You can use SAMPLE to “compress out” the missing data if desired.

 

REG21     Can’t Freely Estimate SW Matrix with <<number>> Conditions. Have Only <<number>>  Observations

 

Errors Involving Matrices

MAT1      Matrix <<name>> Has Not Been Dimensioned

You must dimension an array before you can set or reference individual elements.

 

MAT2      Matrices with Dimensions <<rows x columns>> and <<rows x columns>> Involved in <<operator>> Operation

MAT3      Matrix with Dimensions <<rows x columns>> Involved in <<operator>> Operation. Need <<rows x columns>>

MAT4      Must Use the Form matrix=<<function>>(...) for this Operation.

The function returns an array as a result, so an array name must be provided on the left side of the equal sign.

 

MAT5      Needed Matrix with Dimensions <<rows x columns>>, Got <<rows x columns>> Instead

MAT6      Trying to Store <<rows x columns>> Matrix Into VECTOR

MAT7      Function <<function name>> Requires a <<matrix type>> Matrix As Argument

MAT8      Non-Positive Argument for function <<function name>>

MAT9      Base Address for OVERLAY is Invalid (Subscripts Out of Range)

MAT10     You Can’t OVERLAY with a Series, Only with an Array

MAT11     You Can’t DIMENSION a Series

MAT12     Syntax: EWISE array(I,J)=expression or array(I)=expression

MAT13     Store into Out-of-Range Matrix or Series Element

This can occur if, for example, you try to set element 11 of a matrix that has only been dimensioned to have 10 elements. If you are doing a non-linear estimation using recursive FRMLs, as when estimating GARCH models with MAXIMIZE, where series are being used to hold values of sub-formulas—those series must be initialized over the entire estimation range. Set them to a value over the full range.

 

MAT14     Non-invertible Matrix. Using Generalized Inverse for SYMMETRIC.

RATS tried to invert a matrix, but the matrix was non-invertible. If the matrix was of type SYMMETRIC, RATS has applied a generalized inverse routine.

 

MAT15     Subscripts Too Large or Non-Positive

Array elements are numbered from 1 to the dimensioned size. Don’t use zero or a negative number, or a number larger than the dimensioned size, in referring to an array element. If this appears as a result of a MAXIMIZE command, you most likely have specified the entry range incorrectly, or else one of your formulas is trying to store a result into a series or array element that has not been defined yet—make sure that any series used to hold residuals or variances have been explicitly defined over the entire estimation range.

 

MAT16     Column Choice of <<column>> is Invalid

MAT17     Can’t Use <<row/column>> Range of <<low>> to <<high>> in <<operation>> operation

MAT18     You Must Dimension the Outer Array Separately
 

Errors Relating to Equations

EQ1       Cannot Use Equation Number <<number>> (Value should be Positive)

EQ2       Equation Includes More Than One Explanatory Variable

EQ3       Equation <<name or number>> Has Not Been Defined

EQ4       Equation <<name or number>> Has At Least One Undefined or NA Coefficient

EQ5       Equation <<name or number>> Does Not Include Variable <<name>>

EQ6       Variable <<name>> Is Not the Dependent Variable of Equation <<name>>

EQ7       Variable <<name>> Has Zero Coefficient in Equation <<name or number>>

EQ8       Cannot Replace the Dependent Variable with a Lag

EQ9       ALLOCATE Equation <<number>> is Increased in Size. %COEFF is No Longer Valid

EQ10      Equation <<name or number>> Needs Residuals for This Operation

EQ11      Need To Use MODIFY Instruction to Start Equation Modification

EQ12      Equation <<eqnname>> is Part of ECT Model. Can't be Edited/Displayed Separately.

Non-Linear Estimation Problems

NL1       FRML References More Than 20 Deep. Do You Have a Self-referencing FRML?

NL2       NONLIN Instruction is Required Before Non-Linear Estimation Can Be Done

NL3       FRML <<name>> Has Not Been Defined

NL4       FRMLs Cannot Have Moving Average Parameters

NL5       FRML <<name>> was Defined Without a Dependent Variable

NL6       NONLIN Parameter <<name>> Has Not Been Initialized. Trying 0

This is just a warning that you have not provided an initial value for the specified parameter. RATS will try to do the estimation using 0.0 as the initial value. If the estimation fails to converge, use COMPUTE to supply better initial values before doing the estimation. Also, note that 0.0 may not be a valid initial value for some parameters (if the formula takes the log of the parameter, for example).

 

NL7       NONLIN Parameter Has Invalid Form (Common errors: using = > or < for == >= or <=)

NL8       MODEL Must Have No Linear Equations

NL9       PARMSET is Size <<size>>. Doesn't Match Last Estimation of Size <<name>>

NL10      Analytical Derivatives Can't Be Applied to Formula

NL11      Need at least one of <<list of options>>

On a CVMODEL, you haven't included an option to describe the model.

Errors Involving Vector Autoregressions

VAR1      A SYSTEM instruction is needed first

VAR2      Need SYSTEM and VARIABLES instructions first

VAR3      <<name>> requires either SYSTEM(KALMAN) or KFSET instruction

VAR4      SYSTEM definition is incomplete

VAR5      KFSET Lists <<number>> Arrays, TVARYING Lists <<number>>. They should be equal

VAR6      <<name>> Instruction Lists <<number>> Arrays, Should Have <<number>>

VAR7      Need ESTIMATE or KALMAN(STARTUP=xxx) First

You must either ESTIMATE the model or do KALMAN(STARTUP=date) to initialize the Kalman Filter before using KALMAN to do updating.

 

VAR8      SYSTEM Lists <<number>> Equations, VARIABLES Lists <<number>> Variables. They should be equal

VAR9      You Can’t ADD and DROP on the same KALMAN instruction

VAR10     Can’t DROP Entry <<number>> - Filter Only Includes Entries <<number>> to <<number>>

VAR11     COHISTORY can only be used with a single equation model

VAR12     %s can't be used with a model with ECT terms

VAR13     %MODELCOMPANION can't be used with equations with zero lags (or leads)

VAR14     MODEL must have only EQUATIONS, no FRML's

VAR15     SYSTEM lists <<depvar>> Variables and <<ect>> ECT's. Too many ECT's for the model.

VAR16     LAGS requests only lag <<lagnumber>>. Did you want 1 TO <<lagnumber>> instead?

This is a warning that you probably did the LAGS instruction incorrectly. If you want a "4-lag" VAR, the proper instruction is LAGS 1 to 4, not LAGS 4.
 

Compiled Mode Problems

CP1       END(}) is Improperly Placed. Match with BEGIN({),DO,DOFOR,LOOP,PROCEDURE,MENU,FIND

CP2       This Instruction Must Precede All Executable Instructions

CP3       Instruction is Illegal Outside Compiled Section

CP4       ELSE Must Come Immediately After IF block

If you are using an IF–ELSE structure and want to execute several statements when the IF command is true, you must enclose those statements in { and }.

 

CP5       CHOICE Must Come Immediately After MENU or Another CHOICE block

CP6       Need CHOICE instruction to follow MENU

CP7       No DO, DOFOR, LOOP, WHILE, UNTIL or FIND for BREAK/NEXT

CP8       Label <<name>> Is Undefined

CP9       Label <<name>> Is Already In Use

CP10      Statement Label is Illegal Here

CP11      Statement Label <<name>> is Unreachable From BRANCH

CP12      DO Loop Has Increment of 0

CP13      Switch and Choice Options Cannot be Done By Reference

CP14      Please Do Separate DIMENSION Instruction in Compiled Section

Inside a procedure or loop, you cannot include dimension fields on a DECLARE instruction—use a separate DIMENSION instruction in those cases.

 

CP15      This Supplementary/Data/Text/CARDS card is not Used

CP16      Fatal Error - RATS Program Bug in Executing Compile

CP17      PROCEDURE Must be Initial Statement in a Compiled Section

CP18      <<name>> is not the Name of a PROCEDURE (Did you forget to SOURCE?)

CP19      <<name>> is not a PROCEDURE Parameter

CP20      <<name>> may be used only in a PROCEDURE

CP21      SOURCE Instructions/Executes Nested Too Deeply. Recursive Procedure?

CP22      <<name>> may not be used in a compiled section

CP23      Option abbreviation <<abbrev>> already in use in procedure <<name>>

CP24      PROCEDURE/FUNCTION <<procname>> compiled with errors. Please correct

CP25      Reference to Undefined FUNCTION

CP26      END(RESET) used when compiled section is active

Miscellaneous Errors Relating to Specific Instructions

X1        Syntax is CALENDAR(options)  year  month  day   with this frequency

X2        Don’t Use CALENDAR 1 1 1 for Undated Data. See page 1-5 in the Manual

X3        You Probably Mean <<number>>:1. Note that year:1 is needed with Annual Data

Don’t use just a year number, such as “1999”, as a date reference when working with annual data. Use “1999:1” instead.

 

X4        <<string>> is illegal picture. Pictures must look like *, ##, *.## or ##.##

See picture codes.

 

X5        ENTER(VARYING) Requires a Single VECTOR[...] type Variable

X6        You cannot ENTER an Array with more than one object on the list

X7        TREND=EXPONENTIAL/SEASONAL=MULTIPLICATIVE Cannot Be Used with Non-Positive Data

X8        Unstable ESMOOTH Parameters. Try Different Values.

X9        You should specify an explicit seasonal with this frequency data

X10       Use the TABLE Instruction to Get Statistics on Several Series

X11       Series Lists Have <<number>> and <<number>> Variables. They Should be Same Size

X12       Cannot Do COMPRESS with This Combination of Weights

X13       Redundant Restrictions. Using <<number>> Degrees, not <<number>>

See "Wald Tests". Note that this is a warning, not an error.

 

X14       Sorry, QUERY Can’t Handle Arrays

X15       Expected <<number>> More Data Values

X16       MEDIT only accepts REAL Valued Arrays

X17       Problem and network do not match

The number of input and/or output series, hidden nodes, or DIRECT option setting do not match those used to generate the memory vector for this neural network.

 

X18       Input pattern has different range than test data

The range of values in the input series exceeds the maximum or minimum values specified when the network was first estimated.

 

X19       Unable to open X Window for display

X20       This Item Type Needs an INTEGER for “output value”

X21       You Need a SERIES, LIST, STRINGS, or REGRESSORS Option to Define the List

X22       DISTRIB=GED Can’t Be Used with Multivariate Model. Switching to Normal

X23       FILTER(TYPE=<<type>>) Needs <<value>> for WIDTH/SPAN option

X24       GARCH DENSITY must be FUNCTION(SYMMETRIC,VECTOR) or FUNCTION(REAL,REAL). Got <<datatype>>

X25       GRPARM DEFINE <<description>>. Got <<input>>.

On a GRPARM where you are defining a style, you have given the wrong type of information for a particular style.
 

Forecasting/Simulation Errors

FO1       Equations <<name or number>> and <<name or number>> both have dependent variable <<name>>

Each equation in the system must have a unique dependent variable. See "Simultaneous Equations".

 

FO2       Need the “equation” parameter on each supplementary card

FO3       You need to do THEIL(SETUP) first

FO4       Identities must come last

FO5       SHOCKS array has <<number>> columns. Should have <<number>>

FO6       SIMULATE(SETUP) is no longer needed. See description of SIMULATE.

FO7       Gauss-Seidel solution is explosive. Check model. Try DAMP option.

FO8       Gauss-Seidel did not converge in <<number>> Iterations. Criterion = <<value>>.

See "Gauss-Seidel Algorithm" for tips on getting your simultaneous equation model to converge.

 

FO9       Simultaneous block is singular. Check your equations.

FO10      Either actual or forecast is NA. Skipping step(s).

FO11      IMPULSE, ERRORS and HISTORY can’t handle model with FRMLs.

FO12      Model has <<number>> equations, DSGE lists <<number>> series. These need to match.

FO13      Model produces missing value. You may need to adjust initial guesses.

FO14      Newton's method did not converge in <<iterations>> Iterations. Criterion = <<last criterion>>.

FO15      Model can't be expanded. Includes exogenous series reference.

The MODEL in DSGE is including a reference to a series which is not listed as an endogenous variable.

 

FO16      Newton's method had singularity. If model is non-stationary, use option SOLVEBY=SVD.

FO17      Mismatch between unstable roots and expectational terms.

FO18      No obvious guess value for series <<series>>. Using 0.

FO19      Forecast for <<series>> solves to NA at <<time period>>, on iteration <<iteration>>.
 

Memory/Internal Errors

M1        <<parameter or option>> = <<number>> is Illegal. Value should be between <<number>> and <<number>>

M2        <<parameter or option>> = <<number>> is Illegal. Value should be <<required value type>>

M3        RATS Internal Error!!! This should never happen

M4        A memory request for an additional <<number>>  bytes cannot be satisfied

M5        <<name>>  has Value <<number>> , Must Be <<number>>

M6        User Abort

M7        Untrapped Floating Point Error: Overflow or NA

M8        Untrapped Miscellaneous Error

M9        RATS Internal Error!!! Save Your Work Now Using Save As

M10       Classroom RATS Limit of <<number>> Data Points Exceeded. You Need <<number>>

M11       Integer divide by zero

M12       Polynomials can’t have negative powers

M13       Table Must be 2xN RECT[INTEGER]

M14            Use of undefined/out-of-range <<object>>
 

Dynamic Linear Modeling Errors

DLM1      Rank of Prediction Error Variance < Number of Observables

DLM2      No Observations Produce Valid Output. Check Data and Initial Values

DLM3      The G Option Requires Both A and SW to Solve Out Initial Conditions

DLM4      With TYPE=CONTROL, B Option is Required

DLM5      Probable Model Error. Diffuse prior was not reduced to zero rank

DLM6      METHOD=GAUSS can only be used with univariate Y. Switching to BFGS.
 

Linear/Quadratic Programming Errors

LPQ1      Contradictory constraints

LPQ2      Unbounded problem

LPQ3      General failure of LPQP

LPQ4      Simplex method does not converge

LPQ5      Active set method does not converge

LPQ6      All elements of “b” vector must be non-negative

 

Input/Output Errors

IO1       Unit “<<I/O unit name>> “ is already open

IO2       Unit <<I/O unit name>> Is Already In Use For <<access type>>

IO3       Unable to open <<file name>>

Check to make sure the file isn’t already open in another application.

 

IO4       Unit “<<I/O unit name>>” does not exist

IO5       Unit “<<I/O unit name>>” is permanent. You cannot <<OPEN or CLOSE>> it

IO6       Units <<I/O unit name>>” and “<<I/O unit name>>” are already aliases

IO7       Unit <<I/O unit name>> is not open

IO8       An error occurred while writing to the disk, the disk may be full.

IO9       Invalid input “<<string>>” on line <<number>> while processing series <<name>> entry <<number>>

Usually occurs when a file being read with DATA includes text information. This is only a warning—RATS will set the indicated entry to NA and continue reading data.

 

IO10      Unexpected end of file while processing line <<number>>. (series <<name>> entry <<number>>)

IO11      Input/Output error on <<operation>>  <<error code>>

IO12      A date is missing from series <<name>> after entry <<number>>

IO13      “<<string>>” is not a valid date on line <<number>>

IO14      Data are not in ascending date sequence

IO15      Using dates from the data file

IO16      Input file does not contain dates

IO17      Header names <<number>> series while there are <<number>> series on file

The file should have one series name per column or row of data. This indicates that there are too few or too many series names.

 

IO18      Unexpected end of line while processing line <<number>> (series <<name>> entry <<number>>)

IO19      The file does not have a valid <<format type>> format

IO20      The file contains no valid data

IO21      RATS only process the first worksheet in a spreadsheet file

IO22      Format has nothing to read or write

IO23      Format <<character>> and element <<type>> are of incompatible types

IO24      FORTRAN Hollerith Field Length of <<number>> is Illegal/Clearly Wrong

IO25      Illegal FORTRAN format “<<format string>>”

IO26      Unbalanced parenthesis in FORTRAN format

See FORMAT=FORTRAN.

 

IO27      The file is not in RATS format.

IO28      File appears to be damaged

IO29      No file is currently being edited

IO30      There is no series <<name>> on the file

Check the list of series on the DATA instruction versus the list on the file. Or, omit the list of series and add the VERBOSE option on DATA—this will read in all series on the file and report their names.

 

IO31      Series <<number>> already exists on the file

IO32      At most two comments can be attached to a series

IO33      The file being edited is not version 4

IO34      Date Type is Not Supported by RATS Version 3 Format

IO35      Unable to rename file <<name>> to <<name>>

IO36      Unable to delete file <<name>>

IO37      Cannot use UNIT=INPUT with this format

IO38      Cannot convert between these Frequencies

IO39      Unexpected End of File. Only <<number>> Values Were Processed

IO40      Expected <<type>>. Got “<<string>>”.

IO41      “<<name>>” is not the Name of Series in Working Memory

IO42      Binary file contents do not match READ requests

IO43      Format <<format>> is illegal or not supported

IO44      Date scheme <<string>> is not currently supported on this file type

IO45      Data can not be appended to unit <<I/O unit name>>

IO46      Separate year and period or year month day on UPDATE

IO47      <<format>> cannot process a <<string>>

IO48      File with <<number>> columns might not be readable by other programs

IO49      ODBC/SQL error.

IO50      Format <<format>> is not supported by this version of RATS

IO51      Can't find worksheet/matrix <<sheet>>

IO52      Date form string <<string>> is invalid

IO53      Probable Error with OPEN <<name>>. Is UNIT parameter missing?
 

FAME Format Data Errors

FM1       FAME HLI error <<format>>

X11 Seasonal Adjust Errors (Professional Version Only)

X1101     X11 can take monthly or quarterly series only.

X1102     Series with missing values cannot be used in X11.

X1103     Series has non-positive values. Switching to additive adjustment.

Copyright © 2025 Thomas A. Doan