![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
ERROR=0000 ABCDEFGH.ABCDEFGH+12345 VERSION=00/00/00 00.00 V0.00.000This message is issued by the HDRSBLMC module. This message is issued at the time of an abend if the ESTAE flag is set and if the abend was intentionally generated by the $ABEND macro.
• ERROR displays the abend reason code referencing the internal error messages table in the HDRSBLMC module.
• ABCDEFGH.ABCDEFGH+00000 points to the abend instruction offset from the active module CSECT beginning.
• VERSION displays the abend CSECT date, time and version identification in that order.ERROR=E000 ABCDEFGH.ABCDEFGH+12345 VERSION=00/00/00 00.00 V0.00.000This message is issued by the HDRSBLMC module at the time of an abend if the ESTAE flag is set and if the abend was unintentional.
• ABCDEFGH.ABCDEFGH+00000 points to the abend instruction offset from the active module csect beginning.
• VERSION displays the abend csect date, time and version identification in that order.TIBCO Object Service Broker REQUIRES MVS/XA FOR THIS VERSIONYou must upgrade your system to MVS/XA to use this version of Object Service Broker.This warning message is issued when the Native Execution Environment initialization module detects that it is not invoked as APF authorized. Without APF authorization, Object Service Broker cannot use privileged Operating System facilities such as Cross Memory Services.
• The Object Service Broker loadlib is not APF authorized
• One of the loadlibs concatenated to the Object Service Broker loadlib for the //JOBLIB or //STEPLIB DD is not APF authorized
• Module S6BDR000 is not linked with a "SETCODE AC(1)" statement
1. Identify and correct the cause of the problem and retry
2. Install the Object Service Broker Execution Environment SVC routine to enable APF authorizationThis message is issued by the S6BDR000 module. The Execution Environment initialization/termination routine was unable to either attach or detach the TIBCO(r) Object Service Broker gateway task; the initialization or termination process was terminated. This message is usually accompanied by other more specific error messages.Investigate and correct the problem, or contact TIBCO Support for assistance.This message is issued by the S6BDR000 module. The Execution Environment initialization routine is unable to initialize the interface. This message is usually accompanied by other more specific error messages.Investigate and correct the problem, or contact TIBCO Support for assistance.The specified name given is not a valid gateway, or no gateway was specified.Execution Environment subtask abended, R15=X'xxxxxxxx'This message is issued by the HDRSBSVA module. An attempt to attach the subtask failed. This message is usually preceded by other error messages providing more information for the failure. In the message, xxxxxxxx is the abend code.Determine the cause of the error or contact TIBCO Support for assistance.The specified error occurred while processing the osee shared memory area.If messages that precede this message do not provide sufficient information to diagnose the cause of this failure, contact TIBCO Support.EE MAIN TASK TCB ABENDED PROCESSING ................................_CPE FNC. UID= .........The Execution Environment main task abended. If the abend occurred during the processing of a CPE function, the name of the function appears in the message. If available, the userid is also in the message.The Execution Environment has attached the subtask named in the message.The Execution Environment has dropped the subtask named in the message. The action was due to an abend or initiated for refreshing purposes.NEE COULD NOT RESTART THE RULE-BASED SERVER.The Execution Environment unsuccessfully tried to restart the abended rule-based gateway/server.EE main task TCB has been terminated prematurely due to the unrecoverable errorThe Execution Environment main task suffered an abend and is unable to recover due to one of the following reasons: 1) an abend occurred before the recovery routine was set up. 2) an abend occurred in the retry routine. 3) the number of abends exceeded the limit set.The recovery routine would percolate the abend and the Execution Environment terminated.EE subtask xxxxxxxx is recovering after the user abend Uyyyy at zzzzzzzzTo explain the following actions, such as a subtask recycle, an external gateway recycle, etc., xxxxxxxx names the subtask that has experienced the user abend yyyy while running module called zzzzzzzz.Take no action unless the situation caused other problems, in which case contact TIBCO Support.The specified error occurred while parsing the startup parameters.Correct the syntax of the startup parameters.The specified operation failed for the specified printer.Make sure the printer is correctly installed on your network and retry your printing operation. If it continues to fail, contact your system administrator.The specified operation failed on a Microsoft Device context.Check the operating system error number provided with the message. It should indicate the reason for the failure.An attempt to access the specified font for printing failed.Check the operating system error number provided with the message. It should indicate the reason for the failure.EXECUTION ENVIRONMENT IS NOT ATTACHEDThis message is issued by the S6BCSOPS module. The Execution Environment is not attached.EXECUTION ENVIRONMENT IS ATTACHED - ........This message is issued by the S6BCSOPS module. The Execution Environment is attached and ready to accept logons.EXECUTION ENVIRONMENT IS ALREADY ATTACHEDThis message is issued by S6BCSRUN module. A HINT (interface initialization) transaction was issued to activate the TIBCO(r) Object Service Broker CICS interface, but the Execution Environment task has already been attached and the interface is ready to accept logons.An attempt to initialize the National Language Support tables failed.Make sure the value specified for the CHARSET parameter to the osee is supported on your system.The first rule for a given user session failed.Previous error messages written to the log should explain the reason for the failure.The attempt to spawn a new process using the specified binary failed.Check the operating system error number provided with the message. It should indicate the reason for the failure.Check the operating system error number provided with the message. It should indicate the reason for the failure. If it does not, contact TIBCO Support.Conversion of the specified string value to a value that could be stored in the specified parameter failed.If the value originates from user input, check the type of the parameter and correct the value. Otherwise, contact TIBCO Support.At osee startup, an attempt is made to determine the name of the computer on which the process is executing.Check the operating system error number provided with the message. It should indicate the reason for the failure.TDS=........ MDL=........ OPENPORT FAILED, SERVER TASK IS NOW DORMANTAn attempt by the Execution Environment to establish communications with the Data Object Broker has failed. The value for TDS identifies the Data Object Broker and the value for MDL is the VTAM APPLID supplied by the user.
1.
2. Ensure that the TDS parameter specifies the correct ID for the Data Object Broker.
3. If unable to determine the problem, contact TIBCO Support.ENCRYPTION EXIT LOAD FAILED DUE TO MISSING SVCThe Object Service Broker SVC is mandatory for the use of the security encryption exit.Refer to earlier messages as to why the SVC is not present. Correct the reason, and restart your Execution Environment for the exit to be enabled.ENCRYPTION EXIT LOAD FAILED DUE TO UNAUTHORIZED USER EXITThe customer-installable encryption exit is not authorized, or has been loaded from an unauthorized library.The customer exit must be link edited with an authorized code of 1 (AC(1)). It must also reside in an APF authorized library, and all libraries that may be concatenated with this library must also be APF authorized.ENCRYPTION EXIT LOAD FAILED DUE TO MISSING LOAD MODULEThe customer encryption exit (HDRSCXIT) could not be found in the STEPLIB or HRNLIB data sets.Ensure that you link the HDRSCXIT load module into the proper library.Buffer overflow occurred while writing to a fixed length bufferAn attempt to create a temporary file name failed.Check the operating system error number provided with the message. It should indicate the reason for the failure. If it does not, contact TIBCO Support.Error of type '%' occurred while performing a data conversionAn attempt to convert data from one semantic/syntax type to another failed for the specified reason. The reason is one of the following:
• DATAERR - The input data does not conform to the restrictions placed on it by the input semantic/syntax.
• OVERFLOW - The data is too large for the supported syntax.
• CONVERR - An unsupported conversion was attempted.
• PARMERR - One or more of the parameters to a conversion routine was invalid.
• TRUNCATION - The data was truncated as a result of the conversion to the target syntax.
• SYSTEMERR - A system error occurred during the conversion.Examine the online logs to locate the source of the error. If the reason specified is SYSTEMERR, contact TIBCO Support. If the data originates from user input, provide the user with the appropriate diagnostic messages and re-prompt for input. Otherwise, correct either the data source or the application.An unexpected internal exception occurred.If messages that precede this message do not provide sufficient information to diagnose the cause of this failure, contact TIBCO Support.Conversion of the specified integral value to a value that could be stored in the specified parameter failed.If the value originates from user input, check the type of the parameter and correct the value. Otherwise, contact TIBCO Support.An osee process abended due to an internal exception that occurred at the specified line in the specified source file of the product.If messages that precede this message do not provide sufficient information to diagnose the cause of this failure, contact TIBCO Support.If messages that precede this message do not provide sufficient information to diagnose the cause of this failure, contact TIBCO Support.If messages that precede this message do not provide sufficient information to diagnose the cause of this failure, contact TIBCO Support.If messages that precede this message do not provide sufficient information to diagnose the cause of this failure, contact TIBCO Support.If messages that precede this message do not provide sufficient information to diagnose the cause of this failure, contact TIBCO Support.The osee failed to initialize a transaction stack.If messages that precede this message do not provide sufficient information to diagnose the cause of this failure, contact TIBCO Support.During session startup, a transaction is created for access to startup information that is stored in the MetaStor. The attempt to activate this transaction failed.If messages that precede this message do not provide sufficient information to diagnose the cause of this failure, contact TIBCO Support.Failed to activate session termination transactionDuring session termination, a transaction is created for the logoff rule. The attempt to activate this transaction failed.If messages that precede this message do not provide sufficient information to diagnose the cause of this failure, contact TIBCO Support.A transaction is created for the first rule that is run by the session. The attempt to activate this transaction failed.If messages that precede this message do not provide sufficient information to diagnose the cause of this failure, contact TIBCO Support.An attempt to change the user's security group failed.Previous log messages should provide more information as to the reason for the failure. Make sure the user belongs to the specified security group.The Object Service Broker ESTAE recovery routine detected a problem that occurred while in cross-memory mode. The ASID indicated was the one where the error occurred. This message provides additional information to other error messages for the situation.Connection to Data Object Broker has been lost; EE interface re-initialization requiredThis message is issued by the HDRSBEXR module. It was found that the Data Object Broker connected to this Object Service Broker Execution Environment has been shutdown and restarted, and therefore, the Execution Environment is out of synchronization with the restarted Data Object Broker.The Object Service Broker Execution Environment will have to be re-initialized to re-establish the link.EE SVC nnn(xx) validated, Version: ................ Level: .. ......The Object Service Broker SVC routine has been verified to be correct and compatible with the rest of the Object Service Broker EE system modules. The version and compatibility level are displayed.CROSS-MEMORY COMMUNICATION ENABLED, ID=........This message is issued by the S6BDRTMR module. Communication has been established with the Object Service Broker Data Object Broker utilizing Cross Memory Services with the MDL described by the message.An osee process is unable to connect to the specified Data Object Broker.The preceding log messages should explain the reason for the failure. Make sure the Data Object Broker in question is running.COMMAREA TOO SMALL FOR OCCURRENCEThis message is issued by the BLTPASSD module. Object Service Broker has attempted to place a requested occurrence in the user created COMMAREA. The space remaining in this COMMAREA was too small to contain the occurrence.
• Increase the size of the COMMAREA passed to Object Service Broker.
• Reduce the size of the occurrence to be written to the COMMAREA.
• If the user is writing multiple occurrences to the COMMAREA, reduce the number.This message is issued by the BLTPASSD module. Object Service Broker cannot find the occurrence that was chosen to be written to the user supplied COMMAREA.Ensure that the occurrence exists, or that the occurrence is placed in the table buffer before $SETCOMMAREA is called.This message is issued by the BLTPASSD module. The table specified in $SETCOMMAREA cannot be found.This message is issued by the HDRSBSVA module. It is preceded by either S6BDR060E or S6BDR062E. It provides the Major and Minor compatibility-level numbers for the SVC routine and the HDRSBSVA module.Correct the incompatibility situation or contact TIBCO Support for assistance.Shared ENQ on specified SVC no. nnn(xx) failed verification: xxxxxxxxxxxxxxxxxxxxThis message is issued by the HDRSBSVA module when a shared ENQ was unsuccessful on the Object Service Broker SVC. In the message:
• xxxxxxxxxxxxxxxxxxxxxxxxxxxx is the reason for the failureCorrect the error and retry or contact TIBCO Support for assistance.Load failed for "xxxxxxxx" ABCODE=X'xxxxxxxx' Reason Code=X'xxxxxxxx'This message is issued by the HDRSBSVA module. Loading of the installation default module failed. The module name, abend code, and reason code are documented in the appropriate IBM manual, under the LOAD macro. The Object Service Broker Execution Environment will therefore be running in a non-authorized degraded mode. Full Object Service Broker Execution Environment functionality may not be provided.This message is followed by message S6BDR063W."mmmmmmmm" specified SVC number nnn(xx) failed verification: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxThis message is issued by the HDRSBSVA module. In the message:
• mmmmmmmm is the name of the installation defaults module
• xxxxxxxxxxxxxxxxxxxxxxxxxxxx is the reason for the failureThis message is followed by message S6BDR063W.This message is issued by the HDRSBSVA module and may be preceded by message S6BDR061E or S6BDR062E. The Execution Environment will run unauthorized for the reason stated in the preceding message. If no reason is stated, the Object Service Broker SVC was located properly but the library from which TIBCO(r) Object Service Broker was loaded was unauthorized.To ensure that TIBCO(r) Object Service Broker always initializes in an authorized state, use one of the three methods described in the Installation and Operations manual.INITIALIZATION COMPLETE FOR SERVER CLASS ........ (ATTACHED TASK=...)This message is issued by the S6BDRTMR module. Initialization of the specified gateway/server class has been successful.TERMINATION COMPLETE FOR SERVER CLASS ........This message is issued by the S6BDRTMR module. Termination of the specified gateway/server class has been successful.COMMUNICATION CONNECTION LOST, ID=........This message is issued by the S6BDRTMR module. Execution Environment communication with the Data Object Broker has been lost.Check that the Data Object Broker is still active, and that VTAM is still functioning.This message is issued by the S6BDRTMR module. The user's Execution Environment connection to the Data Object Broker has been lost.Check that the Data Object Broker is still active, and whether the user session was canceled.ERROR RECOVERY FAILED FOR TASK CLASS ........, USER ........This message is issued by the HDRSBEXR module. The attempt to recover from an error situation has failed for the Task class (and the user if the Task was processing a user). The Task was terminated with an Object Service Broker snap dump.CPE CONNECT PROCESSING FAILED FOR XXXXXXXX, RC=XX. CPE HEX DUMP FOLLOWSThis message indicates that an attempt to connect with the Execution Environment has failed for the named VTAM application identifier. The connection processing element is dumped in hexadecimal format to allow diagnosis of the problem.Retain the Execution Environment JES joblog and forward to Object Service Broker TIBCO Support for analysis.OPERATOR CONNECTION LOST, EXECUTION ENVIRONMENT SHUTDOWN SCHEDULEDThe operator connection with the Data Object Broker has been lost. The Execution Environment cannot continue without this connection. An automatic shutdown of the Execution Environment is scheduled.The likely cause of this message is the Data Object Broker to which the Execution Environment is connected has been shutdown either normally or abnormally. Review the Data Object Broker's JES joblog and determine the reason for its termination.This message is issued when the Execution Environment is unable to requite a connection request from either an end user terminal or a remote program.The session has been canceled. There can be any number of reasons to cancel a session: the Data Object Broker is being recycled, locks held by one session prevent other sessions from proceeding, the session is in an infinite loop, etc.This is an information message. The user should consult with the Object Service Broker System Administrator if session cancellation was not only unexpected but disruptive.This message contains a hexadecimal dump of the connection processing element that could not be successfully processed. Message S6BDR069E indicates the end user attempting connection and the reason for the failure.Keep the Execution Environment JES joblog for TIBCO Support.An attempt to initialize the osee startup parameters with values stored in the Data Object Broker failed.Previous log messages should provide more information as to the reason for the failure. Make sure the version of the Data Object Broker is compatible with the version of the osee.An attempt to initialize one or more of the session parameters failed.Previous log messages should provide more information as to the reason for the failure.An attempt to initialize the ActiveX Adapter server in an osee failed.Previous log messages should provide more information as to the reason for the failure.- NOT AUTHORIZED TO ISSUE SMF RECORDSThe address space is not sufficiently authorized to issue SMF records.This is an information message. The Execution Environment can execute from either an authorized or unauthorized load library. Without APF authorization, SMF records cannot be issued.This message is issued by the HDRSBOCP module. This message is an echo to the command entered to serve as an audit trail.EXECUTION ENVIRONMENT REQUIRES AUTHORIZATION FOR THIS COMMAND. COMMAND FAILED.This message is issued by the HDRSBOCP module. The command entered requires APF authorization for the Execution Environment.The command was not processed. Refer to the Installation and Operations manual for information on Authorized Library requirements.EXECUTION ENVIRONMENT SHUTDOWN ALREADY IN PROGRESSExecution Environment shutdown is in progress.USER ........ NOT CURRENTLY LOGGED ON TO THE EXECUTION ENVIRONMENT.This message is issued by the HDRSBOCP module. The user identified in the CANCELUSER command was not currently logged on to TIBCO(r) Object Service Broker via this Execution Environment, and the request could not be completed.Check the userid entered with the CANCELUSER command, correct, and reenter the command.CANCEL OF USER ........ HAS BEEN SCHEDULEDThis message is issued by the HDRSBOCP module. The user session identified was scheduled to be canceled in response to the CANCELUSER command entered.EXECUTION ENVIRONMENT SHUTDOWN HAS BEEN SCHEDULEDThis message is issued by the HDRSBOCP module. A shutdown request has been entered, and this is the acknowledgement that the shutdown sequence has been initiated.COMMAND SPECIFIED IS NOT A VALID EXECUTION ENVIRONMENT COMMAND.This message is issued by the HDRSBOCP module. The command entered was not recognized as a valid Execution Environment command. This message is preceded by the S6BDR078I message, which echoed the command entered.Check the preceding S6BDR078I message for the command entered and reenter with a valid Execution Environment command.AN INTERNAL ERROR OCCURRED PROCESSING THE COMMANDThis message is issued by the HDRSBOCP module. An Execution Environment internal error has been encountered during the processing of the command.This message was issued in response to an Execution Environment CANCELUSER request. This system determined that session termination was already in progress either by a prior CANCELUSER request or due to some other errors such as terminal lost.If the session in question was not terminated for some reason such as it was in a loop, the FORCEUSER command can be used to force the session. 2 WARNING: Use of the FORCEUSER command may cause system integrity problems as proper cleanup is not always possible. Use with discretion.FORCE session request was accepted.FORCE termination of the user session was in progress.Always use the CANCEL session command to take out a session gracefully. Use FORCE only as a last resort.The FORCE session command has not been honoured.Execution Environment not authorized, SHUTI may not be successfulSHUTI may need to FORCE a user session and if the Execution Environment is not running APF authorized, the FORCE will fail and the shutdown may fail.It is recommended that the Execution Environment be APF authorized.Cannot CANCELUSER/FORCEUSER with NOSTAE option specifiedThis message was issued in response to an Execution Environment CANCELUSER request. This request cannot be processed because NOSTAE was specified as an Execution Environment configuration option. TIBCO(r) Object Service Broker uses the z/OS ESTAE facilities to cancel a user session; if NOSTAE is in effect, TIBCO(r) Object Service Broker cannot perform the CANCELUSER function.Issuing the Data Object Broker command CANCELUSER may have left the user active to the Execution Environment. Configure your Execution Environment with the STAE option to allow the successful cleanup of the abnormally terminated user session.Server type not specified, enter "TYPE=" parameter in the commandThe gateway/server type is needed in order to perform the request for the intended type of gateway/server.Reenter the command with the TYPE= keyword parameter.STARTNUMSERVER value exceeded the maximum number set - use the SETN command to increaseSTARTNUMSERVER value exceeded either the initial number specified in the HRNIN parameter file or the number set by the SETNUMSERVER command.Use the SETNUMSERVER command to increase the maximum.SETNUMSERVER value exceeded maximum allowable with the current number of DISINTRP tasksThe SETNUMSERVER value is greater than the number of DSPINTRP tasks minus one. User sessions run under the DSPINTRP tasks, each rule-based gateway/server monopolizes one DSPINTRP task, and at least one gateway/server must be available to run the user session.Run a higher number of DSPINTRP tasks by specifying a higher value for the TASKEXECNUM= parameter in the HRNIN.An attempt to load the definition for the specified table failed.Make sure the specified table is defined in the MetaStor of the Data Object Broker to which your osee is connected.Attempt was made to start too many transactions in a session. The limit is %An attempt is being made to nest more than TRANMAXNUM transactions.Either increase the value of your TRANMAXNUM parameter or rewrite your application to require fewer nested transactions.SHUTI was rejected because the Execution Environment parameter "REJECTSHUTI=YES" is specified.Try SHUT first. If that does not shut down the Execution Environment, then use SHUTI.An attempt to connect a gateway/server process to a Data Object Broker failed.If messages that precede this message do not provide sufficient information to diagnose the cause of this failure, contact TIBCO Support.An attempt to close an HCS port opened for a gateway/server process failed.If messages that precede this message do not provide sufficient information to diagnose the cause of this failure, contact TIBCO Support.Gateways/servers started by an osMon process via a gateway/server definition file have some of their parameters set by the osMon. Any value specified by the user is ignored. This message informs the user that the specified parameter's value is overridden by osMon for the specified gateway/server type.No action required. If you want to avoid the message, remove the parameter's assignment from the gateway/server definition file.An attempt to send or receive a message between a gateway/servers process and a Data Object Broker process failed.A shutdown message was sent to a gateway/server process from a Data Object Broker process. As a result, the gateway/server is brought down.Look in the Data Object Broker processes log file to determine the reason for the shutdown.An unknown message type was sent from the Data Object Broker to a gateway/server.A peer server rejected a logon request from a remote user.Messages that precede this message should provide sufficient information to determine the reason for the failure. Check the security profile of the user.Execution of a gateway/server transaction failed.Messages that precede this message in the log should provide sufficient information to determine the cause of the failure.Several of the parameters used to start peer servers are generated by the osMon. This process failed.Make sure the EENAME parameter is set to a non-empty string and the number of servers started by a given osMon is less than 1369.The TYPE of gateway/server being requested in the operator command is only valid in a CICS Execution Environment.Please refer to the Object Service Broker documentation for the valid gateway/server types. Contact TIBCO Support if you need further assistance.The TYPE of gateway/server being requested in the operator command is not valid in a CICS Execution Environment.Please refer to the Object Service Broker documentation for the valid gateway/server types. Contact TIBCO Support if you need further assistance.This is due to the restrictions of the TYPE of DBMS which allows only one thread per Address Space.Please refer to the Object Service Broker documentation for a detailed explanation. Contact TIBCO Support if you need further assistance.CLI Client CONNECT request failed. Reason: EE not initialized with Standby Sessions.The Execution Environment was not initialized with Standby Sessions. Standby Sessions are needed to support CLI Client/Server applications.Use either of the following options to provide Standby Sessions in the Execution Environment:
• Specify the STANDBYNUM=n region parameter via EECONFIG or via HRNIN to set the number of sessions desired.
• Use the following set of operator commands to dynamically start up Standby Sessions:Example F jobname,SETN=n,TYPE=STBExample F jobname,STARTN=n,TYPE=STB
• For CICS Execution Environment, use the HSRV transaction:Example HSRV SETN=n,TYPE=STBExample HSRV STARTN=n,TYPE=STBStart <type> CICS background task failed. Reason: EE not APF authorized.z/OS APF authorization is required for the Execution Environment to start the indicated CICS background task.Refer to the Object Service Broker documentation to learn how to APF authorize the Execution Environment. Contact TIBCO Support if you need further assistance.CLI Start session failed. Reason: No Standby Sessions exist in EEThere are no Standby Sessions in the Execution Environment. Standby Sessions are needed to support CLI Client/Server applications.Use one of the following options to provide Standby Sessions in the Execution Environment:
• Specify the STANDBYNUM=n region parameter via EECONFIG or via HRNIN to set the number of sessions desired.
• Use the following set of operator commands to dynamically start up Standby Sessions:Example F jobname,SETN=n,TYPE=STBExample F jobname,STARTN=n,TYPE=STB
• For CICS Execution Environment, use the HSRV transaction:Example HSRV SETN=n,TYPE=STBExample HSRV STARTN=n,TYPE=STBEE FAILED TO CONNECT TO COMMUNICATION PORT ........ HDR INITIALIZATION TERMINATEDThis message is issued by the S6BDRTMR module. Unable to establish an operator communication connection with the host Object Service Broker Data Object Broker or the Object Service Broker Native Execution Environment.
1. Ensure that the Object Service Broker Data Object Broker or the Object Service Broker Native Execution Environment is active.
2. If the Object Service Broker Data Object Broker or the Object Service Broker Native Execution Environment is active, contact TIBCO Support.The operating system name given to the host computer is too long. Object Service Broker expects it to be less than 17 characters.Rename your host computer to a name whose length is less than 17 characters.TOKEN service is not supported by the Operating System, Encryption Exit not enabledThe Operating System's TOKEN service is used to implement the Encryption Exit to protect the potential integrity exposure and this version of the Operating System does not support this service.z/OS is required for the IEANTCR service.Attempt to create the Encryption Exit TOKEN failed. This is probably caused by Object Service Broker internal error.Attempt to delete the Encryption Exit TOKEN failed, this is probably caused by Object Service Broker internal error. The Encryption Exit routine would be deleted by the Operating System cleanup routine at EE termination.SERVERTYPE=........ NOT SUPPORTED IN A ........ ENVIRONMENTThis message is issued by the HDRSBSRV csect called by S6BDRTMR during Execution Environment initialization and termination. The message indicates that the Execution Environment is attempting to start a gateway/server in an environment that does not support the specified gateway type. Execution Environment initialization continues as normal.Start the gateway/server in a supported environment. Refer to the Object Service Broker documentation for more information.Message issued by CSECT HDRSBSRV. This message accompanies message S6BDR118W and indicates that a gateway/server of the specified type could not be started.Start the gateway/server in a supported environment. Refer to the documentation for more information.NUMBER OF SERVERS REDUCED TO 1 FOR THIS SERVERTYPEMultiple external database gateways were requested via the SERVERS= parameter. Only one gateway of the specified gateway type can be started. The system has automatically reduced the requested number of gateways to one.Language Environment pre-initialization module successfully loadedThe Object Service Broker Execution Environment initialization successfully loaded module CEEPIPI, the IBM Language Environment pre-initialization module.CLI Start EE failed. Reason: This version of S6BDRAPI does not support CICS EE.The S6BDRAPI load module is not linkedited with the required CICS stubs.Reinstall the Object Service Broker CICS component.A wait() on an operating system named pipe (or FIFO) failed.The osee process cannot duplicate the client socket.All available standby sessions in this Execution Environment are in use. Therefore the Start session request is put in a wait queue.Check with your Object Service Broker system administrator about increasing the number of standby sessions.The waiting for a standby session is over; one or more standby sessions have become available.Remote CLI user ........ session Receive Exit error, session terminatedThe Object Service Broker communications Receive Exit detected a severe internal system error during the processing of an incoming message. The error was unrecoverable and the session was unable to continue.The number of the named task had been increased to the number nnn. This is because the number specified in EE CONFIG or in the EE HRNIN parameter file did not meet the minimum required for the successful operation of the Execution Environment. tttttttt is the type of task nnn is the number of the type of taskEXECUTION ENVIRONMENT QUIESCE HAS COMMENCEDNormal shutdown of the Execution Environment has started.There are no active standby sessions in the CICS Execution Environment. Standby sessions are needed to support CLI client/server applications.This situation could happen if the CLI application is getting ahead of the standby session initialization.CLI Start session waiting for standby session to initialize is completeThe wait for standby session initialization is over; one or more standby sessions have become ready.The print DD statement named in the message is ignored because it is not to be used in a multi-user Execution Environment such as CICS or in a Native Execution Environment.Object Service Broker dynamically allocates spool data sets for print output.OPERATOR COMMAND REJECTED; SHUTDOWN PROCESS IN FINAL STAGESOperator command logged via the preceding S6BDR078I message is not being accepted since Shutdown processing is in its final stages and necessary components to service this command may have been dismantled.Execution Environment initialization complete, Version: ........This message indicates that the Execution Environment initialization process has completed and Version indicates the current release level.An invalid request code was passed to HDRCSOPS.Invalid data was returned to program HDRCSOPS from program HDRBUSR.The SMG control block could not be initialized.STOPSERVER failed, Type=..., Name=........, Id=........, RC=...., reason code=....The STOPSERVER request sent to the Data Object Broker came back with the return code and the reason code indicated in the message.
• The Execution Environment would not be shutdown successfully if the gateway/server was not stopped. The Execution Environment may appear to be hung You can try to stop the gateway/server manually by using the Admin Facility or the following z/OS console command:Increase the SESSIONMEMMAX parameter value.Failed to send session log to OAI client due to loss of communication connectionThe attempt to send the session log to the ActiveX Adapter client failed because the connection to the client is lost.Determine why the connection is lost. It is typically either a hardware failure or an improper shutdown of the ActiveX Adapter application.Failed to send end-of-session message to the client due to loss of communication connectionThe attempt to send the end-of-session message to the client failed because the connection to the client is lost.Determine why the connection is lost. It is typically either a hardware failure or an improper shutdown of the ActiveX Adapter application.The client process closed the session. The normal shutdown procedure calls for the Execution Environment to initiate session close.Determine why the client process closed the session. Typically it is as a result of the user forcing a disconnection.Data received by an Execution Environment process from a client process did not satisfy the constraints of the communication protocol.The attempt to initialize the compression engine for ActiveX Adapter communication packet compression failed. The ActiveX Adapter connection is established with no compression.OAI client version %.% is not supported by this Execution EnvironmentThe ActiveX Adapter client version is not supported by the Execution Environment.Upgrade your ActiveX Adapter client to a more recent version.The Execution Environment failed to compress a packet destined for an ActiveX Adapter client.The Execution Environment failed to decompress a packet received from an ActiveX Adapter client.An attempt to execute the specified thread operation failed.Examine the operating system error codes to determine the reason for this failure.During session initialization, the Execution Environment failed to initialize the trusted base tables.Make sure the Data Object Broker is operating correctly.Make sure the Data Object Broker is operating correctly. Check to see if the audit log is full. If this error persists, contact TIBCO Support.An attempt to close an Object Service Broker Communication Service port failed.This message may result from the abend of the process on the other end of the port. Examine accompanying messages in the local log and in the remote processes' log files.An attempt to prompt a user for their userid and password failed.The specified action on an operating system mutex failed.Examine the operating system error codes to determine the reason for the failure. If the error persists, contact TIBCO Support.Attempt to exceed EE-DOB connection limit for DOB '%' failedThe specified Data Object Broker has been configured to accept only a specified number of Execution Environment connections. An attempt was made to exceed this limit.
• Connect fewer Execution Environments to the Data Object Broker. This can be done by increasing the number of sessions that run on each Execution Environment.
• Increase the MAXUSERS parameter that is set in the crparm file.An error occurred while attempting to % a memory mapped fileThe specified action on a memory mapped file failed.Check the operating system error code to determine the reason for the failure. If the problem persists, contact TIBCO Support.The specified action on an event failed.Check the operating system error code to determine the reason for the failure. If the problem persists, contact TIBCO Support.An error occurred while attempting to % a security descriptorThe specified action on a security descriptor failed.Check operating system error code in order to determine the reason for the failure. If the problem persists, contact TIBCO Support.An atexit call, a system called made to ensure proper process shutdown, failed.Check operating system error code in order to determine the reason for the failure. If the problem persists, contact TIBCO Support.An Execution Environment failed to bind to the shared table or rule cache maintained by its osMon.Check the logs to determine the reason for failure. If the problem persists, contact TIBCO Support.The specified operation failed on a process object.Examine the operating system error codes to determine the reason for the failure.Failed to create or start the thread that waits for session terminationsAn attempt to create or start the thread that waits for session thread terminations failed.Previous error messages and operating system error codes written to the log should explain the reason for the failure.The session has shutdown after waiting for keyboard input for more than the amount of time specified by the TIMEOUTLIMIT parameter.If you do not want a timeout, set the TIMEOUTLIMIT parameter to a larger value or to zero. Refer to the Parameters manual for more detail on the TIMEOUTLIMIT and ALLOWSESSIONTIMEOUTLIMIT parameters.The initialization of a standby session failed. This message follows other, more specific, error messages.Check for other error messages preceding this message.Unable to issue HINT command. Reason: EE not APF authorized.An automatic re-cycle of the CICS interface was required due the failure of the Data Object Broker. The EE was unable to issue the HINT command to achieve this as the EE was not APF authorized.If desired restart the CICS interface manually. If automatic restart capability is required APF authorize this EE.The previous error was found in this registry entry.The previous error was found in this file.Language Environment pre-initialization module is being loadedThis is an informational message indicating that CEEPIPI, the LE pre-initialization module, is being loaded.If loading of this module is successful, initialization of the Object Service Broker Execution Environment continues.If it fails, initialization of the Object Service Broker Execution Environment is terminated by the Operation System with an abend code and a reason code.If initialization is unsuccessful, determine the cause of failure by referring to your operating system's abend codes manual. For assistance, contact TIBCO Support.A call to the IBM Language Environment preinitialization interface routine (CEEPIPI), to run the identified function, ended in an error.RC identifies the Return Code from the LE interface routine. The function code and RC are documented in the IBM Language Environment Programming Guide.This is likely an internal Object Service Broker error.sub_ret_code=% sub_reason_code=% sub_feedback_code=%This message provides additional information, if available, to message S6BDR201E. All the codes are documented in the IBM Language Environment Programming Guide.See message S6BDR201E for more information.The value of the parameter does not specify an existing directory.Set the parameter to the path of an accessible directory.An attempt to allocate a temporary disk file failed. Likely causes are insufficient directory permissions or disk full conditions.Check the operating system error number provided with the message. It should indicate the reason for the failure.Error occurred during sanity check of temporary directory parameter % [%]Verification that temporary files may be created, opened for read and write access, and deleted within the temporary directory failed.Review any previous messages related to temporary files to determine the action to be taken.Examine the operating system error codes to determine the reason for this failure.Examine the return code to determine the reason for the failure.Examine the operating system error codes to determine the reason for this failure.A UNIX International thread API call failed.Examine the return code to determine the reason for the failure.Examine the operating system error codes to determine the reason for this failure.Previous error messages and operating system error codes written to the log should explain the reason for the failure.An attempt to destroy a thread failed.Previous error messages and operating system error codes written to the log should explain the reason for the failure.Previous error messages and operating system error codes written to the log should explain the reason for the failure.A thread object was not in the correct state to allow a start operation.Previous error messages and operating system error codes written to the log should explain the reason for the failure.An attempt to resume a thread failed.Previous error messages and operating system error codes written to the log should explain the reason for the failure.An attempt to join with a thread failed.Previous error messages and operating system error codes written to the log should explain the reason for the failure.An illegal attempt was made to join with a thread that is detached.Previous error messages and operating system error codes written to the log should explain the reason for the failure.A thread object was not in the correct state to allow a join operation.Previous error messages and operating system error codes written to the log should explain the reason for the failure.An attempt to get the state of a thread failed.Previous error messages and operating system error codes written to the log should explain the reason for the failure.Previous error messages and operating system error codes written to the log should explain the reason for the failure.A request to sleep could not be satisfied for the requested interval.Examine the operating system error codes to determine the reason for this failure.Thread Id % has ABENDED from an exception thrown at %:%A thread detected it has not correctly handled an internal exception.Previous error messages and operating system error codes written to the log should explain the reason for the failure.Thread Id % has ABENDED from an unexpected exceptionA thread detected that it incorrectly handled an unexpected exception.Previous error messages and operating system error codes written to the log should explain the reason for the failure.An attempt to allocate an index for thread local storage failed.Previous error messages and operating system error codes written to the log should explain the reason for the failure.An attempt to get a value associated with an index for thread local storage failed.Previous error messages and operating system error codes written to the log should explain the reason for the failure.An attempt to set a value associated with an index for thread local storage failed.Previous error messages and operating system error codes written to the log should explain the reason for the failure.Previous error messages and operating system error codes written to the log should explain the reason for the failure.An attempt to destroy a mutex failed.Previous error messages and operating system error codes written to the log should explain the reason for the failure.Previous error messages and operating system error codes written to the log should explain the reason for the failure.An attempt to unlock a mutex failed.Previous error messages and operating system error codes written to the log should explain the reason for the failure.An attempt to create a semaphore failed.Previous error messages and operating system error codes written to the log should explain the reason for the failure.An attempt to open a semaphore failed.Previous error messages and operating system error codes written to the log should explain the reason for the failure.Previous error messages and operating system error codes written to the log should explain the reason for the failure.An attempt to post a semaphore failed.Previous error messages and operating system error codes written to the log should explain the reason for the failure.Previous error messages and operating system error codes written to the log should explain the reason for the failure.A timed wait on a semaphore failed.Previous error messages and operating system error codes written to the log should explain the reason for the failure.Failed to load DLL/Shared Object % for S6BCALL/S6BFUNCTION supportThe Execution Environment failed to load one of the DLLs/Shared Objects listed in the S6BCALLLIBRARIES parameter value.Ensure that the DLL/Shared Object names in S6BCALLLIBRARIES are spelled correctly and the DLLs/Shared Objects are in the relevant paths.DLL/Shared Object % has no entry point for S6BCALL/S6BFUNCTION supportThe Execution didn't find the required entry point for S6BCALL/S6BFUNCTION support in the DLL/Shared Object.Ensure that the DLL/Shared Object is properly coded S6BCALL/S6BFUNCTION support.An attempt to update a Data Object Broker session counter (increase or decrease) failed.Preceding log messages should provide more information as to the reason for the failure.The limits entry is missing in the license key.Check the session limits and types in the license key. Contact TIBCO Support.You exceeded the limit of users allowed for this session type as specified in the license key.Check the session limits and types in the license key. If necessary, contact TIBCO Support.Not enough session memory to minimize Remote CLI/Java CLI message bufferThe Execution Environment failed to optimize Remote CLI/Java CLI memory usage - not enough session memory.Increase the SESSIONMEMMAX parameter.Not enough session memory to accommodate DataOut Remote CLI/Java CLI commareaThe Execution Environment cannot allocate the DataOut Remote CLI/Java CLI commarea for rule call -- not enough session memory.Increase the SESSIONMEMMAX parameter value.Cannot allocate memory for a Remote CLI or a Java CLI sessionThere is not enough memory to complete Remote CLI or Java CLI request processing.Increase the SESSIONMEMMAX Execution Environment parameter value or make more main memory available to Object Service Broker.Invalid Remote CLI/Java CLI message received. Session abendedData received by an Execution Environment process from a Remote CLI or Java CLI client process does not satisfy the constraints of the communication protocol.This version of Remote CLI or Java CLI client is not supportedThis version of the Remote CLI client or the Java CLI client is not supported by this Execution Environment.Use the appropriate version of the Remote CLI client or the Java CLI client.Unexpected Remote CLI or Java CLI request received. Session abendedThe Remote CLI client or the Java CLI client issued an invalid sequence of requests. The session abended.The Execution Environment failed to open a port for Remote CLI or Java CLI connection.Not enough session memory to receive Remote CLI/Java CLI messageThe Execution Environment cannot accommodate the incoming Remote CLI/Java CLI message - not enough session memory.Increase the SESSIONMEMMAX Execution Environment parameter value.Remote CLI/Java CLI DataOut commarea is inconsistent after rule callA rule called via the Remote CLI or the Java CLI reformatted the DataOut commarea header incorrectly.Make sure that the rule formats the CLI DataOut commarea header correctly.Cannot register Remote CLI/Java CLI commareasThe Execution Environment failed to register Remote CLI/Java CLI commarea memory.An attempt is being made to write too much data into the system message log.Increase the value of the SESSION MSGLOGMAX parameter.An attempt is being made to write too much data into the user message log.Increase the value of the SESSION MSGLOGMAX parameter.A connection to a Remote CLI or a Java CLI client process was lost.Check the accompanying messages to determine the reason for the lost connection.The PRINTDEST parameter is set to LOCAL. An attempt was made to determine which printers are local with respect to the machine on which the process is executing. It failed to locate any local printer.Check the operating system error number provided with the message. It should indicate the reason for the failure.Error occurred while attempting to enumerate local printersThe PRINTDEST parameter is set to LOCAL. An attempt was made to determine which printers are local with respect to the machine on which the process is executing. It failed to locate any printer.Check the operating system error number provided with the message. It should indicate the reason for the failure.Only one of PRINTDEST and PRINTXWTR should be non-NULLThe PRINTDEST parameter specifies the name of the printer the user wants reports printed on. PRINTXWTR specifies a program that directs reports to a nonstandard device. Only one of them should be specified at a time.Reset one of these parameters to NULL. Look in the session log file to determine the source of each parameter.An attempt to terminate a connection to an ActiveX Adapter client by an osee failed.Check the operating system error number provided with the message. It should indicate the reason for the failure.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |