AAS* - Adabas Administration Services Messages

Adabas Administration Services is processing Adabas 6.3 databases only.

No action is required for this informational message.

Adabas Administration Services is processing Adabas 6.4 databases only.

No action is required for this informational message.

Adabas Administration Services was unable to load the required AIF library. The response code from the attempt is given in the message.

Review the meaning of the response code to identify and resolve the problem. If the problem persists, contact your Software AG technical support representative.

Adabas Administration Services was unable to identify the Adabas database location and load the AIF library.

Contact your Software AG technical support representative for assistance.

Adabas Administration Services located the Adabas database at the path identified in the message.

No action is required for this informational message.

Adabas Administration Services is initializing. The platform on which it is initializing and the date are given in the message.

No action is required for this informational message.

This message displays general information about the installed Adabas Administration Services.

No action is required for this informational message.

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

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 service.

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 service has been running.

No action is required for this informational message.

This message provides the total number of administration messages made to the service.

No action is required for this informational message.

This message provides the total number of communication errors that occurred with the service.

No action is required for this informational message.

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

No action is required for this informational message.

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

No action is required for this informational message.

Adabas Administration Services has initialized successfully.

No action is required for this informational message.

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

No action is required for this informational message.

This message identifies the version of the Adabas database.

No action is required for this informational message.

Adabas Administration Services was unable to locate the Adabas 6.3 registry. The response code from the attempt is given in the message.

Review the response code to determine what the problem is and how to repair it. Contact your Software AG technical support representative if you need assistance.

Adabas Administration Services was unable to determine the Adabas version.

No action is required for this informational message.

The remote service 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 registered on the local service.

No action is required for this informational message.

The Adabas database with the identified database ID is no longer registered with the local service.

No action is required for this informational message.

Adabas Administration Services encountered a mismatch between the expected Adabas version and the actual Adabas version.

No action is required for this informational message.

The identified 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 service.

No action is required for this informational message.

Information from the internal transport subsystem used by Adabas Administration Services is provided in this message.

No action is required for this informational message.

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

No action is required for this informational message.

The name of the Adabas Administration Services is given in the message.

No action is required for this informational message.

This message identifies the name of the service

No action is required for this informational message.

This message provides the number of nodes that the service knows about.

No action is required for this informational message.

This message provides the number of nodes to which the service 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 service.

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 service.

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 service.

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 service.

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 contexts processed by the service.

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 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 service.

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 service.

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 service.

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 service.

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.

The identified 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 service occurred.

No action is required for this informational message.

An outbound connection exists for the service listed in the message.

No action is required for this informational message.

The outbound connection for the service 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 service connections, restarting it if necessary to do so.

A service is listening on the TCP/IP port listed in the message.

No action is required for this informational message.

A service 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 service and can now be accessed.

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 for Adabas Administration Services has been received.

No action is required for this informational message.

The UNIX signal value is given in the message.

No action is required for this informational message.

The message indicates that the service 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 incoming service 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 service is now accessible from the local node.

None. This message is informational only.

An immediate disconnection for the named service 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.

The setting of a user command parameter is given in the message.

No action is required for this informational message.

This message identifies the TCP/IP port number on which the services is listening for clients.

No action is required for this informational message

This message identifies the SSL port number on which the services is listening for clients.

No action is required for this informational message

The Adabas Administration Services is terminating.

No action is required for this informational message.

No outbound connections have been defined for this configuration.

No action is required for this warning message.

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.

Remote access to Entire Net-Work open system services has been disabled.

No action is required for this warning message.

Remote access for Entire Net-Work Client services has been disabled.

No action is required for this warning message.

Remote access for Event Replicator Target Adapter services has been disabled.

No action is required for this warning message.

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 trace level has been reset by a System Management Hub (SMH) user. The new trace level is given 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 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 a service. It was not possible to create the definitions for a database to allow it to be accessed by clients.

Restart the service.

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 a database (message AAS0029I), the service 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 registered at the local node nor is it broadcast to other nodes. This error normally results from a failure to provide an XTSaccess URL for the 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 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.

A duplicate URL has been found for a target definition in the Directory Server. The URL and the target ID are given in the message.

No action is required for this warning message.

A syntax error was discovered in the URL for a target definition in the Directory Server. The URL and the target ID are given in the message.

No action is required for this warning message.

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.

