Return Codes and Error Messages
Optimizer Return Codes
The following table shows the possible return codes from the subroutine library functions:
Return Code Description 0 Subroutine completed successfully. 1a Bad input encountered. 2a Bad or corrupt file - unrecoverable. 4a Memory error. 8a Corrupt use. 16a Program error. 32 Subroutine not completed successfully, possibly due to invalid argument. 128 Too many users. a - Unrecoverable error. When the Optimizer terminates after the STOP command, it may set an exit code that can be tested by the operating system or by the calling program. The exit code is set as follows:
Return Code Description 0 Program terminated normally (with STOP). 63 LP optimization unfinished. 64 LP feasible and optimal. 65 LP infeasible. 66 LP unbounded. 67 IP optimal solution found. 68 IP search incomplete but an IP solution has been found. 69 IP search incomplete, no IP solution found. 70 IP infeasible. 99 LP optimization not started. Optimizer Error and Warning Messages
Following a premature exit, the Optimizer can be interrogated as necessary to obtain more information about the specific error or warning which occurred. Library users may return a description of errors or warnings as they are encountered using the function XPRSgetlasterror. This function returns information related to the error code, held in the problem attribute ERRORCODE. For Console users the value of this attribute is output to the screen as errors or warnings are encountered. For Library users it must be retrieved using:
XPRSgetintattrib(prob,XPRS_ERRORCODE,&errorcode);The following list contains values of ERRORCODE and a possible resolution of the error or warning.
- 3 Extension not allowed - ignored.
The specified extension is not allowed. The Optimizer ignores the extension and truncates the filename.
- 4 Column <col> has no upper bound.
Column <col> cannot be at its upper bound in the supplied basis since it does not have one. A new basis will be created internally where column <col> will be at its lower bound while the rest of the columns and rows maintain their basic/non-basic status.
- 5 Error on .<ext> file.
An error has occurred on the . <ext> file. Please make sure that there is adequate disk space for the file and that it has not become corrupted.
- 6 No match for column <col> in matrix.
Column <col> has not been defined in the COLUMNS section of the matrix and cannot be used in subsequent sections. Please check that the spelling of <col> is correct and that it is not written outside the field reserved for column names.
- 7 Empty matrix. Please increase EXTRAROWS.
There are too few rows or columns. Please increase EXTRAROWS before input, or make sure there is at least one row in your matrix and try to read it again.
- 9 Error on read of basis file.
The basis file .BSS is corrupt. Please make sure that there is adequate disk space for the file and that it has not been corrupted.
- 11 Not allowed - solution not optimal.
The operation you are trying to perform is not allowed unless the solution is optimal. Please call XPRSmaxim (MAXIM) or XPRSminim (MINIM) to optimize the problem and make sure the process is completed. If the control LPITERLIMIT has been set, make sure that the optimal solution can be found within the maximum number of iterations allowed.
- 16 Null column <col>.
Column <col> has a zero coefficient in all the rows in the COLUMN section. Please remove empty columns to avoid this warning message.
- 17 More than one RHS not permitted - subsequent ones ignored.
Only one RHS is allowed for a constraint. The first RHS value that has been read will be kept and any subsequent ones ignored.
- 18 Bound conflict for column <col>.
Specified upper bound for column <col> is smaller that the specified lower bound. Please change one or both bounds to solve the conflict and try again.
- 19 Eta overflow straight after invert - unrecoverable.
There is not enough memory for eta arrays. Either increase the virtual paging space or the physical memory.
- 20 Insufficient memory for array <array>.
There is not enough memory for an internal data structure. Either increase the virtual paging space or the physical memory.
- 21 Unidentified section The command is not recognized by the Optimizer.
Please check the spelling and try again. Please refer to the Reference Manual for a list of valid commands.
- 29 Input aborted.
Input has encountered too many problems in reading your matrix and it has been aborted. This message will be preceded by other error messages whose error numbers will give information about the nature of each of the problems. Please correct all errors and try again.
- 36 Linear Optimizer only: buy IP Optimizer from Dash Associates.
You are only authorized to use the Linear Optimizer. Please contact your local sales office to discuss upgrading to the IP Optimizer if you wish to use this command.
- 38 Invalid option.
One of the options you have specified is incorrect. Please check the input option and retype the command. A list of valid options for each command can be found in Console and Library Functions.
- 41 Global error - contact Dash.
Internal error. Please contact your local support office.
- 45 Failure to open global file - aborting. (Perhaps disk is full).
Xpress‑MP cannot open the .GLB file. This usually occurs when your disk is full. If this is not the case it means that the .GLB file has been corrupted.
- 50 Inconsistent basis.
Internal basis held in memory has been corrupted. Please contact your local support office.
- 52 Too many nonzero elements.
The number of matrix elements exceeds the maximum allowed. If you have the Hyper version then increase your virtual page space or physical memory. If you have purchased any other version of the software please contact your local sales office to discuss upgrading if you wish to read matrices with this number of elements.
- 56 Reference row entries too close for set <set> member <col>.
The coefficient of column <col> in the constraint being used as reference row for set <set> is too close to the coefficient of some other column in the reference row. Please make sure the coefficients in the reference row differ enough from one another. One way of doing this is to create a non computational constraint (N type) that contains all the variables members of the set <set> and then assign coefficients whose distance from each other is of at least 1 unit.
- 58 Duplicate element for column <col> row <row>.
The coefficient for column <col> appears more than once in row <row>. The elements are added together but please make sure column <col> only has one coefficient in <row> to avoid this warning message.
- 60 Out of memory - program aborted.
The Optimizer cannot allocate any more memory. Please increase your virtual page space or physical memory.
- 61 Unexpected EOF on workfile.
An internal workfile has been corrupted. Please make sure that there is adequate disk space and try again. If the problem persists please contact your local support office.
- 64 Error closing file <file>.
Xpress‑MP could not close file <file>. Please make sure that the file exists and that it is not being used by another application.
- 65 Fatal error on read from workfile <file> - program aborted.
An internal workfile has been corrupted. Please make sure that your disk has enough space and try again. If the problem persists please contact your local support office.
- 66 Unable to open file <file>.
Xpress‑MP has failed to open the file <file>. Please make sure that the file exists and there is adequate disk space.
- 67 Error on read of file <file>.
Xpress‑MP has failed to read the file <file>. Please make sure that the file exists and that it has not been corrupted.
- 68 <num> errors in sizing parameter <par> - fatal.
During initialization Xpress‑MP has encountered <num> errors. Please contact your local support office.
- 71 Not a basic vector: <vector>.
Dual value of row or column <vector> cannot be analyzed because the vector is not basic.
- 72 Not a non-basic vector: <vector>.
Activity of row or column <vector> cannot be analyzed because the vector is basic.
- 73 Problem has too many rows. The maximum is <num>.
Xpress‑MP cannot input your problem since the number of rows exceeds <num>, the maximum allowed. If you have purchased any other than the Hyper version of the software please contact your local sales office to discuss upgrading it to solve larger problems.
- 76 Illegal priority: entity <ent> value <num>.
Entity <ent> has been assigned an invalid priority value of <num> in the directives files and this priority will be ignored. Please make sure that the priority value lies between 0 and 1000 and that it is written inside the corresponding field in the .DIR file.
- 77 Illegal set card <line>.
The set definition in line <line> of the .MAT or .MPS file creates a conflict. Please make sure that the set has a correct type and has not been already defined. Please refer to the Reference Manual for a list of valid set types.
- 79 File error.
The Optimizer has encountered a file error. Please make sure that there is adequate disk space and that the volume is not corrupt.
- 80 File creation error.
The Optimizer cannot create a file. Please make sure that these is adequate disk space and that the volume is not corrupt.
- 81 Fatal error on write to workfile <file> - program aborted.
The Optimizer cannot write to the file <file>. Please make sure that there is adequate disk space and that the volume is not corrupt.
- 83 Fatal error on write to file - program aborted.
The Optimizer cannot write to an internal file. Please make sure that there is adequate disk space and that the volume is not corrupt.
- 84 Input line too long. Maximum line length is <num>
A line in the .MAT or .MPS file has been found to be too long. Please reduce the length to be less or equal than <num> and input again.
- 85 File not found: <file>.
The Optimizer cannot find the file <file>. Please check the spelling and that the file exists. If this file has to be created by Xpress‑MP make sure that the process which creates the file has been performed.
- 89 No optimization has been attempted.
The operation you are trying to perform is not allowed unless the solution is optimal. Please call XPRSmaxim (MAXIM) or XPRSminim (MINIM) to optimize the problem and make sure the process is completed. If you have set the control LPITERLIMIT make sure that the optimal solution can be found within the maximum number of iterations allowed.
- 90 Not enough memory for Devex pricing: PRICINGALG has been set to -1.
The Optimizer required more memory to perform Devex pricing. Please increase your virtual paging space, physical memory or do not use the Devex pricing algorithm.
- 91 No problem has been input.
An operation has been attempted that requires a problem to have been input. Please make sure that XPRSreadprob (READPROB) is called and that the problem has been loaded successfully before trying again.
- 97 Split vector <vector>.
The declaration of column <vector> in the COLUMN section of the .MAT or .MPS file must be done in contiguous line. It is not possible to interrupt the declaration of a column with lines corresponding to a different vector.
- 98 At line <num> no match for row <row>.
A non existing row <row> is being used at line number <num> of the .MAT or .MPS file. Please check spelling and make sure that <row> is defined in the ROWS section.
- 102 Eta file space exceeded - optimization aborted.
The Optimizer requires more memory. Please increase your virtual paging space or physical memory and try to optimize again.
- 107 Too many global entities at column <col>.
Xpress‑MP cannot input your problem since the number of global entities exceeds the maximum allowed. If you have the Hyper version then increase your virtual page space or physical memory. If you have purchased any other version of the software please contact your local sales office to discuss upgrading it to solve larger problems.
- 111 Duplicate row <row> - ignored.
Row <row> is used more than once in the same section. Only the first use is kept and subsequent ones are ignored.
- 112 Postoptimal analysis not permitted on presolved problems.
Re-optimize with PRESOLVE = 0. An operation has been attempted on the presolved problem. Please optimize again calling XPRSmaxim (MAXIM), XPRSminim (MINIM) with the l flag or turning presolve off by setting PRESOLVE to 0.
- 114 Fatal error - pool hash table full at vector <vector>.
Internal error. Please contact your local support office.
- 120 Problem has too many rows and columns. The maximum is <num>
Xpress‑MP cannot input your problem since the number of rows plus columns exceeds the maximum allowed. If you have purchased any other than the Hyper version of the software please contact your local sales office to discuss upgrading it to solver larger problems.
- 122 Corrupt solution file.
Solution file .SOL could not be accessed. Please make sure that there is adequate disk space and that the file is not being used by another process.
- 127 Not found: <vector>.
An attempt has been made to use a row or column <vector> that cannot be found in the problem. Please check spelling and try again.
- 130 Bound type illegal <type>.
Illegal bound type <type> has been used in the basis file .BSS. A new basis will be created internally where the column with the illegal bound type will be at its lower bound and the rest of the columns and rows will maintain their basic/non-basic status. Please check that you are using XPRSreadbasis (READBASIS) with the t flag to read compact format basis.
- 131 No column: <col>.
Column <col> used in basis file .BSS does not exist in the problem. A new basis will be created internally from where column <col> will have been removed and the rest of columns and rows will maintain their basic/non-basic status.
- 132 No row: <row>.
Row <row> used in basis file .BSS does not exist in the problem. A new basis will be created internally from where row <row> will have been removed and the rest of columns and rows will maintain their basic/non-basic status.
- 140 Basis lost - recovering.
The number of rows in the problem is not equal to the number of basic rows + columns in the problem, which means that the existing basis is no longer valid. This will be detected when re-optimizing a problem that has been altered in some way since it was last optimized (see below). A correct basis is generated automatically and no action needs to be taken. The basis can be lost in two ways: (1) if a row is deleted for which the slack is non-basic: the number of rows will decrease by one, but the number of basic rows + columns will be unchanged. (2) if a basic column is deleted: the number of basic rows + columns will decrease by one, but the number of rows will be unchanged. You can avoid losing the basis by only deleting rows for which the slack is basic, and columns which are non-basic. (The XPRSgetbasis function can be used to determine the basis status.) To delete a non-basic row without losing the basis, bring it into the basis first, and to delete a basic column without losing the basis, take it out of the basis first - the functions XPRSgetpivots and XPRSpivot may be useful here. However, remember that the message is only a warning and the Optimizer will generate a new basis automatically if necessary.
- 142 Type illegal <type>.
An illegal priority type <type> has been found in the directives file .DIR and will be ignored. Please refer to Appendix Log and File Formats for a description of valid priority types.
- 143 No entity <ent>.
Entity <ent> used in directives file .DIR cannot be found in the problem and its corresponding priority will be ignored. Please check spelling and that the column <ent> is actually declared as an entity in the BOUNDS section or is a set member.
- 151 Illegal MARKER.
The line marking the start of a set of integer columns or a set of columns belonging to a Special Ordered Set in the .MPS file is incorrect.
- 152 Unexpected EOF.
The Optimizer has found an unexpected EOF marker character. Please check that the input file is correct and input again.
- 153 Illegal card at line <line>.
Line <line> of the .MPS file could not be interpreted. Please refer to the Reference Manual for information about the valid MPS format.
- 155 Too many files open for reading: <file>.
The Optimizer cannot read from file <file> because there are too many files already open. Please close some files and try again.
- 170 Corrupt global file.
Global file .GLB cannot be accessed. Please make sure that there is adequate disk space and that the file is not being used by another process.
- 171 Invalid row type for row <row>.
XPRSalter (ALTER) cannot change the row type of <row> because the new type is invalid. Please correct and try again.
- 172 Scaling too bad to continue.
Scaling is too bad for recursion entries. Please try scaling your matrix.
- 178 Not enough spare rows to remove all violations.
The Optimizer could not add more cuts to the matrix because there is not enough space. Please increase EXTRAROWS before input to improve performance.
- 180 No change to this SSV allowed.
The Optimizer does not allow changes to this control. If you have the student version, please contact your local sales office to discuss upgrading if you wish to change the value of controls. Otherwise check that the Optimizer was initialized properly and did not revert to student mode because of a security problem.
- 181 Cannot alter bound on BV, SC, UI, PI, or set member.
XPRSalter (ALTER) cannot be used to change the upper or lower bound of a variable if its variable type is binary, semi-continuous, integer, partial integer, semi-continuous integer, or if it is a set member.
- 186 Inconsistent number of variables in problem.
A compact format basis is being read into a problem with a different number of variables than the one for which the basis was created.
- 245 Not enough memory to presolve matrix.
The Optimizer required more memory to presolve the matrix. Please increase your virtual paging space or physical memory. If this is not possible try setting PRESOLVE to 0 before optimizing, so that the presolve procedure is not performed.
- 246 Wrong release of binary files. Release <rel1> detected.
Release <rel2> required. The binary file *.BIF created with release <rel1> cannot be read. Please try using release <rel2> or the previous one <rel2>-1 to create the binary file and try again.
- 247 Directive on non-global entity not allowed: <col>.
Column <col> used in directives file .DIR is not a global entity and its corresponding priority will be ignored. A variable is a 'global entity' it is type is not continuous or if it is a set member. Please refer to Appendix Log and File Formats for details about valid entities and set types.
- 255 Not enough space to presolve matrix. Increase <par> before XPRSreadprob (READPROB).
The is not enough space to presolve the matrix. Please increase parameter <par> before XPRSreadprob (READPROB) or turn the presolve procedure off by setting PRESOLVE to 0.
- 256 Simplex Optimizer only: buy barrier Optimizer from Dash Associates.
The Optimizer can only use the simplex algorithm. Please contact your local sales office to upgrade your authorization if you wish to use this command.
- 261 <ent> already declared as a global entity - old declaration ignored.
Entity <ent> has already been declared as global entity. The new declaration prevails and the old declaration prevails and the old declaration will be disregarded.
- 262 Unable to remove shift infeasibilities of &.
Perturbations to the right hand side of the constraints which have been applied to enable problem to be solved cannot be removed. It may be due to round off errors in the input data or to the problem being badly scaled.
- 263 The problem has been presolved.
The problem in memory is the presolved one. An operation has been attempted on the presolved problem. Please optimize again calling XPRSmaxim (MAXIM), XPRSminim (MINIM) with the l flag or tuning presolve off by setting PRESOLVE to 0. If the operation does not need to be performed on an optimized problem just load the problem again.
- 264 Not enough spare matrix elements to remove all violations.
The Optimizer could not add more cuts to the matrix because there is not enough space. Please increase EXTRAELEMS before input to improve performance.
- 266 Cannot read basis for presolved problem. Re-input matrix.
The basis cannot be read because the problem in memory is the presolved one. Please reload the problem with XPRSreadprob (READPROB) and try to read the basis again.
- 268 Cannot perform operation on presolved matrix. Re-input matrix.
The problem in memory is the presolved one. Please reload the problem and try the operation again.
- 277 This version is not authorized to run as a DLL.
The Optimizer subroutine library is not authorized to run as a DLL. Please contact your local sales office to upgrade your authorization if you wish to tun the Optimizer as a DLL.
- 278 No purchase authorization found.
Please check that the xpress.pwd file can be found. The Optimizer will try to use the xpress.pwd file located in its directory and if this fails it will look for it in the directory pointed to by the environment variable XPRESS. If you needed a dongle to run the Optimizer please check that it has been inserted. Contact you local support office if the problem persists.
- 279 Xpress‑MP has not been initialized.
The Optimizer could not be initialized successfully. Please initialize it before attempting any operation and try again.
- 285 Cut pool is full.
- 286 Cut pool is full.
The Optimizer has run our of space to store cuts.
- 287 Cannot read in directives after the problem has been presolved.
Directives cannot be read if the problem in memory is the presolved one. Please reload the problem and read the directives file .DIR before optimizing. Alternatively, re-optimize using the -l flag or set PRESOLVE to 0 and try again.
- 302 Option must be C/c or O/o.
The only valid options for the type of goals are C, c, O and o. Any other answer will be ignored.
- 305 Row <row> (number <num>) is an N row.
Only restrictive rows, i.e. G, L, R or E type, can be used in this type of goal programming. Please choose goal programming for objective functions when using N rows as goals.
- 306 Option must be MAX/max or MIN/min.
The only valid options for the optimization sense are MAX, max, MIN and min. Any other answer will be ignored.
- 307 Option must be P/p or D/d.
The only valid options for the type of relaxation on a goal are P, p, D and d. Any other answer will be ignored.
- 308 Row <row> (number <num>) is an unbounded goal.
Goal programming has found goal <row> to be unbounded and it will stop at this point. All goals with a lower priority than <row> will be ignored.
- 309 Row <row> (number <num>) is not an N row.
Only N type rows can be selected as goals for this goal programming type. Please use goal programming for constraints when using rows whose type is not N.
- 310 Option must be A/a or P/p.
The only valid options for the type of goal programming are A, a, P and p. Any other answer will be ignored.
- 314 Invalid number.
The input is not a number. Please check spelling and try again.
- 316 Not enough space to add deviational variables.
Increase EXTRACOLS before input. The Optimizer cannot find spare columns to spare deviational variables. Please try increasing EXTRACOLS before input to at least twice the number of constraint goals and try again.
- 318 Maximum number of allowed goals is 100.
Goal programming does not support more than 100 goals and will be interrupted.
- 320 This version is not authorized to run under Windows NT.
The Optimizer is not authorized to run under Windows NT. Please contact your local sales office to upgrade your authorization if you wish to run it on this platform.
- 324 Not enough extra matrix elements to complete elimination phase.
Increase EXTRAPRESOLVE before input to improve performance. The elimination phase performed by the presolve procedure created extra matrix elements. If the number of such elements is larger than allowed by the EXTRAPRESOLVE parameter, the elimination phase will stop. Please increase EXTRAPRESOLVE before loading the problem to improve performance.
- 326 Linear Optimizer only: buy QP Optimizer from Dash.
You are not authorized to use the Quadratic Programming Optimizer. Please contact your local sales office to discuss upgrading to the QP Optimizer if you wish to use this command.
- 349 Release <rel1> of binary files used with version <rel2>.
The binary file created with release <rel1> of the software is being used with release <rel2>.
- 352 Command not authorized in this version.
There has been an attempt to use a command for which your Optimizer is not authorized. Please contact your local sales office to upgrade your authorization if you wish to use this command.
- 361 QMATRIX or QUADOBJ section must be after COLUMN section.
Error in matrix file. Please make sure that the QMATRIX or QUADOBJ sections are after the COLUMNS section and try again.
- 362 Duplicate elements not allowed in QUADOBJ section.
The coefficient of a column appears more than once in the QUADOBJ section. Please make sure all columns have only one coefficient in this section.
- 363 Quadratic matrix must be symmetric in QMATRIX section.
Only symmetric matrices can be input in the QMATRIX section of the .MAT or .MPS file. Please correct and try again.
- 364 Problem has too many QP matrix elements. Please increase M_Q.
Problem cannot be read because there are too many quadratic elements. Please increase M_Q and try again.
- 366 Problems with Quadratic terms can only be solved with the barrier.
An attempt has been made to solve a quadratic problem using an algorithm other than the barrier. Please use XPRSmaxim (MAXIM), XPRSminim (MINIM) with the b flag to invoke the barrier solver.
- 368 QSECTION second element in line ignored: <line>.
The second element in line <line> will be ignored.
- 381 Bug in lifting of cover inequalities.
Internal error. Please contact you local support office.
- 386 This version is not authorized to run Goal Programming.
The Optimizer you are using is not authorized to run Goal Programming. Please contact you local sales office to upgrade your authorization if you wish to use this command.
- 387 Parallel code not initialized - continuing in serial mode.
Parallel mode cannot be used. Please check that the number of slaves is greater than 0 and that HPPVM is installed correctly.
- 388 Slave number <num> has failed.
Slave number <num> has failed and its tasks will be reallocated to the remaining slaves.
- 389 Incorrect type of dongle, or security violation on slave <num>.
Xpress‑MP could not be initialized on slave <num> and its tasks will be reallocated to the remaining slaves. See the section on initialization in Chapter Introduction for details. Contact your local support office if the problem persists.
- 390 Slave number <num> has failed - insufficient memory.
Process on slave <num> has been aborted because there is not enough memory. Please increase your virtual page space or physical memory and try again. The tasks of the failing slaves will be reallocated to the remaining slaves.
- 391 All slaves have failed - continuing in serial mode.
All slaves have failed and the optimization will continue in serial mode.
- 392 This version is not authorized to be called from BCL.
This version of the Optimizer cannot be called from the subroutine library BCL. Please contact your local sales office to upgrade your authorization if you wish to run the Optimizer from BCL.
- 394 Fatal communications error.
There has been a communication error between the master and the slave processes. Please check the network and try again.
- 395 This version is not authorized to be called from the Optimizer library.
This version of the Optimizer cannot be called from the Optimizer library. Please contact your local sales office to upgrade your authorization if you wish to run the Optimizer using the libraries.
- 396 Insufficient memory on slave <num>.
Process on slave <num> cannot be started because there is insufficient memory on this slave. Please increase your virtual page space or physical memory and try again. The tasks of the failing slave will be reallocated to the remaining slaves.
- 401 Invalid row type passed to <function>.
Elements <num> of your array has invalid row type <type>. There has been an error in one of the arguments of function <function>. The row type corresponding to element <num> of the array is invalid. Please refer to the section corresponding to function <function> in Console and Library Functions for further information about the row types that can be used.
- 402 Invalid row number passed to <function>.
Row number <num> is invalid. There has been an error in one of the arguments of function <function>. The row number corresponding to element <num> of the array is invalid. Please make sure that the row numbers are not smaller than 0 and not larger than the total number of rows in the problem.
- 403 Invalid global entity passed to <function>.
Element <num> of your array has invalid entity type <type>. There has been an error in one of the arguments of function <function>. The column type <type> corresponding to element <num> of the array is invalid for a global entity.
- 404 Invalid set type passed to <function>.
Element <num> of your array has invalid set type <type>. There has been an error in one of the arguments of function <function>. The set type <type> corresponding to element <num> of the array is invalid for a set entity.
- 405 Invalid column number passed to <function>.
Column number <num> is invalid. There has been an error in one of the arguments of function <function>. The column number corresponding to element <num> of the array is invalid. Please make sure that the column numbers are not smaller than 0 and not larger than the total number of columns in the problem, COLS, minus 1. If the function being called is XPRSgetobj or XPRSchgobj a column number of -1 is valid and refers to the constant in the objective function.
- 406 Invalid row range passed to <function>.
Limit <lim> is out of range. There has been an error in one of the arguments of function <function>. The row numbers lie between 0 and the total number of rows of the problem. Limit <lim> is outside this range and therefore is not valid.
- 407 Invalid column range passed to <function>.
Limit <lim> is out of range. There has been an error in one of the arguments of function <function>. The column numbers lie between 0 and the total number of columns of the problem. Limit <lim> is outside this range and therefore is not valid.
- 408 Too long a row or column name passed to <function>.
Name number <num> is too long. There has been a error in one the arguments of function <function>. The row or column name corresponding to element <num> of the array is too long.
- 409 Invalid directive passed to <function>.
Element <num> of your array has invalid directive <type>. There has been an error in one of the arguments of function <function>. The directive type <type> corresponding to element <num> of the array is invalid. Please refer to the Reference Manual for a list of valid directive types.
- 410 Invalid row basis type passed to <function>.
Element <num> of your array has invalid row basis type <type>. There has been an error in one of the arguments of function <function>. The row basis type corresponding to element <num> of the array is invalid.
- 411 Invalid column basis type passed to <function>.
Element <num> of your array has invalid column basis type <type>. There has been an error in one of the arguments of function <function>. The column basis type corresponding to element <num> of the array is invalid.
- 412 Invalid parameter number passed to <function>.
Parameter number <num> is out of range. LP or MIP parameters and controls can be used in functions by passing the parameter or control name as the first argument or by passing an associated number. In this case number <num> is an invalid argument for function <function> because it does not correspond to an existing parameter or control. If you are passing a number as the first argument, please substitute it with the name of the parameter or control whose value you wish to set or get. If you are already passing the parameter or control name, please check Console and Library Functions to make sure that is valid for function <function>.
- 413 Not enough spare rows in <function>.
Increase EXTRAROWS before input. There are not enough spare rows to complete function <function> successfully. Please increase EXTRAROWS before XPRSreadprob (READPROB) and try again.
- 414 Not enough spare columns in <function>.
Increase EXTRACOLS before input. There are not enough spare columns to complete function <function> successfully. Please increase EXTRACOLS before XPRSreadprob (READPROB) and try again.
- 415 Not enough spare matrix elements in <function>.
Increase EXTRAELEMS before input. There are not enough spare matrix elements to complete function <function> successfully. Please increase EXTRAELEMS before XPRSreadprob (READPROB) and try again.
- 416 Invalid bound type passed to <function>.
Element <elem> of your array has invalid bound type <type>. There has been an error in one of the arguments of function <function>. The bound type <type> of element number <num> of the array is invalid.
- 418 Invalid cut number passed to <function>.
Element <num1> of your array has invalid cut number <num2>. Element number <num1> of your array contains a cut which is not stored in the cut pool. Please check that <num2> is a valid cut number.
- 419 Not enough space to store cuts in <function>.
There is not enough space to complete function <function> successfully.
- 422 Solution is not available.
There is no solution available. This could be because the problem in memory has been changed or optimization has not been performed. Please optimize and try again.
- 423 Duplicate rows/columns passed to <function>.
Element <elem> of your array has duplicate row/col number <num>. There has been an error in one of the arguments of function <function>. The element number <elem> of the argument array is a row or column whose sequence number <num> is repeated.
- 424 Not enough space to store cuts in <function>.
There is not enough space to complete function <function> successfully.
- 425 Column already basic.
The column cannot be pivoted into the basis since it is already basic. Please make sure the variable is non-basic before pivoting it into the basis.
- 426 Column not eligible to leave basis.
The column cannot be chosen to leave the basis since it is already non-basic. Please make sure the variable is basic before forcing it to leave the basis.
- 427 Invalid column type passed to <function>.
Element <num> of your array has invalid column type <type>. There has been an error in one of the arguments of function <function>. The column type <type> corresponding to element <num> of the array is invalid.
- 428 Increase EXTRAMIPENTS before input.
There are not enough spare global entities to complete function <function> successfully. Please increase EXTRAMIPENTS before input and try again.
- 430 Column types cannot be changed during the global search.
The Optimizer does not allow changes to the column type while the global search is in progress. Please call this function before starting the global search or after the global search has been completed. You can call XPRSmaxim (MAXIM) or XPRSminim (MINIM) with the l flag if you do not want to start the global search automatically after finding the LP solution of a problem with global entities.
- 434 Invalid name passed to XPRSgetindex.
A name has been passed to XPRSgetindex which is not the name of a row or column in the matrix.
- 436 Cannot trace infeasibilities when integer presolve is turned on.
Try XPRSmaxim (XPRSmaxim) / XPRSminim (MINIM) with the l flag. Integer presolve can set upper or lower bounds imposed by the column type as well as those created by the interaction of the problem constraints. The infeasibility tracing facility can only explain infeasibilities due to problem constraints.
- 473 Row classification not available.
- 501 Error at <line> Empty file.
Read aborted. The Optimizer cannot read the problem because the file is empty.
- 502 Warning: 'min' or 'max' not found at <line.col>. No objective assumed.
An objective function specifier has not been found at column <col>, line <line> of the LP file. If you wish to specify an objective function please make sure that 'max', 'maximize', 'maximum', 'min', 'minimize' or 'minimum' appear.
- 503 Objective not correctly formed at <line.col>. Aborting.
The Optimizer has aborted the reading of the problem because the objective specified at line <line> of the LP file is incorrect.
- 504 No keyword or empty problem at <line.col>.
There is an error in column <col> at line <line> of the LP file. Neither 'Subject to', 'subject to:', 'subject to', 'such that' 's.t.', or 'st' can be found. Please correct and try again.
- 505 A keyword was expected at <line.col>.
A keyword was expected in column <col> at line <line> pf the LP file. Please correct and try again.
- 506 The constraint at <line.col> has no term.
A variable name is expected at line <line> column <col>: either an invalid character (like '+' or a digit) was encountered or the identifier provided is unknown (new variable names are declared in constraint section only).
- 507 RHS at <line.col> is not a constant number.
Line <line> of the LP file will be ignored since the right hand side is not a constant.
- 509 The type of the constraint at <line.col> has not been specified.
The constraint defined in column <col> at line <line> of the LP file is not a constant and will be ignored.
- 510 Upper bound at <line.col> is not a numeric constant.
The upper bound declared in column <col> at line <line> of the LP file is not a constant and will be ignored.
- 511 Bound at <line.col> is not a numeric constant.
The bound declared in column <col> at line <line> of the LP file is not a constant and will be ignored.
- 512 Unknown word starting with an 'f' at <line.col>. Treated as 'free'.
A word staring with an 'f' and not know to Xpress‑MP has been found in column <col> at line <line> of the LP file. The word will be read into Xpress‑MP as 'free'.
- 513 Wrong bound statement at <line.col>.
The bound statement in column <col> at line <line> is invalid and will be ignored.
- 514 Lower bound at <line.col> is not a numeric constant. Treated as -inf.
The lower bound declared in column <col> at line <line> of the LP file is not a constant. It will be translated into Xpress‑MP as the lowest possible bound.
- 515 Sign '<' expected at <line.col>.
A character other than the expected sign '<' has been found in column <col> at line <line> of the LP file. This line will be ignored.
- 516 Problem has not been loaded.
The problem could not be loaded into Xpress‑MP. Please check the other error messages appearing with this message for more information.
- 517 Row names have not been loaded.
The name of the rows could not be loaded into Xpress‑MP. Please check the other error messages appearing with this message for more information.
- 518 Column names have not been loaded.
The name of the columns could not be loaded into Xpress‑MP. Please check the other error messages appearing with this message for more information.
- 519 Not enough memory at <line.col>.
The information in column <col> at line <line> of the LP file cannot be read because all the allocated memory has already been used. Please increase your virtual page space or physical memory and try again.
- 520 Unexpected EOF at <line.col>.
An unexpected EOF marker character has been found at line <line> of the LP file and the loading of the problem into the Optimizer has been aborted. Please correct and try again.
- 521 Number expected for exponent at <line.col>.
The entry in column <col> at line <line> of the LP file is not a properly expressed real number and will be ignored.
- 522 Line <line> too long (length>255).
Line <line> of the LP file is too long and the loading of the problem into the Optimizer has been aborted. Please check that the length of the lines is less than 255 and try again.
- 523 Xpress‑MP cannot reach line <line.col>.
The reading of the LP file has failed due to an internal problem. Please contact your local support office immediately.
- 524 Constraints could not be read into Xpress‑MP. Error found at <line.col>.
The reading of the LP constraints has failed due to an internal problem. Please contact your local support office immediately.
- 525 Bounds could not be set into Xpress‑MP. Error found at <line.col>.
The setting of the LP bounds has failed due to an internal problem. Please contact your local support office immediately.
- 526 LP problem could not be loaded into Xpress‑MP. Error found at <line.col>.
The reading of the LP file has failed due to an internal problem. Please contact your local support office immediately.
- 527 Copying of rows unsuccessful.
The copying of the LP rows has failed due to an internal problem. Please contact your local support office immediately.
- 528 Copying of columns unsuccessful.
The copying of the LP columns has failed due to an internal problem. Please contact your local support office immediately.
- 529 Redefinition of constraint at <line.col>.
A constraint is redefined in column <col> at line <line> of the LP file. This repeated definition is ignored.
- 530 Name too long. Truncating it.
The LP file contains an identifier longer than 64 characters: it will be truncated to respect the maximum size.
If you have any comments or suggestions about these pages, please send mail to docs@dashoptimization.com.