gtpm5m1m | Messages (Online) |
INIP0001I | INDIVIDUAL IP TRACE tracename DEFINED |
Where:
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.
INIP0002I | INDIVIDUAL IP TRACE tracename MODIFIED |
Where:
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.
INIP0003I | INDIVIDUAL IP TRACE tracename DELETED |
Where:
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.
INIP0004I | ALL 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.
INIP0005I | INDIVIDUAL 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.
INIP0006I | INDIVIDUAL IP TRACE tracename DISPLAY |
Where:
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.
INIP0007I | INDIVIDUAL IP FORMATTED TRACE tracename DISPLAY |
Where:
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.
INIP0008I | INDIVIDUAL IP TRACE TABLE tracename IS EMPTY |
Where:
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:
INIP0009I | INDIVIDUAL IP TRACE tracename RESET |
Where:
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.
INIP0010I | INDIVIDUAL 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.
INIP0011I | INDIVIDUAL 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.
INIP0020E | FORMAT 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.
INIP0021E | REJECTED, 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:
See TPF Operations for more information about the ZINIP command.
INIP0022E | REJECTED, 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:
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.
INIP0023E | REJECTED, 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.
INIP0024E | REJECTED, 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.
INIP0025E | REJECTED, 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.
INIP0026E | REJECTED, INDIVIDUAL IP TRACE tracename ALREADY EXISTS |
Where:
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.
INIP0027E | REJECTED, INDIVIDUAL IP TRACE tracename DOES NOT EXIST |
Where:
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.
INIP0028E | REJECTED, 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:
Step 2: Do the following:
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.
INIP0029E | MALOC 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:
See TPF Operations for more information about the
ZINIP command. See TPF
General Macros for more information about MALOC macro usage and
storage.
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.
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:
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.
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:
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.
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:
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.
Where:
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.
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:
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.
Where:
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:
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.
Where:
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:
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.
Where:
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:
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.IPDB0001I NETWORK SERVICES DATABASE REFRESHED
IPDB0010E REJECTED, SYSTEM IS IN RESTART
IPDB0011E REJECTED, TCP/IP NATIVE STACK SUPPORT NOT DEFINED
IPDB0012E REJECTED, FILE /etc/services DOES NOT EXIST
IPDB0013E ERROR OPENING FILE /etc/services, ERRNO description
IPDB0014E TOO MANY APPLICATIONS DEFINED IN FILE /etc/services
IPDB0015E ERROR ON LINE NUMBER num IN FILE /etc/services
IPDB0016E DUPLICATE APPLICATION NAMES FOUND IN FILE /etc/services ON LINE NUMBER
num
IPDB0017E DUPLICATE PORT AND PROTOCOL FOUND IN FILE /etc/services ON LINE NUMBER
num