Entire Net-Work LUW Messages

Used for Software AG internal tracing.

No action is required for this informational message.

An incoming connection from the named Entire Net-Work server node has been received. The reference number (ref-num) given in the message is for internal Software AG use only.

No action is required for this informational message.

The identified database is active on the named Entire Net-Work remote server node and can therefore be accessed from the local node.

No action is required for this informational message.

The identified database has been deactivated on the named Entire Net-Work server node and is therefore no longer available to the local node.

No action is required for this informational message.

An outbound connection has been made to the named Entire Net-Work classic node.

No action is required for this informational message.

This message indicates the node identifier and the maximum possible message size acceptable to the remote node specified by the previous log entry.

No action is required for this informational message.

Entire Net-Work for the named platform is initializing on the named host computer.

No action is required for this informational message.

This message provides the version and patch level for the Entire Net-Work product.

No action is required for this informational message.

This message displays two informational messages strings.

No action is required for this informational message.

This message provides the total number of Kernel requests made to the Kernel.

No action is required for this informational message.

This message provides information to Software AG technical support.

No action is required for this informational message.

This message provides the total number of direct clients connected to the Kernel.

No action is required for this informational message.

This message provides the total number of relayed clients connected to the Kernel.

No action is required for this informational message.

This message provides the length of time the Kernel has been running.

No action is required for this informational message.

This message provides the total number of e-business administration messages made to the Kernel.

No action is required for this informational message.

This message provides the total number of e-business communication errors that occurred with the Kernel.

No action is required for this informational message.

This message provides the total number of replies made by the Kernel.

No action is required for this informational message.

This message provides the total number of bytes input to the Kernel.

No action is required for this informational message.

Entire Net-Work has completed the initialization process.

No action is required for this informational message.

This message provides the total number of bytes output by the Kernel.

No action is required for this informational message.

This message shows license parameter values.

No action is required for this informational message.

This message indicates that you are running with a 90-day trial license.

No action is required for this informational message.

The remote Entire Net-Work node listed in the message has requested a disconnection. The reference number (ref-num) given in the message is for internal Software AG use only.

No action is required for this informational message.

The remote Entire Net-Work node listed in the message has successfully disconnected. The reference number (ref-num) given in the message is for internal Software AG use only.

No action is required for this informational message.

The log file is being closed by a user of the System Management Hub or the NETSTOP utilities. A new net-work.log file is being created.

No action is required for this informational message.

An Adabas database with the identified database number is now available via the Entire Net-Work e-business Listen port (default port number 9010).

No action is required for this informational message.

The Adabas database with the identified database ID is no longer available via the Entire Net-Work e-business Listen port (default port number 9010).

No action is required for this informational message.

The identified classic Entire Net-Work node has indicated an immediate disconnection.

No action is required for this informational message.

The identified e-business database has indicated an immediate disconnection.

No action is required for this informational message.

The identified e-business Adabas database is now active on the local Entire Net-Work node.

No action is required for this informational message.

This message provides an internal transport subsystem message as the result of a previously logged error.

No action is required for this informational message.

This message provides the operating system or hardware type of the remote Kernel.

No action is required for this informational message.

This message provides the total CPU time that occurred since the Kernel started.

No action is required for this informational message.

This message identifies the operating system or hardware platform of the Entire Net-Work node as well as the current date and time. The message is provided at intervals in a log file to assist in identifying the Entire Net-Work configuration.

No action is required for this informational message.

This message identifies the Entire Net-Work Server.

No action is required for this informational message.

This message identifies the Entire Net-Work Client.

No action is required for this informational message.

This message identifies the Entire Net-Work Kernel.

No action is required for this informational message.

This message provides the number of e-business nodes that Entire Net-Work knows about.

No action is required for this informational message.

This message provides the number of e-business nodes to which Entire Net-Work is connected.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report. It displays the number of current direct clients connected to this node.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report. It displays the number of current relayed clients connected to this node.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report. It displays the number of hosts connected to this node.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report. It displays the number of pings to this node.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report. It displays the number of e-business contexts processed by the node.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report. It displays the number of active e-business contexts.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report. It displays the rate (requests per second) at which inbound requests have been processed by the Kernel.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report. It displays the rate (requests per second) at which outbound requests have been processed by the Kernel.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report. It displays the rate (bytes per second) at which inbound data has been processed by the Kernel.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report. It displays the rate (bytes per second) at which outbound data has been processed by the Kernel.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report. It displays the number of e-business relay calls to this node.

No action is required for this informational message.

This message is one of many messages that comprise the Periodic Statistical Data Report.

No action is required for this informational message.

The identified e-business database has indicated an immediate disconnection.

No action is required for this informational message.

The current CPU usage is shown in the message.

No action is required for this informational message.

An attempt to disconnect from a remote Entire Net-Work Server occurred.

No action is required for this informational message.

An outbound connection exists for the Entire Net-Work Server listed in the message.

No action is required for this informational message.

The outbound connection for the Entire Net-Work Server listed in the message failed. The response code from the attempt is also given in the message.

Make sure the node of the outbound connection is up and that its parameters are configured correctly. Then refresh the Entire Net-Work Server connections, restarting it if necessary to do so.

An e-business server is listening on the TCP/IP port listed in the message.

No action is required for this informational message.

An e-business server is listening on the SSL port listed in the message.

No action is required for this informational message.

The SMH server is listening on the TCP/IP port listed in the message.

No action is required for this informational message.

The identified database is now active on the local Kernel and can therefore be accessed by both classic and e-business clients.

No action is required for this informational message.

The identified database has been deactivated on the local node and is therefore no longer available to any clients.

No action is required for this informational message.

A shutdown request has been received for the node name listed in the message.

No action is required for this informational message.

The identified remote System Management Hub operator has requested a shutdown of Entire Net-Work. This instance will complete its shutdown once various administration tasks have completed.

No action is required for this informational message.

The message identifies the signal that interrupted the process before it crashed. These values provide system information useful to Software AG technical support.

No action is required for this informational message.

The message indicates that the e-business server failed. An error number is provided in the message.

Contact your Software AG technical support representative for assistance.

As the result of a periodic heartbeat operations, this classic node was sent a ping message to check its connection path. The classic node replied within the time indicated.

No action is required for this informational message.

As the result of a periodic "heartbeat" operation, this database was sent a "PING" message to check its availability. The database replied within the time indicated.

No action is required for this informational message.

The log file is renamed to netxxxxx.log, where xxxxx is a number. This message appears as the first line on a continuation log file.

No action is required for this informational message.

An e-business server incoming connection is described in the message. The reference number (ref-num) listed in the message is for internal Software AG use only.

No action is required for this informational message.

The identified server is now connected to the local node. The reference number (ref-num) listed in the message is for internal Software AG use only.

No action is required for this informational message.

This message is part of the periodic statistical data report.

None. This message is informational only.

The identified Entire Net-Work Server is now accessible from the local node.

None. This message is informational only.

An immediate disconnection for the named Entire Net-Work Server occurred. The reference number (ref-num) given in the message is for internal Software AG use only.

No action is required for this informational message.

This message lists the value of the parameter used to start the running Kernel.

No action is required for this informational message

This message indicates that a partition has been defined and gives the name of the partition.

No action is required for this informational message

This message identifies the TCP/IP port number on which e-business clients are listening.

No action is required for this informational message

This message identifies the SSL port number on which e-business clients are listening.

No action is required for this informational message

Entire Net-Work is shutting down.Entire Net-Work

No action is required for this informational message.

This message identifies the TCP/IP port on which a classic server is listening.

No action is required for this informational message.

A Kernel has indicated that the identified database is active. However, the local node is already aware of this database due to a previous connection. The duplication is ignored and the original path to the database is maintained.

This error may be caused by a genuine duplication of a database number, which should be corrected by the DBA or by excessively complex connections among classic Entire Net-Work nodes. You should examine your configuration to determine if the connections causing this message can be eliminated.

Entire Net-Work cannot make outbound connections unless connections to other classic Entire Net-Work nodes are defined.

If outbound connections are desired, they must be defined. For more information, see the section Entire Net-Work Administration.

The Adabas context listed in the message has been deleted for the database listed in the message.

No action is required for this warning message.

The local Entire Net-Work Kernel cannot be administered remotely by a System Management Hub. This is normally the result of a specific configuration action to inhibit remote management.

If remote management is desired, the Entire Net-Work Kernel must be restarted with configuration changes.

A connection between two Entire Net-Work nodes was detected. This is not recommended and is usually an indication of a configuration error.

The remote kernel has rejected a connection from Entire Net-Work for open systems. Typical reasons include:

• incorrect configuration at the remote node

• unsolicited mode not enabled at the remote node

• errors in DNS or DHCP operation

No action is required for this informational message.

A connection attempt from the local kernel was rejected by a classic remote node because the local kernel was not defined.

Add the name of the local kernel to the definitions at the remote node or enable unsolicited connections at the remote node.

The Adabas context listed in the message for the database and owners listed in the message is scheduled for deletion.

No action is required for this warning message.

A database has started on the local node; however, this database ID was previously used by another database on a remote node.

This indicates a configuration error that needs to be corrected.

The named classic Entire Net-Work node is disconnecting while there are active database calls being processed. The application with the indicated Terminal ID will receive an Adabas response code 149 (ADARSP149 - communications error) as the database is no longer reachable.

Restart the application.

A user has changed the tracing level to the new numeric level shown in the message.

No action is required for this informational message.

A user has requested a PING operation to the target ID identified in the message. PINGs are used to test the integrity of a remote classic connection to the path to a database.

No action is required for this informational message.

A user has requested that the current logging file be closed and a new log file started.

No action is required for this informational message.

An internal error occurred for an Entire Net-Work Server. It was not possible to create the definitions for a classic database to allow it to be accessed by e-business clients.

Restart Entire Net-Work.

A PING message was received for which there was no PING request. This indicates that a logical messages sequencing failure occurred at a remote database.

If the error persists, restart the remote database.

Following a connection by an e-business database (message WCP0029I), the Entire Net-Work Kernel tried to send a simple Adabas command to the database to test the integrity of the communications path. This test failed. The database is not e-business registered at the local node nor is it broadcast to classic nodes. This error normally results from a failure to provide an XTSaccess URL for the e-business database in the Directory Server. The Adabas response code from the connection attempt is given in the message. For complete information on Adabas response codes, refer to the Adabas messages and codes documentation.

Verify that you have provided an XTSaccess URL for the e-business database in the Directory Server and try again.

An Adabas database has connected previously as a classic or local database, disconnected, and is now being connected as an e-business database. This may be intentional or it may be a configuration error.

No action is required for this informational message.

A database was originally connected as a classic or local database, but an e-business disconnection was received.

The database is not disconnected.

If the error persists, contact your Software AG technical support representative.

During the Kernel startup process, a duplicate URL was discovered in the Directory Server. The duplicate URL is ignored. This error can be caused by incorrect administration of the Directory Server entries.

No action is necessary unless the duplicate URL is in error. In this case, correct the URL as described in your Adabas Directory Server documentation. Read Directory Server Target Entries in the Software AG Directory Server Installation and Administration Guide.

During the Kernel startup process, a URL was read in the Directory Server with a syntax error. The incorrect URL is ignored. This error can be caused by incorrect administration of the Directory Server entries.

Correct the URL as described in your Adabas Directory Server documentation. Read Directory Server Target Entries in the Software AG Directory Server Installation and Administration Guide.

This message indicates that an incoming client connection was made and identifies the client ID, the host ID, the port number, and the number of current active client connections.

No action is required for this informational message.

This message indicates that an client connection was dropped and identifies the client ID and the number of current client connections.

No action is required for this informational message.

An e-business Entire Net-Work Server access definition has not been defined in this Entire Net-Work implementation.

No action is required for this informational message.

A classic Entire Net-Work Server access definition has not been defined in this Entire Net-Work implementation.

No action is required for this informational message.

An Entire Net-Work Client access definition has not been defined in this Entire Net-Work implementation.

No action is required for this informational message.

The name of the license file used for this installation of Entire Net-Work is given in the message.

No action is required for this informational message.

The relay client ID, database ID, host name, port number and number of relayed clients are given in the message..

No action is required for this informational message.

The relay client ID, database ID, and number of relayed clients that have been disconnected are given in the message..

No action is required for this informational message.

The client named in the message is relaying data to the Adabas database identified in the message.

No action is required for this informational message.

The client named in the message is making local calls to the Adabas database identified in the message.

No action is required for this informational message.

The client is identified in the message.

No action is required for this informational message.

The innactive life span of the context is given in the message.

No action is required for this warning message.

Your Entire Net-Work license file does not support SSL use with Entire Net-Work, but SSL settings have been supplied for the kernel.

Verify that the kernel settings are correct and adjust them if necessary. If they are correct, contact your Software AG technical support representative to obtain an updated license file.

An Entire Net-Work-to-Entire Net-Work connection has occurred and the remote Entire Net-Work has a Kernel connected to it.

If a Kernel was started as a Windows service and subsequently shut down by means of the Services Control Panel, this informational message is added to the log.

No action is required for this informational message.

An Entire Net-Work-to-Entire Net-Work connection has occurred and databases known to the remote Entire Net-Work are now known to both.

No action is required for this informational message.

The Kernel listed in the message was successfully migrated from the 7.3 version of Entire Net-Work.

No action is required for this informational message.

The client listed in the message was successfully migrated from the 1.3 version of Entire Net-Work Client.

No action is required for this informational message.

The kernel listed in the message was successfully migrated from the 7.4 version of Entire Net-Work.

No action is required for this informational message.

The client listed in the message was successfully migrated from the 1.4 version of Entire Net-Work Client.

No action is required for this informational message.

An e-business database was rejected for traffic relay, as defined by the Entire Net-Work filter settings. Entire Net-Work will not process requests for the database with the database ID given in the message.

No action is required for this informational message.

A classic database was rejected for traffic relay, as defined by the Entire Net-Work filter settings. Entire Net-Work will not process requests for the database with the database ID given in the message.

No action is required for this informational message.

During the periodic check of its known connections, Entire Net-Work has verified that its connection to the e-business database listed in the message is valid and active.

No action is required for this informational message.

An e-business database was rejected by a filter, as defined by the Entire Net-Work filter settings. Entire Net-Work will not process requests for the database with the database ID given in the message.

No action is required for this informational message.

This message indicates that an incoming classic connection was made.

No action is required for this informational message.

This message indicates that an outgoing classic connection was made.

No action is required for this informational message.

An attempt to connect to an already active connection occurred. The connection attempt was rejected.

No action is required for this informational message.

An attempt to connect by the Kernel referenced in the message was rejected by filters. The Kernel node is included in the rejected filter list.

No action is necessary unless you want a connection by the kernel to be accepted. If you do, adjust the parameters on the Kernel Filters panel in SMH.

Entire Net-Work received an illegal message from a classic server that it could not recognize. The message is ignored.

If the problem persists, contact your Software AG support representative.

An Adabas reply has been received from the identified Kernel for a request that cannot be identified.

If the error persists, restart Entire Net-Work.

The identified Kernel has been disconnected due to an I/O error detected during the send process.

Check the connection status and try again.

A connection failure has been detected by the internal transport subsystem. An internal transport subsystem failure code is provided in the message.

Verify the connections are valid. If the error persists, contact you network administrator or your Software AG support representative for assistance.

An unexpected error has occurred while registering the identified classic database; the return code is provided.

Take corrective action as indicated by the following internal transport subsystem message.

An attempt to connect by the Kernel referenced in the message was rejected by filters. The Kernel node is not included in the accepted filter list.

No action is necessary unless you want a connection by the kernel to be accepted. If you do, adjust the parameters on the Kernel Filters panel in SMH.

The client on the host machine and port listed in the message has been rejected because the host machine is not accepted by the filter settings.

No action is necessary unless you want a connection to be accepted. If you do, adjust the parameters on the Kernel Filters panel in SMH.

An e-business database has connected to Entire Net-Work but has indicated a database number that is not in the valid range of 0 - 65535.

Change the database ID to the valid range.

A classic Entire Net-Work node with an unknown node name attempted to connect to Entire Net-Work while the SECURE parameter was set to ON.

Define the node to Entire Net-Work for open systems.

The host machine listed in the message is not accepted by the filter settings.

No action is necessary unless you want a connection to the host machine to be accepted. If you do, adjust the parameters on the Kernel Filters panel in SMH.

Connecting two Entire Net-Work nodes using the RDA protocol is not allowed.

Remove or redefine the connection attempt.

An error has occurred in a System Management Hub callback routine. The response code is given in the message.

If the problem persists, contact your Software AG support representative.

An error has occurred in a System Management Hub send routine. The return code for the failure is given in the message.

If the problem persists, contact your Software AG support representative.

An error occurred during a broadcast routine. The return code for the failure is given in the message.

Verify that all the nodes are up and correctly configured. If the problem persists, contact your Software AG support representative for assistance.

An error occurred during a relay routine. The return code for the failure is given in the message.

Verify that all the nodes are up and correctly configured. If the problem persists, contact your Software AG support representative for assistance.

A zero length message was received during a relay routine.

If the problem persists, contact your Software AG support representative.

A local database has started with an ID of less than 1 or greater than 65535. The startup is being ignored and the database is inaccessible from this Entire Net-Work node.

Check the database configuration files.

A local database has started with an ID that is already in use by another database (local, classic, or e-business remote) known to this Entire Net-Work node. The duplicate will be ignored.

This indicated a configuration error that needs to be corrected.

An Adabas reply was received from a Kernel. The reply could not be matched to a pending Adabas request and will be ignored.

If the error persists, restart Entire Net-Work.

An internal error occurred registering Entire Net-Work Server. The response code is given in the message.

Contact your Software AG technical support representative for assistance.

The client identified in the message is not recognized by the Entire Net-Work server.

If the problem persists, contact your Software AG support representative.

An internal failure occurred during an Adabas call to an e-business database. The database referenced in the Adabas call and the return code from the call are given in the message.

Verify that the Adabas call is valid for the e-business database. If the problem persists, contact your Software AG support representative.

An internal failure occurred during an Adabas ACBX call to an e-business database. The database referenced in the Adabas call, the return code from the call, and the extended Adabas control block (ACBX) return code are given in the message.

Verify that the Adabas call is valid for the e-business database. If the problem persists, contact your Software AG support representative.

During the periodic check of database status, the database became unavailable.

No user action is required.

During the periodic check of a remote Kernel, the kernel became unavailable. The Kernel connection is disconnected.

No user action is required.

An invalid Adabas DBID was encountered. Connections to the database are disconnected.

If the error persists, contact your Software AG technical support representative.

An unknown Adabas DBID was encountered and is disconnected.

If the error persists, contact your Software AG technical support representative.

An unknown Kernel (identified in the message) was encountered.

If the error persists, contact your Software AG technical support representative.

A message was received on a classic connection that was not in the correct format. This can be caused by a port number configuration problem or it may be a denial of service attempt by Entire Net-Work 7.

The system marks the node as unusable and will not accept data from it.

Review your use of RDA port numbers and correct them if necessary. Otherwise, you can ignore this message.

For some reason, Entire Net-Work cannot start the Kernel identified in the message.

Contact your Software AG technical support representative for assistance.

A syntax error occurred during Entire Net-Work processing. The URL in error and the target ID for the URL are given in the message. This error can occur if manual updates to URL connection information are attempted.

Contact your Software AG technical support representative for assistance.

A proxy error occurred. The client ID, database ID, and the return code from the attempt are given in the message.

Make sure the proxy nodes are all up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

An Entire Net-Work Server error occurred. The client ID, database ID and the return code from the attempt are given in the message.

Make sure the Entire Net-Work Server nodes are all up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

An Entire Net-Work Client error occurred. The client ID, database ID and the return code from the attempt are given in the message.

Make sure the Entire Net-Work Client nodes are all up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

An attempt to relay a request to a database failed. The database ID and the return code from the attempt are given in the message.

Make sure the Entire Net-Work nodes and the database in question are all up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

An attempt to make an Adabas ACBX call to a classic (pre-Version 6 on open systems or pre-Version 8 on mainframe systems) Adabas database was made. ACBX calls are only allowed against Adabas 8 (or later) databases.

Resolve the error (either run the ACBX call against a valid database or change the call to an ACB call) and try again.

A request was made to an invalid database.

Correct the database specification and try again.

A request was made to an inactive Adabas database.

Start the Adabas database and try again.

A communication error occurred. The request is rejected. The database ID of the database to which the request was directed is given in the message.

Verify that all connections and the database in question are up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

An outbound connection was attempted but failed because the target could not be identified..

Verify that all connections are up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

A communication error occurred. The request is rejected. The database ID of the database to which the request was directed is given in the message.

Verify that all connections and the database in question are up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

A communication error occurred. The request is rejected. The return code from the request is given in the message.

Verify that all connections are up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

An unknown client request was encountered. The client ID and Adabas database ID are given in the message.

Verify that all connections are up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

A client request was not processed because the number client connections has been exceeded. The client ID, host name, port number, and maximum number of client connections are given in the message.

Verify that the maximum number of client connections is set correctly. If the problem persists, contact your Software AG support representative for assistance.

An attempt to reply to a client failed. The client ID, Adabas database ID, and return code from the attempt are given in the message.

Verify that all connections are up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

The client on the host machine and port listed in the message was rejected because the CPU threshold was exceeded.

Increase the CPU threshold setting. If the problem persists, contact your Software AG support representative for assistance.

An attempt to reply to a client failed. The client ID, Adabas database ID, and error from the attempt are given in the message.

Verify that all connections are up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

An attempt to connect to a mainframe database failed. The Adabas database ID is given in the message.

Verify that all connections are up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

An error occurred. The Kernel listed in the message is disconnected.

Verify that all connections are up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

An attempt to delete the Adabas context listed in the message for the database listed in the message failed.

Verify that all connections are up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

An attempt to connect to the Adabas database listed in the message could not occur because the context for the database is deleted.

Verify that all connections are up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

An unexpected request to destroy a context was received for a client. The request is rejected.

If the problem persists, contact your Software AG support representative for assistance.

An internal error occurred.

Contact your Software AG technical support representative for assistance.

An internal error has occurred in the internal transport subsystem, preventing the use of Directory Services.

Contact your Software AG technical support representative for assistance.

An internal error has occurred in the internal transport subsystem, preventing the use of Directory Services.

Contact your Software AG technical support representative for assistance.

An internal error has occurred in the internal transport subsystem, preventing the use of Directory Services.

Contact Software AG support with the information from accompanying message WCP0030I.

This error is usually caused by an error in the internal transport subsystem.

See the internal transport subsystem message following this message for more information.

The Entire Net-Work threading mechanism failed.

Repeated occurrences of this message may require a restart of the Entire Net-Work Kernel.

The Entire Net-Work threading mechanism failed.

Repeated occurrences of this message may require a restart of the Entire Net-Work Kernel.

An invalid message was received from a System Management Hub. This error can be caused by incorrect Directory Service entries. The message is ignored.

Check the version of the System Management Hub being used for compatibility with Entire Net-Work.

An invalid message was received from a System Management Hub. This error can be caused by incorrect Directory Service entries. The message is ignored.

Check the version of the System Management Hub being used for compatibility with Entire Net-Work.

An invalid message was received from a System Management Hub. This error can be caused by incorrect Directory Service entries. The message is ignored.

Check the version of the System Management Hub being used for compatibility with Entire Net-Work.

The Entire Net-Work semaphoring mechanism failed. The return code from the call is given in the message.

Contact your Software AG technical support representative for assistance.

The Entire Net-Work threading mechanism failed. The return code from the call is given in the message.

Repeated occurrences of this message may require a restart of the Entire Net-Work Kernel.

An internal error occurred.

Contact your Software AG technical support representative for assistance.

An internal error occurred.

Contact your Software AG technical support representative for assistance.

The Entire Net-Work semaphoring mechanism failed. The return code from the call is given in the message.

Contact your Software AG technical support representative for assistance.

A previously logged error is preventing the startup of Entire Net-Work.

Correct the previously reported error and restart Entire Net-Work.

The Entire Net-Work timer threading mechanism failed. The return code is given in the message.

Repeated occurrences of this message may require a restart of the Entire Net-Work Kernel.

The Entire Net-Work threading mechanism failed. The return code is given in the message.

Repeated occurrences of this message may require a restart of the Entire Net-Work Kernel.

The Entire Net-Work threading mechanism failed. The return code is given in the message.

Repeated occurrences of this message may require a restart of the Entire Net-Work Kernel.

The Entire Net-Work threading mechanism failed. The return code is given in the message.

Repeated occurrences of this message may require a restart of the Entire Net-Work Kernel.

The Entire Net-Work threading mechanism failed. The return code is given in the message.

Repeated occurrences of this message may require a restart of the Entire Net-Work Kernel.

The Entire Net-Work killer threading mechanism failed. The return code is given in the message.

Repeated occurrences of this message may require a restart of the Entire Net-Work Kernel.

The Entire Net-Work killer threading mechanism failed. The return code is given in the message.

Repeated occurrences of this message may require a restart of the Entire Net-Work Kernel.

The Entire Net-Work killer thread ran to completion. The killer thread runs when normal shutdown has problems.

No user action is required.

An attempt was made to use a remoteDirectory Server. The attempt failed.

Determine why the remote Directory Server cannot be accessed, fix the problem, and try again.

A Directory Server problem occurred.

Make sure no Directory Server or Entire Net-Work installation files were deleted and that your user ID has security access to use all files in the installation directories. If the problem persists, contact your Software AG support representative for assistance.

A Directory Server problem occurred.

Make sure no Directory Server or Entire Net-Work installation files were deleted and that your user ID has security access to use all files in the installation directories. If the problem persists, contact your Software AG support representative for assistance.

The license file for Entire Net-Work was not found.

Contact your Software AG technical support representative for assistance.

The product key is missing from the license file.

Contact your Software AG technical support representative for assistance.

The license key in the license file is invalid.

Contact your Software AG technical support representative for assistance.

A required parameter is missing from the license file.

Contact your Software AG technical support representative for assistance.

A required component is missing from the license file.

Contact your Software AG technical support representative for assistance.

All parameters of the license key require a value. The license key is not valid.

Contact your Software AG technical support representative for assistance.

Contact your Software AG technical support representative for assistance.

A memory failure occurred during product license processing.

Contact your Software AG technical support representative for assistance.

The license key in the license file has expired.

Contact your Software AG technical support representative for assistance.

The operating system for which the license applies does not match the operating system of the machine on which you have attempted to deploy Entire Net-Work.

Contact your Software AG technical support representative for assistance.

The license file cannot be read.

Contact your Software AG technical support representative for assistance.

The trial license is write-protected.

Remove the write protection from the trial license file.

An internal ASCII-to-EBCDIC conversion error occurred while trying to process the license file.

Contact your Software AG technical support representative for assistance.

An internal UTF conversion error occurred while trying to process the license file.

Contact your Software AG technical support representative for assistance.

An internal UTF conversion error occurred while trying to process the license file.

Contact your Software AG technical support representative for assistance.

A write error occurred while trying to process the license file.

Contact your Software AG technical support representative for assistance.

An internal error occurred during license file processing.

Contact your Software AG technical support representative for assistance.

An attempt to read the license file failed.

Contact your Software AG technical support representative for assistance.

The number of CPUs you are using exceeds the number allowed by the Entire Net-Work license.

Contact your Software AG technical support representative for assistance.

An attempt to identify the number CPUs during license processing failed.

Contact your Software AG technical support representative for assistance.

An internal error occurred during license processing.

Contact your Software AG technical support representative for assistance.

The CPU ID setting cannot be found in the license file.

Contact your Software AG technical support representative for assistance.

The logical partition name cannot be found while processing the license file.

Contact your Software AG technical support representative for assistance.

An internal error occurred during license processing.

Contact your Software AG technical support representative for assistance.

The MSU value in the license file is insufficient.

Contact your Software AG technical support representative for assistance.

The MSU value in the license needs to be checked.

Contact your Software AG technical support representative for assistance.

An internal error occurred during license processing.

If the error persists, reinstall Entire Net-Work correctly.

An internal error occurred during license processing.

If the error persists, reinstall Entire Net-Work correctly.

An internal error occurred during license processing.

If the error persists, reinstall Entire Net-Work correctly.

UNIX systems only. The $SAG environment variable must point to a standard Software AG product directory structure.

Ensure $SAG is set to the correct value.

The local Entire Net-Work configuration is not licensed to operate in this system. This error can be caused by illegally copying license files.

Obtain a valid license file for Entire Net-Work and install it in the appropriate /Lkey directory.

The license is not valid; it does not provide the maximum number of clients allowed.

Obtain a valid license file for Entire Net-Work and install it in the appropriate /Lkey directory.

The license is not valid; it does not provide the maximum number of clients allowed.

Obtain a valid license file for Entire Net-Work and install it in the appropriate /Lkey directory.

The virtualization parameter PPAR is present for the system.

No action is required for this informational message.

The license has been established for the software package with the physical and logical CPU IDs listed in the message.

No action is required for this informational message.

The number of CPUs used does not match the number of CPUs allowed by the license.

Resolve the difference in these counts. Entire Net-Work cannot be used until these numbers are resolved. For assistance, contact your Software AG technical support representative.

The core performance class value for this license (the license bucket value) is given in the message.

No action is required for this informational message.

The core performance class value (the license bucket value) for this license is invalid.

Determine why the core performance class of the license failed. For assistance, contact your Software AG technical support representative.

The model number of the CPU is given in the message.

No action is required for this informational message.

The virtualization parameter PPAR is not present for the system. An attempt to apply the license to a virtual machine failed.

Verify that the license should support virtual machines. For assistance, contact your Software AG technical support representative.

The number of CPUs allowed by the license does not match the number of CPUs used.

Resolve the difference in these counts. Entire Net-Work cannot be used until these numbers are resolved. For assistance, contact your Software AG technical support representative.

An internal error occurred. The error code is given in the message.

Analyze the error description to try to identify and resolve the problem. If the problem persists, contact your Software AG technical support representative for assistance.

An Entire Net-Work 7.2 node cannot be reached. The response from the connection attempt is given in the message.

Verify that the node is started. If it is, analyze the installation of the Entire Net-Work 7.2 node to identify and resolve any configuration problem that may exist. If the problem persists, contact your Software AG technical support representative for assistance.

An attempt to add a Kernel to the System Management Hub (SMH) was made, but the Kernel already is added.

No action is required for this informational message.

The definition listed in the message was successfully added to SMH.

No action is required for this informational message.

The Kernel listed in the message was not found in the Adabas Directory Server.

If you cannot identify and resolve the problem, contact your Software AG technical support representative for assistance.

The definition listed in the message was successfully deleted from SMH.

No action is required for this informational message.

No client configuration definitions were found to manage in the System Management Hub (SMH).

Verify that the service for Entire Net-Work Client is started. Client configuration definitions cannot be reviewed in the System Management Hub (SMH) unless the client service is started. For more information, read Starting and Stopping Entire Net-Work Client. If the problem persists, contact your Software AG technical support representative for assistance.

No Entire Net-Work Server definitions were found in the Adabas Directory Server, so no server machines can be listed in the System Management Hub (SMH).

Verify that Entire Net-Work Server has been installed and that its service has been started. For more information on starting Entire Net-Work Server, read Starting and Stopping Entire Net-Work Server.

The version of Entire Net-Work you are trying to use is incompatible with the Entire Net-Work SMH agent.

Contact your Software AG technical support representative for assistance.

The ping request was returned in the number of milliseconds listed in the message.

No action is required for this informational message.

No databases were found on the Kernel listed in the message.

No action is required for this informational message.

An error occurred during an attempt to communicate with a node. The return code is given in the message.

Use the return code to determine what the problem is and resolve it. Then try again. If the problem persists, contact your Software AG technical support representative.

No connection were made. Either the Kernel is down or there is a configuration error.

No action is required for this informational message.

No clients were found on the Kernel listed in the message.

No action is required for this informational message.

No hosts were found connected to the Kernel listed in the message.

No action is required for this informational message.

Shutdown processing has been started.

No action is required for this informational message.

The return code listed in the message was received during Entire Net-Work processing.

Analyze the return code to see if you can diagnose and resolve the problem. If the problem persists, contact your Software AG technical support representative.

An invalid context was encountered.

Verify that all connections and the database in question are up and configured correctly. If the problem persists, contact your Software AG support representative for assistance.

An invalid client was encountered.

Verify that all clients are configured correctly. If the problem persists, contact your Software AG support representative for assistance.

A new log file has been started.

No action is required for this informational message.

A new trace level has been set.

No action is required for this informational message.

A new statistics level has been set.

No action is required for this informational message.

A dump configuration has been initiated.

No action is required for this informational message.

An invalid Adabas database ID has been specified.

Specify a correct database ID.

An invalid host was specified.

Specify a valid host name.

A problem occurred during an attempt to communicate with the Adabas Directory Server.

Verify that the Adabas Directory Server is stated and try again. If the problem persists, contact your Software AG technical support representative.

A connection attempt was started.

No action is required for this informational message.

A disconnection attempt was started.

No action is required for this informational message.

The deletion attempt was successful.

No action is required for this informational message.

An attempt was made connect to an invalid node.

Refresh your SMH screens. The node was probably deleted since you started your SMH session.

An attempt occurred to connect to a Kernel that is already connected.

If you are having problems communicating with the Kernel and you are getting this error, contact your Software AG technical support representative for assistance.

An attempt was made to disconnect a Kernel that is already disconnected.

No action is required.

An unknown return code was received. The return code is given in the message.

Contact your Software AG technical support representative for assistance.

The Software AG Transport Subsystem library could not be loaded.

Contact your Software AG technical support representative for assistance.

An attempt was made to allocate a Kernel that was already allocated.

Try specifying a different Kernel name for the Kernel you are allocating. If the problem persists, contact your Software AG technical support representative.