unisys Distributed Processing Middleware Open Distributed Transaction Processing Messages imagine it. done. ClearPath OS 2200 Release 13.

Transcription

1 unisys imagine it. done. Distributed Processing Middleware Open Distributed Transaction Processing Messages ClearPath OS 2200 Release 13.0 February

2 NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such agreement. Unisys cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, special, or consequential damages. You should be very careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used. The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions. Notice to U.S. Government End Users: This is commercial computer software or hardware documentation developed at private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data rights clauses. Unisys and ClearPath are registered trademarks of Unisys Corporation in the United States and other countries. All other brands and products referenced in this document are acknowledged to be the trademarks or registered trademarks of their respective holders.

3 Contents Section 1. Getting Started Documentation Updates Purpose Scope Audience Section 2. Messages iii

4 Contents iv

5 Tables 1 1. ELMS Message Ranges v

6 Tables vi

7 Section 1 Getting Started Distributed Processing Middleware Open Distributed Transaction Processing (formerly known as Open/OLTP) software is the Unisys implementation of the Open Group Distributed Transaction Processing (DTP) model. (The Open Group was formerly known as X/Open.) Open Distributed Transaction Processing provides an open, standards compliant environment for developing DTP applications, including global transactions. The DTP environment can include the following systems: OS 2200 operating environment of ClearPath Servers for OS 2200 MCP operating environment of ClearPath Servers for MCP Microsoft Transaction Server (MTS) operating environment Systems of other vendors that support The Open Group standards, such as TUXEDO Note: The information in this guide applies to the OS 2200 operating environment of ClearPath Servers and to OS 2200 systems. Documentation Updates Purpose This document contains all the information that was available at the time of publication. Changes identified after release of this document are included in problem list entry (PLE) To obtain a copy of the PLE, contact your Unisys representative or access the current PLE from the Unisys Product Support Web site: Note: If you are not logged into the Product Support site, you will be asked to do so. The intent of this guide is to make it easier for system administrators and software engineers to access Open Distributed Transaction Processing (OTM) messages by creating a PDF file, in which they can use the search or FIND capabilities of Adobe Reader

8 Getting Started Scope This guide lists and describes the Extended Language Message System (ELMS) messages implemented for OTM messages issued on OS 2200 systems. The OTM messages are printed in the OLTP-TM2200 event log and may appear on the operator console. Many of these messages have two levels of information, where the second level may describe how to solve the problem. These messages may be internationalized by using ELMS. See the OLTP-TM2200 Administration Guide, Volume 1, for a complete description of the event log and information on internationalizing messages using ELMS. Table 1 1 lists the message component identifiers and number ranges assigned to Open Distributed Transaction Processing components that log or print output messages. The Open Distributed Transaction Processing component that produced the message is listed in the Component Identifier field; it is required for messages written to event logs. The values for message number ranges are designed to allow for future expansion. Table 1 1. ELMS Message Ranges Component Component Identifier Message Number Range TPSS (tp system services) internal components TPSS VADD utility program VADD VDEL utility program VDEL VGET utility program VGET TMSCON processor TMSCON TMSDUMP processor TMSDMP TMSC console interface TMSC TMLS utility TMLS TMTIMER utility TMTIME TMTRACER utility TMTRAC Transaction manager internal components TM XATMI CRM internal components XATMI TMBSD utility TMBSD TMHAAD utility TMHAAD TMTSD utility TMTSD TSF processor TSF

9 Getting Started Table 1 1. ELMS Message Ranges Component Component Identifier Message Number Range TWrap utility TWRAP TD2200 utility TD uds_xa_mask UDSXA mcb_intf MCBIF Server main program SERVER BUFMAKE utility BUFMAKE OLTP access interface OLTPAI OSI-TP interface XTP FCSS two-phase commit interface FCSSXA Open Distributed Transaction Processing CMS utility OCMS Audience Open session manager SESSMGR This guide is for OS 2200 Open Distributed Transaction Processing system administrators and application developers that are responsible for: Designing, debugging, and administering Open Distributed Transaction Processing applications Installing and managing Open Distributed Transaction Processing and user applications Building servers that provide access to OS 2200 service routines from client programs Working with OS 2200 operations personnel to maintain Open Distributed Transaction Processing operations

10 Getting Started

11 Section 2 Messages OTM000001: ELMS returned error *1* when processing message *2*. This message is displayed when OLTP-TM2200 is unable to obtain a message from ELMS due to an error. OTM000002: INTERNAL ERROR: *1**2* This message is displayed when an error is detected while executing OLTP-TM2200 code. There is no corrective action available to you except to submit a UCF with any available diagnostic information. OTM000007: Application program error. REG4TERM$ processing is called. This message is displayed whenever an application program error occurs. OTM000008: Internal error. Invalid REG4TERM id = *1*. This message is displayed whenever an internal error occurs. OTM000009: REG4TERM failed, status = *1*, *2*. This message is displayed whenever a call to register for a contingency fails. OTM000010: XATMI interface processing failed: Type/subtype is no longer valid. An XATMI interface request failed because the buffer type/subtype was deleted while processing was in progress. OTM000012: Statistics counters have overflowed for service *1*. One of the statistics counters of the service has overflowed and all of the service's counters have been reset to zero. OTM000013: Statistics counters have overflowed for server *1*. One of the server's statistics counters has overflowed and all of the server's counters have been reset to zero. OTM000014: Qtimer changing date to: *1* This message is displayed whenever the quantum timer detects that midnight has been reached and the date is to be changed

12 OTM000100: SMM: Could not create a bank! Maximum number of banks *1* already created. The maximum number of banks that can be created was reached. OTM000101: SMM: Could not create a bank! CREATE$BANK status = *1* Another bank could not be created. OTM000102: SMM: Created another bank; current number of banks is now *1* Another bank was created. OTM000104: smm_init: CDGETCFIG() returned invalid max banks = *1* CDGETCFIG returned an invalid value for MAX_SHARED_BANKS. OTM000105: smm_init: Could not create a bank! CREATE$BANK status = *1* Could not create another bank. OTM000106: SMM: buffer not allocated; size required (*1*bytes) must be greater than 0. CDGETCFIG returned an invalid value for MAX_SHARED_BANKS. OTM000107: SMM: buffer not allocated; size required (*1* bytes) is greater than the current maximum segment size (*2* bytes). The Buffer size requested was too big. OTM000108: smm_init: CDGETCFIG() returned status = *1* The call to CDGETCFIG to get MIN_SHARED_BANKS failed. OTM000109: smm_init: CDGETCFIG() returned invalid min banks = *1* CDGETCFIG returned an invalid value for MIN_SHARED_BANKS. OTM000200: Invalid characters found while encoding TYPE= *1*, character= *2*. All characters in type must conform to ASN.1 VisableString type. OTM000201: Invalid characters found while encoding SUB-TYPE= *1*, character = *2*. All characters in SUB-TYPE must conform to ASN.1 VisableString type. OTM000202: Invalid characters found while encoding X_OCTET user data, character= *1*. All characters in types X_OCTET, CARRAY, or STRING must be in the ASCII character set. Characters that cannot be encoded in 8 bits are invalid. OTM000203: Invalid characters found while encoding FIELD= *1*, of SUB-TYPE= *2*, character= *3*. All characters of type char must be in the ASCII character set. Characters that cannot be encoded in 8 bits are invalid

13 OTM000204: Invalid characters found while encoding FIELD= *1*, of SUB-TYPE= *2*, character= *3*. All characters of a string type must conform to ASN.1 PrintableString type. OTM000205: Invalid characters found while encoding FIELD= *1*, of SUB-TYPE= *2*, character= *3*. All characters of type carray must be in the ASCII character set. Characters that cannot be encoded in 8 bits are invalid. OTM000206: Invalid characters found while encoding FIELD= *1*, of SUB-TYPE= *2*, character= *3*. All characters of type chartranslate must be in the ASN.1 T61 character set. OTM000207: Invalid characters found while encoding SERVICE name= *1*, character= *2*. All characters of service name must be in the ASN.1 VisableString character set. OTM000208: Invalid characters found while decoding SERVICE name character= *1*. All characters of service name must be in the ASN.1 VisableString character set. OTM000209: Invalid characters found while decoding X_OCTET user data, character *1*. All characters in types X_OCTET, CARRAY, or STRING must be in the ASCII character set. Characters that cannot be decoded into 8 bits are invalid. OTM000210: Size of decoded value is too large to fit into SHORT FIELD= *1*. Short value must fit in 18 bits or less. OTM000211: Size of decoded value is too large to fit into LONG FIELD= *1*. Long value must fit in 36 bits or less. OTM000212: Size of decoded value is too large to fit into INTEGER FIELD= *1*. Integer value must fit in 36 bits or less. OTM000213: Invalid characters found while decoding FIELD= *1*, character= *2*. All characters of type CHAR or CARRAY must be in the ASCII character set. Characters that cannot be encoded in 8 bits are invalid. OTM000214: Special float values +/- infinity are not supported for FIELD= *1*. U2200's do not have a representation for +/- infinity. OTM000215: Invalid encoded base specified for FLOAT FIELD= *1*. Only base values of 2, 8, or 16 are supported. OTM000216: Invalid encoded mantissa specified for FLOAT FIELD= *1*. Mantissa will not fit into the U2200 internal representation for floats or doubles

