Top
NetCOBOL V11.0 Messages
FUJITSU Software

3.3.7 JMP0700 - JMP0799

0701

0702

0703

0704

0705

0724

0725

0726

0727

0771

0772

0773

0774

0775

0776

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 "D.1 Virtual Memory Shortages". After the action is taken, re-execute the program.

JMP0724I-W

FILE CANNOT BE OPENED.  FILE=$1. '$2' OPTION IGNORED.

System action

Continues processing without outputting '$2' information.

Response

  • Verify whether the allocation of the file is correct.

  • Verify whether the file attribute is correct.

  • Verify whether the debugging information is output from two or more processes to the same file.

$1 indicates the access name of the failing file, and $2 indicates the debug function name.

JMP0725I-W

FILE CANNOT 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

  • [Win32] Refer to "@CBR_ATTACH_TOOL (TOOL(Invoke debugger or COBOL Error Report from application)" and "@CBR_JUSTINTIME_DEBUG (Specify inspection using the debugger or the COBOL Error Report at abnormal termination)" in Chapter 5 of the "NetCOBOL User's Guide".

  • [Winx64] Refer to "@CBR_JUSTINTIME_DEBUG (Specify inspection using the COBOL Error Report at abnormal termination)" in Chapter 5 of the "NetCOBOL User's Guide", and the descriptions about @CBR_ATTACH_TOOL in the "NetCOBOL Studio User's Guide".

JMP0772I-W

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

System action

Processing continues as though the environment variable @CBR_ATTACH_TOOL or @CBR_JUSTINTIME_DEBUG 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 (COBOL DEBUGGER or COBOL ERROR REPORT) is set to $1.

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

The table below shows the string set to $2 and $3.

Table 3.35 $2 and $3 of JMP0772I-W

$2

Description

Detailed information ($3)

Programmer Response

SNAP ERROR

COBOL ERROR REPORT did not operate correctly.

COBOL ERROR REPORT could not operate correctly.

Specify @CBR_JUSTINTIME_DEBUG=NO to stop COBOL ERROR REPORT, and re-execute the application.

API=api-name, CODE=errorcode (in hexadecimal)

If an error message is displayed, refer to the contents of the displayed message and troubleshoot the problem.

If logging of COBOL ERROR REPORT is necessary, review the runtime environment, including the following:

  • Whether COBOL is correctly installed

  • Whether there is sufficient memory

  • Whether the system is in a state other than the busy state

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.

LOGON FAILED

Logon failed.

DOMAIN=domain-name,USER=user-name,

PASSWORD=password

Please open a support incident to obtain assistance from a Supplier.

SERVICE NOT RUN

Service is not activated.

NAME=service-name

Open Service from the Control panel and activate the service ($3).

SERVICE BUSY

Service is in busy state.

NAME=service-name

Execute again. If errors repeatedly occur, determine if there is an operational problem.

JMP0773I-W

THE COBOL DEBUGGER DID NOT RESPOND THOUGH PASSED THE TIME-OUT INTERVAL.

System action

  • [Win32] The system ends COBOL debugger, and then regards that the environment variable @CBR_ATTACH_TOOL was not specified, and continues the process.

  • [Winx64] The system ends remote debugging that uses NetCOBOL Studio, and then regards that the environment variable @CBR_ATTACH_TOOL was not specified, and continues the process.

Response

  • [Win32] There is no response to the request from COBOL debugger activated. Execute again and respond to the request from COBOL debugger.

  • [Winx64] There is no response to the request from NetCOBOL Studio activated. Execute again and respond to the request from COBOL debugger.

JMP0774I-W

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

System action

  • [Win32] Processing continues as though the environment variable @CBR_ATTACH_TOOL or @CBR_JUSTINTIME_DEBUG was not specified.

  • [Winx64] 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 below. Detailed information is set in $2.

Table 3.36 $1 of JMP0774I-W

$1

Description

Programmer Response

0

[Win32] The remote debugger resources have not been installed correctly.

[Winx64] The NetCOBOL Studio resources have not been installed correctly.

Install NetCOBOL correctly.

1

winsock1.1(TCP/IP) is not supported.

Re-execute in an environment that can use winsock1.1.

2

[Win32] There is an error in the investigation procedure in the environment variable @CBR_ATTACH_TOOL or @CBR_JUSTINTIME_DEBUG.

[Winx64] 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

[Win32] There is an error in the access destination in the environment variable @CBR_ATTACH_TOOL or @CBR_JUSTINTIME_DEBUG.

[Winx64] 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.

JMP0775I-W

REMOTE DEBUG ERROR, CLIENT WAS DISCONNECTED. $1

System action

  • [Win32] Processing continues as though the environment variable @CBR_ATTACH_TOOL or @CBR_JUSTINTIME_DEBUG was not specified.

  • [Winx64] 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 below.

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

  • [Win32] Processing continues as though the environment variable @CBR_ATTACH_TOOL or @CBR_JUSTINTIME_DEBUG was not specified.

  • [Winx64] 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