Version 9.5 SP1
 —  Error Messages and Codes  —

Message Class ETBE - Broker Log and Console - Error Messages

This page explains EntireX Broker Log and Console Messages. These messages have the format:

ETBEnnnn

where ETBE is the message class, and
nnnn is the message number in the range 0000-9999

Overview of Messages

ETBE0001 | ETBE0013 | ETBE0014 | ETBE0015 | ETBE0018 | ETBE0019 | ETBE0023 | ETBE0024 | ETBE0025 | ETBE0026 | ETBE0027 | ETBE0028 | ETBE0029 | ETBE0030 | ETBE0032 | ETBE0033 | ETBE0034 | ETBE0035 | ETBE0036 | ETBE0037 | ETBE0038 | ETBE0039 | ETBE0040 | ETBE0043 | ETBE0045 | ETBE0053 | ETBE0054 | ETBE0056 | ETBE0058 | ETBE0061 | ETBE0062 | ETBE0063 | ETBE0064 | ETBE0065 | ETBE0066 | ETBE0069 | ETBE0070 | ETBE0071 | ETBE0075 | ETBE0076 | ETBE0077 | ETBE0078 | ETBE0080 | ETBE0082 | ETBE0083 | ETBE0084 | ETBE0086 | ETBE0087 | ETBE0088 | ETBE0089 | ETBE0090 | ETBE0091 | ETBE0092 | ETBE0095 | ETBE0096 | ETBE0097 | ETBE0106 | ETBE0112 | ETBE0115 | ETBE0116 | ETBE0120 | ETBE0128 | ETBE0129 | ETBE0132 | ETBE0133 | ETBE0135 | ETBE0146 | ETBE0147 | ETBE0150 | ETBE0151 | ETBE0152 | ETBE0153 | ETBE0154 | ETBE0155 | ETBE0156 | ETBE0157 | ETBE0158 | ETBE0159 | ETBE0161 | ETBE0168 | ETBE0169 | ETBE0172 | ETBE0190 | ETBE0196 | ETBE0207 | ETBE0217 | ETBE0220 | ETBE0223 | ETBE0224 | ETBE0232 | ETBE0236 | ETBE0240 | ETBE0242 | ETBE0256 | ETBE0257 | ETBE0261 | ETBE0265 | ETBE0269 | ETBE0271 | ETBE0272 | ETBE0276 | ETBE0277 | ETBE0316 | ETBE0319 | ETBE0320 | ETBE0321 | ETBE0322 | ETBE0323 | ETBE0326 | ETBE0328 | ETBE0354 | ETBE0358 | ETBE0370 | ETBE0378 | ETBE0379 | ETBE0381 | ETBE0383 | ETBE0385 | ETBE0388 | ETBE0389 | ETBE0396 | ETBE0402 | ETBE0405 | ETBE0406 | ETBE0407 | ETBE0409 | ETBE0410 | ETBE0414 | ETBE0415 | ETBE0416 | ETBE0423 | ETBE0425 | ETBE0427 | ETBE0431 | ETBE0446 | ETBE0447 | ETBE0450 | ETBE0451 | ETBE0452 | ETBE0456 | ETBE0459 | ETBE0460 | ETBE0461 | ETBE0462 | ETBE0463 | ETBE0470 | ETBE0474 | ETBE0490 | ETBE0491 | ETBE0496 | ETBE0497 | ETBE0501 | ETBE0502 | ETBE0534 | ETBE0511 | ETBE0514 | ETBE0547 | ETBE0548 | ETBE0549 | ETBE0550 | ETBE0551 | ETBE0554 | ETBE0555 | ETBE0558 | ETBE0561 | ETBE0562 | ETBE0564 | ETBE0565 | ETBE0568 | ETBE0570 | ETBE0575 | ETBE0577 | ETBE0583 | ETBE0584 | ETBE0585 | ETBE0590 | ETBE0591 | ETBE0594 | ETBE0596 | ETBE0597 | ETBE0598 | ETBE0599 | ETBE0602 | ETBE0603 | ETBE0611 | ETBE0612 | ETBE0619 | ETBE0620 | ETBE0623 | ETBE0628 | ETBE0629 | ETBE0630 | ETBE0631 | ETBE0632 | ETBE0633 | ETBE0638 | ETBE0642 | ETBE0644 | ETBE0651 | ETBE0654 | ETBE0655 | ETBE0656 | ETBE0659 | ETBE0660 | ETBE0661 | ETBE0664 | ETBE0666 | ETBE0671 | ETBE0674 | ETBE0675 | ETBE0676 | ETBE0679 | ETBE0681 | ETBE0682 | ETBE0690 | ETBE0725 | ETBE0728 | ETBE0737 | ETBE0738 | ETBE0748 | ETBE0751 | ETBE0752 | ETBE0755 | ETBE0756 | ETBE0759 | ETBE0760 | ETBE0761 | ETBE0762 | ETBE0763 | ETBE0764 | ETBE0780 | ETBE0799 | ETBE0800 | ETBE0802 | ETBE0803 | ETBE0814 | ETBE0850 | ETBE0851

