| Text | Length of record to be sorted exceeds 10240 bytes. |
| Expl. | The total length of the record to be sorted must not exceed 10240 bytes. Note: The fields written to sort storage are not only those fields specified in the SORT statement, but all database fields and user-defined variables defined before the SORT statement. |
| Actn. | Ensure that the sort record does not exceed 10240 bytes. |
| Text | Generation of format buffer fails. Reason code .... |
| Expl. | During the generation of format buffers, the following error situation occurred. Reason code descriptions: 4 - The generation buffer overflowed and the buffer could not be enlarged because there was not enough memory available. Ac.==> Start Natural in a larger thread/partition/region. 8 - Length of generated format buffer exceeds maximum of 32 KB. Ac.==> Reduce the number of fields in the format buffer. 12 - At runtime, a format buffer could not be expanded because there was not enough memory available. Ac.==> Start Natural in a larger thread/partition/region. 16 - At runtime, the storage needed to create the record buffer for a MULTI-FETCH database call could not be obtained. Ac.==> Start Natural in a larger thread/partition/region. |
| Actn. | See reason code descriptions above. |
| Text | Storage overflow at execution time. |
| Expl. | Storage overflow while creating a loop-table entry. |
| Actn. | Divide program into segments using "structured
programming" techniques. |
| Text | Too many <MOVE " " TO variable> in program. |
| Expl. | The program contains too many <MOVE " " TO
variable> statements. |
| Actn. | Replace the statements with <RESET variable>. |
| Text | Natural nucleus does not support Version 1.2 runtime. |
| Expl. | The Natural nucleus was linked without the Version 1.2 runtime
system. Only Natural objects cataloged/stowed with Natural Version 2 or above can be executed. |
| Actn. | Relink Natural nucleus with Version 1.2 runtime system and
activate the new copy in your environment. |
| Text | Generation of record buffer failed. Reason code .... |
| Expl. | During the generation of a database statement, the following
error situation occurred. Reason code description: 4 - Under Natural for Open Systems: The record buffer size of an Adabas access statement exceeds 64 KB. 4 - Under Natural for Mainframes: The record buffer size of a database access statement directed to Adabas Version 7 (or below) or to VSAM exceeds 32 KB. A record buffer size greater than 32 KB is only permitted if the called database is defined as Adabas V8 (see Profile Parameter DB). 8 - For DB2/SQL access statements the record buffer size exceeds the maximum of 32 KB. |
| Actn. | Reduce the number of record buffer fields. |
| Text | Data buffer ... not expandable while NATXCAL is active. |
| Expl. | When a subprogram is invoked via the 3GL interface (NATXCAL,
NCIXCALL, NCIXCPRM), a data buffer cannot be expanded if one of the data fields residing in this buffer was supplied as a parameter with the CALL statement that has invoked the 3GL program. One of the following data buffers may be affected: AIVDAT - buffer for AIV variables, GLBUSER - buffer for user global variables, GLBSYS - buffer for system global variables, DATSIZE - buffer for local variables. |
| Actn. | If the buffer indicated is "DATSIZE", start Natural with an increased value for the DATSIZE profile parameter. |
| Text | Insufficient core for CALL, SORT, WORK FILE statements. |
| Expl. | The processing of CALL, SORT and WORK FILE statements requires buffers in the partition. The partition does not have enough memory allocated for the storage requirements of the program. |
| Actn. | Re-submit in larger partition or contact your Natural
administrator. |
| Text | ... incompatible to mainframe version ... (see ...). |
| Expl. | The statement/keyword used is not compatible with the corresponding mainframe version of Natural. You can avoid this error by setting the compatibility switch referred to in the error message (e.g., the profile parameter V41MFCOMP=ON/OFF). |
| Actn. | Use only compatible statements/keywords, or switch off the compatibility switch. |
| Text | Return code ... from ... user exit .... that caused Natural to discontinue program execution. |
| Expl. | The user exit detected a condition that prevented the completion
of the operation. The condition has been indicated to Natural by means of a return code. The return code is specific to the user exit. Natural program execution has been terminated. |
| Actn. | Contact your Natural administrator or the author of the specified
user exit. |
| Text | ESCAPE (TOP) not allowed in ON ERROR or AT block. |
| Expl. | This error may be caused by one of the following: 1. An ESCAPE statement was used to exit from a currently active ON ERROR block. However, an ON ERROR block must be exited with a FETCH, STOP, TERMINATE or RETRY statement. 2. An ESCAPE TOP statement was used within one of the following conditions: - AT BREAK - AT START OF DATA - AT END OF DATA |
| Actn. | Correct error in program. |
| Text | Too many parameters in CALL statement. |
| Actn. | Reduce number of parameters in CALL statement. |
| Text | Program ... cannot be loaded .... |
| Expl. | The specified external program could be neither loaded
dynamically nor located statically. See the supplied operating-system/TP-monitor return code of the failing LOAD request for details. Possible reasons: - The program to be loaded dynamically is not contained in the load libraries currently defined to Natural. - Under CICS: The program is not defined to CICS. - There was not enough storage available to load the program dynamically (under Com-plete: the Com-plete thread was too small). - The limit for the number of programs to be dynamically loaded was exceeded. - For static programs: The program is not defined in NATPARM with the CSTATIC parameter or not linked to the NATPARM module. |
| Actn. | Make sure that the program is contained in a library available to or linked to Natural. Contact your Natural administrator concerning the setting of the Natural profile parameters CDYNAM and CSTATIC. |
| Text | Maximum call level reached. |
| Expl. | Natural supports calls to other Natural objects up to level 99. Whenever a Natural object invokes another Natural object (e.g. via CALLNAT, INPUT MAP, PERFORM, FETCH RETURN), the level counter *LEVEL is incremented by one. When *LEVEL exceeds 99, this error is issued. This error usually occurs when an object calls itself recursively. |
| Actn. | Check program and correct error. |
| Text | Buffer pool not active. |
| Expl. | Natural Version 2 requires an active buffer pool manager. |
| Actn. | Contact your Natural administrator. |
| Text | Invalid program call (:1: :2: :3:/:4:/:5:/:6:). |
| Expl. | The Natural object :3: (of type :2:, loaded from library :4:, database :5:, file number :6:) cannot be invoked by statement or command :1:. |
| Actn. | Invoke Natural objects by the appropriate statements/commands. |
| Text | Command invalid in this context (:1: :2: :3:). |
| Expl. | The command :1: is invalid for object :3: of type :2:. |
| Actn. | Consult the documentation and try again. |
| Text | GDA does not correspond to using program. |
| Expl. | Each time a program uses a GDA (global data area), Natural checks whether the compilation time of the program is later than the compilation time of the GDA. If it is not, Natural assumes that the GDA may not correspond to the layout generated into the program and produces this error. |
| Actn. | Recompile program and restart system. |
| Text | Only objects of type "program" can be "RUN". |
| Expl. | A RUN command was issued for a Natural object which is not a
source program; or the RUN command was issued without a program name, and the editor work area was not empty and set to a type other than "PROGRAM". To test the execution of a subprogram or subroutine, you have to catalog/stow this object and write a program that calls this object (with a CALLNAT or PERFORM statement respectively). A map can be tested in the map editor, as can helproutines and helpmaps. GDA, LDA and PDA define data areas and their initialization values and only become executable when referenced in the DEFINE DATA statement of a Natural object. |
| Actn. | Check that the work area contains a program, and that the editor
type is set to "PROGRAM", or that the specified object is a program, or follow the above hints to test objects of other types. |
| Text | FETCH RETURN statement rejected by Natural Security. |
| Expl. | A program called via a FETCH RETURN statement is security
protected and, therefore, cannot be called from another Natural program. |
| Actn. | Contact your Natural or Natural Security administrator. |
| Text | Program can only be executed from a SYS* library. |
| Expl. | This program is security protected and can only be executed from a SYS* library. (SYSTEM is not treated as a SYS* library.) |
| Actn. | Log on to the correct library. |
| Text | Program cannot be executed in batch mode. |
| Expl. | An attempt was made to execute in batch mode a program that contains online functions/features. |
| Actn. | Execute the program in interactive mode. |
| Text | Program cannot be executed online. |
| Expl. | An attempt was made to execute in interactive mode a program that contains functions/features only available in a batch mode environment. |
| Actn. | Execute the program in batch mode. |
| Text | CMSYNIN job control definition is missing. |
| Expl. | In batch mode execution, the DD statement for the definition of the main command and source input for Natural is missing. No commands can be read. |
| Actn. | Specify definition for the CMSYNIN file in the job control. |
| Text | Program version error. |
| Expl. | The executing program has been recataloged by another user between screen I/Os (that is, it is possible that the program has been stowed by a second user while a first user is still using it). |
| Actn. | Contact your Natural administrator. |
| Text | GDA time-stamp conflict. |
| Expl. | This error occurs if a program references a global data area
(GDA) which was recataloged or a GDA that has been moved from another environment after the program has been cataloged. Also the program that references the GDA could have been moved from a different environment into the current one causing a GDA time-stamp conflict. If a GDA is cataloged again, all objects which reference the GDA must also be cataloged again. |
| Actn. | Check the program structure and recatalog if necessary, or use
the profile parameter RECAT=ON. RECAT=ON is not possible for programs cataloged with the Natural Optimizer Compiler. |
| Text | GDA ... conflicts with active GDA .... |
| Expl. | A Natural Version 2 program attempted to allocate a global data
area within an application where Natural Version 1.2 programs have used global variables which are not defined via a COMMON global data area. |
| Actn. | Use the CREATE GLOBALS command to define a COMMON global data
area with the global variables of the Natural Version 1.2 programs. |
| Text | Conflicting number of parameters (:1: :2:/:3:/:4:/:5:). |
| Expl. | The number of parameters defined in object :2: (of type :1:,
loaded from library :3:, database :4:, file number :5:) does not correspond to the number of parameters used to invoke the object. |
| Actn. | Check program and correct error. |
| Text | Format/length conflict in parameter :1: (:2: :3:/:4:/:5:/:6:). |
| Expl. | The parameter defined at position :1: in object :3: (of type :2:, loaded from library :4:, database :5:, file number :6:) does not match the format/length of the corresponding parameter used to invoke it. The following conditions must be met: - The formats must be equal. - The lengths must be equal. - The precisions must be equal. |
| Actn. | Check program and correct error. |
| Text | Wrong array defined in param. :1: (:2: :3:/:4:/:5:/:6:). |
| Expl. | The array defined as parameter at position :1: in object :3: (of type :2:, loaded from library :4:, database :5:, file number :6:) does not match the array or array range used as corresponding parameter to invoke it. The following conditions must be met: - The ranks must be equal. - The occurrences of each dimension must be equal. This error also occurs if a 3GL routine calls a subprogram, and the subprogram"s PDA specifies a variable array range (1:V). |
| Actn. | Check program and correct error. |
| Text | Prot. param. :1: used as target field (:2: :3:/:4:/:5:/:6:/). |
| Expl. | The parameter defined at position :1: in object :3: (of type :2:, loaded from library :4:, database :5:, file number :6:) is used as a target operand. However, this parameter is protected: it is a constant, or it has the attribute (AD=ON), and must not be modified. |
| Actn. | Check program and correct error. |
| Text | Natural editor is not linked and cannot be loaded. |
| Expl. | The Natural editor modules are not linked and cannot be loaded. |
| Actn. | Contact your database administrator. |
| Text | This terminal command is not supported. |
| Expl. | Terminal commands for screen paging cannot be used under every TP monitor. |
| Actn. | Enter a valid command. |
| Text | Invalid size for screen-paging system file. |
| Expl. | A screen-paging command was entered, but the size of the system file used for screen paging was "0", which means that no screens can be stored. |
| Actn. | Restart Natural session with valid size for screen-paging system
file. |
| Text | Invalid use of hardcopy facility. |
| Expl. | The Natural hardcopy facility is only available under the TP monitor Com-plete. |
| Actn. | Enter a valid Natural command. |
| Text | Screen paging open function failed. |
| Actn. | Check the status of the screen-paging system file. |
| Text | Screen paging record overflow. |
| Expl. | An attempt was made to write to the screen-paging system file a record which was larger than the screen page size. |
| Actn. | Increase the size of the physical terminal buffer. |
| Text | Screen paging write failed. |
| Expl. | An error occurred during an attempt to write a screen to the screen-paging system file. |
| Actn. | Check the status of the screen-paging system file. |
| Text | Screen paging read failed. |
| Expl. | An error occurred during an attempt to read a screen from the screen-paging system file. |
| Actn. | Check the status of the screen-paging system file. |
| Text | Abnormal end due to unhandled LE condition .... |
| Expl. | During the execution of an LE (IBM Language Environment)
subprogram, an error condition has occurred. As no condition handler was active in the subprogram to handle the error, control has been passed to the Natural LE condition handler, which calls LE services to write an LE snap dump to CEEDUMP and to issue more detailed LE error messages. |
| Actn. | Check the LE error condition, the messages and the snap dump to
find out the reason of the error. If necessary, correct the LE subprogram. |