A service definition has not been defined in this Adabas Administration Services implementation.

No action is required for this informational message.

A client access definition has not been defined in this Adabas Administration Services implementation.

No action is required for this informational message.

The listening port is given in the message.

No action is required for this informational message.

The listening port is 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 on the host machine and port number listed in the message is a privileged client.

No action is required for this informational message.

A service-to-service connection has occurred.

If a service 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.

A service-to-service connection has occurred and databases known to the remote service are now known to both.

No action is required for this informational message.

A database was rejected for traffic relay, as defined by the service filter settings. The service 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, the service has verified that its connection to the database listed in the message is valid and active.

No action is required for this informational message.

A e-business database was rejected by a filter, as defined by the service filter settings. The service will not process requests for the database with the database ID given in the message.

No action is required for this informational message.

The database listed in the message has been started.

No action is required for this informational message.

The database listed in the message has been stopped.

No action is required for this informational message.

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

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

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

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

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

No action is necessary unless you want a connection by the node to be accepted. If you do, adjust the parameters on the Service 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 Service Filters panel in SMH.

An e-business database has connected to the service 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 node with an unknown node name attempted to connect to the service while the SECURE parameter was set to ON.

Define the node to Adabas Administration Services.

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 Service Filters panel in SMH.

An error occurred in the Event Replicator Target Adapter callback routine. The response code is given in the message.

Contact your Software AG technical support representative.

An error occurred in the Adabas Administration Services callback routine. The response code is given in the message.

Contact your Software AG technical support representative.

An error occurred in the Entire Net-Work LUW callback routine. The response code is given in the message.

Contact your Software AG technical support representative.

An error occurred in the Adabas Administration Services callback routine. The response code is given in the message.

Contact your Software AG technical support representative.

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 service.

Check the database configuration files.

A local database has started with an ID that is already in use by another database known to this service. The duplicate will be ignored.

This indicated a configuration error that needs to be corrected.

An internal error occurred registeringAdabas Administration Services. The response code is given in the message.

Contact your Software AG technical support representative for assistance.

An internal failure occurred during an Adabas call to a 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 database. If the problem persists, contact your Software AG support representative.

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

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

An internal failure occurred during an Adabas ACBX call to a database because the OP command was not secure. The database referenced in the Adabas call, the extended Adabas control block (ACBX) return code, and the ACBX error code are given in the message.

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

An internal failure occurred during an Adabas ACBX call to a database because the OP command was not valid. The database referenced in the Adabas call, the extended Adabas control block (ACBX) return code, and the ACBX error code are given in the message.

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

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 server (identified in the message) was encountered.

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

The UNIX system is overloaded and will not allow the creation of new processes.

Contact your Software AG technical support representative.

A syntax error occurred during Adabas Administration Services 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 Adabas Administration Services error occurred. The client ID, database ID and the return code from the attempt are given in the message.

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

An Adabas Administration Services error occurred. The client ID, database ID and the return code from the attempt are given in the message.

Make sure the Adabas Administration Services 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 Adabas Administration Services 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.

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 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.

The Adabas Administration Services was unable to add a Directory Server entry.

Contact your Software AG technical support representative for assistance.

An AIF exit error occurred.

Contact your Software AG technical support representative for assistance.

The Adabas Administration Services threading mechanism failed.

Repeated occurrences of this message may require a restart of the service.

The Adabas Administration Services threading mechanism failed.

Repeated occurrences of this message may require a restart of the service.

An internal Adabas Administration Services error occurred.

Contact your Software AG technical support representative for assistance.

An internal Adabas Administration Services error occurred.

Contact your Software AG technical support representative for assistance.

An internal Adabas Administration Services error occurred.

Contact your Software AG technical support representative for assistance.

The Adabas Administration Services semaphoring mechanism failed. The return code from the call is given in the message.

Contact your Software AG technical support representative for assistance.

The Adabas Administration Services 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 service.

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.

An internal error occurred.

Contact your Software AG technical support representative for assistance.

A severe error occurred when the Adabas Administration Services tried to start up. The cause is shown in a previous message.

Contact your Software AG technical support representative for assistance.

The threading mechanism failed. The return code is given in the message.

Repeated occurrences of this message may require a restart of the service.

The threading mechanism failed. The return code is given in the message.

Repeated occurrences of this message may require a restart of the service.

The threading mechanism failed. The return code is given in the message.

Repeated occurrences of this message may require a restart of the service.

Adabas Administration Services could not access the remote Software AG Directory Server.

Contact your Software AG technical support representative for assistance.

A Directory Server problem occurred.

Make sure no Directory Server or Adabas Administration Services 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.

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.

A 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 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 service to the System Management Hub (SMH) was made, but the service 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 service 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 client service is started. Client configuration definitions cannot be reviewed in the System Management Hub (SMH) unless the client service is started. If the problem persists, contact your Software AG technical support representative for assistance.

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

Verify that Adabas Administration Services has been installed and that its service has been started.

The version of Adabas Administration Services you are trying to use is incompatible with the Adabas Administration Services 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 service 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 service is down or there is a configuration error.

No action is required for this informational message.

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

No action is required for this informational message.

No hosts were found connected to the service 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.

A configuration was referenced that does not exist.

No action is required for this informational message.

The return code listed in the message was received during Adabas Administration Services 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 service that is already connected.

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

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

No action is required for this information message.

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 configure a service that is already configured.

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

An invalid request was attempted.

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

An attempt to create a file was unsuccessful.

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

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

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

The service definition configuration attempt was successful. The service definition name is given in the message.

No action is required for this informational message.

The client configuration attempt was successful. The client configuration name is given in the message.

No action is required for this informational message.

An attempt to migrate a service definition from an older version of Adabas Administration Services to a newer version was successful. The name of the service is given in the message.

No action is required for this informational message.

The service listed in the message has been migrated from a previous version.

No action is required for this informational message.

An invalid entry was specified.

Contact your Software AG technical support representative for assistance.

The modification was successful.

No action is required for this informational message.

Invalid data was specified.

Correct the data and try again. If the problem persists, contact your Software AG technical support representative.

The attempt to delete the client configuration was successful.

No action is required for this informational message.

The attempt to delete the service definition was successful.

No action is required for this informational message.

An attempt to delete a service definition was made, but the service is running.

Stop the service before attempting to delete it.

An attempt to start a service was made, but the service is already running.

No action is required for this informational message.

The service is starting.

No action is required for this informational message.

The Keservicernel cannot be started for some reason.

Examine the service log file for reasons for the failure, make appropriate corrections, and try again. If the error persists, contact your Software AG technical support representative for assistance.

The parameter changes were successfully processed.

No action is required for this informational message.

No service definitions have been defined, so none are available.

Define some service definitions.

The client listed in the message has been migrated from a previous version of Entire Net-Work.

No action is required for this informational message.

The name of a service definition cannot exceed eight characters. An attempt was made to specify a name longer than eight characters and the name specified is given in the message.

Reduce the length of the name of the service definition.

An internal error occurred.

Contact your Software AG technical support representative for assistance.

The port number was not specified or is invalid.

Specify a valid port number.

A host name was not specified or is invalid.

Specify a valid host name.

Data received by the SMH agents is not recognized.

Contact your Software AG technical support representative for assistance.

An internal error occurred in a Directory Server definition.

Contact your Software AG technical support representative for assistance.

The name of a service must be unique across the network. A name that has already been used was specified.

Change the service name so it is unique.

You cannot delete the default client configuration that is distributed with Adabas Administration Services.

No action is required.

The list of databases was not specified correctly. The syntax for a list of databases is given in the message.

Correct the list of databases.

The trace information was not specified correctly. The correct syntax for trace information is given in the message.

Correct the trace information.

An invalid value for the UNSOLICITED parameter was specified. Valid values are "YES" or "NO".

Specify a valid value for the parameter.

An invalid value was specified for the ADABAS_TIMEOUT parameter. The value cannot be less than 5 seconds.

Specify a valid value for the parameter.

The command was sent to the service listed in the message.

No action is required for this informational message.

An invalid value was specified for the TIMER_TIMEOUT parameter. The value must be between 1 and 3600 seconds.

Specify a valid value for the parameter.

An invalid value was specified for the STATISTICS_INTERVAL parameter. The value must be between 1 and 1440 minutes.

Specify a valid value for the parameter.

An invalid value was specified for the LOGSIZE parameter. The value must be between 1 and 500 megabytes.

Specify a valid value for the parameter.

An invalid value was specified for the PING_DB_INTERVAL parameter. The value must be between 1 and 1440 minutes.

Specify a valid value for the parameter.

An invalid value was specified for the CHECK_DBS_INTERVAL parameter. The value must be between 5 and 600 seconds.

Specify a valid value for the parameter.

An invalid port number was specified.

Specify a valid port number.

An invalid value was specified for the service ID. The value must be between 1 and 65535.

Specify a valid service ID.

An invalid client configuration name was specified. The client configuration name cannot exceed 16 characters.

Specify a valid client configuration name.

An invalid value was specified for the RELAY_VALUES parameter. Valid values are "YES" or "NO".

Specify a valid value for the parameter.

An invalid port number was specified. Valid values must lie between "1" and "65535".

Correct the port number and try again.

An invalid port number was specified.

Specify a valid port number.

A non-numeric value was specified for a parameter when a numeric value is expected. The parameter name is given in the message.

Specify a valid value for the parameter.

An invalid value was specified for the AUTOSTART or AUTOSTOP parameters. Valid values are "YES" or "NO".

Specify a valid value for the parameter.

No entry definitions were found to manage in the Adabas Directory Server and, consequently, in the System Management Hub (SMH).

Verify that the service for Adabas Administration Services is started. Service definitions cannot be reviewed in the System Management Hub (SMH) unless the server service is started.

No Entire Net-Work 7.2 node definitions were found to manage in the Adabas Directory Server and, consequently, in the System Management Hub (SMH).

If you have any Entire Net-Work 7.2 nodes to be managed, you must first add them in SMH.

No Entire Net-Work 7.2 node definitions were found to manage in the Adabas Directory Server and, consequently, in the System Management Hub (SMH).

If you have any Entire Net-Work 7.2 nodes to be managed, you must first add them in SMH.

An invalid Adabas database ID was specified. Valid database IDs are between 1 and 65535.

Specify a valid database ID.

The name of a service definition was specified with one of the special characters listed in the message.

Specify a valid service definition name.

The name of a Kernel definition was specified with one of the special characters listed in the message. These characters cannot be used in a Kernel definition name.

Specify a valid Kernel definition name.

The name of a client configuration was specified with one of the special characters listed in the message. These characters cannot be used in a client configuration name.

Specify a valid client configuration name.

The Entire Net-Work 7.2 node cannot be found and does not appear to be installed on the local machine.

Correct the Entire Net-Work 7.2 node definition in SMH to point to the correct host machine.

An attempt to add a definition that has already been added. The definition you tried to add is not added.

No action is required for this informational message.

An attempt to delete a service failed; it is possible that it was already deleted.

No action is required for this informational message.

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

Verify that the service for Adabas Administration Services is started. Kernel definitions cannot be reviewed in the System Management Hub (SMH) unless the server service is started. If the problem persists, contact your Software AG technical support representative for assistance.

No Adabas Administration Services entries were found to manage in the System Management Hub (SMH).

Verify that the service for Adabas Administration Services is started. Service definitions cannot be reviewed in the System Management Hub (SMH) unless the Adabas Administration Services service is started. For more information, read Starting and Stopping Adabas Administration Services in your Adabas Administration Services documentation. If the problem persists, contact your Software AG technical support representative for assistance.

The service name cannot contain only numeric values.

Specify a valid service name.

The client name cannot contain only numeric values.

Specify a valid client name.

An attempt to reference an entry in the Directory Server failed.

Refresh your SMH display to obtain the latest Directory Server entries.

An invalid port number was specified.

Specify a valid port number. For more information, read Port Number Reference, elsewhere in this documentation.

The retry count specification was not numeric.

Specify a numeric retry count.

The retry interval specification was not numeric.

Specify a numeric retry interval.

The host name was specified with one of the special characters listed in the message. These characters cannot be used in a host name.

Specify a valid host name.

No additional parameters were supplied for the Adabas Administration Services configuration.

No action is required for this informational message.

An invalid port number was specified.

Specify a valid port number. For more information, read Port Number Reference, elsewhere in this documentation.

When specifying a range of port numbers, the second port number should be larger than the first port number in the range. The port numbers specified are given in the message.

Specify a valid range of port numbers.

The Adabas database ID specified was not numeric.

Specify a numeric database ID.

When specifying a range of Adabas database IDs, the second database ID should be larger than the first database ID in the range. The database IDs specified are given in the message.

Specify a valid range of database IDs.

A blank string was specified for a parameter.

Specify a valid value for the parameter.

An attempt to add an access definition was made but no access type was selected (for example, Classic, e-business Client, e-business SSL Client, etc.).

Select an access type when adding an access definition.

No active access entries were found for the active service.

No action is required for this informational message.

No active connection entries were found for the active service.

No action is required for this informational message.

An invalid value was specified for the REMEMBER_DBID parameter. Valid values are "YES" or "NO".

Specify a valid value for the parameter.

An invalid value was specified for the MAX_CLIENTS parameter. Valid values must be between 5 and 65535.

Specify a valid value for the parameter.

A system timeout error occurred.

Verify that the service is not down. If it is, restart it. If the problem persists, contact your Software AG technical support representative.

An Adabas database ID was not specified or an invalid one was specified.

Specify a valid database ID.

The Adabas database is not active.

Start the database.

An attempt was made to ping a service, but the service does not exist.

Refresh your System Management Hub displays. The node may have been deleted since you started this SMH session.

An attempt was made to ping a service, but the service was not active.

Start the node if you wish.

An attempt was made to review an entry that is no longer available.

Refresh your System Management Hub displays. The entry may have been deleted since you started this SMH session.

No service definition name was specified.

Specify a valid service definition name.

No client configuration name was specified.

Specify a valid client configuration name.

No host name was specified.

Specify a valid host name.

No Adabas database ID was specified.

Specify at least one database ID.

No port number was specified.

Specify a valid port number. For more information, read Port Number Reference, elsewhere in this documentation.

No client configuration definitions were found in the Adabas Directory Server.

Verify that the service for Adabas Administration Services is started. Client configuration definitions cannot be reviewed in the System Management Hub (SMH) unless the service is started. If the problem persists, contact your Software AG technical support representative for assistance.

A syntax error exists in a connection URL. Entire Net-Work cannot make the connection.

Contact your Software AG technical support representative for assistance.

An attempt was made to define a connection to the same node twice. Only one connection definition is needed.

Make sure that there is only one connection definition for the node.

The host identified in the message is not defined in the DNS.

Contact your Software AG technical support representative for assistance.

The host identified in the message is not defined in the DNS.

Contact your Software AG technical support representative for assistance.

A connection attempt was made to a target that is not correctly defined to Adabas Administration Services.

Verify that the target definition is correct and complete (no required parameters are undefined) and try again. If the error persists, contact you Software AG technical support representative for assistance.

An attempt was made to define two connections for the same incoming service. Only one connection definition is needed.

Make sure that only one connection definition exists for the incoming service. If the problem persists, contact your Software AG technical support representative for assistance.

An attempt to make a defined connection failed. The reason code is given in the message.

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

The value of the SERVICE_THREADS parameter is not correct. It must be a numeric value between 5 and 1024.

Correct the value and try again.

The service log file cannot be found.

Contact your Software AG technical support representative.

An invalid value was specified for the MULTIPLEX parameter. Valid values are "YES" or "NO".

Correct the value and try again.

An invalid value was specified for the NOLOCAL parameter. Valid values are "YES" or "NO".

Correct the value and try again.

An invalid value was specified for the NOREMOTE parameter. Valid values are "YES" or "NO".

Correct the value and try again.

An invalid value was specified for the LOAD_BALANCING parameter. Valid values are "YES" or "NO".

Correct the value and try again.

An invalid value has been specified for the MAX_CPU_THRESHOLD parameter.

Correct the value and try again.

An invalid value was specified for the STATISTICS_DETAILS parameter. Valid values are "YES" or "NO".

Correct the value and try again.

An invalid value was specified for the USE_LOCAL_ADABASES parameter. Valid values are "YES" or "NO".

Correct the value and try again.

The service listed in the message is not defined to process local databases.

Correct the USE_LOCAL_ADABASES parameter value in the service definition and try again.

An invalid value was specified for the DATE_STAMP parameter. Valid values are "YES" or "NO".

Correct the value and try again.

An invalid value was specified for the CHECK_CXT_INTERVAL parameter. Valid values are zero (0) seconds or lie between 60 seconds and 43,200 seconds (24 * 60 * 30).

Correct the value and try again.

The service 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.

The database listed in the message could not be accessed.

No action is required for this informational message.