![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
This is an echo of the start up parameters.Object Service Broker gateway initialization is starting.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.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.The DB2 Gateway terminated. The serverid and userid are indicated in the message prefix.The gateway start-up parameters contain a syntax error. The parameter in question was echoed by message S6BD2000I.The start-up parameter value is invalid. The parameter value appears in the preceding S6BD2000I message.Correct the parameter and start the gateway again.Determine the fail safe table name and correct it. The default table name is @DB2FSTRXDB.A required gateway start-up parameter is missing. The TDSAPPL and SSID parameters are both required.Provide the missing parameter and restart the gateway.An error was encountered during the attachment of a gateway subtask.Check the file. If you cannot find a problem with the file, contact TIBCO Support.During gateway subtask startup one of the storage initialization functions failed:
• HDRSBCEV - Initialization of the C environment failed.
1. Verify that the installation procedures were correct.
2. Verify that the JOB/TASK region size is sufficient.
3. Contact TIBCO Support if the first two items are correct.An error was encountered while initializing the table definition bind area.
2. Verify that the POOLSIZE startup parameter is specified correctly.
3. Verify that the JOB/TASK region size is sufficient.
4. Contact TIBCO Support if the first two items are correct.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.Gateway connected to TIBCO(r) Object Service Broker "%"The DB2 Gateway connected with the TIBCO(r) Object Service Broker running under the indicated APPLID.The gateway closed the DB2 plan from the specified SSID for the indicated reason.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.SQL WARNING FOR: % CODE: % WARNING: % VARIABLES: %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.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.The DB2 table definition contains no columns.Correct the DB2 table definition from the DB2 environment.The requested occurrence was not found in the DB2 table.Static SQL was used to satisfy part of the request, but is not supported to perform the remainder of the request.
1. Regenerate the Static SQL, for the gateway for the table being accessed.To default back to Dynamic SQL for the request, use the Object Service Broker Table Definer to save the definition of the table.The DB2 row instance is too large for the gateway buffer.The gateway encountered a DB2 column with a COLTYPE that is not known.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.An error was encountered when parsing the selection string.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.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.The limit of nested GETs or FORALLs on DB2 tables was exceeded.Verify that the transaction logic is correct. Contact TIBCO Support if necessary.When trying to get a column value from the row retrieved, the host variable that is to contain it could not be found.
1. Regenerate the Static SQL, for the gateway for the table being accessed.To default back to Dynamic SQL for the request, use the Object Service Broker Table Definer to save the definition of the table.When converting the field or parameter value to the DB2 syntax, an error occurred.The maximum number of DB2 tables that can be accessed in one transaction was exceeded.Verify transaction logic. Increase POOLSIZE parameter if necessary.Attempt to bind a new table definition failed.Restart the gateway with a larger POOLSIZE.The request received by the gateway is not supported.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.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.Security requirements are not fulfilled according to documented procedures, or a version mismatch exists between the gateway and the Object Service Broker Execution Environment.Userid "%" is not authorized to execute plan "%", or plan "%" does not existYou 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.Userid "%" matches a DB2 privileged authorization id and is rejectedThe 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.
• Use another Object Service Broker userid to access DB2.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.
• The macro HRNSECD2 was correctly installed in DSN3@ATH.
• The userid used to start the DB2 Gateway is defined in table HRNSECDT.DB2 primary authorization id was not set to the TIBCO(r) Object Service Broker useridThe 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.
• The macro HRNSECD2 was correctly installed in DSN3@ATHAn echo of the CAF debug messages. This is displayed if DEBUG is on.The table is parameterized and a parameter value is missing.The operator specified in the selection is not supported.The field specified in the selection was not found in the definition of the table.A field in the order statement was not found in the definition of the table.The SQL statement that the gateway is attempting to build is too large for the buffer that the gateway is using.The maximum number of concurrent identify level agents has been exceeded. The DB2 Gateway detected a 00F30055 error code.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.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.The gateway is running in authorized mode.The DB2 Gateway address space is non-swappable.The DB2 Gateway address space is swappable. In a high volume system this can degrade performance.Shows the DB2 Application Encoding Scheme found in DSNHDECP.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.Gateway subtask ABNORMALLY TERMINATED: "%"Previous messages may indicate the cause for the abend. Contact TIBCO Support.The message is an echo of the Object Service Broker requests. It is displayed if DEBUG is on.The gateway received a request to shut down from the TIBCO(r) Object Service Broker The description of the reason codes follows:
• 0000 - TIBCO(r) Object Service Broker is shutting down.
• 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.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |