Message Class ETBE - Broker Log and Console - Error Messages

EntireX broker was unable to load the security exit. 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 a configuration file (for instance the broker attribute file) has too many characters. This response arises in the following situations:

1. During broker startup 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 configuration 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 broker clients that can be active at one time is reached. A new client cannot be handled until client resources are available again by user timeouts.

Increase NUM-CLIENT (or if CLIENT-NONACT has too high a value, decrease it) in the broker attribute file.

This is a temporary resource shortage. The maximum number of 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 the broker later. If the error occurs frequently, 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 a configuration file (for instance the broker attribute file) is not known by the broker. This response arises in the following situations:

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

1. During broker startup, 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 configuration file as appropriate.

The service-specific CONV-LIMIT value is specified with UNLIM. In this special configuration, this is not allowed because the global NUM-CONVERSATION attribute is set to AUTO. See also Broker Resource Allocation.

Either change the global NUM-CONVERSATION parameter to a defined value, or change the specific CONV-LIMIT value to a particular value.

The global CONV_DEFAULT attribute is either specified as UNLIM or not specified at all. The error occurs in situations where EntireX Broker cannot calculate the number of conversations needed. This situation occurs if

• NUM-CONVERSATION=AUTO and CONV-DEFAULT=UNLIM and there is at least one service that does not assign CONV-LIMIT, or

• NUM-CONVERSATION=AUTO and CONV-DEFAULT is undefined and there is at least one service that does not assign CONV-LIMIT.

Correct the error in the attribute file. Define NUM-CONVERSATION with a particular value or define CONV-DEFAULT with a particular value or use the CONV-LIMIT attribute for every single service definition.

The specified value for a correct keyword in a configuration file (for instance the broker attribute file) must not be zero or null value. This response arises in the following situations:

1. During broker startup, when the global resources defined in the section DEFAULTS=BROKER are read, a value of zero or null 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 value of zero or null is detected within this service definition. The service cannot be registered.

Correct the value assigned to the keyword in the configuration file.

The specified value for a correct keyword in a configuration file (for instance the broker attribute file) is out of range. This response arises in the following situations:

1. During broker startup 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 configuration file.

The specified value for a correct keyword in a configuration file (for instance the broker attribute file) is wrong. This response arises in the following situations:

1. During broker startup, when the global resources defined in the section DEFAULTS=BROKER are read, a 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 configuration file.

The service-specific SHORT-BUFF-LIMIT value is specified with UNLIM. In this special configuration this is not allowed because the global NUM-SHORT-BUFFER attribute is set to AUTO. See also Broker Resource Allocation.

Either change the global NUM-SHORT-BUFFER parameter to a defined value, or change the specific SHORT-BUFF-LIMIT value to a particular value.

The global SHORT-BUFF-DEF attribute is either specified as UNLIM or not specified at all. The error occurs in situation where EntireX Broker cannot calculate the number of short buffers needed. This situation occurs if

• NUM-SHORT-BUFFER=AUTO and NUM-SHORT-DEF=UNLIM and there is at least one service that does not assign SHORT-BUFF-LIMIT, or

• NUM-SHORT-BUFFER=AUTO and NUM-SHORT-DEF is undefined and there is at least one service that does not assign SHORT-BUFF-LIMIT.

Correct the error in the attribute file. Define NUM-SHORT-BUFFER with a particular value or define NUM-SHORT-DEF with a particular value or use the SHORT-BUFF-LIMIT attribute for every single service definition.

The service-specific LONG-BUFF-LIMIT value is specified with UNLIM. In this special configuration ,this is not allowed because the global NUM-LONG-BUFFER attribute is set to AUTO.

Either change the global NUM-LONG-BUFFER parameter to a defined value, or change the specific SHORT-LONG-LIMIT value to a particular value.

The global LONG-BUFF-DEF attribute is either specified as UNLIM or not specified at all. The error occurs in situation where EntireX Broker cannot calculate the number of long buffers needed. This situation occurs if

• NUM-LONG-BUFFER=AUTO and NUM-LONG-DEF=UNLIM and there is at least one service that does not assign LONG-BUFF-LIMIT, or

• NUM-LONG-BUFFER=AUTO and NUM-LONG-DEF is undefined and there is at least one service that does not assign LONG-BUFF-LIMIT

