![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The Message Switch Address is ready to accept requestsLogic error. The supervisor has detected a physical event for which it does not have a service routine. The request is ignored. Processing continuesThe message switch address space has successfully terminated.GETMAIN FAILED DURING INITIALIZATIONAllocation of storage required to complete Message Switch initialization failed.The initialization of a Message Switch address space has failed.Other messages will have been issued. If you are still unable to ascertain the cause of this failure contact TIBCO Support.MAXIMUM CONNECTIONS OBSERVED FOR THIS MESSAGE SWITCH WAS number'This message appears at the time of Message Switch shutdown and the number in the message is the highest number of end users connected simultaneously to this instance of the Message Switch.The indicated subtask has shut down successfully.A severe error occurred during the indicated subtask. The Object Service Broker Message Switch terminates abnormally. S___ is the system abend code and U___ is the Object Service Broker abend code.If an Object Service Broker return code is provided, look at previous console messages for more information. If only a system return code is provided and you cannot resolve the problem based on this code, contact TIBCO Support.MESSAGE SWITCH INITIALIZATION FAILURE - APF AUTHORIZATION REQUIRED'During Message Switch initialization, it was determined that the Message Switch was not executed in an APF Authorized state as required. The Message Switch will abend with user code 49.Refer to the Object Service Broker Documentation for instructions on how to APF Authorize your Message Switch.Storage for an internal Message Switch control block was not available.Increase the region size and restart the Message SwitchThe module for the indicated subtask cannot be accessed. Object Service Broker terminates abnormally.See the previous messages on the console and refer to the Installation and Operations manual.An error occurred during the initialization of the indicated subtask. Object Service Broker terminates abnormally.See the previous messages on the console and refer to the Installation and Operations manual.Insufficient storage was available to build the Message Switch resources for the specified configuration.Refer to the Installation and Operations manual. Validate that the concurrency options are compatible with the region size specified at Message Switch startup.ABEND S___/U____ REAS=________ DETECTED IN MODULE 'The Message Switch has abended as described in the message. If a SYSxDUMP data set was allocated to the Message Switch, it will contain the dump for the error.Collect as much information about the failure as possible and contact TIBCO Support.EVENT (____) REJECTED IN ________, MESSAGE SWITCH TERMINATINGThe module identified by "taskname" received an event to process "xxxx" and the Message Switch started the termination process. The "termtype" value can be either "NORMALLY" indicating a SHUTDOWN request was issued or "ABNORMALLY" indicating a task abended. The requested event processing is ignored.Wait for the termination to complete and then recycle the Message Switch.The indicated parameter does not have an associated assigned value. All Message Switch parameters are of the form: keyword=value. Spaces are not permitted between the keyword, equal sign, or value. The parameter is rejected. Object Service Broker Message Switch startup terminates abnormally.
• Cross Memory Services for Object Service Broker inter-region communication
• Internal Object Service Broker SMF records (optional)
• Journal offload (spin) by Started System Task (optional)REFER TO MESSAGE SWITCH PARMS IN INSTALLATION MANUALAn error was detected in your Object Service Broker initialization parameters.Refer to the Job message log for preceding specific parameter error(s). Refer to the Object Service Broker Documentation for parameter syntax, spelling, ranges, defaults.MSWPARMS FILE BYPASSED - INVALID RECFM OR LRECL'An MSWPARMS DD statement was provided, but its record format was not fixed block, or its record length was not 80. Data Object Broker initialization continues. Parameter values are default values unless a PARM= string containing override values is provided.If Object Service Broker started with incorrect parameter values, shut it down. Do one of the following:
• Allocate an MSWPARMS file with RECFM=FB and LRECL=80, and supply the correct parameter assignments.
• If Object Service Broker runs as a batch job, you can use //MSWPARMS DD * to define parameters in- stream.
• If the parameter specifications are 100 characters or less, you can omit //MSWPARMS and just use the PARM= string.MSWPARMS FILE BYPASSED - OPEN UNSUCCESSFULA MSWPARMS DD statement was provided but failed to open properly. Data Object Broker initialization continues. Parameter values are default values unless a PARM= string containing override values is provided.If Object Service Broker started with incorrect parameter values, shut it down. Investigate the MSWPARMS file problem. When the problem is resolved, restart Object Service Broker._____________ PARM CONTAINS INVALID CHARACTER(S)'The indicated parameter contains characters which are not alphabetic. The parameter is rejected. Object Service Broker startup terminates abnormally.Verify and correct the spelling of the parameter. Refer to the Installation and Operations manual if necessary.The indicated parameter was abbreviated so that it is no longer unique. The parameter is rejected. Object Service Broker startup terminates abnormally.You can spell Data Object Broker parameters in full or abbreviate them through truncation. For example, SNAPOVERRIDE or SNAPOVER or SNAPO are all accepted. Excessive truncation, however, results in abbreviations that can be one of several parameters. For example, SNAP might be any one of SNAPCLASS, SNAPREMOTE, SNAPQUERY, SNAPOVERRIDE, or SNAPVOLSER.Spell the parameter keyword name more fully or completely. In general, five characters are sufficient to achieve uniqueness. Refer to the Installation and Operations manual if necessary.The indicated parameter (only the first 13 characters appear in the message) is not defined to Object Service Broker. You may have used an unrecognizable abbreviation. The parameter is rejected. Object Service Broker startup terminates abnormally.Verify the spelling of the parameter. Refer to the Installation and Operations manual if necessary. Abbreviation through truncation is permitted, but it is recommended that at least the first five letters be supplied to ensure uniqueness.An operator console command was issued, of the form:The keyname specified was a recognized Object Service Broker Data Object Broker parameter, but it is not eligible for modification after startup or once set. The parameter change is rejected. Object Service Broker execution continues.If the parameter must be changed then this change must be made to the Object Service Broker Data Object Broker initialization parameters and will take effect the next time Object Service Broker is restarted._____________ SPECIFIED VALUE HAS TOO MANY CHARACTERS'The value assigned to the keyword has too many characters. The parameter is rejected. Object Service Broker startup terminates abnormally.Provide an acceptable parameter value in //MSWPARMS or PARM= string. Refer to the Installation and Operations manual if necessary._____________ SPECIFIED VALUE CONTAINS INVALID CHAR(S)'The value assigned to the parameter has failed its edit validity check. This occurs for any non-alphanumeric value, or for a discrepancy between edit specifications and the input provided. The parameter is rejected. Object Service Broker startup terminates abnormally.Provide an acceptable parameter value in //MSWPARMS or PARM= string. Refer to the Installation and Operations manual if necessary._____________ SPECIFIED VALUE NOT VALID QUALIFIER(S)'The value assigned to the parameter has failed its validity check. A data set name or qualifier, member name, or other entity with similar syntax was expected. The parameter is rejected. Object Service Broker startup terminates abnormally.Provide an acceptable parameter value in //MSWPARMS or PARM= string. Refer to the Installation and Operations if necessary.The value assigned to the parameter is too big or too small. The parameter is rejected. Object Service Broker startup terminates abnormally.Provide an acceptable parameter value in //MSWPARMS or PARM= string. Refer to the Installation and Operations manual if necessary.GETMAIN FAILURE ON ____ POOL, ____ SPACE _____ THE LINE ON A ____ BOUNDARY, RC=Object Service Broker manages its own storage in blocks referred to as pools. When attempting to acquire storage to support, the specified pool the storage was not available.Determine why the storage requirements were not satisfied. Check the memory control parameters on the run and increase as needed. Contact TIBCO Support if further support is required.XCF MEMBER NAME AND GROUP NAME BOTH SET TO ___________The XCF group and member name are identical. This is not allowed.Modify either the XCF group or member name and restart the message switch.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.NO COMMUNICATION FACILITIES AVAILABLE'No Communications protocols are available to the Object Service Broker Message Switch. Object Service Broke 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 place. If you are unable to resolve the situation, contact TIBCO Support.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.An unformatted logon request has been received by the Message Switch.The logon request is rejected with a sense code of x'0C00'. This is normally caused by an attempt to connect to the Message Switch in error. If the message is issued repeatedly try to ascertain the source of the request. If you are unable to resolve the situation, contact TIBCO Support.REQUEST __________ RETURN CODE ____ FOR ________ USER ________ # =______ FROM _____'A request for action has failed with return code given.If you are unable to determine the cause of the message, contact TIBCO Support.The specified user has been cancelled.connectid action TERM=termid J=jobname connecttype #=num S=source T=targetThis notification message identifies a logon or logoff from the message switch.
• .connectid may or may not be unique depending on site configuration
• .action is either 'LOGGED ON' or 'LOGGED OFF'
•
• .connecttype is the type of connection e.g. 'TSO USER'
• .num is the relative connection block used to support this connection. It is always unique.
• .source is the communication type for the source session
• .target is the communications type for the target sessionServices provided by the operations support task indicated in the message are not available due to the failure of this task to initialize.Review the initialization messages in the Message Switch's job log to determine the reason for the failure. Terminate and restart the Message Switch at the earliest opportunity after the problem is resolved.An error has been encountered during the initialization of the Message Switch's console interface. Message Switch initialization continues but console services are not available.Review the initialization messages in the Message Switch's job log to determine the reason for the failure. Terminate and restart the Message Switch at the earliest opportunity after the problem is resolved.Initialization was successful for the task supporting operator console MODIFY commands. You can enter Object Service Broker MODIFY commands and receive a response.This message indicates that an invalid post code has been received by the Message Switch's operational support task and cannot be processed.This is an internal processing error and should be reported to TIBCO Support.This message is the standard acknowledgement that the command is valid when no more specific reply exists.Upon completion of external command processing, the work buffer used to carry the command could not be released.The operations support services task indicated in the message terminated due to an unrecoverable failure. The system will attempt a restart of the failing task.Review the Message Switch's job log to determine the reason for the failure and report this problem to TIBCO Support._______ SERVICES SUSPENDED - RESTART LIMIT EXCEEDED'The operations support service indicated in the message could not be recovered after a failure. These services are disabled until the Message Switch is restarted.Review the Message Switch's job log to determine the reason for the failure and report this problem to TIBCO Support.This message indicates that automatic recovery is in progress for the service indicated in the message.Begin an investigation into the cause of the initial failure. If the service is successfully reinstated, no immediate action is required.This message is issued to indicate the success or failure of the restart action for the indicated operations service.Example F jobname,action=useridThe specified USER was not logged on to Object Service Broker. No action is taken.Example F jobname,USERLISTdisplays a list of the userids logged on to Object Service Broker.The console command detected multiple userid/termids and needs to know which userid/termid to act upon.Reissue the command with ";xxxx", where xxxx is the mswcnum from message S6BMS514I.USERID TERMID JOBNAME TYPE MSWCNUM STATUS SOURCE TARGETThese are the headings for message S6BMS614I.________ ________ ________ ____________ ______ _______ ______ ____S6BMS613I shows headings for the data rows in S6BMS614I; The data in S6BMS614I is used to determine the different userid/termids.May be used to determine which mswcnum to use when a console command is issued.This message displays the count of duplicate entries.REPEAT COMMAND AS ____________USERID;MSWCNUM"The console command could not determine which duplicate entry to act on. S6BMS614I lists the commnum of all duplicates.Reissue the console command with ";mswcnum" at the end of the command, where the mswcnum is from the preceding S6BMS614I messages.UNEXPECTED USER ID FOUND IN SPECIFIED MSWCOMMAA display/cancel user request was issued. The buffer identified as containing the user information is invalid.Retry the cancel request. If the error recurs, contact TIBCO Support.SPECIFIED MSWCOMMA NUMBER OUT OF RANGE, REQUEST REJECTED'A CANCELUSER/DISPLAYUSER request was issued with an explicate mswcomma number, the supplied mswcomma number is out of range.Example F jobname,CANCELUSER=server_idThe ID specified is a DBMS gateway. No action is taken.Use the Data Object Broker STOPSERVER command to shut down a DBMS gateway.A CANCELUSER command was issued to terminate a user or DBMS gateway. Because no work buffer was available, the request could not be processed.The command may succeed if reissued. If this message occurs again, the reason for the lack of work buffers should be investigated.A request was received by the Message Switch to cancel a specified user session that is currently being terminated. The request cannot be fulfilled.A command was entered and the specified userid was not between 1 and 8 characters long, for example, CANCELUSER=uuuuuu;nnnn. The userid (uuuuuu) must be 1 to 8 characters long.Enter the command again with the correct format.The console command was reissued but no data was detected beyond ";".Reissue the command with the desired mswcnum.MSWCNUM NOT NUMERIC, COMMAND REJECTED'The data in the console command after the ";" was not numeric.Reenter the console command with a numeric value for the mswcnum.MSWCNUM TOO LARGE, COMMAND REJECTED'The mswcnum entered was greater than the highest allocated mswcnum.Check the value of the mswcnum and reenter the command.Example S6BMS629I is the heading followed by the response data. They are followed by summary messages S6BMS630I and S6BMS631I. If no Object Service Broker users are logged on, only S6BMS630I and S6BMS631I are issued.Object Service Broker connections are identified by their userid. The format of the display is c-uuuuuuuu, where:
• D - DBMS Server connection or Outbound Peer (HRN)
• L - Connection that is in the process of logging onSee explanation for message S6BMS629I.See explanation for message S6BMS629I.A MODIFY command was issued in the form "command=value". The particular command verb specified is defined to be a one word action command without any assigned value. The command is rejected.The command can be reissued without an assigned value, if appropriate. If in doubt, refer to the operator command documentation in the Installation and Operations manual._____________ COMMAND CONTAINS INVALID CHARACTER(S)'Verify the spelling of the command. Refer to the Installation and Operations manual if necessary.The indicated command contains characters that are not alphabetic. The command is rejected.The indicated command has been abbreviated so that it is no longer unique. The command is rejected. Object Service Broker MODIFY commands may be spelled in full or abbreviated through truncation. Excessive truncation results in abbreviations that can be one of several that can be one of several commands.Spell the parameter keyword name more fully, or completely. Generally, 5 characters are adequate to achieve uniqueness. Refer to the Installation and Operations manual if necessary.The indicated command (only the first 12 characters appear in the message) is not defined to Object Service Broker. You may have used an unrecognizable abbreviation. The command is rejected.Verify the spelling of the command. Refer to the Installation and Operations manual if necessary. Abbreviations are only recognized if they are spelled the same as the full command up to the point of truncation._____________ REJECTED, SHUTDOWN IN PROGRESS'The specified request was rejected because Object Service Broker had already accepted a shutdown request.Object Service Broker is coming down -- no action required.A MODIFY was issued as a one word action command. The particular command verb is defined to be for a "keyword=value" command. The command is rejected.Provide an appropriate value when issuing this command. Refer to the Installation and Operations manual if necessary._____________ SPECIFIED VALUE HAS TOO MANY CHARACTERS'The value assigned to the keyword has too many characters. The command is rejected.Reenter the command with an acceptable value. Refer to the Installation and Operations manual if necessary._____________ SPECIFIED VALUE CONTAINS INVALID CHAR(S)'The value assigned to the command failed its edit validity check. This error occurs for any non-alphanumeric value, or for a discrepancy between edit specifications and the input provided. The command is rejected.Reenter the command with an acceptable value. Refer to the Installation and Operations manual if necessary._____________ SPECIFIED VALUE NOT VALID QUALIFIER/DSNAME'The value assigned to the command failed its validity check. A data set name or qualifier, member name, or other entity with similar syntax was expected. The command is rejected.Reenter the command with an acceptable value. Refer to the Installation and Operations manual if necessary.The processing of operator console messages encountered a problem while freeing a message buffer. This may result in failure of the Operator Command Interface.If operator console MODIFY commands are no longer being accepted, contact TIBCO Support.COMMAND NOT PROCESSED, COULD NOT OBTAIN BUFFER'The Message Switch was not able to obtain the work area needed to process an operator request. This is usually a temporary situation and should be resolved almost immediately.Reenter the rejected operator command. If the problem persists, obtain a dump of the Message Switch and terminate it at your earliest convenience. Notify TIBCO Support.MODIFY ' ________ _________________________________"The command received from the console is echoed. This verifies command recognition and records the command in the console log for the Object Service Broker Message Switch.There are no user sessions connected to this message switch.Internal logic error. Object Service Broker supervisory code detected an invalid system service request. The transaction is aborted.XCF REQUEST ________ FAILED RETURN CODE ____ REASON CODE ____'Look up the return code and reason code for the failing request in the IBM Sysplex Services Reference. If unable to determine the cause of the failure contact TIBCO Support.IXCQUERY ____ RECORDS NOT RETRIEVED'The internal buffer for the IXCQUERY response was not sufficiently large to accommodate all the records returned by the IXCQUERY request.PRIMARY DATA OBJECT BROKER LOCATION TIME INTERVAL EXPIRED'A primary Data Object Broker was not located in the time specified.The Message Switch will terminate. If required restart the Message Switch.PRIMARY DATA OBJECT BROKER NOT AVAILABLEThe Message Switch could not locate the Primary Data Object Broker.If allowed the message switch will wait for a Primary Data Object Broker to become available, if not the Message Switch will terminate. Make sure a Primary Data Object Broker is available and restart the Message Switch.PRIMARY DATA OBJECT BROKER LOCATED AT MEMBER NAME ________'The Message Switch has located the Primary Data Object Broker.Output from a Memberlist Message Switch command. gggggggg is the XCF group to which the Data Object Broker belongs.MEMBER JOBNAME SYSTEM SYSTEM STATE USER STATE'Output from a Memberlist Command. One line for each member in the XCF group:
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |