gtpm5m1mMessages (Online)

INIP-IPDB

INIP0001IINDIVIDUAL IP TRACE tracename DEFINED

Where:

tracename
The name of the individual Internet Protocol (IP) trace that is being defined.

Explanation: This is the normal response to the ZINIP command with the DEFINE parameter specified.

System Action: Tracing for the specified individual IP trace name begins.

User Response: None.

See TPF Operations for more information about the ZINIP command.

INIP0002IINDIVIDUAL IP TRACE tracename MODIFIED

Where:

tracename
The name of the individual Internet Protocol (IP) trace that is being modified.

Explanation: This is the normal response to the ZINIP command with the MODIFY parameter specified.

System Action: The properties of the specified individual IP trace are changed.

User Response: None.

See TPF Operations for more information about the ZINIP command.

INIP0003IINDIVIDUAL IP TRACE tracename DELETED

Where:

tracename
The name of the individual Internet Protocol (IP) trace that is being deleted.

Explanation: This is the normal response to the ZINIP command with the DELETE and NAME parameters specified.

System Action: The specified individual IP trace is deleted.

User Response: None.

See TPF Operations for more information about the ZINIP command.

INIP0004IALL INDIVIDUAL IP TRACES ARE DELETED

Explanation: This is the normal response to the ZINIP command with the DELETE and ALL parameters specified.

System Action: All individual Internet Protocol (IP) traces are deleted.

User Response: None.

See TPF Operations for more information about the ZINIP command.

INIP0005IINDIVIDUAL IP TRACE SUMMARY

Explanation: This is the normal response to the ZINIP command with the SUMMARY parameter specified.

System Action: Information about the individual Internet Protocol (IP) traces that have been defined are displayed.

User Response: None.

See TPF Operations for more information about the ZINIP command.

INIP0006IINDIVIDUAL IP TRACE tracename DISPLAY

Where:

tracename
The name of the individual Internet Protocol (IP) trace that is being displayed.

Explanation: This is the normal response to the ZINIP command with the DISPLAY parameter specified.

System Action: The contents of the specified individual IP trace table are displayed.

User Response: None.

See TPF Operations for more information about the ZINIP command.

INIP0007IINDIVIDUAL IP FORMATTED TRACE tracename DISPLAY

Where:

tracename
The name of the individual Internet Protocol (IP) trace that is being displayed.

Explanation: This is the normal response to the ZINIP command with the DISPLAY and FORMAT parameters specified.

System Action: The contents of the specified individual IP trace table are displayed.

User Response: None.

See TPF Operations for more information about the ZINIP command.

INIP0008IINDIVIDUAL IP TRACE TABLE tracename IS EMPTY

Where:

tracename
The name of the individual Internet Protocol (IP) trace.

Explanation: This is the normal response to the ZINIP command with the DISPLAY parameter specified when there are no entries in the individual IP trace table.

System Action: None.

User Response: Do the following:

  1. Enter the ZINIP command with the SUMMARY parameter specified to ensure that the specified individual IP trace is not paused.
  2. Do one of the following:
See TPF Operations for more information about the ZINIP command.

INIP0009IINDIVIDUAL IP TRACE tracename RESET

Where:

tracename
The name of the individual Internet Protocol (IP) trace that is being reset.

Explanation: This is the normal response to the ZINIP command with the RESET parameter specified.

System Action: The specified individual IP trace table is initialized.

User Response: None.

See TPF Operations for more information about the ZINIP command.

INIP0010IINDIVIDUAL IP TRACE DEFINITION RECORD RELOADED FROM FILE

Explanation: During TPF system restart, the individual Internet Protocol (IP) trace definition record is reloaded from file.

System Action: None.

User Response: None.

See TPF Transmission Control Protocol/Internet Protocol for more information about individual IP trace support.

INIP0011IINDIVIDUAL IP TRACE DEFINITION RECORD HAS BEEN INITIALIZED

Explanation: During TPF system restart, the individual Internet Protocol (IP) trace definition record is initialized.

System Action: None.

User Response: None.

See TPF Transmission Control Protocol/Internet Protocol for more information about individual IP trace support.

INIP0020EFORMAT OF THE ZINIP COMMAND IS NOT VALID

Explanation: The ZINIP command was entered, but the combination of parameters specified is not valid.

System Action: The command is rejected.

User Response: Enter the ZINIP command again and specify a valid combination of parameters.

See TPF Operations for more information about the ZINIP command.

INIP0021EREJECTED, SYSTEM IS IN RESTART

Explanation: The ZINIP command was entered, but the TPF system is in restart mode.

System Action: The command is rejected.

User Response: Do the following:

  1. Wait for the TPF system to reach 1052 state.
  2. Enter the ZINIP command again.

See TPF Operations for more information about the ZINIP command.

INIP0022EREJECTED, INDIVIDUAL IP TRACE SUPPORT IS NOT DEFINED

Explanation: The ZINIP command was entered, but individual Internet Protocol (IP) trace support is not defined.

System Action: The command is rejected.

User Response: Do the following:

  1. Code the individual IP trace table support parameters in the SNAKEY macro.
  2. Reassemble keypoint record 2 (CTK2) against the SNAKEY macro.
  3. Reload CTK2.
  4. IPL the TPF system.
  5. Enter the ZINIP command again.

See TPF Operations for more information about the ZINIP command. See TPF Transmission Control Protocol/Internet Protocol for more information about the SNAKEY parameters that are required for individual IP trace support. See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.

INIP0023EREJECTED, REMOTE IP ADDRESS SPECIFIED IS NOT VALID

Explanation: The ZINIP command was entered with the DEFINE and RIP parameters specified, but the specified remote Internet Protocol (IP) address is not in a valid format or is one of the following reserved IP addresses:

System Action: The command is rejected.

User Response: Enter the ZINIP command again with the DEFINE parameter specified, and specify a valid value for the RIP parameter.

See TPF Operations for more information about the ZINIP command.

INIP0024EREJECTED, VALUE OF THE PORT PARAMETER IS NOT VALID

Explanation: The ZINIP command was entered with the DEFINE and PORT parameters specified, but the value specified for the PORT parameter is not valid.

System Action: The command is rejected.

User Response: Enter the ZINIP command again with DEFINE parameter specified, and specify a valid value for the PORT parameter.

See TPF Operations for more information about the ZINIP command.

INIP0025EREJECTED, VALUE OF THE SIZE PARAMETER IS NOT VALID

Explanation: The ZINIP command was entered with the DEFINE or MODIFY parameters specified, but the value specified for the SIZE parameter is not valid.

System Action: The command is rejected.

User Response: Enter the ZINIP command again with DEFINE or MODIFY parameter specified, and specify a valid value for the SIZE parameter.

See TPF Operations for more information about the ZINIP command.

INIP0026EREJECTED, INDIVIDUAL IP TRACE tracename ALREADY EXISTS

Where:

tracename
The name of the individual Internet Protocol (IP) trace.

Explanation: The ZINIP command was entered with the DEFINE parameter specified, but the specified individual IP trace name is already defined.

System Action: The command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZINIP command.

INIP0027EREJECTED, INDIVIDUAL IP TRACE tracename DOES NOT EXIST

Where:

tracename
The name of the individual Internet Protocol (IP) trace.

Explanation: The ZINIP command was entered with the DELETE, DISPLAY, MODIFY, or RESET parameter specified, but the specified individual IP trace name is not defined.

System Action: The command is rejected.

User Response: Enter the ZINIP command again and specify an individual IP trace name that is defined.

See TPF Operations for more information about the ZINIP command.

INIP0028EREJECTED, MAXIMUM NUMBER OF INDIVIDUAL IP TRACES ALREADY DEFINED

Explanation: The ZINIP command was entered with the DEFINE parameter specified, but the maximum number of individual Internet Protocol (IP) traces has already been defined.

System Action: The command is rejected.

User Response: Follow Step 1 or Step 2.

Step 1: Do the following:

  1. Enter the ZINIP command with the SUMMARY parameter specified and examine all the individual IP traces defined.
  2. Enter the ZINIP command with the DELETE parameter specified to delete any individual IP traces that are not needed.
  3. Enter the ZINIP command again with the DEFINE parameter specified.

Step 2: Do the following:

  1. Increase the value of the IPTRCNUM parameter in the SNAKEY macro.
  2. Reassemble keypoint record 2 (CTK2) against the SNAKEY macro.
  3. Reload CTK2.
  4. IPL the TPF system.
  5. Enter the ZINIP command again.

See TPF Operations for more information about the ZINIP command. See TPF Transmission Control Protocol/Internet Protocol for more information about the SNAKEY parameters that are required for individual IP trace support. See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.

INIP0029EMALOC ERROR, CANNOT DISPLAY INDIVIDUAL IP TRACE TABLE

Explanation: The ZINIP command was entered with the DISPLAY parameter specified, but there is not enough storage in the TPF system to display the individual Internet Protocol (IP) trace table.

System Action: The command is rejected.

User Response: Do the following:

  1. Determine why there is not enough storage in the TPF system.
  2. Correct the problem.
  3. Enter the ZINIP command again with the DISPLAY parameter specified.

See TPF Operations for more information about the ZINIP command. See TPF General Macros for more information about MALOC macro usage and storage.

IPDB0001INETWORK SERVICES DATABASE REFRESHED

Explanation: This is the normal response to the ZIPDB command with the REFRESH parameter specified.

System Action: The TCP/IP network services database is refreshed to core storage.

User Response: None.

