![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
explanation of return/reason code for connection failureWhen a connection to a Data Object Broker fails, the error message displayed may contain a return code or a reason code in the "sense data" field. Some of the codes require the user to correct a setting and then retry; others represent severe problems over which the user has no control.Other error messages reference this message for the descriptions of these codes.
• 00 - Compatibility code not passed in connect parameters. Coding error.
• 04 - Compatibility-level error, Execution Environment not compatible. Attempting to connect to a Data Object Broker that is at a different release level.
• 08 - Connection type parameter not supplied (RGNTYPE=). Coding error.
• 0C - USERID parameter not supplied. Coding error.
• 10 - Connection type value is not supported. Coding error.
• 14 - Fail Safe level 1 required. Attempting to connect to a Data Object Broker that requires at least Fail Safe level-1 (contingent commit) support with a gateway/server or Data Object Broker that supports only Fail Safe level 0 (serial commit).
• 18 - Server type/ID not specified (spec block too small). Coding error.
• 1C - TAM Server rejected, combined Execution Environment not specified. The remote peer server requires two connections: an Execution Environment and a server. During the attempt to connect the rule server, the Execution Environment to which it was to be coupled could not be found.
• 20 - Fail Safe level 2 required. Attempting to connect to a Data Object Broker that requires at least Fail Safe level-1 (contingent commit) support with a gateway/server or Data Object Broker that supports only Fail Safe level 0 (serial commit).
• 28 - Userid is invalid. Either the passed userid is blank or you are attempting to use a superseded version of S6BBRULH.
• 2C - Server path ID not specified. Coding error.
• 30 - Registration characteristics different than configured. The characteristics specified in the path management system do not match those supplied in the connection list.
• 34 - Expected associated connection not found. Some gateways require two connections: an Execution Environment and a gateway. During the attempt to connect the gateway, the Execution Environment to which it was to be coupled could not be found.
• 38 - Specified associated userid is duplicated. Some gateways require two connections: an Execution Environment and a gateway. During the attempt to connect the gateway, a search of the user list determined that the target Execution Environment userid was used in more than one connection. Therefore it could not be determined which one was appropriate.
• 00 - Data Object Broker is not accepting logons. The Data Object Broker is currently in a status that prevents the acceptance of connections.
• 04 - Storage not available to support connection. Each connection to the Data Object Broker requires a block of private space. The pool containing the space is currently completely allocated.
• 08 - Connections currently restricted to operators. The Data Object Broker is currently in a status that prevents the acceptance of connections other than operator sessions (IR ADMIN CLIST).
• OC - Batch connections are not being accepted. The Data Object Broker is currently in a status that prevents the acceptance of connections from batch jobs.
• 10 - User/Server already logged on. The userid specified in the connection is the same as an existing connection.
• 14 - Maximum Execution Environments limit exceeded. The number of Execution Environments has reached the defined limit (usermax).
• 18 - An inbound connection from a Data Object Broker is not predefined to the resource management facility.
• 1C - Logon is rejected because the system is quiesced.
• 20 - An external DBMS gateway is not defined to the resource management facility.
• 24 - EXTN resource limits already at maximum for path.
• 28 - Connections only accepted via a Message Switch address space
• 3C - Wild card resource exceeds defined resource limit.Based on the return and reason codes, do one of the following:
•
• 04 - Use the same release-level libraries for the Data Object Broker and the item attempting to connect to it.
• 1C - Try to determine if the Execution Environment failed, and then contact TIBCO Support.
• 30 - Check the joblog for a S6BKC081 message, which will identify the characteristics that were specified with the connection. Adjust the connection request or the path management so the characteristics match.
• 34 - Try to determine if the Execution Environment failed, and then contact TIBCO Support.
• 38 - Try to eliminate duplicate Execution Engine userids. If this does not work, contact TIBCO Support.
•
• 00 - Wait for the condition to clear and try again later - the Data Object Broker is not accepting logon requests at this time, check the log for outstanding error conditions.
• 04 - Try again later or increase the MAXUSERS parameter.
• 08 - Wait for the condition to clear and try again later - the Data Object Broker is only accepting logon requests for administration sessions.
• 0C - Wait for the condition to clear and try again later - the Data Object Broker is not accepting logon requests for batch sessions at this time. Check the log for outstanding error conditions.
• 10 - Try to determine why the userids are duplicated or retry the connection with a different userid.
• 14 - Execution Environment session limit reached, retry later or increase the USERMAX limit.
• 18 - Define the incoming Data Object Broker via the Administrator Resource Management function.
• 1C - Check the joblog for outstanding journal spins and try again later.
• 20 - Define the required gateway via the Administrator Resource Management Facility.
• 24 - Increase the schedule limits or retry the connection later (see the Administrator Resource Management Facility).
• 28 - Modify the connecting session to connect to a Message Switch address space.
• 3C - Increase the MAXRESOURCES Data Object Broker parameter.INVALID PEER COMMID SPECIFIED FOR PEERCANCEL REQUEST, REQUEST IGNOREDAn invalid PEERCANCEL command was issued. The COMMID specified in the console command is not defined to the Resource Manager.Reissue the PEERCANCEL command with a valid peer identifier.INBOUND PEER CONNECTION REJECTED DUE TO DUPLICATE USERID, &, HIN &The message identifies the userid and source of an inbound peer connection that has been prevented from logging on to the Data Object Broker. Peer connections must have a unique userid, whether or not the DUPUSERID parameter has been coded. The peer connection has not been established.Determine why a duplicate userid was generated by the remote peer and correct the situation.The duplicate userid may be the result of a configuration error, such as multiple Data Object Brokers using the same userid prefix. In this case, correct the configuration and restart the HRN connections from the remote Data Object Broker.SVC DUMP GENERATED VIA THE ADMINISTRATOR UTILITYAn SVC dump of the Data Object Broker was requested via the Administrator Diagnostics Dumps feature.SEVERE SESSION LIMIT MANAGEMENT ERROR DETECTED, DUMP REQUESTED-INCRDuring the process used to control licensed limits, the internal bitmap masks were not set. This error indicates a problem with the licensing process that is beyond the control of the site.A system dump is generated. Please forward the dump and the Data Object Broker and Native Execution Environment joblogs to TIBCO Support.SEVERE SESSION LIMIT MANAGEMENT ERROR DETECTED, DUMP REQUESTED-DECRDuring the processing of licensed limits, the in-use count was decremented when it was already zero. This is an internal control error that is beyond the control of the site.A system dump is generated. Please forward the dump and the Data Object Broker and Native Execution Environment joblogs to TIBCO Support for analysis.RESOURCE MANAGEMENT ERROR DETECTED, DIAGNOSTIC DUMP REQUESTED, PROCESSING CONTINUESDuring the processing of a gateway/server logoff action, it was detected that a pointer in the gateway/server's control block was pointing to an invalid association.As a result of the error, a diagnostics dump will be requested, the invalid pointer will be cleared and processing will continue. The diagnostics dump generated should be forwarded to TIBCO Support.USER CONNECTION CANCELLED DUE TO ENDSERVER PROCESSING - USER=_____An external resource utilized by the in-flight transaction has terminated. In order to avoid potential integrity issues the associated user session was cancelled.The user can reconnect at their convenience.NO COMMUNICATION FACILITIES AVAILABLENeither Cross Memory Services nor Network Communications are available to the Object Service Broker Data Object Broker. Object Service Broker terminates abnormally.Look for any associated messages which provide further explanation. If this is an initial installation, ensure that the communication definitions required by Object Service Broker are in SYS1.VTAMLST and are activated. Verify that the correct VTAM application identifier initialization value was specified. If you are unable to resolve the situation, contact TIBCO Support.________________ ACCESS VIA ________ TERMINATEDAccess to the specified Object Service Broker node along the specified path was lost because the connection was terminated.If the termination was not expected, review the associated messages to determine if an error condition was reported.________ SERVER HAS BEEN STOPPED VIA OPERATOR REQUESTThe specified gateway has been terminated as a result of an operator stopserver or shutdown request.connectid CONNECTED #=num TYPE=type COMM=comm-type SOURCE=xxxxThis notification message will identify the connection for a user or batch job to the Data Object Broker.
• connectid may or may not be unique depending on site configuration
• num is the relative connection block used to support this connection. It will always be unique.
• type identifies the type of session being connected, e.g., CICSUSER
• comm-type identifies the type of communication supported for the connection (VTAM, XMS or TCP/IP)
• If the connection is for a terminal-based user, the SOURCE value identifies the terminal through which the user is connected
• If the connection is for a Batch Job, the SOURCE value displays the job name and step name for the connection.connectid LOGGED OFF #=num TYPE=type COMM=comm-type SOURCE=xxxThis notification message identifies the logoff for a user or batch job from the Data Object Broker.
• connectid may or may not be unique depending on site configuration
• num is the relative connection block used to support this connection. It is always unique.
• type identifies the type of session logging off, e.g., CICSUSER
• comm-type identifies the type of communication supported for the connection (VTAM, XMS or TCP/IP)
• If the logoff is for a terminal-based user, the SOURCE value identifies the terminal through which the user is connected
• If the logoff is for a Batch Job, the SOURCE value displays the job name and step name for the connection.________ SERVER AVAILABLE, TYPE=___, SERVER ID=_A gateway/server connection has been accepted by the Data Object Broker for a gateway/server with the specified unique identifier. This gateway/server has the specified type and serverid, which are used to group it with like gateways/servers.SERVER TERMINATED, SERVER ID = ________, ID = ___________A gateway/server that was connected to Object Service Broker with the specified type and serverid and unique identifier as specified by "ID=" has terminated its connection.A communications exit received a request that it does not support.Try to identify the circumstances that trigger this message. An isolated occurrence may be insignificant. Contact TIBCO Support if there are multiple occurrences or related problems.Object Service Broker synchronization error. A new transaction arrived before the current transaction completed. The user who experienced the error, their current transaction ID, and the phase (COMMIT or QUERY) are included in the message to help identify the cause.Contact TIBCO Support. If the problem can be recreated make sure you turn snap on so a snap dump can be generated when the problem occurs.The table processing required to satisfy the request could not be processed because a sessarea buffer could not be obtained.Ensure that the Object Service Broker startup configuration specifies a concurrency level that is appropriate for your workload. The concurrency level is set by the MAXTHREADS Data Object Broker parameter.Object Service Broker protocol error. An unassigned DBMS gateway made an unsolicited request for service. The request is ignored.A request was made for access to a gateway with a specific type and serverid. A matching gateway provider has not connected to the Object Service Broker Data Object Broker since it was started.Contact the person responsible for the Data Object Broker or the access you require and request the gateway be made available.A request was made for a service provider with a specific type and serverid. Service providers with match characteristics have registered with the Data Object Broker but they are either all in use or the connection is no longer active.Either wait for a service provider to be freed up (try again) or contact the person responsible for the Data Object Broker and have more service providers made available.USER CURRENTLY ACCESSING MAXIMUM NUMBER OF SERVERSDuring the execution of a transaction there is a limit of six service providers. The request for an additional gateway provider has been rejected because it would exceed this limit.REQUEST REJECTED, MESSAGE FLOW RESTRICTEDA request has arrived at the Object Service Broker Data Object Broker which is currently not able to process any new requests. The restriction could be temporary or the Data Object Broker could be in the process of shutting down. Preceding S6BDB095A messages may also have been issued indicating another cause of the problem.Retry your request at a later time. If S6bDB095A messages were issued, take the appropriate actions as documented for S6BDB095A.WORK BUFFER NOT AVAILABLE TO SUPPORT PROCESSING, REQUEST REJECTEDA work buffer was not available to retain vital information when the request processing was being initialized. The information could not be retained so the request was rejected.Ensure the system is configured with the MAXUSERS parameter at a level appropriate for the current workload. During the retrieval of the buffer an attempt is first made to obtain a work buffer; if that fails, a page buffer is retrieved. The S6BKC029E message is only generated if no buffers are available from either of these pools. If both pools are exhausted, there is a good chance that other problems have occurred or are occurring. Check the joblog to try to determine the cause of these failures.The Communications subtask received a request that it does not support. The request is ignored. Normal processing continues.Try to identify the circumstances which trigger this message. An isolated occurrence may be insignificant. Contact TIBCO Support if there are multiple occurrences or related problems.D.O.B. ACTIVE, NO COMMUNICATION AVAILABLEAn unrecoverable condition in the communication environment has resulted in the termination of all communication to the Object Service Broker Data Object Broker.Refer to the joblog to determine what the error condition is. When the condition is corrected, restart the Data Object Broker communication using the COMRESTART command via the console.This message is displayed in response to the receipt of a command from an administrator. The message displays the first 20 characters of the command text, and the ID of the operator who issued the command.USER LIMIT EXCEEDED, CONNECTION REJECTED - ________When attempting to connect a user session the configured limit was exceeded.Review the MAXUSERS parameter to determine if it is set appropriately for the required workload.CONNECTION MANAGEMENT POOL EXHAUSTED, CONNECTION REJECTEDEach connection made to the Data Object Broker requires a block of private memory to retain information about the connection and statistics. The pool from which this memory is acquired (the COMMPOOL) has exhausted its supply of buffers. The number of buffers available is based on the MAXUSERS parameter and the path management data available at startup. If the schedule for paths have been increased or new paths have been added it may account for the pools shortfall.The only way to reset the size of the pool is to recycle the Data Object Broker. If there has been a lot of changes to the path management limits, the Data Object Broker should be recycled when it is convenient.INITIATING PEER CONNECTION TO luname:node nameNotification that the connection to the identified peer node is being attempted.connectid REJECTED TYPE=type REASON=ee/rrWhen a connection to the Data Object Broker is rejected, this message appears to identify the reason why.
• connectid is the name used to connect to the Data Object Broker. It may or may not be unique depending on site settingsFor Error Code 08 - Logic error, the following reason codes apply:
• 00 - compatibility code not passed in connection data
• 04 - compatibility error - check for wrong load library
• 08 - connection data incomplete, region type missing
• 12 - connection data incomplete, connection ID block missing
• 16 - connection data invalid, connection type not supported
• 24 - connection data incomplete, specification block too small
• 28 - rules-based gateway rejected, partner connection not specified
• 40 - invalid connection ID specified (note: S6BBRULH not acceptable)
• 44 - gateway connection data incomplete, group ID not specified
• 48 - gateway connection data invalid, characteristic error
• 52 - rule-based gateway rejected, connection partner not found
• 56 - rule-based gateway rejected, connection partner associated alreadyFor Error code 12 - Environmental errors, the following reason codes apply:
• 00 - Data Object Broker is not accepting connection request
• 04 - storage not available for the required connection block
• 08 - connection currently restricted to operators
• 12 - batch jobs are not permitted to connect at this time
• 24 - Inbound Peer connection not defined in Resource Manager
• 28 - system quiesced, connection requests are not being accepted
• 32 - gateway type/group combination not defined to the resource management system
• 36 - gateway connection already at maximum as per resource manager
• 40 - In a multi Data Object Broker system connections to the Data Object Broker are only accepted from Message Switches
• 52 - connection information is not in acceptable format
• 60 - wild card gateway definition exceeds resource limits
• 68 - Data Object Broker is not licensed for CICS accessContact TIBCO Support if you need further clarification.TRANSACTION NUMBER EXTRACTION ERROR ON PATH SELECTIONAn internal error or message structure problem has been detected during external gateway/server path selection. The selection process fails and the user is returned an error.SERVER LOST BEFORE COMMIT PROCESSING INVOKEDDuring the edit processing before a commit is initiated, an external gateway/server required for the commit is no longer available. The commit is rejected before any updates are processed.Retry the transaction. If available, another gateway/server will be used automatically.ERROR DETECTED DURING PREPARE TO COMMIT PHASEInternal indicators show pending updates for a DBMS gateway. However, the gateway association does not exist.Invoke the transaction again. If the error recurs, contact TIBCO Support.A discrepancy has been detected in the user/DBMS gateway cross-reference.Invoke the transaction again. If the error recurs, contact TIBCO Support.NO CONTINGENCY LOG RECORDS AVAILABLEThis request had exceeded the configured limit for concurrent indoubt transactions. All tracks within the REDO.PENDING file are in use. This request is aborted.REMOTE COMMIT REQUIRING FAIL SAFE PROCESSING HAS FAILEDThe response to a Prepare-To-Commit or Commit request sent to an external resource has indicated an inability to satisfy the request.System Action: The commit group failed, none of the commit processing for the sync point is processed. User Action: Review the logs of the external resource to determine what cause the prepare to commit failure.SERVER COMMIT FAILURE DETECTED, TRANSACTION REJECTEDA DBMS gateway has responded with a nonzero return code for the first gateway updated within the COMMIT group. The COMMIT group is aborted.SERVER LOST, PENDING TABLE UPDATES HELD IN-DOUBTA DBMS gateway session was lost after the point it was issued a commit and before it could acknowledge the COMMIT complete. The pending TDS table updates are held in-doubt until the system can determine if the DBMS updates were completed or the transaction is manually resolved.Restart the gateway or manually resolve the error by using the administrator utility.While a service provider was processing a request, its connection to the Object Service Broker Data Object Broker was terminated.View the system log to determine why the service provider was terminated, or retry your request at a later time.SERVER FAILURE, COMMIT CURRENTLY IN PROGRESS ABORTEDThe COMMIT group has been aborted because the session for a DBMS gateway with updates responded with an error return code during it commit processing.Refer to the gateway's job log to determine the reason for the failure.CONTINGENCY LOG WRITE FAILURE DETECTEDWhen attempting to record the TDS intent list on the contingency log (REDO.PENDING), physical write errors were reported. The Data Object Broker will be terminated if continuing after this error could result in a data integrity issue.
• If this error does not result in termination of the Data Object Broker, then shut the Data Object Broker down at the earliest convenient time and address the problem with the contingency log.
• If this error terminates the Data Object Broker, address the problem with the contingency log, restart the Data Object Broker and use the administration utility to resolve any IN*DOUBT transactions.
• If necessary contact TIBCO support for guidance.At Data Object Broker initialization time the contingency log contained data records. This means that manual intervention may be required to clean up any in*doubt transactions.Once the Data Object Broker has completed initialization use the Administrator utility to review the contingency log and perform any required actions.SERVER ERROR, TDS UPDATES ABORTED, SERVER DATA INCONSISTENTDuring the COMMIT cycle, a DBMS gateway (not running under Fail Safe constraints) reported a COMMIT error. The default action of the system is to abort the COMMIT, snap the pending TDS updates and roll back any other DBMS gateways. Data between the DBMS gateways and Object Service Broker may now be out of sync because of a partially completed COMMIT group.Try to resolve any data inconsistencies and then retry the application.An outstanding in-doubt transaction has been resolved either automatically or due to manual intervention. The pending TDS table updates have been submitted for processing.IN-DOUBT RESOLVED, TDS REQUEST ABORTEDAn outstanding in-doubt transaction has been resolved either automatically or due to manual intervention. The pending TDS table updates have been rejected.NO STORAGE AVAILABLE FOR MESSAGE INBOUND POOLA message was received that must be copied into a work buffer to support large inbound messages. When an attempt was made to acquire a buffer from the pool there were no buffers available. This could indicate an internal buffer release issue or a pool size that is inadequate to meet your needs.Take a COMM dump and create an incident with TIBCO Support. To alleviate the problem for now, recycle the Data Object Broker with a larger MAXTHREAD parameter value to cause the number of MSGI pool buffers to be increased.NO STORAGE AVAILABLE FOR CONTINGENCY LOG POOLDuring Object Service Broker initialization, sufficient storage (above the line) was not available for use by the contingency log. The Object Service Broker address space may require a larger region size, or authorization to exceed site-imposed limits (IEFUSI).An error was detected when attempting to process the contingency log (REDO.PENDING).See the job log for accompanying messages with more detail.GROUP SYNCHRONIZATION FAILED-UPDATED SERVER LOSTWhen preparing to commit changes, the Object Service Broker Data Object Broker detected that a service provider which had updates against it was no longer available. The pending transaction will be aborted.GROUP SYNCHRONIZATION FAILED-SERVER MANAGEMENT ERRORWhen preparing to commit changes, the Object Service Broker Data Object Broker detected that its internal pointers were not set as expected. The pending transaction will be aborted.Retry the transaction. If the problem recurs contact TIBCO Support.GROUP SYNCHRONIZATION FAILED-MIXED COMMIT PROTOCOLSWhen preparing to commit changes, the Object Service Broker Data Object Broker detected that multiple service providers were updated that supported different levels of Fail Safe processing. The pending transaction will be aborted.Redesign the application to conform to Fail Safe requirements. See the discussions of Fail Safe processing in the Backup and Recovery manual and the appropriate Gateway manual.GROUP SYNCHRONIZATION FAILED-COMMIT CONSTRAINT VIOLATIONWhen preparing to commit changes, the Object Service Broker Data Object Broker detected that multiple service providers that require Fail Safe support were updated. This violates the constraints of Fail Safe level-1 processing. The pending transaction is aborted.Redesign the application to conform to Fail Safe requirements. See the discussions of Fail Safe processing in the Backup and Recovery manual and the appropriate Gateway manual.GROUP SYNCHRONIZATION FAILED-OUTSTANDING INDOUBT TRXWhen preparing to commit changes, the Object Service Broker Data Object Broker detected that a Fail Safe level-1 commit was required against a DBMS service provider which already had an in-doubt transaction against it. The pending transaction is aborted.Retry the transaction and/or resolve the in-doubt transaction. See the discussions of Fail Safe processing in the Backup and Recovery manual and the appropriate Gateway manual.GROUP SYNCHRONIZATION FAILED-PREPARE TO COMMIT FAILUREA prepare to commit request was made to a peer Object Service Broker during the processing of a transaction which utilized Object Service Broker distributed data. The PEERS parameter on the remote Object Service Broker indicated Fail Safe support; however, when "prepare to commit" request was received the remote Object Service Broker was unable to support the request. The pending transaction will be aborted.Correct the PEERS parameter on the local Object Service Broker. See the discussions of Fail Safe processing in the Backup and Recovery manual and the appropriate Gateway manual.GROUP SYNCHRONIZATION FAILED DURING COMMIT CYCLE, HELD IN-DOUBTA Fail Safe level-2 commit has failed. The contingency log is retained until all peer Object Service Broker systems have acknowledged a release of their contingency logs.Review the system log for accompanying messages to determine why the Fail Safe level-2 commit aborted.INCOMPLETE PREPARE TO COMMIT ABORTED DURING RESTARTDuring the restart of an Object Service Broker Data Object Broker, a contingency log in the "prepare to commit" phase of a Fail Safe level-2 commit was recovered. In the "prepare to commit" phase, no updates were committed, the transaction is aborted, and all service providers will be requested to release their contingency logs if they are present.INDOUBT TDS UPDATES COULD NOT BE RETAINEDWhen a transaction is determined to be in-doubt the TDS intents are transferred from the user controlled space to an Object Service Broker control buffer. A buffer could not be acquired.The transaction is aborted and held in-doubt; the TDS is already safe, stored in the REDOLOG.PENDING data set.UNABLE TO ESTABLISH INDOUBT LOCKS DURING RESTARTDuring the startup processing of a Data Object Broker, logical locks for in-doubt transactions are reacquired. During the attempt to acquire the logical lock, an error was detected.Check the joblog for an error from the lock manager, which may help identify the nature of the problem. Contact TIBCO Support for additional assistance.GROUP SYNCHRONIZATION INCOMPLETE-PEER UPDATES DEFERREDDuring a disrupted two phase commit, communications to one of the peer regions was lost. The commit cycle is held until the status of the peer commit is determined.Restart the communications link to the peer region as soon as possible.GROUP SYNCHRONIZATION ORIGINATOR STATUS INDOUBTThe contingent resource of a contingent two phase commit has suffered a communication interruption. The originating Data Object Broker put the transaction into in-doubt status. The message will be produced by the peer when it is informed of the in-doubt condition.Reactivate the lost communication link as soon as possible.2 PHASE GROUP SYNC ABORTED; ORIGINATOR LOST, PENDING FAIL SAFE 1 RESOURCE UPDATESThe remote commit coordinator of a transaction doing a contingent two phase commit has aborted a transaction. It was determined that the connection with the originator was lost before any of the commit group was filed. The transaction has ended abnormally with no updating taking place.GROUP SYNCHRONIZATION TERMINATED BY ORIGINATORThe remote commit coordinator has been instructed by the originator to cancel the two phase commit processing for a transaction and release the remote resources. There was a problem in the commit group coordinated by the originator which could not be overcome, therefore the transaction was aborted.RESOURCE ___-________ IDENTIFIED IN CLOG, NOT IN PATH CONTROLWhen Object Service Broker restarted, it found an indoubt transaction with an external resource that is no longer named in the configuration repositories.Ensure the repository is still intact and determine why the identified path is no longer defined. Either correct the configuration and retry or use the S6BTLADM utility to delete the indoubt transaction.LOGON REJECTED - CICS DISPLAY LIMIT EXCEEDED useridThe connection request for the identified user was rejected because the number of CICS display-type connections is already at the value specified by the MAXDISPLAY parameter.Retry your transaction or wait for a CICS display-type connection to terminate.ATTEMPTED TO CHANGE REMOTE RULE PROCESSOR WITHIN A TRANSACTIONWhen processing remote tables a remote rule server is used. Normally the rule server will default; this can be overridden using the session table. If you do wish to override the rule server selection process it must be done prior to the first remote access on that node within the current transaction. The current transaction has been abended because the rule server had already been selected prior to the failing attempt.Override the Remote Rule Server earlier in your transaction.-________CONNECTION REJECTED, REGISTRATION DIFFERENT THAN RESOURCE MANAGERAn external resource (DBMS gateway, Remote Rule Server or Peer Object Service Broker) connection was rejected with a return code of x'08' and a reason code of x'30'. This means the flags identifying the characteristics of the resource do not match the requirements specified in the Resource Management system. A KC081 message follows this message and identifies the resource characteristics that failed at connection time.SUPPLIED: INT.RLBK _, EARLY RELEASE _, LAST USER _ AND FAIL SAFEAn external resource (DBMS gateway, Remote Rule Server or Peer Object Service Broker) connection was rejected with a return code of x'08' and a reason code of x'30'. This means the flags identifying the characteristics of the resource do not match the requirements specified in the Resource Management system. This message identifies the resource characteristics that failed at connection time.Compare the indicators in the KC081 message for the path identified by the preceding KC080 message against those defined in the Resource Management function via the Administrator utility.CONFIGURATION ERROR, PEER HAS LOCAL VTAMIDIn the definition of a peer Object Service Broker connection, the serverid specified is the applid of the target Object Service Broker. During start-up processing for a peer connection, it was detected that the target applid matched the VTAMID of the local Data Object Broker. The connection is not logically or physically valid.The administrator should go into the path management facility via S6BTLADM and remove the invalid path control entry.When a Data Object Broker was attempting to make a connection to a remote Data Object Broker, the connection was rejected because there is already a session on the remote Data Object Broker with the same userid.In the Administrator Resource Management Facility, edit the outbound Peer detail entry (HRN) and ensure a unique PREFIX is specified for the generated userid.DATA EXCHANGE ELEMENT NOT AVAILABLE FOR RESPONSEA buffer to build an operator response could not be obtained from the system.DATA EXCHANGE ELEMENT LENGTH OUT OF RANGE; TRANSACTION REJECTEDA message length greater than the acceptable limit has been detected by the query processor.The system will abend the transaction. If a snap dump was produced (optional, based on start-up parameters) contact TIBCO Support and forward the snap dump in an incident report.SERVER COMMAND TO _______ TYPE=___, GROUP=________ REJECTED, COMMAND ALREADY ACTIVEA gateway/server command operator modify command was received which includes processing a gateway/server which already has a gateway/server command outstanding.The request is ignored for the gateway/server path.BUFFER NOT AVAILABLE TO CHAIN DEFERRED SERVER COMMANDSWhen attempting to obtain a buffer to support a gateway/server command request, the required buffer space was not available.The requested gateway/server command processing is terminated.SRVR CMD: ISS=____, DEFER=____, RSC=___ ________, CMD=__________This informational message is produced at the completion of the gateway command resource identification process. It identifies how many requests were issued immediately, how many had to be deferred because the path was in use, the name of the resource and the requested command text.SRVR CMD: OK=_____, FAILED=_____, RSC=___ ________, CMD=________This informational message present the gateway/server command processing results when the last candidate path has responded.SRVR CMD REJECTED, NO PATHS MATCH ___ ________When attempting to select appropriate paths to send the requested gateway/server command it was found that no active paths existed.NO SESSAREA AVAILABLE, TASK DELAYEDA new query or commit request is to be processed by the Data Object Broker. At this time no SESSAREA is available for this request. The request is delayed until a SESSAREA becomes available. This message may occur while the Data Object Broker is frozen.If this message occurs regularly during normal processing, increase the value of the MAXTHREADS Data Object Broker parameter until this message no longer appears.SPIN IN PROGRESS SHUTDOWN REQUEST REJECTEDA SHUTDOWN request was received while a journal spin is active.Example MODIFY jobname,JOURNALSTATUSAn Object Service Broker shutdown request was issued by the operator utility, but the Object Service Broker parameters are set to disallow the shutdown.Issue the shutdown request from the operator console.JOURNAL SPIN FLAG ALREADY IN REQUESTED STATEA job executed the S6BSPJEX program to change the Journal spin status. The SPIN flag is already set to whatever was requested. No action is taken.No action is required, but it is recommended that access to the S6BSPJEX program be restricted.JOURNAL SPIN FLAG RESET ONLY - NO OFFLINE JOURNALA job executed the S6BSPJEX program to enable Journal spins. However, no Journal was offline, and therefore no Journal was reopened.No action is required. You may want to display the Journal status. It is recommended that access to the S6BSPJEX program be restricted.SRBMODE=Z SPECIFIED BUT NO ZIIP AVAILABLEThe SRBMODE parameter has been set to Z, but no zIIP processor is available to offload work to.None. The Data Object Broker reverts to SRBMODE=Y for this instance.When attempting to dynamically allocate the repository data set for the Resource Manager, an error was detected.The communication subtask will fail during initialization.ERROR DETECTED IN GENCB FOR "GENCB" FOR REPOSITORYWhen attempting to build a control block to support Resource Management processing, an error was detected.The communication sub-task will fail initialization.During the initialization of the Data Object Broker, an error was detected with the repository open or read.RESOURCE ENTRY NOT SPECIFIED IN DBDLIB, REBUILD DBDLIBThe remote Data Object Broker and gateway/server definitions are saved in a KSDS 128 data set. The required data set could not be located.TRANSACTION MANAGEMENT DIRECTIVE INVALIDAn Object Service Broker user transaction issued a transaction management directive to cause the Data Object Broker to do user accounting or user update. The request has been rejected because of an invalid function code or other format error.The transaction management request should be investigated and corrected.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |