KOBC — KOBO messages
These messages are associated with the OMEGAMON enhanced 3270 user interface, which is part of the OMEGAMON Base component. By
default, trace and error logs are created in SYSPRINT. (An alternate log location may have been
specified, using standard JCL services.) Most of the messages are prefixed by a timestamp and thread
ID.
KOBC00000E Unable to locate an important internal control block. Contact IBM technical
support.
Explanation
The address space cannot continue to process because of an internal error that
resulted in the inability to find an internal control block.
System action
The address space terminates.
User response
Try one time to restart the address space. If the attempt fails, collect dump and
log information and contact IBM Software Support.
KOBC00001E Job or system level memory limit (MEMLIMIT) exceeded.
Explanation
z/OS has refused a request for virtual storage for this address space step. The
reason information returned by z/OS indicates that the request would have exceeded the MEMLIMIT
value for the step.
System action
The address space continues, but may not function correctly.
User response
Verify that MEMLIMIT=NOLIMIT is coded on the address space EXEC
statement within the started task or job JCL, or increase the step EXEC MEMLIMIT value. (See the
documentation for SYS1.PARMLIB member SMFPRMxx, or the z/OS JCL Reference for an
explanation of MEMLIMIT.)
KOBC00002E Error attempting key change. This step must be APF authorized.
Explanation
This program requires APF authorization.
System action
The address space is terminated.
User response
Ensure that all libraries concatenated as part of the STEPLIB DD (in the JCL) are
APF authorized.
KOBC00003E Must be APF authorized.
Explanation
This program requires APF authorization.
System action
The address space is terminated.
User response
Ensure that all libraries concatenated as part of the STEPLIB DD (in the JCL) are
APF authorized.
KOBC00004E Job or system level memory limit (MEMLIMIT) exceeded.
Explanation
z/OS has refused a request for virtual storage for this address space step. The
reason information returned by z/OS indicates that the request would have exceeded the MEMLIMIT
value for the step.
System action
The address space continues, but may not function correctly.
User response
Verify that MEMLIMIT=NOLIMIT is coded on the address space EXEC
statement within the started task or job JCL, or increase the step EXEC MEMLIMIT value. (See the
documentation for SYS1.PARMLIB member SMFPRMxx, or the z/OS JCL Reference for an
explanation of MEMLIMIT.)
KOBC00004I reserved for later use
KOBC00005I reserved for later use
KOBC00006E Unable to create recovery environment. Thread terminates.
Explanation
The thread management functions were unable to establish a recovery environment
during thread creation.
System action
The new thread is not created.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00007E Freeing of lock failed in kob_TCB_Thread_Base(), rc=return_code,
errno=error_number, rsnno=error_reason.
Explanation
The thread management functions were unable to free a lock during thread creation,
for the reasons indicated in the message.
System action
The new thread is not created.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00008E Sib-lock build failure in pthread_create(). rc=n,
errno=x, rsnno=y.
Explanation
The thread management functions were unable to build a lock during thread creation,
for the reasons indicated in the message.
System action
The new thread is not created.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00009E Sib-lock failure in pthread_create(). rc=n, errno=x,
rsnno=y.
Explanation
The thread management functions were unable to obtain a lock during thread creation,
for the reasons indicated in the message.
System action
The new thread is not created.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00010E Sib-unlock failure in pthread_create(). rc=n,
errno=x, rsnno=y.
Explanation
The thread management functions were unable to free a lock during thread creation,
for the reasons indicated in the message.
System action
The address space terminates.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00011E Sib-lock failure in pthread_detach(). rc=n, errno=x,
rsnno=y.
Explanation
The thread management functions were unable to free a lock during thread detach, for
the reasons indicated in the message.
System action
The thread terminates.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00012E Lock release failure in pthread_detach(). rc=n,
errno=x, rsnno=y.
Explanation
The thread management functions were unable to release locking resources during
thread detach, for the reasons indicated in the message.
System action
The thread terminates.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00013E Child not found in pthread_detach() of %016lX.
Explanation
The detachment of a created thread was requested, but the thread was found to be
already detached.
System action
The thread terminates.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00014E Sib-unlock failure in pthread_detach(). rc=n,
errno=x, rsnno=y.
Explanation
The thread management functions were unable to free a lock during thread
detach.
System action
The address space terminates.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00015E Lock build failure in pthread_create(). rc=return_code,
errno=error_number, rsnno=error_reason.
Explanation
The thread management functions were unable to build a lock during thread
create.
System action
The new thread is not created.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00016E Lock obtain failure in pthread_create(). rc=return_code,
errno=error_number, rsnno=error_reason.
Explanation
The thread management functions were unable to obtain a lock during thread
create.
System action
The thread terminates.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00017E Add2Sibling Chain failure in pthread_create(). rc=n,
errno=x, rsnno=y.
Explanation
The thread management functions were unable to update internal linkages to add a new
thread.
System action
The thread terminates.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00018E pthread_create() failure. rc=n, errno=error_code,
rsnno=error_reason.
Explanation
The thread management functions were unable to create a new thread.
System action
The thread terminates.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00019E lock cleanup failure in pthread_create(). rc=return_code,
errno=error_number, rsnno=error_reason.
Explanation
The thread management functions were unable to clean up a lock during thread
creation.
System action
The thread terminates.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00020E Sibling cleanup failure in pthread_create(). rc=n,
errno=x, rsnno=y.
Explanation
The thread management functions were unable to insert a sibling thread during thread
create.
System action
The thread terminates.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00021E Lock destroy failure in pthread_detach(). rc=n,
errno=x, rsnno=y.
Explanation
The thread management functions were unable to clean up a lock during thread
detach.
System action
The thread terminates.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00022E Child cleanup failed in pthread_detach(). rc=return_code,
errno=error_number, rsnno=error_reason.
Explanation
The thread management functions were unable to remove a sub-thread during thread
detach.
System action
The thread terminates.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00023E Unable to obtain thread end lock in pthread_join. rc=return_code,
errno=error_number, rsnno=error_reason
Explanation
An attempt to wait for completion of another thread failed.
System action
The thread terminates.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00024E pthread_detach() failed in pthread_join(). rc=return_code,
errno=error_number, rsnno=error_reason
Explanation
An attempt to release thread resources after waiting for a thread to complete
failed.
System action
The thread terminates.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBC00025E Unable to free thread end lock in pthread_join. rc=return_code,
errno=error_number, rsnno=error_reason
Explanation
The thread management functions were unable to clean up a lock after waiting for a
thread to complete.
System action
The thread terminates.
User response
Collect dump, trace, and system log data. Report the problem to IBM Software
Support.
KOBCM0001E Create thread for kobcmsrv failed, pthreadstatusI = x
Explanation
The conduit manager attempt to create a query
server thread, kobcmsrv, has failed with return code x.
System action
No queries can be processed.
User response
Restart the enhanced 3270 user interface address space. If
the problem persists, call IBM Software Support.
KOBCM0001I nnnnnnnn
uuuuuuuu. Compiled on x at y.
Explanation
The running copy of module nnnnnnnn at Program Temporary Fix (PTF) level
uuuuuuuu was compiled on date x and time y.
User response
Note this PTF for any questions related to query processing within the OMEGAMON
Enhanced 3270 User Interface.
KOBCM0002E Create thread for kobcmdmt failed, pthreadstatusI =n
Explanation
The conduit manager attempt to create a discovery
manager thread, kobcmdmt, has failed with return code n.
System action
No queries can be processed.
User response
Restart the enhanced 3270 user interface address space. If
the problem persists, call IBM Software Support.
KOBCM0003E Create thread for kobcmdpt failed, pthreadstatusI = return_code
Explanation
The conduit manager attempt to create a discovery
manager thread, kobcmdpt, has failed with return code return_code.
System action
No queries can be processed.
User response
Restart the enhanced 3270 user interface address space. If
the problem persists, call IBM Software Support.
KOBCM0004E Create thread for kobcmsrv failed, pthreadstatusI = return_code
Explanation
The conduit manager attempt to create a query
server thread, kobcmsrv, has failed with return code return_code.
System action
No queries can be processed.
User response
Restart the enhanced 3270 user interface address space. If
the problem persists, call IBM Software Support.
KOBCM0005E Create thread for kobcmmnt failed, pthreadstatusI = return
code.
Explanation
The Conduit Manager attempt to create a maintenance processing thread, kobcmmnt, has
failed with return code return code.
System action
No maintenance can be performed.
User response
Re-start the Tivoli OMEGAMON address space. If the problem persists call IBM
support.
KOBCM0006E Create thread for kobcmndt failed, pthreadstatusI =
return_code
+ extended diagnostics
context.
Explanation
The Conduit Manager attempt to create a maintenance worker/ processing thread,
kobcmndt, has failed with return code = return_code.
System action
No maintenance can be performed.
User response
Re-start the Tivoli OMEGAMON address space. If the problem persists call IBM
support.
KOBCM0010E Conduit manager Recv Error, rc = return_code, retry = n, microseconds =
y
+extended diagnostics error and context
Explanation
An IP socket recv() function call ended badly. The return code is
return_code, the elapsed duration of the receive attempt is y. The errno and
errno2 values in the extended data can help clarify what receive error occurred. If the errno is
retry-able, like EINTR, EWOULDBLOCK, or EAGAIN, then retry = n gives the count of
retries done. Many of the conduit manager error messages are followed by extended diagnostic
information. This information is intended to help users determine the context of the failing query, where:
- errno and errno2
- Are further error codes beyond the return code from many system services. When present, the
additional codes can help isolate the exact nature of the problem. Since the conduit manager (CM)
can be in simultaneous conversation with several data retrieval agents (DRAs) associated with several different hub environments, the following data will help identify
just which query to which DRA has encountered a problem.
- Target Hub
- Is the hub environment of the DRA involved in this query.
- DRA IP
- Is the IP address of the LPAR where the DRA is running.
- DRA jobname
- Is the name of the address space where the DRA used is running.
- DRA Port
- Is the port number this DRA is listening to.
- Sequence #
- Is a unique identifier for this query transaction.
- Query
- Is the text string of the query in question.
System action
No further results are processed for this query.
User response
Verify that the partner data retrieval agent (DRA)
is okay by inspecting its RKLVLOG messages. If the errno value is EWOULDBLOCK, it is likely that the
query timed out. Compare the microseconds value to the value found in the most recent log message
KOBCM0066I, KOBCM0068I, KOBCM0081I, or KOBCM0083I. If the microseconds in this message are slightly
longer than the timeout value, in seconds, found in the most recent preceding message, then the
query took too long to process. If the microseconds values are similar to that found in the most
recent KOBCM0066I or KOBCM0068I message, you can try increasing the timeout value using command
"/F tom,SO_TIMEOUT x" to change the
timeout value, where x is the timeout in seconds and tom is
the name of the enhanced 3270 address space. You can try increasing the timeout value to see if that
resolves the problem.
If the microseconds values are similar to that found in the most recent
KOBCM0081I or KOBCM0083I, you can try increasing the timeout value using command "/F
tom,DIS_TIMEOUT x" to change the timeout value, where x is the
timeout in seconds, tom is the name of the enhanced 3270 address space. Retry the
query.
If the problem persists, restarting either the enhanced 3270 user interface or the
DRA address space might help.
KOBCM0011E Conduit Mgr Recv Error - Bad Length, is x should be y
+extended diagnostics error and context
Explanation
The enhanced 3270 user interface address space is expecting
to receive x bytes, but instead received y bytes.
System action
No further results are processed for this query.
User response
Try the query again. If the problem persists, look for connection problems with the
data retrieval agent (DRA) identified in the extended
diagnostics.
KOBCM0012E read_response(), recvbuf storage not obtained.
+ size requested is x
+extended diagnostics error and context
Explanation
Buffer storage to receive result rows for this query could not be obtained. The
storage size requested is x
System action
No further results are processed for this query.
User response
Retry the query. If the problem persists, recycle the enhanced 3270 user interface address space and, if needed, the data retrieval agent address space. Call IBM Software Support if recycling
does not resolve the problem.
KOBCM0013E Block Length Error, tries = n
+ should be x , but is
y
+extended diagnostics error and context
Explanation
The received block length, y, does not match the expected block length,
x. It is likely that a connection failure occurred. If the failure type in the extended
diagnostics was retryable, such as EINTR, EAGAIN, or EWOULDBLOCK, then tries = n
indicates how many retries were made before accepting the error.
System action
No further results are processed for this query.
User response
Retry the query. If the problem persists, use the extended context data to
determine the data retrieval agent (DRA) involved in the
conversation. Look for further error indications from this DRA in its RKLVLOG.
KOBCM0014E Length Error
+ Block Length is x
+ Block Length should be greater than record length which is y
+extended diagnostics error and context
Explanation
The received block length is x. This is less than the expected size
(y) of the record length contained in this block. This should never occur.
System action
No further results are processed for this query.
User response
Retry the query. If the problem persists, recycle the enhanced 3270 user interface address space and, if needed, the data retrieval agent address space. If recycling fails to resolve the problem,
call IBM Software Support.
KOBCM0015E Total of record lengths exceed the block length. Block Length is x Total record
lengths are y
+extended diagnostics error and context
Explanation
The sum of the received record lengths exceeds the block size. This should not
occur.
System action
No further results are processed for this query.
User response
Retry the query. If the problem persists, recycle the enhanced 3270 user interface address space and, if needed, the data retrieval agent address space. If recycling fails to resolve the problem,
call IBM Software Support.
KOBCM0016E Unknown Rec-Type in response. Record Type received is protocol_type
+extended diagnostics error and context
Explanation
The record type found in the received data (protocol_type) is not recognized
as a valid record type.
System action
No further results are processed for this query.
User response
Inspect the IP address and port number in the extended diagnostic data and verify
this is a valid LPAR connection.
KOBCM0017E KOBCM17E: Error condition in DRA. Failed Function is function_name
+extended diagnostics error and context
Explanation
The data retrieval agent (DRA) involved found
something wrong with the query involved in this transaction. The specific SQL1 operation that failed
is function_name.
System action
No further results are processed for this query.
User response
Inspect the query text looking for SQL syntax errors. If this is a user-supplied
query, ensure that all the column names are spelled correctly. Often the RKLVLOG of the Tivoli Enterprise Monitoring Server managing the DRA involved will have helpful diagnostic
information. Repair the query and retry the operation.
KOBCM0018E KOBGW_RR_CM_EndOfRows failed, rc = x
+extended diagnostics error and context
Explanation
The conduit manager component has completed
sending rows for a request and is signaling completion to the next component in the path, the
request router The request router is responding with an error condition.
System action
No further results are processed for this query.
User response
If the problem persists, call IBM Software Support.
KOBCM0019E KOBGW_RR_CM_PutDataRow rc = x
+Dump of failing row
+extended diagnostics error and context
Explanation
The conduit manager component encountered an
error trying to pass a query result row through the request router on its way to the 3270 screen.
System action
No further results are processed for this query.
User response
Retry the query. If the problem persists, call IBM Software
Support.
KOBCM0020W KOBCM20W: Invalid SQL request received & ignored.
+Dump of request
header
Explanation
The conduit manager received a malformed SQL
query header. The “dump” documents the request header involved.
System action
The query is bypassed.
User response
If the problem persists, call IBM Software Support. Include the full content of
this message in your report.
KOBCM0021E Failure getting registered DRA. rc = error_code rs = error_reason
Explanation
The conduit manager attempted to discover the
data retrieval agents registered in this Sysplex.
System action
No queries will be processed.
User response
Use the appropriate version of the z/OS manual MVS Programming: Workload
Management Services (SA22-7619). Locate the reference section for the IWMSRSRS macro and compare
the rc and rs values in this message with the return and reason codes documented for this macro. If
no reasonable resolution is apparent, contact IBM Software Support.
KOBCM0022W Too many hubs. Hub hub_name ignored. More than nn hubs managed.
Explanation
While discovering data retrieval agents (DRAs), the
conduit manager found more hubs active than it can manage. The
current limit for hub management is xx. Hub name hub_name and
all of its DRAs are ignored.
System action
No new hubs are added to the managed system list.
User response
No action is required unless a vital Tivoli Enterprise Monitoring Server hub is being ignored. If an important hub is being
ignored, consider reducing the number of less important hubs in your environment.
KOBCM0023E KOBGW_RR_CM_GetAnyRequest failed with rc = return_code
+extended diagnostics context
Explanation
The conduit manager received a failure notice while waiting for a new query request.
The return code is return_code.
System action
No more requests are processed.
User response
Restart the enhanced 3270 user interface address space as
soon as possible. If the problem persists, call IBM Software Support.
KOBCM0024I Conduit manager retry with alternate DRA
+extended diagnostics error
and context
Explanation
A failed query is being retried through an alternate data retrieval agent (DRA). The extended diagnostics has a sequence number
specifying the exact query instance being retried, the SQL text, and information about the new DRA
path selected.
System action
The query is resubmitted through a different DRA.
User response
Look for a prior KOBCM0010E message with the same sequence number. Note the DRA
used in this failed transaction. If this DRA is frequently seen in failure messages, please recycle
the associated Tivoli Enterprise Monitoring Server or OMEGAMON monitoring agent
address space at your earliest convenience.
KOBCM0025W DRA candidate nn has invalid . . .
Explanation
The e3270 address space found a Data Retrieval Agent candidate that had invalid
registration information. The variable portion of this message specifies one or more problems noted
with the registration:
version number of vvvvvvvv. Must be string between 6 and 8 characters.
address space name of nnnnnnnn. Must be string between 1 and 8 characters.
DRA IP address of cccccccc. Must be string between 14 and 22 characters, starting with
::ffff:
DRA port number of %d. Must be number between 1 and 65535.
Sysplex name of %s. Must be string between 1 and 8 characters.
SMF ID of %s. Must be string between 1 and 4 characters.
Space Token, %s. Must be string of form xxxxxxxx_xxxxxxxx
Hub IP address of %s. Must be string between 14 and 22 characters, starting with
::ffff:
Hub port number of %d. Must be number between 1 and 65535.
Hub origin node of %s. Must be string between 1 and 32 characters.
System action
The candidate DRA is not included in the e3270 address space registry. If this is
the only candidate for a hub, then the hub will not be accessible from the e3270 address
space.
User response
Call IBM Software Support.
KOBCM0026W Dropped DRA count is xx it should be yy.
Explanation
The count of DRAs after eliminating troubled DRAs is found to be xx. Instead,
the count should have been yy.
System action
The e3270 address space should work properly as long as there are 1 or more DRAs
available for the hub.
User response
If this problem persists after the next restart of the e3270 address space, call
IBM Software Support.
KOBCM0030E socket create failed, rc = return_code
+extended diagnostics error and context
Explanation
The conduit manager attempted to allocate a
communication socket for use with thedata retrieval agent. The
attempt failed with return code return_code.
System action
This query is bypassed.
User response
Retry the associated query found in the extended diagnostics. If the problem
persists, call IBM Software Support.
KOBCM0031E setsockopt failed, rc = return_code
+extended diagnostics error and context
Explanation
The conduit manager is attempting to set
communication options for this socket conversation with the data retrieval agent. The attempt failed with return code
return_code.
System action
This query is bypassed.
User response
Retry the associated query found in the extended diagnostics. If the problem
persists, call IBM Software Support.
KOBCM0032E invalid ip or port
+ip = x port = y
+extended diagnostics error and context
Explanation
The conduit manager has detected that either the
IP or port values for the data retrieval agent are incorrect. The
incorrect IP or port number is indicated.
System action
This query is bypassed.
User response
Retry the associated query found in the extended diagnostics. If the problem
persists, call IBM Software Support.
KOBCM0034E BLDgwDataRq failed, rc = return_code
+extended diagnostics error and context
Explanation
The conduit manager has an internal error
constructing the query for the data retrieval agent. Return code is
return_code.
System action
This query is bypassed.
User response
Retry the associated query found in the extended diagnostics. If the problem
persists, call IBM Software Support.
KOBCM0035E send block failed, rc = return_code, microseconds =
mmm
+extended diagnostics error and context
Explanation
The conduit manager send of the query to the
data retrieval agent failed. Return code was return_code. The
elapsed time for the connect attempt, in microseconds, is mmm.
System action
This query is bypassed.
User response
If the errno value is EWOULDBLOCK, it is likely the query timed out. Compare the
microseconds value to the value found in log message KOBCM0066I. If the microseconds in this message
are slightly longer than the time-out value, in seconds, found in KOBCM0066I, then the query took
too long to process. Try increasing the time-out value to see if that resolves the problem. Use the
command "/F tom,SO_TIMEOUT x" to change
the time-out value, where x is the time out in microseconds and
tom is the enhanced 3270 address space name. Retry the associated query found in
the extended diagnostics. If the problem persists, call IBM Software Support.
KOBCM0036E EOD send block failed, rc = return_code
+extended diagnostics error and context
Explanation
The conduit manager send of end-of-query
indication to the data retrieval agent failed. Return code was
return_code.
System action
This query is bypassed.
User response
Retry the associated query found in the extended diagnostics. If problem persists,
call IBM Software Support.
KOBCM0040E Discovery manager thread can not create refresh queue, kob_init_queue_header. rc
=return_code
+extended diagnostics error and context
Explanation
The conduit manager discovery and refresh of data
retrieval agents, hubs, managed system names and managed system lists can not proceed.
System action
The local registry is not initialized.
User response
Try restarting this address space. If problem persists, call IBM Software
Support.
KOBCM0041E Maintenance manager thread can not create Maintenance refresh queue, kob_init_queue_header,
rc = return_code.
Explanation
The Conduit Manager Maintenance Thread can not proceed.
System action
No Maintenance requests can be created/submitted to the worker thread to do
maintenance refresh.
User response
Re-start the Tivoli OMEGAMON address space. If the problem persists call IBM
support.
KOBCM0041W Add discovery refresh request failed. kob_add_to_queue error. rc
=return_code
+extended diagnostics error and context
Explanation
An attempt to request a periodic refresh of data retrieval agents, hubs, managed
system names and managed system lists failed.
System action
The local registry is updated with any recent changes.
User response
If this is a recurring problem, call IBM Software Support.
KOBCM0042E Wait for periodic refresh failed. rc =return_code
+extended diagnostics error and context
Explanation
An attempt to wait for the configured time period between discovery refresh cycles
has failed. Note: This is an extremely unlikely error condition. Basically, it indicates that normal
timer services within the LPAR have failed, so the configured registry refresh time period cannot be
honored.
System action
To prevent looping, the discovery refresh thread suspends periodic refresh and
waits for an operator reply to message KOBCM0043I.
User response
Try replying GO to the associated KOBCM0043I write to
operator with reply (WTOR) message found in the LPAR's SYSLOG. If another KOBCM0043I WTOR appears
immediately, then call IBM Software Support.
KOBCM0042W Add Maintenance refresh request from kobcmmnt failed. kob_add_to_queue error rc =
return_code
+ extended diagnostics
context.
Explanation
An attempt to request a maintenance refresh failed from the kobcmmnt Maintenance
Manager Thread.
System action
No maintenance can be performed.
User response
If this is a reoccurring problem, call IBM support.
KOBCM0043I Discovery refresh wait failed. Simulate timed wait reply GO or END.
Explanation
Write to operator with reply (WTOR) message associated with KOBCM0042E log message.
System action
Discovery refresh thread waits for operator reply.
User response
Try replying GO to this write to operator with reply (WTOR)
message. If another KOBCM0043I WTOR appears immediately, then call IBM Software
Support.
KOBCM0043W Add Maintenance refresh request from myCommandRoutine failed. kob_add_to_queue error rc =
return_code
+ extended diagnostics
context.
Explanation
An attempt to request a periodic refresh of ODI/Thresholds failed.
System action
Most recent ODI/Thresholds refresh request have not been added.
User response
If this is a reoccurring problem, call IBM support.
KOBCM0044W Discovery refresh thread failed to release the refresh queue properly. kob_destroy_queue rc
= return_code
+extended diagnostics error and
context
Explanation
Discovery refresh thread is terminating. Its attempt to release storage associated
with the refresh queue may be orphaned.
System action
Thread termination proceeds.
User response
If termination of the discovery refresh thread is unexpected, call IBM Software
Support.
KOBCM0045E Wait for Maintenance refresh failed. sleep rc = return code
+ extended diagnostics context.
Explanation
An attempt to wait for the configured time period between maintenance refresh cycles
has failed.
System action
To prevent looping, the maintenance refresh thread suspends periodic refresh and
waits for an operator reply to message KOBCM0045I.
User response
Try replying GO to the associated KOBCM0045I write to operator
with reply (WTOR) message found in LPAR's SYSLOG. If another KOBCM0045I WTOR message appears
immediately, then call IBM support.
KOBCM0045I Maintenance refresh wait failed. Simulate timed wait reply GO or END.
Explanation
Write to operator with reply (WTOR) message associated with KOBCM0045E log
message.
System action
Discovery refresh thread waits for operator reply.
User response
Try replying GO to this write to operator with reply (WTOR)
message. If another KOBCM0045I WTOR message appears immediately, then call IBM
support.
KOBCM0045W RC = return code in DRA = Data_Retrieval_Agent_name
IP = IP_address, Hub = hub_monitoring_server_name
(application_name .table_name)
Explanation
Message KOBCM0045W indicates that the Data Retrieval Agent (KOBAGENT) was contacted from the Tivoli®
OMEGAMON® Manager, but an error was detected in the Data
Retrieval Agent. This error indicates that a repeat attempt might be successful.
The following return codes are possible:
- RC=5
- The Hub or Remote Tivoli Enterprise Monitoring Server
is not yet available.
- RC=79
- When attempting to delete a table row, the row was not found.
- RC=80
- When attempting to insert a table row, a duplicate row was found.
- RC=155
- A hub or remote monitoring server could not be contacted.
- RC=202
- A TEMS does not contain application support for a particular column.
- RC=209
- A monitoring server does not contain application support for a particular application and
table.
- RC=3000
- Historical data does not exist for the requested table.
- RC=9036
- The hub monitoring server is not yet available.
- RC=9037
- SQL SELECT string is too long, rejected by the DRA
- RC=9038
- SQL query contains invalid column name, rejected by the DRA
- RC=9999
- The hub monitoring server is not yet available.
- RC=67109015
- A hub or remote monitoring server could not be contacted.
- RC=67109019
- A Hub or Remote TEMS could not be contacted.
- RC=67109066
- A TEMS does not contain application support for a particular column.
- RC=67109073
- A monitoring server does not contain application support for a particular application and
table.
If this message occurs frequently, check the RKLVLOG for the Data Retrieval Agent that is listed,
which might contain more details. If the message indicates that a remote or hub monitoring server is
not yet available, confirm that the monitoring server is running and is not out of storage or
abending.
System action
The query, insertion or deletion fails and any enhanced 3270 user interface workspace that needs
the results might be missing data.
System programmer response
Check the message details for the particular return code (RC) and take the appropriate action.
For example, if the message return code indicates that the monitoring server is not available, check
the system to confirm that the monitoring server is running correctly. If the return codes indicate
that application support files are missing, apply application support (also known as seeding) to the
necessary remote and hub monitoring servers.
KOBCM0046I Refresh Hubs(+aaa,-ddd,ttt)
DRAs(+aaa,-ddd,ttt)
MSNs(+aaa,-ddd,ttt)
MSLs(+aaa,-ddd,ttt), n
seconds
Explanation
A Registry Refresh occurred. As a result of the Registry Refresh, there is a change in the number
of hub monitoring servers (Hubs), Data Retrieval Agents (DRAs), Managed System Names (MSNs), or
Managed System Lists (MSLs) known to this Tivoli
OMEGAMON Manager. The values within parentheses indicate
the number of added items (aaa), the number of deleted items
(ddd), and the total number of items (ttt). The time taken to
perform the Registry Refresh is reported in seconds (n).
System programmer response
None.
KOBCM0047W Connect failed, Err = error code Rsn = reason_code,
nnn seconds Failed for DRA = Data_Retrieval_Agent_name IP =
IP_address, Hub = hub_monitoring_server_name
(application_name .table_name)
Explanation
Message KOBCM0047W indicates that a TCP/IP connection attempt failed between this Tivoli
OMEGAMON Manager and a data retrieval agent (DRA). The
error and reason codes are displayed in the Err=nnn and
Rsn=nnn fields.
The following examples show some typical return values:
- Err=0 Rsn=0x00000000
- The destination rejected the connection.
- Err=1127 Rsn=0x0000020A
- The connection attempt timed out.
If Err=0 Rsn=0x00000000 is returned, the DRA might either be not running or not reachable due to
a TCP/IP firewall between the Tivoli
OMEGAMON Manager and the DRA.
System action
No results from the failed query are available, so any enhanced 3270 user interface workspace
that needs the results might be missing data.
System programmer response
For code Err=0 with Rsn=0x00000000, check that the named DRA is both running and not in an
abending address space. Check that any firewall between this address space and the DRA address space
is configured to allow TCP traffic for the port number in use by the DRA. You can control the port
number of the DRA with the POOL:nnnnn modifier in the KDE_TRANSPORT environmental variable,
contained in the KxxENV file for the DRA address space.
KOBCM0048I Retry with DRA = Data_Retrieval_Agent_name IP =
IP_address, Hub = hub_monitoring_server_name
(application_name.table_name)
Explanation
Message KOBCM0048I indicates that an earlier failure occurred between the Tivoli
OMEGAMON Manager and a Data Retrieval Agent (DRA) and
that same operation will be tried again, with a different DRA. See the earlier message for details
about the failure.
System action
The query is being tried again, with a different DRA.
System programmer response
None.
KOBCM0049W Receive failed, Err = error code Rsn = reason_code,
nnn seconds, retry = n Failed for DRA =
Data_Retrieval_Agent_name IP = IP_address, Hub =
hub_monitoring_server_name (application_name
.table_name)
Explanation
Message KOBCM0049W indicates that a TCP/IP 'receive' failed between this Tivoli
OMEGAMON Manager and a Data Retrieval Agent (DRA). The
error and reason codes are displayed in the Err = nnn and Rsn =
nnn fields. Typical values that you might see include: Err=1102 Rsn=0x76650211
The receive attempt 'timed out'. You can find details about the failure by examining the Rsn value.
For example, you can enter the following TSO command to get Rsn code details: bpxmtext 76650211.
System action
No results from the failed query are available, so any enhanced 3270 user interface workspace
that needs the results might be missing data.
System programmer response
Check that the named DRA is running and not in an abending address space. If this message repeats
frequently, adjust your enhanced 3270UI Global Query Timeout
value to a larger number of
seconds, to allow a longer period for the query to complete. The Global Query Timeout value is found
in the Edit->Preferences (E.P) menu, under the Session/Logon tab.
KOBCM0050E kob_get_from_queue failed, rc = return_code
+extended
diagnostics error and context
Explanation
While selecting discovery refresh requests the conduit manager received a bad return. The failing return code is
x.
System action
Discovery refresh requests will no longer be processed by this address space. The
current data retrieval agents, hub monitoring server, managed system
names and managed system lists will continue to be available for use, but no changes to the
connected Hub environments will be recognized.
User response
Recycle the address space at the next convenient point or when differences between
the locally registered information for the connected hub environments is sufficiently outdated to
cause concern.
KOBCM0051W Recalled DRA registry data is unreliable.
+ dump of registered data retrieval agents
Explanation
After several attempts to recall all registered data retrieval agents (DRAs) in the local registry, only partial data was
retrieved. The log has a dump of the registered DRAs that were found.
System action
Discovery refresh processing continues but possibly with incomplete environmental
information.
User response
The enhanced 3270 user interface address space may not be
aware of all your monitored environments. If this warning appears repeatedly, recycle the address
space. If the warning continues to appear, call IBM Software Support.
KOBCM0052E reqWork too small for MSN sql. Requested size is x.
Explanation
After several attempts to size the reqWork workarea to hold the SQL for MSN refresh,
the required size could not be obtained. The size desired is shown in the message.
System action
Local registry refresh activities terminate. The enhanced 3270 user interface address space will gradually become out of date with
changes to the monitoring agents.
User response
Recycle the address space as soon as is practical. If this error occurs
frequently, call IBM Software Support.
KOBCM0053E reqWork too small for MSL sql. Requested size is x.
Explanation
After several attempts to size the reqWork workarea to hold the SQL for managed
system list (MSL) refresh, the required size could not be obtained. The size desired is shown in the
message.
System action
Local registry refresh activities terminate. The enhanced 3270 user interface address space will gradually become out of date with
changes to the monitoring agents.
User response
Recycle the address space as soon as is practical. If this error occurs
frequently, call IBM Software Support.
KOBCM0054E kobcmndt kob_get_from_queue failed, rc = return code
+
extended diagnostics context.
Explanation
While selecting maintenance refresh requests the Conduit Manager received a bad
return. The failing return code is return code.
System action
Maintenance refresh requests will no longer be processed by kobcmndt. This thread
will be terminated.
User response
The address space should be recycled at the next convenient
point.
KOBCM0054I Registy Refresh {configured | defaults} to x minutes.
Explanation
This documents the local registry refresh cycle that is in use. If the message says
"configured," then the value was supplied as configuration parameter REGREF; otherwise, the message
says "defaults".
System action
Local registry is refreshed periodically at the time interval
specified
KOBCM0055W REGREF configuration variable is value.
+ Valid values are
between 1 minute and 1440 minutes.
+ Default of 5 minutes will be used.
Explanation
Configuration variable REGREF was imported but was not used.
value documents the value read. Valid values are between 1 and 1440 minutes (1
day).
System action
The default of 5 minutes will be used.
User response
Correct the REGREF configuration variable to specify a value within the allowed
range, or accept the default.
KOBCM0056W Get [MSN | MSL] data for hub. Data at address, rc =
return_code
+extended diagnostics context
+ [MSN | MSL] table
header
Explanation
Discovery refresh has received a bad return code (return_code)
while trying to obtain managed system name (MSN) or managed system list (MSL) information from the
specified hub monitoring server. The returned data structure is located at
address. The extended diagnostics context and the result table header structure
are also provided for further diagnosis.
System action
This hub's managed system names or managed system lists are not refreshed in the
local registry.
User response
If this message appears many times, obtain a dump of the enhanced 3270 user interface address space and capture the logs. Call IBM Software
Support.
KOBCM0057I Registry refresh period reset to n.
Explanation
This message documents the local registry refresh cycle that is now in use as a
result of a REGREFRESH command.
System action
Local registry is refreshed periodically at the time interval
specified.
KOBCM0058I Registry refresh cccccccc:
+ Refresh completed in =
n millisec
+ Hubs currently active = n
+ Hubs no longer active = n
+ Hubs just added =
n
+ DRAs currently active = n
+ DRAs newly discovered = n
+ DRAs removed = n
+ DRAs registration errors =
n
+ MSNs Currently registered = n
+ MSNs Newly Registered =n
+ MSNs Removed =n
+ MSNs Registration errors = n
+ MSLs Currently
registerd = n
+ MSLs Newly Registered = n
+ MSLs Removed = n
+ MSLs Registration errors =
n
Explanation
This message appears at the end of every registry refresh cycle, both for periodic
refreshes and for "on demand" refreshes. cccccccc is either "completed" or
"statistics". n is the time, in milliseconds, used to complete the refresh. If a
hub, a data retrieval agent (DRA), managed system (MSN), or managed system list (MSL) is added or
dropped in the recycle, cccccccc will be "statistics" and the option statistics
will be presented. The option messages document what the registry content is and the registry
changes found in the last refresh operation.
KOBCM0059I Maintenance Refresh period reset to n.
Explanation
This documents the local maintenance refresh cycle that is now in use. The value was
changed by a MNTREFRESH command.
System action
ODI or threshold members are refreshed periodically at the time period specified.
KOBCM0059W No viable DRA, Hub=hub-name
(application-name.table-name)
Explanation
The enhanced 3270 user interface address space has attempted
to send an SQL request against table table-name in application
application-name but could not find a suitable Data Retrieval Agent (DRA)
associated with the hub hub-name to handle the request.
System action
The SQL request is not processed.
User response
Check the enhanced 3270 user interface address space
configuration. Make sure the hub hub-name has one or more DRAs associated with it
and that the DRAs are running. Check the DRA and Hub filtering settings to make sure the required
DRAs are not excluded. If further assistance is required, contact IBM Software
Support.
KOBCM0060I processing cmd string = text.
Explanation
The conduit manager has received command
text.
System action
The conduit manager processes the
command.
KOBCM0061I Trace level for KOBGWCND is n.
Explanation
The conduit manager is setting internal trace
level to n.
System action
The conduit manager will start tracing internal
activity messages at interest level n and lower.
User response
Diagnostic tracing for conduit manager can be
prolific. Tracing should be done only under the guidance of IBM Software Support.
KOBCM0062I Registry refresh period is now n minutes.
Explanation
A REGREFRESH command included a valid refresh period value, which is now in
effect.
System action
The local registry refresh period for the conduit manager is changed to n.
User response
Short refresh periods can increase CPU utilization for the enhanced 3270 user interface address space. Use caution in setting refresh
intervals.
KOBCM0063I Maintenance refresh period is now n minutes.
Explanation
A MNTREFRESH command included a valid refresh period value.
System action
Conduit Manager's Maintenance refresh period is changed to n.
User response
Short refresh periods can increase CPU utilization for the Tivoli OMEGAMON address
space.
KOBCM0063W REGREFRESH command specified value.
+ Valid values are
between 1 minute and 1440 minutes.
+ Original period of n minutes
will be used.
Explanation
Command REGREFRESH specified an out-of-range value of value.
Valid values are in the range between 1 and 1440 minutes (1 day).
System action
The immediate refresh is done, but the refresh interval is not
reset.
User response
If a new refresh period is desired, reissue the REGREFRESH command to specify a
value within the valid range.
KOBCM0064I Conduit manager trace level {configured | defaults} to x.
Explanation
This message documents the trace level that is in use by the conduit manager. If the message says "configured," then the value was
supplied as the configuration parameter TRACE; otherwise, the message says
"defaults".
System action
Tracing will be done for all standard messages, plus diagnostic messages at level
x and below.
KOBCM0064W MNTREFRESH command specified value.
+ Allowed values are
between 0 minute and 1440 minutes.
+ Original period of n minutes will be
used.
Explanation
Command MNTREFRESH specified an out of range value of value.
Allowed values are between 0 and 1440 minutes (1 day).
System action
The immediate refresh is done. The refresh period, however, is not reset.
User response
If a new refresh period is desired, reissue the MNTREFRESH command to specify a
value within the allowed range.
KOBCM0065I Maintenance Refresh {configured | defaults} to
x minutes.
Explanation
This documents the maintenance refresh cycle that is in use. If the message says
configured then the value was supplied as configuration parameter MNTREFRESH,
otherwise the message says defaults.
System action
Maintenance thread is refreshed periodically at the time period
specified.
KOBCM0065W TRACE configuration variable is value.
+ Valid values are
integers from 0 and up.
+ Default of x minutes will be
used.
Explanation
The configuration variable TRACE was imported, but was not used. The value
read,value, was not a valid value. Valid values are 0 and up.
System action
The specified default of x will be used.
User response
Correct the TRACE configuration variable to specify a value within the allowed
range or accept the default.
KOBCM0066I Conduit Manager socket timeout level {configured | defaults} to
s.
Explanation
This message documents the time-out seconds in use by the conduit manager for socket
operation connect, send, and receive. If the message says "configured", then the value was supplied
as the configuration parameter SO_TIMEOUT. Otherwise, the message says
"defaults".
System action
Conduit manager socket operations with data retrieval agents (DRAs) will time out
if they have not started within the specified number of seconds.
User response
If communication is slow or error prone and causes many query failures, increase
the time-out value.
KOBCM0067I THRESHOLDS_SOURCE environment variable not FOUND.
Explanation
THRESHOLDS_SOURCE environment variable was not found. Default value of DD:RKANPAR
will be used.
System action
THRESHOLDS_SOURCE set to DD:RKANPAR.
User response
If a new source value of THRESHOLDS is desired, specify that in THRESHOLDS_SOURCE
environment variable.
KOBCM0067W SO_TIMEOUT configuration variable is value.
+ Allowed
values are integers from 0 and up.
+ Default of x seconds will be
used.
Explanation
The configuration variable SO_TIMEOUT was imported but was not
used. value documents the value read. Allowed values are 0 and
up.
System action
The default of x is used.
User response
Correct the SO_TIMEOUT configuration variable to specify a value
within the allowed range or accept the default.
KOBCM0070W Get_Column_Affinities failed. rc = return_code, appl =
appl, table = table
+extended diagnostics context
Explanation
Object Definition Interchange (ODI) file information for the named application,
appl and table, table, was not found. The return code was
return_code. Extended diagnostics will provide the error code and error reason
values as well.
System action
No attempt is made to further adjust the query for agent version level. The query
will be attempted as-is and may fail.
User response
Ensure that the current product ODI table is loaded for the application named in
the message.
KOBCM0081I Conduit Manager discovery socket timeout {configured | defaults} to
x.
Explanation
This message documents the time-out seconds in use by the conduit manager for
discovery socket operation connect, send, and receive. If the message says "configured", then the
value was supplied as a configuration parameter DIS_TIMEOUT. Otherwise, the message
say "defaults".
System action
Conduit manager discovery socket operations with data retrieval agents (DRAs) will
time out if they have not started within the specified number of seconds.
User response
Consult with IBM Software Support before adjusting this value.
KOBCM0082W DIS_TIMEOUT configuration variable is value.
+ Allowed
values are integers from 0 and up.
+ Default of x seconds will be
used.
Explanation
Configuration variable DIS_TIMEOUT was imported but was not used.
value documents the value read. Allowed values are 0 and up.
System action
The default of x is used.
User response
Correct the DIS_TIMEOUT configuration variable to specify a value within the
allowed range or accept the default.
KOBCM0083I Discovery socket timeout seconds for KOBGWCND is n.
Explanation
Conduit manager is setting discovery socket operations time limit to
n seconds.
System action
Conduit manager will wait up to specified seconds for each discovery socket
communication with data retrieval agents (DRAs) to start.
User response
Consult with IBM Software Support before adjusting this value.
KOBCM0084I Conduit Manager ping socket timeout {configured | defaults} to
x.
Explanation
This message documents the time-out seconds that is in use by Conduit Manager for
ping socket operation receive. If the message says configured
, the value was supplied as the
configuration parameter PNG_TIMEOUT. Otherwise the message says defaults
.
KOBCM0085W PNG_TIMEOUT configuration variable is value.
+ Allowed
values are integers from 0 and higher.
+ Default of x seconds will
be used.
Explanation
Configuration variable PNG_TIMEOUT was imported but was not used.
value documents the value read. Allowed values are 0 and above.
System action
The default x will be used.
User response
Correct the PNG_TIMEOUT configuration variable to specify a value within the
allowed range or accept the default.
KOBCM0086I Ping socket timeout seconds for KOBGWCND is n.
Explanation
The conduit manager is setting the time limit for ping-socket operations to
n seconds.
KOBCM0087I Conduit Manager connect socket timeout {configured | defaults} to
x.
Explanation
This message displays the number of seconds before timeout that the conduit manager
uses when connecting to a data retrieval agent (DRA) socket. If the message says
configured, the value was supplied in the configuration parameter
CON_TIMEOUT. Otherwise, the message says
defaults.
KOBCM0088W CON_TIMEOUT configuration variable is value.
+ Allowed
values are integers from 0 and higher.
+ Default of x seconds will
be used.
Explanation
The configuration parameter CON_TIMEOUT was specified, but the
value is not allowed. Allowed values are integers from 0 and above.
System action
The default value of x will be used.
User response
Correct the CON_TIMEOUT parameter value to be within the
allowed range, or accept the default.
KOBCM0089I Connect socket timeout seconds for KOBGWCND is n.
Explanation
The conduit manager is setting the time limit for connect-socket operations to
n seconds.
KOBCM0090W Conduit Manager retried the receive n operation x
times before succeeding.
+ Elapsed time before success is y
microseconds
+ extended diagnostics context
Explanation
Conduit manager receives data from its partner KOBAGENT in two steps. The first step
learns how large the data block will be and the second step receives the actual data. If
n is 1, the conduit manager is receiving the data block size. If
n is 2, the conduit manager is receiving the actual data block.
x is the number of retires before succeeding. y is the number
of microseconds elapsed trying to receive this data.
KOBCM0091I Jobname: nnnnnnnn SYSID: nnnnnnnn SMFID:
ssss.
Explanation
Conduit Manager documents the address space name, System ID, and SMF ID from which
this log is being collected.
KOBCM0100W ODIREFRESH command specified s.
+ Allowed values must begin with K and
be followed by 2 character
+ product code.
Explanation
The ODIREFRESH command entered was not processed. The product code s is not
valid. The command expects you to specify a single product code for the ODI to be refreshed. The
product code must be 3 characters. The first character must be K, the next two characters must be a
product code for a valid product, for example, M5 or CP.
User response
Retry the command using a valid product code. Look at the concatenated files in the
RKANPAR DD statement for this OMEGAMON Enhanced 3270 user interface address space and find the first
instance of the KOBCFGAP member. The first column contains the valid product codes for the ODI files
that this address space might use.
KOBCM0110I Completed Collection_type Situation Collection for
Hub_Name (Total_Sits, +Added_Sits,
-Deleted_Sits).
Explanation
A situation collection processes has completed for the indicated hub TEMS. Details on the
collection type and the number of known situations for this hub TEMS is given, where:
- Collection_type = Periodic | Realtime
- Hub_Name = the origin node of the hub TEMS that was sampled
- Total_Sits = number of situations within the Situation Database for this hub
TEMS
- Added_Sits = number of new situations added to the Situation Database on this
sample
- Deleted_Sits = number of situations deleted from the Situation Database on
this sample
System programmer response
None.
KOBCM0111W Registry Refresh in progress. Periodic Situation Collection will not be performed this
interval.
Explanation
An attempt was made to make start collecting situation data. As the Tivoli
OMEGAMON Manager's internal Registry Refresh processing
was taking place a definitive list of hub TEMS was not available. Collection of situation data
cannot take place and will wait 1 minute before attempting again.
System action
The periodic situation collection is skipped for the current collection interval.
System programmer response
Check the frequency of the Registry Refresh process (KOBCM0054I) and time taken to perform a
Registry Refresh (KOBCM0046I). If this problem is a regular occurrence, consider changing the
situation collection interval, the Registry Refresh process, or both to different intervals to
reduce the chance of Registry Refresh and situation collection occurring at the same time.
KOBCM0112I Situation sampling interval type to frequency
minutes.
Explanation
Indicates how often a periodic situation collection against all know hub TEMS will take place,
where:
- type = configured | defaults
- frequency = frequency, in minutes of the periodic situation collection
process
The value is read from the Tivoli
OMEGAMON Manager's environment settings at startup. The
default value is 5 minutes.
System programmer response
None.
KOBCM0113I Number of cached recent situation samples type to
slot_number samples.
Explanation
Indicates how many recent periodic samples, including status and snapshot data, are retained by
the Tivoli
OMEGAMON Manager for an open situation, where:
- type = configured | defaults
- slot_number = number of slots defined.
The value is read from the Tivoli
OMEGAMON Manager's environment settings at startup. The
default value is 12 samples.
System programmer response
None.
KOBCM0114I Number of cached historical situation samples type to
slot_number samples.
Explanation
Indicates how many historical periodic samples, including status and snapshot data, are retained
by the Tivoli
OMEGAMON Manager for an open situation, where:
- type = configured | defaults
- slot_number = number of slots defined.
The value is read from the Tivoli
OMEGAMON Manager's environment settings at startup. The
default value is 16 samples.
System programmer response
None.
KOBCM0115I Historical situation collection range type to
time_period
units.
Explanation
Indicates the time period that historical situation collection will cover, where:
- type = configured | defaults
- time_period = time period that historical samples will cover
- units = minutes | hours | days
The value is read from the Tivoli
OMEGAMON Manager's environment settings at startup. The
default value is 4 hours. Valid ranges is from 1 minute to 2**32 days.
System programmer response
None.
KOBCM0116I Each historical sample will represent approximately time_period
units.
Explanation
Indicates the time period that a single historical collection sample or slot will cover, where:
- time_period = time period that an individual historical sample will
cover
- units = minutes | hours | days
The value is calculated from overall time period historical situation collection is defined to
cover (KOBCM0115I) divided by the number of periods or slots allocated (KOBCM0114I). If default
values are used, this is 4 hours / 16 samples = 15 minutes.
System programmer response
None.
KOBCM0117W Value of KOB_SITST_SAMPLE_MINUTES configuration variable is frequency.
Valid range is between 1 and 4294967295 minutes. Default of 5 minutes will be used.
Explanation
There was a problem reading the environment variable that defines the situation collection
interval, where:
- frequency = the value for this environment variable as defined in the read
configuration file
The default value of 5 minutes will be used.
System action
Normal processing continues using the default value.
System programmer response
Check the value that is set in the Tivoli
OMEGAMON Manager environment variable files and make any
corrections. The Tivoli
OMEGAMON Manager will need to be recycled for any change
to take effect.
KOBCM0118W Value of KOB_SITST_RECENT_SLOTS configuration variable is slot_number.
Valid range is between 1 and 128 samples. Default of 12 samples will be used.
Explanation
There was a problem reading the environment variable that defines the number recent periodic
samples to be retained by the Tivoli
OMEGAMON Manager for an open situation, where:
- slot_number = the value for this environment variable as defined in the read
configuration file
The default value of 12 samples will be used.
System action
Normal processing continues using the default value.
System programmer response
Check the value that is set in the Tivoli
OMEGAMON Manager environment variable files and make any
corrections. The Tivoli
OMEGAMON Manager will need to be recycled for any change
to take effect.
KOBCM0119W Value of KOB_SITST_HISTORY_SLOTS configuration variable is slot_number.
Valid range is between 1 and 128 samples. Default of 16 samples will be used.
Explanation
There was a problem reading the environment variable that defines the number historical periodic
samples to be retained by the Tivoli
OMEGAMON Manager for an open situation, where:
- slot_number = the value for this environment variable as defined in the read
configuration file
The default value of 16 samples will be used.
System action
Normal processing continues using the default value.
System programmer response
Check the value that is set in the Tivoli
OMEGAMON Manager environment variable files and make any
corrections. The Tivoli
OMEGAMON Manager will need to be recycled for any change
to take effect.
KOBCM0120W Value of KOB_SITST_HISTORY_RANGE configuration variable is time_period.
Valid range is between 1 minute and 4294967295 days. Use suffix M (minutes), H (hours) or D (days)
to indicate units. Default of 4 hours will be used.
Explanation
There was a problem reading the environment variable that defines the time period historical
situation will cover, where:
- time_period = the value for this environment variable as defined in the read
configuration file
The default value of 4 hours will be used.
System action
Normal processing continues using the default value.
System programmer response
Check the value that is set in the Tivoli
OMEGAMON Manager environment variable files and make any
corrections. The Tivoli
OMEGAMON Manager will need to be recycled for any change
to take effect.
KOBCM0121W Historical sample slot interval cannot represent time period less than situation sample
interval. Each historical sample will represent time_period minutes.
Explanation
The calculated historical sample slot interval cannot be less than the defined situation sample
interval (KOBCM0112I). The value is therefore reset to match this value meaning each sample interval
also represents a single historical sample period, where:
- time_period = time period that an individual historical sample will
cover
System programmer response
None.
KOBCM0125E Unable to create Situation Database for hub Hub_Name.
Explanation
There was a problem attempting to create a situation database entry for the given hub, where:
- Hub_Name = the originnode of the hub TEMS that was sampled
System action
Situation collection for the specified hub is stopped for the current interval. Data collected on
this interval will not be retained.
System programmer response
A likely cause for this issue would be a lack of available storage in the Tivoli
OMEGAMON Manager address space. Check the amount of
storage that has been made available and adjust as appropriate.
KOBCM0126E Unable to create record for hub Hub_Name.
Explanation
There was a problem attempting to create a single entry situation database entry for the given
hub, where:
- Hub_Name = the originnode of the hub TEMS that was sampled
System action
Situation collection for the specified hub is stopped for the current interval. Data collected on
this interval will not be retained.
System programmer response
A likely cause for this issue would be a lack of available storage in the Tivoli
OMEGAMON Manager address space. Check the amount of
storage that has been made available and adjust as appropriate.
KOBCM0127E Create thread for kobcmsit failed, pthreadstatusI = pointer
Explanation
There was a problem attempting to create a thread for periodic situation collection, where:
- pointer = pointer location of the failed pthread status
System action
The Tivoli
OMEGAMON Manager will continue but periodic situation
collection will not take place.
System programmer response
Check the problem and make corrections. The Tivoli
OMEGAMON Manager will need to be restarted to enable
periodic situation collection.
KOBCM0128E Create thread for kobcmrst failed, pthreadstatusI = pointer
Explanation
There was a problem attempting to create a thread for realtime situation collection, where:
- pointer = pointer location of the failed pthread status
System action
The Tivoli
OMEGAMON Manager will continue but this instance of a
realtime situation collection will not take place.
System programmer response
Check the problem and make corrections. The Tivoli
OMEGAMON Manager will need to be restarted to use changed
settings.
KOBCM0129W kobcmsit nap had a problem. RC: return_code
Explanation
There was a problem that occurred while the periodic situation collection process was sleeping,
where:
- return_code = return code
System programmer response
If problem is recurring check the problem and make corrections. The Tivoli
OMEGAMON Manager may need to be restarted to use changed
settings.
KOBCM0130E Unable to perform real-time situation sample. Reason
Explanation
There was an error when attempting to make a real-time situation collection. The following line
in the log will give a reason for the error, where:
- Reason = Unable to allocate storage for hub data. | No hub TEMS details
supplied.
System action
The real-time situation data collection is not completed.
System programmer response
If problem is recurring check the problem and make corrections. The Tivoli
OMEGAMON Manager may need to be restarted to use changed
settings.
KOBCM0131I Situation Database statistics:
Explanation
This internal trace message gives a full description as to the current state of the situation
database stored at the Tivoli
OMEGAMON Manager for the specified hub TEMS.
System programmer response
None.
KOBCM0132W There were number_situations new situation records discarded for hub
Hub_Name.
Explanation
The Tivoli OMEGAMON Manager found there was new situations but was unable to collect all the
required information to create a record in the situation database, where:
- number_situations = number of discarded situations
- Hub_Name = the hub TEMS this message applies to
The most likely cause of this would be a timeout in the query to get this information. As the
required information was not collected, the situation record is discarded.
System action
Processing continues. If the situation is still open on the next collection sample, another
attempt to create the record will be made.
System programmer response
Additional tracing (kobflg03 8) may be able to indicate where the problem is. If the issue is
caused by a timeout, increase the value with the Tivoli
OMEGAMON Manager to see if this corrects the issue.
KOBCM0133I The following Hub TEMS are message_type periodic situation sampling:
Hub_Name
Explanation
The KOBENV environment file has a variable that provided a comma-separated case-sensitive list of
hub TEMS names that will be either included or excluded from periodic situation data collection
depending on the variable used. The list of these hub TEMS will be logged on subsequent lines,
where:
- message_type = INCLUDED in | EXCLUDED from
- Hub_Name = the hub TEMS this message applies to.
System action
When periodic situation sampling occurs, the name of each known hub TEMS is checked against the
list and will be skipped if it matches with a name on an exclude list, or it does not match with a
name on an include list.
System programmer response
None.
KOBCM0134W Excluded hub name must be 32 characters or less: Hub_Name.
Explanation
A name on the KOB_SITST_INCLUDE_HUBS or KOB_SITST_EXCLUDE_HUBS environment variable exceeded the
maximum length permitted for a hub TEMS name, where:
- Hub_Name = the hub TEMS this message applies to.
It will be ignored by the Tivoli
OMEGAMON Manager when checking hub TEMS names to either
include or exclude from sampling.
System action
Processing continues. If the situation is still open on the next collection sample, another
attempt to create the record will be made.
System programmer response
Correct the variable value. The Tivoli
OMEGAMON Manager will need to be restarted to use changed
settings.
KOBCM0135I All hubs to be included in periodic situation sampling.
Explanation
The Tivoli
OMEGAMON Manager will periodically sample all hub TEMS
discovered and recorded in the registry for situation data.
System programmer response
None.
KOBCM0136W Both KOB_SITST_INCLUDE_HUBS and KOB_SITST_EXCLUDE_HUBS are specified. Values for
KOB_SITST_INCLUDE_HUBS will be ignored.
Explanation
When processing the environment variables at Tivoli
OMEGAMON Manager startup, entries were found for both the
KOB_SITST_INCLUDE_HUBS and KOB_SITST_EXCLUDE_HUBS. As these environment variables conflict with each
other, the value for KOB_SITST_INCLUDE_HUBS is ignored while the value for KOB_SITST_EXCLUDE_HUBS
will be processed and applied.
System action
Processing continues.
System programmer response
Check the environment variable settings and make corrections. The Tivoli
OMEGAMON Manager will need to be restarted to use changed
settings.
KOBCM0137I Situation Data Collection disabled.
Explanation
No periodic situation data collection will take place against any hub TEMS. Real-time situation
data collection will take place if a user navigates to the Enterprise Status Tree workspace or
refreshes that workspace.
System programmer response
None.
KOBDR001W server pthread_attr_init failed. rc=return_code
Explanation
The attempt to set thread attributes needed to continue initializing the KOBAGENT
Data Retrieval Agent has failed.
System action
Initialization continues.
User response
It is likely this KOBAGENT instance is unusable. Try restarting the address space.
If the problem persists, contact IBM Software Support.
KOBDR002W server pthread_create failed. rc=return_code
Explanation
The attempt to start the main TCP/IP server thread within the KOBAGENT data
retrieval agent has failed.
System action
The data retrieval agent is unable to process client requests.
User response
It is likely this KOBAGENT instance is unusable. Try restarting the address space
if problem persists contact IBM Support. If the problem persists, contact IBM Software
Support.
KOBDR003W Data Retrieval Agent is not registered. Registration stage stage failed
with Return Code = return_code
Explanation
stage can assume the follow values:
- Discover Host IP Data
- The TCP/IP host name of the LPAR where this address space is located could not be determined.
Additional information for this failure can be:
- + gethost_rc =return_code, gethost_errno =
error_code
- + hostname = host_name
- + getaddr_rc = return_code, getaddr_errno =
error_code
- + freeaddr_rc = return_code, freeaddr_errno =
error_code
- Resolve IP Address
- The IP address associated with the host name could not be determined
- Discover HUB Data
- The hub name and IP information for this agent could not be determined
- Register DRA
- The attempt to register the information for this data retrieval agent with the IWMSRSRG service
failed
System action
The data retrieval agent is unable to process client requests.
User response
It is likely this KOBAGENT instance is unusable. Try restarting the address space
if problem persists contact IBM Support. If the problem persists, contact IBM Software
Support.
KOBDR004W client pthread_attr_init failed. rc=return_code
Explanation
The attempt to set thread attributes needed to initialize the query processing
thread in the KOBAGENT data retrieval agent has failed.
System action
The query is abandoned.
User response
Retry the workspace associated with this failure. If the problem persists, contact
IBM Software Support.
KOBDR005W client pthread_create failed. rc=return_code
Explanation
The attempt to initialize the query processing thread in the KOBAGENT data retrieval
agent has failed.
System action
The query is abandoned.
User response
Retry the workspace associated with this failure. If the problem persists, contact
IBM Software Support.
KOBDR006E ERROR: storage_type storage unavailable
Explanation
The attempt to acquire storage within the address space failed. The storage types
involved are:
- Send block
- 1 megabyte is requested
- Send buffer
- 64K bytes is requested
- Row buffer
- 4K bytes is requested
System action
The query is abandoned.
User response
Retry the workspace associated with this failure. If the problem persists, contact
IBM Software Support.
KOBDR007E ERROR: input buffer storage unavailable
Explanation
The attempt to acquire storage to receive query from the enhanced 3270 user interface address space has failed.
System action
The query is abandoned.
User response
Retry the workspace associated with this failure. If the problem persists, contact
IBM Software Support.
KOBDR008E stage failure (return_code)
Explanation
The attempt to start the SQL request in the data retrieval agent failed at stage
stage with code return_code, where stage is
one of:
- SQL1_CreateAccessPlan
- specifies the query to submit
- SQL1_CreateRequest
- establishes connection with agent
- SQL1_GetInputSQLDA
- allows for variable input values
- SQL1_OpenRequest
- collects a table sample
- SQL1_GetOutputSQLDA
- provides structure for return row
System action
The query is abandoned.
User response
Retry the workspace associated with this failure. If the problem persists, contact
IBM Software Support.
KOBDR009E error for SQL, sqlStatus(%d)
Explanation
Fetching row data failed.
System action
The query is abandoned.
User response
Retry the workspace associated with this failure. If the problem persists, contact
IBM Software Support.
KOBDR010E ERROR: Row buffer storage too small
Explanation
Fetching row data failed.
System action
The query is abandoned.
User response
Retry the workspace associated with this failure. If the problem persists, contact
IBM Software Support.
KOBDR011E SQL processing error in call stage. Return code is
return_code. clsocket is socket
Explanation
Documents failure of an SQL request. This message is usually preceded or followed by
KOBDR006E, KOBDR0007E, KOBDR008E, KOBDR009E, or KOBDR010E.
System action
The query is abandoned.
User response
Retry the workspace associated with this failure. If the problem persists, contact
IBM Software Support.
KOBDR012E function function failed with error code code
(code_name) at line line_number.
Reason
Action
Explanation
This message documents many of the possible TCP/IP error codes. The
Action text may suggest a corrective step.
System action
The query is abandoned.
User response
if there is an action mentioned that can be implemented try taking that action.
Otherwise, contact IBM Software Support.
KOBDR013I sent nnn bytes to address space name and SMFID
+ for sequence # = xxxxxxxx_xxxxxxxx,table =
appl.table
Explanation
This message documents the number of bytes returned for this query, where:
- nnn is the count of bytes sent
- address space name and SMFID is the name and SMFID of the job
- xxxxxxxx_xxxxxxxx is the sequence number tied to the request
- appl.table is the name of the application and the table submitting the query
KOBDR020W CreateRequest failed, possibly due to missing TEMS Catalog entries. Resolve this by adding
application support files (seeding) for 'appl.table in the
target {TEMS | Remote TEMS}: monitoring_server_name
Explanation
Message KOBDR020W indicates that a query was relayed by this KOBAGENT (Data Retrieval Agent) to a
remote or hub monitoring server that does not contain the necessary monitoring server catalog
entries (application support files).
System action
The query fails and any enhanced 3270 user interface workspace that needs the results might be
missing data.
System programmer response
Apply application support (also known as seeding) to the necessary remote and hub monitoring
server.
KOBDR023I Host address discovery
Explanation
Message KOBDR023I is an internal trace message that is displayed during KOBAGENT (Data Retrieval
Agent) Host IP address discovery.
System programmer response
None.
KOBDR024I gethostname() rc(return_code),
name(hostname)
Explanation
Message KOBDR024I is an internal trace message that is displayed during KOBAGENT (Data Retrieval
Agent) Host IP address discovery, which shows the result of the gethostname service.
System programmer response
None.
KOBDR025I IRA_GetHostname() name(hostname)
Explanation
Message KOBDR025I is an internal trace message that is displayed during KOBAGENT (Data Retrieval
Agent) Host IP address discovery, which shows the result of the IRA_GetHostname service.
System programmer response
None.
KOBDR026I Host name priority: #1 IRA_GetHostname(hostname) #2
gethostname(hostname) or Host name priority: #1
gethostname(hostname) #2 IRA_GetHostname(hostname)
Explanation
This message displays the host name or names on which the Data Retrieval Agent is running. The
gethostname() value can be given priority over the IRA_GetHostname value (not the default behavior)
by supplying the user configuration value KOB_USE_IRA_HOSTNAME=N in the KxxENV file.
System programmer response
None.
KOBDR027I hostname(hostname) details:
Explanation
Message KOBDR027I is an internal trace message that is displayed during KOBAGENT (Data Retrieval
Agent) Host IP address discovery.
System programmer response
None.
KOBDR030I getaddrinfo().2 flags nnn family nnn type
nnn proto nnn addrlen nnn
Explanation
Message KOBDR030I is an internal trace message that is displayed during KOBAGENT (Data Retrieval
Agent) Host IP address discovery, which shows the result of the getaddrinfo service.
System programmer response
None.
KOBDR031I getaddrinfo().3 address: getaddrinfo_returned_answer
Explanation
Message KOBDR031I is an internal trace message that is displayed during KOBAGENT (Data Retrieval
Agent) Host IP address discovery, which shows the result of the getaddrinfo service.
System programmer response
None.
KOBDR032E Unable to obtain DRA Host Address, cannot run DRA
Explanation
The Data Retrieval Agent (DRA), a component of the OMEGAMON
enhanced 3270 user interface (enhanced 3270UI), was not able to initialize
due to a failure in an attempt to use z/OS®
UNIX System Services TCP/IP services (for example, to obtain
the Host system TCP/IP address).
System action
The DRA will terminate initialization as it cannot function without TCP/IP. TCP/IP
is required for communication between the DRA and the enhanced 3270UI (TOM) address
space.
System programmer response
Perform the following actions:
- Verify that TCP/IP has been started and is running in the Host system where the DRA is
running.
- Verify that TCP/IP has been started before starting the address space where the DRA will be
running.
- Verify that a Security System OMVS Segment has been defined for the address space where the DRA
is running.
KOBDR033I Forcing use of a single TCP IPv4 interface(IPv4_address_text
)(IPv4_address_text) or Forcing use of a single TCP IPv6
interface(IPv6_address_text )(IPv6_address_text)
Explanation
The user configuration value KOB_USE_ONE_INTERFACE=Y was set in the KxxENV file, so the TCP
"listen" for the Data Retrieval Agent component is done on just a single network interface, rather
than on all network interfaces on this host.
System programmer response
None.
KOBDR037I {host | hub} property = property_value
Explanation
A Hub Tivoli Enterprise Monitoring Server and local Host
address were successfully discovered and the listed values are the related network addresses, port
numbers, and names. The Host Port value is the TCP port number on which this address space "listens"
for inbound requests from Tivoli
OMEGAMON Manager address spaces. The possible properties
are shown in the following list:
- Host Name
- Host Address IPv4
- Host Address IPv6
- Host Port
- Host Family
- Hub Name
- Hub Address
- Hub Port
System programmer response
None.
KOBDR043I Hub IP addr = IP_address, port = port_number, orig =
monitoring_server_name
Explanation
A Hub Tivoli Enterprise Monitoring Server was
successfully discovered and the listed values are its network address, port number, and monitoring
server name.
System programmer response
None.
KOBDR044I Hub Name = hub_monitoring_server_name Hub Address =
hub_monitoring_server_address Hub Port =
hub_monitoring_server_port_number
Explanation
A Hub Tivoli Enterprise Monitoring Server was
successfully rediscovered and the listed values are the related network addresses, port numbers, and
names.
System programmer response
None.
KOBDR045I {Call to | Back from} {Init_HUB | Drop_HUB}()
Explanation
These messages indicate the processing flow of Hub Tivoli Enterprise Monitoring Server discovery within the KOBAGENT (Data Retrieval Agent).
System programmer response
None.
KOBDR046I programFlowDetails_controlBlockInformation
Explanation
This internal trace message is displayed during data retrieval agent (DRA)
processing, showing program flow details and internal control block information.
System programmer response
None.
KOBDR047I KOB_DRA_BACKLOG value=x is specified
Explanation
The configuration parameter KOB_DRA_BACKLOG with the value of
x has been found in the KppENV member of the RKANPAR DD
concatenation, where pp is the two-character product code.
System action
The data retrieval agent (DRA) will process the parameter.
User response
No action is required.
KOBDR048W Incorrect KOB_DRA_BACKLOG value=x is specified.
+ Allowed
values are integers from min to max.
+ Default
value of y is assigned
Explanation
The configuration parameter KOB_DRA_BACKLOG has the value of
x, which is incorrect. A correct value should be an integer within the limits
displayed in the message.
System action
The data retrieval agent (DRA) will process the
KOB_DRA_BACKLOG parameter using the default value of
y.
User response
Correct the KOB_DRA_BACKLOG parameter value to be within the
allowed range, or accept the default. The updated value will be picked up when the DRA is
restarted.
KOBDR049I Default DRA backlog value=x will be used
Explanation
The configuration parameter KOB_DRA_BACKLOG was not
specified.
System action
The data retrieval agent (DRA) will continue initialization using the default value
of x.
User response
No action is required.
KOBGW0000I enhanced 3270 user interface address space initialized
successfully.
Explanation
The address space has started.
KOBGW0001I enhanced 3270 user interface address space terminated
successfully.
Explanation
The address space has terminated without error.
KOBGW0002E The enhanced 3270 user interface address space terminated with
errors.
Explanation
The address space terminated, but errors were detected in one or more phases of the
shutdown.
System action
The address space terminates.
User response
Check accompanying messages and forward the job message log to IBM Software
Support.
KOBGW0003E The enhanced 3270 user interface address space is not
APF-authorized.
System action
The address space terminates.
User response
Make sure that the enhanced 3270 user interface address
space started task STEPLIB load libraries are APF-authorized and restart the task.
KOBGW0004E enhanced 3270 user interface CVT eyecatcher invalid at storage
free.
Explanation
The enhanced 3270 user interface CVT control block storage
has been corrupted.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0005E Name/Token IEANTCR failed rc=return_code.
Explanation
The z/OS Name/Token services call used to create an anchor for the enhanced 3270 user interface address space CVT failed with the return code given.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0006E EXTRACT parameter list allocation failed.
Explanation
Storage could not be acquired for a z/OS service to establish a communication area
for operator console communications.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0007E Name/Token IEANTDL failed rc=return_code.
Explanation
The z/OS Name/Token services call used to delete an anchor for the enhanced 3270 user interface address space CVT failed with the return code
given.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0008E Attempt to free enhanced 3270 user interface CVT failed.
Explanation
Freeing of the enhanced 3270 user interface address space
anchor control block failed. The CVT control block storage has been corrupted.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0009E SYSEVENT parameter list allocation failed.
Explanation
Storage could not be acquired for a z/OS service to make the enhanced 3270 user interface address space nonswappable.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0010E ATTACHX parameter list allocation failed.
Explanation
Storage could not be acquired for a z/OS service to start a enhanced 3270 user interface address space subcomponent.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0011I User interface subcomponent subcomponent started successfully.
Explanation
Subcomponent subcomponent of the enhanced 3270 user interface address space user interface started
successfully.
KOBGW0012E LOAD parameter list allocation failed.
Explanation
Storage could not be acquired for a z/OS service to start an enhanced 3270 user interface address space subcomponent.
System action
The address space terminates.
User response
Call IBM Software Support.
KOBGW0013E Load of subcomponent module module failed. rc=return_code,
rsn=reason_number
Explanation
The z/OS service used to load the program required to start the Enhanced 3270 User
Interface address space subcomponent module failed with return code return_code and
reason code reason_number.
System action
The address space terminates.
User response
Call IBM Software Support.
KOBGW0014E pthread_attr_init() for subcomponent subcomponent failed. rc=return_code,
rsn=reason_number
Explanation
A service to initialize attributes for starting a enhanced 3270 user interface address space subcomponent subcomponent failed
with return code return_code and reason code reason_number.
System action
The address space terminates.
User response
Call IBM Software Support.
KOBGW0015E pthread_attr_setJST_np() for subcomponent subcomponent failed.
rc=return_code, rsn=reason_number
Explanation
A service to initialize the task ownership for starting a enhanced 3270 user interface address space subcomponent subcomponent failed
with return code return_code and reason code reason_number.
System action
The address space terminates.
User response
Call IBM Software Support.
KOBGW0016E pthread_create() for subcomponent subcomponent failed. rc=return_code,
rsn=reason_number
Explanation
A service to start a thread for an enhanced 3270 user interface address space subcomponent subcomponent failed with return code return_code and
reason code reason_number.
System action
The address space terminates.
User response
Call IBM Software Support.
KOBGW0017I Subcomponent subcomponent started.
Explanation
The enhanced 3270 user interface address space subcomponent
subcomponent started successfully.
KOBGW0018E Request router queue initialization failed. rc=return_code.
Explanation
A problem occurred in the initialization of the communication queue between the user
interface and the request router.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0019E Request router queue destroy failed. rc=return_code.
Explanation
A problem occurred with the destruction of the communication queue between the user
interface and the request router.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0020E KOBC_IO_Term() failed. rc=return_code.
Explanation
A problem occurred with the destruction of the file descriptor
table.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0021E Delete of LPA-based load modules failed.
Explanation
A problem occurred during the deletion of load modules loaded dynamically into the
Link Pack Area (LPA).
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0022E Allocation of registry root area failed.
Explanation
Allocation of storage for the enhanced 3270 user interface
registry root area failed
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0023E Allocation of request router base area failed.
Explanation
Storage could not be acquired for a enhanced 3270 user interface
request router storage area.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0024E Allocation of trace base area failed.
Explanation
Storage could not be acquired for a enhanced 3270 user interface trace storage area.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0025E LPA-based function load/registration failed. rc=return_code,
rsn=error_reason, rsn2=error_reason2.
Explanation
enhanced 3270 user interface load modules could not be loaded
into the Link Pack Area (LPA) or the registration of the
modules' functions in the GWCVT anchored function table was unsuccessful. Further information
related to the reason codes may be found in the "CSVDYLPA -- Provide Dynamic LPA Services" section
of the MVS Programming: Authorized Assembler Services Reference, Volume 1
(ALE-DYN).
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0026E KOBC_IO_Init() failed. rc=return_code, rsn=error_reason,
rsn2=error_reason2.
Explanation
The allocation and initialization of the enhanced 3270 user interface file descriptor table failed
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0027E User interface subcomponent subcomponent start up failed.
rc=return_code
Explanation
The enhanced 3270 user interface address space subcomponent
subcomponent could not be started due to error return_code.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0028E The enhanced 3270 user interface address space initialized with
errors.
Explanation
The enhanced 3270 user interface address space initialized,
but errors were detected in one or more phases of the start up.
System action
The address space terminates.
User response
Check accompanying messages and forward the job message log to IBM Software
Support.
KOBGW0029E CSVDYLPA REQUEST=ADD failure rc = return_code, rsn = error_reason.
Explanation
Loading of Link Pack Area (LPA) modules at
initialization of the enhanced 3270 user interface failed, with the return
and reason codes displayed in message.
System action
The address space terminates.
User response
Check accompanying messages and forward the job message log to IBM Software
Support.
KOBGW0030E One or more modules could not be loaded into LPA.
Explanation
Loading of Link Pack Area (LPA) modules at
enhanced 3270 user interface initialization failed with return code
4.
System action
The address space terminates.
User response
Check accompanying messages and forward the job message log to IBM Software
Support.
KOBGW0031I Module module loaded into LPA successfully at loadpoint, entry point
entrypoint.
Explanation
Module module was dynamically loaded into LPA at load point loadpoint.
Its entry point is at location entrypoint
System action
Address space initialization continues.
KOBGW0032E Load of module module failed. pcode = pppp, rtncd/abndcd = xxxx,
rsncd/abndrsn = yyyy.
Explanation
Dynamic load of load module module failed with the return, abend reason, and
abend reason codes displayed in the second line of the message. Further information related to the
reason codes may be found in the "CSVDYLPA -- Provide Dynamic LPA Services" section of the MVS
Programming: Authorized Assembler Services Reference, Volume 1 (ALE-DYN).
System action
The address space terminates.
User response
Check accompanying messages and forward the job message log to IBM Software
Support.
KOBGW0033E CSVDYLPA DELETE failure. rc = return_code, rsn =error_reason.
Explanation
Deletion of dynamically loaded Link Pack Area
(LPA) modules failed with return code return_code and reason code
error_reason.
System action
The address space termination continues.
User response
Check accompanying messages and forward the job message log to IBM Software
Support.
KOBGW0034E One or more modules could not be deleted from LPA.
Explanation
Deletion of Link Pack Area (LPA) modules at
termination of the enhanced 3270 user interface failed with return code
4.
System action
The address space termination continues.
User response
Check accompanying messages and forward the job message log to IBM Software
Support.
KOBGW0035I Module module deleted from LPA successfully.
Explanation
Load module module was dynamically deleted from the Link Pack Area (LPA) successfully.
System action
Termination of the address space continues.
KOBGW0036E Delete of module module from LPA failed. pcode = pppp, rtncd/abndcd =
xxxx, rsncd/abndrsn = yyyy.
Explanation
Dynamic deletion of load module module failed with the return, abend reason,
and abend reason codes displayed in the second line of the message. Further information related to
the reason codes may be found in the "CSVDYLPA -- Provide Dynamic LPA Services" section of the
MVS Programming: Authorized Assembler Services Reference, Volume 1
(ALE-DYN).
System action
Termination of the address space continues.
User response
Check accompanying messages and forward the job message log to IBM Software
Support.
KOBGW0037E KOBGW_LoadLPAFunction() registration failed. rc = return_code, errno =
error_number, rsnno = reason_number.
Explanation
Registration of an Link Pack Area (LPA) based
enhanced 3270 user interface address space function failed with return code
return_code, errno error_number and rsnno reason_number.
System action
The address space terminates.
User response
Recreate the error with debugging mode switched on. Establish debugging mode by
specifying the following in the RKANPARU(KOBENV) member before starting the enhanced 3270 user
interface address space: TRACEV1=TRACE KOBGWLPA,1. Check accompanying
messages and forward the job message log to IBM Software Support.
KOBGW0038E Module module function registration failed rc = return_code, errno =
error_number, errno2 = error_number2.
Explanation
The entry point initialization routine for dynamically loaded Link Pack Area (LPA) module module failed with the return and
reason codes displayed in the message.
System action
The address space terminates.
User response
Recreate the error with debugging mode switched on. Establish debugging mode by
specifying the following in the RKANPARU(KOBENV) member before starting the enhanced 3270 user
interface address space: TRACEV1=TRACE KOBGWLPA,1. Check accompanying
messages and forward the job message log to IBM Software Support.
KOBGW0039E RESMGR output token address parameter is zero.
Explanation
A problem occurred with the start of a component enhanced 3270 user interface address space. The value of the RESMGR
TOKEN= keyword parameter is zero.
System action
The address space terminates.
User response
This is a program error. Contact IBM Software Support.
KOBGW0040E Allocation of the resource manager LOAD parameter list failed.
Explanation
Insufficient storage is available to allocate the parameter list for
LOAD.
System action
The address space terminates.
User response
Determine whether there were storage shortage problems at the time of the error and
contact IBM Software Support.
KOBGW0041E Load of resource manager KOBRSMGR failed. rc = return_code, rsn =
error_reason.
Explanation
The LOAD of the enhanced 3270 user interface address space
resource manager routine failed with the return and reason codes displayed in the
message.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0042E Allocation of the parameter list for RESMGR ADD
failed.
Explanation
Insufficient storage is available to allocate the parameter list for RESMGR
ADD.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0043E Allocation of the parameter list for RESMGR DELETE
failed.
Explanation
Insufficient storage is available to allocate the parameter list for RESMGR DELETE,
causing a problem with the start of the enhanced 3270 user interface address
space.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0044E Establishment of resource manager failed rc = return_code.
Explanation
Establishment of the enhanced 3270 user interface address
space resource manager failed with the return code displayed in the message.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0045E Attempt to free the resource manager LPA module table failed.
Explanation
The enhanced 3270 user interface address space resource
manager routine attempted to delete a dynamically loaded LPA module and failed.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0046E Deletion of resource manager failed rc = return_code
Explanation
Deletion of enhanced 3270 user interface address space
resource manager failed. Further information related to the reason codes may be found in the "RESMGR
-- Add or Delete a Resource Manager" section of the MVS Programming: Authorized Assembler
Services Reference, Volume 3 (LLA-SDU).
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0047I enhanced 3270 user interface CVT freed by resource
manager.
Explanation
Anchor control block storage for the enhanced 3270 user interface address space was freed successfully during resource
manager processing.
System action
Resource manager processing continues.
KOBGW0048E Resource Manager KOBGW_DeleteLPAFunction() failed rc =
return_code
Explanation
The deletion of dynamically-loaded LPA modules failed during resource manager
processing with the return code displayed in the message.
System action
Resource manager processing continues.
User response
Contact IBM Software Support.
KOBGW0049E LPA_Term() in resource clean up failed rc = return_code.
Explanation
During processing by the enhanced 3270 user interface address
space resource manager, the routine handling the deletion of dynamically loaded LPA modules failed
with the return code displayed in the message.
System action
Resource manager processing continues.
User response
Contact IBM Software Support.
KOBGW0050E deleteLPAmodTabFromESQA() in resource clean up failed rc = return_code.
Explanation
During processing by the enhanced 3270 user interface address
space resource manager, the routine handling the freeing of a common storage area used during
deletion of dynamically loaded LPA modules failed with the return code displayed in the
message.
System action
Resource manager processing continues.
User response
Contact IBM Software Support.
KOBGW0051E free_GWCVT() in resource clean up failed rc = return_code.
Explanation
The anchor control block storage for the enhanced 3270 user interface address space could not be freed during resource manager
processing for the reason in the return code displayed in the message.
System action
Resource manager processing continues.
User response
Contact IBM Software Support.
KOBGW0052I KOBRSMGR resource manager routine entered.
Explanation
The enhanced 3270 user interface address space resource
manager routine installed to clean up orphaned, critical resources was entered due to an operator
CANCEL command.
System action
Resource manager processing continues.
User response
Investigate the reason for the operator CANCEL command being
issued.
KOBGW0053I KOBRSMGR resource manager routine completed
Explanation
The enhanced 3270 user interface address space resource
manager routine installed to clean up orphaned, critical resources completed its
processing.
System action
Resource manager processing continues.
User response
Investigate the reason for the operator CANCEL command being issued. Also check for
any error messages issued during normal user interface address space processing and in the resource
manager processing.
KOBGW0054E Command table entry for thread thread not found. rsn =
reason_code.
Explanation
The subcomponent has not registered to receive commands. The failure to register was
discovered in the subcomponent command processing routine. The reason code will help to determine
the cause of the problem.
System action
The subcomponent command processing routine terminates.
User response
Contact IBM Software Support.
KOBGW0055E Attempt to get command from the subcomponent command queue failed. rc =
return_code, rsn = error_reason, rsn2 =
error_reason.
Explanation
The subcomponent command processing routine experienced a failure attempting to read
a command from its command queue. The return and reason codes will help to determine the cause of
the problem.
System action
The subcomponent command processing routine terminates.
User response
Contact IBM Software Support.
KOBGW0056E Subcomponent command processing routine failed. rc = return_code, rsn =
error_reason, rsn2 = error_reason2.
Explanation
The subcomponent experienced a failure while processing a command. The return code
and reason codes will help to determine the cause of the problem.
System action
The subcomponent command processing routine terminates.
User response
Contact IBM Software Support.
KOBGW0057E Command table entry for thread thread_name not found.
rsn = error_reason.
Explanation
During subcomponent command registration no thread table entry was found for
subcomponent thread thread_name. The reason code will help to
determine the cause of the problem.
System action
The subcomponent thread terminates.
User response
Contact IBM Software Support.
KOBGW0058E Command command is longer than 16 characters.
Explanation
During subcomponent command registration, registration of a command name with a
length greater than the maximum 16 characters allowed was specified.
System action
The subcomponent thread terminates.
User response
Contact IBM Software Support.
KOBGW0059E Creation of subcomponent command queue failed. rc = return_code, rsn =
error_reason, rsn2 = error_reason2.
Explanation
During subcomponent command registration, the creation of the subcomponent's command
queue failed. The return code and reason codes will help to determine the cause of the
problem.
System action
The subcomponent thread terminates.
User response
Contact IBM Software Support.
KOBGW0060E pthread_attr_init() for subcomponent message thread failed. rc =
return_code, rsn = error_reason, rsn2 =
error_reason2.
Explanation
During the subcomponent launch of its command processing thread, the initialization
of thread attributes failed. The return code and reason codes will help to determine the cause of
the problem.
System action
The subcomponent thread terminates.
User response
Contact IBM Software Support.
KOBGW0061E pthread_create() for subcomponent message thread failed. rc =
return_code, rsn = error_reason, rsn2 =
error_reason2.
Explanation
During the subcomponent launch of its command processing thread, the creation of the
thread failed. The return code and reason codes will help to determine the cause of the
problem.
System action
The subcomponent thread terminates.
User response
Contact IBM Software Support.
KOBGW0062E Command table entry for thread thread not found. rsn =
reason_code.
Explanation
During subcomponent command deregistration, no thread table entry was found for
subcomponent thread thread. The reason code will help to determine the cause of
the problem.
System action
The subcomponent thread terminates.
User response
Contact IBM Software Support.
KOBGW0063E Destruction of command table entry queue failed. rc = return_code, rsn =
error_reason.
Explanation
During subcomponent command deregistration, the destruction of the subcomponent
command queue failed. The return code and reason code will help to determine the cause of the
problem.
System action
The subcomponent thread terminates.
User response
Contact IBM Software Support.
KOBGW0064E No command text specified in the command buffer.
Explanation
A command issued to the subcomponent did not contain any command
text.
System action
Processing continues and the subcomponent waits for another
command.
User response
Make sure that the command issued was specified correctly. If a command greater
than 16 characters in length is documented, this is an error. Contact IBM Software
Support.
KOBGW0065E Command table entry for thread thread not found. rsn =
reason_code.
Explanation
While issuing a command for a subcomponent, no thread table entry was found for
subcomponent thread thread. The reason code will help to determine the cause of
the problem.
System action
Processing continues and the subcomponent waits for another
command.
User response
Contact IBM Software Support.
KOBGW0066E Add of command to command queue failed. rc = return_code, rsn =
error_reason, rsn2 = error_reason2.
Explanation
A command issued for the subcomponent could not be added to the subcomponent's
command queue. The return code and reason codes will help to determine the cause of the
problem.
System action
Processing continues and the subcomponent waits for another
command.
User response
Contact IBM Software Support.
KOBGW0067E pthread_join() failed. rc = return_code, rsn =
error_reason, rsn2 = error_reason2.
Explanation
An attempt to synchronize subcomponent termination with the main task on issuance of
a STOP command to the subcomponent failed. The return code and reason codes will help to determine
the cause of the problem.
System action
The subcomponent processes the STOP command, but the subcomponent thread
termination is not synchronized with the main thread, possibly forcibly terminating the subcomponent
thread with an abnormal termination code.
User response
Contact IBM Software Support.
KOBGW0068E Command command not supported by any active subcomponents.
Explanation
A console command was entered but no active enhanced 3270 user interface subcomponent was registered for the
command.
System action
The interface continues to wait for the next console command.
User response
A console command may have been mistyped. Retry the command. If the command is
documented and entered correctly, contact IBM Software Support.
KOBGW0069E GW_Obtain_GWCVT_Address() returned NULL. rsn = error_reason, rsn2 =
error_reason2.
Explanation
A console command to stop the KOBVTAM subcomponent failed to find a required anchor
control block. The reason codes may help determine the cause of the problem.
System action
The KOBGWOBV subcomponent terminates without terminating the KOBVTAM subcomponent.
The interface will continue to wait for console commands.
User response
This is an internal error. Contact IBM Sofware Support and be prepared to supply
the logs for the address space.
KOBGW0070E Session header block address is NULL.
Explanation
A console command to STOP the KOBVTAM subcomponent failed to find the head of the
session control block chain.
System action
The KOBGWOBV subcomponent terminates without terminating the KOBVTAM subcomponent.
The interface will continue to wait for console commands.
User response
This is an internal error. Contact IBM Sofware Support and be prepared to supply
the logs for the address space.
KOBGW0071W nnnnn UI sessions still have requests in progress. Waiting
nn more seconds to allow requests to complete.
Explanation
A console command to STOP the KOBVTAM subcomponent has been issued but the user
interface component has one or more sessions with active requests. The address space will wait for
up to 60 seconds in 5 second increments or until no active user interface requests are detected.
After 60 seconds a WTOR will be issued allowing the operator to extend the wait for active requests
to complete.
System action
The subcomponent KOBGWOBV will issue KOBGW0071W messages every 5 seconds until it
detects all active user interface requests have completed. KOBGW0085I will be issued as a WTOR after
60 seconds if active user interface requests persist.
User response
This message is most likely issued because at least one long-running request was
still active when a console STOP command was issued against the address space. If, however, the
duration of the request exceeds an expected amount of time, there may be a problem in the request
path. If this is the case, contact IBM Software Support.
KOBGW0072W Maximum wait time for session requests to complete at termination exceeded
Explanation
A console command to STOP the KOBVTAM subcomponent has been issued and the operator
has responded to the KOBGW0085I WTOR to request that no further waiting for request completion be
attempted.
System action
The address space will terminate the KOBVTAM subcomponent. Any user interface
sessions with active requests will be forcibly terminated.
User response
The termination of the KOBVTAM subcomponent may be premature if a long-running
request has not been given enough time to complete. If the request should have completed within the
allowed interval, capture the logs for the address space and the hub Tivoli Enterprise Monitoring Server from which data was being requested and contact IBM
Software support.
KOBGW0073W Sessions with active requests will be forcibly terminated.
Explanation
A console command to STOP the KOBVTAM subcomponent has been issued and the operator
has responded to the KOBGW0085I WTOR to request that no further waiting for request completion be
attempted.
System action
The address space will terminate the KOBVTAM subcomponent. Any user interface
sessions with active requests will be forcibly terminated.
User response
The termination of the KOBVTAM subcomponent may be premature if a long-running
request has not been given enough time to complete. If the request should have completed within the
allowed interval, capture the logs for the address space and the hub Tivoli Enterprise Monitoring Server from which data was being requested and contact IBM
Software support.
KOBGW0074E OBVTAM STOP processing failed rc = return_code, rsn =
error_reason, rsn2 = error_reason2.
Explanation
The STOP console command to terminate the KOBVTAM subcomponent failed with the
return and reason codes provided.
System action
The KOBVTAM subcomponent will not be terminated by the current command. The address
space will continue to wait for other console commands.
User response
Other messages preceding KOBGW0074E will help in determining the cause of the
problem in addition to the return and reason codes displayed.
KOBGW0075E OBVTAM command command not supported by command handler.
Explanation
The KOBGWOBV command handling process does not support the command
command.
System action
The KOBGWOBV subcomponent returns and the address space continues to wait for other
console commands.
User response
This is an internal error. Contact IBM Software Support and be prepared to supply
the logs for the address space.
KOBGW0076E Command registration in KOBGWOBV subcomponent failed. rc = return_code,
rsn = error_reason, rsn2 = error_reason2.
Explanation
KOBGWOBV failed to register for address space console commands.
System action
The KOBGWOBV subcomponent returns and the address space continues to wait for other
console commands. The KOBVTAM subcomponent will not be able to respond to console
commands.
User response
This is an internal error. Contact IBM Software Support and be prepared to supply
the logs for the address space.
KOBGW0077E Command wait in KOBGWOBV subcomponent failed. rc = return_code, rsn =
error_reason, rsn2 = error_reason2.
Explanation
KOBGWOBV failed to establish the routine that waits for its registered console
commands.
System action
The KOBGWOBV subcomponent returns and the address space continues to wait for
further console commands. The KOBVTAM subcomponent will not be able to respond to console
commands.
User response
This is an internal error. Contact IBM Software Support and be prepared to supply
the logs for the address space.
KOBGW0078E Command deregistration in KOBGWOBV subcomponent failed. rc =
return_code, rsn = error_reason, rsn2 =
error_reason2.
Explanation
KOBGWOBV failed to establish the routine that deregisters its registered console
commands.
System action
The KOBGWOBV subcomponent returns and the address space continues to wait for
further console commands.
User response
This is an internal error. Contact IBM Software Support and be prepared to supply
the logs for the address space.
KOBGW0079E KOBOBV_Update_Session_Status() TCBAddress is NULL.
Explanation
A user interface session registration with the command handler supplied a NULL TCB
address.
System action
The user interface will issue a popup error message explaining that the session
initialization failed.
User response
This is an internal error. Contact IBM Software Support and be prepared to supply
the logs for the address space.
KOBGW0080E KOBOBV_Update_Session_Status() sessionStatus out of range (1 - 4). Value passed =
nnnn
Explanation
The status parameter values supplied by the internal routine were outside the
acceptable range?
System action
The user interface will issue a popup error message explaining that the session
request failed.
User response
This is an internal error. Contact IBM Software Support and be prepared to supply
the logs for the address space.
KOBGW0081E GW_Obtain_GWCVT_Address() returned NULL. rsn = error_reason, rsn2 =
error_reason2.
Explanation
A user interface session request failed to find a required anchor control block. The
reason codes may help determine the cause of the problem.
System action
The user interface will issue a popup error message explaining that the session
request failed.
User response
This is an internal error. Contact IBM Software Support and be prepared to supply
the logs for the address space.
KOBGW0083E Current session status is nnnn, requested status is
nnnn - invalid transition.
Explanation
A user interface session request supplied a status value that is an invalid state to
transition to from the current session status.
System action
The user interface will issue a popup error message explaining that the session
request failed.
User response
This is an internal error. Contact IBM Software Support and be prepared to supply
the logs for the address space.
KOBGW0084E Current session status is nnnn, requested status is
nnnn - invalid transition.
Explanation
A user interface session request supplied a status value that is an invalid state to
transition to from the current session status.
System action
The user interface will issue a popup error message explaining that the session
request failed.
User response
This is an internal error. Contact IBM Software Support and be prepared to supply
the logs for the address space.
KOBGW0085I Enhanced 3270 user interface session requests still active. Reply (Y)es to continue
waiting.
Explanation
A console command to STOP the KOBVTAM subcomponent has been issued but the user
interface component has one or more sessions with active requests. The address space has waited for
60 seconds in 5 second increments. After 60 seconds, this WTOR is issued allowing the operator to
extend the wait for active requests to complete by replying to the console message number with a
Y.
System action
If the response to the WTOR is Y, the address space will
wait up to another 60 seconds before reissuing the WTOR. If all user interface requests complete in
that period, termination of the KOBVTAM subcomponent will continue normally.
User response
This is an operator command WTOR. To continue waiting for active user interface
requests to complete, respond Y or y to the console
message. Any other response will result in sessions with active requests being forcibly terminated
and possibly unpredictable results.
KOBGW0086E KOBVTAM session TCB address address not found on session
chain.
Explanation
A user interface session request supplied a TCB address representing the current
session, but the session control block chain did not contain an entry containing the supplied
address.
System action
The user interface will issue a popup error message explaining that the session
request failed.
User response
This is an internal error. Contact IBM Software Support and be prepared to supply
the logs for the address space.
KOBGW0087E USS filepath: /tmp/zzz... open failed, fd = nn, errno =
xxxx, errno2= xxxx.
Explanation
The enhanced 3270 user interface attempted to open a file in
the z/OS
UNIX System Services /tmp path with file name based on job
name and job ID (e.g.,
/tmp/jobname.jobid.log).
System action
The enhanced 3270 user interface continues to run.
User response
This is an internal error. Contact IBM Software Support and be prepared to supply
the logs for the address space.
KOBGW0088E USS file close failed, fd = nn, errno = xxxx, errno2=
xxxx.
Explanation
The enhanced 3270 user interface attempted to close a file in
the z/OS
UNIX System Services /tmp path with the file name based on
job name and job ID (
/tmp/jobname.jobid.log).
System action
The enhanced 3270 user interface continues to run.
User response
This is an internal error. Contact IBM Software Support and be prepared to supply
the logs for the address space.
KOBGW0089E USS file path: /tmp/zzz... open failed, fd = nn, errno =
xxxx, errno2= xxxx.
Explanation
The enhanced 3270 user interface attempted to open or create
a file in the z/OS
UNIX System Services /tmp path with the file name based on
job name and job ID (
/tmp/jobname.jobid.log).
System action
The enhanced 3270 user interface continues to run.
User response
This is an internal error. Contact IBM Software Support and be prepared to supply
the logs for the address space.
KOBGW0090W Threshold parsing encountered an error in the following
statement:
Threshold member:
threshold_member_name
Statement:
statement_with_error
Explanation
The parsing of threshold input file threshold_member_name found
an error in threshold specification statement statement_with_error.
System action
Threshold parsing continues.
User response
Correct the syntax error in the threshold specification statement.
KOBGW0091W Threshold parsing completed with errors.
Explanation
The parsing of a thresholds input file found one or more errors in the threshold
specifications. These errors are reported in the preceding KOBGW0090W messages.
System action
The enhanced 3270 user interface continues to run.
User response
Correct the syntax errors in the threshold specification statements.
KOBGW0092E Allocation of command table failed. rc=return_code
Explanation
Allocation of the internal table containing operator command processing information
failed because sufficient storage is not available. storage
System action
The interface address space terminates.
User response
Contact IBM Software Support.
KOBGW0093E Initial setenv() failed rc = return_code, errno =
error_reason, errno2 = error_reason2.
Explanation
An operation to initialize an environmental variable during initialization of the
interface address space failed with the return and reason codes in the message.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0094E Allocation of session block header failed.
Explanation
Insufficient storage is available to allocate a control block required for user
interface session operations.
System action
The address space terminates.
User response
Try increasing the size of the region using the MEMLIMIT JCL parameter. If this
does not correct the problem, contact IBM Software Support.
KOBGW0095E Allocation of thresholding cache header failed.
Explanation
Insufficient storage is available to allocate a control block required for
thresholding operations.
System action
The address space terminates.
User response
Try increasing the size of the region using the MEMLIMIT JCL parameter. If this
does not correct the problem, contact IBM Software Support.
KOBGW0096E Deallocation of the command table failed. rc=return_code.
Explanation
A problem occurred during an attempt to deallocate the internal table containing
operator command processing information.
System action
The address space terminates.
User response
Contact IBM Software Support.
KOBGW0097W Dynamic load of modules into LPA requested but not supported. Modules loaded into private
area.
Explanation
Loading of function modules into the Link Pack Area was expected but was not
allowed by the operating system. This might be due to the SAF-based security for the installation
prohibiting the interface from performing dynamic LPA loading operations.
System action
Address space initialization continues by loading function modules into the
interface private area.
User response
If loading of function modules into LPA is required, and supported by the level of
operating system, check that the security controls established for loading and deleting modules
dynamically into and from LPA allow the interface to perform these operations. If
LPALOAD=Y is supplied as a parameter in the interface started task JCL, either
eliminating the parameter or coding LPALOAD=N will prevent this message from being
generated.
KOBGW0098E Allocate of function module LOAD parameter list failed.
Explanation
Insufficient storage is available to allocate the z/OS LOAD parameter list required
to load function modules into the enhanced 3270 user interface private area.
System action
The enhanced 3270 user interface address space terminates.
User response
Try increasing the size of the region using the REGION JCL parameter. If this does
not correct the problem, contact IBM Software Support.
KOBGW0099I Status thresholds could not be established from member_name. rc =
return_code
Explanation
The enhanced 3270 user interface initialization could not
establish thresholding for member member_name (CUASITE, IBMSITE, or
KppTHRSH, where pp is the 2-character product
code).
System action
Initialization of the address space continues.
User response
The THRESHOLDS_SOURCE environmental variable or the libraries in the RKANPAR DD
concatenation may specify the wrong DD name. Check to make sure the DD name is correct.
KOBGW0100W Open of threshold directory DD:directory_name failed. errno =
error_number, rsnno = error_reason.
Explanation
Initialization of the enhanced 3270 user interface could not
open the PDS directory allocation directory_name containing the status threshold
members.
System action
Address space initialization continues.
User response
Contact IBM Software Support.
KOBGW0101W Read of threshold directory directory_name failed. errno =
error_number, rsnno = error_reason.
Explanation
Initialization of the enhanced 3270 user interface could not
read the next member of the PDS directory containing the status threshold members.
System action
Initialization of the address space continues.
User response
Contact IBM Software Support.
KOBGW0102W Close of threshold directory directory_name failed. errno =
error_number, rsnno = error_reason.
Explanation
Initialization of the enhanced 3270 user interface could not
close the PDS directory containing the status threshold members.
System action
Initialization of the address space continues.
User response
Contact IBM Software Support.
KOBGW0103I Status thresholds successfully established from member
member_name.
Explanation
Initialization of the enhanced 3270 user interface address
space successfully established status thresholds from member
member_name.
KOBGW0104W Default thresholds refresh could not be completed - active UI evaluations.
Explanation
The enhanced 3270 user interface address space tried to
establish status thresholds but detected that one or more threshold evaluations are currently in
progress. The program waited, but the wait interval expired and threshold evaluation did not
finish.
System action
The enhanced 3270 user interface stops the attempt to
refresh status thresholds.
User response
Try refreshing the status thresholds later. If the problem persists, check the
enhanced 3270 user interface address space logs for related messages. If
further assistance is needed, contact IBM Software Support and supply the logs for the enhanced 3270 user interface address space.
KOBLI0001E Command registration in KOBLISTN subcomponent failed. rc =
return_code
Explanation
KOBLISTN failed to register for enhanced 3270 user interface
console commands.
System action
The KOBLISTN subcomponent returns and the enhanced 3270 user interface continues to wait for further console commands.
User response
This is an internal error. Contact IBM Software Support and supply the logs for the
enhanced 3270 user interface address space.
KOBLI0002E Command wait in KOBLISTN subcomponent failed. rc =
return_code
Explanation
KOBLISTN failed to establish the routine that waits for its registered enhanced 3270 user interface console commands.
System action
The KOBLISTN subcomponent returns and the enhanced 3270 user interface continues to wait for further console
commands.
User response
This is an internal error. Contact IBM Software Support and supply the logs for the
enhanced 3270 user interface address space.
KOBLI0003E Command deregistration in KOBLISTN subcomponent failed. rc =
return_code
Explanation
KOBLISTN failed to establish the routine that deregisters its registered enhanced 3270 user interface console commands.
System action
The KOBLISTN subcomponent returns and the enhanced 3270 user interface continues to wait for further console commands.
User response
This is an internal error. Contact IBM Software Support and supply the logs for the
enhanced 3270 user interface address space.
KOBLI0004E KOBLISTN STOP processing failed. rc = return_code
Explanation
The enhanced 3270 user interface STOP console command to
terminate the KOBLISTN subcomponent failed with the return code
rc.
System action
The KOBLISTN subcomponent will not be terminated by the current command. The
enhanced 3270 user interface will continue to wait for other console
commands.
User response
Use other messages preceding KOBLI0004E in addition to the return and reason codes
displayed to determine the cause of the problem.
KOBLI0005E KOBLISTN TRACE command processing failed. rc = return_code
Explanation
The enhanced 3270 user interface TRACE console command to
begin tracing for the KOBLISTN subcomponent failed with return code
return_code.
System action
The KOBLISTN subcomponent will not be able to process the TRACE command. The
enhanced 3270 user interface will continue to wait for other console
commands.
User response
Use other messages preceding KOBLI0004E in addition to the return code displayed to
determine the cause of the problem.
KOBLI0006E KOBLISTN command command not supported by command handler.
Explanation
The KOBLISTN command handling process does not support the command
command.
System action
The KOBLISTN subcomponent returns and the enhanced 3270 user interface continues to wait for further console
commands.
User response
This is an internal error. Contact IBM Software Support and supply the logs for the
enhanced 3270 user interface address space.
KOBLI0007I Processing command string =command
Explanation
The KOBLISTN command handling routine is processing the command
command.
KOBLI0008I The Trace Command supplied is command.
Explanation
The KOBLISTN subroutine is echoing the command
command.
KOBOD0000I ODI cache initialization has started.
Explanation
The Object Definition Interchange (ODI) cache initialization (which may involve
reading the DOC/ATR files for some applications) has started.
KOBOD0001I ODI cache initialization has completed.
Explanation
The Object Definition Interchange cache initialization, which might involve reading
the DOC/ATR files for some applications, has completed.
KOBOD0002I ODI cache termination has started.
Explanation
The Object Definition Interchange (ODI) cache termination (which involves releasing
all the storage for all applications in the cache) has started.
KOBOD0003I ODI cache termination has completed.
Explanation
The Object Definition Interchange cache termination (which involves releasing all
the storage for all applications in the cache) has completed.
KOBOD0004E Error opening file filename; rc=return_code,
errno=error_number, rsnno=reason_number.
Explanation
An error occurred trying to open the DOC or ATR file for an
application.
System action
The Object Definition Interchange (ODI) loader subcomponent stops processing the
DOC and ATR files for this application.
User response
Verify the file exists and that its file permissions allow the enhanced 3270 user interface address space to read it.
KOBOD0005E Error reading file filename; rc=return_code,
errno=error_number, rsnno=reason_number.
Explanation
An error occurred trying to read the DOC or ATR file for an
application.
System action
The Object Definition Interchange (ODI) loader subcomponent stops processing the
DOC and ATR files for this application.
User response
Verify the file exists in the files concatenated to the RKANDATV DD statement. If
the file is not there, check for it in TKANDATV and try to replace the file. If the file is already
in RKANDATV, try to access the file to verify its integrity. Also, check the log for
security-related messages or some other type of I/O error. If the file is there, and you can access
it, but the problem persists, or if the file is not present, call IBM Software
Support.
KOBOD0006E Error closing file filename; rc=return_code,
errno=error_number, rsnno=reason_number.
Explanation
An error occurred trying to close the DOC or ATR file for an
application.
System action
The Object Definition Interchange (ODI) loader subcomponent will try to use the DOC
and ATR files for this application, if there were no errors reading or parsing the
files.
User response
Verify the file exists and that its file permissions allow the enhanced 3270 user interface address space to read it. Set the permissions to allow
access if necessary.
KOBOD0007E Error parsing DOC/ATR files for application applid, product code
product_code; errno=error_number,
rsnno=reason_number
Explanation
A problem was encountered parsing the information from the DOC or ATR file for the
indicated application.
System action
The Object Definition Interchange (ODI) loader subcomponent continues processing
the DOC and ATR files looking for other parsing errors, but does not keep the information from these
files in the ODI cache.
User response
Since the DOC and ATR files are generated files, this error should only occur if a
file has been corrupted or altered. Restore the original versions of these files.
KOBOD0008E The DOC/ATR files for application applid, product code
product_code will not be used due to errors.
Explanation
The DOC and ATR files for the indicated application will not be used because errors
were encountered reading and parsing the ODI information from them.
System action
The Object Definition Interchange (ODI) loader subcomponent does not add the ODI
information for this application to the cache.
User response
Refer to earlier error messages to determine the root cause of the
error.
KOBOD0009E Error allocating memory for ODI cache. errno=error_number,
rsnno=reason_number
Explanation
An error occurred allocating memory to hold the Object Definition Interchange (ODI)
cache information for this application.
System action
The ODI loader subcomponent does not add the ODI information for this application
to the cache.
User response
The ODI cache is maintained in 64-bit virtual storage. Make sure the address space
has been given sufficient storage to use for the ODI cache. If necessary, increase the value of the
MEMLIMIT JCL parameter.
KOBOD0010E The requested application product ID, applid, is not a registered application.
Explanation
A request for the Object Definition Interchange (ODI) information was received for
an application product that is not registered with the OMEGAMON Enhanced 3270 user
interface.
System action
The ODI Loader subcomponent stops processing the request and returns an error
return code.
User response
The ODI cache is maintained in 64-bit virtual storage. Verify that the address
space has been given sufficient storage to use for the ODI cache. Verify that the runtime
environment was copied correctly. Also, check that the ODI is referenced in the KOBCFGAP and
KOBREGAP members of the data set that is referenced in the RKANPAR DDNAME concatenation list. If the
members are present and the ODI is correctly referenced, but the problem persists, contact IBM
Software Support.Capture the following diagnostic information:
- The OMEGAMON Enhanced 3270 user interface SYSPRINT log file
- A directory listing of the data sets referenced by the OMEGAMON Enhanced 3270 user interface
RKANDATV DD name
- A listing of the content for the members KOBCFGAP and KOBREGAP of the data set or data sets
referenced in the RKANPAR DDNAME concatenation list
KOBOD0011E The application product DOC file, KppDOC, was not found.
Explanation
The DOC file associated with an application could not be found by the Object
Definition Interchange (ODI) loader component. The file names are the PDS member names that were
used to locate the file. The pp value is the two-letter product code for the application that
has the file missing.
System action
The ODI loader subcomponent stops processing the DOC and ATR files for this
application.
User response
Verify that the KppDOC and KppATR files for the application product
are located in the appropriate PDS and that the location of the files is in the concatenation list
for the RKANDATV DDNAME statement.
KOBOD0012E The application product ATR file, KppATR was not found.
Explanation
The ATR file associated with an application could not be found by the ODI loader
component. The file names show the PDS member name and z/OS
UNIX System Services filename variations that were
used.
KOBOD0013E The requested product code, product_code, is not a registered
application.
Explanation
An Object Definition Interchange (ODI) refresh request was received for a product
code that is not registered with the enhanced 3270 user interface.
System action
The ODI loader subcomponent stops processing the request and returns an error
return code.
User response
Verify that the application has been properly installed and registered with the
enhanced 3270 user interface and retry the request.
KOBOD0014I ODI file filename opened successfully.
Explanation
The Object Definition Interchange (ODI) cache initialization process has opened a
file in preparation for reading its content as input to its internal cache.
System action
The ODI loader subcomponent will process the file contents as input to its internal
cache.
KOBOD0015E Command registration in KOBODISC subcomponent failed, rc=return_code,
errno=error_number, rsnno=error_reason
Explanation
The Object Definition Interchange (ODI) loader subcomponent failed to register for
enhanced 3270 user interface console commands.
System action
The ODI loader subcomponent will continue to run; however, it will not be able to
respond to console commands.
User response
This is an internal error. Contact IBM Software support and supply the logs for the
enhanced 3270 user interface address space.
KOBOD0016E Command wait in KOBODISC subcomponent failed, rc = return_code,
errno=error_number, rsnno=error_reason
Explanation
The Object Definition Interchange (ODI) loader subcomponent failed to establish the
routine that waits for its registered enhanced 3270 user interface console
commands.
System action
The ODI loader subcomponent will continue to run, but it will not be able to
respond to console commands.
User response
This is an internal error. Contact IBM Software Support and provide the logs for
the enhanced 3270 user interface address space.
KOBOD0017E Command deregistration in KOBODISC subcomponent failed, rc=return_code,
errno=error_number, rsnno=error_reason
Explanation
The Object Definition Interchange (ODI) loader subcomponent failed to establish the
routine that deregisters its registered enhanced 3270 user interface console
commands.
System action
The ODI loader subcomponent will continue its termination process.
User response
This is an internal error. Contact IBM Software Support and supply the logs for the
enhanced 3270 user interface address space.
KOBOD0018E KOBODISC STOP processing failed, rc=return_code,
errno=error_number, rsnno=error_reason
Explanation
The Object Definition Interchange (ODI) loader subcomponent encountered an error
while processing a console STOP command.
System action
The ODI loader subcomponent will continue its termination
process.
User response
This is an internal error. Contact IBM Software Support and supply the logs for the
enhanced 3270 user interface address space.
KOBOD0019I processing cmd string = command
Explanation
The Object Definition Interchange (ODI) component has received an operator
command.
System action
The ODI loader subcomponent will process the received command; for example, in the
case of the STOP command, it will terminate the ODI cache.