ETBE0001 SECURITY: Failed to load user exit
Explanation

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.

Action

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


ETBE0013 Value For Keyword Too Long
Explanation

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.

Action

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


ETBE0014 Class def missing or invalid
Explanation

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

Action

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


ETBE0015 Max Possible NUM-CLIENT Reached
Explanation

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.

Action

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


ETBE0018 Max Possible NUM-SERVER Reached
Explanation

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.

Action

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.


ETBE0019 TRANSLATION Not Specified

ETBE0023 Unknown keyword
Explanation

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.

Action

Correct or remove the keyword in the configuration file as appropriate.


ETBE0024 CONV-LIMIT may not be UNLIM
Explanation

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.

Action

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


ETBE0025 CONV-DEFAULT not spec or UNLIM
Explanation

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.

Action

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.


ETBE0026 Zero Value For Keyword Not Allowed
Explanation

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.

Action

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


ETBE0027 Value For Keyword Out Of Range
Explanation

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.

Action

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


ETBE0028 Invalid Value For Keyword
Explanation

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.

Action

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


ETBE0029 SHORT-BUFF-LIMIT may not be UNLIM
Explanation

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.

Action

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


ETBE0030 SHORT-BUFF-DEF not spec or UNLIM
Explanation

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.

Action

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.


ETBE0032 LONG-BUFF-LIMIT may not be UNLIM
Explanation

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.

Action

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


ETBE0033 LONG-BUFF-DEF not spec or UNLIM
Explanation

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

Action

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.


ETBE0034 SERVICE
Explanation

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

Action

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


ETBE0035 Duplicate Value Found
Explanation

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.

Action

Eliminate the duplicate keyword in the broker attribute file.


ETBE0036 Unknown service attribute
Explanation

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.

Action

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


ETBE0037 Value must be YES or NO
Explanation

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.

Action

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


ETBE0038 Error During Open Of File
Explanation

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.

Action

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.


ETBE0039 Env Var ETB_ATTR not set
Explanation

This message is issued during broker startup. The environment variable ETB_ATTR is not set. The broker attribute file cannot be accessed.

Action

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.


ETBE0040 Error During Close Of File
Explanation

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.

Action

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.


ETBE0043 Service Definition Not Found
Explanation

The broker did not find the service definition within the attribute file when a service attempted to register

Action

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.


ETBE0045 Keyword Value Must Be Numeric
Explanation

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.

Action

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


ETBE0053 Global Broker Attribute Missing
Explanation

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.

Action

Insert the missing keyword in the broker attribute file.


ETBE0054 DEFAULTS=BROKER Section Missing
Explanation

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

Action

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


ETBE0056 Parameter processing error
Explanation

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

Action

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.


ETBE0058 Failed To Get Memory From OS
Explanation

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.

Action

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.


ETBE0061 Shortage For NUM-LONG-BUFFER
Explanation

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

Action

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.


ETBE0062 Work Queue Anchor For WQEs Missing
Explanation

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.

Action

Contact Software AG support.


ETBE0063 Failed To Start Worker Task
Explanation

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.

Action

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.


ETBE0064 Failed To Start All Workers Tasks
Explanation

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

Action

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.


ETBE0065 WQEs Lost
Explanation

The broker dispatcher has problems distributing the work to the worker subtasks.

Action

Contact Software AG support.


ETBE0066 No Worker Task Dispatched
Explanation

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

Action

Contact Software AG support.


ETBE0069 NUM-LONG-BUFFER Available Again
Explanation

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.

Action

None. This message is informational only.


ETBE0070 Abnormal End Of Dispatcher
Explanation

The broker dispatcher has ended abnormally. The broker is stopped immediately.

Action

Contact Software AG support.


ETBE0071 NUM-SHORT-BUFFER Available Again
Explanation

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

Action

None. This message is for information purposes only.


ETBE0075 TRANS: Failed To Load Routine
Explanation

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.

Action

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.


ETBE0076 No Free OMB - Log Messages Lost
Explanation

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

Action

Contact Software AG support.


ETBE0077 Unknown Route Code Detected
Explanation

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

Action

Contact Software AG support.


ETBE0078 No OMB Available - Broker Failed
Explanation

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.

Action

Contact Software AG support.


ETBE0080 SHUTDOWN DUE TO INITIALIZATION ERROR
Explanation

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

Action

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.


ETBE0082 Failed To Start Timeout Manager
Explanation

The broker has failed to start the TOM Task. This situation can occur during broker startup. The broker cannot be started.

Action

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.


ETBE0083 SYSPRINT FAILED TO OPEN
Explanation

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.

Action

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.


ETBE0084 Failed to start Common Output Manager
Explanation

The broker dispatcher has failed to start the Common Output Manager. This can occur when EntireX is started on BS2000/OSD.

Action

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.


ETBE0086 BROKER STARTUP PARAMETER(S) ERROR
Explanation

During broker startup, at least one error has been detected in the EntireX Broker startup parameters.

Action

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.


ETBE0087 Failed To Open Error Log File
Explanation

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.

Action

Contact Software AG support.


ETBE0088 Failed To Get Lock
Explanation

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

Action

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


ETBE0089 Failed To Write Error Log File
Explanation

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.

Action

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


ETBE0090 EntireX Broker is not APF-authorized
Explanation

During broker startup, the EntireX Broker detected that the load libraries are not all APF-authorized in z/OS.

Action

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.


ETBE0091 EntireX Broker not started under TSOS
Explanation

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.

Action

Start Broker under TSOS.


ETBE0092 Communication Manager Not Stopped
Explanation

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.

Action

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


ETBE0095 Invalid WQE Status Detected
Explanation

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

Action

Contact Software AG support.


ETBE0096 Max Possible NUM-SERVICE Reached
Explanation

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

Action

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


ETBE0097 Max possible NUM-TOPIC reached
Explanation

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

Action

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


ETBE0106 Security Server not accessible
Explanation

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.

Action

Start Broker Security Server and then restart the broker.


ETBE0112 No SUBSCRIBER-STORE assigned
Explanation

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

Action

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.


ETBE0115 NET: NODE attribute missing
Explanation

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.

Action

Set attribute NODE=dbid.


ETBE0116 Allocation of Communicator pool failed
Explanation

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.

Action

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.


ETBE0120 Broker Startup Failed
Explanation

Broker startup has failed.

Action

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.


ETBE0128 Work queue full or alloc XWQE failed
Explanation

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

Action

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


ETBE0129 Not enough space in Communication buffer
Explanation

Communication buffer is too small.

Action

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


ETBE0132 PSI: Parameters not specified
Explanation

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

Action

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


ETBE0133 PSI: Parameter processing error
Explanation

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

Action

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.


ETBE0135 Failed to release Attached Buffers
Explanation

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

Action

Contact Software AG support.


ETBE0146 Access denied by Security Facility
Explanation

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

Action

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


ETBE0147 No authorization for this Service
Explanation

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

Action

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


ETBE0150 EntireX Broker Invalid Operator Command
Explanation

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

Action

This is a user error. Check the operator command specified


ETBE0151 Memory Pool <1> Macro <2> Failed. R15: <3>
Explanation

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

Action

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.


ETBE0152 Attach Error: <1>
Explanation

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.

Action

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.


ETBE0153 Load For Module <1> Failed - Abend
Explanation

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.

Action

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.


ETBE0154 No Response From Dispatcher
Explanation

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

Action

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.


ETBE0155 <1> Unknown ECB Name <2>
Explanation

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

Action

Contact Software AG support.


ETBE0156 ETBXSI: Invalid Task Type
Explanation

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.

Action

Contact Software AG support.


ETBE0157 <1> Macro <2> Failed. R15: <3>
Explanation

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

Action

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.


ETBE0158 <1> Unresolved Pointer To <2>
Explanation

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

Action

Contact Software AG support.


ETBE0159 <1> Log Error: <2>
Explanation

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.

Action

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.


ETBE0161 Broker Version vrsn Initialization Failed
Explanation

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.

Action

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.


ETBE0168 This instance of BROKER already running
Explanation

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

Action

This message is for information purposes only.


ETBE0169 XTI Operator Control Initialize Failed
Explanation

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.

Action

Please check previous error messages and contact Software AG support.


ETBE0172 Failed to get Attached Buffers
Explanation

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

Action

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


ETBE0190 API: Invalid Cmd/Info Services Version
Explanation

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

Action

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 8
  • A possible cause for this error is a SEND-LENGTH that is too short. Increase this value if necessary.


ETBE0196 Disconnected Due To New Location
Explanation

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.

Action

The program has to be ended.


ETBE0207 STUB: No request or reply buffer
Explanation

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.

Action

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.


ETBE0217 Worker Task Failed - Broker Stopped
Explanation

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

Action

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.


ETBE0220 Counter gets negative:
Explanation

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

Action

Contact Software AG support.


ETBE0223 ERROR FROM USER TRANSLATION
Explanation

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.

Action

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


ETBE0224 POST / WAIT error occurred
Explanation

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.

Action

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


ETBE0232 PSI: Query release failed
Explanation

Resources obtained for a Command and Info Services query cannot released.

Action

Contact Software AG support


ETBE0236 ABEND flagged, go down now
Explanation

The broker has terminated abnormally.

Action

Contact Software AG support.


ETBE0240 Error in ENCRYPTION/DECRYPTION exit
Explanation

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

Action

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


ETBE0242 Error in LOGOFF exit
Explanation

An error occurred during the invocation of the LOGOFF exit.

Action

Check the behavior of your security exit.


ETBE0256 Receive Task failed
Explanation

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

Action

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.


ETBE0257 Reply Task failed
Explanation

The Communicator nucleus could not create the Reply task correctly.

Action

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.


ETBE0261 No free participant entry
Explanation

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

Action

Increase NUM-SERVER and/or NUM-CLIENT.


ETBE0265 No free service entry
Explanation

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.

Action

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.


ETBE0269 PSTORE required
Explanation

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

Action

Contact your Broker Administrator.


ETBE0271 Communicator Nucleus failed
Explanation

The Communicator nucleus could not initialize tasks or resources correctly.

Action

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.


ETBE0272 Inactive task detected
Explanation

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.

Action

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


ETBE0276 :1: / Various MCI Errors on UNIX

ETBE0277 PSI: Replace operation failed
Explanation

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

Action

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


ETBE0316 PSI: Persistent Store init failed
Explanation

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

Action

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


ETBE0319 PSI: WRITE failed
Explanation

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

Action

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


ETBE0320 PSI: READ control data failed
Explanation

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

Action

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


ETBE0321 PSI: READ message data failed
Explanation

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

Action

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


ETBE0322 PSI: UPDATE failed
Explanation

An attempt to update the persistent store has failed.

Action

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


ETBE0323 PSI: WRITE both failed
Explanation

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

Action

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


ETBE0326 PSI: PURGE failed
Explanation

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

Action

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


ETBE0328 PSI: Scan operation failed
Explanation

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

Action

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


ETBE0354 EntireX License Key Error
Explanation

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

Action

Consult the additional error text and take appropriate action.


ETBE0358 PSI: Query operation failed
Explanation

The PSTORE operation to run a query is failed.

Action

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


ETBE0370 PSILIB: Invalid PSTORE-TYPE value
Explanation

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

Action

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


ETBE0378 PSILIB: Library not loadable
Explanation

An error occurred while loading a module for PSTORE.

Action

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.


ETBE0379 API: Inconsistent security installation
Explanation

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.

Action

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


ETBE0381 Unable to get lock for PCB Create
Explanation

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

Action

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


ETBE0383 PSILIB: PSILIB: PSTORE value invalid
Explanation

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

Action

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.


ETBE0385 Topic definition not found
Explanation

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

Action

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


ETBE0388 PSI: UOWs can NOT be persisted
Explanation

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

Action

Review broker attribute settings related to the persistent store.


ETBE0389 PSI: UOW status can NOT be persisted
Explanation

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

Action

Review broker attribute settings related to the persistent store.


ETBE0396 Start of SSL Communicator Failed
Explanation

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.

Action

Please check previous error messages and contact Software AG support.


ETBE0402 SECURITY/ENCRYPTION-LEVEL mismatch
Explanation

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

Action

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.


ETBE0405 PSI: UOW Index initialization failed
Explanation

The broker tried to create an internal index for every unit of work. This operation failed.

Action

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


ETBE0406 PSI: Add entry to UOW Index failed
Explanation

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

Action

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


ETBE0407 PSI: Logical read failed
Explanation

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

Action

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


ETBE0409 PSI: Delete entry from UOW Index failed
Explanation

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

Action

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


ETBE0410 PSI: Close UOW Index failed
Explanation

The broker tried to close the internal index for units of work. This operation failed.

Action

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


ETBE0414 SUBSCRIBER-STORE needs PSTORE
Explanation

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.

Action

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


ETBE0415 NUM-SUBSCRIBER-TOTAL too small
Explanation

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

Action

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


ETBE0416 NUM-TOPIC-TOTAL too small
Explanation

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

Action

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


ETBE0423 AUTO/Catch-All Service mismatch
Explanation

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.

Action

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


ETBE0425 Start of TCP Communicator Failed
Explanation

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.

Action

Please check previous error messages and contact Software AG support.


ETBE0427 Failed to start Any Communicators
Explanation

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

Action

Please check previous error messages and contact Software AG support.


ETBE0431 Error during read of file
Explanation

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

Action

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


ETBE0446 ATTR: SERVER-LIMIT may not be UNLIM
Explanation

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.

Action

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


ETBE0447 ATTR: SERVER-DEFAULT not spec or UNLIM
Explanation

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.

Action

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.


ETBE0450 Error during data compression
Explanation

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

Action

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


ETBE0451 Error during data decompression
Explanation

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

Action

Increase available memory for process, if possible.


ETBE0452 Unexpected error during comp/decomp
Explanation

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

Action

Save trace information. Contact Software AG support.


ETBE0456 Accounting file did not open; set to off
Explanation

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

Action

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.


ETBE0459 PUBLICATION-DEFAULT not spec/UNLIM
Explanation

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.

Action

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.


ETBE0460 PUBLICATION-LIMIT may not be UNLIM
Explanation

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.

Action

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


ETBE0461 SUBSCRIBER-DEFAULT not spec/UNLIM
Explanation

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.

Action

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.


ETBE0462 SUBSCRIBER-LIMIT may not be UNLIM
Explanation

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.

Action

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


ETBE0463 TOPIC Section missing
Explanation

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

Action

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


ETBE0470 AUTO/Catch-All Topic mismatch
Explanation

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.

Action

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.


ETBE0474 Durable SUBSCRIBE not allowed
Explanation

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

Action

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


ETBE0490 Max possible NUM-PUBLISHER reached
Explanation

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.

Action

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


ETBE0491 Max possible NUM-SUBSCRIBER reached
Explanation

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.

Action

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


ETBE0496 Timeout Manager not Active
Explanation

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

Action

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


ETBE0497 Worker Task not Active
Explanation

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.

Action

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


ETBE0501 TCP-PORT numbers not unique
Explanation

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

Action

Specify a different PORT number.


ETBE0502 Failed to get lock for WQE
Explanation

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

Action

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


ETBE0534 CONVERSION ignored if ICU-CONVERSION=NO
Explanation

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

Action

Change broker attribute ICU-CONVERSION to YES.


ETBE0511 Nucleus Startup Failed
Explanation

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

Action

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


ETBE0514 Transport Initialization Failed
Explanation

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

Action

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


ETBE0547 Max num AUTHORIZATIONRULE reached
Explanation

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

Action

Reduce the number of AUTHORIZATIONRULE entries.


ETBE0548 Max num HOST entries reached
Explanation

You cannot specify more than five HOST entries per section.

Action

Reduce number of HOST entries.


ETBE0549 Max num PORT entries reached
Explanation

You cannot specify more than five PORT entries per section.

Action

Reduce number of PORT entries.


ETBE0550 DEFAULTS=NET section missing
Explanation

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

Action

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


ETBE0551 DEFAULTS=SSL section missing
Explanation

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

Action

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


ETBE0554 ICULIB: Library not loadable
Explanation

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.

Action

Contact Software AG support.


ETBE0555 Program Exception
Explanation

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.

Action

Contact Software AG support.


ETBE0558 **N00**ETBXXCPT Signal SIGSEGV caught at location 0xA4800658
Explanation

Broker not APF-authorized.

Action

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


ETBE0561 DEFAULTS=TCP section missing
Explanation

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

Action

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


ETBE0562 Failed to start console task
Explanation

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

Action

Contact Software AG support.


ETBE0564 SSL-PORT numbers not unique
Explanation

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

Action

Specify a different PORT number.


ETBE0565 Specify two or none command log file(s)
Explanation

Two command log output files are required for command logging.

Action

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


ETBE0568 Max num STACK-NAME entries reached
Explanation

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

Action

Reduce number of STACK-NAME entries.


ETBE0570 Invalid IBM LE version
Explanation

EntireX Broker requires z/OS version 1.12 or above.

Action

Contact Software AG support.


ETBE0575 PSI: Set Trace Level failed
Explanation

Unable to set the persistent store-specific trace level.

Action

Contact Software AG support.


ETBE0577 Worker queue allocation failed
Explanation

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

Action

Contact Software AG support.


ETBE0583 Invalid SAF-ID specified
Explanation

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

Action

Ensure that SAF user ID is correct.


ETBE0584 Failed to retrieve Security Information
Explanation

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

Action

This message is for informational purposes only.


ETBE0585 broker attribute ACCOUNTING is not on
Explanation

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

Action

This message is for informational purposes only.


ETBE0590 Error in INITIALIZATION exit
Explanation

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

Action

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


ETBE0591 DEFAULTS section missing
Explanation

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

Action

Consult the additional error text and take appropriate action.


ETBE0594 Variable not expanded
Explanation

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.

Action

Consult the additional error text and take appropriate action.


ETBE0596 Error in FINALIZATION exit
Explanation

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

Action

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


ETBE0597 Error in INFORMATION exit
Explanation

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

Action

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


ETBE0598 Error in COMMAND exit
Explanation

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

Action

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


ETBE0599 Macro BIND failed with RC xxxxxxxx for module yyyyyyyy or Macro VSVI1 failed with RC xxxxxxxx for entry point yyyyyyyy
Explanation

An operating system function returned an error.

Action

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.


ETBE0602 Start of TCP/IP Proxy failed
Explanation

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

Action

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


ETBE0603 Start of SSL Proxy failed
Explanation

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

Action

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


ETBE0611 Failed to open command log file:
Explanation

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

Action

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


ETBE0612 broker attribute CMDLOG is not on
Explanation

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.

Action

This message is for informational purposes only.


ETBE0619 Pipe error occurred
Explanation

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

Action

Contact Software AG support.


ETBE0620 Heap overflow
Explanation

The internal heap is exceeded.

Action

Increase the HEAP-SIZE and restart Broker.


ETBE0623 No free TCP connection entry
Explanation

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

Action

Increase the number of file descriptors.


ETBE0628 Expect PSTORE=HOT in STANDBY mode
Explanation

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

Action

Define PSTORE=HOT for your Standby Broker.


ETBE0629 Expect PSTORE=COLD in LOAD mode
Explanation

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

Action

Define PSTORE=COLD for your Load Broker.


ETBE0630 Expect PSTORE=HOT in UNLOAD mode
Explanation

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

Action

Define PSTORE=HOT for your Unload Broker.


ETBE0631 No assignment for PSTORE report
Explanation

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

Action

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


ETBE0632 Failed to open accounting file:
Explanation

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

Action

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


ETBE0633 Failed to write accounting record:
Explanation

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

Action

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


ETBE0638 Failed to open PSTORE report file
Explanation

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

Action

Fix the error condition reported by the operating system.


ETBE0642 Invalid transport configuration detected
Explanation

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

Action

Consult additional error messages and take appropriate action.


ETBE0644 Memory format inconsistency detected
Explanation

An internal memory consistency check failed.

Action

Contact Software AG support.


ETBE0651 Create semaphore failed
Explanation

Unable to create semaphore.

Action

Contact your System Administrator.


ETBE0654 Unresolved function pointer
Explanation

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

Action

Contact Software AG support.


ETBE0655 Pool order failure
Explanation

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

Action

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


ETBE0656 Dynamic pool management not enabled
Explanation

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

Action

Request is rejected due to insufficient resources.


ETBE0659 No assignment for STORAGE Report
Explanation

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

Action

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


ETBE0660 Failed to open STORAGE Report file:
Explanation

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

Action

Fix system error and rerun.


ETBE0661 Key entirex.license.file not found
Explanation

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

Action

Contact Software AG support.


ETBE0664 Failed to open LICENSE Report file:
Explanation

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.

Action

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.


ETBE0666 Failed to load License Check routine
Explanation

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

Action

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.


ETBE0671 Requested allocation exceeds MAX-MEMORY
Explanation

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

Action

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


ETBE0674 Invalid memory pool address detected
Explanation

An inconsistency of memory pool control data was detected.

Action

Contact Software AG support.


ETBE0675 Unexpected status in buffer header
Explanation

An inconsistency of memory pool control data was detected.

Action

Contact Software AG support.


ETBE0676 Invalid slot count in buffer header
Explanation

An inconsistency of memory pool control data was detected.

Action

Contact Software AG support.


ETBE0679 c-tree Plus User Error:
Explanation

An error occurred while performing a persistent store operation.

Action

Depends on the subsequent messages.


ETBE0681 c-tree database already in use
Explanation

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.

Action

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


ETBE0682 PSI: Cannot read Attributes
Explanation

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

Action

Correct the broker attribute file.


ETBE0690 Unable to send broadcast message
Explanation

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

Action

Check the log of ETBSRV running on this machine.


ETBE0725 CONTROL-INTERVAL elapsed - stop Broker
Explanation

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

Action

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


ETBE0728 PSTORE load failed
Explanation

The PSTORE migration failed due to an error.

Action

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


ETBE0737 PSTORE inconsistency detected
Explanation

There was an inconsistency detected while migrating the PSTORE.

Action

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


ETBE0738 PSTORE currently in use
Explanation

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

Action

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.


ETBE0748 Unrecoverable error during takeover
Explanation

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

Action

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


ETBE0751 Takeover sequence failed
Explanation

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

Action

None.


ETBE0752 Max num takeover attempts reached
Explanation

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

Action

Contact Software AG support.


ETBE0755 Request to Partner Broker failed
Explanation

Broker was unable to contact the partner Broker.

Action

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


ETBE0756 Partner Broker is dead
Explanation

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

Action

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


ETBE0759 Transport error occurred
Explanation

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

Action

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


ETBE0760 PARTNER-CLUSTER-ADDRESS mismatch
Explanation

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.

Action

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


ETBE0761 PARTNER-CLUSTER-ADDRESS missing
Explanation

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

Action

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


ETBE0762 PSTORE-TYPE mismatch
Explanation

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

Action

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


ETBE0763 PSTORE-TYPE missing
Explanation

There is no PSTORE defined in the partner Broker instance.

Action

Run the partner Broker with matching persistent store attributes.


ETBE0764 Same PSTORE for UNLOAD and LOAD
Explanation

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

Action

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.


ETBE0780 BROKER ABEND CODE :1: PSW :2:
Explanation

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.

Action

Collect all output files and contact Software AG support.


ETBE0799 Invalid internal command ignored
Explanation

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

Action

Contact Software AG support.


ETBE0800 Broker internal RPC Server: Load failed
Explanation

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

Action

Contact Software AG support.


ETBE0802 Broker internal RPC Server: Load failed
Explanation

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

Action

Contact Software AG support.


ETBE0803 WORKER-MIN greater or equal WORKER-MAX
Explanation

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

Action

Correct the attributes.


ETBE0814 Transport RETRY-LIMIT exceeded
Explanation

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.

Action

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


ETBE0850 SDF variable MAIN-TASK-TSN could not be read: :1:
Explanation

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

Action

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.


ETBE0851 Unable to initialize subtask
Explanation

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

Action

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.


Top of page