|
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |
The session startup rule or the workbench failed.The message log is automatically printed if a startup rule or workbench fails. Browse the log in the output of the job for more information.The specified CHARSET is invalid or is not supported. CHARSET is a session parameter.You specified the EXECMODE Execution Environment parameter with a value other than Y.EXECMODE is obsolete and remains in Object Service Broker for legacy purposes only.Remove EXECMODE or specify EXECMODE=Y. In either case, you get strong type checking in the Rule Editor without logging of violations.This message is issued by the SESSMGR module. The logon request was rejected by the Data Object Broker because the limit for the number of sessions set by the installation has been reached.This message is issued by the SESSMGR module. The Data Object Broker is restricting logons to operators only.Logon rejected - batch connections are not being accepted at this timeThis message is issued by the SESSMGR module. The Data Object Broker is not accepting batch connections.The release level of the Execution Environment software is not compatible with the release level of the Data Object Broker.Verify that you are logging onto the intended Data Object Broker. If you are, then contact your system administrator.You are attempting to log on with a userid that is already being used.Verify that the userid was correctly entered and that you are logging on to the intended Data Object Broker. If these are correct, contact your system administrator.Communication error during LOGON SENSE=X'9999' ID=XXXXXXXXA communication error occurred when the session attempted to connect to the Data Object Broker. The Data Object Broker may be quiesced.If the Data Object Broker is not quiesced, contact TIBCO Support.Review the entered HURN CICS command, or your batch JCL session parameters, to ensure that a userid has been specified.You specified an invalid userid. The name contains more than 8 characters.Verify that you have entered a correct userid when logging on.During Execution Environment logon processing, HDRSBUSR could not add a new userid to the Execution Environment's list of users.USERID not removed from Execution Environment ListDuring Execution Environment logoff processing, HDRSBUSR could not remove the session's userid from the Execution Environments's list of users.During logon processing, the storage manager could not initialize a scope for session storage.During logon processing, the storage manager could not terminate the scope for session storage.LOGON terminated - terminal timeout cleanup in progress, try again laterThe current session was canceled because the user's terminal has been inactive for too long.Press the <Enter> key and attempt to log on again. The maximum period of time a terminal may be left inactive is controlled by the TIMEOUTLIMIT Execution Environment parameter.Unable to Logon - unknown SENSE=X'9999' ID=XXXXXXXXYou cannot connect to the Data Object Broker. For an explanation of the SENSE information, refer to message S6BKC036.You failed logon security validation.Review any previous security messages to determine the action to be taken.The rule manager detected an error during initialization.The message log is automatically printed if a startup rule or workbench fails. Browse the log in the output of the job for more information.The EVENT/SMF monitor detected an error during session initialization.The pre-session create user exit detected an error.A session create exit for the Execution Environment Exit Facility has been defined by the installation. Review the exit defined by HRNXD to determine why the exit returned a nonzero return code.Default storage limits and thresholds for a session could not be changed.The EVENT/SMF monitor detected an error during session recording initialization.The pre-execution session user exit detected an error.A pre-execution session exit for the Execution Environment Exit Facility has been defined by the installation. Review the exit defined by HRNXD to determine why the exit returned a nonzero return code.The security logoff process detected an error.Review any previous messages from security logoff processing to determine the action to be taken.Initialization of the run time environment failed.Insertion of the Capture/Replay facility exit failed.This message is issued by the SESSMGR module. The Data Object Broker is not accepting any logons due to storage constraints.Check the Data Object Broker for more messages, and contact your system administrator.Internal parameter error SENSE=X'9999' ID=XXXXXXXXThis message is issued by the SESSMGR module. An internal parameter error has been detected.This message is issued by the SESSMGR module. A length error has been detected during session end processing. Either the length is a negative number or it exceeded the maximum of 31 KB for a message segment.Correct the error and retry or contact TIBCO Support.The Data Object Broker is in a quiescent state and is not accepting any logons at this time.Check with your System Administrator to find out when you should try again.The Execution Environment is being shut down and is not accepting any logons at this time.Check with your System Administrator to find out when you should try again.Execution Environment startup parameters SERVERTYPE= or SERVERID= may have been misspelled, omitted, or may not be coordinated with the Resource Management System.Use the TSO ADMIN clist to access the Resource Management System and verify that path definitions are coordinated with Execution Environment startup parameters SERVERTYPE= ("TYPE" in Path Management) and SERVERID= ("GROUP ID" in Path Management).The CONNECTIONS MAX value in the Path Management System definition for a specific path has been exceeded by the number of paths requested from the Execution Environment.Use the TSO ADMIN clist to access the Path Management System, and increase the CONNECTIONS MAX value for the path in question. Then reissue the request for paths from the Execution Environment.Possible logic error in Path Management System.An external resource (DBMS gateway, Remote Rule Server or Peer System) connection has been 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 Path Management system. A KC081 message on the Data Object Broker console log identifies the resource characteristics that were failed at connection time.Review the KC081 message on the Data Object Broker console log, and coordinate similar parameters specified in Execution Environment, Data Object Broker and Path Management (e.g., FSLEVEL).A peer serverid defined on one Data Object Broker is not defined as expected on another Data Object Broker.Use the TSO ADMIN CLIST to access the Path Management System on both Data Object Brokers, and examine and coordinate the peer server definitions between them.A peer serverid on one Data Object Broker is already defined for use on another Data Object Broker.Use the TSO ADMIN clist to access the Path Management System on both Data Object Brokers, and examine and coordinate the peer server definitions between them.The Execution Environment has not specified a supported serverid to the Path Management System in the Data Object Broker.Use the TSO ADMIN clist to access the Path Management System, and verify that the paths are defined correctly. Check that the SERVERID= startup parameter in the Execution Environment has been specified correctly. If the message persists, contact TIBCO Support.The session received a DISPLAYCODEPAGE value that is invalid or unsupported. This message is only applicable in a z/OS environment.Correct the value of the session parameter DISPLAYCODEPAGE.The NLS initialization routine has failed. Either the NLS specification in table @NLS1 is invalid or the loading of the required translation tables has failed.Check the log for previous error messages issued during NLS initialization. Respecify correct values for the @NLS1 fields if they are invalid, and ensure the required translation table modules are available and on the search path.CODEPAGE FILE ERROR - TYPE n, RETURN CODE = xxAn error has been detected reading the value of the LOCALE_CP field in the table @NLS1 for the SELF row. The error type n is as follows:
|
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |