![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
This message notifies you that the S6BBRTL1 exit is active.This message notifies you that the S6BBRTL2 exit is active.This message notifies you that the S6BBRTL3 exit is active.PRIMARY KEY VALUE WILL BE GENERATED (IDGEN)This message notifies you that the primary key will be generated (IDgen).ERROR ATTEMPTING INPUT FIELD FORMAT CONVERSIONThe conversion routine detected an error during the conversion of the input record to fixed length format. The actual conversion error message will immediately precede this message. The processing continues with the next record.A table instance was rejected. The rejected table instance contained count1 records starting at input record count2.See the previous audit message and correct the previous error condition.DUPLICATE TABLE INSTANCE, # REJECTS SEE BELOWRecords have been rejected as they belong to a previously complete instance.The number of records rejected are shown below this message.TABLE NOT UPDATED; NO INPUT RECORDS ACCEPTABLENotification that the Object Service Broker Pagestore was not updated because none of the input records were accepted.See the messages in the audit trail to determine why all the records were rejected.When loading a parameterized table there must always be a value associated with each parameter, either from an input file field or from static values.The primary key of an input record is a duplicate.The primary keys must be sorted properly within the table instances (if applicable).Either manually add the entries that are out of sequence, or delete the tree, sort again, and run again.RECORD SHORTER THAN MINIMUM LENGTHA zero data length record encountered.CONVERSION - INPUT FIELD CONTAINS BAD DATAThe field indicated contains data which does not conform to the specified format.The field indicated cannot be converted without possible data-integrity loss.CONVERSION - CONVERSION NOT POSSIBLEThe field indicated cannot be converted due to incompatible source/target syntax.Null primary key/parameter values are not permitted.Null numeric-syntax secondary keys are not permitted.Problem experienced opening the Control File.SPACE FOR DEFINITION TABLE IS NOT AVAILABLEGETMAIN for the internal table to hold input and output definitions failed.The required space is 88 multiplied by the maximum number of fields (50 is the default). Check with your data center manager for private extended storage limits (above the line storage).PRIMARY KEY MUST COME FROM INPUT OR BINARY 4 FOR IDGENThe primary key in Object Service Broker is not derived from an input field. To be considered for IDgen, it must be binary length 4.
• If you want an IDgen key, make the primary key binary length 4.
• If you want to generate a key yourself, define a dummy input field and use exit point 1 (S6BBRTL1). Refer to the Utilities manual for details on exits.SPECIFIED INPUT/OUTPUT SYNTAX CONVERSION TEST FAILEDWhen testing the conversion of the data field syntaxes, an error was detected.See accompanying message. Contact TIBCO Support if a syntax combination is required.SPACE NOT AVAILABLE IN WHICH TO BUILD THE ENTRYGETMAIN for internal work space for the compressed Object Service Broker entry failed.The requested memory was 2025 bytes. Contact your data center manager for private extended storage limits (above the line storage).SPACE NOT AVAILABLE TO RETAIN REQUIRED INDEXING DATAGETMAIN for internal index capture record work area failed. Requested space is the following added together:
• LOAD TABLE COULD NOT BE LOCATED ON CONTROL PAGEThe table to be loaded could not be located in the index of the Resident Table Index.
• Check the spelling of the table name on the Object Service Broker output definition card and ensure that the table type is TDS.
• Ensure that the table you are attempting to load is on the segment specified in the run time parameter.LOAD TABLE COULD NOT BE LOCATED ON TABLE INDEXThe Resident Table Index entry could not be found for the requested table.
• Check spelling on the output definition card and ensure the table type is TDS.
• Ensure that the table you are attempting to load is on the segment specified in the run time parameter.SPACE NOT AVAILABLE FOR INTERNAL INDEX CONTROL TABLESGETMAIN for internal index control stack failed. The requested space is 16 multiplied by 6 from the storage.Check with your data center manager for private extended storage limits (above the line storage).SPACE NOT AVAILABLE FOR REQUIRED PAGE BUFFERSGETMAIN for Object Service Broker page buffer space failed. The requested space is 4 KG multiplied by 6. Add 4 KB if there are parameters, and add 4 KB if there are secondary indexes.Check with your data center manager for private extended storage limits (above the line storage).EXPECTED SECONDARY INDEX ENTRY NOT FOUND ON SIT PAGEThe output definition cards specified a secondary index which was not defined within the Object Service Broker Pagestore.Either build the secondary index by using SIXBUILD processing online, or remove the S for the field in the Object Service Broker output definition card.INCORRECT SEGMENT ACTIVE FOR TABLE LOAD PROCESSINGThe table to be loaded is not on the base store with which the batch utility was started.Specify a run time parameter of "SEGMENT=nnnn", where nnnn is the segment number that contains the table to be loaded.The table to be loaded contains data and no parameters are associated with it. Only table instances can be added to an existing table. Data within a table instance cannot be added.Either remove the data from the table or use an Object Service Broker rule to load the new data.When a secondary index is built by using S6BBRSIX, the table definition is changed (online) to reflect the newly built secondary index. This message was issued because you tried to load the table again (by using S6BBRTBL) but did not change the definition control records to reflect the new secondary index.Recreate the load control records by using BATCHLOAD_CARDS or delete the secondary indexes by using SIXDELETE.Your user exit requested that this record be ignored.Record is ignored. Recreate the load control records by using BATCHLOAD_CARDS or delete the secondary indexes by using SIXDELETE.The UNIT COUNT specified on the control data set for multivolume work file support must be less than or equal to the actual number of units available for the unit group name specified.REQUESTED SECONDARIES DO NOT MATCH THOSE ALLOCATEDThe Secondary key field names identified on the Definition Control File do not match the field names of the allocated secondaries on the Pagestore.The report indicates the discrepancies; use the online tool BATCHLOAD_CARDS to generate an accurate Definition Control File.SECONDARIES ARE ALLOCATED BUT NONE REQUESTEDThere are secondary index fields defined for the table being loaded but no secondaries are defined in the definition control file.Use the online tool BATCHLOAD_CARDS to generate an up-to-date/ accurate Definition Control File for this table.CONTROL CARD TYPE CODE IS INVALID,(EXPECTED I,H,S OR V)The control card type (column 1) has an invalid code. Only I, H, S, or V are acceptable.The sequence numbers (column 3-5) for the input definition cards are not properly sorted.Reorganize the cards or correct the sequence numbers.INPUT DEFINITION CARD ENTRY TYPE CODE INVALID; R OR FThe entry type code (column 7) is invalid for an input definition. Only R (records) and F (field) are acceptable.INPUT DEFINITION CARD SYNTAX CODE IS NOT SUPPORTEDThe syntax code (column 48) defined for the input field is not supported.See the documentation on input definition cards for valid codes.INPUT DEFINITION CARD FIELD LENGTH BLANK/OUT OF RANGEThe field length (column 50-52) on the input definition card is either blank or the value is outside the range for the given syntax.Fill in a field length that is within the range for the syntax. See the documentation on input definitions for valid length ranges.INPUT DEFINITION CARD DECIMAL POSITION IS OUT OF RANGEThe decimal position (column 54-55) specified for the input field is outside the range of the field length.Change the decimal position to fall within the range of the field length.INPUT DEFINITION RECORD CARD HAS INVALID FILE TYPE (F-V)File type is either F (Fixed) or V (Variable). Default is F; no other value is acceptable.DEFINITION TABLE OVERFLOW; INCREASE MAX FIELDS ON SPECThe internal table that retains the input/output definition information has overflowed.Increase the maximum number of fields on the specification card. Refer to the online Utilities documentation for details.SPECIFICATION CARD MUST BE FIRST IN CONTROL CARD FILEIf included, the specification card must be the first card in the control card file.Put the specification card at the front of the control card file.MISSING INPUT DEFINITION - NUMERIC SECONDARYNumeric Secondary index field values cannot be null. No input field is defined cross-referencing to a table field defined as a secondary index, which means the table field value will be loaded as NULL.Remove the secondary index indicator or provide an input field which has significant data in every record or change the syntax of the target (table) field to a character syntax (C or V).A null-equivalent value is valid only when the input file field from which the data is being loaded to this output (table) field is either binary or packed decimal syntax. Columns 64-79 are ignored.OUTPUT DEFINITION CARDS ARE OUT OF SEQUENCEThe sequence numbers (column 3-5) for the output definition cards are not properly sorted.Reorganize Object Service Broker output definition cards or correct the sequence numbers.OUTPUT DEFINITION CARD HAS INVALID ENTRY TYPE (R,P/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 input/output 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. See 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.Enter a field length that is within the range for the syntax. 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 or 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 output Object Service Broker key type (column 57) is invalid. Only blank, P (primary key), and S (secondary key) are supported.Enter a P, an S, or a blank for the output Object Service Broker key type.Check documentation and correct the specification.Check documentation and correct the specification.The primary or secondary key length specified exceeds the maximum.Check documentation and correct the specification.The number of parameters defined exceeds the limit.Check documentation and correct the specification.The total parameter(s) length exceeds the limit.Check documentation and correct the specification.SPECIFICATION CARD MAXIMUM PROCESS RECORDS NOT NUMERICThe maximum records field (column 15-29) contains an invalid numerical value.Correct the value and ensure that it is right aligned.SPECIFICATION CARD MAXIMUM NUMBER OF FIELD NOT NUMERICThe maximum number of fields value in column 31-33 contains invalid numeric data.Correct the value and ensure that it is right aligned.SPECIFICATION CARD MAXIMUM BLOCK SIZE IS NOT NUMERICThe maximum block size field (in column 44-48) contains an invalid numeric value.Correct the value and ensure that it is right aligned.SPECIFICATION CARD SPACE USAGE VALUE IS NOT NUMERICThe percentage specified for one of the following is not numeric:
•
• Correct the value and ensure that it is right aligned.The null-equivalent value (in columns 64-79) is invalid; either the code is misspelled or the value is not numeric.VALUE CARD FIELD/PARAMETER NAME NOT FOUNDThe name specified (in column 3-18) cannot be matched with the output definition table.Check the spelling of the field name. Correct the Object Service Broker output definition name or the static value name.VALUE CARD FOR FIELD/PARAMETER DEFINITION AS INPUTA value card cannot be entered against a field or parameter which is referenced in the input file.
• Remove the static value card or cards for the given field or parameter.
• Remove the reference to the field in the input specification card.VALUE CARD FOR FIELD/PARAMETER ALREADY PROCESSEDA value card was entered for a field or parameter which has already been set.Check to ensure a continue indicator (column 20) is set, if a continuation is being attempted.VALUE CARD FOR NUMERIC FIELD/PARAMETER NOT NUMERICThe value card contains static text (column 22-71) for a numeric field or parameter (packed or binary), but the text contains non-numeric characters.VALUE CARD TEXT LENGTH IS INVALID FOR A NUMERIC ENTRYThe length of the numeric data in the value card text area is not valid (out of range 1-15 digits).VALUE CARD DECIMAL POSITION CONFLICTS WITH DEFINEDThe number of post decimal digits must match the definition of the field or parameter.Change the number of post decimal digits to match the definition of the field or parameter.INVALID OR NO CHARACTER SET TYPE SPECIFIEDThe character set code was found to be invalid.Specify a proper character set. Blank defaults to ENGL.There are too many Value Continuations for the field as defined. Remember that each Value Record holds 50 characters.Shorten the value for the field to the defined length of the field, and remove extraneous Value Records.VALUE CONTINUATION INVALID OR OUT OF SEQUENCEValue Continuation Column Entries must be consecutive and in ascending sequence if there are multiple records (more than 50 characters).The first record of a single field's "Value Records" must have 0 in its Continuation Column. If the value continues beyond 50 characters, the second "Value Record" (which is the first actual continuation) must have 1 in its Continuation Column; the third must have 2, and so on.Check documentation and your installation's date format.STATIC VALUE REJECTED DURING CONVERSIONThe static value associated with the field identified could not be converted to the semantic type/syntax of the target field.This error should have been trapped when the utility processed the Definition Control File - contact TIBCO Support and provide all relevant information: the value of the static value and the target field definition.When attempting to write a page to the current segment a failure occurred.Inspect the audit report for other messages which should indicate why the failure occurred. The table being loaded must be considered incomplete and the segment itself suspect. Contact TIBCO Support and supply all relevant documentation: the audit report, the core dump if produced.DYNAMIC ALLOCATION OF TEMPORARY FILE FAILEDA dynamic allocation request failed.Check the job log for an explanation and verify the dynamic symbolic unit name on the specification card.SPACE NOT AVAILABLE FOR TEMPORARY FILE DCB DEFINITIONThe GETMAIN to obtain storage (below the line) for the temporary file DCB failed.SPACE FOR INTERNAL FIXED FORMAT RECORD IS NOT AVAILABLEGETMAIN for internal work space for fixed format work record failed. Requested space is 2028 bytes.Check with your data center manager for private extended storage limits (above the line storage).ERROR DETECTED WHEN EVALUATING ACCESS METHOD OF INPUTThe JFCB of the input file is used to determine if the input file is sequential or VSAM access. The read JFCB failed.Check your JCL and the job log. If this information does not provide a solution, contact TIBCO Support.INPUT FILE FAILED TO OPEN USING SEQUENTIAL ACCESSThe input file was determined to be sequential and the open for the file failed.The input file was determined to have a format other than fixed or variable. The format is not supported.INPUT FILE FAILED TO OPEN USING VSAM ACCESS METHODThe input file was determined to be a VSAM data set. The open for the file failed.Check your JCL and the job log. A VSAM verify may be required.INDEX CAPTURE WORK FILE FAILED TO OPEN FOR OUTPUTThe work file used to capture indexing information failed to open for output.Check the dynamic symbolic unit and blocksize in the specification cards. Review the job log for further information.INPUT RECORD CONVERSION ERROR THRESHOLD EXCEEDEDThe number of conversion errors detected by the conversion routine exceeds an allowable limit.Verify the input file layout and check for the values rejected by the conversion routine.INVALID PAGE TYPE FOUND WHEN SEARCHING GROUP INDEXTREEA page type code detected when searching for existing table instances was not a group index or group index page type.Verify the Pagestore by using the S6BBRPTR utility. Contact TIBCO Support.***** PROCESSING TERMINATED, ALL INPUT REJECT ******None of the user input data was accepted. Processing ended.Correct the reported audit trail conditions that caused the input to be rejected.NO INPUT RECORDS READ, PROCESSING TERMINATEDNo input records have been found usable.During loading, a null value in the primary key or a secondary index was detected.** PLEASE CHECK INPUT FILE FORMAT SPECIFICATIONS **Refer to the explanation for S6BSV954W.Ensure that the input file is described correctly both in the Control File (-C) and on the command line (-m). If the requested process completed successfully, check that the table data is correctly loaded.There is a limit to the number of secondary index fields permitted in a table definition. This limit is used to determine the size of certain tables within the utility. One of these tables has overflowed.An internal program error occurred.Indicates that the load has completed successfully; the secondary index is complete and has been COMMITTED.The primary data has been loaded successfully and COMMITTED.If no secondaries are being built then the load has completed building the target table. If a secondary index build follows the primary build and it fails, the primary data is complete. After determining why the secondary build failed, use the Secondary Index Builder S6BBRSIX to build the missing secondary indexes.SORT SYNTAX CODE COULD NOT BE LOCATED FOR SYNTAXThe syntax code of the field or parameter cannot be converted to a code acceptable to the sort routine.GROUP INDEX CAPTURE FILE COULD NOT BE OPENED FOR OUTPUTThe work file used to retain table instance information cannot be opened for output.Check the dynamic symbolic unit and blocksize on the specification card. See the job log for further details.SECONDARY INDEX ROOT PAGE NOT FOUND ON SIT PAGEThe secondary index entry cannot be located on the Secondary Index Table page.Ensure that all fields with a key type of S are defined as secondary indexes. If not, invoke online SIXBUILD processing.INVALID PAGE TYPE DETECTED WHEN CAPTURING EXISTING GIXExisting group index chain contains invalid page type codes. (Table is possibly corrupted.)Verify the Pagestore by using S6BBRPTR. Also, contact TIBCO Support.SORT FAILURE DETECTED DURING SECONDARY INDEX PROCESSINGAn error was detected by the sort program when reorganizing the index capture file for a secondary index load.Check the job log for messages from SORT. Ensure that you have a SYSOUT DD in your JCL.SORT FAILURE DETECTED DURING GROUP INDEX PROCESSINGAn error was detected by the sort program when reorganizing the group index capture file for a group index build.Check the job log for messages from SORT. Ensure that you have a SYSOUT DD in your JCL.INDEX CAPTURE FILE FAILED TO OPEN FOR INPUTThe internal index file could not be opened after being built.INDEX CONTROL TABLE OVERFLOWED; TOO MANY INDEX LEVELSThe internal index table is too small for this run.RESIDENT TABLE INDEX UPDATE PREPARATION FAILEDPreparation for actual database update failed.INPUT RECORD LENGTH EXCEEDS LOADS CAPABILITYThe total length of the row defined for the target table is larger than the maximum permitted.Check and correct the definition on the control data set; the table as specified would not have been accepted by the Object Service Broker Table Definer.BROWSE MODE - REQUEST VALIDATION COMPLETEThe option BROWSE was specified, which results in termination after validation of the control file.No action necessary. Remember to remove the BROWSE option when (if) the load is actually submitted.RESERVED TABLE - OFFLINE LOAD NOT PERMITTEDThe table name requested cannot be loaded using this utility.The OLD NULL option applies to the unload utilities only.Remove the option and retry or contact TIBCO Support.STATICS VALUES NOT SUPPORTED FOR UNICODE FIELDSWhen attempting to load data into a table using the offline batch utility S6BBRTBL, a default value was specified for a field that has a Unicode syntax. This is not supported.Remove the default value card and rerun your load process.UNICODE SYNTAX NOT SUPPORTED FOR PARMS OR KEYSA Unicode syntax was specified on the definition cards for a field that either a parameter or key field.Correct the control cards and try the S6BBRTBL utility.The audit trail (printer) failed to open. User abend code 932 is issued.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |