![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
TIBCO(r) Object Service Broker/CICS interface initialization complete.The TIBCO(r) Object Service Broker/CICS interface activation is complete and the interface is ready to accept logons.This message provides the number of users who have logged on through this Execution Environment.CICS Server Task attach failed, check JOBLOG for error message(s)An attempt to attach the TIBCO(r) Object Service Broker/CICS gateway task failed. More diagnostic message(s) may be found in the JOBLOG.CLI Client CONNECT request failed. Reason: Error detected during CLI CICS task "STARTSESSION".A severe error was detected while trying to connect the CLI CICS task to the Standby Session for the CLI Client. Additional error messages precede this message.This error is likely caused by other events or errors elsewhere in the system.Correct the errors indicated by the preceding messages. If necessary, contact TIBCO Support for assistance.Execution Environment Subtask Locate Failure RC=X'...... ...'A request to locate the Execution Environment gateway subtask has failed. Use the return code to determine the cause of the failure:
• X'00000004' - The MSB control block could not be located.
• X'00000008' - The MSB control block failed validation.
• X'00000010' - A TCB validation failure detected during TCB scan.Depending on the return code, do one of the following:
• RC=X'00000004' - Indicates that the Data Object Broker gateway task is not attached. Use the HOPS command to provide a status of Object Service Broker. Issue the HINT command to restart the gateway task if required and retry the session.
• RC=X'00000008' - This is an internal error. Take an SDUMP of the address space if the problem persists and contact TIBCO Support.
• RC=X'0000000C' - This is an operating system error. Take an SDUMP of the address space in question and contact TIBCO Support.
• RC=X'00000010' a TCB validation error may occur when another application is ATTACHing or DETACHing subtasks while TIBCO(r) Object Service Broker is scanning the TCBs. Retrying the session will likely succeed. If problems persist, take a SDUMP and contact TIBCO Support.CICS EXECUTION ENVIRONMENT SUBTASK ABENDED, TCBCMP=X'......'This message is issued by the S6BCSCIC module. The Execution Environment subtask abended with the indicated completion code. Probable cause of error may be that the Data Object Broker was not active and therefore OPENPORT was failed.Check the console log for error messages issued by other TIBCO(r) Object Service Broker routines for more information. If unable to determine the error, do the following:CICS EXECUTION ENVIRONMENT SUBTASK DETACHEDThis message is issued by the S6BCSCIC module. The Execution Environment subtask was successfully detached.SYNTAX ERROR - CLEAR SCREEN AND ENTER AGAINThis message is issued by the S6BCSCIC module.This message is issued by the S6BCSCIC module. The TIBCO(r) Object Service Broker session has ended at the request of the user.SESSION TERMINATED ABNORMALLY-> CODE: ....This message is issued by the S6BCSKRN module. The TIBCO(r) Object Service Broker session has terminated abnormally with the indicated ABEND code.See the previous diagnostic messages, if any. Refer to the IBM manual for CICS messages if it is a CICS ABEND code.TRANSACTION TERMINATED. CANNOT BE STARTED AT CONSOLE.This message is issued by the S6BCSCIC module. You used a console to establish a TIBCO(r) Object Service Broker session.Use a dedicated terminal to establish a TIBCO(r) Object Service Broker session.This message is issued by the S6BCSOPS module. This message displays the list of users that are currently logged on to the Object Service Broker Data Object Broker through this Object Service Broker CICS interface.CICS: NO STORAGE AVAILABLE FOR GETMAINThis message is issued by the S6BCSCIC module. No more storage is available to start a TIBCO(r) Object Service Broker session.Wait for storage to become available and try again (for example, when one or more logged on users finish their TIBCO(r) Object Service Broker session). If this situation occurs often, more resources may be required for this CICS region.This messages is a header for information that follows, dividing subsequent information into columns.An attempt to perform the session end action failed for the indicated reason:Reason codes are documented in the CICS Application Programming Reference manual.Resolve the error situation as indicated and try again. Contact TIBCO Support if you need further assistance."START TRANSID(xxxx) USERID(uuuuuuuu)" failed. Reason: rrrrrrrrrrrrrrrAttempt to start the CLI session CICS background task failed for the identified user and for the indicated reason, which can be one of the following:
• NOTAUTH The regular Object Service Broker transaction (default HURN) is not authorized to issue the "START TRANSID" CICS command for the identified user.
• USERIDERR The identified user is not defined to the external security system.
• TRANSIDERR The identified transaction is not defined to CICS.
• RESP=c1 RESP2=c2 These response codes are not translated into English. They are documented in the IBM CICS Application Programming Reference manual. RESP=c1 was extracted from EIBRESP and RESP2=c2 was extracted from the EIBRESP2, fields in the EIB (EXEC Interface Block) control block.Resolve the error situation as indicated by the reason or the response codes. Contact TIBCO Support if you need further assistance.UNABLE TO LOAD mmmmmmmm ABCODE=X'aaaaaaaa' REASON CODE=X'cccccccc'Error detected when loading Object Service Broker system modules. Object Service Broker Execution Environment startup will be terminated.
• mmmmmmmm is the module name that the load operation was failedCOMMAREA TOO SMALL FOR OCCURRENCEThis message is issued by the BLTPASSD module. Object Service Broker attempted to place a requested occurrence in the user-created COMMAREA. The space remaining in this COMMAREA is 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 writing multiple occurrences to the COMMAREA, reduce the number of occurrencesThis message is issued by the BLTPASSD module. The table specified in $SETCOMMAREA cannot be found.CONNECTION WITH DATA OBJECT BROKER LOST, ID=........This message is issued by the S6BCSCIC module. The Execution Environment connection to the Data Object Broker has been lost.Check that Data Object Broker is still active, whether the user session was canceled, and that VTAM is still functioning.This message is issued by the S6BCSOPS module. When there is more than one screen of display output, the system waits for the action from the user to display the second and subsequent screens, or to end the transaction.Follow the instructions of the message and act accordingly.This message indicates that the current session has been canceled by a HCUS transaction entered from another terminal or an OS console or lost terminal error logic in a CICS environment.Check with the system administrator to find out why the session was canceled. You may reconnect to Object Service Broker/Object Service Broker and continue processing.This message is issued by the S6BCSCIC module. The current session was abnormally terminated because the installation terminal inactivity threshold was exceeded.Discuss with the System Administrator if the threshold is impractical and modify it if necessary.An internal storage stack request has failed. The failure can be identified by analyzing the return code. A CICS transaction dump will be taken with a dumpcode of HEXC.
• X'00000004' - Storage area provided is insufficient for request
• X'0000000C' - Storage area not doubleword-alignedThe HEXC transaction dumpcode is used by Object Service Broker to identify a CICS transaction associated with this message. Format the CICS transaction dump using the utilities supplied with CICS, and contact TIBCO Support for assistance.Invalid PARMS length passed in CICS COMMAREAThe two byte binary COMMAREA length supplied in the COMMAREA is invalid.Recheck length by calling user program and correct.The Execution Environment has been recycled since the last time the user pressed <Enter>.The Application Owning Region has been recycled. The user session no longer exists.CICS Transaction 'hhhh' Abend 'xxxx' detected on terminal 'tttt' for user 'uuuuuuuu' at 'hh:mm:ss'A CICS transaction abend was detected for the specified transaction. The terminal and user identification are identified in the message.A CICS transaction abend was intercepted. A CICS transaction dump will be scheduled for most abends. Exceptions are: ATCH, ATCI, ATNI, AZ** and AX** codes.Refer to the CICS Messages and Codes manual for a description of the abend. Save the CICS transaction dump and all associated logs for analysis by TIBCO Support if the problem appears to be caused by Object Service Broker.Recovery of the error will be attempted except for the abend codes noted above. Message S6BCS084I accompanies this message and provides information on the action scheduled by Object Service Broker for this error condition.Action taken for user 'uuuuuuuu': aaaaaaaa bbbbbbbb ccccccccA CICS transaction abend has been detected as indicated by the associated S6BCS083E message. This message describes the action scheduled as a result of the abend.The uuuuuuuu in the message identifies the user session and the fields aaaaaaaa, bbbbbbbb, and cccccccc indicate the actions scheduled as a result of the associated error condition. Possible values include:
• LOSTTERM - indicates that the terminal facility cannot be used.
• CICSDUMP - a CICS transaction dump has been scheduled for this error. Save this diagnostic information for analysis.
• TERMSESS - the user session must be terminated. The abend is unrecoverable.
• RECOVERY - an attempt to recover the session will be scheduled as the error may be recoverable.
• TERMIMM - a recursive non-recoverable abend situation has been detected and immediate session termination must be performed.
• CANCEL - an abend has been detected while the session is in the process of terminating.The user session cannot be continued because of an undetermined condition.Your session will be terminated. Perform your logon again to reestablish a valid Object Service Broker session. If the logon attempt fails, contact your Object Service Broker system administrator. Use the HOPS command to verify that your original session has been terminated successfully. Save all CICS and Data Object Broker job logs and error logs for analysis.NOT AUTHORIZED TO WRITE TEMPORARY STORAGE. SESSION CANCELLEDAn unauthorized attempt was made to write to TOR temporary storage.The transaction is ended after the above message has been issued.User ........ session lost connection with DOB, enter CICS canceluser transaction to cancel sessionThe named user in the message has lost their session with the Data Object Broker. The Execution Environment is unable to schedule a CICS HCUS command to cancel the user because it is running unauthorized.Manually issue an Object Service Broker CICS HCUS transaction against the named user to cancel them.S6BCSNEM started HCUS TTTTNNNNNNNN routed to AAAAAAAAThis message is issued when a HCUS termid command is scheduled by S6BCSNEM because of a lost terminal condition. It appears in the CICS region's CSMT log, or in the case of an MRO configuration, in the TOR CICS region's CSMT log.
• NNNNNNNN - The user's VTAM terminal ID
• AAAAAAAA - The VTAM applid of the CICS region where the HCUS {TTTT | NNNNNNNN} request will be processed.S6BCSNEM ERROR: EEEEEEEE TERMID=TTTTThis message is issued when an error condition is detected during S6BCSNEM lost terminal processing. It appears in the CICS region's CSMT log, or in the case of an MRO configuration, in the TOR CICS region's CSMT log.
• EEEEEEEE - The CICS error condition, which can be any of the following error codes:
1. INVREQ, IOERR, NOAUTH, SYSIDERR, TERMIDERR, TRANSIDERR, ISCINVREQ
2.
3. Analyze the generated CICS dump. The descriptions of the error codes in item 1 are described in the IBM CICS/VS application programmer's guide. Item 2 indicates that a common area was not specified in the program calling S6BCSNEM. Item 3 indicates that the VTAM applid of the AOR is not defined in the TOR.S6BCSOPT ERROR:WWWWWWWW REASON:XXXXXXXX TERMID=YYYY SYSID=ZZZZThis message is issued when an error condition is detected in the program module S6BCSOPT. It appears in the CSMT log of the CICS owning region. A CICS dump is generated with a dump code of HOPT. The variables represent the following:
• WWWWWWWW - The EXEC command that returned the error response. The possible values are RETRIEVE and START.
• XXXXXXXX - The error condition which can be any of the following: INVREQ, IOERR, ISINVREQ, NOTAUTH, SYSIDERR, TERMIDERR, TRANSIDERR, ENDDATA, ENVDEFERR, LENGERR, NOTFIND.
• ZZZZ - The system ID of the CICS application owning region.Analyze the CICS transaction dump. Detailed error descriptions are documented in the IBM CICS/VS application programmer's guide.The Cancel User transaction must be followed by a blank and then a userid. Example: HCUS BILLUSER.Storage areas are released then the transaction is terminated. The user should reenter the transaction in the correct format, as shown in the given example.The Session Termination transaction must be followed by a valid parameter, which maybe either SHUT, SHUTD (which is functionally the same as SHUT) or SHUTI. Example: HTRM SHUT, where HTRM is the Session Termination transaction.Storage areas are released and the transaction is terminated. The transaction should be reentered. The example illustrates the correct format.LOAD OF MODULE, S6BCSKRN FAILED. CICS INTERFACE INITIALIZATION TERMINATEDAn attempt to load the CICS-Object Service Broker interface initialization module, S6BCSKRN failed. Because of this, the Object Service Broker transaction is unable to continue and is therefor terminated.Retry the Object Service Broker transaction. If the same failure persists, contact the CICS technical support representative.TRANSACTION requires valid parm; refer to documentation.The parameters passed to this CICS transaction are invalid. Additional error messages may precede or follow this message.Refer to the Object Service Broker documentation for the valid parameters.The TIMEOUT and security transaction, HCSS is only supposed to run by means of a started transaction. Instead, the user entered HCSS from the terminal, which is not permitted.Storage areas are released and the transaction is terminated. The HCSS transaction will never work, when entered from a terminal.The HOPS transaction is no longer supported. Please use HINQ for inquiry and HCUS for canceluserThe HOPS transaction has been replaced by HINQ, HCUS, and HFUSUse HINQ for userlist, HCUS for cancel user session, and HFUS for force user session.Program XXXXXXXX received bad return code from HDRBUSR.RC = XXXXProgram XXXXXXXX received an invalid return code from program HDRBUSR.Invalid or unsupported function code XXXX passed to S6BCSKRNThe function code XXXX passed to program S6BCSKRN was invalid or is not supported in the current Execution Environment (CICS, IMS, NEE).
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |