Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Using Messages With Identifiers : SV: Batch Server

SV: Batch Server
S6BSV901E
CNTL File: Invalid numeric value
Batch Server
Definition Control File Error: On the S entry of the file, there are various control fields that must be either completely blank or contain a numeric value. These include all fields on the "S"pecification entry.
Check the file and correct any incorrect entries.
S6BSV902E
CNTL File: - no entries found
Batch Server
Definition Control File Error: The utility requested requires a Definition Control File and an S type entry must be the first entry in the file. No S type entry was found in the Control file indicated.
Check that the file name entered on the command line is correct. If the file is damaged, use the online tool BATCHLOAD_CARDS to recreate the file.
S6BSV903E
CNTL File: 'S' type must be first entry
Batch Server
Definition Control File Error: The utility requested requires a Definition Control File and the S type entry must be the first entry in the file. No S type entry was found in the Control file indicated.
Check that the file name entered on the command line is correct. If the file is damaged, use the online tool BATCHLOAD_CARDS to recreate the file.
S6BSV904E
CNTL File: 'I' sequence # error
Batch Server
Definition Control File Error: The Input (I) entries in the Definition Control file must be in sequence and the sequence number itself must be numeric.
Check the sequence numbers in the Definition Control File and either place them in sequence or correct the sequence numbers.
S6BSV905W
Null-Equivalent value is ignored
Batch Server
A NULL-EQUIVALENT value has been specified for a syntax/field for which it is not accepted.
No action required.
S6BSV906E
Null-Equivalent value is invalid
Batch Server
A NULL-EQUIVALENT value specified on the control file is invalid.
Check the documentation if necessary, correct and retry.
S6BSV907E
CNTL File: field length invalid
Batch Server
Definition Control File Error: The field lengths entered in the Definition Control File must be numeric.
Correct the field length for the field indicated.
S6BSV908E
CNTL File: # of decimals error
Batch Server
Definition Control File Error: The # of decimals entered in the Definition Control File must be either completely blank or a valid number.
Correct the # of decimals for the field indicated. NOTE: For certain semantic-type/syntax combinations no decimals are permitted.
S6BSV909E
CNTL File: field offset error
Batch Server
Definition Control File Error: The offset field must be either completely blank or numeric. The offset (based on 0 as the first position in the input file) is the physical start of the field within the input file.
Check the offset; it may not be required if the field immediately before it in the input file is defined.
S6BSV911E
CNTL File: 'H' sequence error
Batch Server
Definition Control File Error: The Table (H) entries in the Definition Control file must be in numeric sequence.
Check the sequence numbers in the Definition Control File and either place them in sequence or correct the sequence numbers.
S6BSV912E
CNTL File: unknown 'H' subtype
Batch Server
Definition Control File Error: This sub-type is incorrect for a type H entry.
Check the manual for acceptable types and correct the entry or use the requisite online Batch tool (BATCHLOAD_CARDS, etc.) to generate a correct definition file.
S6BSV913E
CNTL File: 'H' internal field name blank
Batch Server
Definition Control File Error: Type H definition statement field names cannot be blank.
Correct the statement in error.
S6BSV915E
CNTL File: invalid key type
Batch Server
Definition Control File Error: The key type entered is incorrect.
Check the manual for acceptable key types and correct the definition for the field indicated.
S6BSV916E
CNTL File: invalid # parms
Batch Server
Definition Control File Error: Type H sub-type T columns 50 through 52 are invalid. This field should show the number of parameters in the table to be unloaded.
Correct the entry.
S6BSV917E
CNTL File: invalid # fields
Batch Server
Definition Control File Error: Type H sub-type T columns 54 through 57 are invalid. This field should show the number of fields in the table to be unloaded.
Correct the entry.
S6BSV918E
CNTL File: bad sequence, static value
Batch Server
Definition Control File Error:
Static value (type V) entries (column 20) must be in sequence. Single entry values (less than 50 characters) sequence number = blank, 0 or 1. If the static value is greater than 50 characters, it appears on more than one definition statement. These statements must be in the correct sequence.
Correct the static value sequence numbers or generate a valid file using the online tool BATCHLOAD_CARDS.
S6BSV919E
CNTL File: no match for static value field
Batch Server
Definition Control File Error: The target field name that is to receive the static value must exist in the table definition (H entries).
Either remove the static value if it is superfluous or insert the correct target field name.
S6BSV920E
CNTL File: collision - field and static value
Batch Server
Definition Control File Error: A static value is loaded into every instance of the field to which it is targeted. Its target field cannot also receive input from an input file field. Both values cannot be placed in the target field.
Correct the table definitions so that only one value is provided to each table field.
S6BSV922E
CNTL File: Static value max length exceeded
Batch Server
Definition Control File Error: This static value exceeds the maximum length permitted.
Consider splitting the field to be filled by the static value, then entering a static value for each of the subfields.
S6BSV923E
CNTL File: no fields defined
Batch Server
Definition Control File Error.
Generate a valid Definition Control File by using the online tool (BATCHLOAD_CARDS; BATCHUNLD_CARDS; SIXBUILD_CARDS).
S6BSV924E
CNTL File: invalid syntax
Batch Server
Definition Control File Error.
Check the manual for acceptable entries and correct the definition for the field name indicated.
S6BSV925E
CNTL File: invalid semantic type
Batch Server
Definition Control File Error.
Check the manual for acceptable entries and correct the definition for the field name indicated.
S6BSV926E
CNTL File: 'I' to 'H' field incompatibility
Batch Server
Definition Control File Error: There are semantic-type/syntaxes which cannot be converted to other selected semantic-type/syntaxes, (for example packed decimal cannot be converted to Logical/Character).
Check the definition for the fields indicated (length to length; syntax to syntax).
S6BSV927E
CNTL File: Value to 'H' field incompatibility
Batch Server
Definition Control File Error: Static values are always considered to be NO-semantic-type/syntax Character (C or V). If the target field's semantic-type/syntax is not compatible with this combination, this error will occur.
Check and correct the target (table) field's semantic-type/syntax.
S6BSV928E
CNTL File: Offset overlaps previous fields
Batch Server
Definition Control File Error: Fields must be defined once only and cannot be redefined (no part of a field can occur in another field). Offsets are expected to be in relation to zero (the first character in a file is considered at offset 0). The offset specified overlaps a previously defined field.
Check the definition for the field indicated in relation to the field before it. If two adjacent fields are defined it is not necessary to include an offset for the second as the first field will establish the second's position in the file.
S6BSV929E
CNTL File is required (-C option)
Batch Server
The identity of the Definition Control File is missing from the command line (-C).
Try again, ensuring that the -C option is specified on the command line.
S6BSV934E
Invalid Segment requested
Batch Server
The segment identifier provided in the -s option on the command line is invalid.
Check and correct.
S6BSV935E
Parameter field length exceeds maximum
Batch Server
Definition Control File Error.
Check the manual for the maximum length permitted and correct the entry indicated.
S6BSV936E
Total Parameter length exceeds maximum
Batch Server
Definition Control File Error: There is a maximum total length for all parameters combined; this limit has been exceeded.
Check the manual for the maximum total parameter length.
S6BSV937E
Illegal Parameter syntax
Batch Server
Definition Control File Error: Not all syntaxes are acceptable as parameters.
Check the manual for acceptable parameter syntaxes.
S6BSV938E
Maximum # of Parameters exceeded
Batch Server
Definition Control File Error: There is a limit on the number of parameters which can be defined for a table; this limit has been exceeded.
Check and correct.
S6BSV939E
Primary/Secondary key field length exceeds maximum
Batch Server
Definition Control File Error: There is a limit on the length of each individual key field.
Check and correct.
S6BSV940E
Total Primary key length exceeds maximum
Batch Server
Definition Control File Error: There is a limit to the total length of all primary key fields combined.
Check and correct.
S6BSV941E
Illegal Primary key syntax
Batch Server
Definition Control File Error: All syntaxes are not eligible to be used as primary keys.
Check the definition of the field indicated and correct it.
S6BSV942E
Maximum # Primary key fields exceeded
Batch Server
There is a limit to the number of primary keys which can be defined in a single table.
Check and correct.
S6BSV943E
First Primary key cannot serve as Secondary
Batch Server
Definition Control File Error: The first or PRIMARY primary-key may not also be defined as a secondary key.
Check and correct.
S6BSV944E
IDGEN Primary key definition error
Batch Server
Definition Control File Error: When a table is defined as IDgen, its primary key must be defined as binary (B) syntax with a length of 4.
Check and correct.
S6BSV946E
Maximum # Secondary key fields exceeded
Batch Server
Definition Control File Error: There is a limit to the number of secondary key fields which may be defined in a single table.
Check and correct.
S6BSV947E
Unknown key type
Batch Server
Definition Control File Error: An invalid entry has been made in the key-type field of the identified field's definition statement.
Correct the entry.
S6BSV948E
IDGEN permits 1 Primary Key only
Batch Server
Definition Control File Error: An IDgen keyed table is allowed only one primary key field.
Correct the entry.
S6BSV949E
HCS processing failed
Batch Server
This utility requires the -t option on the command line.
Try again, indicate the ID of the Object Service Broker node using the -t command line option.
S6BSV950E
Unable to open Segment requested
Batch Server
The segment requested must be disconnected (offline) from online processing in order for this utility to function correctly.
Request that the segment be placed offline.
S6BSV951E
Unable to close the Segment
Batch Server
The utility was unable to close the segment on which it was working.
If the utility in use modifies the Pagestore (LOAD/SIXBUILD/S6BBRPGC (Pagestore correction)) the Pagestore must be considered potentially inconsistent. Investigate or report the error to support staff. The cause of the error must be identified and corrected before the failed activity is tried again. Inspect the report produced by the utility, it may help in determining the reason for the failure or show that the primary-data-build was successfully completed. If the LOAD-secondary-index-build failed, it is possible to delete the secondary index pages (online) and rebuild using the SIXBUILD only. If the utility in use was an UNLOAD, it cannot have impacted the Pagestore in any way. However before using the file which has been created it should be checked for completeness.
S6BSV953E
Static Value content error
Batch Server
Definition Control File Error:
Correct the static value.
S6BSV954W
**WARNING** - Possible Input File Format Error - **WARNING*
Batch Server
There are three file formats. All are derived from z/OS sequential file types:
FIXED - The equivalent of a z/OS FB data set after FTP to Windows or Solaris. The file contains records all the same length (as described in the Control (-C) File). No record lengths are contained in the file.
VARIABLE NO BDW - The result when a z/OS VB data set is FTPed to Windows or Solaris. This file contains a 4-byte RDW (length) in front of each record. All possible fields in the file must be defined using BATCHLOAD_CARDS (-C Control File) and "Input Data File Length Format" must be set to "V". NOTE: Do not specify the -m (Blocked Variable) option on the command line.
VARIABLE BLOCKED - The first record of each block is preceded by a 4-byte BDW (block length) and a 4-byte RDW (record length). This is the file format used when files are created using the Unload utilities (hrnbrulh, hrnbrulb, and hrnbrula) on Windows or Solaris. When using BATCHLOAD_CARDS to describe the file's format, you must define all possible fields and set the "Input Data File Length Format" to "V". On the command line you must specify the -m option.
Using BATCHLOAD_CARDS, the input file is described using the "INPUT FILE DEFINITION SCREEN". All possible data fields in the file must be defined. Do not define the length fields if the file is Variable. If the input file was created using S6BBRULA, then the entry "Was input data unloaded from an archive" must be set to "Y". If the input file is either "VARIABLE NO BDW" or "VARIABLE BLOCKED" (see above), then the entry "Input Data File Length Format" must be set to "V".
NOTE: This is a warning only; it is not possible for the utility, by analyzing the file's data, to be absolutely certain that the file has a format that differs from that specified in the Control File (-C) and the Command Line (-m).
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 format was correctly specified before using the output from the utility.
____________________________________________ If you are transferring Object Service Broker files between platforms, refer to documentation for the S6BBRFRU/hrnbrfru (Reformat Object Service Broker Files Transferred with FTP) utility.
S6BSV957E
Unable to open the specified input file
Batch Server
An Open input file request failed. This can be caused by problems with the input device, but most commonly is caused by one of:
Correct the problem and try again. If you need the Large File Support feature, contact TIBCO Support.
S6BSV962E
SELECT File: invalid include/exclude indicator
Batch Server
Selection Criteria File Error: Each selection entry requires an indicator (I or X) in column 17. It indicates inclusion (I) or exclusion (X) (for rows matching the selection criteria) in the unloaded table.
Check and correct the entry.
S6BSV963E
SELECT File: invalid relational operator
Batch Server
Selection Criteria File Error: The relational operator specified is invalid.
Check the UNLOAD documentation for acceptable relational operators and correct the select statement.
S6BSV964E
SELECT File: relational operator not constant
Batch Server
Selection Criteria File Error: The relational operator chosen for the first selection statement must be used on all other selection statements.
Check and correct.
S6BSV965E
SELECT File: invalid numeric value
Batch Server
Selection Criteria File Error: The selection value stated refers to a numeric field and therefore should be numeric.
Check and correct.
S6BSV966E
Numeric Syntax secondaries cannot be NULL
Batch Server
Definition Control File Error: A secondary index field is defined with no corresponding input field which means all field instances in the table will be Null. Null numeric secondary values are not permitted.
Check and correct.
S6BSV967E
Illegal Secondary Key syntax
Batch Server
Definition Control File Error: All syntaxes are not eligible to be used as secondary keys.
Check the field indicated and correct it.
S6BSV968E
Std Input not permitted with non-text input
Batch Server
Text data as input is not currently supported.
An input file name must be provided on the command line.
S6BSV970E
Unable to acquire a free page on this segment
Batch Server
The segment in use is full.
Inspect the utility report.
LOAD -- If the primary-data-index is complete and the failure occurred during the secondary-index build:
1.
2.
3.
Use the offline secondary index builder to build the secondary index.
1.
Clear the partially built table using either: for a failed LOAD, the CLEARTAB tool; for a failed SIXBUILD, the online tool SIXDELETE.
2.
3.
S6BBRPGC/hrnbrpgc (Pagestore Correction) -- Increase the storage available to the segment and rerun the failed utility.
S6BSV972E
Maximum # Fields for a table - exceeded
Batch Server
Definition Control File Error: The number of fields specified (S type entry columns 31-33) exceeds the maximum number of fields which can be defined in a table.
Check the entry; if it is correct, this table cannot be loaded using this utility.
S6BSV973E
# fields specified in control file exceeded
Batch Server
Definition Control File Error: The number of fields defined exceeds the maximum specified (S type entry columns 31-33) earlier in the Control File.
Check and correct.
S6BSV974E
SELECT File: Illegal selection statement
Batch Server
Selection Criteria File Error: No selection criteria value supplied.
Check and correct.
S6BSV975E
SELECT File: Illegal Format
Batch Server
Selection Criteria File Error: The statement cannot be processed.
Refer to the documentation for the correct format of the Selection Criteria entries, or use the online BATCHUNLD_CARDS tool to create a properly formatted file.
S6BSV979E
Input Data I/O error
Batch Server
An input operation failed. This can be caused by problems with the input device, but may be caused (on Solaris) by attempting to read a file larger than 2 gigabytes in size.
Check for the cause of the I/O failure and fix the problem. If the problem is caused by file size, you may require the Large File Support feature. To obtain this feature, contact TIBCO Support.
S6BSV982E
Bad input data variable length format
Batch Server
If variable-length format data is indicated in the Definition Control File, the data must conform to z/OS variable-length format: each record must be preceded by four bytes as follows: a 2-byte length followed by 2 bytes of binary zero.
Check the input file and ensure the data is in Object Service Broker data format (EBCDIC) and that it is variable. If the file is not variable, modify the Definition Control File accordingly.
S6BSV986E
I/O error
Batch Server
An input or output operation failed. This can be caused by problems with the I/O device, but most commonly is caused by one of:
[Solaris] The file exceeds the 2 gigabyte file-size limit (input) or is attempting to exceed the limit (output)
Check for the cause of the I/O failure and fix the problem. If the problem is caused by file size, you may require the Large File Support feature. To obtain this feature, contact TIBCO Support.
S6BSV990E
SELECT File: Blank value not permitted
Batch Server
Selection Criteria File Error: A blank criteria value is not permitted.
Check and correct.
S6BSV996E
Maximum row size exceeded
Batch Server
There is a limit on the size of row which Object Service Broker supports; anything longer than this cannot be stored on the Pagestore.
Correct the table definition, the definition in the utility control file does not match that presented to the Object Service Broker Table Definer.
S6BSV998E
Access to table denied
Batch Server
You do not have the necessary authority to access this table
Contact Object Service Broker administration and request the necessary authority

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved