Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Using Messages With Identifiers : D2: DB2 Gateway

D2: DB2 Gateway
S6BD2000I
%
DB2 Gateway
This is an echo of the start up parameters.
No action required.
S6BD2001I
Starting gateway initialization
DB2 Gateway
Object Service Broker gateway initialization is starting.
No action is required.
S6BD2002E
DB2 CAF % ERROR: % % % %
DB2 Gateway
The CAF CONNECT call failed with the specified DB2 reason code. A DB2 Call Attach Facility (CAF) call failed. The first variable identifies the type of call (CONNECT, OPEN, CLOSE, or DISCONNECT). The second variable identifies the DB2 reason code for the failure. The third variable indicates the DB2 SSID that the call was issued against. The fourth displays the DB2 plan name being OPENED or CLOSED. The fifth is the DB2 error message, if available, that describes the reason for the OPEN plan failure.
The reason code is described in the DB2 Messages & Codes manual. Check this manual for the meaning of the error code and take the action dictated. Verify that the CAF call is being issued against the correct DB2 SSID and/or PLAN. If not, make sure the gateway was started with the correct DB2 SSID and/or PLAN.
S6BD2003E
TIBCO(r) Object Service Broker "%" is not available
DB2 Gateway
The external gateway for DB2 data has not been connected to the Data Object Broker identified by the indicated APPLID.
Ensure that the TDSAPPL and MODLAPPL parameters are correct. Verify that the Data Object Broker is active before starting the gateway.
S6BD2004I
DB2 Gateway terminated
DB2 Gateway
The DB2 Gateway terminated. The serverid and userid are indicated in the message prefix.
No action is required.
S6BD2005E
Startup parameter format error
DB2 Gateway
The gateway start-up parameters contain a syntax error. The parameter in question was echoed by message S6BD2000I.
Correct the parameter format.
S6BD2006E
The previous startup parameter is invalid
DB2 Gateway
The start-up parameter value is invalid. The parameter value appears in the preceding S6BD2000I message.
Correct the parameter and start the gateway again.
S6BD2007E
Fail safe table definition ; not found
DB2 Gateway
The table name specified cannot be found.
Determine the fail safe table name and correct it. The default table name is @DB2FSTRXDB.
S6BD2023E
Required input parameter missing
DB2 Gateway
A required gateway start-up parameter is missing. The TDSAPPL and SSID parameters are both required.
Provide the missing parameter and restart the gateway.
S6BD2024E
Error attaching gateway subtask
DB2 Gateway
An error was encountered during the attachment of a gateway subtask.
Contact TIBCO Support.
S6BD2026E
Failed to open file: "%"
DB2 Gateway
The specified file cannot be opened.
Check the file. If you cannot find a problem with the file, contact TIBCO Support.
S6BD2028E
Gateway subtask initialization failed: "%"
DB2 Gateway
During gateway subtask startup one of the storage initialization functions failed:
Do the following:
1.
2.
3.
S6BD2029E
Definition bind area initialization failed
DB2 Gateway
An error was encountered while initializing the table definition bind area.
Do the following:
1.
2.
Verify that the POOLSIZE startup parameter is specified correctly.
3.
4.
S6BD2030E
TIBCO(r) Object Service Broker "%" version mismatch
DB2 Gateway
The gateway is attempting to connect to a Data Object Broker that is not at the same release level.
Verify the TDS start-up parameter. Contact your system administrator to find out what release of the gateway and TIBCO(r) Object Service Broker were installed.
S6BD2031I
Gateway connected to TIBCO(r) Object Service Broker "%"
DB2 Gateway
The DB2 Gateway connected with the TIBCO(r) Object Service Broker running under the indicated APPLID.
No action is required.
S6BD2032E
CLOSE PLAN(%) SSID(%) %
DB2 Gateway
The gateway closed the DB2 plan from the specified SSID for the indicated reason.
No action is required.
S6BD2033E
SQL ERROR FOR: % CODE: % VARIABLES: %
DB2 Gateway
The gateway received an SQL error with the indicated code after issuing the indicated SQL call to DB2.
Refer to the DB2 messages and codes for further information and take the action indicated for the code that was received based on the variables.
S6BD2034E
SQL WARNING FOR: % CODE: % WARNING: % VARIABLES: %
DB2 Gateway
The gateway received an SQL warning of the indicated code after issuing the indicated SQL statement to DB2.
Refer to the DB2 messages and codes and take the action indicated for the code that was received.
S6BD2036E
SQLCODE % %. %
DB2 Gateway
A DB2 SQL call returned the indicated sqlcode. The third parameter is the text of the DB2 message.
Refer to the DB2 messages and codes for further information and take the action indicated for the code received.
S6BD2037E
No columns in the DB2 table definition
DB2 Gateway
The DB2 table definition contains no columns.
Correct the DB2 table definition from the DB2 environment.
S6BD2038E
Occurrence not found
DB2 Gateway
The requested occurrence was not found in the DB2 table.
No action required.
S6BD2039E
Static SQL is not supported after partial access
DB2 Gateway
Static SQL was used to satisfy part of the request, but is not supported to perform the remainder of the request.
Do the following:
1.
Regenerate the Static SQL, for the gateway for the table being accessed.
2.
3.
To default back to Dynamic SQL for the request, use the Object Service Broker Table Definer to save the definition of the table.
S6BD2040E
DB2 row too large
DB2 Gateway
The DB2 row instance is too large for the gateway buffer.
Contact TIBCO Support.
S6BD2041E
Unknown DB2 column type
DB2 Gateway
The gateway encountered a DB2 column with a COLTYPE that is not known.
Contact TIBCO Support.
S6BD2042E
No columns found for requested table
DB2 Gateway
The DB2 table definition corresponding to the Object Service Broker external table has no columns defined.
Correct the DB2 table definition. Contact TIBCO Support if necessary.
S6BD2043E
Selection string error
DB2 Gateway
An error was encountered when parsing the selection string.
Contact TIBCO Support.
S6BD2044E
DB2 column not found for: "%"
DB2 Gateway
The DB2 column mapped to one of the Object Service Broker external table fields does not exist in the DB2 table definition. This could be caused when the named DB2 column is also a DB2 reserved word.
Correct the external table or the DB2 table definition.
S6BD2046E
Cursor not found for subsequent Forall
DB2 Gateway
The gateway encountered an error when trying to obtain the next set of records during FORALL processing. The cursor associated with the request in progress could not be found.
Contact TIBCO Support.
S6BD2047E
No available cursors for request
DB2 Gateway
The limit of nested GETs or FORALLs on DB2 tables was exceeded.
Verify that the transaction logic is correct. Contact TIBCO Support if necessary.
S6BD2049E
Missing definition of host variable
DB2 Gateway
When trying to get a column value from the row retrieved, the host variable that is to contain it could not be found.
Do the following:
1.
Regenerate the Static SQL, for the gateway for the table being accessed.
2.
3.
To default back to Dynamic SQL for the request, use the Object Service Broker Table Definer to save the definition of the table.
S6BD2051E
CONVERSION ERROR on field %: %
DB2 Gateway
When converting the field or parameter value to the DB2 syntax, an error occurred.
Verify your definitions.
S6BD2052E
Maximum number of tables exceeded
DB2 Gateway
The maximum number of DB2 tables that can be accessed in one transaction was exceeded.
Verify transaction logic. Increase POOLSIZE parameter if necessary.
S6BD2053E
Gateway cannot store table definition for: "%"
DB2 Gateway
Attempt to bind a new table definition failed.
Restart the gateway with a larger POOLSIZE.
S6BD2054E
Unsupported request: "%"
DB2 Gateway
The request received by the gateway is not supported.
Contact TIBCO Support.
S6BD2055E
Security information was not received
DB2 Gateway
The TIBCO(r) Object Service Broker release level does not match the Gateway release level or a severe error occurred.
Ensure that the gateway was installed at the current release level. If this was done and the problem persists, contact TIBCO Support.
S6BD2056E
Current group value cannot be used as a valid userid
DB2 Gateway
The gateway is configured to use the Current Group as the DB2 primary authorization ID. The group of the current user cannot be used as a valid DB2 primary authorization ID.
Make sure the user belongs to a TIBCO(r) Object Service Broker group and the length of the TIBCO(r) Object Service Broker group does not exceed 8 bytes.
S6BD2057E
Blank userid received
DB2 Gateway
Security requirements are not fulfilled according to documented procedures, or a version mismatch exists between the gateway and the Object Service Broker Execution Environment.
Correct and retry.
S6BD2058E
Userid "%" is not authorized to execute plan "%", or plan "%" does not exist
DB2 Gateway
You are not authorized to execute the named plan, or the named plan does not exist.
Grant execute on the plan name to the userid; and/or define the plan to DB2.
S6BD2059E
Userid "%" matches a DB2 privileged authorization id and is rejected
DB2 Gateway
The Object Service Broker userid mentioned in the message matches a DB2 primary authorization ID coded in macro HRNSECDZ. The IDs in HRNSECDZ are privileged DB2 authorization IDs and cannot be used to access DB2 from Object Service Broker. These IDs are defined and coded by the customer.
Do one of the following;
S6BD2062E
Userid "%" is not authorized to start an DB2 Gateway
DB2 Gateway
HRNSECD2 (the DB2 security macro) within DSN3@ATH (DB2 connection authorization exit) could not match the userid used to start the DB2 Gateway with one of the IDs within HRNSECDT.
Verify that:
The macro HRNSECD2 was correctly installed in DSN3@ATH.
The userid used to start the DB2 Gateway is defined in table HRNSECDT.
S6BD2063E
DB2 primary authorization id was not set to the TIBCO(r) Object Service Broker userid
DB2 Gateway
The DB2 Gateway was started with SECLEVEL=1 but macro HRNSECD2 in DB2 connection authorization exit DSN3@ATH failed to set the DB2 primary authorization ID with the TIBCO(r) Object Service Broker userid.
Verify that:
S6BD2064I
DEBUG: %
DB2 Gateway
An echo of the CAF debug messages. This is displayed if DEBUG is on.
No action required.
S6BD2066E
Missing value for table parameter
DB2 Gateway
The table is parameterized and a parameter value is missing.
Contact TIBCO Support.
S6BD2067E
Unsupported operator: "%"
DB2 Gateway
The operator specified in the selection is not supported.
Contact TIBCO Support.
S6BD2069E
Field in key selection was not found in table
DB2 Gateway
The field specified in the selection was not found in the definition of the table.
Contact TIBCO Support.
S6BD2070E
Field in ordered clause was not found in table
DB2 Gateway
A field in the order statement was not found in the definition of the table.
Do the following:
1.
2.
3.
4.
5.
S6BD2071E
DB2 SQL statement too long
DB2 Gateway
The SQL statement that the gateway is attempting to build is too large for the buffer that the gateway is using.
Contact TIBCO Support.
S6BD2072E
No DB2 threads available
DB2 Gateway
The maximum number of concurrent identify level agents has been exceeded. The DB2 Gateway detected a 00F30055 error code.
User response: Try again later.
System Programmer Response: Ensure that the DB2 system parameters controlling the maximum number of concurrent identifies are correct. These system parameters are Max Users, Max TSO connect and Max Batch connect on installation panel DSNTIPE.
S6BD2073I
The DB2 Gateway is not running authorized
DB2 Gateway
The DB2 Gateway is being executed from an unauthorized library or one or more of the libraries in the STEPLIB concatenation is unauthorized.
Ensure that the library the DB2 Gateway executes from, and all the libraries in the STEPLIB concatenation, are authorized.
S6BD2074I
The DB2 Gateway is running authorized
DB2 Gateway
The gateway is running in authorized mode.
None.
S6BD2075I
The DB2 Gateway is non-swappable
DB2 Gateway
The DB2 Gateway address space is non-swappable.
None.
S6BD2076I
The DB2 Gateway is swappable
DB2 Gateway
The DB2 Gateway address space is swappable. In a high volume system this can degrade performance.
None.
S6BD2077I
DB2 Release ; Level ;
DB2 Gateway
Shows the DB2 Release Level.
None.
S6BD2078I
DB2 Application Encoding Scheme is ;
DB2 Gateway
Shows the DB2 Application Encoding Scheme found in DSNHDECP.
None.
S6BD2079E
Unable to use static sql: table=% module=% %
DB2 Gateway
The DB2 Gateway has failed to load the static SQL module for the table. There is a short description as to why the module cannot be loaded/used.
Either disable static SQL for the table or correct the indicated module.
S6BD2099E
Gateway subtask ABNORMALLY TERMINATED: "%"
DB2 Gateway
The DB2 Gateway task abended.
Previous messages may indicate the cause for the abend. Contact TIBCO Support.
S6BD2100I
REQUEST: % % %
DB2 Gateway
The message is an echo of the Object Service Broker requests. It is displayed if DEBUG is on.
No action required.
S6BD2401I
% Gateway shutdown requested, reason="%"
DB2 Gateway
The gateway received a request to shut down from the TIBCO(r) Object Service Broker The description of the reason codes follows:
0004 - A stopserver all*** was requested. All the gateways of this type will be terminated.
0008 - A stopserver gateway userid was requested. Only this gateway will be terminated.
0010 - The TIBCO(r) Object Service Broker resource directory is full. Contact TIBCO Support.
0014 - The maximum number of gateways has been exceeded. Increase the MAXDBMS parameter in the TIBCO(r) Data Object Broker and restart, or contact TIBCO Support.
00018 - The gateway anchor list has overflowed. Contact TIBCO Support.
No further action is required.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved