Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Using Messages With Identifiers : MN: osMon

MN: osMon
S6BMN000E
Out of memory
osMon
A request by a process for storage failed because all the virtual memory is in use.
Either run fewer processes on your system or add memory.
S6BMN001I
Unable to open the mon.prm file '%'
osMon
The attempt to open the mon.prm parameter file failed.
Check the operating system error code to determine the reason for this failure. Note: Use of the mon.prm is optional.
S6BMN002I
Unable to open the ee.prm file '%'
osMon
The attempt to open the ee.prm parameter file failed.
Check the operating system error code to determine the reason for this failure. Note: Use of the ee.prm is optional.
S6BMN004E
An invalid message type was received from an osee. It is ignored
osMon
The osMon process received an unrecognized message type from a child osee process.
If this message persists, contact TIBCO Support.
S6BMN005E
A pipe read failed with error '%'
osMon
A read on a named pipe (or FIFO) failed.
Examine operating system supplied error codes to determine reason for the failure.
S6BMN006L
osMon shutdown due to a CLOSE request
osMon
The osMon process shut down because it received a CLOSE request from another osMon process.
No action is required.
S6BMN007E
Write on named pipe % failed
osMon
A write on a named pipe (or FIFO) failed.
Examine operating system supplied error codes to determine the reason for the failure.
S6BMN008E
System operation failed, '%'
osMon
The specified operating system operation failed.
Check the operating system error number provided with the message. It should indicate the reason for the failure.
S6BMN009E
Invalid data received on connection
osMon
An error was discovered in the data received from an inter-process communication connection.
Contact TIBCO Support.
S6BMN010L
Session (%) stopped with exit code (%) on EE [%]:%
osMon
Object Service Broker session stopped with specified exit code.
No action is required. If the exit code is more than 128, the session abended. Check exit code documentation in order to determine what the exit code signifies.
S6BMN011L
Session (%) started on EE [%]:%
osMon
The Object Service Broker session started on the specified Execution Environment.
No action is required.
S6BMN012E
Invalid session start notification received from EE [%]:%
osMon
When a session is started by an osMon, it sends the start request to a child osee process. After the child osee process spawns the thread for the session, it should notify the osMon process that the session has started. This message is generated when the osMon process receives a notification on a session that it has no record of initiating.
Recycle your osMon process. If this message persists, contact TIBCO Support.
S6BMN013E
Invalid session stop notification received from EE [%]:%
osMon
When a session initiated by an osMon process ends, the child osee process sends the parent osMon a notification. This message is generated if the osMon process receives notification on a session for which it has no record.
Recycle your osMon process. If this message persists, contact TIBCO Support.
S6BMN014W
EENAME [%] was not found in ee.prm. Defaults used
osMon
An attempt was made to start a session with the session parameter EENAME set to a value that is not assigned to any NAME parameter in the ee.prm file.
If your intention is to use the EENAME parameter to access a set of Execution Environment parameter settings in the ee.prm file, then add those settings, preceded by "NAME = <your EENAME value>".
S6BMN015L
osMon shutdown due to a STOP request
osMon
An osMon process shut down upon receipt of a STOP request from another osMon process.
No action is required.
S6BMN016L
osMon shutdown due to a STOPALL request
osMon
An osMon process shut down upon receipt of a STOPALL request from another osMon process.
No action is required.
S6BMN017L
Terminating due to signal %
osMon
An osMon process terminated upon receiving the specified signal.
No action is required.
S6BMN018L
Terminating on request
osMon
An osMon process terminated because it received a request to do so.
No action is required.
S6BMN019E
Terminating due to error
osMon
An osMon process terminated due to an error.
If messages that precede this message do not provide sufficient information to determine the cause of this failure, contact TIBCO Support.
S6BMN020L
Logon from %:%, user=%, terminal=%
osMon
This message is written to the log whenever a connection is established between an ActiveX Adapter client and an osee via an osMon process.
No action is required.
S6BMN021E
Invalid data received on connection from %:%
osMon
An invalid request type was received by an osMon process from the specified client machine on the specified port number.
If messages that precede this message do not provide sufficient information to determine the cause of this failure, contact TIBCO Support.
S6BMN022E
Unable to connect to osMon at port %, monitor may not be running
osMon
An attempt to make a socket connection to an osMon process listening on the specified port failed.
Check to see if the osMon process in question is running. Otherwise, contact your system administrator. This is likely a communications problem.
S6BMN023L
Connection to port % was rejected
osMon
An attempt to establish a connection by an ActiveX Adapter client failed.
If messages that precede this message do not provide sufficient information to determine the cause of this failure, contact TIBCO Support.
S6BMN024L
Stop request sent to osMon with pid=%
osMon
This message is written to an osMon log whenever an osMon process sends a request to another osMon process to stop executing.
No action required.
S6BMN025E
Unable to send request
osMon
This message is sent to an osMon log if the corresponding process failed to execute a request.
If messages that precede this message do not provide sufficient information to determine the cause of this failure, contact TIBCO Support.
S6BMN026L
CLOSE request sent to osMon with pid=%
osMon
A CLOSE request was sent to the osMon process whose process Id is specified in the message.
No action is required.
S6BMN027I
Could not find DEFAULT_MON_NAME system variable
osMon
The osMon process is unable to load the DEFAULT_MON_NAME system variable.
Use the osconfig utility to change the value of the DEFAULT_MON_NAME parameter.
S6BMN028L
Session startup on PID=% completed
osMon
This message is written to an osMon log whenever the corresponding process successfully spawns the binary with the specified process ID.
No action required.
S6BMN029E
Port % is in use, osMon may already be running
osMon
An attempt was made to start an osMon process with a MONPORT parameter equal to another osMon process that is running on the same machine.
Start the osMon process with a unique MONPORT value with respect to the given machine.
S6BMN030L
osMon at port % has been stopped
osMon
This message is written to an osMon log whenever the corresponding osMon process successfully stops another osMon process.
No action required.
S6BMN031E
Unable to stop osMon at port %, attempting to kill process
osMon
If a request is made of an osMon to stop another osMon process, it first attempts to contact the other osMon process and bring it down in a graceful manner. If this fails, this message is written to the log and an attempt is made to kill the other osMon process.
Check the operating system error number provided with the message. It should indicate the reason for the failure.
S6BMN032I
The DEFAULT_MON_NAME system variable (%) must be between 1 and 32 characters long
osMon
The DEFAULT_MON_NAME system variable must be at least 1 character and at most 32 characters long.
Use the osconfig utility to change the value of the DEFAULT_MON_NAME variable.
S6BMN033L
Log file % was deleted
osMon
The specified log file is deleted. Log files are automatically deleted when they are sufficiently old. See the documentation for details on the osMon DELETELOG parameter.
No action is required.
S6BMN034E
Missing NAME parameter at line % in file %. Parameter assignment sets must begin with a NAME assignment
osMon
Parameter files consist of one or more parameter assignment sets. Each set must begin with a NAME assignment.
Add a NAME assignment to the specified parameter file on the specified line.
S6BMN035L
Parameter reload request sent to osMon with pid=%
osMon
The osMon with the given process ID was sent the request to reload the Execution Environment and session parameters.
No action is required.
S6BMN036E
Session startup failed
osMon
The attempt by osMon to start a session failed.
Check preceding messages in the osMon log for the failure.
S6BMN037W
Error occurred in idle shutdown thread
osMon
An osMon process allocates a thread to keep track of how long each osee has been idle. This thread experienced an error.
If the message repeats, assume the osMon is in an undefined state, and should be brought down as soon as possible.
S6BMN038E
osee abended. PID=% EE [%]:% Exit code %
osMon
The specified osee process abended with the specified exit code.
Check the osee log file to determine the reason for the abend.
S6BMN039E
osMon abended due to exception thrown at %:%
osMon
The Object Service Broker Monitor abended due to an internal (unexpected) exception.
If messages that precede this message do not provide sufficient information to determine the cause of this failure, contact TIBCO Support.
S6BMN040E
osMon abended
osMon
The Object Service Broker Monitor abended.
If messages that precede this message do not provide sufficient information to determine the cause of this failure, contact TIBCO Support.
S6BMN041E
Session (%) abended with exit code (%) on EE [%]:%
osMon
The specified session abended with the specified exit code.
Check the session log and the osee log files to determine the reason for the abend.
S6BMN043E
Value of STOPEE parameter (%) must be either pid or eename:instance
osMon
The value of the STOPEE parameter must be either a process ID (i.e., a number) or an Execution Environment NAME immediately followed by a colon that is immediately followed by an Execution Environment INSTANCE number.
Rerun the osMon process with the correct syntax for the STOPEE parameter.
S6BMN044E
Value of STOPSESS parameter (%) must be either pid:tid or eename:instance:instance
osMon
The value of the STOPSESS parameter must be either a processId:threadId (i.e., number:number) or an EENAME:Execution Environment instance number:Session instance number.
Rerun the osMon process with the correct syntax for the STOPSESS parameter.
S6BMN045L
STOPSESS request received for session (%)
osMon
The osMon process received a STOPSESS request for the specified session.
No action is necessary.
S6BMN046L
STOPEE request received for EE (%)
osMon
The osMon process received a STOPEE request for the specified Execution Environment.
No action is necessary.
S6BMN047L
CLOSEEE request received for EE (%)
osMon
The osMon process received a CLOSEEE request for the specified Execution Environment.
No action is necessary.
S6BMN050E
Failed to create main thread
osMon
An attempt by the service to create the main thread failed.
Check the operating system error number provided with the message. It should indicate the reason for the failure.
S6BMN051E
Failed to connect main thread to service control dispatcher
osMon
An attempt to connect the main thread to the service control dispatcher failed.
Check the operating system error number provided with the message. It should indicate the reason for the failure.
S6BMN052E
Failed to create or open the semaphore for stopall requests
osMon
An attempt to create or open an interprocess semaphore used for STOPALL requests failed.
Previous error messages and operating system error codes written to the log should explain the reason for the failure.
S6BMN053E
Failed to open or post the semaphore for stopall requests
osMon
An attempt to open or post an interprocess semaphore used for STOPALL requests failed.
Previous error messages and operating system error codes written to the log should explain the reason for the failure.
S6BMN054E
Failed to create or start the thread for stopall requests
osMon
An attempt to create or start the thread that waits for STOPALL requests failed.
Previous error messages and operating system error codes written to the log should explain the reason for the failure.
S6BMN055E
Failed to create or start the delete log thread
osMon
An attempt to create or start the thread that deletes log files failed.
Previous error messages and operating system error codes written to the log should explain the reason for the failure.
S6BMN056E
Failed to create or start the thread that waits for osee terminations
osMon
An attempt to create or start the thread that waits for the termination of osee processes failed.
Previous error messages and operating system error codes written to the log should explain the reason for the failure.
S6BMN057E
Failed to create or start the thread that listens for osee messages
osMon
An attempt to create or start the thread that listens for messages from osee processes failed.
Previous error messages and operating system error codes written to the log should explain the reason for the failure.
S6BMN058E
Failed to create or start the thread that services TN3270 clients
osMon
An attempt to create or start the thread that services TN3270 clients failed.
Previous error messages and operating system error codes written to the log should explain the reason for the failure.
S6BMN059E
Failed to join with the thread that services TN3270 clients
osMon
An attempt to join with the thread that services TN3270 clients, that is, to wait for the termination of the thread, failed.
Previous error messages and operating system error codes written to the log should explain the reason for the failure.
S6BMN060E
Failed to create or start a thread to service a client connection
osMon
An attempt to create or start a thread to process a client connection failed.
Previous error messages and operating system error codes written to the log should explain the reason for the failure.
S6BMN061E
Failed to create or start a thread to shutdown idle osee processes
osMon
An attempt to create or start a thread to shutdown idle osee processes failed.
Previous error messages and operating system error codes written to the log should explain the reason for the failure.
S6BMN099E
The value specified for the osMon SERVERS parameter is not valid
osMon
The osMon SERVERS parameter value does not conform to the syntax "<number1> <session name1> <number2> <session name2> ... <numberN> <session nameN>".
Correct the SERVERS parameter value.
S6BMN100L
The % service was installed
osMon
The osMon service with the given name is successfully installed on the host.
No action is required.
S6BMN101L
The % service was removed
osMon
The osMon service with the given name is successfully removed from the host.
No action is required.
S6BMN102E
The % service could not be removed
osMon
An attempt to remove an osMon service failed.
Check the operating system error code. Retry to remove the service. If all else fails, reboot.
S6BMN103E
The control handler could not be installed
osMon
The attempt to register the osMon service with the system failed.
Retry to start the service. If that fails, reboot the system and retry. If that fails, contact TIBCO Support.
S6BMN104E
The initialization process failed
osMon
Failed to initialize the osMon service.
Retry. If that fails, reboot the system and retry. If that fails, contact TIBCO Support.
S6BMN105E
Failed to detach from the binding area
osMon
An osee process failed to detach from the shared memory area provided by the osMon process that spawned it.
Check to make sure the osMon process is still running. If messages that precede this message do not provide sufficient information to determine the cause of this failure, contact TIBCO Support.
S6BMN106W
The service received an unsupported request
osMon
The service received (and ignored) an unsupported request type.
No immediate action is required. However, if this message persists, contact TIBCO Support.
S6BMN107L
The service was stopped
osMon
The osMon service is successfully stopped.
No action is required.
S6BMN108L
The service was started
osMon
The osMon service started successfully.
No action is required.
S6BMN110W
The server name (%) in the osMon SERVERS parameter is not associated with a set of parameter assignments
osMon
The given gateway/server name is not associated with a set of parameter assignments in the session.prm file or in the Windows registry.
Change the gateway/server name or add an entry for this name to the session.prm file or to the Windows registry.
S6BMN111E
Could not release existing binding area, because the shared memory segment is in use
osMon
An osMon process failed to release a shared memory binding area because some process is attached to it.
Check the operating system error number provided with the message. It should indicate the reason for the failure.
S6BMN112E
OS would not permit release existing binding area
osMon
The operating system did not permit the osMon process to release a shared memory binding area.
Check the operating system error number provided with the message. It should indicate the reason for the failure.
S6BMN113E
Could not remove locks for shared binding area
osMon
An osMon process is unable to remove locks held on portions of a shared memory binding area.
The messages that precede this message should provide sufficient information to determine the cause of this failure. Check to see if the osee processes that were spawned by the osMon processes were brought down successfully.
S6BMN115I
Could not open defaults file %
osMon
At startup, osMon attempted to load startup parameters from the specified file.
Check the operating system error number provided with the message. It should indicate the reason for the failure. If you do not want to load startup parameters from the specified file, this message can be ignored.
S6BMN117L
osee shutdown. PID=% EE [%]:% Exit code %
osMon
This message is written to an osMon log every time an osee that was spawned by the corresponding osMon process is shut down.
If the exit code is nonzero, the osee did not shut down normally. Check the documentation of osee exit codes to determine the cause of the shutdown.
S6BMN120E
Error occurred when getting exit code
osMon
An error occurred when an osMon process attempted to get the exit code for one of the osee processes that it spawned.
If the operating system error code does not provide sufficient information to determine the cause of this failure, contact TIBCO Support.
S6BMN121E
Error occurred while waiting on child process
osMon
An error occurred while an osMon process was waiting to see if any of its child processes had terminated.
If the operating system error code does not provide sufficient information to determine the cause of this failure, contact TIBCO Support.
S6BMN122E
Line % in % is too long. It must be no more than % characters
osMon
The specified line in the specified configuration file is too long.
Edit the specified file, shortening the specified line to be no longer than the specified maximum length.
S6BMN123E
Unexpected token % occurred in % on line %
osMon
The specified token was found on the specified line in the specified file. It was not expected.
Edit the specified file.
S6BMN124E
Matching 'end' for server definition block missing from %, line %
osMon
Gateways/servers started by an osMon process have definition files where the startup parameters for the gateway/server are stored. The parameters for a given group of gateways/servers are listed inside a definition block within the definition file. The definition block should begin with a line of the form "begin <n>" (where <n> is the number of gateways/servers which will be started with the given parameters) and end with a line of the form "end". The ending line was not found in the specified definition file on the specified line.
Edit the specified definition line, adding the missing end line.
S6BMN125E
Server definition corresponding to session name % is missing non-blank server type
osMon
In the gateway/server definition file (which is read by the osMon process in order to run gateway/server processes), each gateway/server definition block is required to specify the type of gateway/server that is to be started. A block was processed that does not contain a gateway/server type.
Edit the specified file, adding the appropriate gateway/server type.
S6BMN126L
% started with pid=%. Executing server type %
osMon
This message is written to an osMon log file every time a corresponding osMon process starts a gateway/server process.
No action is required.
S6BMN127E
Logon Failed
osMon
The logon of an ActiveX Adapter client to an osee server failed.
If messages that precede this message do not provide sufficient information to determine the cause of this failure, contact TIBCO Support.
S6BMN128E
Attempt to start an osee timed out
osMon
An attempt to start an osee timed out. When an osee is started, the osMon waits CONNTIMEOUT seconds for the osee to connect to the ActiveX Adapter client. If it fails to do so, this message is written to the log and the connection to the client is closed.
Increase the value of your osMon CONNTIMEOUT parameter.
S6BMN129I
The osMon DOB parameter is empty
osMon
The Data Object Broker parameter to the osMon is an empty string.
When an osee is started, its Data Object Broker parameter defaults to the Data Object Broker parameter of the osMon that spawned it. Therefore, all osees spawned by the osMon whose Data Object Broker parameter is empty require their Data Object Broker parameter to be set to a valid Data Object Broker name. The osee Data Object Broker parameter can be set either from the ActiveX Adapter client or as an environment variable in a default file. Refer to the documentation on the osee for more information.
S6BMN130E
Create named pipe %
osMon
Creation of a named pipe (or FIFO) failed.
Examine the operating system error code in order to determine the reason for the failure.
S6BMN131E
Connect to named pipe %
osMon
An attempt to connect to a named pipe (or FIFO) failed.
Examine the operating system error code in order to determine the reason for the failure.
S6BMN132E
Set named pipe % property
osMon
An attempt to set a named pipe (or FIFO) property failed.
Examine the operating system error code in order to determine the reason for the failure.
S6BMN133E
Create Windows Event Object
osMon
An attempt to create a Windows Event Object failed.
Examine the operating system error code to determine the reason for the failure. The most common reason is lack of storage.
S6BMN134E
Disconnect from named pipe %
osMon
An attempt to disconnect from a named pipe (or FIFO) failed.
Examine the operating system error code to determine the reason for the failure.
S6BMN135E
State error on named pipe %
osMon
The named pipe has entered an invalid state.
If operating system error codes do not provide enough information to resolve the reason for this failure, contact TIBCO Support.
S6BMN136L
osee started. PID=% EE [%]:%
osMon
A child osee process was spawned with the given process ID, NAME, and INSTANCE number.
No action is required.
S6BMN137E
The maximum number of EE (%) that the osMon can execute has been reached
osMon
The MON parameter MAXEE determines how many osee processes an osMon process can spawn simultaneously. An attempt was made to exceed the limit.
Do either of the following:
Increase the Execution Environment MAXSESSION parameter, so that fewer osee processes can service the same number of sessions.
S6BMN138L
Remote CLI or Java CLI logon
osMon
A Remote CLI or a Java CLI client initiated a logon.
No action is required.
S6BMN139L
Remote CLI or Java CLI logon succeeded
osMon
A Remote CLI or a Java CLI logon completed successfully.
No action is required.
S6BMN140L
Remote CLI or Java CLI logon failed
osMon
A Remote CLI or a Java CLI logon failed.
Examine the accompanying log messages to determine the reason for the failure. The startup log may also provide pertinent information.
S6BMN142E
Invalid host name specified: %
osMon
The host name specified in the MONHOST parameter is invalid.
Determine the correct spelling of your host's name.
S6BMN143W
IP address (%) does not correspond to host name (%). Using IP address
osMon
Both the IP and the HOST Execution Environment parameters are set. However, the IP address corresponding to the DNS name is not the same as the IP Execution Environment parameter. Therefore the NAME value is ignored and the IP value is used.
No action is required unless you want the HOST Execution Environment parameter to be used. In this case, do not set the IP Execution Environment parameter.
S6BMN144I
No host name or IP specified. osMon will listen on all IP addresses
osMon
Neither the HOST nor the IP Execution Environment parameters are set Therefore, the osMon process listens on all IP addresses associated with the host it is running on.
No action is required unless you want the osMon process to listen exclusively on a particular IP address. If this is the case, you should set either the HOST or the IP Execution Environment parameter.
S6BMN145E
Remote CLI client or Java CLI client requested unsupported code page
osMon
A Remote CLI or a Java CLI application attempted to use an unsupported Remote CLI/Java CLI code page.
Make sure that the application uses supported code pages, and that the @NLS1 table is initialized as documented in the NLS manual.
S6BMN200E
Logon terminated at user's request
osMon
The user canceled the logon process.
No action is required.
S6BMN201E
Unsupported version of TN3270 terminal
osMon
osMon process cannot accept connections from this terminal.
Use either the IBM 3278 or the IBM 3279 terminal.
S6BMN202E
Unsupported TN3270 protocol
osMon
An error occurred during the TN3270 negotiation protocol.
No action is required.
S6BMN300E
Unable to open osMon NAME parameter lockfile '%'
osMon
An attempt to create or open a disk file failed. The disk file is used to ensure a NAME parameter is not in use by more than one osMon process. Likely causes are insufficient directory permissions or disk full conditions.
Check the operating system error number provided with the message. It should indicate the reason for the failure.
S6BMN301E
Unexpected file locking error during '%' command for osMon NAME parameter lockfile '%'
osMon
An attempt to get or set a file lock using the fcntl(2) system call failed. The file lock is used to ensure a NAME parameter is not in use by more than one osMon process.
Check the operating system error number provided with the message. It should indicate the reason for the failure.
S6BMN302E
Unexpected file mapping creation error for osMon NAME parameter lockfile '%'
osMon
An attempt to create or open a memory-mapped file failed. The memory-mapped file is used to ensure a NAME parameter is not in use by more than one osMon process.
Check the operating system error number provided with the message. It should indicate the reason for the failure.
S6BMN303E
Unexpected error mapping view of osMon NAME parameter lockfile '%'
osMon
An attempt to create a view of a memory-mapped file failed. The memory-mapped file is used to ensure a NAME parameter is not in use by more than one osMon process.
Check the operating system error number provided with the message. It should indicate the reason for the failure.
S6BMN304E
osMon NAME parameter '%' is in use by process ID %
osMon
An osMon NAME parameter may not be used by multiple osMon processes because it is used to uniquely identify Execution Environment resources.
Start osMon with a NAME parameter that is not in use. A new set of default parameter assignments may have to be added to the Object Service Broker monitor parameter source file.
S6BMN900E
Error occurred during an attempt to release resources
osMon
A failure occurred while the osMon was shutting down.
Restart the osMon process. If this message persists, contact TIBCO Support.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved