Event Logging Codes

All events that are logged to MCS have an event code associated with them. These are listed in the View Events page under Event Codes. The following codes are listed numerically and divided into functional groups, such as general errors, navigation and datastream events.

100000 - 100049 Datastream Events

Event code Description
100000 The CONNECT command was used to request a specific printer but the device-name requested is the partner to some terminal.
100001 The requested device-name is already associated with another session.
100002 The ASSOCIATE command was used and either the device-name is not a printer or the device-name is not a terminal.
100003 The resource name or device name specified in the CONNECT or ASSOCIATE commands is not known to the server.
100004 The server does not support the requested device type.
100005 The requested device-name or resource-name is incompatible with the requested device-type (such as terminal/printer mismatch).
100006 An unknown error is device type or name processing has occurred.
100007 The server is not configured to satisfy the type of request sent by the client.
100008 Attempt to write to a protected field.
100009 An invalid command was received.
100010 An illegal buffer address or order sequence was received.
100011 A connection to the host has not yet been established.
100012 A connection of the required type could not be established.
100013 Connection not configured.
100014 The connection to the host has been terminated.
100015 Read interrupted.
100016 Received an unknown data type code in the TN3270E header
100017 Invalid command for this terminal mode
100018 Invalid cursor position
100019 Invalid bind state
100020 Invalid suspend state
100021 Received invalid buffer address
100022 Received an invalid length for Write Structured Field
100023 Received an invalid ID fro Write Structured Field
100024 Received invalid Write Structured Field command byte
100025 Multiple partitions are not supported
100026 Received an invalid PID for query
100027 Received an invalid PID for query list
100028 Received an invalid read partition type
100029 Received data following EAU
100030 Negative values are not allowed
100031 Configuration failure
100032 Received invalid character set
100033 Blocking read timed out
100034 Invalid mode for command
100035 Received unknown op code
100036 Invalid data stream command
100037 Incorrect position in data chain
100038 Invalid SF address
100039 Invalid WSF address
100040 Invalid roll parameter
100041 Invalid SOH length
100042 Premature data stream termination
100043 Invalid row or column
100044 Too many fields
100045 Invalid field length
100046 Address less than current address
100047 Illegal field attribute
100048 Attempt to write past end of buffer
100049 A connection to the host could not be established

200000 - 200041 Navigation Engine Events

Event code Description
200000 Invalid WHERE rule
200001 Invalid table START rule
200002 Invalid table END rule
200003 Invalid table NEW PAGE rule
200004 Invalid table NEW DETAIL PAGE rule
200005 Invalid table NEW DETAIL PAGE ACTION rule
200006 Invalid table NEW PAGE ACTION rule
200007 Unrecognized screen
200008 There is no initial state defined for this procedure
200009 The host is not in any of the initial states for this procedure
200010 This procedure does not contain data for the initial state
200011 Unrecognized screen when returning from detail state
200012 Unrecognized screen when executing next page action
200013 The connection is closed
200014 The procedure name is invalid
200015 The procedure version is invalid
200016 The procedure parameter is invalid
200017 Timeout executing navigation procedure
200018 The application could not connect to the Runtime Service
200019 Invalid or missing server configuration parameter
200020 An error occurred in communication with the remote server
200021 An error occurred on the remote server
200022 The requested user is already logged on
200023 The connection is closed because of a terminal action
200025 The host did not send a transient screen as expected
200040 A task endpoint was reached.
200041 A task endpoint was reached in error

270000 - 290002 General Navigation Events

Event code Description
270000 Begin navigation
270001 End navigation
270002 Next state
270003 Next state (transient)
270004 Begin table navigation
270005 End table navigation
270006 Table next page
270008 Table detail page
270009 Reset task
270010 Reset task failed
270011 End navigation. Task failed.
280000 General error
280001 General warning
280002 General information
290000 User defined error
290001 User defined warning
290002 User defined information

300000 - 300008 Runtime Service Events

Event code Description
300000 The runtime engine could not download the requested NavMap from the MCS server. This may be because the NavMap's read-only attribute has been set, or because the NavMap does not exist on the server. If the file exists, check its attributes; otherwise to make the NavMap available, publish your project from Task Builder to MCS.
300001 The client requested a connection from a session pool that does not exist on the runtime engine. This could be because the requested session pool name is different from the NavMap name, or because the session pool has not been configured. This could also occur if internal files required by the Runtime Service have been changed or cannot be found in the expected location.
300002 The requested item cannot be found. A variety of situations can cause this problem. The item name should help you make a more specific diagnosis.
300003 Corrupt configuration file. Either the file ConfigTree.db or another internal data file (.data extension) has been corrupted or is of an incompatible version. This may be because a file was manually altered. These files are required by the Runtime Service. To re-create the files, the Runtime Service must be reinitialized. See the Runtime Service online help in the User's Guide for instructions.
300004 One of the files required by the Runtime Service was moved or deleted after the session pool was configured. You can either copy the file back to its original location, or reinitialize the Runtime Service to re-create the file.
300005 RMI port in use. This error usually indicates that another instance of the Runtime Service or another application is listening for network traffic on the same port. Make sure only one instance of the Runtime Service has been started. If another application is competing for the port, edit the screen.properties file and change the value associated with the rmi.port key, then restart the Runtime Service.
300006 The Runtime Service configuration server could not be started. This error could result from using an incompatible version of the ConfigTree.db file. try terminating your runtime and regenerating the ConfigTree.db file.
300007 The Runtime Service configuration server could not be initialized. This error could result from using an incompatible version of the ConfigTree.db file. try terminating your runtime and regenerating the ConfigTree.db file.
300008 The Runtime Service cannot download the custom steps jar file from the MCS server. This may be beacasue the jar file's read-only attribute has been set, or because the jar does not exist on the server. If the file exists, check its attributes; otherwise to make the NavMap available, publish your project from Task Builder to MCS.

400000 - 400011 Session Allocation Events

Event code Description
400000 Pool started
400001 Pool stopped
400002 Connection deallocated
400003 Connection allocated
400004 Connection removed
400005 Connection added
400006 Error occurred
400007 Connection closed
400008 Pool added
400009 Pool removed
400010 A blocking read timed out; the navigation engine could not connect to the host. A variety of situations can cause this message to be displayed. Most commonly, this error occurs if the hsot displays an unrecognized screen while a task is running.
400011 Could not connect to host. There is a problem connecting to or logging into the host. Either the host is down, or the login failed because of an incorrect username or password combination or because that user is already logged in. You may need to specify a different username or password, or change the username and password options in the pool configuration.
400012 Connection creation failure. Setting connection creation retry interval to {0}.
400013 Connection clean-up error.

500000 - 500004 System Events

Event code Description
500000 Runtime started (version {0})
500001 Runtime stopped.
500002 The Runtime Service cannot communicate with the MCS Service Agent. The runtime engine will continue to operate, but any errors or events it encounters will not be reported to MCS.
500003 Runtime start failure.
500004 Runtime stop failure.
Related Topics
Bullet Synapta Services Builder, Overview
Bullet Configuring MCS Event Logging
Bullet Configuring Synapta Services Builder for Screens Event Logging
  Attachmate