14 OTM000217: Decoded float value too large to fit into a FLOAT field= *1*. Float values must fit within a 36 bit word on the U2200's. OTM000218: Special double values +/- infinity are not supported for FIELD= *1*. U2200's do not have a representation for +/- infinity. OTM000219: Invalid encoded base specified for DOUBLE FIELD= *1*. Only base values of 2, 8, or 16 are supported. OTM000220: Invalid encoded mantissa specified for DOUBLE FIELD= *1*. Mantissa will not fit into the U2200 internal representation for floats or doubles. OTM000221: Decoded double value too large to fit into a DOUBLE field= *1*. Float values must fit within a 72 bit word on the U2200's. OTM000222: Invalid characters found while decoding FIELD= *1*, character= *2*. All characters of type string must be in the PrintableString character set. Characters that cannot be encoded are invalid. OTM000223: Invalid characters found while decoding FIELD= *1*, character= *2*. All characters of type T61 must be encodable in 7 bits. Characters that cannot be encoded in 7 bits are invalid. OTM000224: Size of decoded DIAGNOSTIC too big to fit into integer field. Integer value must fit into 36 bits. OTM000225: Size of decoded USER CODE too big to fit into integer field. Integer value must fit into 36 bits. OTM000226: Size of decoded PCI too big to fit into integer field. Integer value must fit into 36 bits. OTM000227: Invalid characters found while decoding TYPE, character= *1*. All characters in type must conform to ASN.1 VisableString type. OTM000228: Invalid characters found while decoding SUB-TYPE, character = *1*. All characters in SUB-TYPE must conform to ASN.1 VisableString type. OTM000229: Decode error while processing TYPE= *1*, SUB-TYPE= *2*. Check prior log messages to determine type of error and correct it

15 of user buffer description file= *1* failed, status= *2*. Correct the problem and re-initialize the sub-system. OTM000231: User buffer description file: *1* is rolled out, status = *2*. The status is an octal value returned from ER CSF$ when attempting to assign the bdt file. Correct the problem and re-initialize the sub-system. OTM000232: User buffer description file: *1* is assigned to a different run, or a security violation occurred, status = *2*. The status is an octal value returned from ER CSF$ when attempting to assign the file. Correct the problem and re-initialize the sub-system. OTM000233: User buffer description file: *1* is catalogued with read or write key, status = *2*. The status is an octal value returned from ER CSF$ when attempting to assign the bdt file. The file has a read or write key, which is not supported at this time. Correct the problem and re-initialize the sub-system. OTM000234: User buffer description file: *1* could not be assigned, status = *2*. The status is an octal value returned from ER CSF$ when attempting to assign the bdt file. Correct the problem and re-initialize the sub-system. OTM000235: User buffer description file= *1* too small for last I/O, file size= *2* words. Re-assign the file larger and re-initialize the sub-system. OTM000236: User did not enter a buffer description file name into the config. A buffer description file name is required to permanently save user defined views. OTM000237: Invalid syntax in the buffer description file = *1*. Review the syntax of the buffer description file. The following rules apply: The file must follow proper U2200 filename syntax. Remote hosts are not supported. OTM000238: Invalid syntax in the language description file = *1*. Review the syntax of the language description file. The following rules apply: The file must follow proper U2200 filename syntax. Remote hosts are not supported. OTM000239: Could not fopen() file= *1*, errno= *2*. The C library function fopen() failed. Refer to the UC PRM to interpret the error number. OTM000240: Error processing Translation file. Illegal syntax for Translation Language Identifier, current tag= *1*. The Translation file must begin with the tag NAME="identifier". Language file entries are being flushed until a valid identifier is found

16 OTM000241: Error processing Translation file. Too many Translation Language Descriptions, current identifier = *1*. The Translation file description table for the above identifier contains too many entries. OTM000242: Error processing Translation file. Illegal table entry, current identifier= *1* illegal value = *2*. The Translation file description table entry must be greater than or equal to zero and less than 256. OTM000243: Error processing Translation file. Duplicate identifier = *1*. The duplicate entry will be ignored. OTM000244: BMalloc(): Buffer not allocated; size requested (*1* octal bytes) is greater than the maximum size allowed by malloc() (*2* octal bytes). The buffer size that was requested would exceed the currently available amount of space in the bank from which it would be malloc()ed. Consequently, the malloc() request is rejected. OTM000245: Buffer type *1* is invalid. Cause: The buffer type specified does not match a buffer type supported by OLTP-TM2200. Action: The user must change the buffer type specified to a valid buffer type supported by OLTP-TM2200. OTM000246: Buffer subtype *1* of buffer type *2* has not been installed. Cause: The specified buffer subtype has not been installed into OLTP-TM2200. Action: The buffer subtype needs to be installed into the OLTP-TM2200 product using the VADD processor. OTM000247: Buffer subtype *1* has been installed as type X_C_TYPE and the user has specified the type to be X_COMMON. Cause: The buffer subtype has been installed as an X_C_TYPE buffer. This is because when the subtype was installed the input view contained a member that can only be used by an X_C_TYPE buffer. Action: The user should specify the buffer type as X_C_TYPE or the buffer subtype should be reinstalled with all of its members being valid X_COMMON members. OTM000248: View mismatch: VIEW expects data of type short. Cause: In processing the input buffer, the view corresponding to the input buffer stored in the OLTP-TM2200 subsystem does not match the input data due to a data type mismatch. The view shows the next character should be of type short and the input buffer has a valid data type such as a long, which is incompatible. This is caused by a mismatch between the views installed on the remote host system and this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view

17 OTM000249: View mismatch: VIEW expects data that is a short array. Cause: In processing the input buffer, the view corresponding to the input buffer stored in the OLTP-TM2200 subsystem does not match the input data due to a data type mismatch. The view thinks the next character should be of type short array and the input buffer has a valid data type such as a long, which is incompatible. This is caused by a mismatch between the views installed on the remote host system and this system. Action: The user should verify that the views installed on each system are the same. The user should also verify that application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000250: View mismatch: VIEW expects data that is type long. Cause: In processing the input buffer, the view corresponding to the input buffer stored in the OLTP-TM2200 subsystem does not match the input data due to a data type mismatch. The view shows the next character should be of type long and the input buffer has a valid data type such as a short, which is incompatible. This is caused by a mismatch between the views installed on the remote host system and this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000251: View mismatch: VIEW expects data that is a long array. Cause: In processing the input buffer, the view corresponding to the input buffer stored in the OLTP-TM2200 subsystem does not match the input data due to a data type mismatch. The view shows the next character should be of type long array and the input buffer has a valid data type such as a short, which is incompatible. This is caused by a mismatch between the views installed on the remote host system and this system. Action: The user should verify that the views installed on each system are the same. The user should also verify that application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000252: View mismatch: VIEW expects data that is type char. Cause: In processing the input buffer, the view corresponding to the input buffer stored in the OLTP-TM2200 subsystem does not match the input data due to a data type mismatch. The view shows the next character should be of type char and the input buffer has a valid data type such as a short, which is incompatible. This is caused by a mismatch between the views installed on the remote host system and this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000253: View mismatch: VIEW expects data that is a character array. Cause: In processing the input buffer, the view corresponding to the input buffer stored in the OLTP-TM2200 subsystem does not match the input data due to a data type mismatch. The view shows the next character should be of type character array and the input buffer has a valid data type such as a short, which is incompatible. This is caused by a mismatch between the views installed on the remote host system and this system. Action: The user should verify that the views installed on each system are the same. The user should also verify that application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000254: View mismatch: VIEW expects data that is of type integer. Cause: In processing the input buffer, the view corresponding to the input buffer stored in the OLTP-TM2200 subsystem does not match the input data due to a data type mismatch. The view shows the next character should be of type integer and the input buffer has a valid data type such as a short, which is incompatible. This is caused by a mismatch between the views installed on the remote host system and this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view

18 OTM000255: View mismatch: VIEW expects data that is an integer array. Cause: In processing the input buffer, the view corresponding to the input buffer stored in the OLTP-TM2200 subsystem does not match the input data due to a data type mismatch. The view shows the next character should be of type integer array and the input buffer has a valid data type such as a short, which is incompatible. This is caused by a mismatch between the views installed on the remote host system and this system. Action: The user should verify that the views installed on each system are the same. The user should also verify that application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000256: View mismatch: VIEW expects data of type float. Cause: In processing the input buffer, the view corresponding to the input buffer stored in the OLTP-TM2200 subsystem does not match the input data due to a data type mismatch. The view shows the next character should be of type float and the input buffer has a valid data type such as a short, which is incompatible. This is caused by a mismatch between the views installed on the remote host system and this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000257: View mismatch: VIEW expects data of type float array. Cause: In processing the input buffer, the view corresponding to the input buffer stored in the OLTP-TM2200 subsystem does not match the input data due to a data type mismatch. The view shows the next character should be of type float array and the input buffer has a valid data type such as a short, which is incompatible. This is caused by a mismatch between the views installed on the remote host system and this system. Action: The user should verify that the views installed on each system are the same. The user should also verify that application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000258: View mismatch: VIEW expects data of type double. Cause: In processing the input buffer, the view corresponding to the input buffer stored in the OLTP-TM2200 subsystem does not match the input data due to a data type mismatch. The view shows the next character should be of type double and the input buffer has a valid data type such as a short, which is incompatible. This is caused by a mismatch between the views installed on the remote host system and this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000259: View mismatch: VIEW expects data of a type double array. Cause: In processing the input buffer, the view corresponding to the input buffer stored in the OLTP-TM2200 subsystem does not match the input data due to a data type mismatch. The view shows the next character should be of type double array and the input buffer has a valid data type such as a short, which is incompatible. This is caused by a mismatch between the views installed on the remote host system and this system. Action: The user should verify that the views installed on each system are the same. The user should also verify that application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000260: View mismatch: VIEW expects data of type character string. Cause: In processing the input buffer, the view corresponding to the input buffer stored in the OLTP-TM2200 subsystem does not match the input data due to a data type mismatch. The view shows the next character should be of type character string and the input buffer has a valid data type such as a short, which is incompatible. This is caused by a mismatch between the views installed on the remote host system and this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view

19 OTM000261: View mismatch: VIEW expects data of type octet. Cause: In processing the input buffer, the view corresponding to the input buffer stored in the OLTP-TM2200 subsystem does not match the input data due to a data type mismatch. The view shows the next character should be of type octet and the input buffer has a valid data type such as a short, which is incompatible. This is caused by a mismatch between the views installed on the remote host system and this system. Action: The user should verify that the views installed on each system are the same. The user should also verify that application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000262: View mismatch: VIEW expects data of type t61. Cause: In processing the input buffer, the view corresponding to the input buffer stored in the OLTP-TM2200 subsystem does not match the input data due to a data type mismatch. The view shows the next character should be of type t61 and the input buffer has a valid data type such as a short, which is incompatible. This is caused by a mismatch between the views installed on the remote host system and this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000263: View mismatch: Input data has type short, which doesn't match the view. Cause: The input data has a data type of short, which doesn't correspond to a short in the view stored in the OLTP-TM2200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on each system are the same. The user should also verify that application programs using copy or header files generated from OTM000264: View mismatch: Input data has type short array, which doesn't match the view. Cause: The input data has a data type of short array, which doesn't correspond to a short array in the view stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000265: View mismatch: Input data has type long, which doesn't match the view. Cause: The input data has a data type of long, which doesn't correspond to a long in the view stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on each system are the same. The user should also verify that application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000266: View mismatch: Input data has type long array, which doesn't match the view. Cause: The input data has a data type of long array, which doesn't correspond to a long array in the view stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view

20 OTM000267: View mismatch: Input data has type char, which doesn't match the view. Cause: The input data has a data type of char, which doesn't correspond to a char in the view stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on each system are the same. The user should also verify that application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000268: View mismatch: Input data has type char array, which doesn't match the view. Cause: The input data has a data type of char array, which doesn't correspond to a char array in the view stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000269: View mismatch: Input data has type integer, which doesn't match the view. Cause: The input data has a data type of integer, which doesn't correspond to a integer in the view stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on each system are the same. The user should also verify that application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000270: View mismatch: Input data has type integer array, which doesn't match the view. Cause: The input data has a data type of integer array, which doesn't correspond to a integer array in the view stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000271: View mismatch: Input data has type float, which doesn't match the view. Cause: The input data has a data type of float, which doesn't correspond to a float in the view stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on each system are the same. The user should also verify that application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000272: View mismatch: Input data has type float array, which doesn't match the view. Cause: The input data has a data type of float array, which doesn't correspond to a float array in the view stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view

21 OTM000273: View mismatch: Input data has type double, which doesn't match the view. Cause: The input data has a data type of double, which doesn't correspond to a double in the view stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on each system are the same. The user should also verify that application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000274: View mismatch: Input data has type double array, which doesn't match the view. Cause: The input data has a data type of double array, which doesn't correspond to a double array in the view stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000275: Cause: The input data has a data type of character string, which doesn't correspond to a character string in the view stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on each system are the same. The user should also verify that application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000276: View mismatch: Cause: The input data has a data type of octet, which doesn't correspond to a octet in the view stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000277: View mismatch: Input data has type t61, which doesn't match the view. Cause: The input data has a data type of t61, which doesn't correspond to a t61 in the view stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on each system are the same. The user should also verify that application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000278: Data truncation due to view size mismatch. Cause: The size of the data for the input buffer does not match the size the buffer's view as stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: The user should verify that the views installed on application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000279: Statistics counters have overflowed for client *1*. One of the client's statistics counters has overflowed and all of the client's counters have been reset to zero

22 OTM000280: User buffer description file: *1* is not catalogued or there is an f-cycle conflict, status = *2*. The status is an octal value returned from ER CSF$ when attempting to assign the file. Correct the problem and reinitialize the subsystem. OTM000281: Unable to allocate shared memory during initialization. This message is displayed if there is a problem allocating memory for the initial control structures. The MAX_SHARED_BANKS parameter should be inspected in the TMSCONFIG file and its value should be increased if necessary.. OTM000282: Unable to allocate a large bank. Not enough consecutive BDIs available. This message is displayed if there is a problem allocating memory. The amount of memory requested was too large to fit into one bank so a request was made to allocate a large bank. The creation of large banks requires the availability of consecutive small banks. There were not enough of these consecutive banks to service the request. OTM000283: View mismatch on reply buffer. Cause: The size of the data for the reply buffer does not match the size the buffer's view as stored in the OLTP-TM200 system. This is caused by a mismatch between the view on remote system and the view on this system. Action: Verify that the views installed on each system are the same and verify that application programs using copy or header files generated from these views have been generated from the correctly installed view. OTM000284: Working storage too small for reply. Cause: The size of the data for the reply buffer is larger than the working storage allocated for the reply. None of the reply data has been copied to the working storage. Action: The application program should allocate more working storage for the reply. OTM000285: Request buffer is too small for view. Cause: The buffer passed in as input is too small for the buffer subtype. Because of this, the input buffer is incomplete. Action: The application program should allocate a larger input buffer. OTM000286: Request to remote service *1* failed. All remote systems associated with the configured AE_ALIAS entries are down. Cause: The remote service was configured with multiple AE_ALIAS entries as a result of using load balancing or failover processing. The remote destinations associated with these AE_ALIAS configuration entries are all unavailable. Action: Check to make sure that the OSI-TP components associated with the configured AE_ALIAS entries are up and available on the remote systems. OTM000287: Remote AE_ALIAS *1* is DOWN. Cause: The remote system associated with the AE_ALIAS is down or unavailable. Because of this, requests cannot be sent to this remote destination. Action: Check to make sure that the OSI-TP components associated with the specified AE_ALIAS entry is up and available on the remote systems. OTM000288: Remote AE_ALIAS *1* is now UP. Cause: The remote system associated with the AE_ALIAS up and available. Requests can now be sent to this remote destination. Action: Typically, no action is required since this is an informational message

23 OTM001001: First message for TMSBUF. Doc for first TMSBUF message. *INFO OTM002001: *1* TMSCON debugging message. *ERROR OTM002002: *1* TMSCON error message. *WARNING OTM002003: *1* TMSCON warning message. OTM002004: *1* TMSCON information message. *INFO OTM003001: *1* TMSDUMP header. *INFO OTM003002: *1* TMSDUMP start string. *ERROR OTM003003: Illegal options specified. Cause: The command line options specified are not supported. Action: You must specify option a, o or both. *WARNING OTM003004: *1* is not a valid TMCOMMON object. Cause: The object specified is not a valid TMCOMMON object. Action: You must specify a valid TMCOMMON object. *INFO OTM003005: *1* TMSDUMP end string. OTM003006: Fatal error status received trying to write to dump file. Dump activity terminating. Cause: The file which the dump activity was trying to write to may be too small to contain all the dump information. This file may also be corrupt in some way causing a contingency. Action: Run the TMSDUMP processor again using a new larger file to capture the output into. If contingency snaps are produced, capture the output and report the problem to product support. OTM004001: TMSC status in command mode. This error is displayed when executing TMSC in command mode, and status is received

24 OTM004002: TMCOMMON FATAL ERROR *1*-*2*-*3* *4*-*5*-*6* This error is displayed when a TMCOMMON FATAL ERROR occurs. OTM004004: RUNID=*1*/*2*. This error is displayed when a TMCOMMON FATAL ERROR occurs to identify the offending run-id. OTM004005: *1* This error is displayed when a TMCOMMON FATAL ERROR occurs to identify the ERROR CODE and ERROR ADDRESS. OTM004006: TRANSACTION MANAGEMENT SYSTEM IS DOWN. This error is displayed after a TMCOMMON FATAL ERROR occurs to indicate that the Transaction Management System is now down. OTM004007: UNABLE TO CATALOG DUMP FILE: Status = *1*. This error is displayed if there is a problem in cataloging a dump file for a RASSLOG Entry. OTM004008: UNABLE TO ASSIGN DUMP FILE: Status = *1*. This error is displayed if there is a problem in assigning a dump file for a RASSLOG Entry. OTM004009: UNABLE TO OPEN DUMP FILE: *1*. This error is displayed if there is a problem in opening a dump file for a RASSLOG Entry. OTM004010: UNABLE TO WRITE TO DUMP FILE: Status = *1*. This error is displayed if there is a problem writing to the dump file. OTM004011: TMCOMMON DUMP GENERATED *1* *2*. This error is displayed to indicate that a dump file has been generated. OTM004012: *1*. This error message is displayed when an error is encountered in changing from state 0 to another state in the command handler. OTM004013: The receiver did not appear to terminate normally. This error message is displayed if there is a problem downing TMRCV. OTM004014: Maximum number of named traces exceeded. This error message is displayed if a request is made for a named trace and the maximum number has been reached. The maximum number of clients and/or servers that can be traced at one time is defined by the MAX_TRACE_NAMES configuration parameter in the TMS_LIMITS subsection of the *RESOURCES section of the tmsconfig configuration file. OTM004015: '*1*' is an invalid TMSC command. This error message is displayed whenever an illegal TMSC command is used. OTM004016: The '*1*' command requires a parameter

25 This error message is displayed whenever a command that requires a parameter is used with no parameter. OTM004017: STAT CLIENT command unavailable: Possible System Error. This error message is displayed if there is a problem getting information about a client. OTM004023: Internal function error, unknown status = *1*. Doc for TMSC message. OTM004024: TMRCV UNAVL: UNABLE TO START TMRCV. Doc for TMSC message. OTM004025: TMRCV UNAVL: ALREADY ACTIVE IN ANOTHER RUN. Doc for TMSC message. OTM004026: TMTIMER UNAVL: ALREADY ACTIVE IN ANOTHER RUN. Doc for TMSC message. OTM004027: Software version incompatibility. Doc for TMSC message. OTM004033: '*1*' is an invalid TMSC keyword. This error message is displayed when an illegal TMSC keyword is used. OTM004034: KEYWORD '*1*' ACCEPTED. Doc for TMSC message. OTM004035: *1* Message displayed to echo 1-word console input to event log. OTM004036: *1* *2* Message displayed to echo 2-word console input to event log. OTM004037: *1* *2* *3* Message displayed to echo 3-word console input to event log. OTM004038: TD2200 UNAVL: ALREADY ACTIVE IN ANOTHER RUN. Doc for TMSC message. OTM004039: TMSC SHUT DOWN AT *1*-*2*-*3* *4**5*:*6* This is the message displayed on normal termination of TMSC. OTM004040: ABNORMAL TERMINATION AT *1*-*2*-*3* *4**5*:*6* This is the message displayed on abnormal termination of TMSC

26 OTM004041: OLTP-TM2200 *1* TMSC START UP AT *2*-*3*-*4* *5**6*:*7* This is the message displayed on start up of TMSC. OTM004042: TMSC START-UP ABORTED: TMSC ALREADY ACTIVE IN ANOTHER RUN This message is displayed if you attempt to start TMSC, but it has already been started in another run. OTM004043: TMSC START-UP ABORTED: LOAD TMSCONFIG FIRST This message is displayed if you attempt to start TMSC, but has not yet loaded the TMSCONFIG. Load TMSCONFIG and try again. OTM004044: Recovery Server did not initialize. This message is displayed if there are problems UP-ing the TRM Recovery Server. OTM004045: Run TMSDUMP to see user log messages. This message is displayed if there are problems UP-ing the TRM Recovery Server to instruct the user to run TMSDUMP to find the problem. OTM004046: Illegal options specified. This message is displayed if you have specified illegal options on the TMSC processor call line. Check the Operations Specification for proper options and try again. OTM004047: ABNORMAL TERMINATION INITIATED AT *1*-*2*-*3* *4**5*:*6* This error message is displayed whenever an error is encountered in changing from state 0 to another state in the command handler. OTM004048: *1* Message displayed to handle error messages from the command handler that have no inserts. OTM004049: *1* Message used to send 1-word remarks to the operator's console from the command handler. OTM004050: *1* *2* Message used to send 2-word remarks to the operator's console from the command handler. OTM004051: *1* *2* *3* Message used to send 3-word remarks to the operator's console from the command handler. OTM004052: TMHAAD UNAVL: TMHAAD UTILITY MUST BE STARTED MANUALLY This error message is displayed if the user attempts to up the TMHAAD Utility from within TMSC. TMHAAD must be started manually. OTM004053: *1* TRACE ON FOR SERVER (*2*) This message is displayed to indicate that client/server tracing was just turned on for the specified server. This is not an error. OTM004054: *1* TRACE ON FOR CLIENT (*2*) This message is displayed to indicate that client/server tracing was just turned on for the specified client. This is not an error

27 OTM004055: SERVER *1* *2* This message is displayed to indicate that client/server tracing is currently turned on for the specified server at the specified level. This is not an error. OTM004056: CLIENT *1* *2* This message is displayed to indicate that client/server tracing is currently turned on for the specified client at the specified level. This is not an error. OTM004057: TRACE OFF FOR SERVER (*1*) This message is displayed to indicate that client/server tracing has just been turned off for the specified server. This is not an error. OTM004058: TRACE OFF FOR CLIENT (*1*) This message is displayed to indicate that client/server tracing has just been turned off for the specified client. This is not an error. OTM004059: CLIENTS ATTACHED: (*1*) *2* This message is displayed to indicate the number of clients currently attached. OTM004060: CLIENTS ATTACHED: (*1*) This message is displayed to indicate the number of clients currently attached. OTM004061: *SHARED MEMORY DATA: *1* This message is displayed as the header when information has been requested about the amount of shared data in use. OTM004062: SERVERS ATTACHED: (*1*) *2* This message is displayed to indicate the number of servers currently attached. OTM004063: SERVERS ATTACHED: (*1*) This message is displayed to indicate the number of servers currently attached. OTM004064: Console keyin tag specified in TMSCONFIG is a system reserved tag. Cause: The TMSCONFIG file configuration parameter CONS_KEYIN has been set to a value that is currently being used by the system. Action: The TMSCONFIG file must be changed to use a different CONS_KEYIN tag. The OLTP-TM2200 product must then be deactivated and reloaded to activate the new configuration value. OTM004065: ER KEYIN$ failed due to security violation. Subsystem owner must have ER KEYIN$/COM$ security privilege. Cause: The OLTP-TM2200 TMSCONFIG configuration file has a CONS_KEYIN tag specified and the OLTP-TM2200 subsystem is not allowed to register this tag due to a security problem. The subsystem owner must have the security privilege ER KEYIN$/COM$ before the specified keyin can be registered with the system. Action: The security attributes of the user-id owner of the OLTP-TM2200 installation file TM$COMMON must be modified using SIMAN to enable the use of the ER KEYIN$/COM$ executive requests. The OLTP-TM2200 subsystem must then be deactivated and restarted to activate the new security attributes

28 OTM004066: ER KEYIN$ error - console keyin in use by another run Cause: The OLTP-TM2200 TMSCONFIG configuration file has a CONS_KEYIN tag specified which is being used by another run. Action: The user should make sure that if the TMSC run had been active before, that it has completely terminated before restarting. If another TMSC run is not active, the TMSCONFIG file parameter CONS_KEYIN should be changed to a different value since another run has chosen the current value. The OLTP-TM2200 subsystem must then be deactivated and restarted to activate the new configuration. OTM004067: ER KEYIN$ error - octal status *1*. Cause: An error occurred trying to register the console keyin specified by the CONS_KEYIN parameter of the OLTP-TM2200 TMSCONFIG file. Action: Check the Exec System Software Executive Requests Programming Reference Manual for the status indicated. If the status indicates a software problem, submit a UCF against the appropriate product. OTM004068: Enter command This message is displayed to indicate that the TMSC processor is in command mode and is able to accept commands from users in console mode. OTM004069: OCMS UNAVL: UNABLE TO START OCMS This message is displayed to indicate that OCMS could not be started. Check the event log for possible reasons. OTM004070: SERVER: *1* Time Initialized: *2* All time measurements are in milliseconds, and all SUP measurements are in increments of 200 microseconds. avg = average num = number OTM004071: SERVICE: *1* Time Initialized: *2* All time measurements are in milliseconds, and all SUP measurements are in increments of 200 microseconds. avg = average num = number OTM004072: CLIENT: *1* Time Initialized: *2* All time measurements are in milliseconds, and all SUP measurements are in increments of 200 microseconds. avg = average num = number OTM004073: svc_resp_time: *1* SUPs_for_resp: *2* OTM004074: avg_dec_time: *1* avg_dec_sups: *2* OTM004075: avg_enc_time: *1* avg_enc_sups: *2* OTM004076: num_failures: *1* num_aborts: *2* OTM004077: time_active: *1* sleeps: *2* sleeping_time: *3* OTM004078: num_sends: *1* num_receives: *2* OTM004079: num_non2pc_req: *1* num_non2pc_call: *2* OTM004080: num_2pc_req: *1* num_2pc_calls: *2* num_2pc_txns: *3* OTM004081: num_txn_commits: *1* num_txn_rollbacks: *2* num_txn_timeouts: *3*