A duplicate LUNAME exists on the system and tracing of luname will not occur.
luname will not be traced.
Rename luname so that it is unique to the system.
INFO
There is a severe problem with the dialog trace facility (DTF) environment.
Dialog tracing is terminated.
Contact IBM® Software Support.
ERROR
A $SNAP macro was coded to request a snap of the registers or the registers and a storage area. The snap was called in module at offset offset.
TMS:Engine takes the requested snap and continues.
This is an IBM debugging tool developed for TMS:Engine applications, and it is specific to a particular product.
INFO
An abend occurred in module abndmod at offset abndoff.
TMS:Engine issues snap dumps of the environment, and processing continues.
Contact IBM Software Support.
LOG, VIEW
The system has been requested to capture a dump on the data set specified by the SYSMDUMP DD statement.
TMS:Engine requested the system to take a dump of the environment. A summary dump is also taken on RKLVSNAP.
Copy the dump to tape and contact IBM Software Support.
LOG, VIEW
An abend occurred at address in module.
TMS:Engine issues snap dumps of the environment, and processing continues.
Contact IBM Software Support.
ALERT
The dialog control verb &SYSECHO has been detected while evaluating an expression.
The requested text is logged.
None.
LOG, VIEW, REPLY
The TMS:Engine operator command, FLUSH, was issued to request the IBM VSAM data management services to write all pending VSAM records to the appropriate cluster. The request has completed successfully.
None.
None. To prevent accidental data loss, users are encouraged to leave the automatic FLUSH in RKANCMD(KLVSTART). To eliminate the automatic FLUSH, delete the statement from RKANCMD(KLVSTART).
The KLVSTART member in RKANCMD, which contains commands that are performed during TMS:Engine initialization, contains an EVERY 30:00 FLUSH command. This causes FLUSH to be issued every 30 minutes.
REPLY
The TMS:Engine operator command, FLUSH, was issued to request the IBM data management services to write all pending RKLVLOG records to the currently active RKLVLOG data set. The request has completed successfully.
None.
None.
REPLY
The TMS:Engine operator command, FLUSH, was issued to request the IBM data management services to write all pending Network Accounting Facility (NAF) records to the NAF data set or to SMF or both. The request has completed successfully.
None.
None.
REPLY
The integrity of the free storage area has been lost. This is caused by a storage overlay.
TMS:Engine will abend U0200 to terminate the address space.
Save the run sheets, dump files, and z/OS® system log, Then contact IBM Software Support.
REPLY
An invalid storage release request has been detected. This is may be caused by a storage overlay or an invalid address.
TMS:Engine will abend U0100 to terminate the requesting thread.
Save the run sheets, dump files, and z/OS system log. Then contact IBM Software Support.
ABEND
A request for storage exceeded the LIMIT parameter that was specified or implied at start-up.
For problem determination, a dump is generated with a user abend code.
Increase the limit parameter value and restart the product.
REPLY
A zero length storage request was made to TMS:Engine.
For problem determination, a dump is generated with a user abend code.
Contact IBM Software Support.
REPLY
The integrity of the free storage list has been corrupted.
For problem determination, a dump is generated with a user abend code.
Contact IBM Software Support.
REPLY
The integrity of the free storage area has been corrupted.
For problem determination, a dump is generated with a user abend code.
Contact IBM Software Support.
REPLY
TMS:Engine has used all available free storage and was unable to satisfy a storage allocation request.
For problem determination, a dump is generated with a user abend code.
Adjust the TMS:Engine MINIMUM and MAXIMUM parameters in the RKLVIN file and restart TMS:Engine.
REPLY
TMS:Engine has detected an invalid storage release request.
For problem determination, a dump is generated with a user abend code.
Contact IBM Software Support.
REPLY
The handle services initialization module has processed all input parameters and initialized the handle services environment without error.
Processing continues.
None.
INFO
The value specified in the keyword parameter was outside the range (min-max) shown. The default value default has been substituted.
Processing continues.
If the default value is unacceptable, modify the keyword parameter in your RKANPAR member KLVINHSM and restart TMS:Engine.
INFO
An attempt to register a thread anchor for handle services manager (HSM) failed.
HSM initialization is terminated.
Contact IBM Software Support.
ERROR
The address of the handle services manager vector table is zero.
handle services manager initialization is terminated.
Contact IBM Software Support.
ERROR
Module KLVINHSM logs its start-up parameters as they are read from RKANPAR. This is the header message and will be followed by message KLVHS006.
None.
None.
LOG
As the parameters in module KLVINHSM are read, a log audit trail is created.
None.
None.
LOG
The specified MAXPOOLS value pools was rounded to rpools. The specified MAXHANDLES value handles was rounded to rhandles. The rounded values will be used by the handle services manager.
Processing continues.
None.
INFO
During handle name deregistration or handle pool purge processing, a notify routine abended. t is the abend type (S)ystem or (U)ser and nnnn is the abend code. The abend code is three hexadecimal digits for a system abend and four decimal digits for a user abend. handle is the handle name. addr is the address of the handle name block within the handle pool. pool is the handle pool address. exit is the notify routine address. parm is the parameter passed to the exit. assoc is the 32-bit associated value for this handle name.
A dump is produced and cleanup processing for the handle name is terminated. Processing continues.
Contact IBM Software Support. Keep dump, RKLVLOG, SYSLOG, and runsheets.
ERROR
A request to initialize a handle pool could not be serviced because no empty table slot was available.
A dump is produced and the thread is terminated.
Contact IBM Software Support. Keep dump, RKLVLOG, SYSLOG, and runsheets.
ERROR
The handle services manager vector table was invalid during the processing of a handle services request.
A dump is produced and the thread is terminated.
Contact IBM Software Support. Keep dump, RKLVLOG, SYSLOG, and runsheets.
ERROR
The handle services manager return area ($HRA) was not large enough to allow required information to be returned during the processing of a handle services request.
A dump is produced and the thread is terminated.
Contact IBM Software Support. Keep dump, RKLVLOG, SYSLOG, and runsheets.
ERROR
The handle use count was already zero during the processing of a handle services request to release a handle.
A dump is produced and the thread is terminated.
Contact IBM Software Support. Keep dump, RKLVLOG, SYSLOG, and runsheets.
ERROR
This is the title line for the HSM Global Statistics display.
None.
None.
INFO
The maximum number of handle pools that can be allocated.
None.
None.
INFO
The maximum number of handles available in a single handle pool.
None.
None.
INFO
The total number of handle pools that are currently allocated and in use.
None.
None.
INFO
The total number of handles in use in all pools.
None.
None.
INFO
The total amount of storage currently in use by handle services. This storage is allocated above the 16 M line.
None.
None.
INFO
The total number of times the handle services manager performed a handle pool expansion.
None.
None.
INFO
The average number of handles in a handle pool.
None.
None.
INFO
The QUERYHSM command was issued with both the OWNERID= and POOLID= keywords specified.
Only GLOBAL statistics are displayed.
Re-enter the command with either POOLID= or OWNERID= specified.
INFO
This is the title line for the HSM Global Statistics Detail display.
None.
None.
INFO
This message is printed when the QUERYHSM GLOBAL DETAIL command is entered. It is printed once for each active handle pool. poolid is the handle pool ID, ownerid is the owning logical resource name, and poolsize is the handle pool size in bytes.
None.
None.
INFO
This message indicates that all the requested handle services manager statistics have been displayed.
None.
None.
INFO
The specified ownerid is not a valid logical resource number or was not 8 characters long. The owner ID must include all leading zeros.
Only GLOBAL statistics are displayed.
Issue QUERYHSM DETAIL command for a list of valid owner IDs and then reissue the QUERYHSM OWNERID= command specifying all 8 characters of the owner ID.
INFO
This is the title line for the handle pool owner ID statistics display.
None.
None.
INFO
This message is printed when the QUERYHSM OWNERID= command is issued. cccccccc is the owner ID and nn is the number of pools owned.
None.
None.
INFO
In addition to message KLVHS832, this message is printed when the QUERYHSM DETAIL OWNERID= command is issued. It is printed once, immediately following message KLVHS832, for each owned handle pool. poolid is the handle pool ID, nnnnnn is the size of the handle pool in bytes, and hhhhhh is the number of handles in the pool.
None.
None.
INFO
The value poolid was specified on a QUERYHSM command, but it is not a valid handle pool ID.
Only GLOBAL statistics are displayed.
Issue QUERYHSM DETAIL command to get a list of valid pool IDs. Then reissue the QUERYHSM POOLID= command with the correct pool ID.
INFO
This is the title line for the handle pool statistics display.
None.
None.
INFO
In addition to message KLVHS822, this message is printed when the QUERYHSM DETAIL POOLID= command is issued. It is printed immediately following message KLVHS822. handles is the total number of handles in the handle pool and inuse is the number of handles that are currently in use.
None.
None.
INFO
In addition to messages KLVHS822 and KLVHS843, this message is printed when the QUERYHSM DETAIL POOLID= command is issued. It is printed immediately following message KLVHS843. prisize is the initial number of handles in the handle pool and expsize is the number of new handles added to the pool each time it expands.
None.
None.
INFO
In addition to messages KLVHS822, KLVHS843, and KLVHS844, this message is printed when the QUERYHSM DETAIL POOLID= command is issued. It is printed immediately following message KLVHS844. nnn is the number of times the handle pool has been expanded.
None.
None.
INFO
This is the title line for the handle services manager storage isolation statistics display.
None.
None.
INFO
The values used to allocate the storage isolation pool used by handle services. prisize is the initial storage amount allocated and secsize is the additional amount of storage allocated each time the storage pool is expanded.
None.
None.
INFO
The amount of storage in the storage pool that is currently in use.
None.
None.
INFO
The maximum amount of storage in the storage pool that was ever in use.
None.
None.
INFO
The total amount of TMS:Engine storage currently allocated to the storage pool.
None.
None.
INFO
A failure has occurred in the handle services manager at the indicated location.
The HSM request is terminated.
Contact IBM Software Support.
LOG, ERROR
The intercommunications manager successfully established communications with node, usually as a result of the NODE command being issued.
None.
None.
INFO
The intercommunications manager has lost contact with node.
None.
None.
INFO
The intercommunications manager successfully completed initialization for node, usually as a result of the NODE command being issued.
None.
None.
INFO
Operator opid has logged on from device ocdev, causing this message to be logged as an audit trail.
None.
None.
INFO
Operator opid has logged off, creating this message to be logged as an audit trail.
None.
None.
INFO
The POSIX environment has been successfully established.
None.
This message is informational.
A fatal an unexpected error has occurred.
The process terminated.
Gather relevant logs and report this problem to IBM Software Support.
A fatal an unexpected error has occurred.
The process terminated.
Gather relevant logs and report this problem to IBM Software Support.
During TMS:Engine start-up, the TMS:Engine dispatcher started the identified task to perform its work. The displayed fields contain information useful for IBM diagnostic efforts.
None.
None.
LOG
During TMS:Engine start-up the command library, DD name RKANCMD, could not be accessed. It is probably not present in the TMS:Engine JCL procedure.
Any data contained in the command library is unavailable.
Refer to the z/OS system log for any IBM data management messages (IEC). Determine the reason the command library could not be opened, correct it, and restart TMS:Engine.
WARNING
During TMS:Engine start-up, module modname with sequence number num will be invoked. If an initialization parameter member of RKANPAR is found for this module, it is identified as member in the message. The entry-point address will only be included in the message if debug mode is in effect.
None.
None.
LOG
During TMS:Engine start-up, module modname detected an error. r15 should have a nonzero value.
TMS:Engine is terminated after any subsequent start-up modules are invoked.
Examine the TMS:Engine log data set for additional messages to determine a more specific reason for the error. Correct it, and restart TMS:Engine.
ALERT
After TMS:Engine is successfully started, any pending messages are written to the log so that start-up messages may be viewed by the site to determine if the TMS:Engine environment was correctly established.
None.
None.
LOG
TMS:Engine version ver is up and running on system smfid. The variable nnn refers to the address of the Global Storage Area, the TMS:Engine primary control block.
None.
None.
INFO
During TMS:Engine start-up the parameter library, DD name RKANPAR, could not be accessed. It is probably not present in the TMS:Engine JCL procedure.
Any data contained in the parameter library is unavailable.
Refer to the z/OS system log for any IBM data management messages (IEC). Determine the reason the command library could not be opened, correct it, and restart TMS:Engine.
WARNING
The INITLIST keyword was coded and member is being processed for start-up member name overrides.
None.
None.
INFO
The contents of the INITLIST member are echoed in override-statement.
None.
None.
INFO
An override statement references a start-up module that is not present in this TMS:Engine address space.
The override is ignored and processing continues.
Correct the override statement and restart the TMS:Engine address space if necessary.
WARNING
member could not be found in RKANPAR.
The start-up is terminated.
Correct the INITLIST keyword to specify a valid member name and restart the TMS:Engine address space.
ERROR
member could not be found in RKANPAR for start-up module module. This message will only be issued if the override member name differs from the default.
The start-up is terminated.
Correct the INITLIST member to specify a valid override member name and restart the TMS:Engine address space.
ERROR
A syntax error was encountered while parsing an Inter-Process Communications (IPC) command buffer. The contents of the command buffer is displayed in the ddddddddddddddddddddddd field of the message.
The command is ignored.
Contact IBM Software Support.
VIEW
A service other than CREATE, DESTROY, DEQUEUE, PUSH, ACCESS, ALARM, or QUEUE was requested from IPC.
The dialog is terminated.
If this error occurred in a user-created dialog, correct the error and restart the dialog process. If this error occurs while running any other IBM Tivoli® product, contact IBM Software Support.
VIEW
The CL/CONFERENCE logging facility is unavailable.
Using the RC and service name, determine the cause of the error, correct it, and restart TMS:Engine.
ERROR
An internal error occurred while processing a lock.
TMS:Engine terminates.
Contact IBM Software Support.
ALERT
TMS:Engine detected a main storage shortage. To recover from the shortage, TMS:Engine will not accept any logons.
Users cannot logon or start a session.
None. However, if these messages occur frequently on your system, you should examine the memory allocation parameters that are in effect. These are the RKLVIN keywords MINIMUM, MAXIMUM, and RESERVE.
ALERT
TMS:Engine detected main storage availability and released the quiesce caused by main storage shortage.
TMS:Engine will now allow users to logon or start a session.
None.
REPLY
While accessing the logical resource table, an integrity error was detected.
For problem determination, a dump is generated with a user abend code.
Contact IBM Software Support.
The TMS:Engine logical resource manager detected an error during resource purge or cleanup processing and has bypassed a purge/cleanup exit to avoid further problems.
A dump is produced because DEBUG(Y) is in effect. Some resources and storage may be hung.
Contact IBM Software Support.
The TMS:Engine logical resource manager detected an error during resource purge or cleanup processing and has bypassed a purge/cleanup exit to avoid further problems.
Some resources and storage may be hung.
Copy the exact contents of the message and contact IBM Software Support. Be sure to include the debugging data fields resnum1, resname, and resnum2 contained in the message.
An error was encountered while processing a resource manager request.
The current request is ignored and a U0100 abend is generated to supply information for the logic error.
Acquire the dump from the U0100 abend and contact IBM Software Support.
REPLY
The maximum number of logical resources has been exceeded.
The current request is ignored. The system will continue running. As resources are freed, new resources can be created, but the stability of the system is unpredictable since it is not known what resources will be rejected.
Reduce activity on the system and contact IBM Software Support.
ALERT
In response to the TLVLOG TMS:Engine operator command, this message shows where TMS:Engine messages are currently being written to. ddname is the ddname being used for RKLVLOG.
None.
None.
REPLY
In response to the TLVLOG TMS:Engine operator command, this message shows the maximum number of lines that will be written to the currently active RKLVLOG before an automatic TLVLOG SWITCH is performed.
None.
None.
If the value is zero, there is no maximum.
REPLY
In response to the TLVLOG, TMS:Engine operator command, this message shows the number of lines that have been written to the currently active RKLVLOG.
None.
None.
REPLY
In response to the TLVLOG TMS:Engine operator command, this message reports that an error has caused TMS:Engine to stop writing messages to the RKLVLOG file. ddname is the name of the DD to which TMS:Engine had been recording.
None.
Issue TLVLOG SWITCH to attempt to allocate a new RKLVLOG dynamically.
REPLY
In response to the TLVLOG TMS:Engine operator command, this message precedes a set of KLVLW012 messages that show the values that will be used for the next RKLVLOG dynamic allocation.
None.
None.
REPLY
| Keyword | Value |
|---|---|
| CLASS | The SYSOUT class. |
| COPIES | The number of copies. |
| DEST | The SYSOUT destination, if any. |
| FCD | The FCB name, if any. |
| FORM | The FORM name, if any |
| HOLD | Whether the SYSOUT file will be placed in a operator hold (YES) or note (NO). |
| UCS | The UCS name, if any. |
| USER | The user ID associated with the SYSOUT destination, if any. |
| WTRNAME | The external writer name, if any. |
None.
None.
REPLY
In response to a TLVLOG SWITCH request, TMS:Engine has dynamically allocated a SYSOUT field and is now writing RKLVLOG messages to it. ddname is the new ddname.
None.
None.
REPLY
In response to a TLVLOG SWITCH request, TMS:Engine has closed and dynamically deallocated the previous RKLVLOG file. ddname is the ddname.
None.
None.
REPLY
An invalid COPIES value was entered on a TLVLOG command. Only an integer between 1-254 is accepted.
The command terminates.
Reissue the command with a valid COPIES value.
ERROR
An invalid MAXLINES value was entered on a TLVLOG command. Only an integer between 0-16000 is accepted.
The command terminates.
Reissue the command with a valid MAXLINES value.
ERROR
An invalid HOLD value was entered on a TLVLOG command. Only YES or NO is accepted.
The command terminates.
Reissue the command with a valid HOLD value.
ERROR
A TLVLOG SWITCH request has been accepted. TMS:Engine will allocate a new RKLVLOG SYSOUT file and begin recording on it. Then close and release the old RKLVLOG file. This message is followed by KLVLW022 and KLVLW023, which report successful processing.
None.
None.
REPLY
A BSAM WRITE issued against the currently active RKLVLOG file failed because of a permanent error.
RKLVLOG recording is suspended.
TLVLOG SWITCH
ALERT
A TLVLOG SWITCH request
was not
successful because the dynamic allocation for a new SYSOUT file failed.
rc is the return code from the DYNALLOC request; error and info are
the error and information reason codes.
The command terminates. The previous RKLVLOG is still active.
Refer to RKLVLOG or VIEWLOG for any KLVDAnn messages that may have been issued. Refer to IBM z/OS MVS Programming: Authorized Assembler Services Reference (GC28-1764 through GC28-1767) for DYNALLOC return codes.
LOG, ERROR
A TLVLOG SWITCHrequest could not open a dynamically allocated SYSOUT file. ddname is the ddname that could not be opened.
The command terminates. The previous RKLVLOG is still active; ddname remains allocated to the TMS:Engine address space.
Refer to SYSLOG for any IEFxxxxx messages that may describe the OPEN error.
LOG, ERROR
A TLVLOG SWITCH request could not dynamically deallocate the RKLVLOG JCL DD statement. rc is the return code from the DYNALLOC request; error and info are the error and information reason codes.
The RKLVLOG JCL DD statement remains allocated to the TMS:Engine address space. Refer to IBM z/OS MVS Programming: Authorized Assembler Services Reference for DYNALLOC return codes.
LOG, ERROR
The pseudo-operator *SYSTLG* could not be initialized.
*SYSTLG* will not be recognized if specified with the AS operator command. All other RKLVLOG processing continues normally.
If you are using operator validation in a NAM user exit (for example, KLVA2NEV), ensure that the *SYSTLG* operator is authorized for logon.
LOG, ERROR
This is the header of the response to a TLVLOG STATS command. It will be followed by additional KLVLWnnn messages containing the various RKLVLOG counters.
Processing continues.
None.
The indicated number of lines have been written to RKLVLOG.
Processing continues.
None.
The indicated number of buffer writes to RKLVLOG have been performed because the buffer was full.
Processing continues.
None.
The indicated number of writes to RKLVLOG have been performed in response to operator requests.
Processing continues.
None.
The system needed to wait the indicated number of times for an available log buffer.
Processing continues.
None.