Diagnostic information &DIA1 for cluster &SUFF-file: &INF1: &INF2
The insert &SUFF designates the file to which the message refers.
The insert &DIA1 describes the cause of the error; the inserts &INF1 and &INF2 provide additional information.
The Grp. (Group) column in the tables below describes the reason group to which the error code belongs. The following groups exist:
A | The cause is a user error, e.g. an error in generating and administering UTM applications operating UTM applications generating the system (e.g. division of the address space)
|
U | The cause is an error in the UTM code. |
S | The cause is an error in another system component (software or hardware). |
| M | The cause is a memory bottleneck. |
| I | The message is for information only. |
Message K190 for the cluster configuration file
If &DIA1 is in the range 1000 to 1099, then &SUFF has the value ’CFG’ and the message refers to the cluster configuration file.
The table below provides an overview of the values of the insert &DIA1 for the cluster configuration file and their meanings, together with the values and meanings of the inserts &INF1 and &INF2 which may occur in combination with &DIA1.
&DIA1 | Grp. | Meaning | &INF1 | &INF2 |
1001 | A | APPLNAME_MISMATCH
Different application names in the cluster configuration file and KDCFILE. | Application name from the cluster configuration file | Application name from the KDCFILE |
1002 | A | HOSTNAME_NOT_FOUND
The host computer name was not found in the cluster configuration file. | Local host name | Host name of the cluster node or blank |
1003 | A | INVALID_KDCDEF_TIME
The generation time of the KDCFILE is too old; another node application with a more recent KDCFILE has already been started. | KDCDEF time from the cluster configuration file | KDCDEF time from the KDCFILE |
1004 | I | OLD_STATE_INVALID (warning)
The old status of the node is "registered" and the start was not a warm start. | G generated:
The node has never been started. R registered:
The node is active T terminated:
The node was terminated normally A abterm:
The node was terminated abnormally F failure:
The node is marked as failed | D: Start after KDCDEF run C: Cold start W: Warm start U: Start after KDCUPD run |
1006 | A | CLUSTER_FILE_CHANGED
The cluster configuration file was regenerated during the application run. | Generation time from the cluster configuration file or KDCFILE filebase from the cluster configuration file | Generation time from the KDCFILE or KDCFILE filebase from the KDCFILE |
1008 | U | NODE_NOT_REGISTERED
The local application is not entered as registered in the KAA. |
|
|
1009 | A | PLATFORM_MISMATCH
The operating system platform of the local application does not match the information from the cluster configuration file. | OS type or bit mode of the local computer | OS type or bit mode from the cluster configuration file |
1010 | AS | NODE_START_SERIALIZATION
The lock for the serialization of the start of different node applications could not be initialized or could not be set. | INIT: Error when initializing lock
LOCK: Error when setting lock | 1: Timeout
2: Locked
3: Try later |
1014 | A | INVALID_FILE_VERSION
The file version of the cluster configuration file does not match the UTM system code. | Expected version of the cluster configuration file | Actual version of the cluster file |
1015 | ASU | CLUSTER_FILE_CORRUPTED
The start and end markers of the cluster configuration file could not be found; the file is probably not a cluster configuration file. |
|
|
1016 | A | NODE_KDCFILE_MISSMATCH
A node application has already been started on another host computer with this KDCFILE. | Name from the cluster configuration file of the host computer on which a startup has already been performed using this KDCFILE. | Name from the cluster configuration file of the host computer on which a startup is now to be performed using this KDCFILE. |
1017 | A | NODE_GT_KDCFILE_START
The node application was not last started with this KDCFILE. | Time of the last start with this KDCFILE | Time of the last start of this node application. |
1018 | A | NODE_START_GT_KDCFILE_DEF
The newly generated KDCFILE was generated before the last start of the node application. | Generation time of the KDCFILE | Time of the last start of this node application. |
1019 | A | NODE_NAME_OF_OWN_HOST
Node recovery of the node application at the local computer is not permitted. |
|
|
1020 | A | NODE_NAME_NOT_FOUND
Node name for node recovery does not exist in the cluster configuration file. | Node name in the cluster configuration file | Node name in the KDCFILE |
1021 | A | NODE_NAME_INCONSISTENCY
The sequence of node names in the cluster configuration file and the KDCFILE do not match. |
|
|
Message K190 for the cluster user file
If &DIA1 is in the range 1100 to 1199, then &SUFF has the value ’USER’ and the message refers to the cluster user file. In this case, the message can also be output by the KDCDEF utility program.
The table below provides an overview of the values of the insert &DIA1 for the cluster user file and their meanings:
&DIA1 | Grp. | Meaning |
1101 | AS | TIMEOUT_FOR_USERFILE
A timeout occurred on the request for a file lock when opening or closing the cluster user file. |
1102 | A | NO_USER_FILE
The first page in the file is not a CONS page of a cluster user file. |
1103 | A | INVALID_FILE_VERSION
The version number in the cluster user file does not match the version number in the UTM system code. |
1104 | A | APPLINAME_MISMATCH
Different application name in the cluster user file and the KDCFILE. |
1105 | A | GEN_TIME_MISMATCH
The generation time of the cluster user file specified in the cluster user file is not the same as that specified in the KDCFILE. |
1106 | A | CLUSTER_FILEBASE_MISMATCH
The cluster filebase specified in the cluster user file is not the same as that specified in the KDCFILE. |
1107 | ASU | LAST_PAGE_CORRUPTED
The last page in the file is not a CONS page of a cluster user file. |
1108 | U | PAGE_COUNTERS_INCONSISTENT
The counters for the free and used entries in the cluster user file are inconsistent. |
1109 | U | FREE_ANCHOR_INCONSISTENT
The free chain administration fields in the cluster user file are inconsistent. |
1110 | U | ENTRY_NOT_FOUND
An error occurred while addressing an entry in the cluster user file. |
1111 | U | FREE_ANCHOR_BROKEN
The chaining of the first entry in the free chain is inconsistent. |
1112 | U | USER_STATE_INVALID
The status of a user entry in the free chain is invalid. |
1113 | U | ENTRY_NOT_FREE
An entry in the free chain is not identified as free. |
1114 | U | END_OF_CHAIN_NOT_FOUND
The last element was not found when the free chain was searched. |
1115 | U | FREE_CHAIN_BROKEN
The number of elements in the free chain does not correspond to the counter in the control page. |
1116 | AU | MAX_FILE_SIZE_REACHED
The cluster user file cannot be extended any further since it already contains the maximum number of entries. |
1118 | A | VERSION_MISMATCH
The cluster user file and KDCFILE come from different openUTM versions. |
1119 | A | OS_TYPE_MISMATCH
The cluster user file and KDCFILE have a different OS type and/or bit mode. |
Message K190 for the cluster JKAA file
If &DIA1 is in the range 1200 to 1399, then &SUFF has the value ’JKAA’ and the message refers to the cluster JKAA file.
The table below provides an overview of the values of the insert &DIA1 for the cluster JKAA file and their meanings:
&DIA1 | Grp. | Meaning |
1202 | AU | FILE_IS_EMPTY
The JKAA file is empty. |
1203 | AU | FILE_DOES_NOT_EXIST
The JKAA file does not exist. |
1204 | AU | DMS_ERROR
DMS error for the cluster JKAA file
Insert &INF1 contains the DMS error code. |
1205 | M | MEMORY_INSUFFICIENT
Error allocating memory for FCB and read buffer.
Action: Increase the virtual memory. |
1206 | AU | FILE_OPEN_ERROR
DMS error when opening the JKAA file.
Insert &INF1 contains the DMS error code. |
1207 | ASU | LOCK_INIT_TIMEOUT
Timeout when initializing file lock (KCCGFLI). |
1208 | SU | LOCK_INIT_ERROR
Error when initializing file lock (KCCGFLI). |
1209 | ASU | FILE_LOCK_TIMEOUT
Timeout when requesting file lock (KCCGFLK). |
1210 | SU | FILE_LOCK_ERROR
Error when requesting file lock (KCCGFLK). |
1211 | AU | INVALID_FILE_TYPE
The file is not a JKAA file. |
1212 | AU | FILE_CORRUPTED
The second CONS page has an invalid format. |
1213 | ASU | FILE_UNLOCK_TIMEOUT
Timeout when releasing file lock (KCCGFLK). |
1214 | SU | FILE_UNLOCK_ERROR
Error when releasing file lock (KCCGFLK). |
1215 | ASU | DESTROY_LOCK_TIMEOUT
Timeout when destroying file lock (KCCGFLK). |
1216 | SU | DESTROY_LOCK_ERROR
Error when destroying file lock (KCCGFLK). |
1217 | SU | FILE_CLOSE_ERROR
DMS error when closing the JKAA file. |
1218 | AU | READ_FILE_ERROR
DMS error when reading the KAA pages of the JKAA file.
Insert &INF1 contains the DMS error code. |
1219 | A | VERSION_MISMATCH
The KDCFILE and JKAA file have different openUTM versions.
Insert &INF1 contains the openUTM version of the KDCFILE.
Insert &INF2 contains the openUTM version of the JKAA file. |
1220 | A | OS_TYPE_MISMATCH
The KKAA file and KDCFILE have a different OS type and/or bit mode.
Insert &INF1 contains the OS version of the KDCFILE.
Insert &INF2 contains the OS version of the JKAA file. |
1221 | A | APPLINAME_MISMATCH
The KDCFILE and JKAA file have different application names.
Insert &INF1 contains the application name of the KDCFILE.
Insert &INF2 contains the application name of the JKAA file. |
1223 | A | DATETIME_NOT_EQUAL
The KAA generation time of the JKAA file is not the same as the KAA generation time of the KDCFILE even though the node application that is starting has the same generation time as the running UTM cluster application. &INF1 contains the KAA generation time of the KDCFILE.
Insert &INF2 contains the KAA generation time of the JKAA file. |
1224 | A | DATETIME_NOT_LATER
The KAA generation time of the KDCFILE is not later than the KAA generation time of the JKAA file even though the starting node application has been newly generated.
Insert &INF1 contains the KAA generation time of the KDCFILE.
Insert &INF2 contains the KAA generation time of the JKAA file. |
1225 | A | KCSANT_ERROR
The KCSANT component returned an incorrect return code on the inclusion of a KSET for generation in the object tree of the local application. |
1226 | A | OBJECT_TYPE_ERROR
On the generation of a user (USER) or an LU6.1 session in the local application, it was found that an LU6.1 session or user already exists under the index in the local application. |
1301 | A | BLKSIZE_ERROR
The block size of the KDCFILE is not equal to 4K.
Action: Generate KDCFILE with MAX BLKSIZE=4K. |
1302 | A | BUFFER_RQ_ERROR
Error when requesting write/read buffer.
Action: Increase the virtual memory. |
1303 | A | FCB_RQ_ERROR
Error requesting memory for FCB.
Action: Increase the virtual memory. |
1304 | AU | FILE_CMD_ERROR
DMS error when setting up the JKAA file.
Insert &INF1 contains the DMS error code. |
1305 | AU | OPEN_ERROR
DMS error when opening the JKAA file.
Insert &INF1 contains the DMS error code. |
1306 | U | WRITE_NSR_1_ERROR
DMS error when writing the first NSR page.
Insert &INF1 contains the DMS error code.
Insert &INF1 contains the half page number. |
1307 | U | WRITE_NSR_ERROR
DMS error when writing the follow-up NSR pages.
Insert &INF1 contains the DMS error code.
Insert &INF1 contains the half page number. |
1308 | U | WRITE_NSR_END_ERROR
DMS error when writing the last block of NSR pages.
Insert &INF1 contains the DMS error code.
Insert &INF1 contains the half page number. |
1309 | AU | PWRT_LOCK_ERROR
Error when requesting periodic write lock. |
1310 | U | READ_DSR_1_ERROR
DMS error when reading the first DSR page.
Insert &INF1 contains the DMS error code.
Insert &INF1 contains the half page number. |
1311 | U | WRITE_SR_ERROR
DMS error when writing SR pages.
Insert &INF1 contains the DMS error code.
Insert &INF1 contains the half page number. |
1312 | U | WRITE_SR_END_ERROR
DMS error when writing the last block of SR pages.
Insert &INF1 contains the DMS error code.
Insert &INF1 contains the half page number. |
1313 | U | READ_SR_1_ERROR
DMS error when reading the first SR page.
Insert &INF1 contains the DMS error code.
Insert &INF1 contains the half page number. |
1314 | U | READ_SR_ERROR
DMS error when reading the follow-up SR pages.
Insert &INF1 contains the DMS error code.
Insert &INF1 contains the half page number. |
1315 | U | SR_PAGE_TYPE_ERROR
Read SR page has incorrect page type.
Insert &INF1 contains the type of the read page.
Insert &INF1 contains the half page number. |
1316 | U | READ_DSR_ERROR
DMS error when reading the follow-up DSR pages.
Insert &INF1 contains the DMS error code.
Insert &INF1 contains the half page number. |
1317 | U | DSR_PAGE_TYPE_ERROR
Read DSR page has incorrect page type.
Insert &INF1 contains the type of the read page.
Insert &INF1 contains the half page number. |
1318 | U | WRITE_DSR_ERROR
DMS error when writing DSR pages.
Insert &INF1 contains the DMS error code.
Insert &INF1 contains the half page number. |
1319 | U | WRITE_DSR_END_ERROR
DMS error when writing the last block of DSR pages.
Insert &INF1 contains the DMS error code.
Insert &INF1 contains the half page number. |
1320 | U | READ_CONS_ERROR
DMS error when reading the first CONS page.
Insert &INF1 contains the DMS error code.
Insert &INF1 contains the half page number. |
1321 | AU | WRITE_CONS_1_ERROR
DMS error when writing the first CONS page.
Insert &INF1 contains the DMS error code.
Insert &INF1 contains the half page number. |
1322 | AU | WRITE_CONS_2_ERROR
DMS error when writing the last CONS page.
Insert &INF1 contains the DMS error code.
Insert &INF1 contains the half page number. |
1323 | U | CLOSE_ERROR
DMS error when closing the JKAA file.
Insert &INF1 contains the DMS error code. |
1324 | SU | GFLI_ERROR
Error when initializing file lock KCCGFL).
Insert &INF1 contains the KCCGFLI return code. |
1325 | ASU | GFLI_TIMEOUT
Timeout when initializing file lock KCCGFLI.
Insert &INF1 contains the KCCGFLI return code. |
1326 | SU | GFLK_LOCK_ERROR
Error when requesting file lock KCCGFLK.
Insert &INF1 contains the KCCGFLK return code. |
1327 | AU | GFLK_LOCK_TIMEOUT
Timeout when requesting file lock KCCGFLK.
Insert &INF1 contains the KCCGFLK return code. |
1328 | SU | GFLK_UNLOCK_ERROR
Error when releasing file lock KCCGFLK.
Insert &INF1 contains the KCCGFLK return code. |
1329 | ASU | GFLK_UNLOCK_TIMEOUT
Timeout when releasing file lock KCCGFLK.
Insert &INF1 contains the KCCGFLK return code. |
1330 | SU | GFLK_DESTROY_ERROR
Error when destroying file lock KCCGFLK.
Insert &INF1 contains the KCCGFLK return code. |
1331 | ASU | GFLK_DESTROY_TIMEOUT
Timeout when destroying file lock KCCGFLK.
Insert &INF1 contains the KCCGFLK return code. |
1332 | U | JFCT_START_ERROR
Error when writing the copy status (Started) to the journal file. |
1333 | U | JFCT_END_ERROR
Error when writing the copy status (Completed) to the journal file. |
Message K190 for the administration journal files
If &DIA1 is in the range 1400 to 1499, then &SUFF has the value ’JRN’ and the message refers to the administration journal.
The table below provides an overview of the values of the insert &DIA1 for the administration journal files and their meanings:
&DIA1 | Grp. | Meaning |
1401 | AU | One or both journal files do not exist.
See previous K043 message(s)
Action: Regenerate the application. |
1402 | AU | Error when opening a journal file.
See previous K043 message. |
1403 | AU | Error when creating a journal file.
See previous K043 message. |
1404 | SU | Error when setting up lock for the journal files. |
1405 | SU | Error when closing a journal file.
See previous K043 message. |
1406 | ASU | Error when releasing reserved pages in a journal file.
See previous K043 message. |
1407 | A | Errored journal file(s): Incorrect ID.
&INF1/&INF2: ID in file with suffix JRN1/JRN2.
Action: Delete files, regenerate the application. |
1408 | A | Errored journal file(s): Incorrect file ID.
&INF1/&INF2: ID in file with suffix JRN1/JRN2. |
1409 | A | Errored journal file(s): Incorrect UTM application name.
&INF1/&INF2: Application name in JRN1 file / KDCFILE. |
1410 | A | Errored journal file(s): Incorrect UTM application name.
&INF1/&INF2: Application name in JRN2 file / KDCFILE. |
1411 | A | Errored journal file(s): Incorrect cluster filebase.
&INF1/&INF2: Cluster filebase in JRN1 file / KDCFILE. |
1412 | A | Errored journal file(s): Incorrect cluster filebase.
&INF1/&INF2: Cluster filebase in JRN2 file / KDCFILE. |
1413 | A | Errored journal file(s): Different creation time.
&INF1/&INF2: Creation time of file with suffix JRN1/JRN2. |
1414 | AU | Errored journal file(s): Invalid file status.
&INF1/&INF2: File status in file with suffix JRN1/JRN2. |
1415 | SU | Error when destroying lock for the journal files. |
1416 | AU | Errored journal file(s): Incorrect file sequence numbers.
&INF1/&INF2: File sequence numbers in JRN1/JRN2 file |
1417 | A | Errored journal file(s): Incorrect file version.
&INF1/&INF2: Version of JRN1 file / expected version. |
1418 | A | Errored journal file(s): Incorrect file version.
&INF1/&INF2: Version of JRN2 file / expected version. |
Message K190 for the cluster page pool control file
If &DIA1 is in the range 1500 to 1599, then &SUFF has the value ’CPMD’ and the message refers to the cluster page pool control file.
The table below provides an overview of the values of the insert &DIA1 for the cluster page pool control file and their meanings:
&DIA1 | Grp. | Meaning |
1501 | A | Control file has incorrect file version.
&INF1/&INF2: Version of CPMD file / expected version.
Action: Regenerate all the UTM cluster files. |
1502 | A | A cluster update with transfer to the CPMD file was terminated abnormally.
Action: Regenerate the cluster configuration files. |
1503 | A | The size of the cluster page pool has been reduced.
&INF1/&INF2: Size in CPMD file / size in KDCFILE.
Action: Regenerate all the UTM cluster files. |
1504 | A | The number of files in the cluster page pool has been changed.
&INF1/&INF2: Number in CPMD file / number in KDCFILE.
Action: Regenerate all the UTM cluster files. |
1505 | A | Error when trying to increase the size of the files in the cluster page pool.
&INF1: 4K page number that could not be written.
&INF2: Generated size of the cluster page pool in 4K pages.
Action: Make sufficient disk space available for the UTM cluster files. |
1506 | AU | The size of the free page quota in the cluster page pool is invalid.
&INF1: Size of quota as number of UTM pages.
Action: Regenerate all the UTM cluster files or write problem report. |
1507 | AU | The number of pages in the free page quota in the cluster page pool is invalid.
&INF1: Number of pages for the full free page quota.
Action: Regenerate all the UTM cluster files or write problem report. |
1508 | AU | Error in management of the free page quota in the cluster page pool.
Action: Regenerate all the UTM cluster files or write problem report. |
1509 | AU | Invalid ID for file size increase in the cluster page pool.
&INF1: ID for file size increase.
Action: Regenerate all the UTM cluster files or write problem report. |
1510 | AU | Invalid ID for running a cluster update with transfer to the CPMD file.
&INF1: ID for running cluster update.
Action: Regenerate all the UTM cluster files or write problem report. |
1511 | A | MAX APPLIMODE of the node application has been changed. To change between Secure and Fast, it is necessary to recreate all the UTM cluster files.
&INF1/&INF2: APPLIMODE in CPMD file / in KDCFILE |
1512 | A | MAX VGMSIZE of the node application has been changed. All UTM cluster files must be regenerated.
&INF1/&INF2: VGMSIZE in CPMD file / in KDCFILE |
1513 | A | MAX KB of the node application has been changed.
All UTM cluster files must be regenerated.
&INF1/&INF2: KB in CPMD file / in KDCFILE |
1514 | A | MAX NB of the node application has been changed.
All UTM cluster files must be regenerated.
&INF1/&INF2: NB in CPMD file / in KDCFILE |
1515 | A | MAX LSSBS of the node application has been changed.
All UTM cluster files must be regenerated.
&INF1/&INF2: LSSBS in CPMD file / in KDCFILE |
1516 | A | MAX TRMSGLTH of the node application has been changed.
All UTM cluster files must be regenerated.
&INF1/&INF2: TRMSGLTH CPMD file / KDCFILE. |
1517 | A | The number of generated databases has been changed.
All UTM cluster files must be regenerated.
&INF1/&INF2: Number in CPMD file / KDCFILE. |
1518 | A | Invalid combination with and without user IDs.
All UTM cluster files must be regenerated. |
1520 | A | Change of CLUSTER ABORT-BOUND-SERVICE.
All UTM cluster files must be regenerated. |
1521 | A | Change of generated database systems.
All UTM cluster files must be regenerated. |
Message K190 for the cluster ULS file
If &DIA1 is in the range 1600 to 1699, then &SUFF has the value ’ULS’ and the message refers to the cluster ULS file in which the administration data for ULS areas is stored in UTM cluster applications.
The table below provides an overview of the values of the insert &DIA1 for the cluster ULS file and their meanings:
&DIA1 | Grp. | Meaning |
1601 | AU | The file is not a cluster ULS file or the file is corrupt. |
1602 | A | The version of the cluster ULS file is invalid. |
1603 | A | The application names are different in the cluster ULS file and KAA. |
1604 | AU | The last page of the cluster ULS file is destroyed. |
1605 | U | UTM generation error: The number of ULS blocks from the cluster ULS file is different from the number of ULS blocks in the KDCFILE. |
1606 | U | Generation error: A ULS from the cluster ULS file is missing in the KDCFILE. |
1607 | ASU | A timeout occurred while requesting a lock for the cluster ULS file. |
Message K190 for the cluster lock file
If &DIA1 is in the range 1700 to 1799, then &SUFF has the value ’LOCK’ and the message refers to the cluster lock file for locking global resources in UTM cluster applications (GSSB and ULS).
The table below provides an overview of the values of the insert &DIA1 for the cluster lock file and their meanings:
&DIA1 | Grp. | Meaning |
1700 | AU | An error occurred while opening the existing cluster lock file.
See previous K043 message. |
1701 | AU | An error occurred while creating the cluster lock file.
See previous K043 message. |
1702 | SU | Error while writing the cluster lock file.
See previous K043 message. |
1703 | SU | Error while closing the cluster lock file.
See previous K043 message. |
1704 | SU | Error while opening the cluster lock file.
See previous K043 message. |
1705 | SU | Error while replacing the cluster lock file.
See previous K043 message. |
1706 | I | Information message - the cluster lock file has been extended.
The number of new pages is output. |
1707 | SU | Error while closing the cluster lock file.
See previous K043 message. |
Message K190 for the cluster GSSB file
If &DIA1 is in the range 1800 to 1899, then &SUFF has the value ’GSSB’ and the message refers to the cluster GSSB file in which the administration data for GSSB areas is stored in UTM cluster applications.
The table below provides an overview of the values of the insert &DIA1 for the cluster GSSB file and their meanings, together with the values and meanings of the inserts &INF1 and &INF2 which may occur in combination with &DIA1:
&DIA1 | Grp. | Meaning | &INF1 | &INF2 |
1800 | ASU | GSSBFILE_LOCK_ERROR
An error or timeout occurred when requesting or releasing a lock for the cluster GSSB file. | LOCK: Error when requesting lock
LOCK: Error when releasing lock | TIMEOUT: Timeout (KCSGFLK return
code)
TRY LATER: Try later (KCSGFLK return code)
LOCKED: File is already locked by own task
NOT LOCKED: File is not locked |
1801 | A | INVALID_FILE_VERSION
The version of the cluster GSSB file is invalid. | File version in the GSSB file | Expected file version |
1802 | AU | HEADER_PAGE_CORRUPTED
The control page of the cluster GSSB file is destroyed. | Incorrect field content in the GSSB file | Expected field content |
1803 | AU | FREE_PAGES_ANCHOR_CORRUPTED
The free page chaining of the cluster GSSB file is corrupt. |
|
|
1804 | AU | NO_GSSBFILE
The file is not a cluster GSSB file or the file is corrupt. | File type on the CONS page of the GSSB file | Expected file type |
1805 | AU | PAGE_COUNTER_INCONSISTENT
The page counters of the cluster GSSB file are corrupt. |
|
|
1806 | AU | LAST_PAGE_INCONSISTENCY
The file sizes on the CONS and control pages of the cluster GSSB file are different. |
|
|
1808 | SU | CONS_PAGE_READ_ERROR
Error when reading the first CONS page of the cluster GSSB file. |
|
|
1809 | SU | CONS_PAGE_WRITE_ERROR
Error when writing the first CONS page of the cluster GSSB file. |
|
|
1810 | SU | READ_ERROR_GSSBFILE
Error when reading a page of the cluster GSSB file. |
|
|
1811 | SU | WRITE_ERROR_GSSBFILE
Error when writing a page of the cluster GSSB file. |
|
|
1812 | U | RELEASE_BUFFER_ERROR
Error when releasing a page of the cluster GSSB file. |
|
|
1814 | U | FREE_ENTRY_CHAIN_CORRUPTED
The chaining of the free GSSB entries in the cluster GSSB file is corrupt. |
|
|
1815 | U | HASH_CHAIN_CORRUPTED
The hash chaining of the GSSB entries in the cluster GSSB file is corrupt. |
|
|
1816 | U | FREE_PAGE_CHAIN_CORRUPTED
The free page chaining of the cluster GSSB file is corrupt. |
|
|
1817 | U | GSSB_CNTR_ERROR
The counter for the occupied GSSB entries in the cluster GSSB file is corrupt. |
|
|
1818 | AU | MAX_GSSB_ERROR
The value of MAX GSSB in the KDCFILE is different from the value in the cluster GSSB file. | MAX_GSSB in the GSSB file | MAX_GSSB in the KDCFILE |
Message K190 for the UTM cluster files
If &DIA1 is in the range 1900 to 1949 then the message refers to the request for a lock for a UTM cluster file and is used for diagnostic purposes only.
The table below provides an overview of the values of the insert &DIA1 and their meanings:
&DIA1 | Grp. | Meaning |
1900 | I | The lock request could not be executed in the generated time (operand CLUSTER FILE-LOCK-TIMER-SEC). The lock request is repeated in accordance with the value generated by the FILE-LOCK-RETRY operand. &INF1: Internal error code of the lock request. |
1901 | I | This message is issued on the release of the file lock if the lock has been maintained by this processfor at least half the time generated in the operand FILE-LOCK-TIMER-SEC in the CLUSTER statement. &INF1: Status of the requested lock.
&INF2: Lock maintenance period in seconds. |
&SUFF specifies the suffix of the UTM cluster file for which the lock was requested.
The following suffixes, which stand for real KDCFILE files, are also generated:
IKDC | for the imported KDCFILE |
OKDC | for the local KDCFILE |
EKDC | for the KDCFILE of another node |
Message K190 on the failure of a node application
If &DIA1 is in the range 2001 to 2099, then &SUFF has the value ’KDCA’ and the message refers to the KDCFILE of a node application. This message is output if a node failure is detected.
The table below provides an overview of the values of the insert &DIA1 and their meanings:
&DIA1 | Grp. | Meaning |
2001 | I | The application is not active. |
2002 | S | An error occurred while requesting memory. |
2003 | ASU | An error was reported by the file system; see also the message K043 |
2004 | SU | An error occurred while initializing the lock. |
2005 | U | The node could not be found in the UTM cluster file |
&INF1 contains the node number of the node that has been identified as failed.
&INF1 contains the file name of the KDCFILE of the node that has been identified as failed.
