3.3 Message Details

Messages are listed in numeric order.

0001	0002	0004	0007	0009	0010	0012	0015	0016	0018
0019	0020	0022	0024	0026	0029	0031	0032	0033	0034
0035	0062	0070	0071	0072	0078	0079	0081	0085	0086
0087	0096	0097	0099	0101	0102	0103	0104	0105	0106
0107	0200	0201	0202	0204	0206	0208	0211	0212	0214
0221	0222	0223	0224	0225	0250	0251	0252	0253	0254
0260	0261	0262	0263	0301	0302	0310	0311	0313	0320
0321	0322	0323	0324	0325	0326	0327	0328	0330	0331
0340	0350	0360	0362	0363	0364	0370	0371	0372	0373
0374	0375	0376	0400	0410	0600	0601	0608	0609	0612
0613	0614	0615	0616	0701	0702	0703	0704	0705	0724
0725	0726	0727	0771	0772	0774	0775	0776	0810	0812
0820	0821	0822	0828	0829	0899	0901	0902	0903	0904
0905	0931	0932	0933	0935

JMP0001I-U

[Linux] OPEN ERROR. FILE=$1.

[Solaris][Linux64] OPEN ERROR. FILE=$1.'$2'

System action

Abnormally terminates the program.

Response

[Linux] Check whether access name ($1) corresponding to function name SYSIN or SYSOUT is assigned correctly. If so, check whether the assigned file attribute is correct.

[Solaris][Linux64] Referring to the character string specified in $2, correct the cause of the error involving the file assigned to the access name ($1) corresponding to the function name SYSIN or SYSOUT. Then retry the operation.

Table 3.2 $2 of JMP0001I-U
$2	Description	Programmer Response
NOT ASSIGNED	No access name ($1) has been assigned.	Assign an access name ($1).
INVALID ASSIGN	The keyword specified for assigning the file for SYSIN or SYSOUT contains an error.	Check whether the character string specified following the file name is valid for an expanded function. (*1)
INVALID PATH-NAME	The path name of the file contains an error.	Check whether the path name of the file is correctly specified.
FILE LOCK	The file assigned for SYSOUT is in the locked state.	Retry the operation. If this locking error frequently occurs, it may be an operational problem.
MEMORY SHORTAGE	There is insufficient memory for opening the file.	Refer to "B.1 Virtual Memory Shortages".
READ ONLY	The file assigned for SYSOUT is a read-only file.	Change the access permission to allow writing to the file.
NOT EXISTED	The file assigned for SYSIN was not found.	Create the file before executing the program.
LOCK FULL	Too many OPEN requests were issued for the same file, and the lock table became full.	Retry the operation. If this locking error frequently occurs, it may be an operational problem. (*2)
THREAD SYNC ERROR (0xXXXX)	Synchronization processing of the thread failed.	Correct the cause of the error according to the system errno explanation.
ERRCD=0xXXXX	Another error occurred.	Correct the cause of the error according to the specified error code.
RMERR=0xXXXX	This indicates an error code received from the runtime system.	Since this is considered a system error, open a support incident to obtain assistance from a supplier.

*1. Refer to " Expanded file input functions of the ACCEPT statement " and "Expanded file output functions of the DISPLAY statement" in the "NetCOBOL User's Guide".

*2 The maximum number of OPEN requests that can be accepted concurrently for the same file is 1024.

JMP0002I-U

PROGRAM '$1' IS RECURSIVELY CALLED.

System action

Abnormally terminates the program.

Explanation

The program ($1) was called, and is re-called before it terminates (before execution of the STOP RUN or EXIT PROGRAM statement).

Response

Check the CALL statement in the called program.

JMP0004I-U

THE LAST STATEMENT IN USE FOR DEAD-LOCK EXECUTED..

System action

Abnormally terminates the program.

Response

Use the STOP RUN statement, EXT PROGRAM statement, or GO TO statement so that the end of the USE FOR DEAD-LOCK procedure will not be reached.

JMP0007I-W

INVALID OPTION. $1.

System action

Ignores the runtime option ($1), and continues processing.

If the specified runtime option is SWITCH, the SWITCH runtime option is enabled as follows:

If the digit count of the number in the specified numeric part is smaller than eight, the number is written left-justified.

If the digit count is greater than eight, the high-order eight digits are valid.

Response

Specify the correct runtime option, then re-execute.

JMP0009I-U

INSUFFICIENT STORAGE AVAILABLE. '$1'

System action

Abnormally terminates the program.

Response

Refer to the system errno explanation for the error code in $1, fix the cause of the error, and then re-execute. For details about the cause and corrective action, refer to "Appendix B Notes".

JMP0010I-U

LIBRARY WORK AREA IS BROKEN.

System action

Abnormally terminates the program.

Explanation

The work area of the COBOL runtime system is broken.

Response

Check the program as follows:

If an item including a subscript, index, reference modification, or OCCURS DEPENDING ON clause is referred to, confirm that the item is within the reference range. This check can be made by specifying the CHECK option.
If a parameter was specified for transferring data via the CALL statement, confirm that the sender and receiver have the same parameter attributes. Especially, check the length attribute.
If a file is used, confirm that the record is referenced in the correct length. For example, if the maximum record length is used instead of the actual record length and the remaining portion is filled with spaces, the record is referenced incorrectly.

JMP0012I-U

INTERNAL PROGRAM IS RECURSIVELY CALLED IN PROGRAM $1.

System action

Abnormally terminates the program.

Explanation

The nested program included in the outermost program ($1) was called, and the nested program is re-called before it terminates (before execution of the STOP RUN or EXIT PROGRAM statement).

Response

Check the CALL statement in the called program.

JMP0015I-U

CANNOT CALL PROGRAM '$1'. $2.

System action

Abnormally terminates the program.

Explanation

Make sure that the program entry information is specified correctly. The error code is set in $2. See "Entry Information for Sub-programs" in the "NetCOBOL User's Guide", "Appendix A COBOL File System Error Codes".

Response

[Linux] If system error code (errno) is output to $2, take action according to the contents. If not output, check the following:
- Whether the entry point is specified in the CALL statement
- Whether the search path is set correctly
- Whether the executable program is created correctly
- Whether enough space is available to load the program

[Solaris][Linux64] Eliminate the cause of the error according to the error code written for $2, then re-execute.

Table 3.3 $2 of JMP0015I-U
$2	Explanation
dlopen-so	Indicates failed loading of a shared object.
dlopen-out	Indicates failed loading of an executable program.
dlsym-so	Indicates failed acquisition of the entry-name from a shared object.
dlsym-out	Indicates failed acquisition of the entry-name from an executable program.

If a subprogram is created as a shared object, see the error message following the strings "dlopen-so" and "dlsym-so".

Also, check the following:

If "dlopen-so" is set:
- Has the appropriate search path (LD_LIBRARY_PATH) been set?
- Has the symbol of the shared object been resolved?
- You can check for an unresolved symbol by specifying the -r option in the ldd command.
- Is there space for loading the shared object?
If "dlsym-so" is set:
- Does the shared object contain the program (entry name) specified in the CALL statement?
- You can check this by using the nm command.
- Has a program (entry-name) consisting of national characters been called?

If the subprogram is in an executable program or the shared object linked through the -l option to the executable program, see the error message following the string "dlopen-out" or "dlsym-out".

Also, check the following:

If "dlopen-out" is set:
- Has the executable program been appropriately created?
If "dlsym-out" is set:
- Does the executable program contain the program (entry-name) specified in the CALL statement? You can check this by using the nm command.
- Was "-l" used to link a shared object containing the program (entry-name) specified in the CALL statement when the executable program was created?

JMP0016I-U

[Linux] READ/WRITE ERROR. FILE='$1'.

[Solaris][Linux64] READ/WRITE ERROR. FILE='$1'. '$2'

System action

Abnormally terminates the program.

Response

[Linux] Check the file assigned in access name ($1).

[Solaris][Linux64] Referring to the character string specified in $2, correct the cause of the error involving the file assigned to the access name ($1), and then retry the operation.

Table 3.4 $2 of JMP0016I-U
$2	Description	Programmer Response
MAXIMUM SIZE	The maximum file size was exceeded.	Take appropriate action, such as splitting the file into multiple files so that no single file exceeds the maximum size.(*1)
NO SPACE	There is insufficient space.	Check the free disk space. If a file capacity limit has been set by a command, increase the limit value and retry the operation.
THREAD SYNC ERROR (0xXXXX)	Synchronization processing of the thread failed.	Correct the cause of the error according to the specified error code. (*2)
ERRCD=0xXXXX	Another error occurred.	Correct the cause of the error according to the specified error code. (*2)
RMERR=0xXXXX	An error code was received from the runtime system.	Since this is considered a system problem, open a support incident to obtain assistance from a supplier.

*1 For details, refer to Table "Functional differences between file systems", in "File Processing", in the "NetCOBOL User's Guide".

*2 For details, see the explanation of errno for the system.

JMP0018I-U

[Linux] CLOSE ERROR.FILE='$1'.

[Solaris][Linux64] CLOSE ERROR.FILE='$1'. '$2'

System action

Abnormally terminates the program.

Response

[Linux] Check the file assigned in access name ($1).

[Solaris][Linux64] Referring to the character string specified in $2, correct the cause of the error involving the file assigned to the access name ($1), and then retry the operation.

Table 3.5 $2 of JMP0018I-U
$2	Description	Programmer Response
NO SPACE	There is insufficient space.	Check the free disk space. If a file capacity limit has been set by a command, increase the limit value and retry the operation.
ERRCD=0xXXXX	Another error occurred.	Correct the cause of the error according to the specified error code.
RMERR=0xXXXX	An error code was received from the runtime system.	Since this is considered a system problem, open a support incident to obtain assistance from a supplier.

JMP0019I-U

EXTERNAL DATA ATTRIBUTE ERROR. DATA='$1'. '$2','$3'

System action

Abnormally terminates the program.

Response

Check to ensure the definition of EXTERNAL data ($1) does not conflict between programs ($2 and $3).

JMP0020I-U

INVALID ENTRY INFORMATION. PGM=$1

System action

Abnormally terminates the program.

Response

Check whether the entry information library file name (.so), program name and the second entry point name of the called program ($1) is correctly defined in the entry information file specified via the environment variable CBR_ENTRYFILE or in the initialization file for execution.

Refer to "Subprogram entry information" in Chapter 4 of the "NetCOBOL User's Guide".

JMP0022I-U

EXTERNAL FILE ATTRIBUTE ERROR. FILE=$1. PGM=$2,$3. '$4'.

System action

Abnormally terminates the program.

Response

Confirm that the program ($2) in which the error was detected and the program ($3) that is first defined the EXTERNAL file ($1) have the same $1 definition. A file name is usually written for $1. If the file name cannot be written, the file definition number that appeared in the source program is written. Tables below shows the contents of $4 of JMP0022I-U.

Table 3.6 $4 of JMP0022I-U(Common file organizations)
$4	Error Contents
ACCESS-MODE	Access mode
ACCESS-NAME	Access name
FILE-ORG	File organization
LOCK-MODE	LOCK MODE clause specification
MAXRL	Maximum record length
MINRL	Minimum record length
OPTIONAL	Presence or absence of OPTIONAL clause specification
REC-MODE	Record format

Table 3.7 $4 of JMP0022I-U(Line sequential file)
$4	Error Contents
REC-ATR	Record item attribute

Table 3.8 $4 of JMP0022I-U(Relative/Indexed file)
$4	Error Contents
ALT-KEY	Number of alternate record keys
KEY-ATR	Key item attribute
KEY-DISP	Displacement of the key item in a record
KEY-DUPL	Presence or absence of DUPLICATES clause specification
KEY-LEN	Key length
REL-ATR	Attribute of the relative key item
REL-COL	Column count of the relative key item
REL-KEY	Presence or absence of RELATIVE KEY clause specification
REL-LEN	Length of the relative key item
REL-NAME	Name of the relative key item

Table 3.9 $4 of JMP0022I-U(Print file)
$4	Error Contents
ADVANCING	Presence or absence of the WRITE statement in which ADVANCING is specified
CHAR-TYPE	Presence or absence of specification of how to write the CHARACTER TYPE clause for format 3
CODE	Presence or absence of specification of the CODE-SET clause
CTLCHR	Attribute of the control statement area
LINAGE	Presence or absence of specification of the LINAGE clause
LNG-ATR	Attribute and column count of the LINAGE data item
LNG1-INTEG	Integer of LINAGE data item 1
LNG1-NAME	Name of LINAGE data item 1
LNG2-INTEG	Integer of LINAGE data item 2
LNG2-NAME	Name of LINAGE data item 2
LNG3-INTEG	Integer of LINAGE data item 3
LNG3-NAME	Name of LINAGE data item 3
LNG4-INTEG	Integer of LINAGE data item 4
LNG4-NAME	Name of LINAGE data item 4
REC-LEN	Record length

JMP0024I-U

USE FOR DEAD-LOCK NOT FOUND.

System action

Abnormally terminates the program.

Response

A deadlock exit subroutine call was executed, but the deadlock exit could not be found in the deadlocked program or a parent program that called the deadlocked program with a CALL statement. Confirm that a deadlock exit is registered using a USE FOR DEAD-LOCK statement.

JMP0026I-W

NO 'ON EXCEPTION' STATEMENT EXISTS, WHEN EXCEPTION OCCURRED ON
'$2 $1' STATEMENT.

System action

Continues processing.

Response

Specify the ON EXCEPTION clause in the $2 (ACCEPT or DISPLAY) statement corresponding to the $1 function name (ARGUMENT-VALUE or ENVIRONMENT-VALUE).

JMP0029I-W

[Linux] ENVIRONMENT VARIABLE LANG AND PROGRAM IN CODE MUST AGREE. $1

[Solaris][Linux64] ENVIRONMENT VARIABLE LANG AND PROGRAM IN CODE MUST AGREE. $1 $2 $3

System action

Terminates the program abnormally.

Response

[Linux] Check the LANG environment variable used at program execution time and the one used at program compile time. The program name is set in $1.
[Solaris][Linux64] Check the LANG environment variable used at program execution time and the one used at program compile time. The program name is set in $1, the code system of the environment variable (LANG) is set in $2, and the COBOL program code system is set in $3.

JMP0031I-U

TWO OR MORE THREADS WERE EXECUTED IN PROCESS MODE.

System action

Abnormally terminates the program.

Response

A possible cause is listed below. Correct the cause of the error, and retry the execution.

The program is not executed with the THREAD(MULTI) compilation option specified.

JMP0032I-U

PROGRAM '$1' CANNOT BE EXECUTED.

System action

Abnormally terminates the program.

Response

The program $1 compiled with the compiler option THREAD (MULTI) specified may have been deleted from memory, the possible causes of which are shown below. Change the program to the dynamic program structure to ensure that it will not be removed from memory or use the CANCEL statement to remove it from memory and then rerun the program.
- The program $1 was removed from memory because it is linked statically or dynamically to a program removed from memory by the CANCEL statement.
- The program $1 was removed from memory by a system function.
Two or more programs having the same entry name exist in a run unit, the possible causes of which are shown below. Eliminate the cause of error and return the program.
- Different programs having the same name exist in the run unit. Change the program names in the run unit such that they are all different.
- A program is statically linked to two or more libraries. Change the link format of the program to be shared to the dynamic link.

JMP0033I-U

COBOL RUN-TIME SYSTEM FOR MULTITHREAD MODEL AND COBOL RUN-TIME SYSTEM FOR PROCESS MODEL CANNOT BE EXECUTED IN THE SAME PROCESS.

System action

Abnormally terminates the program.

Response

Programmer response: The runtime system for multi-thread and the runtime system for the process model cannot be executed in the same process. Confirm that the runtime systems are in the program that operates the process.

JMP0034I-U

THREAD SYNCHRONIZATION FAILED. '$1' .

System action

Abnormally terminates the program.

Response

Remove the cause of error while referring to the character string indicated in $1, then rerun the program. Table "$1 of JMP0034I-U" provides explanations and responses of the character strings indicated in $1.

Table 3.10 $1 of JMP0034I-U
$1	Description	Programmer response
CODE = 0xXXXX	A system error code is indicated.	Determine the cause while referring to the explanation on the system error code and respond accordingly.

JMP0035I-U

THE PROCESS MODEL PROGRAM CANNOT BE EXECUTED IN THE MULTITHREAD MODEL. '$1'

System action

Abnormally terminates the program.

Response

A single thread program ($1) cannot be executed in multithread mode. Determine whether a program compiled with the compiler option THREAD (SINGLE) specified or a program compiled by a COBOL product not supporting the multithread is included, then rerun the program.

JMP0062I-U

CODE CONVERSION LIBRARY CANNOT BE LOADED. $1 $2 $3

System action

Abnormally terminates the program.

Response

Refer to the character string indicated in $1 and $2 and remove the cause of error. Then rerun the program. $1is the type of the code conversion library (ICONV), and $2 is the error code or "INVALID-VL" of the system. $3 indicates an error address.

The type set to $1 shows the code conversion library specified for environment variable CBR_CONVERT_CHARACTER.

Please confirm that the run time system is correctly installed when $1 is ICONV.

JMP0070I-1

RUN-TIME ENVIRONMENT INFORMATION: VERSION='$1' THREAD-MODE='$2' INIT-FILE='$3'

System action

Continues processing.

Response

Because environment variable CBR_CBRINFO = YES is specified, information of the executing program is output. Check the version and level ($1), thread mode ($2), and runtime initialization file name ($3) of the runtime system in progress from the output information. If no runtime initialization file is used, the character string "NONE (EXE=directory-name LIB=directory-name)" indicating the directory searched for in a runtime initialization file is set in $3. For information on using the runtime initialization file, see "Runtime Initialization File" in the "NetCOBOL User's Guide".

JMP0071I-U

LIBRARY WORK AREA DESTRUCTION WAS DETECTED. $1 $2 BRKADR=0x$3.

System action

Abnormally terminates the program.

Response

The runtime system area has been destroyed for some reasons.

[Solaris][Linux64] Investigate the cause of the destruction by referring to "Using the CHECK Function" in the "NetCOBOL User's Guide".

Note that the location where the area destruction has been detected is set in $1, while the program or method name where the area destruction has been detected is set in $2. (The location is either START indicating the start of the program or that of the procedure of the method or END indicating the end.) The address of the area destroyed is set in $3.

JMP0072I-U

Forced terminated for the restriction. '$1' $2

System action

Abnormally terminates the program.

Response

A function which is outside the limits of functions for the current product was used. Review the environment referring to information of $1. A program name or class name and method name are set to $2.

Table 3.11 $1 of JMP0072I-U
$1	Description	Programmer response
PRODUCT-MISSMATCH OBJECT= Development Environment product type RUNTIME= Runtime product type	The runtime product is not equal to the level of the development environment. OBJECT is categorized by Development Environment product types. RUNTIME is categorized by operatable Runtime product types.	Please confirm each Development Environment product type to each Runtime product type.

JMP0078I-U

THE PROGRAM NOT SPECIFIED THE PROGRAM WHICH SPECIFIED COMPILE OPTION RCS(UCS2,BE) WAS EXECUTED IN THE SAME PROCESS. '$1'.

System action

Abnormally terminates the program.

Response

Execution of a program with the "RCS(UCS2,BE)" compilation option specified and a program without that option specified within the same process is unfeasible. Use the same compilation option in both programs.

JMP0079I-U

CANNOT GET ENVIRONMENT INFORMATION. '$1'

System action

Abnormally terminates the program.

Response

While referring to the error code set in $1 and the explanation of errno for the system, correct the cause of the error, and then retry the execution.

JMP0081I-U

THE PROGRAM OF A CHARACTER CODE DIFFERENT IN THE EXECUTION ENVIRONMENT EXISTS. '$1'

System action

Abnormally terminates the program.

Response

Check the operating code system for the program ($1). Use the same code system for the programs operating in the runtime environment.

JMP0085I-U

CANNOT REGISTER THE ENVIRONMENT VARIABLE '$1'.

System action

Abnormally terminates the program.

Response

The environment variable '$1' could not be registered. Correct the runtime initial file so that the statement of the total length of environment variable information used by the corresponding program does not exceed 16 kilobytes, then rerun the program.

Refer to "B.1 Virtual Memory Shortages" for details.

JMP0086I-W/U

CHARACTER CODE CONVERSION FAILED. $1 $2

System action

If there is a character code conversion failure and the severity code of the error message is W, then the default character is passed through and the conversion continues. If the severity code is U, the system abnormally terminates the program.

Response

Data that was not in the range of valid characters for the encode method was encountered. Remove the cause of the error by referring to the error code set in $1 and the error address is set in $2, and then rerun the program.

Table 3.12 $1 of JMP0086I-W/U
$1	Description	Programmer response
E2BIG 7(0x7)	The code row storage was insufficient for the converted data.	Ensure the length of the data item is large enough to handle the converted data.
ENOMEM 12(0xc)	Not enough space.	Refer to "B.1 Virtual Memory Shortages".
EINVAL 22(0x16)	There is an inappropriate code in the origin conversion data row.	Check if the character data of the origin conversion data is not incomplete when moved or partially referred.
EILSEQ 84(0x54)	There is a non-existent code set in the origin conversion data row.	The origin conversion data is outside of code set. Check whether the data item that use different encoding method is not used by overlapping (REDEFINES phrase) or the binary data is stored other than the character-code.

Refer to the system errno explanation for the error code other than the table "$1 of JMP0086I-W/U".

Refer to "CBR_CONVERT_CHARACTER" in the "NetCOBOL User's Guide" for detail of environment variable CBR_CONVERT_CHARACTER.

JMP0087I-I/E/W/U

OPEN OF THE MESSAGE CATALOG FAILED,USE FOR DEFAULT MESSAGE CATALOG. DETAIL='$1'

System action

Opening of the message catalog for outputting execution-time messages failed. Consequently, this message is output and the default message catalog (English) is used to output execution-time messages. The severity code of this message is the same as that of an execution-time message.

Response

While referring to the detailed message of the error specified in $1, check NLSPATH and correct the cause of the error.

JMP0096I-U

[Linux] RUN-TIME INITIALIZATION FILE'S PATH IS INVALID.

[Solaris][Linux64] RUN-TIME INITIALIZATION FILE'S PATH IS INVALID. $1 $2

System action

Abnormally terminates the program.

Response

[Linux] Check whether the path name of the initial file for execution is specified correctly.
[Solaris][Linux64] Confirm that the path name set in $1 is correct. If the path name is correct, refer to the error code set in $2 and the explanation of errno for the system, correct the cause of the error, and retry the execution.

JMP0097I-U

COBOL RUN-TIME SYSTEM IS NOT INSTALLED PROPERLY. FILE=$1.

System action

Abnormally terminates the program.

Response

Confirm the file($1) is correctly installed.

Confirm the runtime system or the environment package is correctly installed.

JMP0099I-U

FORCED TERMINATION. CODE=$1.

System action

Abnormally terminates the program.

Response

Eliminate the cause of the error according to the level U message output before this message. If no level U message was written, check the program for the following:

If referencing an item using a subscript, index, reference modification, or OCCURS DEPENDING ON clause, check that these are within the reference range (these can be checked by specifying the CHECK(ALL) compiler option).
If a statement such as CALL contains a parameter for transferring, check that the parameter attributes on the receiving and sending side match (particularly the length). These can be checked by specifying the CHECK(ALL) compiler option.
If handling a file, check that records are not being referenced with the wrong length (for example, in a variable length input file, check that padding was not inserted using the maximum length when the actual record length should have been processed).

In any other case than those listed above, an internal error probably occurred. Contact Fujitsu Software Support.

The runtime system internal error code is set in $1.

JMP0101I-U

INSUFFICIENT STORAGE AVAILABLE TO CREATE '$1' OF CLASS '$2'.

System action

Abnormally terminates the program.

Response

To allow the environment to create the factory object or object instance ($1) of class ($2), take the action described in "Appendix B Notes", or the following action, then re-execute the program.

If environment variable CBR_InstanceBlock is set to USE (execution performance preferred), reduce the number of instances that can be stored (initial value or incremental value) for the class ($2) defined in the class information file specified for CBR_ClassInfFile. See "CBR_InstanceBlock " and "CBR_ClassInFile" in the "NetCOBOL User's Guide".
Specify UNUSE (memory preferred) for environment variable CBR_InstanceBlock.

JMP0102I-U

CLASS '$1' CANNOT BE USED.

System action

Abnormally terminates the program.

Response

Modify the program or execution environment so that the class used in class initialization can be used. Then re-execute the program.

Possible causes are as follows. See "Cautions", in "Calling Subprogram (Inter-Program Communication)", in "NetCOBOL User's Guide" and "Overview of Program Structure", in "Developing and Executing Object-Oriented Programs", in the "NetCOBOL User's Guide".

The class is implicitly deleted from the memory by the CANCEL statement or equivalent.
Two or more executable files (including libraries) containing the object file in the same class exist in the COBOL runtime.
Different classes with the same class name exist in the COBOL run unit.

JMP0103I-U

CANNOT INVOKE METHOD '$1'. 'CLASS=$2' $3.

System action

Abnormally terminates the program.

Response

Eliminate the error cause according to the error code set in $3 then re-execute the program. Also, make sure that the method entry information is specified correctly. Moreover, please confirm the following:

Is the retrieval path (LD_LIBRARY_PATH) correctly set?
Can the executable program be made correctly?
Is there enough space to load and execute the program?
Does the called method contain national characters?

JMP0104I-U

EXCEPTION OCCURRED '$1'

System action

Abnormally terminates the program.

Response

If $1 is "OBJECT", describe the USE statement that specifies the class name having the inheritance relationship with the exception object that has been generated.

JMP0105I-U

CANNOT LOAD CLASS '$1'. CODE=$2.

System action

Abnormally terminates the program.

Response

Eliminate the error cause according to the error code set in $2 then re-execute the program. Also, make sure that the class entry information is specified correctly. Moreover, please confirm the following:

Is the retrieval path (LD_LIBRARY_PATH) correctly set?
Can the executable program be made correctly?
Is there enough space to load and execute the program?
Does the called method contain national characters?

JMP0106I-U

EXCEPTION OBJECT USE PROCEDURE IS RECURSIVELY CALLED.

System action

Abnormally terminates the program.

Response

If the error handling procedure is re-executed due to occurrence of a new exception object in the exception object error handling procedure being executed, control must not reach the last statement in the preceding error handling procedure.

Do not allow the error handling procedure to be called recursively or use the EXIT PROGRAM statement, EXIT METHOD statement, or GO TO statement so that the last statement in the error handling procedure will not be reached.

JMP0107I-U

THE STOP RUN STATEMENT CANNOT BE EXECUTED DURING EXECUTION OF FINALIZE METHOD.

System action

Abnormally terminates the program.

Response

Change the STOP RUN statement written in the finalize method or the program invoked from the finalize method to the EXIT PROGRAM or EXIT METHOD statement, then rerun the program.

JMP0200I-E

INSUFFICIENT DATA ACCEPTED FROM SYSIN.

System action

Continues processing if the remaining part of the input data area is blank.

Response

Prepare the number of data items that can be input by executing the ACCEPT FROM SYSIN statement.

Confirm that the ACCEPT statement is not executed a number of times equal to or greater than the number of data items.

JMP0201A-I

AWAITING A REPLY.

System action

After receiving response, continues processing.

Explanation

The system asks the operator to input data by using the ACCEPT statement.

Response

Input any necessary data.

JMP0202A-I

System action

After receiving response, continues processing.

Explanation

The STOP literal statement is being executed.

Response

Input any character. The literal specified in the STOP literal statement is written for $1.

JMP0204I-U

STATEMENT SEQUENCE ERROR. STM=$1. PGM=$2. LINE=$3. RPT=$4.

System action

Abnormally terminates the program.

Response

Correct the execution sequence of statements for the report or detail phrase indicated in the message, then re-execute.

$1 : The type of statement (INITIATE, GENERATE, or TERMINATE)
$2 : The outermost program name
$3 : The statement number
- [Solaris][Linux] [COPY-qualification-value-]line-number.verb-sequence-number-in-a-line
- [Linux64] [COPY-qualification-value-]line-number
$4 : The report name or data name (detail phrase name)

JMP0206I-W

SCREEN ITEM SIZE IS LARGER THAN LOGICAL SCREEN.

System action

The screen item is displayed partially.

Response

Specify a logical screen size large enough to display the entire item.

JMP0208I-E

INVALID NUMERICAL VALUE ACCEPTED.

System action

Writes zero to the receive data item, then continues processing.

Response

Specify a value for the numeric data item of the ACCEPT statement correctly, then re-execute.

JMP0211I-U

KEY DEFINITION FILE OPEN ERROR. FILE=$1. $2

System action

Abnormally terminates the program.

Response

Check the key definition file ($1) specified by environment variable CBR_SCR_KEYDEFFILE.

Eliminate the cause of the error according to the error code written for $2, then rerun the program

JMP0212I-W

KEY DESCRIPTION IS INVALID. '$1'

System action

Continues processing without setting the "KEY" in the key definition file.

Response

Please correct the key definition file referring to the character string set in $1, and execute program again. Table "$1 of JMP0212I-W" lists the contents of $1.

Table 3.13 $1 of JMP0212I-W
$1	Description	Programmer Response
SECTION	The mistake is found in the description of the section name. It is judged that all keys are not specified in the key definition file.	Please confirm the section name [COBOL.KBD] of the key definition file.
KEY=key name	The mistake is found in the description of the key name. It is considered that the key set in $1 is not specified in the key definition file.	Please confirm the description form of the key name in the key definition file and whether the value of the key is in the effective range. Please confirm the content of the key definition. [Solaris] Refer to the "Using Key Definition File" in the "NetCOBOL User's Guide".

JMP0214I-W

TWO OR MORE THREADS WERE EXECUTED IN THE SCREEN HANDLING

System action

Abnormally terminates the program.

Response

Correct the program so it does not call the screen operation function from more than one thread at the same time in the same process; then execute the program again.

JMP0221I-U

ERROR OCCURRED IN '$1' OF THE METHOD INVOCATION. '$2'

System action

Abnormally terminates the program.

Response

Eliminate the error cause according to the string set in $2 then re-execute the program. Table "$2 ofJMP0221I-U" lists the text that can be set in $2

Table 3.14 $2 ofJMP0221I-U
$2	Description	Programmer response
BIND	Binding the method failed.	Make modification so that the object identifier specified in the INVOKE statement invoking method ($1) will be correct.
NULL	The method is invoked from the NULL object.	Set the object reference for the class that conforms to the class containing method ($1) in the object reference data item specified in the INVOKE statement.

JMP0222I-U

ERROR OCCURRED IN THE AS PHRASE. SPECIFICATION ON THE RIGHT SIDE OF THE AS PHARASE IS '$1'

System action

Abnormally terminates the program.

Response

Make sure that class name $1 or interface name $1 specified on the right side of object modifier AS, or selective specification of class name $1 (FACTORY OF specification or ONLY specification), conforms to the object referenced by the object reference identifier specified by the AS modifier.

JMP0223I-U

CONFORMANCE ERROR OCCURRED IN THE SETTING OF THE SENDING OBJECT REFERENCE DATA ITEM TO THE RECEIVING OBJECT REFERENCE DATA ITEM.

System action

Abnormally terminates the program.

Response

Make modification so that the object reference specified for the return item in the header of the procedure division at the sender conforms to the object reference specified for the return item at the receiver.

JMP0224I-U

ERROR OCCURRED IN A PROPERTY METHOD INVOCATION. '$1' 'NULL'

System action

Abnormally terminates the program.

Response

Make the object reference specified for the object property conform to the class or interface containing the property name ($1).

JMP0225I-U

CANNOT INVOKE METHOD '$1' WITH THE ANY LENGTH CLAUSE SPECIFICATION. '$2' '$3' $4

System action

Abnormally terminates the program.

Response

Remove the cause of the error by referring to the string set to $3, and execute again. The table "$3 of JMP0225I-U" shows the string set to $3.

Table 3.15 $3 of JMP0225I-U
$3	Description	Programmer Response
PARM=n	There is an error in the parameter. The called method ($1) has an ANY LENGTH clause and the data item which is not allowed to be specified as a data item of an ANY LENGTH clause is specified to method which calls ($4). "n" indicates the position of the parameter which has an error.	Correct the program so that the method ($1) is called by the correct parameter.
[Solaris] VL	The method invoking statement specifying the ANY LENGTH clause is compiled by a compiler with a version and level not supporting it.	Re-compile the caller method ($4) with COBOL V40L20 or later, when USING is set in $2. Re-compile the caller method ($4) with COBOL V50L10 or later when RETURNING is set in $2.

JMP0250I-U

START ENVIRONMENT ERROR TO PERFORM ACCEPT/DISPLAY IN COLLABORATION WITH Systemwalker Centric Manager. '$1'

System action

Abnormally terminates the program.

Response

Remove the cause of the error by referring to the string set to $1, and execute again. See the table below.

Table 3.16 $1 of JMP0250I-U
$1	Description	Programmer Response
LANG ERROR	[Solaris] Unicode is specified for environment variable LANG.	This function cannot be executed in the Unicode environment. Execute it with SJIS or EUC.
NOT-INSTALLED	Systemwalker Centric Manager is not correctly installed.	Confirm that Systemwalker Centric Manager is correctly installed.

JMP0251I-U

CANNOT DISPLAY UPON CONSOLE.

System action

Abnormally terminates the program.

Response

Check that Systemwalker Centric Manager is active.

JMP0252I-U

CANNOT ACCEPT FROM CONSOLE. '$1'

System action

Abnormally terminates the program.

Response

While referring to the string set in $1, correct the cause of the error, and then retry the execution. See the table below.

Table 3.17 $1 of JMP0252I-U
$1	Error Details	Programmer Response
ERR_PARAM	An error occurred during ACCEPT statement input processing.	If the same error occurs when the program is reexecuted, it may be a system error. Please open a support incident with your support provider.
TIME_OUT	A timeout occurred during ACCEPT statement input.	Enter the ACCEPT statement before 1,440 minutes elapse.
STOP_BY_USER	Systemwalker Centric Manager was stopped by a user request.	Confirm that Systemwalker Centric Manager is active. For details, see the Systemwalker Centric Manager online manual or access the Help information.
ERR_CONECT	An attempt to connect to Systemwalker Centric Manager failed.	Confirm that Systemwalker Centric Manager is active. For details, see the Systemwalker Centric Manager online manual or access the Help information.
ERR_SEND	Transmission to Systemwalker Centric Manager failed.	Confirm that Systemwalker Centric Manager is active. For details, see the Systemwalker Centric Manager online manual or access the Help information.
ERR_RCV	Receiving from Systemwalker Centric Manager failed.	Confirm that Systemwalker Centric Manager is active. For details, see the Systemwalker Centric Manager online manual or access the Help information.
ERR_CONNECTOVER	The maximum number of input requests was exceeded.	Execute the input requests that are waiting for a response. For details, see Systemwalker Centric Manager online manual or access the Help information.
ERR_UXEXPCT	An unexpected error occurred.	If the same error occurs when the program is re-executed, it may be a system error. Please open a support incident with your support provider.
ERR_OTHER	A Systemwalker Centric Manager operation error occurred.	If the same error occurs when the program is re-executed, it may be a system error. Please open a support incident with your support provider.

JMP0253I-U

INVALID JOBDATE FORMAT.

System action

Abnormally terminates the program.

Response

Check that the date specified in the environment variable CBR_JOBDATE is specified in the correct format.

JMP0254I-E/U

ERROR IN COLLABORATION WITH GENERALIZED LOG. '$1' '$2' '$3'

System action

Abnormally terminates the program. When closing the general-purpose log fails, an E level message is displayed and processing continues.

Response

Remove errors in character strings $1,$2, and $3 and execute again.

Table 3.18 $2 of JMP0254I-E/U
$2	Error Details	Programmer Response
LOAD-FAIL	Loading of the library required for the general-purpose log link function failed.	While referring to the string set in $3, check environment settings to determine whether Interstage Business Application Server is correctly installed.
ENOMEM	A memory shortage occurred.	Check the amount of free memory in the system.
FUNCTION	An error occurred in a function for the general-purpose log link function.	$1 indicates the function name and $3 indicates an error code of the function. Refer to the Interstage Business Application Server manual to correct the cause of the error.
NOT-SYMBOL	A function required for the general-purpose log link function was not found.	If the same error occurs when the program is re-executed, it may be a system error. Please open a support incident with your support provider.
INTERNAL-ERROR	An internal contradiction was detected.	If the same error occurs when the program is re-executed, it may be a system error. Please open a support incident with your support provider.

JMP0260I-U

TRANSCRIPTION OF $2th DATA FAILED. STATEMENT='$1'. '$3'

System action

Abnormally terminates the program.

Response

The character string of either STRING or UNSTRING is in $1. The error number is in $2. Correct the character string in $3 and execute again.

Table 3.19 $3 of JMP0260I-U
$3	Description	Programmer Response
CONVERT ERROR=0xXXXX	When the STRING or UNSTRING statement was executed, an error was detected when changing matched type codes on the receiving side.	Refer to the system error codes.
NOT NUMERIC ITEM	Non-transferable data (non-numeric characters and invalid signs) to number items were detected during an UNSTRING execution.	Check the data item type on the receiving and sending sides.

Example: When transferring a receiving side item, the "Extension number" failed following execution of the UNSTRING statement. Number 5 is in the message.

[Statement]
UNSTRING employee-data INTO employee BY CSV-FORMAT
[Data Definition]
77 employee-data   PIC X(35)
                   VALUE "8701,TARO FUJITSU,38,SalesDepartment,7551-4535".
  01 employee.
    02 Employee-Number  PIC 9(6).
    02 Name             PIC X(15).
    02 Age              PIC 9(2).
    02 Department       PIC X(20).
    02 Extension number PIC 9(9).  *> To be written "7551-4535", a message is displayed.

JMP0261I-U

INITIAL VALUE OF 'POINTER' PHRASE IS INVALID. STATEMENT='$1'

System action

Abnormally terminates the program.

Response

The character string of either STRING or UNSTRING is in $1. Correct the POINTER initial values and execute again.

JMP0262I-W

SOME CHARACTERS HAVE BEEN LEFT IN SENDING ITEM. STATEMENT='$1'

System action

The $1 statement execution is exited, and program processing continues.

Response

The character string of either STRING or UNSTRING is in $1. Correct the error in $1 as indicated below and execute again.

STRING Statement
Moving to the low order end in the receiving side item has been completed, but there are still characters in the sending side item. Resize the receiving side data items so that all sending side items can be moved.
UNSTRING Statement
There is some split data that cannot be moved from the sending side item. Increase the data item numbers on the receiving side so that all of the split data can be stored.

Use CBR_CSV_OVERFLOW_MESSAGE to suppress the display of this message without modifying the program. Refer to "CBR_CSV_OVERFLOW_MESSAGE (Specify to suppress messages at CSV data operation)" in the "NetCOBOL User's Guide" for details.

JMP0263I-W

TRUNCATION OF $1th DATA OCCURRED. STATEMENT='UNSTRING'

System action

The data following the moving rule is truncated, and the UNSTRING statement processing continues.

Response

Error numbers are in $1. Character strings split by the UNSTRING statement are larger than the receiving side item, so the data was truncated. Resize the receiving side item that was truncated, and execute again.

Use environment CBR_CSV_OVERFLOW_MESSAGE to suppress the display of this message without modifying the program. Refer to "CBR_CSV_OVERFLOW_MESSAGE (Specify to suppress messages at CSV data operation)" in the "NetCOBOL User's Guide" for details.

Example: When transferring a receiving side item, "Department" failed following execution of the UNSTRING statement. Number "4" is in the message.

[Statement]
UNSTRING employee data INFO employee BY CSV-FORMAT
[Data Definition]
77 employee-data   PIC X(35)
                   VALUE "8701,TARO FUJITSU,38,SalesDepartment,7551-4535".
  01 employee.
    02 Employee-Number  PIC 9(6).
    02 Name             PIC X(15).
    02 Age              PIC 9(2).
    02 Department       PIC X(10).  *> To be written "SalesDepartment", 
    02 Extension number PIC X(10).  *> a message is displayed.

JMP0301I-E

'$1' ($2) IS NOT CLOSED. $3

System action

Terminates the program without performing close processing for the file.

Response

Correct the program ($3) so that the CLOSE statement is executed for the file ($1) before termination of the program ($3). The open mode of the file ($1) is written for $2.

JMP0302I-U

CLOSE ERROR DURING PROGRAM TERMINATION. PGM=$1. FILE=$2.

System action

Abnormally terminates the program.

Response

Check and eliminate the cause of the error. If another message is written, refer to it to determine the cause. The program name is written for $1. The access name or file name is written for $2.

JMP0310I-I/U

$1 ERROR. FILE=$2. '$3'.

System action

Continues program processing if the severity code is I; aborts the program if the severity code is U. The severity code is determined as follows:

I: The FILE STATUS clause is specified for file definition.
U: The FILE STATUS clause and error procedures are not specified.

Response

Eliminate the cause of the error according to the character string output in $3, then re-execute. OPEN or CLOSE is output in $1. The access name or file name is output in $2. Meanings of the strings output in $3 and actions to be taken are shown in table "$3 of JMP0310I-I/U (1)" and "$3 of JMP0310I-I/U (2)".

Table 3.20 $3 of JMP0310I-I/U (1)
$3 (Character String)	Error Contents	Programmer Action
ACC-METHOD or ACC-METHOD (98XX)	File access method is invalid. (*1)	Specify the correct access method.
BLKED-FILE	The file is unavailable due to error at CLOSE statement execution.	Check the file and take corrective action.
CNVER = xxxx	Character code conversion failed. xxxx: Hexadecimal notation	Check for and eliminate the cause of the error according to the system error code. If the error code is 0xFFFFFFFF, it indicates the location where non-shift-JIS characters were used while they were not allowed. Correct the program.
[Solaris] ENV-ERR	The operating environment of the application has not been opened.	Check that the application has been started in the Apcoodinator.
ERFLD=xxxx	An input-output file access error occurred. xxxx: Hexadecimal notation	The error code value shown in $3 is the error code of an input-output file. Refer to errno for the system or file system manuals, and take appropriate action. (*2)
ERRCD=xxxx	An error occurred during presentation file access.	For PowerFORM RTS: For error details, refer to the "PowerFORM Runtime Reference". The two high-order digits of the error code indicated by $3 indicate the input-output status value. The two low-order digits indicate the return code. For other connection products: The value of error code that $3 shows is the post code of each connection product. Refer to the manual of each connection product. (*3)
EXCL-ERROR	Exclusion error occurred.	Re-execute. If the exclusion error occurs frequently, check for a problem during operation.
[Solaris][Linux64] EXFH-INF	Opening the External file handler information file failed, or the contents of the External file handler information file are invalid.	Check the path name or contents of the External file handler information file.
FCB	The contents of FCB are invalid.	Confirm the contents of FCB.
FILE-LOCK	The file is being used by another user.	Re-execute. If the exclusion error occurs frequently, check for a problem during operation.
FONT-TABLE	Contents of the font-table are invalid.	Verify the contents of the font-table.
FTNCD=xxxx	Error code (errno) from system. xxxx: hexadecimal	Verify the cause according to the system errno and take the appropriate action.
LOAD	Loading the subprogram or another product failed	Verify that environment variable LD_LIBRARY_PATH is set correctly. Call the multithread unsupported program at the time of executing the multithread mode. Check the multithread condition of each product.
LOAD=xxxxxx	Loading another product failed. xxxxxx: hexadecimal	Remove the cause of the error by referring to the set error code. (*5)
[Linux64] LOAD=type(error message)	Loading failed. type: EXFH or PIPE error message: error message by dlerror function	Eliminate the cause of the error that the error message shows.
[Solaris][Linux64] LOAD-EXFH	Start environment of the External file handler failed.	Possible causes are as follows. Eliminate the cause of the error and then rerun the program. The environment variable CBR_EXFH_API is not specified. The library of External file handler specified for the environment variable CBR_EXFH_LOAD is not found or is damaged. When the environment variable CBR_EXFH_LOAD is not specified, the shared object file name is obtained by turning the entry-point-name specified in the environment variable CBR_EXFH_API into "libentry-point-name.so". That is not found or is damaged.
LOCK-FULL	More than one application demand is OPEN to the same file, which results in a lock table shortage.	Re-execute. If the exclusion error occurs frequently, check for a problem during operation.(*7)
NON-FILE	An OPEN statement without OUTPUT specified was executed, but the file does not exist.	Create the file before executing the program.
NON-REEL	A CLOSE statement with REEL/UNIT specified was executed.	Delete the REEL/UNIT specification in the CLOSE statement.
OPEN-MODE	File open mode is invalid.	Open the file in a valid open mode.
PRT-INF	Opening the print information failed, or the contents of the print information file are invalid.	Verify that path name of the print information file is correctly set in environment variable CBR_PRT_INF. Or verify the contents of the print information file.
READ-ONLY	The file is a read-only file.	Either change the access permission to allow writing to the file or specify the correct file.
REC-MODE	The record format is invalid.	Correct the record format.
RMERR=xxxx	Error code from systemxxxx: Hexadecimal notation	The error may be system failure. Collect information and open a support incident with your support provider. (*4)
SESS-END	The OPEN statement was executed after the session ended or was interrupted.	Correct this so that the OPEN statement is not executed before the session has started.
THREAD=xxxxxx	Thread synchronization failed.xxxxxx: Hexadecimal notation	Refer to the indicated error code and remove the cause of error. (*5)
TIMEOUT	The OPEN statement was executed after the timeout.	Correct this so that the OPEN statement is not executed after the timeout.
UNSUPPORT	The specified function is not supported.	Check the functional range of the specified file or file system. (*6)

*1: The following event errors in the file accessing method may have occurred:
- Tried to access files of a different configuration.
- Tried to access index files that need to be restored.
- The file expressive form does not match the program performance code-type or definitions within the program.
*2:
- If a message is generated showing error information ERFLD=101 when a print file (without the FORMAT clause specified) is executed, ensure the following:
  - Only the required number of printer drivers are installed.
  - The FCB control statement is less than 2,048 bytes.
  - All the specified forms overlay patterns are correct.
  - All the registered forms overlay pattern names are correct.
  - The spool area is large enough.
  - Confirm the disk capacity of the environment variable (TMPDIR) directory.
  - Stop all other applications that are executing at the same time.
  - Confirm the size of real storage and increase it if necessary.
  - Confirm the size of virtual storage and increase it if necessary.
  - If no problems are found in the above checks, a system error probably occurred.
  - Collect the error information, then open a support incident with your support provider.
- Refer to the system errno explanation for details on character strings indicating errors in the file message text other than those listed above.
*3 If ERRCD=90xx is output while PowerFORM Runtime is used, refer to the "PowerFORM Runtime Reference" for xx.
*4 When RMERR=7F17 (98xx) is output, the file cannot be used normally. For indexed files, use the file utility or indexed file recovery function to restore the file.
*5 Refer to the system errno explanation for details.
*6 Check multithread or Unicode operation as follows:
- Check the multithread support status of each product to determine whether a product not supporting multithread operation is called during multithread model operation.
- Check the Unicode support status of each product to determine whether a product not supporting Unicode is called during Unicode application operation.
*7 The maximum number of OPEN requests that can be accepted concurrently for the same file is 1024.

If any character strings explained in "$3 of JMP0310I-I/U (2)" are displayed, check the following:

Whether the defined contents of the program, a file, or a record are consistent with the attribute of the file actually processed.
Whether this product was used to create the file that is actually processed.
Whether the specified file system type is correct.

If the file that is used was created with a product other than this product (OSIV COBOL85 or another programming language) or belongs to a different file system, the following errors may occur:

Table 3.21 $3 of JMP0310I-I/U (2)
$3 (Character String)	Error Contents	Contents Checked by Program
INV-BLKSZ	Block length is invalid.	Length specified in BLOCK CONTAINS clause.
INV-CODEST	Code set is invalid.	Character sign of CODE SET clause.
INV-COLSEQ	Character collating sequence is invalid.	Code system name of PROGRAM COLLATING SEQUENCE.
INV-DELMTR	Delimiting records are invalid.	Data specified in the ORGANIZATION, and RECORD clauses (*1).
INV-KEYDUP	Keys cannot be duplicated.	Presence or absence of DUPLICATE specification in RECORD KEY and ALTERNATE RECORD KEY clauses.
INV-KEYLEN	Key length of allocated file conflicts with program definition.	Length of data-name specified in RECORD KEY and ALTERNATE KEY clauses. (*2)
INV-KEYSTR	Key structure is invalid.	Length of data-name or number of data items specified in RECORD KEY or ALTERNATE RECORD KEY clauses.
INV-LRECL	Record length of allocated file conflicts with program definition.	Contents of ORGANIZATION clause specification. Length specified in RECORD CONTAINS clause or record length.
INV-RKP	Location of relative key of allocated file conflicts with program definition.	Relative location of data name specified in RECORD KEY and ALTERNATE RECORD KEY clauses.
KEY-ATTR	Key attribute of allocated file conflicts with program definition.	Attribute of data-name specified in RECORD KEY and ALTERNATE RECORD KEY clauses.
NON-ESDS	Allocated file is other than record sequential file.	Contents of ORGANIZATION clause specification.
NON-KSDS	Allocated file is other than indexed file.	Contents of ORGANIZATION clause specification.
NON-RRDS	Allocated file is other than relative file.	Contents of ORGANIZATION clause specification.
NOT-TEXT	File other than text file is allocated to print.	Contents of ORGANIZATION clause specification.
NOT-UNIQUE	Duplicate key is contained in allocated file without DUPLICATES specification.	Presence or absence of DUPLICATES specification in RECORD KEY and ALTERNATE RECORD KEY clauses.

*1 : Check the program definition to verify that the file organization and the record format (fixed or variable record length) are consistent with the processed file.

*2 : When two or more data items are specified for the RECORD KEY clause and the ALTERNATE RECORD KEY clause, the length of all data items should correspond to the length of each key of the allocated file.

JMP0311I-I/U

[Linux] MISSING ALLOCATION. FILE=$1.

[Solaris][Linux64] MISSING ALLOCATION. FILE=$1. '$2'.

System action

Continues program processing if the severity code is I; aborts the program if the severity code is U. The severity code is determined as follows:

I: The FILE STATUS clause is specified for file definition.
U: The FILE STATUS clause and error procedures are not specified.

Response

[Linux] Check the following and then execute again:
- Is the file ($1) allocated correctly?
- If a comma (,) is included in the filename, is it enclosed in double quotation marks?
- After the filename, is a valid character string specified correctly as the file function?
Refer to "Other File Functions", in "File Processing", in the "NetCOBOL User's Guide" for information concerning file functions.

[Solaris][Linux64] Allocate the file ($1) if necessary, or specify the file correctly, then re-execute. See the table "$2 of JMP0311I-I/U" for more information regarding the character string in $2.

Table 3.22 $2 of JMP0311I-I/U
$2	Description	Programmer Response
NOT ASSIGNED	The environment variable is not specified for an access name, and a file name is blank.	Specify the file name of the environment variable or data name specification.
INVALID ASSIGN	An analysis error occurred in the specified character strings.	Check the following: Is an effective character string specified for the file function? Is the combination of specified function and file organization correct? Refer to "Other File Functions" in the "NetCOBOL User's Guide".
INVALID PATH-NAME	The path name of the file contains an error.	Check the path name of the file.

JMP0313I-I/U

INSUFFICIENT STORAGE AVAILABLE. STM=$1. FILE=$2.

System action

Discontinues error file processing, then continues program processing if the severity code is I; aborts the program if the severity code is U. The severity code is determined as follows:

I: The FILE STATUS clause is specified for file definition.
U: The FILE STATUS clause and error procedures are not specified.

Response

For the cause and action to be taken, see "Appendix B Notes".. After the action is taken, re-execute the program.

The COBOL statement (OPEN, CLOSE, START, READ, WRITE, REWRITE, or DELETE) that caused the virtual storage to become insufficient is written for $1. The file name or access name of the processed file is written for $2.

JMP0320I-I/U

INPUT/OUTPUT ERROR. STM=$1. FILE=$2. '$3'.

System action

Discontinues error file processing, then continues program processing if the severity code is I; aborts the program if the severity code is U. The severity code is determined as follows:

I: The FILE STATUS clause is specified for file definition.
U: The FILE STATUS clause and error procedures are not specified.

Response

Eliminate the cause of the error according to the character string output for $3. The COBOL statement (START, READ, WRITE, REWRITE, or DELETE) that caused the input-output error is output in $1. The file name or access name of the processed file is output in $2. Table "$3 of JMP0320I-I/U" shows the meanings of strings to be output in $3 and the actions to be taken.

Table 3.23 $3 of JMP0320I-I/U
$3	Description	Programmer Response
ALTD-LEN	The record length specified in the REWRITE statement is different from the length of an existing record.	Do not change the length of an existing record when updating the record.
BLKED-FILE	The file cannot be used because of a CLOSE statement error.	If message JMP0310I-I is displayed before JMP0320I-I, eliminate the cause of the error according to message JMP0310I-I.
CNVER = xxxx	Character code conversion failed. xxxx: Hexadecimal notation	Check for and eliminate the cause of the error according to the system error code. Error code 0xFFFFFFFF indicates the location where non-ACP characters were used where they were not allowed.
ERRCD=xxxx	A presentation file access error occurred.	Check for and eliminate the cause of the error according to the manuals of the linked products. (*1)
EXCEED-LEN	The length of the record to be written exceeds the maximum record length specified in the program.	Set the record length to within the specified maximum record length.
EXCL-ERROR	An exclusive error occurred.	Re-execute. If the exclusive error occurs repeatedly, confirm that the error does not affect operation.
FCB	The FCB contents are invalid.	Check the FCB contents.
FDBK=xxxx	An error occurred while accessing the input-output file. xxxx: Expressed in hexadecimal	The value set in $3 is the error code of the input-output file. Check for and eliminate the cause of the error according to the system error code or the manuals of the file system. (*2)
FONT	A font that did not exist in the system was specified for output. Or, the specified font table could not be opened.	Check the specified font name, and install necessary fonts in the system. Or, check if the correct font table name has been specified.
FOVER=xxxx	Error occurred at overlay pattern combine processing.	Check cause according to xxxx and take corrective action. For contents of xxxx, see the table "Contents of error when $3 of JMP0320I-I/U is FOVER=xxxx" below.
FOVL	The specified directory containing the forms overlay definition is invalid, or the forms overlay definition is invalid.	Check the initial file to determine if the directory containing the correct forms overlay definition is specified.
FTNCD=xxxx	Error code from the system xxxx: Expressed in hexadecimal	Check for and eliminate the cause of the error according to the system error code. (*2)
INV-CHAR	A line sequential file record or print file record contains an invalid character.	Check the data contents.
INV_DELMTR	A record delimiter is incorrect.	Correct the contradiction between the program specification and attribute of the assigned file.
INV-LEN	The record length specified in the WRITE or REWRITE statement is invalid.	Specify the correct length of the record to be written.
INV_TRANS	Transaction is suspended or terminated after execution of preceding READ statement in sequential READ, sequential DELETE, or sequential REWRITE statement.	Correct the program so that the transaction is not suspended or terminated between sequential READ statement and subsequent sequential READ, sequential DELETE, or sequential REWRITE statement.
LOAD	The subprogram could not be loaded.	Check the program runtime environment.
LOAD-FOVL	Loading system program required to combine overlay patterns failed.	Check the program execution environment.
KEY-CHANGE	Key value specified for updating record is different from when one record was read.	Correct the program so that the key value of record to be updated is not changed.
KEY-LEN=0	Valid generic key length is zero.	Correct the program so that the valid generic key length is not zero.
MACRO	Requesting OPEN/CLOSE macro or OPEN/MACRO for subsystem is unsuccessful.	Take actions according to the system error message preceding this message.
NO-TRANS	Some characters cannot be converted into a code set.	Check the data contents.
OVER-RECLN	The length of the print data area that was to be output from the line record exceeded the maximum length.	Correct the length of the print data area so that it is within the determined maximum length (*4).
OVER-RECLN	The length of the record that was input exceeds the maximum record length determined by the program.	Correct the program so that the length of the record to be input is within the determined maximum length.
PHYSIC-ERR	A physical error occurred.	Check the file contents (physical structure).
READ-ONLY	A read-only file is used.	Change the access permission to allow writing to the file.
REC-LOCK	The record is exclusively used by another user, or the record cannot be used exclusively because it is being used by another user.	Re-execute. If the exclusive error occurs repeatedly, confirm that the error does not affect operation.
R.KEY-ERR	The relative key contents conflict with the definition specified in the PICTURE clause during random or dynamic access.	Specify a data item size in the PICTURE clause large enough to store the maximum value of the relative key.
R.KEY-ERR	The relative key item value is 0.	Specify a non-zero value for the relative key item.
RMERR=xxxx	Error code from the runtime system xxxx: Expressed in hexadecimal	A system error probably occurred. Collect the error information, then Contact Fujitsu Software Support. (*3)
RRN>R.KEY	When the READ or WRITE statement is executed for sequential processing, the relative record number exceeds the maximum value of the relative key item.	Specify a size of the relative key item large enough to store the maximum relative record number of the file
SESS-END	The READ statement was executed after session has ended or been interrupted.	Correct this so that the READ statement is not executed before the session has started.
THREAD=xxxxxx	Thread synchronization failed. XXXXXX: Hexadecimal notation	Remove the cause of error while referring to the indicated error code.
TIMEOUT	The READ or WRITE statement was executed after the timeout.	Correct this so that the READ or WRITE statement is not executed after the timeout.
[Solaris] UNSUPPORT	When using the External File Handler is to be used, a START statement with the FIRST phrase specified for indexed file cannot be executed.	Check the program that uses the External File Handler for a START statement with the FIRST phrase and remove it.

*1 If ERRCD=90xx is output while PowerFORM RTS is used, refer to the "PowerFORM Runtime Reference" for xx.
*2
- If a message is generated showing error information ERFLD=101 when a print file (without the FORMAT clause specified) is executed, ensure the following:
  - Only the required number of printer drivers are installed.
  - The FCB control statement is less than 2,048 bytes.
  - All of the specified forms overlay patterns are correct.
  - All of the registered forms overlay pattern names are correct.
  - The spool area is large enough.
  - Confirm the disk capacity of the environment variable (TMPDIR) directory.
  - Stop all other applications that are executing at the same time.
  - Confirm the size of real storage and increase it if necessary.
  - Confirm the size of virtual storage and increase it if necessary.
  - If no problems are found in the above checks, a system error probably occurred.
- [Solaris] For details on error codes to the RDM file, refer to "error code list" in "RDB/7000 Manual" and "communication error detail codes" in "SymfoWARE7000 DB Collaboration Help".
- [Solaris] For details on error codes for PowerRDBconnector, see the "PowerRDBconnector Handbook".
- See "System Error Codes" for details on character strings indicating errors in the file message text other than the above.
*3 If RMERR=7F17 (98xx) is output, the file cannot be used normally. For the indexed file, use the file utility or indexed file recovery function to restore the file.
*4 The length of the record that can be written from the line record (though it is just a guideline) can be obtained with the following formula:
```
32 Kbytes > Output record length + 2 + 100 * Number of basic items
```

If a national data item is specified in the report group description entry when the report writer module is used, this message may be output. The execution results of the report containing national data items for the report writer module are not guaranteed. Correct the program so that no national data items are specified.

Table 3.24 Contents of error when $3 of JMP0320I-I/U is FOVER=xxxx
Value of FOVER=xxxx	Error Contents
16	The output file cannot be used due to insufficient resources, etc.
8000	The work memory area is insufficient.
8028	Opening the overlay file failed. The path name of the overlay file is invalid. The overlay file cannot be accessed.
8029	Reading the overlay file failed. The overlay file is empty. The overlay file cannot be read.
8030	Overlay file close error. The overlay file cannot be closed for some reason.
8031	The format of the overlay pattern is invalid. An overlay pattern other than KOL5 was specified.
8034	An unsupported function was used. Example: A KOL6 format overlay pattern was specified when a PostScript Level 1 data stream was output. (PostScript Level 1 supports only KOL5.)
Others	A system failure is assumed. Collect information and open a support incident with your support provider.

JMP0321I-U

AT END CONDITION. STM=READ. FILE=$1.

System action

Abnormally terminates the program.

Explanation

The file name or access name of the file with which a file end condition was produced is written for $1.

Response

Specify AT END phrase in the READ statement to perform file end processing.

Check whether the number of input data items is correct.

JMP0322I-U

KEY SEQUENCE ERROR. STM=$1. FILE=$2.

System action

Abnormally terminates the program.

Explanation

The file name or access name of the file with which an invalid key condition was produced is written for $2.

Response

If $1 is the WRITE statement, correct the program so that the key values are written in ascending order.

If $1 is the REWRITE or DELETE statement, correct the program so that the key value of the record read by the previous READ statement is not changed.

JMP0323I-U

DUPLICATE KEY ERROR. STM=$1. FILE=$2.

System action

Abnormally terminates the program.

Explanation

The error COBOL statement (WRITE, REWRITE or CLOSE) is written for $1. The file name or access name of the error file is written for $2.

Response

Correct the program so that a key is not duplicated.

JMP0324I-U

RECORD NOT FOUND. STM=$1. FILE=$2.

System action

Abnormally terminates the program.

Explanation

The error COBOL statement (READ, REWRITE, START, or DELETE) is written for $1. The file name or access name of the error file is written for $2.

Response

Correct the program so that attempts to access a non-existent record are inhibited.

Correct the program by using the FILE STATUS or INVALID KEY clause so that the program checks an attempt to access a non-existent record.

JMP0325I-I/U

MAXIMUM FILE SIZE EXCEEDED, OR INSUFFICIENT DISK SPACE. STM=$1. FILE=$2.

System action

The free disk space is insufficient or the maximum file size has been exceeded.

Terminates the program abnormally when the severity code is U.

When the FILE STATUS clause is specified in the file definition, the severity code is I. When the FILE STATUS clause and an error processing procedure are not specified, the code is U.

Explanation

The error COBOL statement (WRITE, REWRITE, READ, START, or CLOSE) is written for $1. The file name or access name of the error file is written for $2.

Response

The disk space is insufficient or the maximum size of the file was exceeded. Refer to Table "Functional differences between file systems", in "File Processing", in the "NetCOBOL User's Guide". When the disk space is insufficient, increase the size of disk space, then re-execute. If the file capacity is limited by the command, increase the maximum value, then rerun the program. When the maximum size of the file is exceeded, divide the file into multiple parts.

JMP0326I-U

NO-SPACE CONDITION. STM=$1. FILE=$2.

System action

Abnormally terminates the program.

Explanation

The error COBOL statement (WRITE, REWRITE, READ, START, or CLOSE) is written for $1. The file name or access name of the error file is written for $2.

Response

Increase the size of the file space or disk space, then re-execute.

JMP0327I-U

INVALID KEY CONDITION. STM=$1. FILE=$2. '$3'.

System action

Abnormally terminates the program.

Explanation

The error COBOL statement (WRITE) is written for $1. The file name or access name of the error file is written for $2.

Response

If $3 is RRN>R.KEY, correct the program so that the relative record number does not exceed the maximum value permitted for the relative key item when records are written in sequential processing. Alternatively, correct the program by using the INVALID KEY clause so that processing for an invalid key condition is performed.

JMP0328I-I/U

DEPENDING ON OBJECT VALUE IS OUT OF RANGE. STM=WRITE. FILE=$1.

System action

Continues program processing if the severity code is I; aborts the program if the severity code is U. The severity code is determined by:

I: The FILE STATUS clause is specified for file definition.
U: The FILE STATUS clause and error procedures are not specified.

Explanation

The file name or access name of the error file is written for $1.

Response

Correct the program so that the DEPENDING ON value is defined in the specified range.

JMP0330I-I/U

STATEMENT SEQUENCE ERROR. STM=$1. FILE=$2. '$3'.

System action

Continues program processing if the severity code is I; aborts the program if the severity code is U. The severity code is determined by:

I: The FILE STATUS clause is specified for file definition.
U: The FILE STATUS clause and error procedures are not specified.

Explanation

The COBOL statement (OPEN, CLOSE, READ, WRITE, REWRITE, START, or DELETE) with which an input-output error occurred is output in $1. The file name or access name of the processed file is output in $2. The character strings output for $3 are listed in Table "$3 of JMP0330I-I/U".

Response

Eliminate the cause of the error according to the character string output in $3, then re-execute.

Table 3.25 $3 of JMP0330I-I/U
$3	Description
AT-END	After a file at end condition was produced, the READ statement was re-executed.
DUPL-OPEN	The OPEN statement was executed for an open file.
LOCKED	After the CLOSE statement with LOCK phrase specified was executed an attempt was made to open the file.
NO-READ	The previous statement is not a successful READ statement.
NOSPACE	After a no-space condition was produced, the WRITE statement was re-executed.
NOT-OPENED	An input-output statement was executed for a closed file.
OPEN-MODE	The OPEN mode is invalid or the combination of the OPEN mode and the input-output statement is invalid.
POS-ERROR	The file position indicator is undefined.

JMP0331I-U

THREAD SYNCHRONIZATION FAILED. FILE=$1. '$2'.

System action

Abnormally terminates the program.

Response

Remove the cause of error while referring to the character string indicated in $2, then rerun the program. Table "$2 of JMP0331I-U" provides explanations and responses of the character string indicated in $2.

Table 3.26 $2 of JMP0331I-U
$2	Description	Programmer Response
CODE = 0xXXXX	A system error code is indicated.	Determine the cause while referring to the explanation on the system error code, then respond accordingly.

JMP0340I-U

CONTROL RECORD FORMAT ERROR. STM=WRITE. FILE=$1. '$2'.

System action

Abnormally terminates the program.

Explanation

The file name or access name of the processed file is output in $1. Table "$2 of JMP0340I-U" lists the strings that can be written to $2 along with the control record contents. When a blank is not set in RSV(system usage) region, this error message might be output. Confirm that a blank is set in the RSV region.

Response

Eliminate the cause of the error according to the character string written for $2, then re-execute.

Table 3.27 $2 of JMP0340I-U
$2	Field Contents
BIND	Binding direction
CMOD	Copy modification module name
DOC-INFO	Document name identification information
C-NO	Number of copies
FCB	FCB name
FID	[Solaris] Screen form descriptor name [Linux][Linux64] Form descriptor name
FORM	Forms code
FOVL	Forms overlay module name
F-NO	Number of forms overlay fields
HOP	Hopper
ID	Control record ID
LEN	Control record length
LOAD	Dynamic loading
MODE	Control mode
OFST	Print origin position
OSTK	Offset stack
PFRM	Printing format
POST	Printing surface positioning
PRTA	Unprintable area
RSV	Reserved area (not blank)
R-NO	Forms overlay printing count
SIDE	Printing surface specification
SIZE	Forms size
STK	Stacker
S-NO	Copy correction start number
T-NO	Number of character array table for copy correction
WDTH	Binding width
XTB	Name of character array table for copy correction

JMP0350I-U

USE PROCEDURE IS RECURSIVELY CALLED.

System action

Abnormally terminates the program.

Response

If execution of an input-output statement during an error procedure causes re-execution of the error procedure, do not let control reach the last statement of the first-executed error procedure.

JMP0360I-U

PS FILE ACCESS ERROR. CODE=$1.

System action

Abnormally terminates the program.

Explanation

The internal code indicating detailed error information is written for $1.

Response

Check the contents of the destination specified in the SYMBOLIC DESTINATION clause. If the contents are correct, a system error probably occurred. Collect the error information, then Contact Fujitsu Software Support.

JMP0362I-U

ORDER CREATE PROCESS ERROR. STM='$1'. FILE='$2'. CODE=$3.

System action

Abnormally terminates the program.

Response

The COBOL statement (either of OPEN, CLOSE, or WRITE) with the error is set in $1, while the file name or access name for file processing is set in $2.

[Solaris] If the print function of another company's printer is used, this error is assumed to be a system fault. Output resources and open a support incident with your support provider.
If the form descriptor is used, check the error code set in $3 and eliminate the cause. Then, rerun the program. For details on error codes, see the Systemwalker/ListWORKS online manual or the Interstage List Works online manual.

JMP0363I-U

SYMBOLIC DESTINATION ERROR. FILE=$1.

System action

Abnormally terminates the program.

Explanation

The file name or access name is written for $1.

Response

Specify the destination name in the SYMBOLIC DESTINATION clause correctly, then re-execute.

JMP0364I-U

CLAUSE '$1' ERROR. FILE=$2.

System action

Abnormally terminates the program.

Explanation

The file name or access name is written for $2.

Response

Specify the correct data item in the $1 clause, then re-execute.

JMP0370I-U

INSUFFICIENT STORAGE AVAILABLE TO PERFORM SQL.

System action

Abnormally terminates the program.

Response

For the cause and action to be taken, see "Appendix B Notes". After the action is taken, re-execute the program.

JMP0371I-U

ENVIRONMENT INFORMATION FILE ERROR TO PERFORM SQL. '$1'.

System action

Abnormally terminates the program.

Explanation

The character string indicating the error information is output in $1. Table "$1 of JMP0371I-U (with ODBC) " lists the texts that can be output to $1.

Response

Specify data in the environment information file correctly, then re-execute.

Table 3.28 $1 of JMP0371I-U (with ODBC)
$1	Description
ODBC_Inf	No ODBC information file was specified, or the specified ODBC information file does not exist.
@SQL_DATASRC	No data source name was specified.
@SQL_SERVER	No server name was specified.
@SQL_USERID	No user ID was specified.
@SQL_PASSWORD	No password was specified.

JMP0372I-U

START ENVIRONMENT ERROR TO PERFORM SQL. '$1'. $2

System action

Abnormally terminates the program.

Explanation

Table "$1 of JMP0372I-U" lists the text that can be output to $1.

Response

Eliminate the cause of the error according to the character string output for $1, then re-execute.

Table 3.29 $1 of JMP0372I-U
$1	Description	Programmer Response
LOAD	The runtime library could not be loaded.	Eliminate the cause of the error according to the detail code written for $2.
FREE	The runtime library could not be loaded.	Eliminate the cause of the error according to the detail code written for $2.

JMP0373I-I

$1 ERROR. STM=$2. SERVER=$3. '$4'.

System action

Continues program processing.

Explanation

The type of the client interface is written for $1. The error SQL statement is written for $2. The name of the error server is written for $3.

Response

Eliminate the cause of the error according to the error code written for $4, then re-execute.

For the error code, refer to the error code manual of the client interface.

JMP0374I-U

UNRECOGNIZABLE SQL STATEMENT WAS FOUND.

System action

Abnormally terminates the program.

Response

Delete the SQL statement that cannot be used, then re-execute. For SQL statements that cannot be used, see the requirements for each database environment and notes on the environment.

JMP0375I-U

THE SQL STATEMENT CANNOT BE EXECUTED IN ACCORDANCE WITH THE ENVIRONMENT INFORMATION FILE. '$1'

System action

Abnormally terminates the program.

Response

Remove the cause of error while referring to the character string indicated in $1, then rerun the program. See below.

Table 3.30 $1 of JMP0375I-U
$1	Description	Programmer Response
INV-SCOPE-THREAD	An embedded SQL statement written in the class definition is executed in an operating environment where THREAD is specified for the connection scope in the ODBC information file.	Change the value specified for the connection scope. Alternatively, change the program so that only the embedded SQL statement written in the program definition is executed.
INV-SCOPE-OBJECT-INSTANCE	An embedded SQL statement written in the program definition is executed in an operating environment where OBJECT_INSTANCE is specified for the connection scope in the ODBC information file.	Change the value specified for the connection scope. Alternatively, change the program so that only the embedded SQL statement written in the class definition is executed.

JMP0376I-U

ERROR OCCURRED BY OPENING THE ENVIRONMENT OF SymfoWARE TO EXECUTE SQL STATEMENT IN THE MULTITHREAD MODE. '$1'

System action

Abnormally terminates the program.

Response

Remove the cause of error while referring to the character string indicated in $1, then rerun the program. See below.

Table 3.31 $1 of JMP0376I-U
$1	Description	Programmer response
NOT-INSTALLED	The SymfoWARE client is not installed normally.	Ensure that the SymfoWARE client is installed normally.
ENVIRONMENT-ERROR: SymfoWARE error message	A SymfoWARE operation error has occurred.	A SymfoWARE error message is output simultaneously, so respond accordingly while referring to the Symfoware/RDB Message Reference Manual.

JMP0400I-U

ACCESS ENVIRONMENT ERROR OCCURRED. SYS=$1,FILE=$2,BLK=$3,$4=$5

System action

Abnormally terminates the program.

Explanation

A system error probably occurred. The following information is written for $1 to $5:

$1: Error information from the system, or the character string NONE if the system sends no error information
$2: System information
$3: Control block address at which the error was detected
$4: ERR or REQ
$5: The following is set as the internal error information:
- If $4 is ERR: Error-detected location
- If $4 is REQ: Processing code

Response

Collect the error information, then Contact Fujitsu Software Support.

JMP0410I-U

STOP RUN STATEMENT MUST NOT BE EXECUTED USING JMPCINT2.

System action

Abnormally terminates the program.

Response

Replace the STOP RUN statement in the application program with the EXIT PROGRAM statement.

JMP0600I-I/U

INSUFFICIENT STORAGE AVAILABLE TO PERFORM SORT OR MERGE STATEMENT.

System action

Continues program processing if the severity code is I; aborts the program if the severity code is U. The severity code is determined as follows:

I: SORT-STATUS is referred to for file definition.
U: SORT-STATUS is not referred to.

Response

For the cause and action to be taken, see "Appendix B Notes". After the action is taken, re-execute the program.

JMP0601I-I/U

SORT OR MERGE STATEMENT ERROR. $1.

System action

Continues program processing if the severity code is I; aborts the program if the severity code is U. The severity code is determined as follows:

I: SORT-STATUS is referred to for file definition.
U: SORT-STATUS is not referred to.

Explanation

The file information (file name or access name) or detailed information is output for $1. Table "$1 of JMP0601I-I/U" explains the values output for $1.

Values of detail information, meanings, and actions to be taken are listed in Table "$1 of JMP0601I-I/U"

Response

Eliminate the cause of the error according to the value output for $1, then re-execute.

Table 3.32 $1 of JMP0601I-I/U
$1	Description	Programmer Response
0	16 is set in special register SORT-STATUS.	Sorting or merging ended because 16 was set in special register SORT-STATUS. No programmer response is necessary.
50	Memory is insufficient	Modify the environment to allocate enough memory (*1)
51	An error occurred during input processing for the record to be sorted.	If the same error occurs when the program is re-executed, a system error probably occurred. Collect the error information, then Contact Fujitsu Software Support.
52	Memory is insufficient.	Modify the environment to allocate enough memory. (*1)
53 54 56 59 62	An error occurred during input processing for the record to be sorted.	If the same error occurs when the program is re-executed, a system error probably occurred. Collect the error information, then Contact Fujitsu Software Support.
100	An error occurred in the sort-merge program.
101	An error occurred during input processing for the record to be sorted.
102	An error occurred during output processing for the record to be sorted.
103	An error occurred during input processing for the record to be merged.
110	The address of the record to be sorted could not be obtained.
111	The record length is invalid.	Check whether the record length complies with the COBOL specification.
112 113	An error occurred during input processing for the record to be sorted.	If the same error occurs when the program is re-executed, a system error probably occurred. Collect the error information, then Contact Fujitsu Software Support.
114	An error occurred during input processing for the record to be merged.	Correct the program so that it merges the records in the target file after sorting.
208	An error occurred when a temporary file (for sorting and merging) was opened.	The work area may be insufficient. Use environment variable BSORT_TMPDIR and specify a work directory. Modify the environment to allocate a large enough temporary file. If the same error occurs when the program is re-executed, a system error probably occurred. Collect the error information, then Contact Fujitsu Software Support.
212	The size of the temporary file (for sorting and merging) is insufficient.	Modify the environment (e.g., hard disk) to allocate a large enough temporary file.
214	A temporary file (for sorting and merging) cannot be created.	Modify the environment (e.g., hard disk) to allocate a large enough temporary file.
224	An error occurred during write to a temporary file (for sorting and merging).	If the same error occurs when the program is re-executed, a system error probably occurred. Collect the error information, then Contact Fujitsu Software Support.
250	A sort-merge program error occurred.	If the same error occurs when the program is re-executed, a system error probably occurred. Collect the error information and open a support incident with your support provider.
Other	Error occurred in PowerBSORT (when PowerBSORT) is being used.	Refer to the "PowerBSORT User's Guide" or access the Help information.

*1 For the action to be taken, see "Appendix B Notes".

JMP0608I-I/U

RELEASE STATEMENT CAN NOT BE EXECUTED IN OUTPUT PROCEDURE.

System action

Continues program processing if the severity code is I; aborts the program if the severity code is U. The severity code is determined as follows:

I: SORT-STATUS is referred to for file definition.
U: SORT-STATUS is not referred to.

Response

Correct the program.

JMP0609I-I/U

RETURN STATEMENT CAN NOT BE EXECUTED IN INPUT PROCEDURE.

System action

Continues program processing if the severity code is I; aborts the program if the severity code is U. The severity code is determined as follows:

I: SORT-STATUS is referred to for file definition.
U: SORT-STATUS is not referred to.

Response

Correct the program.

JMP0612I-I/U

RETURN STATEMENT CAN NOT BE EXECUTED AFTER AT END.

System action

Continues program processing if the severity code is I; aborts the program if the severity code is U. The severity code is determined as follows:

I: SORT-STATUS is referred to for file definition.
U: SORT-STATUS is not referred to.

Response

Correct the program so that the RETURN statement is not executed after a file at end condition is produced.

JMP0613I-I/U

SORT/MERGE LIBRARY CANNOT BE LOADED. $1 $2

System action

Continues program processing if the severity code is I; aborts the program if the severity code is U. The severity code is determined as follows:

I: SORT-STATUS is referred to for file definition.
U: SORT-STATUS is not referred to.

Explanation

The library file name is set in $1 and the error code is set in $2.

Note

If $1 and $2 are not output, confirm whether or not PowerBSORT is correctly installed.

Response

Check the following and take necessary action, then re-execute the program.

[Linux][Solaris] Whether the sort-merge library (process model : libcobsrt.so or multithread model : librcobsrt.so) exists
Whether the sort-merge library (libcobsrt.so or librcobsrt.so) path is set in environment variable LD_LIBRARY_PATH
Whether PowerBSORT is correctly installed.

JMP0614I-I/U

SORT/MERGE STATEMENT CANNOT BE EXECUTED IN AN INPUT/OUTPUT PROCEDURE.

System action

Continues the program process if the severity code is I but terminates the program abnormally if the severity code is U.

The severity code is I if special register SORT-STATUS is referenced in the program. Otherwise, the severity code is U.

Response

Modify the program so that the SORT statement or MERGE statement will not be executed while the input or output procedure described in the SORT or MERGE statement is in progress.

JMP0615I-I/U

THREAD SYNCHRONIZATION FAILED DURING THE SORT/MERGE STATEMENT. '$1'.

System action

Continues program processing if the severity code is I but terminates the program abnormally if the severity code is U. The severity code is I if special register SORT-STATUS is referenced in the program; otherwise, the severity code is U.

Response

Remove the cause of error while referring to the character string indicated in $1, then rerun the program. Table "$1 of JMP0615I-I/U" provides explanations and responses of the character string indicated in $1.

Table 3.33 $1 of JMP0615I-I/U
$1	Description	Programmer Response
CODE = 0xXXXX	A system error code is indicated.	Determine the cause of error while referring to the explanation on the system error code, then respond accordingly.

JMP0616I-U

THREAD SYNCHRONIZATION FAILED.

System action

Abnormally terminates the program.

Response

An error was detected during thread synchronization. If the error occurs frequently, a system failure is assumed. Collect data and contact a supplier.

JMP0701I-U

GCB IS BROKEN.

System action

Abnormally terminates the program.

Response

The area (GCB) used by the COBOL runtime system is destroyed. Check for the following items, correct the program and rerun it.

If an item including a subscript, index, reference modification, or OCCURS DEPENDING ON clause is referred to, confirm that the item is within the allowable reference range.
If there is a parameter for transferring data through the CALL statement, confirm that the sender and receiver have the same parameter attributes. (Be sure to check the length attribute.)
If a file is used, confirm that the correct record length is referenced. (For example, if SPACE clear processing is performed with the maximum record length instead of the actual record length when a variable-length input file is used, the record length referenced is incorrect.)

JMP0702I-U

LIA IS BROKEN.

System action

Abnormally terminates the program.

Response

The area (LIA) used by the COBOL runtime system is destroyed.

See JMP0701I-U.

JMP0703I-U

RCB IS BROKEN.

System action

Abnormally terminates the program.

Response

The area (RCB) used by the COBOL runtime system is destroyed.

See JMP0701I-U.

JMP0704I-U

DEBUG TABLE IS BROKEN.

System action

Abnormally terminates the program.

Response

See JMP0701I-U.

JMP0705I-W

INSUFFICIENT STORAGE AVAILABLE. FUNC=$1.

System action

Cancels the '$1' function, then continues processing.

Explanation

The function name of the debug function is set in $1.

Response

For the cause and action to be taken, see "Appendix B Notes". After the action is taken, re-execute the program.

JMP0724I-W

FILE CAN NOT BE OPENED. FILE=$1. '$2' OPTION IGNORED.

System action

Continues processing without outputting '$2' information.

Response

Determine whether the file has been allocated normally. $1 indicates the access name of the failing file, and $2 indicates the debug function name.

JMP0725I-W

FILE CAN NOT BE OPENED. '$1' OPTION IGNORED. '$2'

System action

Stop outputting '$1' information to continue processing.

Explanation

The debug function name is written for $1.

Response

Correct the error in the character string in $2, then rerun the program.

Table 3.34 $2 of JMP0725I-W
$2	Description	Programmer Response
ERRCD = 0xXXXX	A system error code (error) is indicated.	Refer to the system error code description.

JMP0726I-W

THE VALUE OF ENVIRONMENT VARIABLE '$1' IS INVALID. '$2' OPTION IGNORED.

System action

The output of the '$2' information is canceled, and program processing continues.

Response

Specify a correct value for the environment variable '$1,' and retry the operation.

JMP0727I-W

MAXIMUM SIZE OF THE FILE IS EXCEEDED. FILE='$1'. '$2' OPTION IGNORED.

System action

Output of '$2' information is canceled, and program processing is continued.

Response

Check the size of the file specified for the environment variable '$1,' and retry the operation.

JMP0771I-W

THE VALUE OF ENVIRONMENT VARIABLE $1 IS INVALID.

System action

Processing continues as though the environment variable ($1) was not specified.

Response

Specify the correct value in the environment variable ($1), and re-execute.

Refer to "CBR_ATTACH_TOOL" in the "NetCOBOL User's Guide" for details on the environment variable.

JMP0772I-W

THE INVOKE OF THE $1 FAILED. '$2'. '$3'

System action

Processing continues as though the environment variable CBR_ATTACH_TOOL was not specified.

Response

Remove the cause of the error by referring to the string specified to $2, and execute again.

The line that indicates the tool ([Solaris][Linux] COBOL DEBUGGER, [Linux64] STUDIO) is set to $1.

Detailed information on the cause of the error is set to $3.

Table "$2 and $3 of JMP0772I-W" shows the string set to $2 and $3.

Table 3.35 $2 and $3 of JMP0772I-W
$2	Description	Detailed information ($3)	Programmer Response
API ERROR	A system error was detected.	API=API-name, CODE=error-code (hexadecimal)	Please open a support incident to obtain assistance from a supplier.

Note

When ($3) is "API=semid CODE=1c" or "API=semop CODE=1c", check the following points. If none of these seem to apply, the cause may be system trouble. In this case, retrieve the data and open a support incident with your support provider.

When you start debugging from a program and you forcibly terminate the program before debugging starts, this will cause semaphores. If this operation is repeated, the number of semaphores that remain will increase and you will not be able to create new semaphores. This error will occur in this situation. It is recommended that you not forcibly terminate the program before debugging starts.
Semaphores, message queues, and shared memory have become full. Delete any unnecessary resources. To browse the state of these resources, use the ipcs command. Use the ipcrm command to refer the state of resources. Ask the system administrator to delete the resources correctly.

JMP0774I-W

REMOTE DEBUG ERROR, CONNECTING CLIENT FAILED. $1. $2

System action

Processing continues as though the environment variable CBR_ATTACH_TOOL was not specified.

Response

Refer to the information set in $1, fix the cause of the error, and then re-execute. The meaning and corrective action procedure for the information set in $1 is shown in Table "$1 of JMP0774I-W". Detailed information is set in $2.

Table 3.36 $1 of JMP0774I-W
$1	Description	Programmer Response
0	The remote debugger resources have not been installed correctly.	Install the remote debugger.
2	There is an error in the investigation procedure in the environment variable CBR_ATTACH_TOOL.	$2 is not supported in remote debugging. Specify a supported format. The string specified in the environment variable is set in $2.
10	There is an error in the access destination in the environment variable CBR_ATTACH_TOOL.	Check that there are no spelling mistakes in the host name for accessing the client. Check that the host name for accessing the client has been defined.
11		Check that there are no errors in the IP address definition for resolving the host name. Check that there are no mistakes in the format for the IP address.
12		There is a value that is outside the range that can be set for the port number. Set a range from 1024 to 65535.
20	Access to the client failed.	Check that the client remote debugger connector runs on a computer specified in the access destination. Check that the access is permitted according to the client remote debugger connector access restriction.
21	The version of the remote debugger is not appropriate.	Make sure that the versions of the client and server debuggers are compatible.
30	The code conversion of the specified combination is not supported.	Enable the code conversion set to $2. The character string specified for the environment variable is set to $2.
31	The character outside the SJIS range was specified.	The character beyond the limits of shift JIS is included since the character string set to $2. Change the corresponding character to the character within the range of shift JIS. The character string specified for the environment variable is set to $2.

JMP0775I-W

REMOTE DEBUG ERROR, CLIENT WAS DISCONNECTED. $1

System action

Processing continues as though the environment variable CBR_ATTACH_TOOL was not specified.

Response

Refer to the information set in $1, fix the cause of the error, and then re-execute. The meaning and corrective action procedure for the information set in $1 is shown in Table "$1 of JMP0775I-W".

Table 3.37 $1 of JMP0775I-W
$1	Description	Programmer Response
0	The packet might have been falsified, so access to the client was interrupted.	Verify with the network administrator that the environment is secure.
1	Access to the client was interrupted.	Check whether access was denied because of a restriction on access to the client remote debugger connector. Access was interrupted because the client application was closed. Verify that the client remote debugger connector has started. Verify that the network can be used.

JMP0776I-W

REMOTE DEBUG ERROR OCCURRED AT '$2' IN '$1'. $3. $4

System action

Processing continues as though the environment variable CBR_ATTACH_TOOL was not specified.

Response

Re-execute. If the problem continues, open a support incident to obtain assistance from a supplier. The following is set in $1 to $4.

$1: Module name
$2: API name
$3: Error code (decimal notation)
$4: Error code description

JMP0810I-E/U

FAILURE IN $2 PARAMETER OF THE '$1' METHOD. $3 $4 $5

System action

Uses the parameter as it is and continues processing if the severity code is E.

Abnormally terminates the program if the severity code is U.

Explanation

The following information is set in $1 through $5:

$1: Name of the method with an incorrect parameter is specified.
$2: Parameter specification (USING or RETURNING)
$3: USING specified parameter error details
"NUMBER": The number of parameters is incorrect
PARAMETER=n: The n-th parameter is incorrect.
$4: External program name or method name
$5: Statement number
- [Linux][Solaris] [COPY-qualification-value-]line-number.verb-sequence-number-in-a-line
- [Linux64] [COPY-qualification-value-]line-number

Response

Modify the program so that the method ($1) indicated by the message will be called with the correct parameter then re-execute the program.

JMP0812I-E/U

FAILURE IN '$1' OF CALL STATEMENT. $2. $3.

System action

Continues processing when the severity code is E level, while still using invocation rules or parameters as they are.

Abnormally terminates the program when the severity code is U level.

Response

Based on the content indicated by $1, perform the action described in Table "$1 of JMP0812I-E/U".

Table 3.38 $1 of JMP0812I-E/U
$1	Programmer Response
USING PARAMETER NUMBER	Match the number of USING phrase parameters
USING nTH PARAMETER (nTH = 1ST, 2ND, 3RD, 4TH...)	Match the size of the nth USING phrase parameters
RETURNING PARAMETER	Match the size of the RETURNING phrase parameters

The following information is specified in $2 and $3:

$2: A program name, or a class name and method name
$3: The statement number
- [Linux][Solaris] [COPY-qualification-value-]line-number.verb-sequence-number-in-a-line
- [Linux64] [COPY-qualification-value-]line-number

JMP0820I-E/U

SUBSCRIPT/INDEX IS OUT OF RANGE. $1. $2. OPD=$3 ($4)

System action

Severity code E level : Uses the subscript or index value as is, then continues processing.

Severity code U level : Abnormally terminates the program.

Explanation

The following information is set in $1 through $4:

$1 : The outermost program name or method name.
$2 : The statement number
- [Linux][Solaris] [COPY-qualification-value-]line-number.verb-sequence-number-in-a-line
- [Linux64] [COPY-qualification-value-]line-number
$3 : The data name
$4 : The number of dimensions

Response

Specify a correct value for the subscript or index indicated in the message, then re-execute.

JMP0821I-E/U

REFERENCE MODIFIER IS OUT OF RANGE. $1. LINE=$2. OPD=$3.

System action

Severity code E level : Performs reference with an incorrect value, then continues processing.

Severity code U level : Abnormally terminates the program.

Explanation

$1 : The outermost program name or method name
$2 : The statement number
- [Linux][Solaris] [COPY-qualification-value-]line-number.verb-sequence-number-in-a-line
- [Linux64] [COPY-qualification-value-]line-number
$3 : The data name

Response

Correct the program so that reference modification of the data item indicated in the message is performed within the specified range.

JMP0822I-E/U

ODO OBJECT VALUE IS OUT OF RANGE. $1. LINE=$2. OPD=$3. ODO=$4.

System action

Severity code E level : Uses the object value specified in the OCCURS DEPENDING ON clause as is, then continues processing.

Severity code U level : Abnormally terminates the program.

Explanation

The following information is set in $1 through $4:

$1 : The outermost program name or method name
$2 : The statement number
- [Linux][Solaris] [COPY-qualification-value-]line-number.verb-sequence-number-in-a-line
- [Linux64] [COPY-qualification-value-]line-number
$3 : The name of the data that refers to the data including the OCCURS DEPENDING outermost-program-name ON clause
$4 : The object name specified in the ODO clause

Response

Specify a correct value for the object (in the OCCURS DEPENDING ON clause) indicated in the message, then re-execute.

JMP0828I-E/U

INVALID VALUE SPECIFIED. $1. LINE=$2. OPD=$3.

System action

Uses the incorrect value as it is and continues processing if the severity code is E.

Abnormally terminates the program if the severity code is U.

Explanation

The following information is set in $1 through $3:

$1: External program name or method name
$2: Statement number
- [Linux][Solaris] [COPY-qualification-value-]line-number.verb-sequence-number-in-a-line
- [Linux64] [COPY-qualification-value-]line-number
$3: Data name

Response

Modify the program so that the reference modification of the data name indicated by the message will not exceed the range then re-execute the program.

JMP0829I-E/U

DIVIDED BY ZERO. $1. LINE=$2. OPD=$3.

System action

Uses zero as the divisor as it is and continued processing if the severity code is E. The result of dividing by zero depends on the system.

Abnormally terminates the program if the severity code is U.

Explanation

The following information is set in $1 through $3:

$1: External program name or method name
$2: Statement number
- [Linux][Solaris] [COPY-qualification-value-]line-number.verb-sequence-number-in-a-line
- [Linux64] [COPY-qualification-value-]line-number
$3: Data name

The operand name is not set if the divisor is a value of an arithmetic expression or a function.

Response

Set a value that does not make the divisor zero for the operand indicated by the message then re-execute the program.

JMP0899I-U

LOGICAL ERROR.

System action

Abnormally terminates the programs.

Response

The program or dynamic area may be damaged because of a program error. Check for the cause of the error in the same manner as when JMP0701I-U is written.

JMP0901I-E

FUNCTION $1 ERROR, ARGUMENT ABSOLUTE VALUE IS MORE THAN 3.53E+15.

System action

Returns 0, then continues processing.

Explanation

The name of the error function (SIN or COS) is written for $1.

Response

Specify the absolute value of the argument within the calculation enabled range, then re-execute.

JMP0902I-E

FUNCTION $1 ERROR, ARGUMENT ABSOLUTE VALUE IS MORE THAN 1.0.

System action

Returns 0, then continues processing.

Explanation

The name of the error function (ASIN or ACOS) is written for $1.

Response

Specify the absolute value of the argument that can be stored in the definition area, then re-execute.

JMP0903I-E

FUNCTION $1 ERROR, ARGUMENT VALUE IS OUT OF RANGE.

System action

Returns 0, then continues processing.

Explanation

The name of the error function (LOG, LOG10, ANNUITY, FACTORIAL, RANDOM, SQRT, or TAN) is written for $1.

Response

Specify the value of the argument that can be stored in the definition area, then re-execute.

JMP0904I-E

FUNCTION $1 ERROR, ARGUMENT VALUE IS INVALID.

System action

Returns 0, then continues processing.

Explanation

The name of the error function is written for $1.

Response

Specify the value of the argument that satisfies the condition of each function, then re-execute.

JMP0905I-E

FUNCTION ANNUITY ERROR, ARITHMETIC EXCEPTION.

System action

Returns 0, then continues processing.

Response

Specify the value of the argument that satisfies the condition of each function, then re-execute.

JMP0931I-U

INSUFFICIENT STORAGE AVAILABLE FOR THE '$2' METHOD OF THE SPECIAL CLASS '$1'.

System action

Abnormally terminates the program .

Response

For the cause and action to be taken, see "Appendix B Notes". After the action is taken, allow the execution environment for method ($2) to acquire the area then re-execute the program.

JMP0932I-E/U

FAILURE IN $3 PARAMETER OF THE '$2' METHOD OF THE SPECIAL CLASS '$1'. $4

System action

If the severity code is E, the system continues processing.

If the severity code is U, the system abnormally terminates the program.

Explanation

The following is set in $1 through $4:

$1: Special class name
$2: Name of the method with an incorrect parameter is specified.
$3: Parameter specification (USING or RETURNING)
$4: USING specified parameter error details
- "NUMBER": The number of parameters is incorrect.
- PARAMETER=n: The n-th parameter is incorrect.

Response:

Modify the program so that the parameter in the method ($2) indicated by the message will be an attribute usable in the special class and conform to the interface for the calling method then re-execute the program.

JMP0933I-E/U

TYPE CONVERSION ERROR OCCURRED IN $3 PARAMETER OF THE '$2' METHOD OF THE SPECIAL CLASS '$1'. $4

System action

If the severity code is E, the system continues processing.

If the severity code is U, the system abnormally terminates the program.

Explanation:

The following information is set in $1 through $4. See the on-line help or manual of the application (including the COM server).

$1: Special class name
$2: Name of the method whose the incorrect parameter attribute is specified
$3: Parameter specification (USING or RETURNING)
$4: USING specified parameter error details
- PARAMETER=n: The attribute of the n-th parameter is incorrect.

Response:

Modify the program so that the parameter corresponding to the attribute for the parameter in the method ($2) for the COM server will be specified then re-execute the program.

JMP0935I-U

TOO MANY ITEMS WERE REGISTERED. SPECIAL CLASS=$1.

System action

Abnormally terminates the program.

Response

Correct the program so that the number of data items to register does not exceed the maximum allowed. Execute again.

Increase the maximum number of data items to register specified when the object of the special class ($1) is created. The number should be increased according to the number of data items to register.
Decrease the number of data items to register to the object of the special class ($1).