| Text | No data defined in program. |
| Expl. | The program (or subprogram, subroutine, helproutine) to be
displayed in the top half of the editing screen does not contain any explicit field definitions. |
| Actn. | Check program to be displayed, and have the data area used by the program displayed to see the desired variables. |
| Text | Field/parameter type is missing. |
| Expl. | Field/parameter type must be specified. |
| Actn. | Enter a field/parameter type. |
| Text | Do not enter starting value for an index which is "0". |
| Expl. | For a dimension whose index is "0" you cannot specify a "Starting from" value. |
| Actn. | Either specify an index, or remove starting value. |
| Text | Dynamic layout not possible for WRITE statement. |
| Expl. | You cannot use a dynamic layout map for a map that is to be
output via a WRITE statement. |
| Actn. | Correct error. |
| Text | Verification name already exists, but is not a free rule. |
| Expl. | The verification you have specified already exists and is defined in Predict as an automatic rule. |
| Actn. | Specify other verification name. |
| Text | Rejected by Predict defaults. |
| Expl. | The switch "Rule in Map Editor" in the Predict Defaults
is set to "D" (disallowed). |
| Actn. | Ask your Predict administrator to change the default. |
| Text | Do not enter a rule name and source text at same time. |
| Expl. | Enter either a free rule name to include the rule source from Predict into the rule editor, or enter source text, press ENTER and then enter a rule name to save the source in Predict. |
| Actn. | Remove either the rule name or the source text and press ENTER again. |
| Text | Do not apply a processing rule to an output field. |
| Expl. | A processing rule that is attached to an output field is not executed. |
| Actn. | Remove the processing rule or change the field class. |
| Text | Internal error...while searching library path for object. |
| Expl. | An unexpected internal error occurred while searching for an
object in the current library and concatenated libraries. |
| Actn. | Contact Software AG support. |
| Text | Table overflow, too many variables defined. |
| Expl. | The number of variables in a map has been exceeded. The maximum
number is 500 variables. |
| Actn. | Reduce the number of variables to fewer than 501. |
| Text | Map contains GUI elements and cannot be stowed via CATALL. |
| Expl. | The map contains GUI elements. The "stow" was not
executed, because it would have destroyed the original map source. The map has been loaded from a GUI-supporting platform and contains elements like bitmaps, selection boxes, drop-down menus and the like, which are not available on a mainframe platform. If such a map were stowed, all these elements would be removed to generate a mainframe-compatible map. In normal edit mode, when you attempt to stow the map, you will be warned about the loss of elements, but can proceed to stow the map (if the loss is acceptable to you). |
| Actn. | Either STOW the map individually (not with the CATALL command), or use the CATALOG function only. |
| Text | Invalid array range. |
| Expl. | Invalid array dimension: The lower bound must be smaller than the upper bound. |
| Actn. | Specify different lower or upper bound. |
| Text | Error occurred during migration of a KAPRI map. |
| Expl. | This error message is only issued during CATALL. During the migration process of a KAPRI map, an incorrect box formatting element was found, which could not be applied. |
| Actn. | Migrate the map manually with the SYSMAP utility. |
| Text | XREF request disallowed by Natural Security definition. |
| Expl. | In a Natural Security environment, XREF can only request settings
that provide more detailed information than defined by means of the Natural Security profile that applies. The following table shows the possible combinations (valid combinations marked with "+"): Definition I Request by XREF command in Natural I Security I profile I OFF ON FORCE -------------+----------------------------- OFF I + + + ON I - + + FORCE I - - + |
| Actn. | Check data and correct error, or contact the DBA to modify the appropriate security profile. |
| Text | Function not possible with DBID = 0. |
| Expl. | To generate the Natural cross references the DBID of the Natural system file, where the module is to be stored, must not be zero. |
| Actn. | Contact the DBA to generate a valid Natural parameter module or invoke Natural and overwrite the value of the data base identification dynamically. |
| Text | Invalid input data. |
| Expl. | Invalid data have been specified for the field. |
| Actn. | Specify valid input data. |
