Text |
Object cross-reference displayed. |
Explanation |
The cross-reference of the requested objects has been displayed. |
Text |
Internal error. |
Explanation |
An internal error has occured. |
Action |
Contact sag support. |
Text |
Unknown language in preprocessor found. |
Explanation |
A unknown language was found by the preprocessor. The preprocessor terminates abnormally. The preprocessor accepts two input data fields: 1. language 2. program id valid languages are : BAL and ASM,ASSEMBLER COBOL P,PLI,PL1,PL/1,PL/I COBOL,BAL and ASSEMBLER may be truncated. |
Action |
Correct input data and restart the preprocessor. |
Text |
No source code as input found. |
Explanation |
No source code found on work file 1. |
Action |
Check work file 1. |
Text |
No defaults defined. See DDA. |
Explanation |
For an unknown reason the default record is missing. |
Action |
See DDA. The DDA can add the default record via the DDA services. |
Text |
To many entries for this command. |
Explanation |
The number of parameters for a command is restricted. Possibile missing end-exec. The command COPY,FORMAT-BUFFER has 2 parameters The command GENERATE has 12 parameters The command PROGRAM-ID has 1 parameter. |
Action |
Check parameters. |
Text |
Entry name to long. |
Explanation |
The given entry was to long. The entry is skipped. |
Action |
Check entry name. |
Text |
Invalid command in preprocessor. |
Explanation |
Valid preprocessor commands are only : COPY GENERATE FORMAT-BUFFER PROGRAM |
Action |
Verify command. |
Text |
Unknown keyword. |
Explanation |
The entered keyword was not correct. Keyword skipped. |
Action |
Verify keyword. |
Text |
No program name found. |
Explanation |
The preprocessor needs a program name to store the active records. The program name can be specified via: INPUT (second parameter) Preprocessor statement (EXEC Adabas PROGRAM-ID...) Source language statement (see documentation) |
Action |
Check source code or specify a program name via input. |
Text |
Numeric data expected. |
Explanation |
The preprocessor expected a numeric data field, but it was not numeric. |
Action |
Check input data. |
Text |
Keyword out of sequence. |
Explanation |
The keywords of a PREPROCESSOR command are in the wrong sequence. |
Action |
Correct sequence of keywords. |
Text |
File not found. |
Explanation |
The given file-id is not (or no longer) defined in Predict. |
Action |
Verify the file-id. |
Text |
No member generated. |
Explanation |
For the file was no member generated in Predict. So the copy function could not be executed. |
Action |
Generate a member for the file and restart the preprocessor or use the generate option of the preprocessor. |
Text |
More than 1 member generated. |
Explanation |
For this file more than 1 members are generated, but the member, which should be taken, not specified. |
Action |
Specify a member and restart the preprocessor. |
Text |
Member for this file must be regenerated. |
Explanation |
The file is modified after generation and so the member(s) must be regenerated. |
Action |
Regenerate member and restart the preprocessor. |
Text |
Member not generated for this file. |
Explanation |
The specified member name is not in the generated copy code list of the file. |
Action |
Verify which members are generated for the file and restart the preprocessor. |
Text |
No change allowed by DDA. |
Explanation |
The DDA has decided that this value should not be overwritten by the user. The preprocessor has set the value to the default value. |
Action |
If necessary modify the default value. |
Text |
Buffer name invalid. |
Explanation |
The specified buffer name in the command GENERATE or FORMAT-BUFFER must be vaild according to the rules of the used language in the preprocessor. |
Action |
Specify a correct buffer name and restart the preprocessor. |
Text |
Duplicate field names generated. |
Explanation |
During generation one or more fields with the same name have been generated. This error may occure because the resulting length of the field name including prefix and suffix is longer than 32 characters and is truncated to 32 characters. |
Action |
Regenerate with a shorter prefix and a shorter suffix. |
Text |
Invalid level number generated. |
Explanation |
The generate level was to high for cobol(greater than 49). |
Action |
Do not specify such a high start-level and level-increment. |
Text |
Invalid field name generated. |
Explanation |
The generated field names are not correct for the source language and the validation character was set to blank. |
Action |
Specify a synonym for the invalid fields or specify a validation character. |
Text |
Field without occurrences found. |
Explanation |
At least 1 periodic group or multiple value field has been found without an explicit occurrence number. If the file is an Adabas file or an userview the default occurrence number of 99 or 191 is assumed for periodic groups or multiple value fields respectively. In all other cases a default of 1 is assumed. |
Action |
Supply a value for maximum number of occurrences on field level if defaults are not suitable. |
Text |
Fields not initialised. |
Explanation |
Periodic-group-field and multiple-value-fields can not be initialised by the value clause. |
Text |
Fields with wrong format generated. |
Explanation |
Fields with wrong format are generated. For example in COBOL the BIT format is not allowed and therefore a CHARACTER format is generated. This message is a warning. Check the generated formats and change it if necessary. |
Action |
Check generated format. |
Text |
Field names truncated. |
Explanation |
If the names are to long they have been truncated. If you want to eliminate the truncation use only short names. |
Text |
Filler generated. |
Explanation |
If no name could be found for an object, because there are only invalide characters, a filler is generated. This message is a warning. |
Action |
Check object name and change it if necessary. |
Text |
The generated code is missing. |
Explanation |
The generated code for the copy function was not found. Possibily the code is purged by the user. |
Action |
Generate/regenerate the member for the file in Predict and restart the preprocessor. |
Text |
More than one file found. |
Explanation |
For the specified search criteria more than one file was found. This message is a warning. |
Action |
Specify the search criteria. |
Text |
File name not specified. |
Explanation |
For the commands COPY,GENERATE,FORMAT-BUFFER the file name must be specified. |
Action |
Restart the preprocessor with a specified file name. |
Text |
File must be recovered. |
Explanation |
A transaction is aborted and therefore the file must be recovered. Use the DDA services to recover the file. |
Action |
Use the DDA service function to recover the file. |
Text |
No generation for conceptual file. |
Explanation |
With a conceptual file you cannot start the generation function. |
Action |
Use another file type for generation. |
Text |
Start level must be 1 thru 40. |
Explanation |
It is not possible to specify a start level greater 40. |
Action |
Verify the value for the start level. |
Text |
Level increment must be 1 thru 40. |
Explanation |
The specify level increment must be in the value range 1 thru 40. |
Action |
Correct the value of the level increment and restart preprocessor. |
Text |
Number of comments must be less than or equal to 16. |
Explanation |
The maximal number of comments is 16. More comments are not allowed. |
Action |
Modify the number of comments and restart the preprocessor. |
Text |
Please enter "Y" or "N". |
Explanation |
You must specify for the input data "Y" or "N". |
Action |
Correct input data. |
Text |
Truncation may only be left, rigth or middle. |
Explanation |
The truncation of object name is possible in following ways: "R" - right positions are truncated "L" - left positions are truncated "M" - middle positions are truncated. |
Action |
Specify one of this 3 truncation modes. |
Text |
Format buffer only possible for files of type "A" or "U". |
Explanation |
Only for Adabas files and userviews a format buffer can be generated. |
Action |
Do not try to generate a format buffer for other files. |
Text |
Increment + start level must be < 49. |
Explanation |
The sum of the specified values for the start and increment level must less than 49. |
Action |
Modify the values of start and increment level. |
Text |
Invalid truncation character. |
Explanation |
A invalid truncation character was specified. |
Action |
Verify the truncation character. |
Text |
No program documentation available. |
Explanation |
The DDA specified in the system defaults that every entry must be described. The preprocessor checks this constraint and rejects the function, if no documentation is available. |
Action |
Enter a Predict documentation. |
Text |
Object must be edited. |
Explanation |
If you modify an object and the variable for the edit object in the DDA-Service is set to "Y" or "F", you must edit this object. |
Action |
Change variable in DDA-services or edit this object |
Text |
Field will be marked non standard. |
Explanation |
A field will be marked as NON-STANDARD, i.e. it is no longer connected to a standard file and the field will not be modified via rippling process. |
Text |
Type must be blank for PE counter. |
Explanation |
Enter blank for element type. |
Text |
No override in VSAM. |
Explanation |
No override of format and length in VSAM is allowed. |
Text |
Edit mask only allowed for Adabas files and its Userviews. |
Explanation |
The definition of edit masks is only allowed for Adabas files and Userviews. |
Action |
Enter the edit masks in the Adabas file or in the Userview. |
Text |
Edit mask must be E1 thru E15. |
Explanation |
Only edit mask E1 thru E15 allowed. |
Action |
Check used edit mask and correct error. |
Text |
VSAM requires occurrence for PE/MU-FIELDS. |
Explanation |
The number of occurrences for a periodic group or a multiple field of VSAM file is required. |
Action |
Specify number of occurrences. |
Text |
Occurrence number must be same as in master-field. |
Explanation |
The number of element-occurrences in a VSAM userview must equal to the occ. of the master-field. |
Action |
Enter the valid number of occurrences. |
Text |
No occurrence allowed. |
Explanation |
The specification of occurrences is only allowed, if the field type is MU or PE. |
Action |
Enter blank for number of occurrences. |