![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Initialization was successful for the task supporting operator console MODIFY commands. You can enter Object Service Broker MODIFY commands and receive a response.An error has been encountered during the initialization of the Data Object Broker's console interface. Data Object Broker initialization continues but console services are not available.Review the initialization messages in the Data Object Broker's job log to determine the reason for the failure. Terminate and restart the Data Object Broker at the earliest opportunity after the problem is resolved.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 Data Object Broker task.This message is the standard acknowledgement that the command is valid when no more specific reply exists. Parameter assignment has completed successfully.No action usually required. If the command triggers an action other than parameter assignment, check for subsequent responses that are issued from the task which actually performs the request.This message indicates that an invalid post code has been received by the Data Object Broker's operational support task and cannot be processed.This is an internal processing error and should be reported to TIBCO Support.This message is issued to record the processing of a command initiated by a timed event.Example MODIFY jobname,QUIESCEThis prevents any new user logons to Object Service Broker and helps existing work drain out of the system. Setting the QUIESCE state helps prepare for an Object Service Broker system shutdown.An Object Service Broker SHUTDOWN command may be issued, or normal operation can continue by issuing the command:Example MODIFY jobname,RESUMEExample MODIFY jobname,RESUMEThe flag for the QUIESCE state that occurred in Object Service Broker was reset.The command that displays the QUIESCE flag setting is:Example F jobname,JOURNALSTATUSInvestigate cases, other than during a shutdown, where Object Service Broker enters a QUIESCE state.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.Services 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 Data Object Broker's job log to determine the reason for the failure. Terminate and restart the Data Object Broker at the earliest opportunity after the problem is resolved.LENGTH OF SPECIFIED USER ID IS OUT OF RANGE FOR THE CANCEL OR FORCEUSER COMMANDA CANCELUSER or FORCEUSER 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 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 Data Object Broker'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.________ SERVICES SUSPENDED - RESTART LIMIT EXCEEDEDThe operations support service indicated in the message could not be recovered after a failure. These services are disabled until the Data Object Broker is restarted.Review the Data Object Broker's job log to determine the reason for the failure and report this problem to TIBCO Support.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)The indicated command contains characters that are not alphabetic. The command is rejected.Verify the spelling of the command. Refer to the Installation and Operations manual if necessary.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. For example, SNAPOVERRIDE, SNAPOVER, or SNAPO are all accepted. Excessive truncation results in abbreviations that can be one of several commands. For example, SNAP might be any one of SNAPCLASS, SNAPREMOTE, SNAPQUERY, SNAPOVERRIDE, or SNAPVOLSER.Spell the parameter keyword name more fully, or completely. Generally, 5 characters are adequate to achieve uniqueness. (TRACEID and TRACEOFF are exceptions). 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.COMMAND NOT PROCESSED, COULD NOT OBTAIN BUFFERThe Data Object Broker 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 Data Object Broker and terminate it at your earliest convenience. Notify TIBCO Support.COULD NOT OBTAIN WORK BUFFER FOR TIMER COMMANDThe Data Object Broker was not able to obtain the work area needed to process an the indicated timed service. This is usually a temporary situation and should be resolved almost immediately.If possible enter the command from the operator console. If the problem persists, obtain a dump of the Data Object Broker and terminate it at your earliest convenience. Notify TIBCO Support.xxxxxxxx PARM NOT DYNAMICALLY MODIFIABLExxxxxxxx parameter is only modifiable at STARTUPA 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 CHARACTERSThe 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/DSNAMEThe 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 value assigned to the keyword is too big or too small.Reenter the command with an acceptable value. Refer to the Installation and Operations manual if necessary._____________ ALREADY ASSIGNED - CANNOT MODIFYThe specified parameter was previously assigned a value. Further changes are not permitted. The MODIFY command for this parameter is provided to permit assignment only if the parameter was omitted from the initialization parameters.This parameter is normally specified as a Data Object Broker Initialization parameter. Changes are effective at the next Data Object Broker startup._____________ REJECTED, SHUTDOWN IN PROGRESSThe specified request was rejected because Object Service Broker had already accepted a shutdown request.Object Service Broker is coming down -- no action required.The value of the parameter indicated in the variable portion of the message text is not changed as requested. Refer to any preceding messages for the cause of the failure.Correct the request as indicated by the accompanying messages and resubmit the request.JOURNAL ___ CANNOT SUPPORT CHPAGELIMIT OF ____A request has been made to increase the value of the CHPAGELIMIT parameter; however, while validating this request, the Data Object Broker determined that there was not sufficient space in the Journal data set indicated in the message to support this change. The request is rejected.Select a lower value and retry the request or reallocate the failing Journal data set to a size which will support this request and reissue the request.REDO LOG CANNOT SUPPORT CHTRANLIMIT OF ____A request has been made to increase the value of the CHTRANLIMIT parameter; however, while validating this request, the Data Object Broker determined that there was not sufficient space in the REDOLOG data set indicated in the message to support this change. The request is rejected.Select a lower value and retry the request or reallocate the REDOLOG data set to a size which will support this request and reissue the request.This message provides a timestamp in the SYSLOG.CHPAGELIMIT OF ___ EXCEEDS 15% OF RESIDENT PAGESWhile validating a request to increase the value of the CHPAGELIMIT parameter, the Data Object Broker determined that the new value would exceed the maximum allowed based on the size of the Resident Page Pool. The request is rejected.Select a lower new value for CHPAGELIMIT and reissue the request.CHECKPOINT MAXIMUM PAGES = ______, TRANSACTIONS = ______This message is issued as confirmation of the new values set by a request to modify either the CHPAGELIMIT parameter or the CHTRANLIMIT parameter.TASK STATUS BUSY-TIME TCB-SEC EVENTS MSGS INFLT M-CONThis is the heading line for information displayed in response to the Object Service Broker Data Object Broker Status command:Example F jobname,CRSTATUSNo action is required. Refer also to the explanations for messages S6BKP046I and S6BKP047I.These lines display information in response to the Object Service Broker Data Object Broker Status command:Example F jobname,CRSTATUS.One status line appears for the Data Object Broker main task and attached subtasks. During routine operation these are numbers 0-4 and 6. If issued while a shutdown is in progress, any task which has properly terminated is absent.Subtasks are most commonly in READY status; they go into ACTIVE status when handling a unit of work and return to READY state when complete. Busy time and TCB time are displayed for each. CRSTATUS always shows Task 6 as ACTIVE because it is actively generating the CRSTATUS display.The presence of one or more asterisks between BUSY MM:SS and TCB TIME identifies a situation where the TCB has been active nonstop processing events - A task has been active in excess of one second of clock time (*) or over 10 seconds (**). In such cases the TCB SEC amount shown may be less than the actual current value. A problem may have occurred in the TCB.If any task is flagged with two asterisks (**), investigation is required. Start the Object Service Broker ADMINISTRATOR clist check system activity (option s monitoring), user activity and usage statistics. Contact TIBCO Support if a system problem is detected. Otherwise, no action is required. Refer to explanations for messages S6BKP045I and S6BKP047I.This is the final summary line for information displayed in response to the Data Object Broker Status command:Example F jobname,CRSTATUSData Object Broker Address Space totals are shown. In general the TCB time value reported on this line will be greater than but close to the sum of the individual task TCB SEC values.No action required. Refer also to explanations for messages KP045I and KP047I.These are the headings for data displayed in response to the command:Example F jobname,DBSEGMENTSTATUSOne status line appears for each database segment defined in the DBDLIB. The first letter is the status:This informational message provides the display under the S6BKP050 headings:
• A (a) can be O for online or F for offline (if offline, Pages, Used, Read, and Writes are not displayed)
• ID (num) is the segment number as specified in the DBDLIB
• NAME (name) is the name of the segment as specified in the DBDLIB
• MODE (mode) is the processing mode (can be R/W -- read/write, R -- read only, and -S -- system segment)
• JRN (jrn) indicates whether journaling is active for the segment (yes or no)
• PAGES (pages) is the number of pages in the segment
• USED (used) is the number of used pages in the segment
• READ (read) is the number of physical page reads against the segment
• WRITES (writes) is the number of physical pages written to the segmentDBSEGMENT ________ IS A 'SYSTEM' SEGMENT - REQUEST DENIEDYou entered one of the following commands:Example F jobname,DBONLINE=segment_nameagainst a segment which has been defined in the DBGEN as required by the system (or segment 0 which is required by definition). The request is rejected.Do not attempt to take a required segment offline while Object Service Broker is running. Any batch maintenance of these segments requires that the Object Service Broker system be shut down.You entered one of the following commands:Example F jobname,DBOFFLINE=identifierExample F jobname,DBONLINE=identifier.To see the names and numbers of the segments that are available, enter this command:Example F jobname,DBSEGMENTSTATUSExample F jobname,DBONLINE=identifierDBSEGMENT ________ IS ALREADY OFFLINEExample F jobname,DBOFFLINE=identifierDBSEGMENT ________ VARY ALREADY ACTIVE - REQUEST DENIEDThe DBONLINE or DBOFFLINE command you entered was rejected because there was already another DBONLINE or DBOFFLINE command being processed for the requested segment.Wait for the previous DBONLINE or DBOFFLINE command to complete, and then reenter your request if needed.DBSEGMENT ________ IS ONLINE - REQUEST DENIEDAn operator initiated request to disable Journaling for the segment identified in the message was denied as the segment was still online to the Data Object Broker.Take the desired segment offline via the DBOFFLINE command, and reissue the command to disable journaling for the segment.When Object Service Broker execution crosses the midnight boundary, all segments are checked to ensure that the space utilization has not exceeded the 80% threshold. This message is issued once for each segment that has exceeded the threshold.It is recommended that you increase the number of free pages available either by cleaning up or moving existing tables, or by increasing the size of the data sets within the segment.Example F jobname,JOURNALSTATUSMessages S6BKP060I and S6BKP061I are headings and data in response.Normally, one of the Journals is ACTIVE, the other is READY, and all flags are N. When a Journal becomes full, its status becomes OFFLINE or DEFER and the BKUP and DEFR flags are set to Yes. When the corresponding Journal spin job completes successfully, the BKUP and DEFR flags are reset, and the OFFLINE Journal becomes READY.The PEND flag is set to Yes by the commands:Example SPINSUBMIT=Checkpoint SPINSUBMIT=ImmediateExample SPINSUBMIT=NotnowThe QUIESCE flag is set to Yes during an Object Service Broker Shutdown. It may also be set to Yes if a Journal fills and there is no READY alternate Journal. In such a case, steps must be taken to resolve the Journal situation and the QUIESCE state can then be ended using:Example F jobname,RESUMEUsually no action is required. Correct detected Journal problems as necessary.JOURNALLING ALREADY ________ FOR SEGMENT ________An operator initiated request to modify the Journaling status for the segment identified in the message was denied since the Journaling status for the segment was already in the requested state.Reissue the command specifying the correct Journaling status.JOURNALLING ________ FOR SEGMENT ________This message is issued to confirm a change in the Journaling status for the segment shown in the message text.Example F jobname,USERMAX=######## is a one to four digit maximum user count. The message was issued because #### exceeded the MAXUSERS value in effect when Object Service Broker was started. This value can be adjusted but not increased beyond the initial value until the next time that Object Service Broker is restarted.Example F jobname,USERLISTS6BKP065I and S6BKP066I are headings and data in response. They are followed by summary messages S6BKP067I and S6BKP068I. If no Object Service Broker users are logged on, only S6BKP067I and S6BKP068I are issued.Object Service Broker connections are identified by their userid. The format of the display is ctuuuuuuuu, where:If the trace indicator is "+", it indicates the connection is currently being traced. A blank or "-" has no significance other than a separator.
• D - DBMS Server connection or Outbound Peer (HRN)
• L - Connection that is in the process of logging onYou issued one of the following commandsExample . F jobname,USERLISTExample . F jobname,USERS6BKP067I and S6BKP068I are headings and data in response. The count of users, DBMS gateways, batch jobs, and operator interface users is provided, as well as the number of available slots.JOURNALLING DISABLED BY INITIALIZATION PARAMETERThis message is issued in response to an operator request to display the status of the Data Object Broker's JOURNAL data sets. Status cannot be displayed as journaling was disabled at initialization by the JOURNALS=NO directive in the initialization parameters.You issued the following command:Example F jobname,GTFSTATUSS6BKP070I and S6BKP071I are headings and data in response to the command. The current settings of the various tracing controls are displayed.This message provides the data display for message S6BKP070I.REQUEST DENIED - CANNOT CHANGE MODE FOR SEGMENT 000An operator request was made to change the base segment's recording mode to read-only. This segment MUST remain in read/write mode. The request is rejected.An operator request has been received to change the recording mode of the indicated segment; however, the Data Object Broker found that the segment was already set to the requested mode.A CANCELUSER or STOPSERVER 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.Upon completion of external command processing (e.g., from S6BTLCMD), the work buffer used to carry the command could not be released.CANCEL DENIED - LOGOFF INITIATED AT ________ ON _________, WAITING FOR___________A request was received by the Data Object Broker to cancel a specified user session that is currently being terminated. The request cannot be fulfilled because the processing for termination has already partially completed. The connection has been waiting for a response from the displayed date and time from the identified external resource.CANCEL DENIED - USER LOGOFF DEFERREDExample F jobname,CANCELUSER=useridThe specified user is in deferred logoff status. The user's logoff cannot proceed until a coordinated external resource update happens. No action is taken.If unable to resolve a problem with a user hung up in deferred logoff status, then contact TIBCO Support.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.CANCEL DENIED - DBMS SERVER, USE STOPSERVERExample F jobname,CANCELUSER=server_idThe ID specified is a DBMS gateway. No action is taken.Use the STOPSERVER command to shut down a DBMS gateway.JOURNAL SPIN FLAG ALREADY IN REQUESTED STATEExample F jobname,SPINENABLE=YES or NOThe spin flag is already set to whatever you requested. No action is taken.JOURNAL SPIN FLAG RESET ONLY - NO OFFLINE JOURNALExample F jobname,SPINENABLE=YESNo Journal was offline; therefore, no Journal was reopened. Probably, a previous MODIFY command forced SPIN deferral for maintenance purposes.No action is required. You may want to display the current Journal status with the command:Example F jobname,JOURNALSTATUSUNEXPECTED USER ID FOUND IN SPECIFIED COMMAREAA cancel user request was issued from the S6BTLADM utility. The buffer identified as containing the user information is invalid.Retry the cancel request. If the error recurs, contact TIBCO Support.CHECKPOINT REQUEST TERMINATED - NO PENDING UPDATESAn operator has entered the CHECKPOINT command to flush the pending changes to the database. There were no updates pending, so the request is ignored.REQUEST DENIED - NO ALTERNATE JOURNALS AVAILABLE FOR RECORDINGAn attempt was made to spin the last available journal via the SPINSUBMIT operator command. The request is rejected.Determine the reason that the alternate journal is not available. Correct the situation and reissue the command.REQUEST DENIED - JOURNAL ___ IS NOT CONFIGUREDAn operator request to vary the indicated journal data set has been rejected as the journal data set was not defined in the DBGEN.If more journal data sets are required, modify the journals definition in the DBGEN so that more are available the next time the Data Object Broker is started.REQUEST DENIED - JOURNAL ___IS ALREADYAn operator request has been received to vary the indicated journal data set; however, the Data Object Broker found that the journal was already set to the requested state.REQUEST DENIED - CANNOT CHANGE STATUS OF ACTIVE JOURNALAn attempt has been made to vary offline the active journal data set. This request is rejected.If the active journal data set must be taken offline, issue a journal spin command. Once the spin completes, the journal can be safely taken offline.REQUEST DENIED - JOURNALLING SERVICES ARE NOT AVAILABLEAn operator command has been entered to manipulate one or more journal data sets; however, JOURNALS=NO was specified in the Data Object Broker's initialization parameters. The request is ignored.An operator initiated vary request for the indicated journal data set has been successfully received by the Data Object Broker.This message displays the name of a user session that has been terminated because Object Service Broker is being shut down.VARY REQUEST ALREADY ACTIVE FOR JOURNAL ___ - REQUEST DENIEDA vary request has been received for the indicated journal data set, however, the Data Object Broker is already processing a vary request for this journal.Wait for the current vary request to complete and then reenter your request. If the current request does not complete, take a dump of the Data Object Broker, and restart at your earliest convenience. Contact TIBCO Support.Example F jobname,SHUTDOWNA request has been issued against the Data Object Broker which acts upon SPIN JCL; however, the Data Object Broker was initialized to use STC for spin jobs. This request is denied.If the intent of the request was to modify the SPIN JCL, then simply modifying the STC PROC is all that is necessary. Otherwise, this request is illogical for the environment, and subsequently no further action is required.SPIN LOAD REQUEST FOR JOURNAL ___ ACCEPTEDThis message is issued as an acknowledgement of a SPINLOAD request for the indicated Journal's SPIN JCL.SPECIFIED PEER NOT DEFINED, STARTPEER COMMAND REJECTEDThe peer you specified is not defined.Check the spelling, or check the peer definitions with S6BTLADM.SPECIFIED PEER IS ALREADY ATTEMPTING CONNECTIONS, STARTPEER COMMAND REJECTEDThe Peer connection is currently in progress. When processing of the Peer completes, all required connections that are viable should have been established.Retry the command at a later time if required.LOCKTRACE (ON/OFF/MARK POINT), ON TABLE ________, ON USER ______This informational message is presented to show the lock trace characteristics for the trace just activated.INVALID LOCKTRACE PARAMETER; "ON", "OFF", "T=...", "U=..." OR "*" ACCEPTABLEThis warning identifies the acceptable parameters for a locktrace request.Reenter the locktrace request with the correct parameter values.LOCKTRACE "T=" OR "U=" REQUIRE TABLE NAME OR USER IDThe LOCKTRACE request was invalid because of missing information.Reenter the request with all required information."FORCEUSER" COMMAND REPLACED WITH "CANCELUSER" FOR USER ________, NO PREVIOUS CANCELBefore a FORCEUSER command can be processed a CANCELUSER must already be active for the specified user. The FORCEUSER is intended to provide a last resort method terminating a hung user, before it is attempted a CANCELUSER must be attempted.The command is downgraded to a CANCELUSER and processed.FORCEUSER COMMAND ISSUED AGAINST USER ________This message is produced to ensure there is a record of the use of the FORCEUSER command.SHUTDOWN COMMAND ACCEPTED, DEFERRED DUE TO CURRENT PROCESSINGThe shutdown command has been accepted. There is currently work outstanding that must be completed before the shutdown can proceed. In particular, there is a long running transaction such as a table clear or secondary index build or delete inflight. When the long running transaction completes, the shutdown request will automatically continue and the Data Object Broker will terminate.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 commnum from message S6BKP112I.USERID TERMID JOBNAME TYPE COMMNUMThese are the headings for message S6BKP112I.S6BKP111I shows headings for the data rows in S6BKP112I; the data in S6BKP112I is used to determine the different userid/termids.Determine which commnum to use when the console command is reissued.This message displays the count of duplicate entries.REPEAT COMMAND WITH "command = userid;commnum"The console command could not determine which duplicate entry to act on. S6BKP112I lists the commnum of all duplicates.Reissue the console command with ";commnum" at the end of the command, where the commnum is from the preceding S6BKP112I messages.The console command was reissued but no data was detected beyond ";".Reissue the command with the commnum.COMMNUM NOT NUMERIC, COMMAND REJECTEDThe console command after the ";" was not numeric. The commnum is a numeric value.Reenter the console command with a numeric value for the commnum.COMMNUM TOO LARGE, COMMAND REJECTEDThe commnum entered was greater than the highest allocated commnum.Check the value of the commnum and reenter the command.SPECIFIED COMMAREA NUMBER OUT OF RANGE, REQUEST REJECTEDA CANCELUSER request was issued with an explicate commarea number, the supplied commarea number is out of range.Correct the CANCELUSER request and resubmit.SWEEPLIMIT FORMAT INVALID; EXPECTED "SWEEPLIMIT=(LIMIT,USERID)"When attempting to set a Sweep Limit for a specific user, you used an invalid command format.SWEEPLIMIT REQUEST COMMAREA NUMBER CONTAINS INVALID NUMERIC CHARACTERSWhen entering a command to set a sweep limit, you used invalid characters in the numeric portion of the command.SWEEPLIMIT REQUEST SPECIFIED A COMMAREA NUMBER THAT IS OUT OF RANGEWhen entering a Sweep Limit, you specified an out-of-range value.Refer to the Object Service Broker documentation and re-enter the command with a valid limit.SWEEPLIMIT REQUEST IDENTIFIES A USERID AND COMMAREA NUMBER THAT DO NOT MATCHIn your Sweep Limit command, either the userid or the relative connection number are in error.Re-enter the command with the correct userid and COMMAREA number.SWEEPLIMIT REQUEST LIMIT CONTAINS INVALID NUMERIC CHARACTERSThe Sweep Limit specified in the command has invalid numeric characters.Re-enter the command with a valid Sweep Limit value.SWEEPACTION FORMAT INVALID; EXPECTED "SWEEPACTION=(ACTION,USERID)"The specified action to be invoked when a user exceeds the Sweep Limit threshold is invalid.Refer to the Object Service Broker documentation for valid actions and re-enter the command.SWEEPACTION REQUEST COMMAREA NUMBER CONTAINS INVALID NUMERIC CHARACTERSWhen specifying the action to be invoked when a Sweep Limit Threshold is exceeded, you entered a COMMAREA number that contains invalid numeric characters.Re-enter the command with a valid COMMAREA number.SWEEPACTION REQUEST SPECIFIED AN COMMAREA NUMBER THAT IS OUT OF RANGEIn your attempt to specify the action to be taken when the Sweep Limit threshold is exceeded, the COMMAREA number specified is not valid. It exceeds the number of the pool buffers available.Re-enter the command with a correct COMMAREA number.SWEEPACTION REQUEST IDENTIFIES A USERID AND COMMAREA NUMBER THAT DO NOT MATCHThe COMMAREA number specified in the command identifies a connection for a userid other than the one supplied.Re-enter the command with the correct userid and COMMAREA number.SWEEPACTION SPECIFIED USERID COULD NOT BE LOCATEDThe userid specified in the SWEEPACTION command could not be located on the Data Object Broker.Verify the userid and re-enter the command.SERVER COMMAND - PROCESSING BUFFER NOT CURRENTLY AVAILABLE, RETRYA buffer to retain the gateway command control block could not be obtained from the system.This is most likely a temporary situation, retry the gateway command.SERVER COMMAND - SERVER TYPE MUST BE A 3 CHARACTER VALUE FOLLOWED BY A COMMAThe system was not able to identify the desired resource type to process because the message format was incorrect.Correct the message format and reissue the request.SERVER COMMAND - SERVER TYPE WILD-CARD MUST BE "*," OR "***,"The gateway command was issued with the gateway type value with wildcards. However the format of the wildcard is invalid. The type value must either be completely specified or completely wildcards.Correct the gateway command request and reissue it.SERVER COMMAND - FORMAT "TYPE,GROUP,COMMAND" ONE OR MORE SUB-PARAMETERS MISSING.The format of the gateway command was incorrect.SERVER COMMAND - SERVER GROUP MUST BE 1 TO 8 CHARACTERS FOLLOWED BY A COMMAWhen extracting the group name from the input command, either the group name was too long or a comma was missing.SERVER COMMAND - SERVER GROUP WILD-CARD VALUE DOES NOT ACCEPT EMBEDDED "*"The group ID was entered using a * to indicate a wildcard the * must be followed immediately by a "," to indicate the end of the group name.SERVER COMMAND - SERVER COMMAND IS TOO LONG TO PROCESS, LIMITED TO 48 CHARACTERSThe longest gateway command that can be processed is 48 bytes. The request exceeds this limit. If this restriction causes a problem, contact TIBCO Support.SWEEPACTION COMMAND ACTION INVALID; USE LOG,NOLOG,SMF,NOSMF,DUMP OR NODUMPThe action specified in a SWEEPACTION command is invalid. The message identifies the acceptable actions.SWEEPACTION REQUEST SET ACTION TO SMF, SMF RECORD IS NOT ACTIVEThe action specified in the SWEEPACTION command specifies an SMF record to be cut when the threshold is exceeded. The current Data Object Broker environment is not producing any SMF records.Either select a different action or set the SMFRECORD parameter to start SMF logging and re-enter the command.This message is provided as feedback of the completion of a timed services maintenance request.TIMER INTERVAL GREATER THAN 1 DAY, ENTRY DISABLEDA timed services entry has been encountered which specifies an interval greater than 1 day (1440). This entry is disabled, and Data Object Broker processing continues normally.This is an internal error condition. Contact TIBCO Support for further assistance.PROCESSING BUFFER NOT AVAILABLE TO PROCESS ____________A buffer was not available to process the indicated timed services request. The request is ignored.Contact TIBCO Support for further assistance.COMMAND % REJECTED; SYSTEM IS FROZEN: %Only certain commands may be issued while the system is frozen.Wait until the system is unfrozen and reissue the command.This message is issued as a result of a Status operator command. The system status is ACTIVE, FROZEN, FREEZING, or UNFREEZING.LONG RUNNING TASK ACTIVE id #=num TYPE=_ COMM=comm-type SOURCE= xxxxThis message is issued for each long running task active at the time of a Status operator command. See message S6BKC016 for the meaning of the fields displayed in this message.This message appears as a result of one of the following actions:
• You issued a Freeze command and you do not have a valid license for this feature
• You issued a Freeze command while the system was already frozen
• You issued an Unfreeze command while the system was not frozen.Reissue the command when the system state is the appropriate one.This message is issued as a result of a STATUS command on a system where BWO support is licensed and enabled.This message is issued as a result of a BWOSTATUS command on a system that is not enabled for BWO support.BWO support may be enabled using the BWO Data Object Parameter if required.COMMAND ______________ REJECTED; SYSTEM IN SECONDARY MODEThe system is in secondary mode and a command that is only valid when the system is in primary mode has been entered.A switch command was for one of the following reasons:
• FORCE OR ALLOW REQUIRED: The switch command requires either the FORCE or ALLOW option to complete successfully.
• INVALID MEMBER NAME: The member name specified is not a member of the current XCF group
• XCF NOT ENABLED: The Data Object Broker is not running in XCF mode, the Switch command is not supported.
• SWITCH IN PROGRESS: A SWITCH is already in progress for this Data Object Broker
• LRT IN PROGRESS: A Long Running Transaction, such as a Clear Table, is in progress. The SWITCH command is ignored. Retry the SWITCH command after the Long Running Transaction has completed.
• WORK BUFFER UNAVAILABLE: A work buffer was not available to schedule the SWITCH. Retry the SWITCH later.Correct the Switch command and re-issue it.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |