HP 3000 Manuals HP 3000 Manuals
SDCDE Operational Warning Messages
4741 MESSAGE Name truncated while adding prefix to long-name (SDWARN 4741)
CAUSE The length of the given COBOL name, after adding the prefix to
it exceeds 61 characters.
ACTION None necessary. The name is automatically truncated to 61
characters.
--------------------------------------------------------------------------------------
4742 MESSAGE Name truncated while adding suffix to long-name (SDWARN 4742)
CAUSE The length of the given COBOL name, after adding the suffix to
it, exceeds 61 characters.
ACTION None necessary. The name is automatically truncated to 61
characters.
--------------------------------------------------------------------------------------
4743 MESSAGE Invalid-name contains illegal characters (SDWARN 4743)
CAUSE The given COBOL name contains illegal characters.
ACTION None necessary. The illegal characters are replaced with a
hyphen, '-'. Check the manual for a list of illegal characters.
--------------------------------------------------------------------------------------
4744 MESSAGE Invalid-name contains a leading hyphen (SDWARN 4744)
CAUSE The given COBOL name contains a leading hyphen.
ACTION None necessary. The leading hyphen, '-', will be automatically
prefixed by the following string: 'X-'.
--------------------------------------------------------------------------------------
4745 MESSAGE Invalid-name contains a trailing hyphen (SDWARN 4745)
CAUSE The given COBOL name contains a trailing hyphen.
ACTION None necessary. The trailing hyphen, '-', will be automatically
suffixed by the following string: '-X'.
--------------------------------------------------------------------------------------
4750 MESSAGE Invalid-name is a COBOL reserved word (SDWARN 4750)
CAUSE The given name is a COBOL reserved word.
ACTION None necessary. The name will be automatically suffixed by the
following string: '-X'.
--------------------------------------------------------------------------------------
(cont.)
--------------------------------------------------------------------------------------
4751 MESSAGE Illegal name above is transformed into transformed-name (SDWARN
4751)
CAUSE Due to a previous error, the name has been transformed into the
given valid COBOL name.
ACTION None necessary. This is just an informative message.
--------------------------------------------------------------------------------------
4752 MESSAGE Module line number too big (>= 1000000) (SDWARN 4752)
CAUSE The module number of the next line (which is automatically
generated in SDCDE) exceeds the 6 digit limit, 999999.
ACTION None necessary. SDCDE will prompt you for the name of the
module into which the source generation will continue.
--------------------------------------------------------------------------------------
4753 MESSAGE IMAGE-DATABASE data-base contains no data set. No source
generated (SDWARN 4753)
CAUSE No IMAGE-DATABASE contains IMAGE-DATASET relationships were
found in the dictionary for the given database.
ACTION No source will be generated for the database until the
relationship(s) are added to the dictionary.
--------------------------------------------------------------------------------------
4754 MESSAGE IMAGE-DATASET data-set contains no RECORD. No source generated
(SDWARN 4754)
CAUSE No IMAGE-DATASET contains RECORD relationships were found in the
dictionary for the given data set.
ACTION No source will be generated for the data set until the
relationship(s) are added to the dictionary.
--------------------------------------------------------------------------------------
4755 MESSAGE IMAGE-DATASET data-set has no search item (SDWARN 4755)
CAUSE No IMAGE-DATASET key ELEMENT relationships were found in the
dictionary for the given data set if the set is a master set.
If it is a detailed set, no five way chain relationships were
found in the dictionary.
ACTION No search item constants will be generated for the data set
until the relationship(s) are added to the dictionary.
--------------------------------------------------------------------------------------
(cont.)
--------------------------------------------------------------------------------------
4760 MESSAGE Data-set has an illegal data set type. Defaulting to DETAIL
(SDWARN 4760)
CAUSE The image-dataset-type attribute retrieved from the dictionary
does not contain a valid data set type.
ACTION The default value, DETAIL, is assigned if the image-dataset-type
attribute is invalid. The image-dataset-type attribute must be
updated in the dictionary to one of the following valid values:
AUTOMATIC, MASTER, or DETAIL.
--------------------------------------------------------------------------------------
4761 MESSAGE Path for search-item data set has a blank search item (SDWARN
4761)
CAUSE In the IMAGE-DATASET, ELEMENT, ELEMENT, IMAGE-DATASET,
IMAGE-DATABASE chains relationship, the search item (the first
ELEMENT) is a blank entity.
ACTION No search item constant will be generated for the given data
set. If one is required, a non-blank search item must be
specified in the IMAGE-DATASET, ELEMENT, ELEMENT, IMAGE-DATASET,
IMAGE-DATABASE chains relationship.
--------------------------------------------------------------------------------------
4762 MESSAGE FORMSFILE forms-file contains no FORM. No source generated
(SDWARN 4762)
CAUSE No FORMSFILE contains FORM relationships were found in the
dictionary for the given forms file.
ACTION No source will be generated for the forms file until the
relationship(s) are added to the dictionary.
--------------------------------------------------------------------------------------
4763 MESSAGE FORM form contains no ELEMENTS. No source generated (SDWARN
4763)
CAUSE No FORM contains ELEMENT relationships were found in the
dictionary for the given form.
ACTION No source will be generated for the form until the
relationship(s) are added to the dictionary.
--------------------------------------------------------------------------------------
4764 MESSAGE FILE file contains no RECORD. No source generated (SDWARN 4764)
CAUSE No FILE contains RECORD relationships were found in the
dictionary for the given file.
ACTION No source will be generated for the file until the
relationship(s) are added to the dictionary.
--------------------------------------------------------------------------------------
(cont.)
--------------------------------------------------------------------------------------
4765 MESSAGE FILE file uses multiple DEVICE-CLASSES. No dev-cl name incl in
ASSIGN clause (SDWARN 4765)
CAUSE Multiple FILE uses DEVICE-CLASS relationships were found for the
given file.
ACTION The ASSIGN clause will not include any device name. If one is
desired, all but one FILE uses DEVICE-CLASS relationship must be
deleted from the dictionary for the given file.
--------------------------------------------------------------------------------------
4770 MESSAGE Relative file cannot produce SD statement. Generating FD
(SDWARN 4770)
CAUSE The SD option was chosen at the FD/SD prompt, when the file
being defined in the file section. Relative files can only be
defined using the FD statement.
ACTION The FD statement will automatically be used in the file section
definition. No action required by user.
--------------------------------------------------------------------------------------
4771 MESSAGE File size cannot be negative (SDWARN 4771)
CAUSE The file-size attribute of the FILE entity is negative.
ACTION No file size will be included in the SELECT statement. The
file-size attribute of the FILE entity should be modified to a
non-negative integer value.
--------------------------------------------------------------------------------------
4772 MESSAGE Inconsistent blocking min/max values (SDWARN 4772)
CAUSE 1. The blocking-min attribute of the FILE entity is a negative
number.
2. The blocking-max attribute of the FILE entity is a negative
number.
3. The blocking-max attribute is positive, and is less than the
blocking-min attribute.
ACTION 1. No BLOCK CONTAINS clause will be generated. The
blocking-min attribute of the FILE entity should be modified to
a non-negative integer value.
2. No BLOCK CONTAINS clause will be generated. The
blocking-max attribute of the FILE entity should be modified to
a non-negative integer value.
3. A BLOCK CONTAINS clause will be generated, however, the
blocking-min value will be used as the blocking-max value. The
blocking-min and/or blocking-max attributes should be modified
so that the blocking-max is greater than the blocking-min.
--------------------------------------------------------------------------------------
(cont.)
--------------------------------------------------------------------------------------
4773 MESSAGE Inconsistent min/max record size values (SDWARN 4773)
CAUSE 1. The min-record-size attribute of the FILE entity is a
negative number.
2. The max-record-size attribute of the FILE entity is a
negative number.
3. The max-record-size attribute is positive, and is less than
the min-record-size attribute.
ACTION 1. No RECORD CONTAINS clause will be generated. The
min-record-size attribute of the FILE entity should be modified
to a non-negative integer value.
2. No RECORD CONTAINS clause will be generated. The
max-record-size attribute of the FILE entity should be modified
to a non-negative integer value.
3. A RECORD CONTAINS clause will be generated, however, the
min-record-size will be used as the max-record-size. The
min-record-size and/or max-record-size attributes should be
modified so that the max-record-size is greater than the
min-record-size.
--------------------------------------------------------------------------------------
4774 MESSAGE Formal file name contains special char's. Name transformed
(SDWARN 4774)
CAUSE The first eight characters of the formal FILE name contain
invalid characters.
ACTION The formal name used in the ASSIGN statement will be transformed
to a valid name by altering each invalid character to a 'x'.
The following are valid characters: a...z, A...Z, 0...9. The
formal name of the FILE entity could be altered to contain only
valid characters.
--------------------------------------------------------------------------------------
4775 MESSAGE File lockword contains special char's. Lockword transformed
(SDWARN 4775)
CAUSE The lockword attribute of the FILE entity contains invalid
characters.
ACTION The lockword will be transformed to a valid lockword by altering
each invalid character to a 'x'. The following are valid
lockword characters: a...z, A...Z, 0...9. The lockword
attribute of the FILE entity should be altered to contain a
valid lockword.
--------------------------------------------------------------------------------------
4780 MESSAGE File rec size is zero or negative. Generated dummy record
(SDWARN 4780)
CAUSE The max-record-size attribute of the FILE entity is zero or
negative.
ACTION The record description for the FD statement will default to PIC
X(2). The max-record-size attribute of the FILE entity should
be modified to a positive integer value.
--------------------------------------------------------------------------------------
(cont.)
--------------------------------------------------------------------------------------
4781 MESSAGE KSAMFILE ksamfile contains no RECORD. No source generated
(SDWARN 4781)
CAUSE No KSAMFILE contains RECORD relationships were found in the
dictionary for the given ksam file.
ACTION No source will be generated for the ksam file until the
relationship(s) are added to the dictionary.
--------------------------------------------------------------------------------------
4782 MESSAGE KSAMFILE ksamfile has no key. No key name generated (SDWARN
4782)
CAUSE No KSAMFILE key ELEMENT relationships were found in the
dictionary for the given ksam file.
ACTION No RECORD clause(s) in the SELECT section will be generated for
the KSAM file until the relationship(s) are added to the
dictionary.
--------------------------------------------------------------------------------------
4783 MESSAGE Formal KSAM file name contains special char's. Name transformed
(SDWARN 4783)
CAUSE The first 8 characters of the formal KSAMFILE name contain
invalid characters.
ACTION The formal KSAMFILE name used in the ASSIGN clause will be
transformed to a valid name by altering each invalid character
to a 'x'. The following are valid characters are: a...z,
A...Z, 0...9. The formal name of the KSAMFILE entity could be
altered to contain only valid characters.
--------------------------------------------------------------------------------------
4784 MESSAGE Boolean not a valid cobol element type. PIC X used! (SDWARN
4784)
CAUSE The element-type attribute retrieved from the dictionary has a
value of "B" , boolean. This is not a valid COBOL type.
ACTION The PICTURE clause is generated with a single alphanumeric
character, PIC X.
--------------------------------------------------------------------------------------
4785 MESSAGE Floating point not a valid cobol element type. PIC X used!
(SDWARN 4785)
CAUSE The element-type attribute retrieved from the dictionary has a
value of "R, D, or E" , floating point. This is not a valid
COBOL type.
ACTION The PICTURE clause is generated with a single alphanumeric
character, PIC X.
--------------------------------------------------------------------------------------
(cont.)
--------------------------------------------------------------------------------------
4790 MESSAGE String not a valid cobol element type. PIC X used! (SDWARN
4790)
CAUSE The element-type attribute retrieved from the dictionary has a
value of "S" , string. This is not a valid COBOL type.
ACTION The PICTURE clause is generated with a single alphanumeric
character, PIC X.
--------------------------------------------------------------------------------------
4791 MESSAGE Invalid edit mask attribute. Generating edit mask! (SDWARN
4791)
CAUSE The edit-mask attribute retrieved from the dictionary contains
invalid characters, and is not a valid COBOL edit mask.
ACTION The edit mask will be generated as if no edit-mask attribute
exists in the dictionary. If a special edit mask is required,
the dictionary edit-mask attribute must be updated.
--------------------------------------------------------------------------------------
4792 MESSAGE Edit mask too long. Remaining characters truncated! (SDWARN
4792)
CAUSE The edit-mask attribute contains more than 30 characters.
ACTION All characters following the 30th character are truncated, and
the remaining 30 characters are validated.
--------------------------------------------------------------------------------------
4793 MESSAGE Sub-elements' total length exceeds parent-element's length
(SDWARN 4793)
CAUSE 1. The total length of all sub-elements is greater than the
length of their parent element.
2. The total length of all sub-elements may not be greater than
the length of their parent element, but the byte-offset
attribute causes the sub-elements to b e placed such that their
adjusted length will be greater than the length of their parent
element.
ACTION 1. The parent's length is assumed to be valid, and generation
continues as if no error had occurred, but the data definition
will cause compile warnings. The parent's length should be
adjusted to include all child elements, or the child elements'
length should be adjusted to fit into the parent element.
2. The parent's length is assumed to be valid, and generation
continues as if no error had occurred, but the data definition
will cause compile warnings. The parent's length should be
adjusted to include all child elements with their current byte
offsets, or the child element byte offsets should be adjusted to
fit into the parent element.
--------------------------------------------------------------------------------------
(cont.)
--------------------------------------------------------------------------------------
4794 MESSAGE Redefining-element's length exceeds redefined entity's length
(SDWARN 4794)
CAUSE 1. The length of the redefining element or record is greater
than the length of the redefined element or record. This can
happen with the ELEMENT redefines ELEMENT or RECORD redefines
RECORD relationship.
2. The length of the redefining element may be greater than the
length of the redefined element or record if a forced redefine
occurs. The byte-offset attribute may force an element to
exceed the length of its parent element or record.
ACTION 1. The length of either the redefining element or record, or
the redefined element or record, must be updated to match the
length of the other element or record.
2. Either the byte-offset attribute or the redefined element or
records length must be updated in the dictionary.
--------------------------------------------------------------------------------------
4795 MESSAGE Multiple ELEMENT references ELEMENT occurrences for
first-element (SDWARN 4795)
CAUSE The element which contains the back reference element type has
more than one ELEMENT references ELEMENT relationship
occurrences in the dictionary.
ACTION The ELEMENT references ELEMENT relationship with the lowest
relationship-position attribute value will be used as the back
referenced element. If this is not the required back reference,
the undesired ELEMENT references ELEMENT relationships must be
deleted from the dictionary.
--------------------------------------------------------------------------------------
4799 MESSAGE Unable to get condition value variable for condition-name
(SDWARN 4799)
CAUSE 1. No CONDITION-VALUE variable attribute exists for the ELEMENT
contains CONDITION-NAME relationship.
2. The CONDITION-VALUE variable attribute has a length of zero.
ACTION 1. No level-88 definition will be generated for the
relationship until a CONDITION-VALUE variable attribute is
created.
2. No level-88 definition will be generated for the
relationship until a CONDITION-VALUE variable attribute length
is greater than zero.
--------------------------------------------------------------------------------------
(cont.)
--------------------------------------------------------------------------------------
4800 MESSAGE Unable to get var attribute. No default used! (SDWARN 4800)
CAUSE A System Dictionary error occurred while retrieving the default
attribute for an ELEMENT.
ACTION No VALUE clause is generated for the element. If a serious
System Dictionary error is suspected, notify the Dictionary
Administrator.
--------------------------------------------------------------------------------------
4801 MESSAGE Unable to get var attribute. Created edit mask! (SDWARN 4801)
CAUSE A System Dictionary error occurred while retrieving the
edit-mask attribute for an ELEMENT.
ACTION The edit mask is generated using other attribute values. If a
serious System Dictionary error is suspected, notify the
Dictionary Administrator.
--------------------------------------------------------------------------------------
4802 MESSAGE Invalid sign attribute. Sign clause not created! (SDWARN 4802)
CAUSE The sign attribute retrieved from the dictionary contains an
invalid value.
ACTION No SIGN clause is created for the element. The sign attribute
should be updated to one of the following valid values: LS, LO,
TS, TO, or <blank>.
--------------------------------------------------------------------------------------
4803 MESSAGE RECORD record contains no ELEMENT (SDWARN 4803)
CAUSE No RECORD contains ELEMENT relationships were found for the
given record.
ACTION The record will not be further defined, thus the definition will
produce compiler errors. In order to generate the record
correctly, RECORD contains ELEMENT relationship(s) should be
added to the dictionary.
--------------------------------------------------------------------------------------
4804 MESSAGE Non-numeric default value too long. Truncated! (SDWARN 4804)
CAUSE The default variable attribute contains more than 132
characters.
ACTION The first 132 characters will be used in the VALUE clause. The
default variable attribute should be updated in the dictionary.
--------------------------------------------------------------------------------------
4805 MESSAGE Numeric default value too long. None generated! (SDWARN 4805)
CAUSE The default variable attribute contains more than 20 numbers and
characters.
ACTION No VALUE clause will be generated for the element. The default
variable attribute should be updated in the dictionary.
--------------------------------------------------------------------------------------
4806 MESSAGE Justify not allowed when parent contains level-88 (SDWARN 4806)
CAUSE The JUSTIFY attribute is not allowed for an ELEMENT that is
directly indirectly contained by an ELEMENT that contains a
CONDITION-NAME.
ACTION Either the JUSTIFY attribute must be false, or the ELEMENT
contains CONDITION-NAME relationship must be deleted.
--------------------------------------------------------------------------------------
(cont.)
--------------------------------------------------------------------------------------
4807 MESSAGE Synchronize not allowed when parent contains level-88 (SDWARN
4807)
CAUSE The SYNCHRONIZE attribute is not allowed for an ELEMENT that is
directly or indirectly contained by an ELEMENT that contains a
CONDITION-NAME.
ACTION Either the SYNCHRONIZE attribute must be false, or the ELEMENT
contains CONDITION-NAME relationship must be deleted.
--------------------------------------------------------------------------------------
4808 MESSAGE Usage is COMP not allowed when parent contains level-88 (SDWARN
4808)
CAUSE The ELEMENT-TYPE attribute values I, J, or K are not allowed for
an ELEMENT that directly or indirectly contained by an ELEMENT
that contains a CONDITION-NAME.
ACTION Either the ELEMENT-TYPE attribute must be modified, or the
ELEMENT contains CONDITION-NAME relationship must be deleted.
--------------------------------------------------------------------------------------
4809 MESSAGE Usage is COMP3 not allowed when parent contains level-88 (SDWARN
4809)
CAUSE The ELEMENT-TYPE P is not allowed for an ELEMENT that is
directly or indirectly contained by an ELEMENT that contains a
CONDITION-NAME.
ACTION Either the ELEMENT-TYPE attribute must be modified, or the
ELEMENT contains CONDITION-NAME relationship must be deleted.
--------------------------------------------------------------------------------------
4810 MESSAGE Invalid numeric default value. None generated! (SDWARN 4810)
CAUSE The default variable attribute contains more than 18 numbers, or
more than 2 edit characters.
ACTION No VALUE clause will be generated for the element. The default
variable attribute should be updated in the dictionary.
--------------------------------------------------------------------------------------
4811 MESSAGE Numeric picture exceeds 18 digits. PIC X used! (SDWARN 4811)
CAUSE The generated edit mask allows more than 18 digits. The
byte-length attribute must not exceed 18 for numeric elements.
ACTION The PICTURE clause is generated with a single alpha-numeric
character, PIC X. The byte-length attribute should be updated to
a positive value not exceeding 18, in the dictionary.
--------------------------------------------------------------------------------------
4812 MESSAGE Expected byte length of 2, 4, or 8. PIC X used! (SDWARN 4812)
CAUSE The byte length attribute must be 2, 4, or 8 for elements of
type I, I+, J, J+, K, and K+.
ACTION The PICTURE clause is generated with a single alpha-numeric
character, PIC X. The byte-length attribute should be updated in
the dictionary to one of the following values: 2, 4, or 8.
--------------------------------------------------------------------------------------