Correct the error in the attribute file. Define NUM-LONG-BUFFER with a particular value or define NUM-LONG-DEF with a particular value or use the LONG-BUFF-LIMIT attribute for every single service definition.

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 under Broker Attributes.

A duplicate keyword a configuration file (for instance the broker attribute file) cannot be read.

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.

An unknown attribute definition was found. Please refer to the entry in the log file in order to find the line and the column where this error occurred.

Correct the broker attribute file and provide valid attribute definitions. See Service-specific Attributes under Broker Attributes.

The valid values for this attribute are YES or NO only. Please refer to the entry in the log file to find the line and the column where the error happened.

Correct the attribute file and select either YES or NO for the attribute where the error happened

A configuration file (for instance the broker attribute file) cannot be accessed. This response arises in the following situations:

1. During broker startup, 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.

Contact administrator or check for the following causes:

1. No configuration file is allocated to the broker.

2. The specified configuration file does not exist.

3. The broker has no access to the configuration file, for example for security reasons, or the configuration file is enqueued by another process.

4. The configuration file has an invalid format for the platform used. Refer to the appropriate Installation documentation.

This message is issued during broker startup. 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.

A configuration file (for instance the broker attribute file) cannot be accessed. This response arises in the following situations:

1. During broker startup, 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 the broker and the service definition from the DEFAULTS=SERVICE section is read, this service cannot be used.

Check all causes listed under error 0038, and then the following:
Ensure that no other process has changed the file characteristics of the configuration file.

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

The specified value for a correct keyword in a configuration file (for instance the broker attribute file) is wrong, that is, not alphanumeric. This response arises in the following situations:

1. During broker startup, when the global resources defined in the section DEFAULTS=BROKER are read, a 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 configuration file.

A mandatory keyword in the broker attribute file is missing. This response arises in the following situation: During broker startup, 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.

During broker startup, the section DEFAULTS=BROKER with the global resources was not found in the broker attribute file. The broker cannot be started.

Define the section DEFAULTS=BROKER in the broker attribute file.

During broker startup, an error has been detected in a configuration file parameters (for instance in the broker attribute file).

Examine the 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 during broker startup. The broker cannot be started.

Contact Software AG support.

The broker dispatcher has failed to start a worker task. This can occur during broker startup. 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 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 broker dispatcher has failed to start any worker task. This can occur at broker startup. The broker cannot be started.

Examine the 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 broker dispatcher has problems distributing the work to the worker subtasks.

Contact Software AG support.

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

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

Contact Software AG support.

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

During broker startup, the EntireX Broker detected an initialization error which causes shutdown.

Examine the output referenced by the SYSPRINT DD statement as well as the 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 broker has failed to start the TOM Task. This situation can occur during broker startup. The broker cannot be started.

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

During broker startup, 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 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 broker dispatcher has failed to start the Common Output Manager. This can occur when EntireX is started on BS2000/OSD.

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

During broker startup, 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 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 broker detected an error while writing messages to the log data set. This message is issued during broker startup. 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.

During broker startup, 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.

The EntireX Broker on BS2000/OSD was started with global attribute SECURITY=YES and security attribute ACCESS-SECURITY-SERVER=NO. This mode requires Broker running under TSOS in order to execute privileged security checks.

Start Broker under TSOS.

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

The maximum number of EntireX Broker services that can be active at one time is reached. A subsequent service register request is not accepted.

Try again later. If this error occurs frequently, increase the NUM-SERVICE attribute in the section DEFAULTS=BROKER in the broker attribute file.

The maximum number of EntireX Broker topics that can be active at one time is reached.

Try again later. If this error occurs frequently, increase the NUM-TOPIC attribute in the section DEFAULTS=BROKER in the broker attribute file.

The EntireX Broker on BS2000/OSD was started with global attribute SECURITY=YES and security attribute ACCESS-SECURITY-SERVER=YES. This mode requires that the Broker Security Server has already been started.

Start Broker Security Server and then restart the broker.

A topic is defined as ALLOW-DURABLE=YES but there is no subscriber store defined to save the subscriber data on any store.

Either change the topic attributes to ALLOW-DURABLE=NO which makes it impossible to make a durable subscription, or set the value of global attribute SUBSCRIBER-STORE to PSTORE. A valid SUBSCRIBER-STORE requires additional attributes for the persistent store type etc.

Note:
The secondary persistent store (SSTORE) feature is no longer available. We recommend you use the PSTORE persistent store to store your subscriber data, by setting Broker-specific parameter SUBSCRIBER-STORE=PSTORE.

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

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

During broker startup, 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.

During broker startup, an error has been detected in the broker persistent store parameters.

Examine the output referenced by the SYSPRINT DD statement as well as the 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/OSD, 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/OSD, you can obtain additional information by looking up the meaning of the macro return code in the BS2000/OSD Executive Macros documentation (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/OSD 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/OSD 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/OSD 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/OSD 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/OSD 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/OSD only. The ECB name that determines the event name for BS2000/OSD 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/OSD 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/OSD only. A BS2000/OSD 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/OSD Executive Macros documentation (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.

The EntireX Broker kernel does not recognize the Command and Information Services API version requested.

This is a user error. Please check the following:

• If you are using ETBINFO, ETBCMD or any other Software AG-provided Command and Information Services application: Check that the version of ETBINFO or ETBCMD is the same or earlier than the version of the Broker kernel.

• If you are using your own Command and Information Services application: verify that the Command and Information Services API version will work with the version of EntireX. The following table shows the maximum CIS API version for the respective version of EntireX:

  Broker/EntireX Version	Max. CIS API Version
  ETB 1 or ETB 2	1
  EXX 3,4,5,6	2
  EXX 7.1	3
  EXX 7.2	4
  EXX 7.3	5
  EXX 8.0 or 8.1	6
  EXX 8.2	7
  EXX 9.0, 9.5, 9.6	8

• A possible cause for this error is a SEND-LENGTH that is too short. Increase this value if necessary.

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

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

An EntireX Broker call involving PSTORE is requested but EntireX Broker runs with setting PSTORE=NO. Any PSTORE operation is prohibited.

Contact your Broker Administrator.

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 the 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. See Security Solutions in EntireX.

For ACI version 8 and above, this error can be caused by an application not honoring the returned value of kernel security in the 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 the 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.

The broker did not find the topic definition within the attribute file when a topic attempted to subscribe.

Check the topic specified in the TOPIC field in the API, or make sure the topic definition in the broker attribute file is valid.

A request for a UOW to be persisted (STORE=BROKER) cannot be fulfilled, because 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.

A mismatch in the broker attribute file has been detected: If an ENCRYPTION-LEVEL is specified, then SECURITY must be set to YES.

Verify that the security exit is present and set SECURITY=YES to enable ENCRYPTION-LEVEL processing.

Note:
The broker attribute setting SECURITY=NO cannot be used with any encryption level not equal to 0 (= zero); otherwise the ETBE0402 error condition will occur when application issues registration command.

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

The 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 through the Adabas PSTORE returned an error.

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

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

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

SUBSCRIBER-STORE=PSTORE is defined in broker attribute file, but PSTORE is set to NO in order to disable the persistent store for this Broker run.

Set PSTORE=COLD or PSTORE=HOT to run Broker with enabled PSTORE.

NUM-SUBSCRIBER-TOTAL must be greater than or equal to NUM-SUBSCRIBER. This parameter is required if SUBSCRIBER-STORE=PSTORE is defined.

Set NUM-SUBSCRIBER-TOTAL to AUTO or use a value greater than or equal to NUM-SUBSCRIBER.

NUM-TOPIC-TOTAL must be greater than or equal to NUM-TOPIC. This parameter is required if SUBSCRIBER-STORE=PSTORE is defined.

Set NUM-TOPIC-TOTAL to AUTO or use a value greater than or equal to NUM-TOPIC.

A mismatch in the broker attribute file has been detected: if the catch-all service has been defined (CLASS= *, SERVER= *, SERVICE = *) then the value of AUTO is not allowed for the NUM-CONVERSATION, NUM-LONG-BUFFER or NUM-SHORT-BUFFER attributes.

If the catch-all service is defined, make sure the attributes NUM-CONVERSATION, NUM-LONG-BUFFER and NUM-SHORT-BUFFER all have specified values.

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.

Please check previous error messages and contact Software AG support.

Broker is not able to start at least one communication manager and shuts down.

Please check previous error messages and contact Software AG support.

A configuration file (for instance the broker attribute file) cannot be read.

Make sure that the configuration file is readable and not corrupt.

The service-specific SERVER-LIMIT value is specified with UNLIM. In this special configuration, this is not allowed because the global NUM-SERVER attribute is set to AUTO. See also Broker Resource Allocation.

Either change the global NUM-SERVER parameter to a defined value, or change the specific SERVER-LIMIT value to a particular value.

The global SERVER-DEFAULT attribute is either specified as UNLIM or not specified at all. The error occurs in situations where EntireX Broker cannot calculate the number of servers needed. This situation occurs if

• NUM-SERVER=AUTO and SERVER-DEFAULT=UNLIM and there is at least one service that does not assign SERVER-LIMIT, or

• NUM-SERVER=AUTO and SERVER-DEFAULT is undefined and there is at least one service that does not assign SERVER-LIMIT.

Correct the error in the attribute file. Define NUM-SERVER with a particular value or define SERVER-DEFAULT with a particular value or use the SERVER-LIMIT attribute for every single service definition.

Compression of the data was attempted, but resulting size was equal to or greater than original data.

The compress option is turned OFF for this transmission of data; data will not be compressed.

During a decompress operation, failure occurred; it is most likely the result of insufficient memory for the process.

Increase available memory for process, if possible.

Error resulted from a compress or decompress operation, and is not accounted for by Errors 450 or 451.

Save trace information. Contact Software AG support.

The accounting output file on UNIX or Windows failed to open during Broker startup. The accounting function is turned off.

If accounting is not needed, no action is required. If accounting is needed, ensure that the accounting file to be written to is not in use by another process. After the accounting file is freed, the Broker must be restarted.

The global PUBLICATION-DEFAULT attribute is either specified as UNLIM or not specified at all. The error occurs in situations where EntireX Broker cannot calculate the number of publications needed. This situation occurs if

• NUM-PUBLICATION=AUTO and PUBLICATION-DEFAULT=UNLIM and there is at least one topic that does not assign PUBLICATION-LIMIT, or

• NUM-PUBLICATION=AUTO and PUBLICATION-DEFAULT is undefined and there is at least one topic that does not assign PUBLICATION-LIMIT.

Correct the error in the attribute file. Define NUM-PUBLICATION with a particular value or define PUBLICATION-DEFAULT with a particular value or use the PUBLICATION-LIMIT attribute for every single topic definition.

The topic-specific PUBLICATION-LIMIT value is specified with UNLIM. In this special configuration, this is not allowed because the global NUM-PUBLICATION attribute is set to AUTO. See also Broker Resource Allocation.

Either change the global NUM-PUBLICATION parameter to a defined value, or change the specific PUBLICATION-LIMIT value to a particular value.

The global SUBSCRIBER-DEFAULT attribute is either specified as UNLIM or not specified at all. The error occurs in situations where EntireX Broker cannot calculate the number of subscribers needed. This situation occurs if

• NUM-SUBSCRIBER=AUTO and SUBSCRIBER-DEFAULT=UNLIM and there is at least one topic that does not assign SUBSCRIBER-LIMIT or

• NUM-SUBSCRIBER=AUTO and SUBSCRIBER-DEFAULT is undefined and there is at least one topic that does not assign SUBSCRIBER-LIMIT.

Correct the error in the attribute file. Define NUM-SUBSCRIBER with a particular value or define SUBSCRIBER-DEFAULT with a particular value or use the SUBSCRIBER-LIMIT attribute for every single topic definition.

The topic-specific SUBSCRIBER-LIMIT value is specified with UNLIM. In this special configuration, this is not allowed because the global NUM-SUBSCRIBER attribute is set to AUTO. See also Broker Resource Allocation.

Either change the global NUM-SUBSCRIBER parameter to a defined value, or change the specific SUBSCRIBER-LIMIT value to a particular value.

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

Correct the attribute file and provide a valid DEFAULTS=TOPIC section. See Topic-specific Attributes under Broker Attributes.

A mismatch in the broker attribute file has been detected: if a catch-all topic has been defined (e.g. TOPIC= *), then the value of AUTO is not allowed for the NUM-PUBLICATION, NUM-LONG-BUFFER, NUM-SHORT-BUFFER, or NUM-SUBSCRIBER attributes.

If a catch-all topic is defined, make sure the attributes NUM-PUBLICATION, NUM-LONG-BUFFER, NUM-SHORT-BUFFER, and NUM-SUBSCRIBER all have specified values.

TOPIC attribute specifies ALLOW-DURABLE=NO, but application has requested to subscribe durably.

Ensure broker attribute file is consistent with the intention of the application.

This is a temporary resource shortage. The maximum number of EntireX Broker publishers that can be active at one time is reached. A new publisher cannot be handled until publisher resources are available again by user timeouts.

Increase NUM-PUBLISHER (or if PUBLISHER-NONACT has too high a value, decrease it) in the broker attribute file.

This is a temporary resource shortage. The maximum number of EntireX Broker subscribers that can be active at one time is reached. A new subscriber cannot be handled until subscriber resources are available again by user timeouts.

Increase NUM-SUBSCRIBER (or if SUBSCRIBER-NONACT has too high a value, decrease it) in the broker attribute file.

All Broker threads check the active state of the Timeout Manager during startup. This task is not running and Broker will shutdown.

Check the log file for error messages created by the Timeout Manager.

All Broker threads check the active state of the Worker tasks during startup. Since at least one Worker task did not come up properly, Broker will shutdown.

Check the log file for error messages created by the Worker tasks.

You cannot specify the same PORT number twice for the same HOST.

Specify a different PORT number.

This message reports a situation where EntireX Broker internal resources are currently not available.

None. This message is for diagnostic purposes only. EntireX Broker recovers the situation internally.

Global attribute ICU-CONVERSION in Broker section is set to NO and one or more service (or topic) definitions specify CONVERSION METHOD=ICU.

Change broker attribute ICU-CONVERSION to YES.

One nucleus of the transport layer detected an error and will stop now. All supported transports will issue this message on error.

Check the log file for error messages. Contact Software AG support.

An error occurred during initialization of the transport layer. All supported transports will issue this message on error during initialization.

Check the log file for error messages. Contact Software AG support.

The maximum number of AUTHORIZATIONRULE entries in the attribute file has been reached. The current maximum number is 16 authorization rules.

Reduce the number of AUTHORIZATIONRULE entries.

You cannot specify more than five HOST entries per section.

Reduce number of HOST entries.

You cannot specify more than five PORT entries per section.

Reduce number of PORT entries.

TRANSPORT=NET was specified but the transport-specific section DEFAULTS=NET is missing.

Define the transport-specific attributes in section DEFAULTS=NET.

TRANSPORT=SSL was specified but the transport-specific section DEFAULTS=SSL is missing.

Define the transport-specific attributes in section DEFAULTS=SSL.

The ICU Converter library (sagtchaicu.so on UNIX, sagtchaicu.dll on Windows or EXXICU on z/OS) is not loadable. The broker kernel will terminate.

Contact Software AG support.

A program exception was detected in Broker. The current request was interrupted with error response 00780777. Further details of the exception will be reported in the broker log.

Contact Software AG support.

Broker not APF-authorized.

Ensure that all load libraries in the broker kernel steplib are APF-authorized.

TRANSPORT=TCP was specified but the transport-specific section DEFAULTS=TCP is missing.

Define the transport-specific attributes in section DEFAULTS=TCP.

The mainframe console task failed to start. The broker kernel will terminate.

Contact Software AG support.

You cannot specify the same PORT number twice for the same HOST.

Specify a different PORT number.

Two command log output files are required for command logging.

Specify two command log output files when starting the broker kernel.

You cannot specify more than five STACK-NAME entries per section.

Reduce number of STACK-NAME entries.

EntireX Broker requires z/OS version 1.12 or above.

Contact Software AG support.

Unable to set the persistent store-specific trace level.

Contact Software AG support.

Broker could not create the queue entries and semaphores to manage the worker tasks.

Contact Software AG support.

An invalid SAF user ID was specified while attempting to reset a user.

Ensure that SAF user ID is correct.

Command and Information Services were unable to obtain security information. Security information is only available with EntireX Security.

This message is for informational purposes only.

Command and Information Services were unable to enable or disable accounting because the broker ACCOUNTING attribute is not on.

This message is for informational purposes only.

EntireX Security encountered an error during initialization. Additional error information will describe the problem. The broker kernel will terminate.

Consult the additional error text and take appropriate action or contact Software AG support.

The broker attribute file is missing a DEFAULTS section. Additional error information will display the section name.

Consult the additional error text and take appropriate action.

A variable in a configuration file (for instance the broker attribute file) cannot be read.

could not be exanded. Additional error information will display the variable name.

Consult the additional error text and take appropriate action.

EntireX Security encountered an error during finalization. Additional error information will describe the problem.

Consult the additional error text and take appropriate action or contact Software AG support.

EntireX Security encountered an error during a Command and Information Services request. Additional error information will describe the problem.

Consult the additional error text and take appropriate action or contact Software AG support.

EntireX Security encountered an error during a Command and Information Services request. Additional error information will describe the problem.

Consult the additional error text and take appropriate action or contact Software AG support.

An operating system function returned an error.

Please determine the real error by checking the macro return code in the BS2000/OSD documentation. For example, Message "ETBE0599 Macro BIND failed with RC 0C010600 for module BROKBTIA" will be issued if the ETBLIB is not correctly assigned to the load library containing module BROKBTIA.

The proxy component of the TCP/IP communicator could not be started in order to interact with the partner Broker.

Check the output files for additional error messages issued by the Broker.

The proxy component of the SSL communicator could not be started in order to interact with the partner Broker.

Check the output files for additional error messages issued by the Broker.

A command log output file could not be opened. Additional error information will describe the problem. Command logging will be disabled.

Consult the additional error text and take appropriate action or contact Software AG support.

Command and Information Services were unable to enable or disable command logging, switch command log output files or manipulate command log filters because the broker CMDLOG attribute is not on.

This message is for informational purposes only.

The internal communication of Broker failed due to an operating system error.

Contact Software AG support.

The internal heap is exceeded.

Increase the HEAP-SIZE and restart Broker.

The maximum number of TCP/IP connections is derived from the number of available file descriptors. This maximum has been reached.

Increase the number of file descriptors.

The Standby Broker instance must use PSTORE=HOT in order to perform a PSTORE takeover if necessary.

Define PSTORE=HOT for your Standby Broker.

The Load Broker (RUN-MODE=PSTORE-LOAD) must use PSTORE=COLD in order to create a new persistent store.

Define PSTORE=COLD for your Load Broker.

The Unload Broker must use PSTORE=HOT in order to migrate a persistent store.

Define PSTORE=HOT for your Unload Broker.

The PSTORE report was requested but there is no assignment to write the actual report data.

The PSTORE report was requested but there is no assignment to write the actual report data.

The accounting output file could not be opened. Additional error information will describe the problem. Accounting will be disabled.

Consult the additional error text and take appropriate action or contact Software AG support.

A accounting record could not be written. Additional error information will describe the problem. Accounting will be disabled.

Consult the additional error text and take appropriate action or contact Software AG support.

The PSTORE report was requested but the file could not be opened due to a system error.

Fix the error condition reported by the operating system.

No configured transport mechanism successfully initialized. The broker kernel will terminate.

Consult additional error messages and take appropriate action.

An internal memory consistency check failed.

Contact Software AG support.

Unable to create semaphore.

Contact your System Administrator.

The broker dispatcher has failed to start a thread due to a missing address constant.

Contact Software AG support.

The internal communication path between the task ordering a pool allocation and the task executing the order received an error.

broker log provides more detailed diagnostics about the reason not being able to perform post and wait between Broker threads.

Existing memory pool is full. Dynamic pool management is not enabled.

Request is rejected due to insufficient resources.

Attribute STORAGE-REPORT=YES was defined but no report file was assiged.

Assign storage report file. Refer to Storage Report for details.

Unable to open the storage report file. Check system error for details.

Fix system error and rerun.

Configuration file entirex.config does not contain the requested key that specifies the location of the license file.

Contact Software AG support.

On BS2000/OSD and z/OS, the license is printed during broker startup. However, the broker was unable to open the license report output file.

This error is accompanied with additional error text describing the problem. Correct the error and restart the broker. If the cause cannot be determined, contact Software AG support.

On BS2000/OSD and z/OS, the license check module is loaded dynamically. However, the broker was unable to load the license check module.

On BS2000/OSD, the LINK-NAME MLCLIB was not assigned to the MLC load library. On z/OS, the MLC load library is not concatenated to the STEPLIB chain.

The allocation of this pool will exceed MAX-MEMORY and is rejected.

Increase MAX-MEMORY or no action if maximum value was defined correctly. See Broker-specific attribute MAX-MEMORY.

An inconsistency of memory pool control data was detected.

Contact Software AG support.

An inconsistency of memory pool control data was detected.

Contact Software AG support.

An inconsistency of memory pool control data was detected.

Contact Software AG support.

An error occurred while performing a persistent store operation.

Depends on the subsequent messages.

This error may occur during Broker startup. c-tree detected PSTORE files still being used by a previous Broker instance. These files are being closed during Broker shutdown. However, this problem most likely occurs if the old instance of the Broker did not yet stop completely and the new instance already tried to initialize the PSTORE.

Wait for the previous Broker instance to shut down completely, then start the new Broker instance.

The broker cannot start because the PSTORE attribute parser has discovered an error in the attribute file.

Correct the broker attribute file.

On UNIX and Windows, the broker failed to contact ETBSRV.

Check the log of ETBSRV running on this machine.

The PSTORE migration delayed due to an unexpected error. The procedure will be stopped.

Check error messages reported in the broker log and fix the problem, then restart the migration procedure, by restarting both Brokers.

The PSTORE migration failed due to an error.

Check error messages reported in the broker log and fix the problem, then restart the migration procedure, by restarting both Brokers.

There was an inconsistency detected while migrating the PSTORE.

Check error messages reported in the broker log and fix the problem, then restart the migration procedure, by restarting both Brokers.

The original Standard Broker was started again but the Standby Broker performed the takeover and is now the new Standard Broker.

You cannot start the original Standard Broker while Standby Broker is running as the new Standard Broker. The original Standard Broker sould be started as the new Standby Broker.

An unrecoverable error occurred while taking over the persistent store. The Standby Broker stops.

Check error messages reported in the broker log and fix the problem.

A recoverable error occurred while taking over the persistent store. The Standby Broker will perform another attempt after CONTROL-INTERVAL time.

None.

MAX-TAKEOVER-ATTEMPTS has been reached by the Standby Broker without being able to take over the persistent store. The Standby Broker stops.

Contact Software AG support.

Broker was unable to contact the partner Broker.

Check error messages reported in the broker log and fix the problem.

The Standard Broker did not respond to Standby Broker's ping. The Standby Broker will initiate the takeover phase.

Check error messages reported in the log of the original Standard Broker and fix the problem.

Broker detected a transport error while trying to communicate with the partner Broker.

Check error messages reported in both broker logs and fix the problem.

The PARTNER-CLUSTER-ADDRESS defined in the Standard Broker does not match any of the TCP or SSL transport entries defined in the Standby Broker.

Either adjust PARTNER-CLUSTER-ADDRESS in Standard Broker or start Standby Broker with a matching transport entry.

There is no PARTNER-CLUSTER-ADDRESS definition in the Standard Broker.

Define PARTNER-CLUSTER-ADDRESS in the Standard Broker to allow running a Standby Broker.

The persistent store defined in Standard Broker and Standby Broker must be exactly the same.

Adjust the attributes for PSTORE-TYPE and the PSTORE-specific sections in each broker attribute file so both Broker instances match.

There is no PSTORE defined in the partner Broker instance.

Run the partner Broker with matching persistent store attributes.

The persistent stores defined in Load Broker and Unload Broker must be different.

Adjust the attributes for PSTORE-TYPE and the PSTORE-specific sections for both Broker instances. Make sure the Load Broker is assigned to a new persistent store, and your Unload Broker is assigned to the persistent store you wish to unload.

The broker detected an abend condition. This message is sent to the operator console and is accompanied by additional messages reporting general purpose register values.

Collect all output files and contact Software AG support.

An internal command was received with an unknown command code. This invalid command was ignored.

Contact Software AG support.

A shared library could not be loaded. EntireX Broker detected an error while loading an RPC Command and Information Services shared library.

Contact Software AG support.

A shared library could not be loaded. EntireX Broker detected an internal error while loading a Broker-internal RPC shared library.

Contact Software AG support.

The value of global attribute WORKER-MIN is greater than or equal to the value of global attribute WORKER-MAX.

Correct the attributes.

It was not possible to establish a new connection (or reestablish an existing connection after an interruption) for transport method TCP, SSL or NET. The connection was attempted as often as specified under RETRY-LIMIT (with a wait between attempts as specified under RETRY-TIME), but without success.

Check for the correct settings and availability of the appropriate transport.

An error occurred while reading the SDF variable MAIN-TASK-TSN. :1; provides further details.

This error is accompanied by an additional error text describing the problem. Correct the error and restart the broker. If the cause cannot be determined, contact Software AG support.

The subtask was unable to attach to the global shared memory.

This error is accompanied by an additional error text describing the problem. Correct the error and restart the broker. If the cause cannot be determined, contact Software AG support.