The following table lists and describes messages starting with KT.
Types of messages starting with KT
Wait until all pending commands have finished execution before taking corrective action.
-
KTA: Tiered Storage Manager for Mainframe license
-
KTC: Syntax error related to CLI commands
-
KTD: Syntax error, format error, or I/O error related to Tiered Storage Manager for Mainframe files
-
KTG: Troubleshooting function such as logging
-
KTH: I/O processing
-
KTM: Messages output to the ISPF panel or the ISPF log
-
KTR: REXX variable
-
KTX: XML format error
-
KTZ: Common messages for Tiered Storage Manager for Mainframe
Message ID |
Message text |
Explanation and recommended actions |
---|---|---|
KTA001I ISPF |
The license key(s) has been installed. |
The license key has been installed. |
KTA051E ISPF |
An error occurred in the license information dataset. |
An error occurred in the license information dataset. Make sure that the prefix of the license information dataset has been registered correctly, and that the license information dataset has been created correctly. For details on how to register the prefix of the license information dataset, see the Tiered Storage Manager for Mainframe User Guide. |
KTA052E ISPF |
An error occurred in the license key dataset. |
An error occurred in the license key dataset. Make sure that the name of the license key dataset is correct, and that the license key dataset has been created correctly. If necessary, re-create the license key dataset and transfer the license key file again. |
KTA071W ISPF |
The license key was not found. |
An attempt was made to install a license key, but a license key that could be installed in the license key dataset was not found. Check whether one of the following conditions exists:
|
KTA072W ISPF |
Couldn't install the license key. |
The license key could not be installed. Check whether one of the conditions below exists. If neither condition exists, make sure that the key code is correct.
|
KTA080E MSG CON SC=36 RC=36 |
The expiration date for your license key(function). |
The license for the function indicated by function has expired. To continue using the product, you need a permanent license. |
KTA081W MSG CON SC=0 RC=0 |
Your function license will expire in n day(s). |
Your license for the function indicated by function will expire in n days. To continue using the product after the expiration date, you need a permanent license. |
KTA087E MSG SC=40 RC=40 (file) |
Couldn't read license information dataset. |
The license information dataset could not be read. Check whether the name of the license information dataset is correct, and whether the license information dataset was correctly created. If necessary, re-create the license information dataset, and install the license key again. |
KTA291E MSG SC=36 RC=36 |
function is not licensed for use on this system. |
The licenses key for the function indicated by function is not correctly installed or recognized. Check whether the installed license key is for the current version. |
KTA400I CON |
Environment variables (version) |
This message indicates Tiered Storage Manager for Mainframe environment information. |
KTA401I CON |
variable: value |
This message indicates Tiered Storage Manager for Mainframe environment settings. |
KTA402I CON |
varname = value-1 (symbol = value-2) |
This message indicates the specified values for the Tiered Storage Manager for Mainframe environment variables and system symbols. |
KTA403I CON |
product-name |
This message shows the program product name. |
KTC000T TSO RC=48 |
command-name: Supplied parameters invalid, reason code=rrrr. |
An invalid parameter was specified. For details about reason code rrrr, see the description of IKJPARS in the IBM manual TSO/E Programming Services. |
KTC001E TSO PRT SC=48 RC=48 |
command-name: No parameter-name parameter supplied. |
No parameter was specified in parameter-name. |
KTC002E TSO SC=48 RC=48 |
parameter-name parameter value does not include trailing ".". |
The last character of the string specified by parameter-name is not a period. |
KTC003E TSO PRT SC=48 RC=48 |
parameter-name parameter value is invalid. |
The value specified by parameter-name is invalid. |
KTC004E TSO SC=48 RC=48 |
"SYSAUTH." cannot be specified in parameter-name parameter. |
SYSAUTH. cannot be specified for parameter-name. Specify another name. |
KTC005E TSO PRT SC=48 RC=48 |
parameter-name parameter value is too long. |
The character string specified by parameter-name is too long. |
KTC007E TSO SC=48 RC=48 |
Starting parameter-name-1 parameter value exceeds ending parameter-name-2. |
The starting value (minimum value) specified by parameter-name-1 exceeds the exit value (maximum value) specified by parameter-name-2. |
KTC008E TSO SC=48 RC=48 |
parameter-name parameter value is not valid hex. |
The value specified by parameter-name is not in hexadecimal format. |
KTC009E TSO PRT SC=48 RC=48 |
Parameter combination is invalid. |
The specified combination of parameters is invalid. For specifiable combinations of parameters, see the Tiered Storage Manager for Mainframe User Guide. |
KTC012E TSO SC=48 RC=48 |
IODESTID parameter is allowed only on 1st call of KTLOAD. |
You can specify the IODESTID parameter only when you execute the KTLOAD command for the first time. |
KTC099I PRT SC=0 |
command-name command return code=nnnn |
The command-name command ended with the return code nnnn. |
KTC310I SYS |
hh:mm:ss command |
This log message indicates that a CLI command was issued. |
KTC311I SYS |
hh:mm:ss command RC=rc |
This log message gives the execution results of a CLI command. |
KTC910I CON |
command |
This log message indicates that a CLI command was issued. |
KTC911I CON |
command RC=rc |
This log message gives the execution results of a CLI command. |
KTD085E MSG SC=40 RC=40 (file:rec#) |
Unable to read the configuration file. |
The configuration file (file) could not be read because the record length is too long. |
KTD086E MSG TSO SC=40 RC=40 (file) |
File status is:dsstate |
The configuration file (file) cannot be used. If the message IKJ58211I is displayed at the same time as this message, check the value of the DYNAMNBR parameter specified in the JCL EXEC statement. For details about the value to be specified, see the description of the KTSTORE or KTIMPORT command in the Tiered Storage Manager for Mainframe User Guide. If an attribute of the configuration file is abnormal, one of the following messages is output:
XX is the file attribute value that caused the error. YY is the correct file attribute value. |
KTD088E MSG SC=40 RC=40 (file) |
File Open error[: dsstate]. |
An attempt to open the configuration file (file) failed. |
KTD089E MSG SC=40 RC=40 (file) |
File Close error: dsstate. |
An attempt to close the configuration file (file) failed. |
KTD090E MSG SC=40 RC=40 (file) |
File Allocation Failed[: dsstate]. |
Configuration file (file) could not be allocated. Make sure that configuration file (file) has been created correctly. |
KTD091E MSG SC=40 RC=40 (file) |
File Deallocation Failed: dsstate. |
Configuration file (file) could not be deallocated. |
KTD092E MSG SC=40 RC=40 (file) |
File Read error[: dsstate]. |
Configuration file (file) could not be read. |
KTD093E MSG PRT SC=40 RC=40 (file) |
An error occurred during file output. EXECIO RC =n |
An attempt to create or update the configuration file failed due to a failure in the TSO/E REXX EXECIO command (return code n). For details, see the IBM manual TSO/E REXX Reference. |
KTD200E MSG SC=32 RC=32 (file rec#) |
name is not specified in Tiering Policy information CSV file. |
Item (name) is not specified in the tiering policy CSV file (file). |
KTD201E MSG SC=32 RC=32 (file rec#) |
The value of name in the tiering policy information CSV file is invalid. |
The value (value) specified for the item (name) in the tiering policy CSV file (file) is not correct. Check the following:
|
KTD202E MSG SC=32 RC=32 (file rec#) |
The value of name in the tiering policy information CSV file is too long. |
The value (value) of item (name) in the tiering policy CSV file (file) is too long. |
KTD203I MSG SC=4 RC=4 (file) |
No Tiering Policy Group is defined in the specified the tiering policy information CSV file. |
No tiering policy group is defined in the tiering policy CSV file (file). A TPG definition file was not created because there was no valid record. |
KTD204E MSG SC=32 RC=32 (file rec#) |
The number of items specified for a line in the tiering policy information CSV file is invalid. |
The number of items specified for a line in the tiering policy CSV file (file) is invalid. |
KTD206E MSG SC=32 RC=32 (file rec# value) |
The specified volume does not exist in the disk configuration definition file. |
The specified volume does not exist in the disk configuration definition file. The volume specified in the tiering policy CSV file or in the I/O destination device definition file (file) must exist in the disk configuration definition file. Scan the specified volume, and then execute the command. Alternatively, execute the KTIMPORT command with the SCAN parameter specified. If a Non Gen'ed volume is specified by using a dummy device number, assign the dummy device number, and then execute the command. |
KTD207E MSG SC=32 RC=32 (file rec# value) |
The specified volume is not a tiering volume. |
The specified volume or a volume included in the specified SMS storage group is not a Dynamic Tiering for Mainframe volume. Specify a Dynamic Tiering for Mainframe volume in the tiering policy CSV file (file). In addition, the error might have occurred because the microcode version of the storage system is not supported. Check whether the microcode version of the storage system is supported. |
KTD208E MSG SC=32 RC=32 (file rec# storage-group-name) |
No volumes belong to the specified storage group storage-group-name. |
No volume belongs to the SMS storage group (storage-group-name). |
KTD209E MSG SC=36 RC=36 (file) |
SUPFNC SUPFnc does not support function-name. |
The function indicated by function-name cannot be used by this storage system. Use a device# that supports the function indicated by function-name. If you did not perform a scan after replacing the storage system microcode, perform a scan.
|
KTD210W MSG SC=4 RC=4 (file) |
The Relocation Priority value that is specified for devn was disabled because of SUPFNC(SUPFnc). |
The Relocation Priority value specified for this device was disabled. Use a device# for which Relocation Priority is supported. If you did not perform a scan after replacing the storage system microcode, perform a scan. |
KTD211E MSG SC=48 RC=48 (file rec#) |
The ending value must not be lower than the starting value. |
The specified end value of the range is smaller than the start value. |
KTD212E MSG SC=36 RC=36 (file rec# storage-group-name) |
No volumes belong to the wildcard-designated storage group storage-group-name. |
No volumes belong to the SMS storage group (storage-group-name) specified by using wildcard characters. |
KTD213E MSG SC=36 RC=36 (file rec# storage-group-name) |
Information about the wildcard-designated storage group storage-group-name could not be retrieved. |
Information could not be acquired about the SMS storage group (storage-group-name) that was specified by using wildcard characters. The probable causes of the failure are as follows:
|
KTD214E MSG SC=32 RC=32 (file rec# value) |
The volumes in the specified range, wildcard-designated volumes, or volumes that belong to the wildcard-designated storage group do not exist in the disk configuration definition file. |
The volumes specified by using range specification, volumes specified by using wildcard characters, or volumes that belong to the SMS storage group specified by using wildcard characters do not exist in the disk configuration definition file. The volumes specified in the tiering policy CSV file (file) must exist in the disk configuration definition file. Scan the target volumes before executing the KTIMPORT command. Alternatively, execute the KTIMPORT command with the SCAN parameter specified.
|
KTD215E MSG SC=32 RC=32 (file rec# value) |
The volumes in the specified range, wildcard-designated volumes, or volumes that belong to the wildcard-designated storage group are not tiering volumes. |
The volumes specified by using range specification, volumes specified by using wildcard characters, or volumes that belong to the SMS storage group specified by using wildcard characters are not the Dynamic Tiering for Mainframe volumes. Specify the Dynamic Tiering for Mainframe volumes in the tiering policy CSV file (file). In addition, the error might have occurred because the microcode version of the storage system is not supported. Make sure that the microcode version of the storage system is supported.
|
KTD216W MSG SC=4 RC=4 (file rec# value) |
The specified volume does not exist in the disk configuration definition file. |
The specified volume does not exist in the disk configuration definition file. This volume was skipped and processing continued.
|
KTD217W MSG SC=4 RC=4 (file rec# value) |
The specified volume is not a tiering volume. |
The specified volume is not a Dynamic Tiering for Mainframe volume. Alternatively, a volume that is not a Dynamic Tiering for Mainframe volume is included in the specified SMS storage group. The volume that was not a Dynamic Tiering for Mainframe volume was skipped and processing continued.
|
KTD218W MSG SC=4 RC=4 (file rec# storage-group-name) |
No volumes belong to the specified storage group storage-group-name. |
No volumes belong to the specified SMS storage group (storage-group-name). This SMS storage group was skipped and processing continued. |
KTD219W MSG SC=4 RC=4 (file rec# value) |
The tiering volumes specified by the record do not exist. |
No Dynamic Tiering for Mainframe volume exists in the specified range. The target volume does not exist in the disk configuration definition file. Alternatively, the target volume is not a Dynamic Tiering for Mainframe volume. This record (rec#) was skipped and processing continued.
|
KTD220W MSG SC=4 RC=4 (file rec# storage-group-name) |
No volumes belong to the wildcard-designated storage group storage-group-name. |
No volumes belong to the SMS storage group (storage-group-name) specified by using wildcard characters. No SMS storage groups that match the specified wildcard characters exist. Alternatively, no volumes are defined in the SMS storage group that matches the specified wildcard characters. |
KTD230W MSG SC=4 RC=4 (file) |
The Relocation Priority value that is specified for SN=serial-number,CU/CCA=device-address was disabled because of SUPFNC(SUPFnc). |
The Relocation Priority value that is specified for this device was disabled. Use a device# that supports Relocation Priority. Also, if you did not perform a scan after replacing the storage system microcode, perform a scan.
|
KTD260E MSG SC=44 RC=44 |
Too long record:record. |
The attempt to output the record to the dataset failed because the length of the record (record) exceeds 252 characters. The value of the REXX variable is incorrect. Check and revise the REXX variable so that the length of the record is no more than 252 characters. |
KTD270E MSG TSO SC=40 RC=40 |
Failed to create the configuration file. (name =dataset-name,op,dsstate) |
Creation of the configuration file will stop because an error occurred during creation. Revise the environment based on the information indicated in the message, and then try to create the configuration file again. For details about corrective actions, see the message that is output concurrently with this message.
|
KTD285E MSG PRT SC=48 RC=48 |
filename is too long for a filename. |
File name filename is too long. The file name is made up of the values of the specified parameters. Shorten the parameter lengths so that the file name is no longer than 44 characters. |
KTD920E MSG RC=48 |
The parameter is invalid. param=parameter-name,reason=reason-code,record number=record-number |
The parameter-name parameter in the I/O destination device definition file is invalid. Check the reason by using reason-code, and then revise the description of the record displayed in record-number. |
KTD921E MSG RC=48 |
The parameter operand is invalid. param=parameter-name,OP=operand-name,reason=reason-code,record number=record-number |
The operand-name operand of the parameter-name parameter in the I/O destination device definition file is invalid. Check the reason by using reason-code, and then revise the description of the record displayed in record-number.
|
KTD922E MSG RC=48 |
The value of the parameter operand is invalid. param=parameter-name,OP=operand-name,reason=reason-code,record number=record-number |
An invalid value was specified for the operand-name operand of the parameter-name parameter in the I/O destination device definition file. Check the reason by using reason-code, and then revise the description of the record displayed in record-number. |
KTD923E MSG RC=48 |
The value of the parameter suboperand is invalid. param=parameter-name,OP=operand-name,POS=pos,reason=reason-code,record number=record-number |
Of the operand-name operand of the parameter-name parameter in the I/O destination device definition file, the value of the suboperand at the position indicated by pos is invalid. Check the reason by using reason-code, and then revise the description of the record displayed in record-number. |
KTD924E MSG RC=48 |
The required parameter is not specified. parm=parameter-name |
A required parameter (parameter-name) is not specified in the I/O destination device definition file. |
KTD928E MSG RC=48 |
The number of continuation lines exceeded the upper limit. record number=record-number |
The I/O destination device definition file contains a continuation symbol, and the maximum number of continuous lines has been reached. |
KTD929E MSG RC=48 |
An invalid continuation line was detected. |
The I/O destination device definition file contains a continuation symbol, but there is no subsequent line. |
KTG001I MSG SC=0 RC=0 |
message-count message(s) were not stored in the REXX variable due to buffer overflow. |
The number of messages indicated by message-count could not be stored in the message structure because there are too many output messages to be retained in the internal buffer. |
KTG003I ISPF SC=0 RC=0 |
message-count message(s) are not displayed in the message list because the number of messages exceeds 999. |
The number of messages indicated by message-count could not be displayed in the message list because the number of output messages exceeds 999. |
KTG004I ISPF SC=0 RC=0 |
message-count message(s) are not displayed in the message list due to internal buffer overflow. |
The number of messages indicated by message-count could not be displayed in the message list because there are too many output messages to be retained in the internal buffer. |
KTG207E MSG TSO CON SC=52 RC=0 |
A log stream process error occurred. (detail=message-text, cmd=xxx, pos=yyy) |
The command cannot be executed because a log stream process error occurred.
|
KTG215W MSG CON SC=0 RC=0 |
A GTRACE error occurred. (return code=nnn, id=mmm, length=lll, cmd=xxx, pos=yyy) |
A GTRACE macro error occurred. If this message is often displayed, stop acquisition of the GTF trace specified for USR trace (TRACE=USR). If the cause of the error is insufficient capacity of the trace buffer or trace dataset, expand the capacity and then restart GTF.
|
KTG217E MSG CON PRT SC=0 RC=0 |
A Logger error occurred. (return code=nnn, reason code=mmm, name=name, cmd=xxx, pos=yyy) |
An error occurred in the system logger service.
|
KTG218I CON PRT RC=0 |
Output log count=nnn. |
The number of log messages that have been output is nnn. |
KTG261E MSG CON SC=0 RC=0 |
The YKLOGnn DD statement is not specified. (cp=xxx:yyy) |
The DD statement for YKLOG01 or YKLOG02 is not specified. |
KTG262E MSG CON SC=0 RC=0 |
A YKLOGnn open error occurred. (rc=nnn, cp=xxx:yyy) |
A YKLOG01 or YKLOG02 open error occurred. |
KTG263E MSG CON SC=0 RC=0 |
A YKLOGnn I/O error. (text, cp=xxx:yyy) |
A YKLOG01 or YKLOG02 I/O error occurred. |
KTG264E MSG CON SC=0 RC=0 |
A YKLOGnn close error occurred. (rc=nnn, cp=xxx:yyy) |
A YKLOG01 or YKLOG02 close error occurred. |
KTG267E MSG CON SC=0 RC=0 |
A YKLOGnn DEVTYPE macro error occurred. (rc=nnn, reason=mmm, cp=xxx:yyy) |
An error occurred in the DEVTYPE macro for YKLOG01 or YKLOG02.
|
KTG291I CON SC=0 RC=0 |
The log dataset is full. (DSN=ddd, cp=xxx:yyy) |
The log dataset is full.
|
KTG292I CON SC=0 RC=0 |
The log dataset was switched. (from=YKLOGmm, to=YKLOGnn, job=jjj, cp=xxx:yyy) |
The log dataset was switched.
|
KTH004E MSG SC=48 |
Specified DEVN is not found. |
The device having the device number specified for the DEVN parameter or IODEVN parameter was not found. Alternatively, a device other than DASD or an ALIAS volume for PAV was specified. |
KTH033I MSG SC=4 RC=4 (count) |
The specified devices that had no available I/O paths were skipped. |
As a result of a scan, information acquisition was skipped for the devices on which no I/O paths were available. |
KTH251E MSG TSO SC=32 RC=32 (volume-ID) |
DASD device device-number-1(device-number-2) management error, message-text. (code-1 code-2, cmd=xxx, pos=yyy) |
The requested processing could not be performed. This device was skipped and processing continued. Check the status of the device that caused the error, correct any error in the configuration or execution conditions, and then re-execute the command.
|
KTH253E MSG TSO SC=32 RC=32 (volume-ID) |
DASD device device-number-1(device-number-2) I/O error. (CC=code-1 CSW=code-2 code-3 code-4 code-5, cmd=xxx, pos=yyy) |
An I/O error occurred. This device was skipped and processing continued. If sense byte information has been set, the KTH255E message displays the sense byte information.
|
KTH255E MSG TSO SC=32 RC=32 (volume-ID) |
DASD device device-number-1(device-number-2) sense: diagnostic-information (cmd=xxx, pos=yyy) |
This message displays detailed information for an I/O error.
|
KTH257E MSG TSO SC=32 RC=32 (volume-ID) |
DASD device device-number-1(device-number-2) management error. (Message type: code-1 Reason code: code-2 Error code: code-3 code-4, cmd=xxx, pos=yyy) |
The requested processing could not be performed. This device was skipped and processing continued. Check the status of the device that caused the error, correct any error in the configuration or execution conditions, and then re-execute the command.
|
KTH410E MSG SC=12 RC=12 (volume-ID) |
The command cannot be executed because the device (devn) is not supported. (SUPFnc,command) |
The command was not issued because this device is not supported. Use a device# that is supported by Tiered Storage Manager for Mainframe. Also, if you did not perform a scan after replacing the storage system microcode, perform a scan.
|
KTH500E MSG SC=48 RC=48 |
SN parameter value is different from the serial number of the storage system that belongs to the device set for IODEVN. |
The value specified for the SN parameter does not match the serial number of the storage system containing the volume specified for the IODEVN parameter. |
KTH510E MSG SC=48 RC=48 |
SUPFNC SUPFnc does not support NG scan. |
This storage system cannot perform NG scans. Use a device that supports NG scans.# |
KTM012E ISPF |
The End Devn value must not be lower than the Start Devn |
The device number specified in End is lower than the device number specified in Start. |
KTM014E ISPF |
The member name specified in COMMAND is invalid. Check the specified member name, or check whether the specified member exists. |
The member name specified in COMMAND is invalid. Check the specified member name, and check whether the specified member exists. |
KTM015I LOG |
RC:nn CMD:command MODID:modid |
The command indicated by command was issued, and ended with the return code nn. |
KTM016W LOG |
SEV:nn TEXT:message-text VALUE:message-value |
The command output the following information to the message structure, and then ended. |
KTM018I LOG |
RC:rc RS:rs CMD:command MODID:modid |
The command indicated by command was issued, and ended with the return code rc. |
KTM021E ISPF |
Check Storage Group, Volser or Device Number. |
Specify / for one of Storage Group, Volser, or Device Number. |
KTM022E ISPF |
The End Volser value must not be lower than the Start Volser |
The volume serial number specified in End is lower than the one specified in Start. |
KTM023E ISPF |
Invalid value |
The value is invalid. |
KTM025E ISPF |
Enter 0 or a numeric value from 10 to 5000 |
Enter 0 or a numeric value from 10 to 5000. |
KTM027E ISPF |
Failed to create a data set. |
An attempt to create a data set failed. |
KTM028E ISPF |
Point-and-shoot on AC to access Actions or enter "/". |
Either point-and-shoot AC field, or specify a forward slash (/) for AC field to display the action selection panel. |
KTM029E ISPF |
Enter one of the listed values. |
Enter a listed value. |
KTM031E ISPF |
You cannot specify the apostrophe. |
An apostrophe cannot be specified. |
KTM523E ISPF |
You cannot enter values to both License Key Dataset Name field and Key Code field at the same time. |
The License Key Dataset Name field and the Key Code field cannot both be specified at the same time. |
KTM524E ISPF |
Please enter alphanumeric characters to Key Code field. |
The value specified in the Key Code field is neither a number nor alphabetic characters. |
KTM525E ISPF |
Invalid Key Code is entered. Please re-enter the Key Code. |
The key code is invalid. Enter the key code again. |
KTM526E ISPF |
Invalid dataset name is specified. |
The specified dataset name is invalid. |
KTM527E ISPF |
You cannot specify the license information dataset. |
The license information dataset cannot be specified. |
KTM700E ISPF |
This table operation is not available. |
The executed table operation command cannot be used in that panel. |
KTM701E ISPF |
Enter required field at the cursor position. |
Enter the required information at the cursor location. |
KTM702E ISPF |
The length of the data must be = crtlen |
The length of the input data must be crtlen. |
KTM703E ISPF |
Enter hexadecimal characters (0-9, A-F, a-f). |
Enter hexadecimal digits (0-9, A-F, and a-f). |
KTM708E ISPF |
This table operation cannot be performed for multi-column sort fields. |
This table operation command cannot be executed for multi-column sort fields. |
KTM709E ISPF |
Execute the sort command before executing the locate command. |
The list is not sorted. Execute the SORT command before executing the LOCATE command. |
KTM721I ISPF |
Enter one of the selection item number. |
Enter one of the selection item numbers that are listed. |
KTM722E ISPF |
Invalid pattern is specified. |
Enter a valid condition string. Make sure that none of the following are the cause of the error:
|
KTM724E ISPF |
Field data is too long. |
Either the length of the command condition string or the length of the string entered in the condition field in the pop-up panel exceeds the maximum number of characters for the field. |
KTM726E ISPF |
Enter numerical characters (0-9). |
Enter decimal digits (0-9). |
KTM727E ISPF |
Range is not supported for the command. |
You cannot use a range specification for the condition string of the command. |
KTM728I ISPF |
Row include the value is not found. |
No row that matches the specified pattern was found. |
KTM731E ISPF |
ISPF service error occurred. info |
An error occurred in the ISPF service. |
KTM732E ISPF |
IKJPARS error occurred. info |
An IKJPARS macro error occurred. |
KTM765I ISPF |
A description for the specified error code was not found. |
No description for the specified error code was found. For details about an error code, see Details of error codes. If the error code is not listed in the manual, contact customer support. |
KTM901E TSO |
ISPF service is not available. |
The ISPF service is unavailable. Execute the KTSTART command in the ISPF environment. |
KTM902E TSO |
Load module is not found. |
The load module for Tiered Storage Manager for Mainframe was not found. The Tiered Storage Manager for Mainframe datasets might not be linked with LNKLST. Correct settings for LNKLST, and then re-execute the KTSTART command. |
KTM903E TSO |
SELECT service terminated abnormally. RC=nn |
The SELECT service ended with RC=nn. If this message is displayed immediately after the execution of the KTSTART command, the Tiered Storage Manager for Mainframe datasets might not be linked with the panel library (DD name is ISPPLIB), table library (DD name is ISPTLIB), or REXX Exec library (DD name is SYSEXEC). |
KTM904E TSO |
Message library was not found. |
The message library was not found. The Tiered Storage Manager for Mainframe datasets might not be linked with the message library (DD name is ISPMLIB). |
KTM905E TSO |
A GETMAIN error occurred. |
A GETMAIN error occurred. The program will stop processing. Contact customer support. |
KTM906E TSO |
A FREEMAIN error occurred. |
A FREEMAIN error occurred. The program will stop processing. Contact customer support. |
KTM907E TSO |
Creation of a REXX environment failed. |
An attempt to create a REXX environment failed. |
KTM908E TSO |
Exec library was not found. |
The REXX Exec library was not found. The Tiered Storage Manager for Mainframe dataset might not be concatenated to the REXX Exec library (DD name: SYSEXEC). |
KTR010E TSO RC=40 |
REXX failure return code=nnnn starting with variable name |
An attempt to access REXX variable name failed. The return code -2 indicates that the area for the REXX variable is insufficient. Check and revise the region size, and then re-execute the command. For details about the return codes, see the IRXEXCOM macro specifications in the IBM manual TSO/E Programming Services. |
KTR079E MSG SC=44 RC=44 (result) |
YKVSET program failure for: name = value |
An attempt to set the variable name with the value value failed with the result value indicated in result. The probable cause of the error is that an incorrect value was specified for the STEM parameter. |
KTR203E TSO RC=40# |
A REXX read error occurred. (return code=nnn, name= name, cmd=xxx, pos=yyy) |
The command cannot be executed because a REXX read error occurred.
|
KTR204E TSO RC=40# |
A REXX write error occurred. (return code=nnn, name= name, value=value, cmd=xxx, pos=yyy) |
The command cannot be executed because a REXX write error occurred.
If the error persists after the above actions has been taken, contact customer support.
|
KTR205E TSO RC=52 |
Unable to update MSG(stem) in Caller's environment. YKVSET result = result |
An attempt to set a variable value in the message structure failed with the result value indicated by result. The probable cause of the error is that an incorrect value was specified for the MSG parameter. |
KTR206E TSO RC=52 |
Unable to update MSG(stem) in Caller's environment. |
An attempt to set a variable value in the message structure failed. The probable cause of the error is that an incorrect value was specified for the MSG parameter. |
KTR250E MSG SC=36 RC=36 |
The value in the variable name is an invalid format. Value=value |
The value (value) of name is invalid. Contact customer support. |
KTR251E MSG SC=36 RC=36 |
Command processing stopped because a variable value is invalid. (variable=name,value=value) |
The variable value (value) indicated by name is invalid, so processing was canceled. The probable causes of the error are as follows:
|
KTR290E MSG SC=44 RC=44 (result) |
YKVGET program failure for:vn |
An attempt to acquire the variable vn failed with the result value indicated in result. The probable cause of the error is that an incorrect value was specified for the STEM parameter. |
KTX050W MSG SC=4 RC=4 (file:rec#) |
Encountered an unrecognized element: name |
An unrecognized element indicated by name was detected. Revise the specification on line number rec# in file. If the error still cannot be corrected, contact customer support. |
KTX051E MSG SC=36 RC=36 (file:rec#) |
Encountered end of file in comment. |
The format of the XML comment is invalid. Make sure that all XML comments are balanced. Note that XML comments cannot be nested. If the error still cannot be corrected, contact customer support. |
KTX053W MSG SC=4 RC=4 (file:rec#) |
Unrecognized Version attribute value: value |
The version attribute value of the XML element on line number rec# in file is not recognized. Check the indicated line, and then identify the cause of the error by referring to the description of the XML document type definition of the configuration file in the manual Tiered Storage Manager for Mainframe User Guide. |
KTX054E MSG SC=36 RC=36 (file:rec#) |
Unexpected termination of element: name |
The XML element name on line number rec# in file has not been created correctly. Check the indicated line, and then identify the cause of the error by referring to the description of the XML document type definition of the configuration file in the manual Tiered Storage Manager for Mainframe User Guide. |
KTX074E MSG SC=36 RC=36 (file:rec#) |
Invalid "&" character discovered in quoted string. string |
An entity reference with an invalid description indicated by string was found on line number rec# in file. Only use the entity references defined in the Extensible Markup Language (XML) 1.0 specification produced by the World Wide Web Consortium (W3C) (http://www.w3.org/) . |
KTX075W MSG SC=4 RC=4 (file:rec#) |
Unrecognized Encoding attribute value: value |
The encoding attribute value of the XML element on line number rec# in file is not recognized. Check the indicated line, and then identify the cause of the error by referring to the description of the XML document type definition of the configuration file in the manual Tiered Storage Manager for Mainframe User Guide. |
KTX076W MSG SC=4 RC=4 (file:rec#) |
Unrecognized attribute: name = value |
The XML element on line number rec# in file is not recognized. Check the indicated line, and then identify the cause of the error by referring to the description of the XML document type definition of the configuration file in the manual Tiered Storage Manager for Mainframe User Guide. |
KTX077W MSG SC=4 RC=4 (file:rec#) |
APIInfo Level=level invalid. Supported level is v.r.m. |
The Level attribute level of the APIInfo element on line number rec# in file is invalid. Check the indicated line, and then identify the cause of the error by referring to the description of the XML document type definition of the configuration file in the manual Tiered Storage Manager for Mainframe User Guide.
|
KTX220T MSG SC=36 RC=44 (file) |
The target volume of the operation is not specified in the definition of the tiering policy group. |
The operation-target device is not specified in the TPG definition file (file). |
KTX221T MSG SC=36 RC=44 (file) |
An I/O destination device is not specified in the I/O destination device definition file. |
No I/O destination device is specified in the I/O destination device definition file (file). |
KTX241W MSG SC=4 RC=4 (file:rec#) |
The attribute attname is already defined. |
The XML attribute attname has already been defined. Revise the specification of attname on line number rec# in file. |
KTX250E MSG SC=36 RC=36 (file:rec#) |
The value value of the attribute name is an invalid format. |
The format of the value value of the XML attribute name is invalid. Revise the specification on line number rec# in file. |
KTX251E MSG SC=36 RC=36 (file:rec#) |
name attribute missing. |
The necessary XML attribute name was not found. Revise the specification on line number rec# in file. |
KTX252E MSG SC=36 RC=36 (file:rec#) |
The attribute statement(s) are invalid. |
The specification of an XML attribute is invalid. Revise the specification on line number rec# in file. |
KTX253E MSG SC=36 RC=36 (file:rec#) |
This kind of elements element can't be defined more than once. |
The same element name of XML element element was defined more than once. Revise the specification on line number rec# in file. |
KTX254E MSG SC=36 RC=36 (file:rec#) |
The value value of attribute name does not match with filename. |
The value value of the XML attribute name does not match the configuration file name (the substring at a specific part of the file name). Revise the specification on line number rec# in file. Alternatively, correct the file name. |
KTX255E MSG SC=36 RC=36 (file:rec#) |
The element name-1, for which the value value was specified for the attribute name-2, was not found. |
The XML element name-1 with the value value specified for the XML attribute name-2 was not found. Revise the specification on line number rec# in file. |
KTX256E MSG SC=36 RC=36 (file:rec#) |
The disk device information could not be resolved. |
Element DiskDevice, which is not included in the disk configuration definition file, was detected. Alternatively, a local scan has not been performed for the I/O destination device. Revise the specification on line number rec# in file. |
KTX257E MSG SC=36 RC=36 (file:rec#) |
The attribute name-1 is not a content of the element name-2. |
The XML attribute name-1, which cannot be specified for the XML element name-2, was found. Revise the specification on line number rec# in file. |
KTX271E MSG SC=36 RC=36 (file:rec#) |
The element name is required, but no element was found. |
The necessary XML element name was not found. Revise the specification on line number rec# in file. |
KTX273E MSG SC=36 RC=36 (file:rec#) |
The element statements are invalid. |
The specification of an XML element is invalid. Revise the specification on line number rec# in file. |
KTX274E MSG SC=36 RC=36 (file:rec#) |
ETag name is mismatch. /correct-ETag-name is expected, but /incorrect-ETag-name is specified. |
An ETag name /incorrect-ETag-name that is not the expected ETag name /correct-ETag-name was specified. Revise the specification on line number rec# in file. |
KTX275W MSG SC=4 RC=4 (file:rec#) |
Extra ETag is specified: ETag-name |
An extra ETag-name was specified. Revise the specification on line number rec# in file. |
KTX276E MSG SC=36 RC=36 (file:rec#) |
The element name-1 is not a content of the element name-2. |
The XML element name-1 that cannot be specified is found in the XML element indicated in name-2. Revise the specification on line number rec# in file. |
KTX277E MSG SC=36 RC=36 (file:rec#) |
name element missing. |
The XML element name is not found. Revise the specification on line number rec# in file. |
KTX285E MSG SC=36 RC=36 (file:rec#) |
Serial Number HDASN is required, but Serial Number DDSN is found. |
While the same value as the SerialNum=HDASN element in the disk configuration definition file must be defined for SerialNum for the DiskDevice element, the defined value is DDSN. Revise the specification on line number rec# in file. |
KTX295E MSG SC=44 RC=44 (file:rec#) |
The element stack was overflowed. |
The work area for internal routines was insufficient. Contact customer support. |
KTX296E MSG SC=36 RC=36 (file) |
SUPFNC SUPFnc does not support function-name. |
The function indicated by function-name cannot be used by this storage system. Use a device# that supports the function indicated by function-name. If you did not perform a scan after replacing the storage system microcode, perform a scan.
|
KTZ007E MSG SC=44 RC=44 |
macro-name macro error occurred. (cmd=xxx, return code=nnn, reason code=mmm) |
The command cannot be executed because a macro error occurred. |
KTZ008E MSG SC=36 RC=36 |
service-name service error occurred. (cmd=xxx, return code=nnn, reason code=mmm) |
The command cannot be executed because an error occurred when the service was called. |
KTZ010E TSO PRT SC=44 RC=44 |
Module not found: load-module-name |
Load module load-module-name was not found. Make sure that the load module is installed correctly. |
KTZ015I MSG PRT |
RC:nn CMD:command-name |
The command-name command was issued, and ended with the return code nn. |
KTZ016I PRT |
RC: rc CMD: command-name Severity: Severity Text: Text Value: Value |
The command-name command was issued, and ended with the return code rc. Severity: Severity, Text: Text, and Value: Value are displayed an amount of times equal to the number of messages included in the message structure. |
KTZ032I MSG SC=0 (count) |
Hitachi storage systems Devices Found |
The number of Hitachi storage-system devices scanned by executing the KTSCAN command is output. |
KTZ041I PRT SC=0 RC=0 |
The number of volumes output to copy group 2nd-copy-group-ID does not match the number output to copy group 1st-copy-group-ID. |
In the output tiering policy CSV file, the number of volumes of the copy group 1st-copy-group-ID does not match the number of volumes of the copy group 2nd-copy-group-ID. |
KTZ042I PRT SC=0 RC=0 (count) |
The program processing results were output to the tiering policy information CSV file. |
The number of volumes output to the tiering policy CSV file by the KTCG2CSV program is count. |
KTZ099I PRT SC=0 RC=0 |
program-name return code=nnnn |
The program-name program ended with the return code nnnn. |
KTZ100E MSG SC=36 RC=36 |
Information about the storage group storage-group-name could not be retrieved. |
Information about the SMS storage group (storage-group-name) could not be acquired. The probable causes of the failure are as follows:
|
KTZ101E MSG SC=36 RC=36 |
No volumes belong to the storage group storage-group-name. |
No volume belongs to the SMS storage group (storage-group-name). |
KTZ102E MSG SC=36 RC=36 |
The specified volume(s) device(type) in the tiering policy information CSV file could not be scanned. |
An attempt to scan the volume or SMS storage group indicated by device that is specified in the tiering policy CSV file failed. Check the status of the volume or SMS storage group indicated by device. For details about the error cause, see the return code for the KTSCAN command indicated in the message KTZ015I that was output at the same time. |
KTZ103E LOG SC=36 RC=36 |
A list of the active storage groups could not be retrieved. |
A list of the active SMS storage groups could not be retrieved. The probable causes of the failure are as follows:
|
KTZ104E LOG SC=36 RC=36 |
There are no active storage groups. |
No active storage groups exist. |
KTZ112E MSG SC=36 RC=36 |
The specified volume(s) SN=serial-number,CU/CCA=device-address(type) in the tiering policy information CSV file could not be scanned. |
An attempt to scan the volume specified in the tiering policy CSV file failed. Check the status of the volume whose CU and CCA is device-address and that exists in the storage system whose serial number is serial-number. For details about the cause of the error, see the return code for the KTSCAN command displayed in the message KTZ015I that was output at the same time as this message. |
KTZ201E MSG TSO CON PRT SC=44 RC=44# |
A GETMAIN error occurred. (return code=nnn, size=mmm, area=area, cmd=xxx, pos=yyy) |
The command cannot be executed because a GETMAIN error occurred. Expand the job execution area, and then re-execute the command.
|
KTZ202E MSG TSO CON SC=52 RC=0 |
A Logical error occurred. (reason code=nnn, cmd=xxx, pos=yyy) |
A logical error occurred. Contact customer support. |
KTZ203W MSG SC=4 RC=4 |
An unrecognized storage system model was found. |
A storage system of an unrecognized model was found. |
KTZ205E PRT RC=0 |
A Parameter error occurred. (detail=message-text, cmd=xxx, pos=yyy) |
The command cannot be executed because a parameter error occurred. |
KTZ206E TSO RC=0 |
An I/O error occurred. (detail=message-text, cmd=xxx, pos=yyy) |
The command cannot be executed because an I/O error occurred. |
KTZ207E MSG TSO CON SC=52 RC=44 |
A Core process error occurred. (detail=message-text, cmd=xxx, pos=yyy) |
The command cannot be executed because a Core processing error occurred.
|
KTZ208I CON PRT RC=0 |
The Core processing( process ) started. (DATE=yyyy/mm/dd, TIME=hh:mm:ss.th, TOD=ttt, cmd=xxx, pos=yyy) |
Core processing started. |
KTZ209I CON PRT RC=0 |
The Core processing( process ) ended. (DATE=yyyy/mm/dd, TIME=hh:mm:ss.th, TOD=ttt, cmd=xxx, pos=yyy) |
Core processing ended. |
KTZ210E MSG TSO CON SC=44 RC=44 |
A NAME/TOKEN read error occurred. (return code=nnn, name= name, cmd=xxx, pos=yyy) |
The command cannot be executed because a NAME/TOKEN read error occurred. Make sure that the KTLOAD command terminated normally.
|
KTZ211E MSG CON SC=44 RC=44 |
A NAME/TOKEN write error occurred. (return code=nnn, name= name, cmd=xxx, pos=yyy) |
The command cannot be executed because a NAME/TOKEN write error occurred.
|
KTZ212W CON# RC=0 |
A FREEMAIN error occurred. (return code=nnn, cmd=xxx, pos=yyy) |
A FREEMAIN error occurred. Contact customer support.
|
KTZ214E MSG TSO SC=40 RC=40 |
The specified PREFIX is being used by another program: prefix-name. |
The specified prefix prefix-name is being used by another program. Check whether any other program is accessing the specified prefix. Terminate all programs that are accessing the specified prefix, and then re-execute the processing. |
KTZ215W MSG SC=0 RC=0 |
DEQ error occurred. (return code=nnn, cmd=xxx, pos=yyy) |
A DEQ error occurred. Contact customer support. |
KTZ231E MSG SC=48 RC=48 |
Information for a required I/O destination device was not found. |
Information about the I/O destination device that is necessary to continue processing was not found. Check whether one of the following conditions exists:
|
KTZ247E MSG SC=44 RC=44 |
STEM(stem) information for TPG Processing is not found. |
No information about the value specified for the STEM parameter was found. The KTLOAD command has not been executed. Alternatively, the value specified for the STEM parameter is different from the value specified for the STEM parameter of the KTLOAD command. For details about CLI commands, see the Tiered Storage Manager for Mainframe User Guide. |
KTZ266I PRT RC=0 |
Parameters were input. ( nnn, xxx ) |
Parameters were input from SYSIN. |
KTZ268E MSG CON PRT SC=0 RC=0 |
Incorrect dataset format. (DD name=ddd, KKK=AAA must be BBB, cp=xxx:yyy) |
The dataset format is invalid.
|
KTZ298E MSG TSO SC=44 RC=44 (detailed-info) |
cli-name encountered an unexpected error. |
An unexpected error occurred. This error might have occurred with another error. If another error message was output concurrently with this error message, first resolve the problem indicated in that message. If no other error messages were output, the version for the registered user SVC might not satisfy the prerequisite conditions for the user SVC version. Execute the KTINSCHK command to check if OK is output for User SVC Routine, which proves that the latest user SVC has been registered. If the latest user SVC has been registered, collect the following information, and then contact customer support:
|
KTZ300E MSG SC=44 RC=44 |
SVC # is null. |
The user SVC is not registered. Define the user SVC in SVCPARM and then perform a re-IPL, or register the user SVC by using the KTALCSVC command. For details about how to register a user SVC, see the Tiered Storage Manager for Mainframe User Guide. |
KTZ301E TSO |
The task is not authorized to execute the request. |
The task is not authorized to execute the CLI command. The program will terminate. For details about the cause, see the return code of the message YKZ301E that was output at the same time. For details about how to set CLI command execution permissions, see the Tiered Storage Manager for Mainframe User Guide. |
KTZ807E MSG TSO CON SC=52 RC=44 |
A Core process error occurred. (detail=message-text, cmd=xxx, pos=yyy) |
The command cannot be executed because a Core processing error occurred.
|