Error Class ETBE - Broker Log and Console Messages

EntireX Broker was unable to load the security exit. EntireX Broker tries to load the security exit only if SECURITY=YES is defined in the attribute file.

Either do not specify the SECURITY=YES in the attribute file, or make the security exit available.

The specified value for a correct keyword in the Broker attribute file has too many characters. This response arises in the following situations:

1. At EntireX Broker startup time when the global resources defined in the section DEFAULTS=BROKER are read, a wrong value length is detected within this section. The Broker cannot be started.

2. When a server tries to register with EntireX Broker and the service definition from the DEFAULTS=SERVICE section is read, a wrong value length is detected within this service definition. The service cannot be registered.

Correct the value assigned to the keyword in the Broker attribute file.

The definition of a server class is either missing or invalid.

Either specify a Class definition or use the correct values to specify one.

This is a temporary resource shortage. The maximum number of EntireX Broker servers that can be active at one time is reached. New servers are not accepted until server resources are available again, either by deregistrations or user timeouts.

Try to register the server to EntireX Broker later. If the error occurs freqently, increase NUM-SERVER (or if SERVER-NONACT has too high a value for some services, decrease it) in the Broker attribute file.

A given keyword in the Broker attribute file is not known by the Broker. This response arises in the following situations:

1. At EntireX Broker startup time, when the global resources defined in the section DEFAULTS=BROKER are read, a wrong keyword is detected within this section. The Broker cannot be started.

2. When a server tries to register with EntireX Broker and the service definition from the DEFAULTS=SERVICE section is read, a wrong keyword is detected within this service definition. The service cannot be registered.

Correct or remove the keyword in the Broker attribute file as appropriate.

The specified value for a correct keyword in the Broker attribute file is out of range. This response arises in the following situations:

1. At EntireX Broker startup time when the global resources defined in the section DEFAULTS=BROKER are read, the wrong value is detected for a value within this section. The Broker cannot be started.

2. When a server tries to register with EntireX Broker and the service definition from the DEFAULTS=SERVICE section is read, a wrong value is detected within this service definition. The service cannot be registered.

Correct the value assigned to the keyword in the Broker attribute file.

The DEFAULTS=SERVICE section in the attribute file could not be found.

Correct the Broker attribute file and provide a valid DEFAULTS=SERVICE section. See Service-specific Attributes.

A duplicate keyword in the Broker attribute file is found. This response arises in the following situation: At EntireX Broker startup time when the global resources defined in the section DEFAULTS=BROKER are read, a duplicate keyword is found within this section. The Broker cannot be started.

Eliminate the duplicate keyword in the Broker attribute file.

The Broker attribute file cannot be accessed. This response arises in the following situations:

1. At EntireX Broker startup time, when the global resources defined in the section DEFAULTS=BROKER are read, the Broker cannot be started.

2. When a server tries to register with EntireX Broker and the service definition from the DEFAULTS=SERVICE section is read, this service cannot be used.

Check for the following causes:

1. No Broker attribute file is allocated to the Broker.

2. The specified Broker attribute file does not exist.

3. EntireX Broker has no access to the attribute file, for example for security reasons, or the attribute file is enqueued by another process.

4. The Broker attribute file has an invalid format for the platform used. See the appropriate installation documentation.

If problem persists, contact administrator.

This message is issued at EntireX Broker startup time. The environment variable ETB_ATTR is not set. The Broker attribute file cannot be accessed.

The environment variable ETB_ATTR must contain the path and file name of the Broker attribute file to get startup parameters and the Service definitions. ETB_ATTR is set by the Broker startup shell script. Check the assignment of ETB_ATTR.

EntireX Broker did not find the service definition within the attribute file when a service attempted to register

Check the service specified in the CLASS, SERVER and SERVICE fields in the API, or make sure the service definition in the Broker attribute file is valid.

A mandatory keyword in the Broker attribute file is missing. This response arises in the following situation: At EntireX Broker startup time, when the global resources defined in the section DEFAULTS=BROKER are read, a keyword is missing in this section. The Broker cannot be started.

Insert the missing keyword in the Broker attribute file.

At EntireX Broker startup time, the section DEFAULTS=BROKER with the global resources was not found in the Broker attribute file. The Broker cannot be started.

Define the section DEFAULT=BROKER in the Broker attribute file.

At EntireX Broker startup time, an error has been detected in the Broker attribute file parameters.

Examine the EntireX Broker log data set and the operating system log. Correct the error and restart the Broker. If the cause cannot be determined, contact Software AG support.

The requested store needed by the definitions made along with the attributes in the section DEFAULTS=BROKER in the Broker attribute file is not available from the operating system.

Increase the storage available to the EntireX Broker from the operating system or, if possible, decrease the defined resources in the section DEFAULTS=BROKER in the Broker attribute file. The amount of storage required is given by message 0284.

This is a resource shortage. Currently, no long message containers are available. Long message containers are used for data/messages longer than 2048 bytes.

Because this is a temporary resource shortage, it makes sense to try the SEND call later in hope that the resource shortage is over. Be careful not to have a loop programmed in this situation. If this occurs frequently, increase the number of long message containers defined in the section DEFAULTS=BROKER with the keyword NUM-LONG-BUFFER.

The entry point to the work queue in the work queue header is not present. This can occur at EntireX Broker startup time. The Broker cannot be started.

Contact Software AG support.

The EntireX Broker dispatcher has failed to start a worker task. This can occur at EntireX Broker startup time. The Broker is active if at least one worker task can be started.

Check that the setting of NUM-WORKER in the Broker attribute file is not too high for the platform. Examine the EntireX Broker log data set and the operating system log. Correct the error and restart the Broker. If the cause cannot be determined, contact Software AG support.

The EntireX Broker dispatcher has failed to start any worker task. This can occur at EntireX Broker startup time. The Broker cannot be started.

Examine the EntireX Broker log data set and the operating system log. Correct the error and restart the Broker. If the cause cannot be determined, contact Software AG support.

The EntireX Broker dispatcher has problems distributing the work to the worker subtasks.

Contact Software AG support.

The EntireX Broker dispatcher cannot find a worker subtask to delegate work to. The Broker is stopped immediately.

Contact Software AG support.

This message is issued when the resource shortage in the long message container is over. You may find a 0061 error message in the log data set denoting the start of the resource shortage.

None. This message is informational only.

The EntireX Broker dispatcher has ended abnormally. The Broker is stopped immediately.

Contact Software AG support.

This message is issued when the resource shortage in the short message container is over. You may find a 0057 error message in the log data set denoting the start of the resource shortage. v

None. This message is for information purposes only.

The user exit that performs translation services could not be loaded. For Broker Services, the translation routine for the service is specified by the TRANSLATION= keyword of the directory entry. For the Broker, the translation routine for the service is specified by the TRANSLATION parameter for the service in the attribute file. The routine is loaded during RECEIVE calls to the Broker.

Check the log data set for further load failure messages. Possible causes for the failure are:

1. An incorrect name for the translation routine is specified.

2. The translation routine is linked incorrectly.

3. The translation routine does not reside in a library accessible by the Broker.

While writing a message to the log data set, a resource shortage occurred and the output of a log message is not possible.

Contact Software AG support.

EntireX Broker detected an error while writing a message. Messages are normally routed to the COM task for output.

Contact Software AG support.

EntireX Broker detected an error while writing a message. The structure for routing messages to the COM task does not exist or is destroyed. The Broker is stopped immediately.

Contact Software AG support.

At EntireX Broker startup time, the EntireX Broker detected an initialization error which causes shutdown.

Examine the output referenced by the SYSPRINT DD statement as well as the EntireX Broker log data set and the operating system log. Correct the error and restart the Broker. If the cause cannot be determined, contact Software AG support.

EntireX Broker has failed to start the TOM Task. This situation can occur at EntireX Broker startup time. The Broker cannot be started.

Examine the EntireX Broker log data set and the operating system log. Correct the error and restart the Broker. If the cause cannot be determined, contact Software AG support.

At EntireX Broker startup time, an error has been detected attempting to open the data set referenced by the SYSPRINT DD statement. The attempted output from the echo of the Broker startup parameters, the persistent store parameters, and the Broker attribute file parameters to the data set referenced by the SYSPRINT DD statement failed.

Examine the SYSPRINT DD statement, the EntireX Broker log data set and the Operating System log. Correct the error and restart the Broker. If the cause cannot be determined, contact Software AG support.

At EntireX Broker startup time, at least one error has been detected in the EntireX Broker startup parameters.

Examine the output referenced by the SYSPRINT DD statement as well as the EntireX Broker log data set and the operating system log. Correct the error and restart the Broker. If the cause cannot be determined, contact Software AG support.

EntireX Broker detected an error while writing messages to the log data set. This message is issued at EntireX Broker startup time. The Broker cannot be started.

Contact Software AG support.

This situation occurs when EntireX Broker is busy and internal resources needed to satisfy the call are currently not available.

Retry the call to EntireX Broker. If this occurs frequently, contact Software AG support.

This message applies to z/OS systems only.EntireX Broker detected an error while writing messages to the log data set. This message is issued at EntireX Broker startup time. The Broker cannot be started.

Check the JCL for a missing assignment of the SYSTERM DD statement.

At EntireX Broker startup time, the EntireX Broker detected that the load libraries are not all APF authorized in z/OS.

Ensure that all the data sets referenced by the STEPLIB DD statement have been APF authorized in z/OS. Check the spelling of the data set names for accuracy. Correct any error and restart the Broker. If the cause cannot be determined, contact Software AG support.

EntireX Broker has detected a shutdown request, and after telling the COM task to terminate, the COM task has not terminated within an acceptable time limit.

Examine the log data set of EntireX Broker and the operating system log. If the cause cannot be determined, contact Software AG support.

An error has been detected during the return of the user's EntireX Broker call back to the caller.

Contact Software AG support.

Attribute NODE in section DEFAULTS=NET is not defined. However, attribute NODE is necessary to identify the DBID that the Broker uses to work as an addressable "target". Extracting the DBID from the numeric section of the BROKER-ID is no longer supported.

Set attribute NODE=dbid.

During Broker startup, the shared memory for the Communicator instances could not be allocated. The previous message in the Broker error log contains detailed information about the allocation problem.

Check the previous error log message to solve the problem. If the shared memory is already allocated, a message "File exists" is written as the previous log message.

Broker startup has failed.

Examine the EntireX Broker log data set and the operating system log and use the information message in the log data set issued at startup to determine the cause of the error. If you cannot determine the cause, contact Software AG support.

EntireX Broker was unable to successfully allocate a worker queue entry (WQE) because insufficient entries are available.

Increase the parameter NUM-WQE in the Broker attribute file.

Communication buffer is too small.

Increase size of the communication buffer (NUM-COMBUF) and retry.

At EntireX Broker startup time, the EntireX Broker persistent store parameters were not specified. This is caused by not having SYSIN specified in the startup job.

The EntireX Broker persistent store parameters need to be specified in the input data set referenced by the SYSIN DD statement.

At EntireX Broker startup time, an error has been detected in the EntireX Broker persistent store parameters.

Examine the output referenced by the SYSPRINT DD statement as well as the EntireX Broker log data set and the operating system log. Correct the error and restart the Broker. If the cause cannot be determined, contact Software AG support.

This is an internal error and occurs if the buffer manager gets inconsistent data structures.

Contact Software AG support.

The user-written SECURITY exit has returned an error. The user is not authorized to use EntireX Broker.

A security violation has occurred. This message and the related user ID are written to the Broker log.

The user-written SECURITY exit has returned an error. The user is not authorized to use the requested Service.

A security violation has occurred. This message and the related user ID are written into the Broker log.

The Broker has received an invalid command from the operator console.

This is a user error. Check the operator command specified

During Broker startup, the required memory could not be allocated and the Broker could not be started. The name of the macro that failed is given in <2>. For BS2000, also given are the memory pool name in <1> and the return code of the macro in <3>.

Check the space requirements against the available space. Space requirements are highly influenced by the attributes defined in the attribute file. For the actual size, see message 0284 which was issued during Broker startup.

For BS2000, you can obtain additional information by looking up the meaning of the macro return code in the BS2000 manual Executive Macros, Reference Manual (Makroaufrufe an den Ablaufteil).

Example: R15 = 14000004 for ENAMP means that there is not enough free space in the task's address space.

If you cannot determine the cause of the error, contact Software AG support.

This message applies to BS2000 only. During startup, the Broker engine could not start the Dispatcher or the Dispatcher could not start the other Broker tasks. Therefore, the Broker could not be started.

Administrator - Depending on the additional error information:

1. <err.msg.code> from ENTER for <task>

   BS2000 returns error message code <err.msg.code> for ENTER/ENTER-JOB command which is used to start task <task>. Analyze the error message code and check parameter PRM... for <task> in EntireX Broker engine parameter file. Example: "JMS0031 from ENTER for ETBTOM" means that BS2000 has given error JMS0031 which means "job class not known to system". The cause for this error is a wrong job class name specified with parameter PRMTOM.

2. Internal error during ENTER for <task>

   The ENTER/ENTER-JOB command itself causes a problem. Contact Software AG support.

3. No JCL defined for <task>

   The JCL location was not specified correctly. Check parameter JOB.... for <task> in EntireX Broker engine parameter file for example, parameter JOBTOM if <task> is TOM.

This message applies to BS2000 only. During startup, the identified Broker module could not be loaded and therefore the Broker could not be started.

The module must be contained in the module library that is assigned to link name DDLIB2 in the Broker startup procedure. If this has been done correctly and you cannot determine the cause of the error, contact Software AG support.

The EntireX Broker engine has not received "Ready for work" from the Broker Dispatcher and the Broker cannot be started.

z/OS and z/VSE users, contact Software AG support.

BS2000 users, ensure that the Dispatcher task was started correctly and program ETBMAIN was loaded before this error message was issued. If both are true, contact Software AG support.

This message applies to BS2000 only. The ECB name that determines the event name for BS2000 eventing is invalid. The program where the error was detected is identified in the message (<1> and <2>).

Contact Software AG support.

This message applies to BS2000 only. The task name was not passed correctly to a task started by the Broker Engine or the Broker Dispatcher and therefore the Broker could not be started.

Contact Software AG support.

This message applies to BS2000 only. A BS2000 macro has returned an error. If this happens during startup, the EntireX Broker cannot be started. The name of the program where the error was detected is given in <1>, the macro name in <2>, and the return code in <3>.

Check the explanation for the return code in the BS2000 manual Executive Macros, Reference Manual (Makroaufrufe an den Ablaufteil). If the cause cannot be determined, contact Software AG support.

The address of an internal structure is not valid. The name of the program where the error was detected is given in <1> and the name of the structure is given in <2>.

Contact Software AG support.

An error has occurred during logging done in the EntireX Broker engine. The name of the program where the error was detected is given in <1>. <2> contains additional information about the error situation.

Depends on the additional error information:

• File not assigned
  Check JCL of EntireX Broker start job for CLOG assignment.

• OPEN error
  Check access to file assigned to CLOG. Ensure that the CLOG file has the correct format for the platform used.

• Data set is full
  This is for information purposes only. Logging is stopped but EntireX Broker continues.

  Any other error situation: contact Software AG support.

The EntireX Broker engine could not start the Dispatcher successfully, or the Dispatcher started but has not reached "Ready for work and active". Notation vrsnn refers to the version, release, SM and patch level, for example 61102 if patch 2 is installed.

Examine the Broker log data set and the operating system log. Correct the error and restart the Broker. If you cannot determine the cause of the problem, contact Software AG support.

You have attempted to start a Broker that is already running.

This message is for information purposes only.

Broker cannot create the thread to run the XTI operator command handler. This component is needed to run the Adabas/Entire Net-Work transport properly on Windows platforms. Broker will shutdown.

Please check previous error messages and contact Software AG support.

The Broker buffer manager could not allocate memory for the RECEIVE buffer. A detailed error message follows this message.

Check the next error message line in the EntireX Broker error log.

This situation occurs only when working with the TOKEN parameter in the API; that is, the user is identified by USER-ID/TOKEN instead of USER-ID/Internal ID. If the user changes the physical location between EntireX Broker calls (e.g., a new session from another terminal), the old session retrieves this response. The new session takes all conversations of the old session.

The program has to be ended.

This is a problem with the Broker stub used by the application. The stub did not send the EntireX Broker call in the correct internal format.

Check that the Broker stub being used is the correct one. Check the log data set for an image of the internal format. Examine this string for the user issuing the call.

The EntireX Broker dispatcher has detected the abend of a worker task. The Broker is stopped immediately.

If the problem reoccurs, start the Broker with parameter SIGCATCH=NO. This will produce a dump of the error situation. Send this dump to Software AG support.

One of the internal counters describing the number of used short buffers, long buffers, etc. has become negative.

Contact Software AG support.

This message is written if the user translation or conversion routine has an error. The message indicates active class.name.service and name of the relevant translation or conversion routine.

This is a user error. Check the application, locale string assigned and designated translation or conversion exit. Correct the error.

The internal communication between Broker processes has failed. This is a hard error. The previous message line in the Broker error log contains additional error information.

The error must be solved to get EntireX Broker running properly. A restart of the Broker could be required.

Resources obtained for a Command-And-Info Services query cannot released.

Contact Software AG support

EntireX Broker has terminated abnormally.

Contact Software AG support.

An error has occurred within the security exit, either explicitly returned by the exit function, or implicitly by overwriting the buffer maximum length.

Check the implementation of the security exit. Also check whether the application has sufficient permission to perform the desired operation.

An error occurred during the invocation of the LOGOFF exit.

Check the behavior of your security exit.

The Receive task could not be created correctly by the Communicator nucleus.

The previous message line in the Broker error log describes the reason for the failed task creation. EntireX Broker terminates with an error condition. Try to solve the problem and restart the Broker.

The Communicator nucleus could not create the Reply task correctly.

The previous message line in the Broker error log describes the reason for the failed task creation. EntireX Broker terminates with an error condition. Try to solve the problem and restart the Broker.

The Broker has detected an error while searching for a free PCB entry. There is no PCB entry available.

Increase NUM-SERVER and/or NUM-CLIENT.

The Broker has detected an error while searching for a free SCB (Service Control Block) entry. There is no SCB entry available. The number of SCBs is set based upon the number of clients, servers, and services. When this error is returned, it means that all of the SCBs are in use. The current formula for the number of SCBs is: NUM-CLIENTS + NUM-SERVERS + NUM-SERVICES + 5.

Recommendations:

• Increase NUM-SERVICE.

• Increase NUM-SERVER.

• Increase NUM-CLIENTS.

Increasing the values will increase the total number of SCBs.

To free up the idle SCBs sooner:

• Decrease CLIENT-NONACT.

• Decrease CONV-NONACT.

• Set SERVER-NONACT.

Decreasing the non-activity timers will cause the inactive resources to be made available to other users.

If DYNAMIC-MEMORY-MANAGEMENT is set to "YES", this error should no longer occur.

The Communicator nucleus could not initialize tasks or resources correctly.

The previous message lines in the Broker error log describe the reason for the failed Communicator initialization. EntireX Broker terminates with an error condition. Try to solve the problem and restart the Broker.

Each EntireX Broker process waits a short time after successful initialization. The process then checks all other Broker processes for activity. If a task is not active, this message is issued.The Broker performs its shutdown processing and terminates with an error.

Check the reason for the failed process and try to solve the problem.

The PSTORE operation to replace the contents of a unit of work failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

Initialization of the persistent store failed. The Broker could not be initialized.

Verify that the persistent store environment is set up properly and restart EntireX Broker.

An attempt to write data to the persistent store has failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

An attempt to read control data from the persistent store has failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

An attempt to read message data from the persistent store has failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

An attempt to update the persistent store has failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

An attempt to write two data items to the persistent store has failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

An attempt to delete data from the persistent store has failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

An attempt to scan for selected data on the persistent store has failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

An error occurred while processing the EntireX License file. Additional error test will provide more information. The broker kernel will terminate.

Consult the additional error text and take appropriate action.

The PSTORE operation to run a query is failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

An error occurred during initialization of PSTORE. The attribute, which specifies type of PSTORE, is not correct.

Check the broker attribute file. PSTORE-TYPE should be ADABAS, DIV, or FILE.

An error occurred while loading a module for PSTORE.

Check the library path (or steplib value), and make sure that pstore modules are installed. Pstore module names could be BTPSI or ADAPSI. The names vary depending on platform.

The setting for security in the Broker kernel is different from the settings in one or more of the Broker stubs. Either the Broker kernel and all stubs must be configured to operate with security, or the kernel and all stubs must be configured to operate without security. .

For ACI version 8 and above, this error can be caused by an application not honoring the returned value of Kernel Security in the EntireX Broker control block field.

Ensure the security settings are consistent for broker kernel and all the stubs.

The Broker is busy and the internal resources needed to satisfy the call are currently not available (due to concurrent attempts to serialize the process of creating a user, a block occurs and the user cannot get logged on).

Retry the call to EntireX Broker. If this happens frequently, contact Software AG support.

This error is associated with an invalid value for the PSTORE parameter for the persistent store being used.

Check the available values for PSTORE for the target persistent store. To create a new (empty) B-tree persistent store, use PSTORE=COLD.

Note:
B-tree is no longer supported. Using B-tree, data could be lost under certain machine failure conditions.

A request for a UOW to be persisted (STORE=BROKER) cannot be accomplished, since at startup, the Broker attributes specify no persistent store (PSTORE=NO).

Review Broker attribute settings related to the persistent store.

A request for a UOW status to be persisted cannot be accomplished, since at startup, the Broker attributes specify no persistent store (PSTORE=NO).

Review Broker attribute settings related to the persistent store.

Broker cannot create the thread to run the communication manager for SSL transport. If it is not possible to start at least one communication manager, Broker will shutdown.

Please check previous error messages and contact Software AG support.

EntireX Broker tried to create an internal index for every unit of work. This operation failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

EntireX Broker tried to add an entry to the internal index for units of work. This operation failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

The logical read operation thru the Adabas PSTORE returned an error.

Examine the Broker log file for more information and contact Software AG support if necessary.

EntireX Broker tried to delete an entry from the internal index for units of work. This operation failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

EntireX Broker tried to close the internal index for units of work. This operation failed.

Examine the Broker log file for more information and contact Software AG support if necessary.

Broker cannot create the thread to run the communication manager for TCP/IP transport. If it is not possible to start at least one communication manager, Broker will shutdown.