This page explains informational messages from the EntireX Broker Log and Console. These messages have the format:
ETBMnnnn
where | ETBM | is the message class, and |
nnnn | is the message number in the range 0000-9999 |
ETBM0020 | ETBM0068 | ETBM0079 | ETBM0071 | ETBM0100 | ETBM0101 | ETBM0102 | ETBM0103 | ETBM0104 | ETBM0107 | ETBM0109 | ETBM0111 | ETBM0113 | ETBM0119 | ETBM0121 | ETBM0123 | ETBM0127 | ETBM0129 | ETBM0136 | ETBM0137 | ETBM0139 | ETBM0144 | ETBM0160 | ETBM0162 | ETBM0173 | ETBM0176 | ETBM0177 | ETBM0178 | ETBM0179 | ETBM0222 | ETBM0235 | ETBM0273 | ETBM0290 | ETBM0291 | ETBM0344 | ETBM0352 | ETBM0355 | ETBM0376 | ETBM0391 | ETBM0410 | ETBM0428 | ETBM0429 | ETBM0432 | ETBM0433 | ETBM0456 | ETBM0458 | ETBM0464 | ETBM0465 | ETBM0466 | ETBM0473 | ETBM0498 | ETBM0499 | ETBM0500 | ETBM0507 | ETBM0508 | ETBM0509 | ETBM0510 | ETBM0512 | ETBM0513 | ETBM0515 | ETBM0516 | ETBM0527 | ETBM0528 | ETBM0529 | ETBM0578 | ETBM0579 | ETBM0580 | ETBM0581 | ETBM0582 | ETBM0592 | ETBM0593 | ETBM0600 | ETBM0601 | ETBM0608 | ETBM0609 | ETBM0641 | ETBM0645 | ETBM0657 | ETBM0680 | ETBM0691 | ETBM0692 | ETBM0720 | ETBM0729 | ETBM0730 | ETBM0731 | ETBM0732 | ETBM0733 | ETBM0734 | ETBM0742 | ETBM0743 | ETBM0744 | ETBM0745 | ETBM0746 | ETBM0747 | ETBM0749 | ETBM0750 | ETBM0753 | ETBM0754 | ETBM0757 | ETBM0758 | ETBM0804 | ETBM0805
ETBM0020 | Failed to inform Attach Manager |
Explanation |
An Attach Manager is registered for this service, but could not be instructed to start a new replica. This might happen occasionally due to synchronization problems. |
Action |
If this error happens only rarely, do not worry about it. If it happens more often, or even prevents your automatic startup system from working correctly, contact Software AG support. |
ETBM0068 | Parameter processing successful |
Explanation |
During broker startup, configuration file parameters have been successfully processed for the correct syntax. |
Action |
This message is for information purposes only. |
ETBM0079 | Loading kernel security module |
Explanation |
During startup, the broker kernel loads the kernel security module.
ETBM0079 User Security Exit processing started ETBD0286 Diagnostic Values:
ETBD0286 Diagnostic Values:
|
Action |
This message is for information purposes only. |
ETBM0071 | NUM-SHORT-BUFFER available again |
Explanation |
The shortage for |
Action |
None. |
ETBM0100 | SAG EntireX Broker |
Explanation |
This message is issued at broker startup time. |
Action |
This message is for information purposes only. |
ETBM0101 | Broker Initializing |
Explanation |
The Broker startup procedure has begun. |
Action |
This message is for information purposes only. |
ETBM0102 | Broker Attributes Reading |
Explanation |
During startup, the Broker is reading the resource definitions in the
|
Action |
This message is for information purposes only. |
ETBM0103 | Obtaining memory for Broker Memory Pool |
Explanation |
During startup, the Broker read the attribute file correctly and is now
obtaining storage for the resources as defined in the
|
Action |
This message is for information purposes only. |
ETBM0104 | Initializing Structures |
Explanation |
During startup, the Broker has read the attribute file correctly and obtained the storage needed from the operating system. The Broker is now initializing the internal structures. |
Action |
This message is for information purposes only. |
ETBM0107 | Broker Stopped |
Explanation |
EntireX Broker has shut down, either by shutdown request from the console operator or by an abnormal end. |
Action |
This message is for information purposes only. |
ETBM0109 | Starting Worker Tasks |
Explanation |
During startup, the Broker has read the attribute file, obtained the storage needed from the operating system, initialized the internal structures, entered the dispatcher and started the COM task correctly. This message is issued before any worker task is started. |
Action |
This message is for information purposes only. |
ETBM0111 | Starting Timeout Manager |
Explanation |
During startup, the Broker has read the attribute file, obtained the storage needed from the operating system, initialized the internal structures, entered the dispatcher and started the COM task and at least one worker task correctly. This message is issued before the TOM task is started. |
Action |
This message is for information purposes only. |
ETBM0113 | Starting Common Output Manager |
Explanation |
During startup, the Broker has read the attribute file, obtained the storage needed from the operating system, initialized the internal structures, entered the dispatcher and started the COM task and at least one worker task correctly. This message is issued before the COM task is started. |
Action |
This message is for information purposes only. |
ETBM0119 | Receive Task started |
Explanation |
During Broker startup, a Receive Task for lightweight or compatibility communication has started successfully. This message is issued for every Receive Task. |
Action |
This message is for information purposes only. |
ETBM0121 | Common Output Manager stopped |
Explanation |
The COM task has detected a shutdown request for EntireX Broker. The COM task will shut down immediately. |
Action |
This message is for information purposes only. |
ETBM0123 | Timeout Manager Stopped |
Explanation |
The TOM task has detected a shutdown request for EntireX Broker. The TOM task will shut down immediately. |
Action |
This message is informational only. |
ETBM0127 | Receive Task stopped |
Explanation |
A Receive task has detected the shutdown request and will stop soon. This message is issued from every Receive task. |
Action |
This message is for information purposes only. |
ETBM0129 | Not enough space for Reply buffer |
Explanation |
The EntireX Broker buffer manager could not allocate enough memory for
the Reply buffer. The value of startup parameter |
Action |
Try the call again later. Increase the value |
ETBM0136 | Common Output Manager started |
Explanation |
The Broker COM task has started successfully. |
Action |
This message is for information purposes only. |
ETBM0137 | Timeout Manager Started |
Explanation |
The Broker TOM task has started successfully. |
Action |
This message is for information purposes only. |
ETBM0139 | Worker Task Started |
Explanation |
This message is issued for each worker task that is started successfully. |
Action |
This message is for information purposes only. |
ETBM0144 | Worker Task Stopped |
Explanation |
A worker task has detected the shutdown request for EntireX Broker and will stop soon. This message is issued from every worker task. |
Action |
This message is for information purposes only. |
ETBM0160 | Broker Version vrsnn Initialized |
Explanation |
The EntireX Broker engine has received "Ready for work" from the Dispatcher and the Dispatcher is active. Notation vrsnn represents the version, release, SM and patch level (for example 61102 if patch 2 is installed). |
Action |
This message is for information purposes only. |
ETBM0162 | :<1>:<2>:<3>:<4>:<5>:<6>:<7> |
Explanation |
During broker startup, this message shows specific module maintenance information (<1> module name, <2> date, <3> time, <4> version maintenance level, <5> entry point, <6> length, <7> load point). |
Action |
This message is for information purposes only. |
ETBM0173 | EntireX Broker initialization finished |
Explanation |
All tasks and resources of EntireX Broker are established. The main process waits until the activated processes are finished. |
Action |
This message is for information purposes only. |
ETBM0176 | Nucleus has finished initialization |
Explanation |
The Communicator nucleus has established all processes and resources for the Communicator instances (Receive and Reply tasks).The nucleus returns to the EntireX Broker main task successfully. |
Action |
This message is for information purposes only. |
ETBM0177 | Starting Reply Task |
Explanation |
The Communicator nucleus is creating the Reply process. The Reply task is needed to return data from EntireX Broker to the user. |
Action |
This message is for information purposes only. |
ETBM0178 | Starting Receive Task |
Explanation |
The Communicator nucleus is creating the Receive process. The Receive task is needed to get data from the user and send it to EntireX Broker. |
Action |
This message is for information purposes only. |
ETBM0179 | Broker Stopping As Requested |
Explanation |
The EntireX Broker dispatcher has detected a shutdown request and will initiate Broker shutdown immediately by informing all worker tasks and the COM task to terminate. Only calls to the Broker that have already been dispatched to the worker tasks will be completed. New calls to the Broker or calls in the Broker input queue will not be processed. |
Action |
This message is for information purposes only. |
ETBM0222 | Command from Administrator accepted |
Explanation |
The Broker kernel has received a valid command. The command is logged for statistical purposes. |
Action |
None. |
ETBM0235 | SHUTDOWN flagged, go down now |
Explanation |
Shutdown has been requested and the associated indication has been detected. |
Action |
None. |
ETBM0273 | <variable text> |
Explanation |
An MCI command was issued by the ETBOPR utility. This message provides the command received from EntireX Broker. The command is executed immediately after this message. |
Action |
This message is for information purposes only. |
ETBM0290 | Reply Task started |
Explanation |
During Broker startup, a Reply task for lightweight or compatibility communication has started successfully. This message is issued for each Reply task started. |
Action |
This message is for information purposes only. |
ETBM0291 | Reply Task stopped |
Explanation |
A Reply task has finished its work. This message is issued from every reply task. |
Action |
This message is for information purposes only. |
ETBM0344 | Service MAX-UOWS exceeds Broker MAX-UOWS |
Explanation |
The value of the |
Action |
None. This message is for information purposes only. The server's
|
ETBM0352 | EntireX License is Perpetual |
Explanation |
The EntireX license will never expire. |
Action |
This message is informational only. |
ETBM0355 | Preceding License Key Errors are ignored |
Explanation |
On BS2000/OSD and z/OS, the license check has detected errors. However, these errors will be ignored. Subsequent product-specific license checks may cause a Broker shutdown. |
Action |
This message is for information purposes only. |
ETBM0376 | ECS Initialization failed |
Explanation |
The Broker could not initialize Entire Conversion Services (ECS) which
are needed if any server definition in the Broker attribute file specifies the
|
Action |
Make sure that the Broker knows where the ECS object files are located. For UNIX, this means that environment variable ECSOBJDIR is defined and contains the name of a directory containing the ECS object files (*.edo and *.pto files). For z/OS, this means that the DDECSOJ DD statement points to the EXX ECS library included on the EntireX installation medium. If the problem remains, contact Software AG support. |
ETBM0391 | ICU Initialization failed |
Explanation |
Broker was unable to initialize the ICU converter. |
Action |
None. |
ETBM0410 | X-COM Communicator stopped |
Explanation |
The XCOM Communicator could not be started. |
Action |
See the previous error message in the log and correct this problem. |
ETBM0428 | Windows delayload error |
Explanation |
A required library is missing or invalid. |
Action |
A subsequent error message will provide more information. |
ETBM0429 | Missing or invalid XTI library |
Explanation |
|
Action |
If the Entire Net-Work transport is required, install the Entire Net-Work product. |
ETBM0432 | Obsolete attribute |
Explanation |
A configuration file (for instance the Broker attribute file) contains an attribute which is no longer supported. |
Action |
Edit the configuration file to either delete the obsolete attribute or comment out the attribute. |
ETBM0433 | Attribute invalid on this platform |
Explanation |
Broker attribute file contains an attribute that is not valid on this platform. |
Action |
Edit the attribute file to either delete or comment out the invalid attribute. |
ETBM0456 | Accounting file did not open; set to off |
Explanation |
There was an error in creating a file to write accounting records. Accounting will be disabled and broker will continue to initialize. |
Action |
Check broker log file for more details. |
ETBM0458 | Opening accounting file |
Explanation |
Broker has successfully created/opened the accounting file. Name of the accounting file follows this message. |
ETBM0464 | RESTART: PSF Initialization complete |
Explanation |
The persistent store framework was successfully initialized. |
Action |
None. |
ETBM0465 | RESTART: PSF Open complete |
Explanation |
The persistent store was successfully opened for restore processing. |
Action |
None. |
ETBM0466 | RESTART: a group of 1000 UOWs restored |
Explanation |
Broker reports the progress of the restore procedure in steps of 1,000 units of work. Another 1,000 units of work have been successfully restored. |
Action |
None. |
ETBM0473 | Internal service ignored |
Explanation |
Broker detected an entry corresponding to a reserved internal service name in the broker attribute file. |
Action |
Remove the offending service definition from the attribute file. |
ETBM0498 | Invalid Adabas Command Rejected |
Explanation |
The receiver task of the NET transport detected an unsupported Adabas command. This command will be rejected with error response 02150022. See Adabas Messages and Codes for response code 22. The Adabas client used the database ID of EntireX by mistake. |
Action |
No action necessary. |
ETBM0499 | Wrong Adabas File Number Rejected |
Explanation |
The receiver task of the NET transport detected a wrong Adabas file number in the Adabas control block. This command will be rejected with error response 02150017. See Adabas Messages and Codes for response code 17. The Adabas client used the database ID of EntireX and a wrong file number by mistake. |
Action |
No action necessary. |
ETBM0500 | Transport Ready for Communications |
Explanation |
The Transport layer initialized properly and is ready for communications. All supported transports will issue this message on success. |
Action |
Informational message only. |
ETBM0507 | Communicator Started |
Explanation |
The Communicator of the Transport layer is started. All supported transports will issue this message on startup. |
Action |
Informational message only. |
ETBM0508 | Communicator Stopped |
Explanation |
The Communicator of the Transport layer is stopped. All supported transports will issue this message before termination. |
Action |
Check the log file for error messages. Ignore this message if shutdown was requested. |
ETBM0509 | Nucleus Started |
Explanation |
One nucleus of the Transport layer is started. All supported transports will issue this message on startup. |
Action |
Informational message only. |
ETBM0510 | Nucleus Stopped |
Explanation |
One nucleus of the Transport layer is stopped. All supported transports will issue this message before termination. |
Action |
Check the log file for error messages. Ignore this message if shutdown was requested. |
ETBM0512 | Transport Initialization Started |
Explanation |
The Communicator starts to initialize the transport layer. All supported transports will issue this message on startup. |
Action |
Informational message only. |
ETBM0513 | Transport Initialization Finished |
Explanation |
The Communicator initialized the transport layer successfully. All supported transports may issue this message. |
Action |
Informational message only. |
ETBM0515 | Transport Restart Possible |
Explanation |
The Communication Manager detected the termination of the Communicator. According to the transport-specific response code, it is possible to restart this transport layer again, but it might be forbidden due to the transport-specific attribute file definitions. |
Action |
Informational message only. |
ETBM0516 | Transport Restart Permitted |
Explanation |
The Communication Manager detected the termination of the Communicator. According to the transport-specific attribute file definitions, it is permitted to run the restart section of the Communication Manager to try to reestablish this specific transport layer. |
Action |
Informational message only. |
ETBM0527 | OP-CMD CHANGE_LOG_LEVEL Received |
Explanation |
The operator command interface echoes the incoming command request. |
Action |
Informational message only. |
ETBM0528 | OP-CMD PING Received |
Explanation |
The operator command interface echoes the incoming command request. |
Action |
Informational message only. |
ETBM0529 | OP-CMD SHUTDOWN Received |
Explanation |
The operator command interface echoes the incoming command request. The EntireX will shutdown. |
Action |
Informational message only. |
ETBM0578 | Reset ACEE for SAF-ID .. |
Explanation |
Operator command |
Action |
None. |
ETBM0579 | Security statistics |
Explanation |
Operator command |
Action |
None. |
ETBM0580 | Broker statistics |
Explanation |
Operator command |
Action |
None. |
ETBM0581 | Broker resource usage |
Explanation |
Operator command |
Action |
None. |
ETBM0582 | Function completed |
Explanation |
Indicates the end of the console output. |
Action |
None. |
ETBM0592 | Redundant attribute is ignored |
Explanation |
Since transport-specific sections have been introduced, the global attribute is considered redundant information. This message informs about details of the attribute processing. |
Action |
Delete the reported global attribute. It is no longer necessary. |
ETBM0593 | Attribute will be retired |
Explanation |
Since transport-specific sections have been introduced, the global attribute is no longer necessary. The transport-specific attribute should be used instead. |
Action |
Delete the reported global attribute and specify the transport-specific attribute instead. |
ETBM0600 | Transport Proxy started |
Explanation |
The transport proxy has been successfully started. |
Action |
None. |
ETBM0601 | Transport Proxy stopped |
Explanation |
The transport proxy has been stopped. |
Action |
None. |
ETBM0608 | Command log file opened: |
Explanation |
The specified command log output file has been opened. |
Action |
This message is for informational purposes only. |
ETBM0609 | Command log file closed: |
Explanation |
The specified command log output file has been closed. |
Action |
This message is for informational purposes only. |
ETBM0641 | EntireX License Data |
Explanation |
EntireX licensing data is displayed. |
Action |
None. |
ETBM0645 | License check completed |
Explanation |
The license check has been finished without detecting an error. |
Action |
This message is for information purposes only. |
ETBM0657 | Broker pool usage: |
Explanation |
This message provides the response to operator command
|
Action |
No action required. |
ETBM0680 | Retry allocation with emergency setting |
Explanation |
Broker was unable to create the initial set of memory pools with the existing configuration and will attempt to repeat with an emergency configuration. |
Action |
No action required. |
ETBM0691 | Broadcast message sent |
Explanation |
On UNIX and Windows, the broker sent a broadcast message to ETBSRV. |
Action |
None. |
ETBM0692 | Send broadcast message |
Explanation |
On UNIX and Windows, the broker is going to send a broadcast message to ETBSRV. |
Action |
None. |
ETBM0720 | Operator typed in: :1: |
Explanation |
Broker received command :1: from the operator console. |
Action |
None. |
ETBM0729 | PSTORE load finished successfully |
Explanation |
The Load Broker finished the PSTORE migration successfully. |
Action |
None. |
ETBM0730 | PSTORE unload finished successfully |
Explanation |
The Unload Broker finished the PSTORE migration successfully. |
Action |
None. |
ETBM0731 | PSTORE unload started |
Explanation |
The Unload Broker started the PSTORE migration. |
Action |
None. |
ETBM0732 | PSTORE unload stopped |
Explanation |
The Unload Broker stopped the PSTORE migration. |
Action |
None. |
ETBM0733 | PSTORE load started |
Explanation |
The Load Broker started the PSTORE migration. |
Action |
None. |
ETBM0734 | PSTORE load stopped |
Explanation |
The Load Broker stopped the PSTORE migration. |
Action |
None. |
ETBM0742 | Broker running in ADMIN mode |
Explanation |
The broker is running in
|
Action |
None. |
ETBM0743 | Broker running in STANDARD mode |
Explanation |
The broker is running in
|
Action |
None. |
ETBM0744 | Broker running in STANDBY mode |
Explanation |
The broker is running in |
Action |
None. |
ETBM0745 | Broker running in PROXY mode |
Explanation |
The broker is running in |
Action |
None. |
ETBM0746 | Broker running in PSTORE-LOAD mode |
Explanation |
The broker is running in
|
Action |
None. |
ETBM0747 | Broker running in PSTORE-UNLOAD mode |
Explanation |
The broker is running in
|
Action |
None. |
ETBM0749 | Takeover sequence finished successfully |
Explanation |
The Standby Broker successfully performed the takeover sequence. It will
change to |
Action |
None. |
ETBM0750 | Broker ready for communications |
Explanation |
Broker is ready. |
Action |
None. |
ETBM0753 | Check status of partner Broker |
Explanation |
Standby Broker will check the status of the Standard Broker. |
Action |
None. |
ETBM0754 | Partner Broker is alive |
Explanation |
Standby Broker was checking the status of the Standard Broker. The Standard Broker responded to Standby Broker's request. Standard Broker is up and running. |
Action |
None. |
ETBM0757 | Takeover sequence started |
Explanation |
The Standby Broker is starting the takeover sequence to restore the persistent store data of the Standard Broker in its own address space. |
Action |
None. |
ETBM0758 | Takeover sequence stopped |
Explanation |
The Standby Broker is stopping the takeover sequence. |
Action |
None. |
ETBM0804 | TRACE-LEVEL changed |
Explanation |
The value of attribute |
Action |
None. |
ETBM0805 | TRAP-ERROR changed |
Explanation |
The value of attribute |
Action |
None. |