Error Messages
The following describes client error messages.
Client/Server Basic Error Messages
Section titled “Client/Server Basic Error Messages”150- Explanation:
- Server system error. For more information refer to TCB(20) to get the server error number. Also see Virtual Error Table below.
171- Explanation:
- Undefined Link.
Virtual Error Table
- Explanation:
- Errors accessing SQL Server tables will generate text errors in a Virtual Error Table. The Virtual Error Table is defined as the Link: OOLSQLER. Before using the Virtual Error Table, you will need to update this Link to reflect your Server ID.
After any error trying to access SQL Server data, you can check the Virtual Error Table for more detailed SQL Server error messages. Often this table will contain more than one error message, so you will need to read records until you reach end of file. The Virtual Error Table is accessed like an SQL Server table but it is stored in Thoroughbred memory. It doesn’t actually make an SQL Server call. The following is sample code on accessing the Virtual Error Table:
CH = UNT;
FORMAT INCLUDE #OOFSQLER
OPEN (CH,OPT=”LINK”) “OOLSQLER”;
CLEAR ERC;
WHILE ERC <> 2;
READ(CH,ERC=2) #OOFSQLER;
IF ERC = 0
PRINT #OOFSQLER
FI;
WEND
Thoroughbred Basic Startup Messages
Section titled “Thoroughbred Basic Startup Messages”No match for server id in SERVER.MAP- Explanation:
- The two-character server id defined in the IPLINPUT file cannot be located in the SERVER.MAP file.
- Action:
- Verify contents of both files.
Could not resolve Network address for Thoroughbred foreign file server- Explanation:
- System does not understand the Network address configured in the SERVER.MAP file.
- Action:
- Verify that the address or host name in the SERVER.MAP file is a valid value for the system. On systems that use DNS, be sure the system is configured.
Invalid Thoroughbred foreign file server type- Explanation:
- The system found an invalid value in the server type parameter in the IPLINPUT server device line.
- Action:
- Verify that the server device line is defined properly with a Server type of 4.
Cannot mix SQL and Windows Authentication for SQL Server- Explanation:
- The IPLINPUT file indicates Windows Authentication but also includes an SQL Server Login/Password Authentication.
- Action:
- Either set the Authentication Type to 1 (SQL Server) or remove the SQL Server Login/Password value.
Could not connect to Thoroughbred foreign file server- Explanation:
- Thoroughbred Basic could not establish communication to the tsmssqlmgr manager.
- Action:
- Verify that the Thoroughbred Manager service is started.
From the TS DataServer for MS SQL Server, version 8.9.1. Open this page in the PDF