Server Messages

If the message you are looking for does not appear in this section, look for it elsewhere in this topic, particularly in the section Messages from Client and Server. Messages from the communication layer (RCI) that pertain both to client and server are documented in that section.

DBA000 ERROR: <error_text>

Explanation:

This error occurs under z/OS if a requested VSAM dataset could not be found, the dynamic file assignment failed, or the VSAM parameters are inconsistent from the Rochade point of view. <error_text> contains details on the specific error that has occurred.

Action:

Check if the files specified within your job are physically available and whether the specifications in the initialization file and the jobstream are consistent.

DBA001 VSAM ERROR: <error_text>

Explanation:

This error occurs under z/OS if accessing a database results in a VSAM error. <error_text> contains details on the specific error that has occurred. Depending on the reason for the error, additional messages with the code DBA002 VSAM NOTE may follow, containing more error information.

Action:

Check the consistency of the databases and whether there is sufficient free disk space. If the database is corrupted, you will need to bring it back to a consistent state by means of the service utility RODBUCX<os> or restore a previous backup.

DBA002 VASM NOTE: <error_text>

Explanation:

This error message occurs in connection with the message DBA001 and details the reason for the error signaled there.

Action:

None required.

DBA003 VASM ERROR: Database <name> <spec> already initialized

Explanation:

This error occurs under z/OS if you try to create an already existing database with $OPER CREATEDB.

Action:

Check the existing databases and specify a new name for the new database you wish to create.

DBA004 VASM ERROR: Database <name> <spec> initialized

Explanation:

This message occurs under z/OS when a database has been created successfully with $OPER CREATEDB. In this context, <name> is the ddname of the database, and <spec> is the name that is specified for the database in DFILE.

Action:

None required.

E0010 Not enough memory available

Explanation:

Not enough memory is available to start the server.

Action:

Check your system resources and restart the server.

E0202 Serious error while initializing server.

Explanation:

An error occurred during initialization of the server. This message always appears in connection with other messages that give additional information about possible causes.

Action:

Remove the errors that occurred and restart the server.

E0212 Check sum error detected in program code.

Explanation:

This message appears if the server program code was altered.

Action:

Use a licensed official server version and restart the server.

E0260 Database <file> locked ( Error: <error> ).

Explanation:

An error occurred when the database was accessed. The database is locked by the server against further access attempts. If <error> has the value fatal, an error has occurred in the access method. The value overflow means that the storage capacity on the data carrier is no longer sufficient.

Action:

If <error> has the value fatal, you must shut down the server and restore database consistency using the program RODBUCX<os>.

If <error> has the value overflow, you must shut down the server and ensure that there is sufficient storage capacity on the data carrier. If necessary, you must move the database to a different data carrier and restart the server.

E0302 Database <database>: Incorrect Rochade version

Explanation:

This message indicates that there is a conflict between the versions of the database and the Rochade component (server or service program such as RODBUCX<os>) being used. The nature of the conflict depends on the major and minor version numbers involved (for example, for a version 5.3, the major version number would be 5, the minor version number 3).

The message is usually followed by one or more additional messages with further information and suggestions how to react.

If the major version number of the database differs from that of the Rochade component, this message appears:

If the minor version number of the database is greater than that of the Rochade component (within same major version number), this message appears:

E0306 Database <database> : WORDSIZE incorrect

Explanation:

The server cannot work with this database because the values for WORDSIZE are different between database and server.

Action:

Use a server that uses the same value for WORDSIZE as the database does.

E0310 Database <file> : Index <index> in number <number> wrong.

Explanation:

An internal error occurred when the database was accessed.

Action:

Check the consistency of your database and restart the server.

E0312 Database <file> : No more item numbers available.E0313 Database <file> : No more container numbers available.

Explanation:

The capacity of the Rochade database is exhausted. No further item numbers and container numbers are available.

Action:

Contact ASG Customer Support.

E0315 Database <database> : Error while writing <NUMFILE/DOCFILE> headerE0316 Database <database> : Error while reading <NUMFILE/DOCFILE> header

Explanation:

The internal index header could not be written or read, respectively, due to an error in the database. For example, the database may be physically inconsistent or corrupted in some other way.

Action:

Usually this message appears as the last of a sequence of messages that describe the type of error involved in more detail down to the data access method and operating system level. The solution will depend on these messages.

E0409 LOG file <file> : Write error.

Explanation:

Either there is a hardware error, or the capacity of the data medium to which the LOG file is written is exhausted. The server terminates itself when this error occurs.

Action:

Check your system resources and the consistency of your data medium.

E0418 LOG file <file> cannot be opened.

Explanation:

An attempt to write to a LOG file is failing because the specified LOG file cannot be opened.

Action:

Check the LOG setting in the server initialization file. Ensure that the LOG file can be accessed via the access path of your operating system.

E0420 Database cannot be opened.

Explanation:

The database cannot be found or is already being used by another program.

Action:

Check the DFILE setting in the server initialization file. Make sure that the database is accessible in the network via the path specified in DFILE. Furthermore, check if the database is being used by some other program.

E0453 Could not open record containing reconstruction information

Explanation:

For reconstruction, some server scenarios require additional information that is stored in a reconstruction record in the database header. When the message E0453 appears, that header cannot be read.

Action:

Verify the database by running the service program RODBUCX<os> with the -v option.

E0500 Communication error while processing <process>: rc = <error>

Explanation:

An error occurred in the communication.

Action:

Check if your network is running properly.

E0501 Communication : Section <section> not found in ini file <file>

Explanation:

The <section> that describes the communication could not be found in the specified initialization file.

Action:

Check and correct the settings in your initialization file, and restart the server.

E0515 SetConsoleCtrlHandler failed.

Explanation:

This message only appears under Windows. It appears if the function SetConsoleCtrlHandler could not be executed because of system errors or insufficient resources.

Action:

Check your system resources and restart your operating system.

E0540 Code table file <file>: Open failed.

Explanation:

The specified file, which should be loaded as an external code table, could not be opened.

Action:

Check the specifications in the CODEPAGE setting in the initialization file. Check, too, whether the file specified is accessible via the access path. Further, check your access rights for this file, and check whether the file specified is a binary file.

E0541 Code table file <file>: Unexpected end of file.

Explanation:

The code page is incomplete, but the end of the file has been reached.

Action:

Check the size of the file and reinstall the external code page if necessary.

E0542 Code table file <file>: Invalid version or magic number.

Explanation:

The file specified contains a false ID. As a result, the file is not recognized as an external code page.

Action:

Check the specifications in the CODEPAGE setting in the initialization file. Check the specified code page and reinstall the external code page if necessary.

E0543 Code table file <file>: Out of memory while loading file.

Explanation:

The operating system could not supply enough memory to load the code page, or the code page may be damaged.

Action:

Check your system resources and the specified code page. If necessary, reinstall the external code page.

E0544 Code table file <file>: Internal error.

Explanation:

The order in which characters appear in the code page is incorrect.

Action:

Contact ASG Customer Support and send the file for analysis.

E0545 Checksum error in code table <file>

Explanation:

The internal checksum of the code page is incorrect.

Action:

Contact ASG Customer Support and send the file for analysis.

E0546 Code table <file>: Error while initializing internal code table.

Explanation:

An error occurred while the code page was being initialized.

Action:

Contact ASG Customer Support.

E0547 Code table <file>: No such internal server code table name.

Explanation:

There is no internal code page by this name.

Action:

Check the name of the code page and the CODEPAGE setting in the initialization file. Load an analogous external code page, carefully following the correct syntax for specifying external code pages.

E0548 Code table file <file>: Internal error while reading code table file.

Explanation:

An internal error has occurred.

Action:

Contact ASG Customer Support.

E0602 Setting <setting>: Illegal value, default value assumed.

Explanation:

The value assigned to setting <setting>, which can take the value USER, SESSIONS, or EVENTLOG, is invalid. The default setting will be used.

Action:

Check the value assigned to <setting> in the initialization file.

E0606 Setting <setting>: Illegal value.

Explanation:

The value assigned to one of the settings ADB, COMPANY, LICENSE, LOG_..., or ONLINE_BACKUP... , specified in <setting>, is invalid.

Action:

Check the value in the initialization file and correct it.

E0607 Setting ADB : Database <dbname> is not an active database.

Explanation:

The database specified as the administration database is not assigned to the server data space.

Action:

Check the value assigned to the ADB setting in the initialization file and correct it.

E0608 Setting ADB : Database <name> is not in update mode.

Explanation:

The administration database is write-protected.

Action:

Check the MODE setting in the section <db_section>, where the administration database is described. For an administration database, MODE must be set to the value U.

E0611 Setting <setting>: Section <section> not found.

Explanation:

The section for describing the database, which is specified in the setting <setting>, has not been found.

Action:

Check if the section name was specified correctly in the initialization file. Make sure that the specified section does exist in the initialization file.

E0615 Setting <setting> not found in section <section>.

Explanation:

One of the settings NAME or DFILE has not been found in the initialization file section that describes the database.

Action:

Add the missing setting in the initialization file.

E0616 Setting <setting> in section <section> has an illegal value.

Explanation:

The value assigned to one of the settings describing the database is incorrect.

Action:

Check the value assigned to the setting <setting> in the specified initialization file section <section> and correct it if necessary.

E0619 Start section <section> not found in ini file <file> or section is empty.

Explanation:

The section <section> for the server start contains no valid settings or is empty.

Action:

Check the settings in this section. For more information, see Configuring Rochade .

E0630 Error while processing section <section> in ini file <file>E0631 Setting <setting> not found.

Explanation:

The specified setting is missing in the initialization file.

Action:

Insert the missing setting in the initialization file.

E0632 Setting LICENSE or COMPANY invalid.

Explanation:

The value assigned to one of the settings COMPANY or LICENSE is invalid.

Action:

Check the initialization file for the values assigned to the settings specified and correct the values if necessary.

E0633 Setting LICENSE has expired.

Explanation:

The license has expired. You can work with this Rochade test version for a limited period of time only.

Action:

Contact ASG Customer Support.

E0634 Setting LICENSE: The operating system in the license is invalid for this server.

Explanation:

The license number specified does not apply to the operating system on which the server was started.

Action:

Check your license number. Contact ASG Customer Support.

E0646 More than 128 Rochade databases specified

Explanation:

The Rochade Server can work with a maximum of 128 Rochade databases simultaneously. You have attempted to activate more than 128 databases.

Action:

Reduce the number of databases specified before you attempt to activate a new database.

E0648 Error while opening ROCHADE databases.

Explanation:

An error occurred while the databases were being opened.

Action:

Check the database settings in your initialization file and the consistency of your databases.

E0649 Error while opening server event log file <file>.

Explanation:

An error occurred while the file containing the server event log was being opened.

Action:

Check the EVENTLOG setting in your initialization file; in particular, check whether the path specified there is correct.

Check if the server is running and if another application already accesses this file.

E0687 Databases require recovery but the logfile <file> does not contain appropriate data. The server is therefore not started

Explanation:

The server recognized during startup that a database recovery is required, but the LOG file specified in <file> is not the same as the one that was specified when the server crash occurred or the server was shut down.

Action:

Check the setting LOG_NAME and make sure that the server is started in exactly the same environment as it was when it crashed.

E0702 Cannot increase number of file handles to <obj>. (<number> handles available)

Explanation:

The server needs more file handles than the system can provide.

Action:

Check system resources and ensure an adequate number of file handles.

E0704 Non-unique file ID detected.DB file <file> has the same file ID asDB file <file>Automatic file ID correction is not possible. One or more DB files require automatic transaction recovery.

Explanation:

For the transaction mechanism to work properly, the database files must have unique file IDs. Database files with identical file IDs may arise as a result of copying (duplicating) an existing database. The server cannot correct this. It assumes that the last server run was not terminated properly.

Action:

Start the server in the same environment. The action can be repeated after automatic transaction recovery has been executed and the server has been shut down properly.

E0716 Error while processing database <file>.

Explanation:

An error occurred while the database was being accessed.

Action:

Check the consistency of your database.

E0803 Error while repairing NUMFILE

Explanation:

This message indicates that the NUMFILE index is irreparably corrupted.

Action:

Contact ASG Customer Support.

E0918 Unable to delete service type <name> from start section

Explanation:

An error occurred while the server initialization file was updated via the $OPER UNMOUNTSERVICE command.

Action:

Make sure that the initialization file is not write-protected. Check if there is enough available disk space for modifying the initialization file.

E0919 MOUNTSERVICE: unable to enter new service type <name> into start section

Explanation:

An error occurred while the server initialization file was updated via the $OPER MOUNTSERVICE command.

Action:

Make sure that the initialization file is not write-protected. Check if there is enough available disk space for modifying the initialization file.

E0920 SERVICE<n>: section <rpc_service> not found.

Explanation:

The <rpc_service> section was not found in the server initialization file.

Action:

Check whether the specified section exists in your initialization file. Check the spelling for the specified section in the SERVICE<n> setting and correct any incorrect values or supply the missing section.

E0921 SERVICE<n>: Setting <setting> not found in section <rpc_service>.

Explanation:

The <setting> setting has not been found in the <rpc_service> section of the initialization file.

Action:

Specify the <setting> setting in the <rpc_service> section of the initialization file.

E0922 SERVICE<n>: error in setting <setting> of section <rpc_service>.

Explanation:

The value specified in <setting> is not numeric or is a negative number.

Action:

Specify a positive numeric value in <setting>.

E0923 Maximum number of service types exceeded.

Explanation:

The maximum number of 32 RPC services that you can assign to the server via the SERVICE<n> setting has been reached. This error also occurs if 32 RPC services are already assigned to the server, one of them is removed using the $OPER UNMOUNTSERVICE command and one service instance of this RPC service is still active at the time when another RPC service is to be assigned to the server.

Action:

Reduce the number of assigned RPC services either temporarily using the $OPER UNMOUNTSERVICE command or permanently by removing SERVICE<n> settings that you do not need from the initialization file.

Using the $OPER RPCSTATUS command, check whether there are still active service instances whose RPC services are no longer assigned to the server. If necessary, you can terminate these service instances using the $OPER RPCCANCEL command.

E0924 SERVICE<n>: service name <name> used twice.

Explanation:

The logical name of the RPC service is already assigned to another RPC service.

Action:

Check the logical names of all RPC service sections assigned to the server. The logical name of an RPC service must be unique.

E0925 Unable to initialize service control layer.

Explanation:

Not enough memory is available to initialize the RPC service.

Action:

Check the system resources on the server machine.

E0930 Could not spawn task <service>.

Explanation:

The service monitor cannot carry out the required service.

Action:

Check whether the PROGRAM setting in the initialization file refers to an API program that is programmed according to the conventions for RPC services.

E0933 Service did not respond to term signal.

Explanation:

The RPC service did not react to the termination signal that was sent because the service monitor had not received a status message.

Action:

Check whether the workload of the server machine is excessively high.

Check whether the value for the TIMEOUT setting in the service section is sufficiently high.

E0934 Instance <id> of type <name> did not deliver state information.

Explanation:

The service instance does not return any status information. As a result, the RPC service is terminated.

Action:

Check whether service monitoring of time-intensive processes has been switched off in the RPC service.

E0935 Instance <id> of type <name> did not logon.E0936 Instance <id> of type <name> did not come to ready state.

Explanation:

The service instance could not complete the connection to the server. The maximum time allowed to establish a connection has been exceeded.

Action:

Check whether the implementation of your RPC service satisfies the conventions for RPC services. Check your network. Consult ASG Customer Support if you cannot fix the error.

W0514 Too few file handles available.

Explanation:

The number of file handles available for this server does not suffice.

Action:

Check your system configuration and make more file handles available.

W0645 License expires this month.

Explanation:

You can work with this Rochade test version for a limited period of time only. The license expires this month.

Action:

Contact ASG Customer Support.

W0862 Cannot accept client <client>

Explanation:

A client cannot log on to the Rochade Server. This can have one of these reasons:

•

The maximum number of sessions is exhausted.

•

The server is not running.

Action:

If the server is running, try logging on again later, when fewer than the maximum number of clients are logged on.

W0931 Maximum number of instances <number> for service <name> reached.

Explanation:

The maximum number of service instances that an RPC service can have has been reached.

Action:

If the RPC service permits, you can increase the value of the MAX_INSTANCES setting. If the maximum value of 250 service instances per RPC service has been reached, you must free some service instances using the $RPC UNBIND command.

W0932 Session <log_handle> terminated during RPC execution.

Explanation:

A client that has sent a request for a service in synchronous mode has been terminated before the service instance returned the results to this client.

Action:

None required.

W0940 Request <no> running on instance <id> of type <name> canceled by user

Explanation:

The service instance was terminated by the user although a request was still active within this instance.

Action:

None required.