See TPF Operations for more information about the ZIPDB command. See TPF Transmission Control Protocol/Internet Protocol for more information about TCP/IP network services database support.

IPDB0010EREJECTED, SYSTEM IS IN RESTART

Explanation: The ZIPDB command was entered, but the TPF system is in restart mode.

System Action: The command is rejected.

User Response: Do the following:

  1. Wait for the TPF system to reach 1052 state.
  2. Enter the ZIPDB command again.

See TPF Operations for more information about the ZIPDB command. See TPF Transmission Control Protocol/Internet Protocol for more information about TCP/IP network services database support.

IPDB0011EREJECTED, TCP/IP NATIVE STACK SUPPORT NOT DEFINED

Explanation: The ZIPDB command was entered, but TCP/IP native stack support is not defined.

System Action: The command is rejected.

User Response: Do the following:

  1. Code the TCP/IP native stack support parameters in the SNAKEY macro.
  2. Reassemble keypoint record 2 (CTK2) against the SNAKEY macro.
  3. Reload CTK2.
  4. IPL the TPF system.
  5. Enter the ZIPDB command again.

See TPF Operations for more information about the ZIPDB command. See TPF Transmission Control Protocol/Internet Protocol for more information about the SNAKEY parameters that are required for TCP/IP native stack support. See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.

IPDB0012EREJECTED, FILE /etc/services DOES NOT EXIST

Explanation: The ZIPDB command was entered with the REFRESH parameter specified, but the /etc/services file does not exist.

System Action: The command is rejected.

User Response: Do the following:

  1. Create the /etc/services file on the TPF file system.
  2. Enter the ZIPDB command again with the REFRESH parameter specified.

See TPF Operations for more information about the ZIPDB command. See TPF Transmission Control Protocol/Internet Protocol for more information about TCP/IP network services database support and the /etc/services file.

IPDB0013EERROR OPENING FILE /etc/services, ERRNO description

Where:

description
The errno function value.

Explanation: The ZIPDB command was entered with the REFRESH parameter specified, but an error occurred when opening the /etc/services file.

System Action: The command is rejected.

User Response: Look in errno.h to see a description of the error and do one of the following:

See TPF Operations for more information about the ZIPDB, ZFILE ls, and ZFILE chmod commands. See TPF Transmission Control Protocol/Internet Protocol for more information about TCP/IP network services database support.

IPDB0014ETOO MANY APPLICATIONS DEFINED IN FILE /etc/services

Explanation: The ZIPDB command was entered with the REFRESH parameter specified, but there are too many applications defined in the /etc/services file.

System Action: The command is rejected.

User Response: Do the following:

  1. Code the /etc/services file again with a valid number of rules defined.
  2. Enter the ZIPDB command again with the REFRESH parameter specified.

See TPF Operations for more information about the ZIPDB command. See TPF Transmission Control Protocol/Internet Protocol for more information about TCP/IP network services database support.

IPDB0015EERROR ON LINE NUMBER num IN FILE /etc/services

Where:

num
The line number in the /etc/services file that contains the error.

Explanation: The ZIPDB command was entered with the REFRESH parameter specified, but there was a syntax error in one of the defined applications in the /etc/services file.

System Action: The command is rejected.

User Response: Do the following:

  1. Correct the error in the /etc/services file.
  2. Enter the ZIPDB command again with the REFRESH parameter specified.

See TPF Operations for more information about the ZIPDB command. See TPF Transmission Control Protocol/Internet Protocol for more information about TCP/IP network services database support.

IPDB0016EDUPLICATE APPLICATION NAMES FOUND IN FILE /etc/services ON LINE NUMBER num

Where:

num
The line number in the /etc/services file that contains the error.

Explanation: The ZIPDB command was entered with the REFRESH parameter specified, but a duplicate application name was found on the specified line number in the /etc/services file.

System Action: The command is rejected.

User Response: Do the following:

  1. Remove the duplicate application entry in the /etc/services file.
  2. Enter the ZIPDB command again with the REFRESH parameter specified.

See TPF Operations for more information about the ZIPDB command. See TPF Transmission Control Protocol/Internet Protocol for more information about TCP/IP network services database support.

IPDB0017EDUPLICATE PORT AND PROTOCOL FOUND IN FILE /etc/services ON LINE NUMBER num

Where:

num
The line number in the /etc/services file that contains the error.

Explanation: The ZIPDB command was entered with the REFRESH parameter specified, but a duplicate port and protocol were found on the specified line number in the /etc/services file.

System Action: The command is rejected.

User Response: Do the following:

  1. Remove the duplicate application entry in the /etc/services file.
  2. Enter the ZIPDB command again with the REFRESH parameter specified.

See TPF Operations for more information about the ZIPDB command. See TPF Transmission Control Protocol/Internet Protocol for more information about TCP/IP network services database support.