gpss_manual
.pdfArgument B must be greater than argument A.
When the arguments were evaluated, argument B was not greater than argument A. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Arithmetic overflow.
The result of the operation exceed the maximum value permitted. You must change values, operands, or the flow of
Transactions in the simulation to prevent this condition.
Array coordinate is out of range.
The element of the array does not exist. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Array ordinal error.
The element of the array does not exist. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Assembly count was not positive.
The evaluation of an assembly count results in a 0 or negative value. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Attempt to release an idle Facility.
The Active Transaction is attempting to release a Facility which it neither owns nor has been preempted from. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Attempt to release an unowned Facility.
The Active Transaction is attempting to release a Facility which is not owned. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Attempt to release more storage than existed.
The Active Transaction is attempting to cause a storage entity to have more available capacity than was defined in the STORAGE Command. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Authorization has failed.
You have attempted an action which requires authorization that you do not currently have. Please consult with your Network Administrator.
Bad format for call data.
An error occurred during an input/output operation. Follow the
GPSS World Error procedure, above.
Block index is not positive.
An incremental value used to calculate Block addresses is zero or negative. You must change values, operands, or the flow of
Transactions in the simulation to prevent this condition.
Block index is too big.
A Block location was calculated that exceeds the number of
Blocks in the model. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Block labels cannot be used elsewhere.
Block labels cannot be used as entity names or as names in other parts of the model.
Block limit is too small.
The Block limit location comes before the starting Block location. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Call stack overflow. Possible circular reference. Increase the stack size.
The nesting depth of procedure calls exceeded the maximum allowed. This maximum can be set in the Model Settings Notebook. It is possible that the Procedure calls formed an unending sequence that you must change. This can happen if a Procedure calls the Procedure which called it.
Can’t get Local Plus Array.
A memory request was denied. The maximum memory request can be specified in the Simulate Page of the Model Settings
Notebook. Be sure you have enough swap space on your hard disk drives.
Can’t get memory for Text String.
A memory request was denied. The maximum memory request can be specified in the Simulate Page of the Model Settings Notebook. Be sure you have enough swap space on your hard disk drives.
Can’t get Numeric Group Element.
A memory request was denied. The maximum memory request can be specified in the Simulate Page of the Model Settings
Notebook. Be sure you have enough swap space on your hard disk drives.
Can’t get Parameter Block.
A memory request was denied. The maximum memory request can be specified in the Simulate Page of the Model Settings
Notebook. Be sure you have enough swap space on your hard disk drives.
Can’t get Transaction Parameter.
A memory request was denied. The maximum memory request can be specified in the Simulate Page of the Model Settings
Notebook. Be sure you have enough swap space on your hard disk drives.
Can’t get Transaction queuing element.
A memory request was denied. The maximum memory request can be specified in the Simulate Page of the Model Settings Notebook. Be sure you have enough swap space on your hard disk drives.
Can’t get Transaction.
A memory request was denied. The maximum memory request can be specified in the Simulate Page of the Model Settings Notebook. Be sure you have enough swap space on your hard disk drives.
Cannot be created.
A memory request was denied. The maximum memory request can be specified in the Simulate Page of the Model Settings Notebook. Be sure you have enough swap space on your hard disk drives.
Cannot find Model Settings to update.
Please follow the Error Reporting Procedure, above.
Cannot perform requested action.
Please follow the Error Reporting Procedure, above.
Character error in statement.
An invalid character was found in a text line. Please correct the character using the full screen editor of the Model Window.
Circular reference in expressions.
The nesting depth of in an expression evaluation exceeded the maximum allowed. This maximum can be set in the Model Settings Notebook. It is possible that the GPSS Variable
Entities and Procedure calls formed an unending sequence that you must change.
This error usually is caused by a circular reference during the evaluation of an expression. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition. You can assign an intermediate value to a savevalue or Transaction parameter. Then evaluate another function or variable based on the saved value.
Conjugate block is not a MATCH block.
The Active Transaction is attempting to test for a match condition in a Block which is not a MATCH Block. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Corrupt stack.
Please follow the Error Reporting Procedure, above.
COUNT block ran out of entities.
The Active Transaction has initiated a count calculation in a
COUNT Block which ran out of entities before it could be completed. You must change values, operands, or the flow of
Transactions in the simulation to prevent this condition.
DASD error.
An input or output operation has failed. The system reports that a hardware failure has occurred. Retry the operation. If the error persists, contact your hardware support person for assistance.
Data Stream failed to open.
The Data Stream OPEN Block failed.
Data Stream read failed.
The Data Stream READ Block failed. A hardware error may have occurred.
Data Stream write failed.
The Data Stream WRITE Block failed. A hardware error may have occurred.
Datum has not been initialized.
You have attempted to use a variable in an operation before it has been given an initial value. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Decrement not defined for this data type.
The variable has a value which could not be coerced into an arithmetic value. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Divide not defined for this data type.
The variable has a value which could not be coerced into an arithmetic value. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Division overflow.
The result of the operation exceed the maximum value permitted. You must change values, operands, or the flow of
Transactions in the simulation to prevent this condition.
Division range error.
One of the operands has a value for which the operation is not defined. Divide by zero. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Do you really want to write over the existing file?
A file by the same path and name already exists. If you answer yes the existing file will be replaced.
Do you want to retry?
A temporary failure was detected. If you answer yes, the operation will be retried.
Do you want to Save the changes?
Changes have been made to a model or its settings, or the settings have been refreshed. If you answer yes, it will be written out to the Primary Model File.
Entity is not a BVariable.
The Active Transaction caused an attempt to evaluate a
Variable Entity which does not exist. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Entity is not a Variable.
The Active Transaction caused an attempt to evaluate a variable entity which does not exist. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Error creating ANOVA Table.
An error occurred while attempting to perform the calculation in an ANOVA Window. Each treatment level must have more than
1 result, and for an ANOVA Table there must be more than 1 treatment level. Treatment levels, when specified, must be nonnegative integers.
Error in derivative Evaluation found while Integrating:
An error was detected evaluating the derivative while attempting to integrate the following User Variable. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Error in INCLUDE file.
The Translator detected a syntax error in a Secondary Model
File. You should open the Model Window onto this file and
Translate as if it were the Primary Model File and correct the errors.
Error in Model. Can’t open Block View. Please Translate, and make corrections.
The Translator detected a syntax error in the Model File when an attempt was made to open the Block Input Window. Please Translate the model and correct the errors before attempting to open the Block Input Window.
Error in Operand A of QUEUE.
The evaluation of Operand A of a QUEUE Block resulted in a nonpositive value You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Error in Threshold Evaluation found while Integrating:
An error was detected evaluating a Transaction generation threshold while attempting to integrate the following User
Variable. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Error priming GENERATE Block with its first Transaction.
GPSS World was not able to initialize the GENERATE block with its first Transaction. There is an error in the calculation of its arrival time, or in one of the other Operands of the GENERATE Blocks.
Error processing the interaction.
The Translator detected a syntax error in the list of Interactive Statements. Please correct this and retry the interaction.
Error writing Default Settings and Configuration.
An error occurred writing model settings or project configuration to disk. This could be caused by a hardware error, or a disk full condition.
Error writing Report File.
An error occurred writing a Report File to disk. This could be caused by a hardware error, or a disk full condition.
Error: Unable to delete the file.
An attempt to delete a file failed. The file could be shared with another process, it could no longer exist, or a hardware error could have occurred.
EXECUTE block cannot act on another EXECUTE block.
The Active Transaction caused an EXECUTE Block to attempt to execute another EXECUTE Block, or itself. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Exponentiation Overflow.
The result of the operation exceed the maximum value permitted. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
File Close error.
An attempt to close failed. A hardware error could have occurred.
File length error.
An attempt to read a file failed. The file system could be corrupt, or a hardware error could have occurred.
File Open error.
An attempt to open a file failed. The file system could be corrupt, or a hardware error could have occurred.
File Read error.
An attempt to read a file failed. The file system could be corrupt, or a hardware error could have occurred.
File Read/Write error.
An attempt to read or write a file failed. The file system could be corrupt, or a hardware error could have occurred.
File type error.
An attempt to access a file failed. The file system could be corrupt, or a hardware error could have occurred.
File was not created by this version of GPSS World. Settings have been refreshed.
A Model File was opened which did not include the same version of Model Settings as that used by the software. The
Model Settings have been refreshed with the default values.
File write error. Possible disk full.
An error occurred writing a File to disk. This could be caused by a hardware error, or a disk full condition.
Filename exceeded range.
The file specification is too long. Choose a short specification, or use a different directory.
Floating point exception during Integration.
A floating point operation encountered an overflow or underflow. Scale the values of your variables so that they fit into real value limits.
Font must be between 4 and 200 points. Using 12 Points.
You must use a Font between 4 and 200 points.
GENERATE block must have A or D operand.
You cannot use a GENERATE Block that has neither A nor D
Operand.
Help System failure.
The online Help System is not active. Be sure you have rebooted after the installation.
Identifier has not been defined.
You have referred to a name which you did not define. Add the appropriate definition to the model.
Illegal attempt to make Queue entity content negative.
A Transaction tried to enter a QUEUE or DEPART Block, which would have caused the content of a queue entity to be negative. This is not allowed. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Illegal combination of operands in ALTER block.
You have used an illegal combination of operands in an ALTER
Block. Please consult Chapter 7 of this manual for the details on using ALTER blocks.
Illegal combination of operands in REMOVE block.
You have used an illegal combination of operands in a
REMOVE Block. Please consult Chapter 8 of this manual for the details on using REMOVE blocks.
Illegal combination of operands in UNLINK block.
You have used an illegal combination of operands in an
UNLINK Block. Please consult Chapter 8 of this manual for the details on using UNLINK blocks.
Illegal SNA class in COUNT or SELECT block.
You have used an illegal SNA class in operand E of a COUNT or SELECT Block. Please consult Chapter 8 of this manual for the details on using these blocks.
Incorrect Keyword.
You have used a keyword which does not belong where you tried to use it. Please correct the statement.
Incorrect media; a CRC error has occurred.
A media error has occurred attempting to access an external file. Please replace the media where the file occurred.
Increment not defined for this data type.
The variable has a value which could not be coerced into an arithmetic value. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Input and output have the same name.
Do not use the same name for input and output.
Integer division overflow.
The result of the operation exceed the maximum value permitted. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Integer division range error.
One of the operands has a value for which the operation is not defined. Divide by zero. You must change values, operands, or the flow of Transactions in the simulation to prevent this
condition.
Integration Tolerance cannot be maintained for :
During the integration of the following variable, a reduction in ministep size was not sufficient to bring the local error below the error tolerance. You must either increase the Error
Tolerance in the Simulate Page of the Model Setting Notebook, or you must create your own integration method using one or more PLUS Procedures. It is possible that the derivatives of Integration Variables are too large in magnitude.
Integration Variable was not initialized:
When attempt was made to integrate the following variable it was found to have no initial value. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Internal depth error.
Please follow the Error Reporting Procedure, above.
Invalid 0 or negative argument.
The argument must be strictly positive. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Invalid access.
Please follow the Error Reporting Procedure, above.
Invalid compilation type.
Please follow the Error Reporting Procedure, above.
Invalid data type.
Please follow the Error Reporting Procedure, above.
Invalid discrete Function argument.
When the argument of a discrete function was evaluated it was too large or it was 0 or negative. You must change values, operands, or the flow of Transactions in the simulation to prevent this condition.
Invalid drive or directory.
An attempt was made to use an invalid drive or directory. Please correct and retry.
Invalid expression.
An expression was not correctly formed using defined syntax.
Please correct it and retry the operation. The formal grammar