What does my error message mean?

 

ALOGIT can fail in one of three ways:...

 

  1. ALOGIT generates a message telling you that there is a problem. There are three types of message...

-        WARNING: this is information the user might like to be informed about. These messages will not stop the run and they may not be important but in some cases they may indicate a need for action.

-        ERROR: this is the most common type of message and usually means that the user has asked for something that cannot be understood or that is impossible.  There will be other information which should help you to understand what is wrong.  Change the input and try again.  ERROR messages in ALOGIT 4 will cause a system code 41 to be generated, which may be useful if you are writing specialised batch files.

-        PROGRAM ERROR: something has gone wrong in the program itself.  The user will not usually be able to fix this problem, although you may of course be able to do something a little different which avoids it.  This is not supposed to happen!  ALOGIT Software & Analysis would appreciate information about errors of this type so we can fix them in future releases of ALOGIT.  PROGRAM ERROR messages will also cause ALOGIT 4 to generate system code 41 and ALOGIT will usually stop immediately.

 

  1. ALOGIT ‘crashes’, which will usually be associated with a system message and a number of screen messages generated by the system that are normally unintelligible.  This is not supposed to happen!  ALOGIT Software & Analysis would appreciate information about errors of this type so we can fix them in future releases of ALOGIT.

 

  1. Something goes wrong in the file handling processes. This is usually because the user is causing ALOGIT to request more system resources than are available. These messages are identified by an error code number. The most common error codes are listed below, together with fix advice which should be sufficient for most of these problems to be fixed by the user. Please let us know if there are problems you cannot solve.

 

Back to Software FAQ's

 

Asking for Help

To ask ALOGIT Software & Analysis for help contact the help desk and send:

-        the control file, or a reduced version of it that still causes the problem

-        the data file, or sufficient records from it to cause the problem

-        the print file (LOG file or F16 file).

The F11 and F14 files are not usually helpful in solving a problem.

 

Confidentiality will be preserved.  We shall do our best to respond quickly.

 

Back to Software FAQ's

 

File Handling Error Messages:

number

message

meaning

6103

invalid REAL

This message may be generated when a data file contains invalid characters such as letters or punctuation marks. Sometimes word processing packages insert codes that lead to this message.

6413

file already connected to a different unit

This message may be generated when the same file name is used for different ALOGIT files. Different file names must be used for all the ALOGIT files.

6414

access not allowed

This message can be caused when the file specified is actually a directory, or the file is specified as read-only when ALOGIT would have to write to it, or when there are sharing conflicts (e.g. on a network).

6416

file not found

This message is caused by the non-existence of an essential file, such as the F11 file.

6417

too many open files

The FILES= command in CONFIG.SYS must be changed to increase the number of files that can be open at any time.

6422

no space left on device

The disk is full!

6504

invalid number in input

This message may be generated when a data file contains invalid characters such as letters or punctuation marks.

6981

initial left parenthesis expected in format

The format supplied by the user for reading data must begin with a left bracket ‘(’ and end with a right bracket ‘)’.

6982-6991

 

These are more complex format errors relating to the reading of data files.

 

Back to Software FAQ's