![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
RESTART PROCESSING REQUEST AFTER PVS SELECTION BREAKS6BBRULA is running in restart mode after a break occurred for external table instance processing.count PVS ENTRIES TO RECOVER ACCORDING TO BREAK POINT CONTROL RECORDWhen the process was interrupted to allow external table instance selection, a control record was generated containing the number of table instances. This message displays the total number of table instances so that you can verify that the restart is using the correct file.count PVS ENTRIES RECOVERED AFTER BREAK POINTThis message displays the number of table instances that were processed in the restart processing mode.count PVS ENTRIES IGNORED AFTER BREAK POINTThis message displays the number of table instances that were removed from the table instance break file during external selection processing.count DATA ENTRIES TO RECOVER ACCORDING TO BREAK POINT CONTROL RECORDWhen the process was interrupted to allow external table instance selection, a control record was generated containing the number of data page entries. This message displays the total number of data page entries so that you can verify that the restart is using the correct file.count DATA ENTRIES RECOVERED AFTER BREAK POINTThis message displays the number of data page entries that were processed in the restart processing mode.count DATA ENTRIES IGNORED AFTER BREAK POINTThis message displays the number of data page entries that were ignored because of external table instance selection.The first pass (read through) of the archive file was initiated.PASS ONE; count RECORDS READ, count ACCEPTED, count PROCESSEDThis message specifies the number of archive records read, accepted, and processed. If the archive contains multiple segments, only the correct segment pages are accepted. If the archive contains unrecognizable pages, the processed count may be less than the accepted count.The second pass of the archive information occurs only if one or more of the unloaded tables are parameterized. Pass two processing reads through only those pages that pertain to table instances that were saved in the pages file.GIX TABLE COMPRESSION COMPLETE INPUT=count, OUTPUT=countTable instance information is retained for all tables in the archive. Once the required table instance pages are identified, all others are removed. The input count is the total number of table instance pages. The output count is the number that are required.DATA TABLE COMPRESSION COMPLETE INPUT=count, OUTPUT=countWhen all the tables are processed and it is known which data page contains the required information, all others are eliminated. The input count is the total number of data pages. The output count is the number of data pages that are required.TABLE INSTANCE SELECTION BREAK REQUESTEDThe BREAK run time parameter was supplied. Therefore, processing will be interrupted at the end of pass two.count DATA CHAIN ENTRIES SAVED AT BREAK POINTAt the time of the interruption (to externally select table instances), count data page entries were backed up to the BRKDATA file.count PVS TABLE ENTRIES SAVED AT BREAK POINTAt the time of the interruption (to externally select table instances) count table instances were backed up to the BRKPVS file.PASS TWO; GROUP INDEX PAGES READ count, count PROCESSEDThe extracted table instance pages are processed. Of the pages read in READ count, count were processed.The third and final pass of the data is initiated. The third pass extracts all required data elements from the archive file.PASS THREE; count RECORDS READ, count ACCEPTED, count PROCESSEDThe indicated number of records were read from the archive file. Of the records read, the indicated number were accepted and the indicated number were processed. Note that the actual number of records read may be less than the records read in pass one. This can occur because all requested records were retrieved before the end of the archive was reached.There were count records unloaded for table tablename.tablename count RECORDS UNLOADED BEFORE PROCESSING ABORTEDThere were count records unloaded for table tablename. Table tablename did not complete unloading because of an error detected during processing. However, any records unloaded prior to the error are retained in the recovery file.SELECTION RCD count; PARM parm# NUMERIC DATA INVALID; TABLE tablenameThe selection record number count for the specified parm# of table tablename contains an invalid numeric. The selection entry is ignored.SELECTION TABLE NOT FOUND; SELECTION RECORD IGNOREDThe table specified on the selection is not among the tables to be unloaded. Following this message, the first 80 bytes of the selection record are displayed.SELECTION TABLE NOT PARAMETERIZED; SELECTION RECORD IGNOREDThe table specified in the selection record is not parameterized according to the Object Service Broker definition cards. The selection record is ignored. Following this message, the first 80 bytes of the selection record are displayed.More tables were detected in the Object Service Broker definition cards than the program was prepared to handle based on the table count in the first control card. The rejected control card is displayed after this message.Divide the tables to be unloaded into smaller groups.PROCESSING TERMINATED FOR TABLE tablenameThe specified table is ignored for the remainder of the run because an error was detected.Refer to the previous message in the audit trail to determine what the error was.ACTUAL LENGTH (len) GREATER THAN DEFINED LENGTH (len) ON FIELD fieldnameThe actual length of a field value from the archive file is greater than the length of the field according to the Object Service Broker definition control cards.Verify that your definition is appropriate for the time when the archive was created.MORE FIELDS DEFINED IN DATA OCCURRENCE THAN VIA DEFINITION CONTROL CARDSThe number of fields in an archive file occurrence is greater than the number of the fields according to the Object Service Broker definition control cards.Verify that your definition is appropriate for the time when the archive was created.Columns 64-79 are valid for packed decimal and binary fields only.The Table Control File Entry being processed indicates that it is a parameterized table. The EXEC-PARMS which request resource allocation to process such tables are HIX, GIX and PVS. These PARMS indicate that no parameterized tables are to be processed (each PARM is set to zero).Note: If parameterized table(s) are to be recovered, all three of the above mentioned PARMS must be nonzero.Either remove the HIX, GIX and PVS EXEC-PARMS altogether (request the defaults) or assign a percentage to each PARM. Resubmit the request after correcting the PARMS.SPACE NOT AVAILABLE TO RETAIN INFORMATION FOR XX-30-XXGETMAIN failed to retrieve memory space to retain internal processing tables. XX-30-XX is one of the following:During the attempt to open the file named in the message, an open error was detected. XX-40-XX is one of the following:
• I - SEQUENTIAL ARCHIVE (ARCHIVE) 202,204The "I -" and "O -" represent open for input or output respectively. The abend codes issued are 201 to 204 as listed above.The named internal table overflowed. XX-20-XX is one of the following:Increase the number of pages, or redistribute the page concentrations by using the run time parameters.RESTART ERROR DETECTED; CONTROL RECORD FOR PVS NOT FOUNDWhen the BRKPVS file was generated in pass 2 to allow external table instance selection, a control record was generated to indicate the number of entries. When the restart initialization processing retrieved the table instances file, the control entry was not the first record. Abend code 201 is issued.RUN TIME PARAMETER IS NOT RECOGNIZED - run_time_parmThe indicated run time parameter is not recognized. Abend code 201 is issued.VALUE value OUT OF RANGE (range TO range) FOR PARAMETER - parmThe run time parameter parm contains a value that is outside the range specified in the error message. Abend code 201 is issued.CONTROL CARD HAS AN INVALID TYPE CODE (COLUMN 7)The control card type is not recognized. Refer to the card image that follows this message in the audit trail. Abend code 201 is issued.RESTART ERROR DETECTED; CONTROL TABLE NOT FOUND FOR TABLE - tablenameThe specified table cannot be found in the table definition which is based on the control cards. Abend code 201 is issued.Ensure that the restart files (CONTPVS and CONTDATA) are the appropriate files for the control card file supplied.RESTART ERROR DETECTED; CONTROL RECORD FOR DATA NOT FOUNDWhen the BRKDATA file was generated in pass 2 (to allow external table instance selection), a control record was generated to indicate the number of entries. When the restart initialization processing retrieved the data occurrence file, the control entry was not the first record. Abend code 201 is issued.TABLE COUNT CONTROL RECORD (TYPE "*" - COLUMN 7) NOT FOUNDThe first card expected in the control card file is the table count card. During the processing of the control card file, the table count card was not found. Abend code 201 is issued.TABLE INSTANCE PVS SELECTION CONTROL CARD NOT FOUNDThe record in the table instance selection file must be a control record specifying the number of entries. This control record was not found. Abend code 201 is issued.INPUT SELECTION RECORDS NOT SORTED BY TABLE NAMEThe table instance selection was not presorted into table name sequence. Abend code 201 is issued.Sort the selection file by table name and rerun S6BBRULA.PARM/FIELD SEQUENCE ERROR DETECTED; TABLE NUMBER NOT EQUAL TO PREVIOUS TABLE CARDThe sequence of the parameter or field definition cards is in error. Abend code 201 is issued.Correct either the card sequence numbers or sort the control cards again.ERROR DETECTED WHEN DETERMINING ARCHIVE FILE FORMATWhen attempting to determine the organization of the input archive file (sequential or VSAM), RDJFCB failed. Abend code 202 or 204 is issued.Refer to the job log for further information.RESIDENT TABLE INDEX ENTRY NOT FOUND FOR TABLE - tablenameThe specified table cannot be found in the resident table index. Abend code 202 is issued.
• The spelling of the table name in the control cards
• The segment number in the run time parametersARCHIVE CONTAINS WRONG SEGMENT FOR TABLE - tablenameThe specified table resides on a segment other than the one being processed. Abend code 201 is issued.Check the segment number in the run time parameters, and verify that you have the appropriate archive file.PAGE NUMBER (page#) NOT FOUND, INPUT PARM % INCORRECT
• The specified page number is part of the named table's tree, but that page is not on the archive file.
• GIX/PVS run time parameter is specified as 0 and the table is parameterized.
• For item 1, check that you have a complete archive and/or run the archive pointer validation process (S6BBRPTR).
• For item 2, if the table is parameterized verify that the GIX and PVS values are entered correctly. Refer to the documentation for the default values.ARCHIVE UNLOAD PROCESSING TERMINATED BECAUSE OF ERRORAll the tables to be unloaded were eliminated because of errors. Abend code 203 or 204 is issued.Correct the errors detected for each table and rerun S6BBRULA.TABLE NUMBER CONTAINS NONNUMERIC CHARACTERSThe table number (columns 3-5) on a T, P, F or R type of card contains an invalid numeric character. Leading zeros are required.Processing is terminated. The card image is displayed after the message.PARM/FIELD LENGTH CONTAINS NONNUMERIC CHARACTERSThe length (columns 50-52) entered on a parameter or field definition card contains an invalid numeric character. Leading zeros are required.Processing is terminated. The card image is displayed after the message.DECIMAL POSITION CONTAINS NONNUMERIC CHARACTERSThe decimal position (columns 54-56) entered on a parameter or field definition card contains an invalid numeric character. Leading zeros are required.Processing is terminated. The card image is displayed after the message.OUTPUT OFFSET/RECORD LENGTH NOT NUMERICThe output offset (columns 60-63) entered on a parameter or field definition card contains an invalid numeric character. When you enter the offset, remember that leading zeros are required. If calculated offsets are desired, the field must be blank.Processing is terminated. The card image is displayed after the message.FIELD COUNT CONTAINS NONNUMERIC CHARACTERSThe field count (columns 54-56) entered on the table header card contains an invalid numeric character. Leading zeros are required.Processing is terminated. The card image is displayed after the message.PARAMETER COUNT CONTAINS NONNUMERIC CHARACTERSThe parameter count (columns 50-52) entered on the table header definition card contains an invalid numeric character. Leading zeros are required.Processing is terminated. The card image is displayed after the message.MEMORY REQUIREMENT CALCULATION ERROR DETECTEDWhen calculating the internal memory requirements (which are based on a percentage of the total anticipated pages), the total number of pages was found to be zero. Check the specification of the PAGES execution parameter.The table number (columns 3-5) is either out of sequence, or the first table number is not 000.Processing is terminated. Do the following:
• Ensure that the control cards are properly organized.
• For each table to be unloaded, cards must appear in the following sequence:
1.
4. tablename END RECORD CONTROL RECORD MISSINGWhen validating table definitions after the control card file was exhausted, S6BBRULA determined that the R end of table block record was not received for the indicated table. Either the R card was omitted, or it is not positioned correctly in the control card file.Processing is terminated. Correct the control card file.tablename PARAMETERS DEFINITION INVALIDThe number of parameters specified in the header for the indicated table is invalid, or the parameter definition information is incomplete.Processing is terminated. Correct the parameters.The number of fields specified in the header for the indicated table is invalid, or the field definition information is incomplete.Processing is terminated. Correct the field number or definitions.The text length specified in the end of table block (R type) record does not agree with the total length of the defined parameters and fields for the table indicated in the message.Processing is terminated. Correct the length specified in the R record.The number of tables (columns 60 to 63) specified in the table control card (type = "*") contains an invalid numeric character. Leading zeros must be specified.Processing is terminated. Correct the number of tables.HIX/GIX/PVS CONSISTENCY ERROR DETECTEDThe run time parameters HIX, GIX, and PVS have been entered to override the default page type percentage estimates. One or more of the parameters contains a zero and the remainder are nonzero.Processing is terminated. If the table or tables you are unloading do not contain any parameters, set all three to zero. If parameters are present, all three must contain positive nonzero values.Conflicting specifications for parameterized tables.Processing is terminated with ABEND 201. Check the specifications. Make sure that tables are correctly defined.NULL-EQUIVALENT VALUE FOUND IN TABLE ROW FIELD:A null equivalent value was found in the table. This value is the value you selected to represent a null in the unloaded file. Obviously, should you wish to load this data to an Object Service Broker database, the LOAD utility will be unable to distinguish between this value and an actual null-equivalent value. This field would be loaded as a null value.It is advisable to discard the output from this UNLOAD, choose a unique null-equivalent value and rerun.NULL FOUND IN "NOVALUE" (NO NULL ALLOWED) FIELD:A field described by the control data set as a NOVALUE or "no nulls permitted" field has a null value. It will be unloaded as zero.Determine whether this field should have been described as NOVALUE, discard the output from this run, and try again with the correct control specifications.Columns 64-79 are invalid. If the value entered is one of the acceptable codes (LOWVALUE, HIGHVALUE, or NOVALUE), it is probably misspelled; otherwise, it should be numeric.Null Equivalent related warnings indicate that the control data set may be incorrect.Check and correct the warnings received prior to this message and try again.The selection data set LRECL is incorrect.At least one of the DDNAMES mentioned has incorrect LRECL.The CONTROL data set must be RECFM F or FB; LRECL 80.The data set supplied does not appear to be an archive.Check and if JCL is correct, contact TIBCO Support.SYNTAX/SEMANTIC TYPE COMBINATION NOT SUPPORTEDThe semantic type and syntax code combination on the identified definition card is not supported.UNICODE FIELD LENGTH MUST BE EVEN (DIVISIBLE BY 2)The identified definition card contains a field with Unicode syntax whose length is not even. This is not supported.UNICODE PARAMETERS ARE NOT SUPPORTEDUnicode syntax is not support for a parameter field.Correct the definition cards and run the job again.The audit trail file would not open for output.See the job log for additional information.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |