![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
SPACE FOR DEFINITION TABLE IS NOT AVAILABLEGETMAIN failed to get internal space for the table to return the definition of the Object Service Broker table.The attempt to open the control card file for input failed.See the job log for additional information.DEFINITION DOES NOT IDENTIFY A NEW SECONDARYYou did not identify a new secondary index. The secondary indexes identified from the cards already exist.INTERNAL TABLE WORKING SPACE NOT AVAILABLEGETMAIN failed to get space to retain internal tables.CONTROL CARD TYPE CODE IS INVALID,(EXPECTED H OR S)The control card type (in column 1) contains an invalid code. Only H or S are supported.See the card image with the message and correct the control cards.OUTPUT DEFINITION CARDS ARE OUT OF SEQUENCEThe sequence numbers (column 3-5) for the output definition cards are not properly sorted.Reorganize the Object Service Broker output definition cards or correct the sequence numbers.OUTPUT DEFINITION CARD HAS INVALID ENTRY TYPE (R,P OR F)The entry type code (column 7) is invalid for an Object Service Broker output definition. Only R (record), P (parameter), and F (field) are acceptable.DEFINITION TABLE OVERFLOW, INCREASE MAX FIELDS ON SPECThe internal table that retains the Object Service Broker table definition information has overflowed.Increase the maximum number of fields on the specification card. Refer to the online Utilities documentation for details.OUTPUT DEFINITION SEMANTIC TYPE/SYNTAX NOT SUPPORTEDThe semantic type (column 46) and syntax code (column 48) do not form a valid combination.Change either the semantic type or the syntax to form a valid combination. Refer to the Processing manual for a list of valid combinations or check the online definition.OUTPUT DEFINITION CARD FIELD LENGTH BLANK/OUT OF RANGEThe field length (column 50-52) on the output definition card is either blank or the value is outside the range for the given syntax or key type. A secondary index is constrained to 127 bytes.Enter a field length that is within the range for the syntax or key type required. Check the online definition.OUTPUT DEFINITION CARD DECIMAL POSITION IS OUT OF RANGEThe decimal position (column 54-55) specified for the Object Service Broker parameter field is outside the range of the field length.Enter a decimal position that is within the range for the field length.OUTPUT DEFINITION CARD KEY TYPE NOT SUPPORTED (" ",P/S)The Object Service Broker key type (column 57) is invalid. Only a blank, P (primary key), and S (secondary key) are supported.Enter a P, S, or a blank for the output Object Service Broker key type.This field on the control data set must be either blank or a number equal to or less than the actual total number of units comprising the dynamic unit name selected.The field length for a field with Unicode syntax must be even.Correct the S6BBRSIX CNTRL input cards and resubmit the job.UNICODE SYNTAX NOT SUPPORTED FOR PARMS OR KEYSThe definition cards provided to the S6BBRSIX Offline Batch Utility indicate that a field with a Unicode syntax is to be used as a parameter or key (primary or secondary). This is not supported.Correct the input control cards and resubmit the job.SPECIFICATION CARD MAXIMUM PROCESS RECORDS NOT NUMERICThe maximum record field (column 15-29) contains invalid numerics.Correct the value and ensure that it is right aligned.SPECIFICATION CARD MAXIMUM NUMBER OF FIELD NOT NUMERICThe maximum number of fields value (column 31-33) contains invalid numeric values.Correct the value and ensure that it is right aligned.SPECIFICATION CARD MAXIMUM BLOCK SIZE IS NOT NUMERICThe maximum block size field (column 44-48) contains invalid numerics.Correct the value and ensure that it is right aligned.SPACE FOR INDEX CONTROL STACK NOT AVAILABLEGETMAIN failed to get space to retain the index-level stack.REQUESTED SECONDARY INDEX ALREADY EXISTSA definition key type was specified as S for a secondary index that already existed. Only specify S for new secondary indexes.LOAD TABLE COULD NOT BE LOCATED ON CONTROL PAGEThe requested table name is greater than all the TDS tables currently in the TIBCO(r) Object Service Broker data store.Check the spelling of the table name and check that the correct segment was processed.LOAD TABLE COULD NOT BE LOCATED ON TABLE INDEXThe Resident Table Index entry for the requested table cannot be located.SPACE NOT AVAILABLE FOR SECONDARY INDEX TABLEGETMAIN failed to get space to retain the TIBCO(r) Object Service Broker secondary index table page.A secondary index table page (T) exists but contains no entries.DYNAMIC ALLOCATION OF TEMPORARY FILE FAILEDS6BBRSIX detected a failure when it attempted to allocate a temporary work file.Check the unit on the specification card, and check the job log for additional information.SPACE NOT AVAILABLE FOR TEMPORARY FILE DCB DEFINITIONWORK FILE USED TO RETAIN CAPTURED DATA FAILED TO OPENA sequential file is used to retain data pointers captured from the Object Service Broker Pagestore. The file intended to retain this data failed to open.See the job log for additional information.INVALID PAGE TYPE DETECTED WHEN EXTRACTING DATAAn unexpected page type was detected during the attempt to capture information required for the secondary index build.Run S6BBRPTR to verify segment integrity.SPECIFIED SYNTAX CODE INVALID FOR CAPTURE PROCESSINGYou specified an invalid syntax code on a parameter or field required by extract processing.RESIDENT TABLE INDEX OFFSET CALCULATION ERROR DETECTEDA Resident Table Index internal control error is detected.SORT TYPE CODE NOT FOUND FOR SECONDARY KEY SYNTAX CODEThe syntax of a parameter, primary key field, or secondary key field cannot be translated for the sort parameter list.The routine used to sort the extracted data into the appropriate order for secondary index creation failed.See the job log for additional information.INPUT OPEN ERROR DETECTED ON INDEX TEMPORARY FILEThe file used to retain indexing information failed to open during the index construction phase of processing.See the job log for additional information.INDEX CONTROL TABLE OVERFLOWED-TOO MANY INDEXING LEVELSThe batch secondary index build process was designed to support 5 levels of indexing. This limit has been exceeded.GROUP INDEX CAPTURE FILE FAILED TO OPEN FOR OUTPUTThe work file that retains group index (table instance) information failed to open.See the job log for additional information.An attempt has been made to create more secondary indexes than the Object Service Broker system supports.Consult your System Administrator for the maximum number of secondary indexes allowed for the release of Object Service Broker you are using.The utility is unable to process table data obtained from the Pagestore.A possible cause of this problem is the use of out-of-date control cards to attempt to build the secondary index after adding extra fields to the underlying table.Verify your control cards. If they are correct, contact TIBCO Support for assistance in resolving the issue.Secondary indexes cannot contain numeric nulls.It is not possible to create a secondary index for fields which have NULL values and are defined as either binary or packed decimal syntax.BROWSE MODE - REQUEST VALIDATION COMPLETEDYou requested the BROWSE=Y PARM option which results in termination after the validation of the control file entriesThe program was unable to read a page from the segment.Ensure the correct number of data sets for the correct segment were opened at startup. If this seems correct then take a backup/pointercheck of the segment and rerun the program and capture a dump. Contact support and supply output from all three programs and the dump.The table name specified in the control file does not have an entry in the requested segment RTIX.Check the table name and the segment number. If both are correct, the table must be defined and contain data before a secondary index can be built.The control file does not indicate any secondary index fieldsCheck to make sure the correct control file is being used, if it is then modify the control file to indicate which field(s) are to be used as secondaries.An unexpected event occurred that the utility cannot handle.The detail associated with this message is essential to identify and resolve the problem. Print the audit report and pass it on to TIBCO Support.The detail associated with this message is essential to identify and resolve the problem. Print the audit report and pass to support personnel.EXPECTED PAGE NOT FOUND ON PAGESTOREThe page retrieved is not the page expected by the utility.Print the audit report and pass to support personnel.OLD GROUP INDEX CAPTURE RECORD OUTPUT FAILUREA work file has run out of space and the job is aborted.Provide more space in the current or selected work directory and retry.INDEX CAPTURE WORK FILE FAILED TO OPEN FOR OUTPUTThe utility needs to build a work file. A path (-W) to the directory if specified will result in the utility trying to use that directory for the work file otherwise it will attempt to build the work file in the current directory.Make sure you have the necessary permissions in the directory you have specified (or defaulted).The Index Work File is empty; no index information was recovered for the table.If the table contains no data, a secondary index cannot be built. If the table contains data print the audit file and pass to support personnel.The Pagestore segment is full; increase the space available and try again.REQUIRED PAGE COULD NOT BE RETRIEVEDThe utility was unable to retrieve a previously retrieved page.RESIDENT TABLE INDEX UPDATE PREPARATION FAILEDThe utility was unable to locate previously retrieved information on the RTIX.A write-to-operator message is generated to indicate that the file used to retain the execution report (audit trail) cannot be opened.See the job log for additional information.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |