Message Class 1005 - RPC Server

An invalid configuration file name or a wrong file type was used to start the RPC server.

Restart the server with correct configuration file.

Configuration problem.

Contact Software AG support

RPC server was started with an incomplete configuration file: Parameter endworkers has been set to timeout.

Restart server with desired definition.

RPC server was started with an inconsistent configuration file: Parameter minworkers was either less than 1 or greater than the available thread entries.

Restart server with desired definition.

RPC server was started with an inconsistent configuration file: Parameter maxworkers was either greater than the available thread entries or (if endworkers=never was not specified) was less than 2.

Restart server with desired definition.

RPC server was started with an inconsistent configuration file: Parameter minworkers was greater than maxworkers.

Restart server with desired definition.

Initialization of ERX runtime failed. This message is accompanied by an ERX runtime error message.

Check ERX runtime error message for further action.

A new thread could not be established. This message is accompanied by message 10050009.

See message 10050009 for further action.

The predefined thread table is full. This table normally is 256 entries long, under CICS there are 38 entries located in the ERX main control block. With ENDW=USER, each user thread requires an additional entry.

Check reason of the overflow: if a thread abnormally terminates (abends), the thread entry might be marked as UNUSABLE. If there are too many abnormal terminations during the lifetime of the RPC server, the table might be shortened. In other cases, contact Software AG support.

Internal function failed. This message follows a genuine error message.

Check original ERX error message for further action.

Internal function failed. This message follows a genuine error message.

Check original ERX error message for further action.

Internal function failed. This message follows a genuine error message.

Check original ERX error message for further action.

Register call to ERX runtime failed. This message is accompanied by a genuine error message.

Check original ERX error message for further action.

Logon call to ERX runtime (logon to Broker) failed. This message is accompanied by a genuine error message.

Check original ERX error message for further action.

Logoff call to ERX runtime (logoff from Broker) failed. This message is accompanied by a genuine error message.

Check original ERX error message for further action.

Unregister call to ERX runtime failed. This message is accompanied by a genuine error message.

Check original ERX error message for further action.

Informational. This message is the header of the statistic messages 10050018 - 10050023 which will be printed when RPC server terminates.

None.

Informational. Prints the number of conversational and non-conversational calls.

None.

Informational. Prints the number of worker threads with normal end.

None.

Informational. Prints the number of worker threads with abnormal end.

None.

Informational. Prints the maximum number of concurrently active worker threads.

None.

Informational. Prints the number of failing worker threads.

None.

EndServing call to ERX runtime ( Broker DEREGISTER) failed. This message is accompanied by a genuine error message.

Check original error message for further action.

Internal function failed. This message is accompanied by a genuine error message.

Check original error message for further action.

Internal function failed. This message is accompanied by a genuine error message.

Check original error message for further action.

Internal function failed. This message is accompanied by a genuine error message.

Check original error message for further action.

Internal function failed. This message is accompanied by a genuine error message.

Check original error message for further action.

Internal function failed. This message is accompanied by a genuine error message.

Check original error message for further action.

Internal function to prepare the data conversation failed. This message is accompanied by a genuine error message.

Check original error message for further action.

Internal function for data conversation failed, <library>=requested Library, <program>=requested Program. This message is accompanied by a genuine error message.

Verify that the data received from client is correct. It may be necessary to reproduce the error while tracing is on.

Internal function for data conversation failed, <library>=requested Library, <program>=requested Program. This message is accompanied by a genuine error message.

Verify that the data sent by a server subroutine is correct. It may be necessary to reproduce the error while tracing is on.

A client request could not be answered successfully. The client is notified with the appropriate protocol error, depending on the genuine error. This message is accompanied by a genuine error message.

Check original messages for possible errors.

SignalHandler indicates critical error. Depending on the operating system, dump information will be provided. Message 10050060 provides information about the program that is involved in this abend.

Check message 10050060 for more information.

BeginServing call to ERX runtime (Broker REGISTER) failed. This message is accompanied by a genuine error message.

Check original error message for further action.

Informational. This message is the header of the information messages 10050037 - 10050042 and 10050051 - 10050052 which are printed when RPC server is started.

None.

Informational. Prints minworkers startup parameters.

None.

Informational. Prints maxworkers startup parameters.

None.

Informational. Prints endworkers startup parameters.

None.

Informational. Prints timeout startup parameters.

None.

Informational. Prints ETB_APIVERS startup parameters.

None.

Informational. Prints CODEPAGE startup parameters.

None.

Internal check has detected an error in thread status logic. The reason might be system shortages. The thread might be flagged unusable.

Check if the server can still continue working. If not, restart server. If problem persists, contact Software AG support.

Dispatcher call to ERX runtime (Broker RECEIVE) failed. This message is accompanied by a genuine error message.

Check original error message for further action.

Informational. This token is used to identify the originator thread of a message.

None.

Informational. This token is used to identify the original thread of a message.

None.

Internal function failed. This message is accompanied by a genuine error message.

Check original error message for further action.

Internal callback function failed. This message is accompanied by a genuine error message.

Check original error message for further action.

Internal callback function failed. This message is accompanied by a genuine error message.

Check original error message for further action.

Internal function failed. This message is accompanied by a genuine error message. CICS: This message will also be used to dynamically initialize a shared memory block within the ERX Main control block.

Check original error message for further action. CICS: Recompile and/or reload ERX Main control block.

Informational. Prints BROKERID startup parameters (entered in the command line or configuration parameter BrokerID.

None.

Informational. Prints CLASS SERVER SERVICE startup parameters (entered in the command line or configuration parameter Class, ServerName and Server).

None.

CICS only: ERX Main control block could not be loaded.

Check CICS resource definitions and if module exist in DFHRPL load library.

CICS only: Invalid version detected in ERX Main control block. Either the version is out of support or (most likely) the control is corrupt.

Recompile ERX Main control block with updated ERXMAIN macro.

The message indicates an error with ERX Main control block. This message is accompanied by a genuine error message.

Check original messages for possible errors.

Usage error. The correct syntax will be displayed. The server will terminate.

Start server again with correct syntax.

Operating system-dependent USAGE message, part of message 10050056.

Start server again with correct syntax.

Operating system-dependent USAGE message, part of message 10050056.

Start server again with correct syntax.

Part of message 10050056.

Confirm usage messages and start server again with correct syntax.

(Customer) server subroutine <program-name> has abended. Depending on the operating system, dump information will be provided. The server will continue running. The thread in which the abend occurred will be terminated or (if not possible) will be marked as UNUSABLE.

Correct the malfunctioning subroutine.

Informational message.

None.

The complex function ERXTerminateServer will communicate with the Broker to stop all existing replicas for this server. This message is accompanied by a genuine error message.

Check original error message for further action.

Informational. Prints the number of "unsuccessful" calls:

• all calls that return with error because of server subroutine problem and/or data conversations,

• Broker (timeout) terminated the call

• client terminates during conversation

• in conversational mode: the conversation did not finish with DISCONNECT-COMMIT.

None.

Internal error in server. This message is accompanied by a genuine error message.

Check original error message for further action.

Service function failed. This message is accompanied by a genuine error message.

Check original error message for further action.

Informational. This message is printed to a trace file. The maximum number of thread entries is 256.
Exception: under CICS it is automatically calculated from free memory in the ERX Main control block.

None.

Informational. This message is accompanied by a timestamp. The message will be generated after the Broker availability has been successfully tested. See also message no. 10050069.

none

Informational. This message is accompanied by a timestamp.

none.

The EntireX RPC server detected that the Broker is not available (either during startup or at runtime). Depending on the restartcycles option, the server will try to logon again after a one-minute timeout. If the Broker becomes available during these restart cycles, the server will continue with message 10050067. Otherwise, it will terminate.

Restart Broker, if desirable.

Informational. Prints the Broker ID with which a session is requested. This Broker ID can be different from the default Broker ID.

None

Informational. Prints the class name, server name and service with which a connection is established. The values can be different from the default or the logical service

None

Your EntireX Installation is destroyed.

Reinstall EntireX.

The EntireX RPC server returned an error.

See under error number for further explanation and action to take.

The EntireX/Natural RPC Server did not find the server program.

Depending on the type of your RPC server, one of the following situations may apply:

1. If the server is an EntireX RPC server on Windows/UNIX:

   • The server stub with the name D<library>.dll on Windows or D<library>.so|sl on UNIX must be accessible to the EntireX RPC server. The program called must be available within that library as an export named D<program>.

   • The same applies to the server program. A server with the name <library>.dll on Windows or <library>.so|sl on UNIX must be accessible to the EntireX RPC server. The program called must be available within that library as an export named <program>.

   Check read/execution access, library names and exports.

2. If the server is an EntireX RPC server on CICS:

   • A program named <program> must exist in the DFHRPL steplib concatenation.

   • The program must be CSD-defined and (depending on CICS version) must be installed.

3. If the server is a Natural RPC Server:

   • If Natural Logon is switched on for the request or conversation, the program must be found within the target library (or its steplib concatenation).

   • If Natural Logon is switched off for the request or conversation, the program must be found in the initial library (or its steplib concatenation) of the Natural RPC Server.

   See also the appropriate Natural documentation.

4. If the server is an EntireX XML/SOAP RPC Server:

   • The server classes must be accessible from the EntireX XML/SOAP RPC Server.

   • Make sure that the path of the server classes is in the classpath.

Informational. Message will be displayed if SMH service was successfully established. The local listener port will be exposed.

None.

Some platforms require the shared library EXXRPCTCP to establish SMH services.

Check your installation: On Windows, the library exxrpctcp.dll should be contained in <drive>:\SoftwareAG\EntireX\bin; on UNIX, the library libexxrpctcp.so should be contained in folder /opt/softwareag/EntireX/lib.

The EntireX RPC server could not use TCP to support SMH services. This message is issued if TCP requests fail completely.

Contact your system administrator.

The SDF variable WORKER-PARMS in S-procedure START-RPC-SERVER is not set up correctly. This message will be sent by RPC servers under BS2000/OSD only.

Correct the job control and rerun the job.

An error occurred while establishing the main or a worker task. This message will be sent by RPC servers under BS2000/OSD only.

Contact Software AG support.

The server program called by the EntireX/Natural RPC Server caused an abnormal end.

Check the program and correct the error.

RPC server was started with option KERNELSECURITY, but failed.

This message is accompanied by a genuine error message.

Correct installation error and restart.

Informational.

RPC server runs with broker KERNELSECURITY=<level>.

None.

The host security refused an authentication request.

Inspect reason code. Retry if password mistyped, otherwise contact your security administrator.

Internal PC routines could not be installed.

Inspect reason code and contact your system administrator.

The host security refused to reset a previously performed authentication request.

Inspect reason code and contact your security administrator.

EntireX RPC server requires the ERX shared library to be available. On Windows this is usually located in directory <drive>:\SoftwareAG\EntireX\bin.

Check EntireX installation. Verify that the erx.dll is in standard installation path.

RPC server received request for target PL/I application but application interface has higher indent level than PL/I supports (32).

Correct RPC client application.

The server mapping file accessed with IDL library and IDL program for the RPC request contained an RPC protocol version not supported by the RPC server. See Supported RPC Protocols. A server mapping file is an EntireX Workbench file with extension .svm or .cvm. See Server Mapping Files for COBOL.

Contact Software AG support for RPC server upgrade.

The server mapping file accessed with IDL library and IDL program for the RPC request contained an invalid format. A server mapping file is an EntireX Workbench file with extension .svm or .cvm. See Server Mapping Files for COBOL.

Check that you have the latest updates for the EntireX Workbench installed. Try to produce the server mapping again, see COBOL Wrapper or IDL Extractor for COBOL and retry.

• If you are using server-side mapping files (.svm), deploy the correct server mapping to the RPC server. See Deploying Server-side Mapping Files to the RPC Server in the RPC server documentation for z/OS (CICS, Batch, IMS) | Micro Focus | CICS ECI | IMS Connect | BS2000/OSD | z/VSE (CICS | Batch).

  Note:
  For IMS Connect and CICS ECI connections with the webMethods EntireX Adapter, server-side mapping files are not deployed. They are wrapped into the Integration Server connection - the same as client-side mapping files. You need to update your Adapter connection. See Step 3: Select the Connection Type in the Integration Server Wrapper documentation. For RPC connections, deployment to the target RPC server is mandatory.

• If you are using client-side mapping files (.cvm), you need to rebuild all RPC clients communicating with this RPC server program. Select the appropriate wrapper (see EntireX Wrappers) and re-generate the client interface objects. For RPC connections with the webMethods EntireX Adapter, you need to update your Adapter connection. See Step 3: Select the Connection Type in the Integration Server Wrapper documentation.

If this fails, contact Software AG support.

If the RPC server uses a server-side mapping container, this message will be printed, otherwise no message. See Server-side Mapping Files in the RPC Server in the RPC server documentation for z/OS (CICS, Batch, IMS) | BS2000/OSD | z/VSE (CICS, Batch).

None.

The RPC server did not come up. In the RPC server configuration, EXTRACTOR is specified as the broker service name, but EXTRACTOR is used for internal purposes of the RPC server and is a Software AG reserved service name.

Do not specify EXTRACTOR as the broker service name in the RPC server configuration, and restart the RPC server.

The RPC server did not come up. In the RPC server configuration DEPLOYMENT is specified as the broker service name, but DEPLOYMENT is used for internal purposes of the RPC server and is a Software AG reserved service name.

Do not specify DEPLOYMENT as the broker service name in the RPC server configuration, and restart the RPC server.

The RPC server did not come up. In the RPC server configuration, the deployment service is specified (see Deployment Service for z/OS (CICS, Batch, IMS) | BS2000/OSD | z/VSE (CICS, Batch)), but the server-side mapping container could not be opened.

Check your installation. Possible reasons:

• The server-side mapping container is missing. For configuration see Enabling the Deployment Service for z/OS (CICS, Batch, IMS) | BS2000/OSD | z/VSE (CICS, Batch).

• The server-side mapping container has mismatched DCB parameter.

• ....

The CICS RPC Server tried to call an RPC server with an interface of type CICS with DFHCOMMAREA Calling Convention (COBOL Wrapper | Extractor), but the length of the data exceeded the CICS DFHCOMMAREA maximum of 32 KB.

Check the interface type of the target RPC server program called:

• If it is not a DFHCOMMAREA interface but a Large Buffer or Channel Container interface, the server mapping file may be missing or is wrong. A server mapping file is an EntireX Workbench file with extension .svm or .cvm. See Server Mapping Files for COBOL.

  • If you are using server-side mapping files (.svm), deploy the correct server mapping to the RPC server. See Deploying Server-side Mapping Files to the RPC Server in the RPC server documentation for z/OS (CICS, Batch, IMS) | Micro Focus | CICS ECI | IMS Connect | BS2000/OSD | z/VSE (CICS | Batch).

    Note:
    For IMS Connect and CICS ECI connections with the webMethods EntireX Adapter, server-side mapping files are not deployed. They are wrapped into the Integration Server connection - the same as client-side mapping files. You need to update your Adapter connection. See Step 3: Select the Connection Type in the Integration Server Wrapper documentation. For RPC connections, deployment to the target RPC server is mandatory.

  • If you are using client-side mapping files (.cvm), you need to rebuild all RPC clients communicating with this RPC server program. Select the appropriate wrapper (see EntireX Wrappers) and re-generate the client interface objects. For RPC connections with the webMethods EntireX Adapter, you need to update your Adapter connection. See Step 3: Select the Connection Type in the Integration Server Wrapper documentation.

• If it is a DFHCOMMAREA interface, it is not possible to call such an RPC server program. Check if you can migrate the RPC server program to a Large Buffer or Channel Container interface. See Supported COBOL Interface Types under Introduction to the IDL Extractor for COBOL or COBOL Server Interface Types under Introduction to the COBOL Wrapper.

The EntireX server was started as Micro Focus server, but the interface library EXX2MF was not found or could not properly be initialized.

• Check if the library EXX2MF can be found in the standard EntireX installation directory and if it is valid.

• Check for the Micro Focus installation if the library directory is located in the OS-library path.

  Note:
  Software AG might not support Micro Focus on your platform.

The EntireX interface library EXX2MF could not properly perform (thread) initialization.

Check the Micro Focus installation.

EntireX services EXTRACTOR or DEPLOYMENT were used other than by broker services EXTRACTOR or DEPLOYMENT.

• For the EntireX RPC client: use broker service EXTRACTOR and broker service DEPLOYMENT respectively.

• For the EntireX RPC server: configure the RPC server with EXTRACTOR=YES and DEPOLOYMENT=YES.

• Allow services EXTRACTOR and DEPLOYMENT in the Broker attribute file.

The EntireX RPC server runs with optionIMPERSONATION=AUTO,SAME_USER. This requires the client to send both, the EntireX user ID as well as the RPC user ID and the IDs must be equal.

Correct your EntireX client.

Deployment service is feasible only when using the programming language COBOL for the server programs (see also configuration parameter MARSHALLING in the respective RPC documentation section).

Check the RPC server configuration options for consistency.

By default, COBOL support under UNIX or Windows requires a server-side mapping container, but no container was specified.

Correct the RPC server configuration and provide a server-side mapping container; see Server-side Mapping Files in the RPC Server.

The RPC server runs with COBOL support but no server mapping file was found for this particular RPC request, where one is required. A server mapping file is an EntireX Workbench file with extension .svm or .cvm. See Server Mapping Files for COBOL.

• If you are using server-side mapping files (.svm), deploy the correct server mapping to the RPC server. See Deploying Server-side Mapping Files to the RPC Server in the RPC server documentation for z/OS (CICS, Batch, IMS) | Micro Focus | CICS ECI | IMS Connect | BS2000/OSD | z/VSE (CICS | Batch).

  Note:
  For IMS Connect and CICS ECI connections with the webMethods EntireX Adapter, server-side mapping files are not deployed. They are wrapped into the Integration Server connection - the same as client-side mapping files. You need to update your Adapter connection. See Step 3: Select the Connection Type in the Integration Server Wrapper documentation. For RPC connections, deployment to the target RPC server is mandatory.

• If you are using client-side mapping files (.cvm), you need to rebuild all RPC clients communicating with this RPC server program. Select the appropriate wrapper (see EntireX Wrappers) and re-generate the client interface objects. For RPC connections with the webMethods EntireX Adapter, you need to update your Adapter connection. See Step 3: Select the Connection Type in the Integration Server Wrapper documentation.

The server mapping file accessed with IDL library and IDL program is inconsistent and does not match the RPC request. A server mapping file is an EntireX Workbench file with extension .svm or .cvm. See Server Mapping Files for COBOL.

Check you have the latest updates for the EntireX Workbench installed. Try to produce the server mapping again and retry. See COBOL Wrapper or IDL Extractor for COBOL.

• If you are using server-side mapping files (.svm), deploy the correct server mapping to the RPC server. See Deploying Server-side Mapping Files to the RPC Server in the RPC server documentation for z/OS (CICS, Batch, IMS) | Micro Focus | CICS ECI | IMS Connect | BS2000/OSD | z/VSE (CICS | Batch).

  Note:
  For IMS Connect and CICS ECI connections with the webMethods EntireX Adapter, server-side mapping files are not deployed. They are wrapped into the Integration Server connection - the same as client-side mapping files. You need to update your Adapter connection. See Step 3: Select the Connection Type in the Integration Server Wrapper documentation. For RPC connections, deployment to the target RPC server is mandatory.

• If you are using client-side mapping files (.cvm), you need to rebuild all RPC clients communicating with this RPC server program. Select the appropriate wrapper (see EntireX Wrappers) and re-generate the client interface objects. For RPC connections with the webMethods EntireX Adapter, you need to update your Adapter connection. See Step 3: Select the Connection Type in the Integration Server Wrapper documentation.

If this fails, contact Software AG support.

EntireX server has found an application that exceeded the calculated API size. The impact depends on how much the limit is exceeded by.

Check that the program interface definition (IDL file) matches the server's interface.

An error occurred within the RPC Server runtime while deallocating storage during worker task shutdown.

None.

The (CICS) RPC server was started with transaction ID different to the transaction-id that was specified in ERXMAIN control block.

The transaction IDs must be unique.

An attempt was made to start (CICS) RPC server a second time.

This message was issued by the RPC server (see also message 10170004). Only one server instance can be started using the same shared memory block (ERXMAIN control block).

An attempt was made to start an RPC worker or user task, but the allocated thread table has no more free entries.

Either reduce the MAXW parameter or increase the SIZE parameter. Check also the server log file for errors, because this situation may also be caused by aborting threads.

Message of RPC server running under z/OS. Informational. Supports process automation.

None.

Message of RPC server running under z/OS. Informational. Supports process automation.

None.

Internal error.

Contact Software AG support

The server was configured to use a feature that is not supported under this operation system.

Change server configuration.

RPC server under CICS tried to perform EXEC CICS SYNCPOINT (due to end of conversation) but failed.

Check CICS response codes for this error.

At startup, the server found an option that is deprecated.

The message is informational. Normally, the option will still be supported for compatibility reasons, but support may be withdrawn in a future release. See Release Notes for recommended action.

A final step of the server initialization is to launch the configured minimum number of worker tasks. If this does not succeed within 10 seconds, the server aborts the initialization.

Verify server output for additional messages indicating problems with the worker initialization. Verify server trace output for additional error messages.

The cause of the error and corrective action depends on the type of your RPC server.

• If the server is an EntireX RPC server, contact Software AG support because of internal problems within the server.

• If the server is a Natural RPC Server, see the appropriate Natural documentation for error 6971.

The cause of the error and corrective action depends on the type of your RPC server.

• If the server is an EntireX RPC server, increase your memory resources and retry the program because a memory request could not be fulfilled by the operating system.

• If the server is a Natural RPC Server, see the appropriate Natural documentation for error 6974.

The EntireX/Natural RPC request could not be executed.

Examine the log of the EntireX/Natural RPC Server for the cause of the malfunction.

The cause of the error and corrective action depends on the type of your RPC server.

• If the server is an EntireX RPC server, the reason could be an invalid compression value.

• If the server is a Natural RPC Server, refer to the appropriate Natural documentation for error 6978.