Message Class ETBW - Broker Log and Console - Unit of Work/Persistence Messages

During broker startup, an error was detected during the restart processing phase.

Examine the EntireX Broker log. Determine the cause of the error. Correct the error and restart the Broker. If the cause cannot be determined, contact Software AG Support.

The unit of work status code is not a recognized value.

This is probably an internal EntireX Broker error. Contact Software AG Support.

An attempt to shut down the persistent store failed.

None.

Your EntireX License has expired.

Contact your local Software AG office or distributor to extend your license.

UNIX/Windows only. The "etbnuc" process encountered an error while creating shutdown thread. Broker could not be initialized.

Contact Software AG Support.

The Communication Manager of the transport layer stops due to unrecoverable errors, exceeded retry limit or shutdown.

Check the log file for error messages. Ignore this warning if shutdown was requested.

The Communication Manager did not succeed in running the transport-specific Communicator. All attempts to restart the Communicator were not successful.

Check the log file for error messages.

A component of the transport layer detected an unexpected status and will stop immediately.

Check the log file for error messages or shutdown.

An operator command was issued that interacts with Broker's security component. However, security was not activated for this Broker.

Do not issue security relevant operator commands without activating security.

Broker detected that attributes of the indicated service specify both TRANSLATION and CONVERSION parameters. Broker ignores the TRANSLATION parameter and continues with initialization.

For a full migration from TRANSLATION to CONVERSION, edit the Broker attribute file and delete the line containing TRANSLATION= for this service in DEFAULTS=SERVICE.

This PSTORE-TYPE is not supported on this operating system.

Enter valid PSTORE-TYPE in the Broker attribute file. See PSTORE-TYPE under Broker-specific Broker Attributes.

Command logging was requested. However, it is not possible to switch on command logging due to configuration errors.

Fix the problem and switch on command logging.

The CPU time of the task is exceeded. Broker received the interrupt from the operating system and will go down.

Specify a TIME=1440 parameter for the JCL EXEC statement of the Broker to run Broker without CPU limit.

The transport-specific operator command cannot be executed. The transport is currently not active.

Issue the operator command when the transport is active.

The PARSER report was requested but the file assignment is missing.

Specify DD name ETBAREP to assign the PARSER report file.

A warning occurred while processing the EntireX License file. Additional error test will provide more information.

Consult the additional error text and take appropriate action.

Under z/OS and BS2000, the license is printed during startup. However, the assignment for the license report output file is missing.

Assign the license report output file.

Broker not APF-authorized.

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

Shutdown service failed. The service was not used by servers.

None.

An incorrect character conversion configuration for a broker service (CLASS, SERVER and SERVICE) was detected and corrected. The broker service is logged in the preceding message.

Correct the Broker attribute file. See Broker's Mechanism for Choosing the Character Conversion Approach under Introduction to Internationalization.

The CONFIG report was requested but the file assignment is missing.

Specify DD name ETBCREP to assign the CONFIG report file.

The MODULE report was requested but the file assignment is missing.

Specify DD name ETBMREP to assign the MODULE report file.

The defined percentage value defined with broker attribute PERCENTAGE-FOR-CONNECTION-SHORTAGE-MESSAGE has been reached.
:1: represents the number of connections currently in use.
:2: displays the maximum number of possible connections.

None. This message is for information purposes only.

This may indicate a configuration problem with Broker. Adabas Event Replication usually needs a Broker with a persistent store. However, this Broker is currently running without persistent store.

Stop Broker, configure a persistent store and start Broker with PSTORE=COLD or PSTORE=HOT. Ignore this warning if no persistent store is needed.

The TASK report was requested but the file assignment is missing.

None.

Direct SSL/TLS support (using GSK) inside the Broker under z/OS is no longer supported.

Configure the Broker port in AT-TLS instead. See the following sections in the z/OS Administration documentation:

• Using IBM's Application Transparent Transport Layer Security (AT-TLS)

• Migration from Broker's Direct SSL/TLS Support to AT-TLS