Text |
Duplicate file number for physical DDM not allowed. |
Explanation |
A file number for a physical VSAM DDM may only be used once. |
Action |
Use another file number or specify "yes" for a replace option. |
Text |
File related to user DDM does not exist. |
Explanation |
A VSAM user DDM is related to physical VSAM DDM, which does not exist. A logical user DDM must have the same file number than the physical file. |
Action |
Correct the file number or create an appropriate physical VSAM DDM. |
Text |
There is no physical file with the given number. |
Explanation |
A VSAM DDM logical refers to a physical VSAM DDM which does not exist. |
Action |
Create an appropriate physical VSAM DDM, or logically relate the DDM to another physical VSAM DDM. |
Text |
Logical file must be of type KSDS or VRDS. |
Action |
Change the logical file type. |
Text |
File number missing for related physical file. |
Action |
Enter a file number. |
Text |
DDM too large, not enough size. |
Explanation |
A DDM will be temporarily stored in an internal buffer during a CHECK or CAT operation. There is not enough space available to allocate this buffer. |
Action |
Reduce other Natural buffer sizes (e.g. ESIZE), reduce the size of the DDM or contact a Natural administrator. |
Text |
Primary key invalid for ESDS files. |
Action |
Remove the primary-key field. |
Text |
RRDS files must not contain any key. |
Action |
Remove the key. |
Text |
Duplicate long field name ... not allowed. |
Explanation |
There are two DDM fields with the same long name. This is not allowed. |
Action |
Change the long name of the DDM field. |
Text |
... |
Explanation |
No detailed explanation available. |
Text |
KSDS file must contain at least one primary key. |
Action |
Insert a primary key in the KSDS DDM. |
Text |
Alternate index name valid only for types "A", "X". |
Explanation |
An alternate index is specified for a field, but the descriptor column of the field is not marked with "A" or "X". |
Action |
Correct error. |
Text |
Value for ... must be "Y" or "N". |
Explanation |
The value for an input field must be "Y" or "N". |
Action |
Enter "Y" or "N" or contact a Natural administrator. |
Text |
... must not be blank. |
Action |
Enter a value other than blank, or contact a Natural administrator. |
Text |
... must be .... |
Explanation |
No detailed explanation available. |
Text |
Catalog ... disallowed by security definition. |
Explanation |
The user does not have the privileges in Natural Security to catalog this DDM. |
Action |
Contact a Natural Security administrator or change the name of the DDM. |
Text |
Catalog DDM disallowed for SYSDDM utility. |
Explanation |
The user does not have the privileges to catalog a DDM with the SYSDDM Utility. |
Action |
Contact a Natural Security administrator. |
Text |
Code "C" not supported. .... |
Explanation |
An internal error during a call to Natural Security occurred. Natural Security does not know code "C" for the cataloging of DDMs. Natural Security issued a response code. |
Action |
Contact a Natural Security administrator. |
Text |
Duplicate short name ... not allowed. |
Explanation |
It is not allowed for this DDM to use a short name more than once. |
Action |
Change the short name of a field. |
Text |
S-Descriptor ... must not refer to PE/MU field .... |
Explanation |
The master field of a super- or subdescriptor must not be a periodic-group or multiple-value field. |
Action |
Change the super- or subdescriptor. |
Text |
Creator not found in DDM name, check against table not possible. |
Explanation |
The DDM name of an SQL DDM is supposed to consist of the creator name and the table name separated by a "-". If the creator and table name cannot be identified, the SQL DDM cannot be checked against a SQL table. Note that there is no check against the SQL table when you catalog the DDM. |
Action |
Use a DDM name which consists of creator and table name separated by a "-". |
Text |
Return code ... after Adabas LF-command. |
Explanation |
An Adabas LF-command was issued to retrieve the field characteristics of an FDT. A non-zero return code was received after the call. |
Action |
Check the file number of the FDT or contact a Natural administrator. |
Text |
This command is disallowed. |
Explanation |
There was an attempt to perform a function which is disallowed by Natural Security. |
Action |
Contact a Natural Security administrator. |
Text |
Specify table name and creator name. |
Explanation |
Either the creator name or the table name of an SQL table was missing during an attempt to generate a DDM from an SQL table. |
Action |
Issue creator and table name. |
Text |
Table ... created by ... not found. |
Explanation |
The SQL table from which you wanted to create a DDM was not found. |
Action |
Either create the SQL table or issue the correct creator and table name. |
Text |
Too many columns for view (< 750). |
Explanation |
The SQL table from which you wanted to generate a DDM has too many columns. The maximum number of columns is 750. |
Action |
Reduce the number of columns in the table. |
Text |
Error ... parsing SQL View (NATG0301). |
Explanation |
The error occurred during a check of a view for updateable fields. There may be an error in the view definition. |
Action |
Contact a Natural administrator. |
Text |
Table ... has no columns. |
Explanation |
An attempt was made to generate a DDM from an SQL table which has no columns. |
Action |
Contact a Natural administrator. |
Text |
Too many columns - cannot generate short names. |
Explanation |
There is a limited number of short names for key fields and non-key fields in SQL DDMs. The maximum number of one kind of field has been exceeded. |
Action |
Reduce the number of columns in the SQL table. |
Text |
Invalid database number. |
Explanation |
A database number was issued which is not valid in the context. |
Action |
Enter another database number. |
Text |
DDM already defined on database other than :1:. |
Explanation |
You were trying to catalog a DDM whose name already exists;
however, the existing DDM is for a different database than :1:.
:1: could be: CNX for SQL databases accessed via NSB, or
DB2 for SQL databases accessed via NDB/NSQ.
|
Action |
Remove the existing DDM manually and catalog again, or generate the new DDM in a different FDIC file. |
Text |
DB2 not active, DDM cannot be tested. |
Explanation |
An attempt was made to check a DB2 DDM against the DB2 database, but Natural found that DB2 is not active. |
Action |
Contact a Natural administrator. |
Text |
Null indicator must be of type I2. |
Explanation |
A null indicator is not of the required type and length. |
Action |
Change format and/or length of the null indicator. |
Text |
Invalid format or length in LOB or long alpha field. |
Explanation |
LOB fields may have the format "A", "B" or "U". The maximum length for format "A" or "B" is 1073741824. The maximum length for format "U" is 536870912. Long alpha fields may have the format "A" or "U". The maximum length for format "A" is 16381. The maximum length for format "U" is 8190. |
Action |
Specify the correct format/length. |
Text |
Null indicator is a descriptor. |
Explanation |
The null indicator is defined as a descriptor, but the null-indicator field in the DDM is not a descriptor. |
Action |
Define the null-indicator field of the DDM as a descriptor. |
Text |
Null indicator could not be related to a field. |
Explanation |
Possible reasons for this message: - The short name of a field and the short name of the corresponding null indicator must be equal. - A null indicator must be preceded by its related DB field. |
Action |
Change short name or position of null indicator. |
Text |
Invalid null indicator field name. |
Explanation |
The long name of a null indicator must be the long name of the corresponding field prefixed by N@. On mainframe platforms, "@" is the character with the hexadecimal value H"7C". |
Action |
Change the long name of the null indicator. |
Text |
Format must be binary (B). |
Explanation |
The format of a field was found to be binary during the check of the DDM against the database. |
Action |
Set the format of the field to binary. |
Text |
Field is not defined as LOB field in Adabas. |
Explanation |
The DDM field is marked with the field option "LB", which indicates that the field is an Adabas LOB field. However, the field is not defined as an LOB field in Adabas. |
Action |
Regenerate the DDM; or change the field option on the extended field editing map, activated with the .e line command. |
Text |
Field is not defined as a long alpha field in Adabas. |
Explanation |
The DDM field is marked with the field option "LA", which indicates that the field is an Adabas long alpha field. However, the field is not defined as a long alpha field in Adabas. |
Action |
Regenerate the DDM; or change the field option on the extended field editing map, activated with the .e line command. |
Text |
CMZUL ... with response code .... |
Explanation |
There has been an error calling the CMZUL editor. |
Action |
Contact a Natural administrator. |
Text |
Invalid file number. |
Explanation |
A file number in the range from 1 to 5000 must be entered. |
Action |
Enter a valid file number. |
Text |
CICS file name missing. |
Explanation |
No detailed explanation available. |
Text |
Only K,E,R,V (file-org); Y,N (compress); F,C (zone) allowed. |
Explanation |
No detailed explanation available. |
Text |
Y (compress) only allowed for KSDS, ESDS and VRDS files. |
Explanation |
No detailed explanation available. |
Text |
Invalid command, please enter valid command. |
Explanation |
A command has been entered which is not valid. |
Action |
Enter a valid command. |
Text |
Element length cannot be greater than .... |
Explanation |
A length for a field has been entered which is longer than the maximum for this field type. |
Action |
Check and enter correct length. |
Text |
Function cancelled. |
Explanation |
A function has been cancelled by the user. |
Action |
No action required. |
Text |
:3: :1: invalid for :2: tables. |
Explanation |
The specified database ID/logical file :1: is invalid for the SQL table
of type :2:.
:2: can be: - CNX for tables accessed via NSB or
- DB2 for tables accessed via NDB or NSQ.
The SQL type associated with a database ID is defined by the NDBID
macro of the NDB parameter module.
:1: is either the Lfile number or the database ID.
:3: is either "Logical File" or "Database ID".
|
Action |
Enter or select a valid database ID for this type of table. |
Text |
Not allowed to write a Super Natural user file. |
Explanation |
A Super Natural user file will be generated by a Super Natural application. You can read or list the file and store or backup it with another file type. But it is not allowed to change it, because the Super Natural application which uses the file may not longer run. |