Filter
Top Products
If you type:
PING SYSNAM02.
then just SYSNAM02 is sent to the remote name server, and the remote name
server resolves the name, similar to when the full host name and domain name are
specified. The only difference between this name and the previous name is the use
of the period at the end of the name.
Common Error Messages
When you use the PING command to verify the connection to another host in the
network, TCP/IP could give you an error message. The following are some of the
most common error conditions:
v No TCP/IP service available
TCP/IP has not been started yet or has not completed starting. All jobs may not
be started in the QSYSWRK subsystem.
Note: Use the NETSTAT command to see if TCP/IP is active. Use the Work with
Active Jobs (WRKACTJOB) command to verify that the QSYSWRK
subsystem and related jobs are active. If they are not active, look in the
job log or system default output queue for any messages.
v Not able to establish connection with remote host system
Check your configured interfaces, their related line descriptions and the TCP/IP
routes.
v Remote host did not respond to VFYTCPCNN within 10 seconds for connection
verification 1.
Your configuration is probably correct, but you do not get an answer back from
the remote system. Ensure that the remote host is able to reach your system.
Call the remote system operator and ask them to verify the connection to your
system.
Check the host tables or remote name server (if you are using a name server)
for both systems, and the TCP/IP interfaces and routes. The remote name server
may not be able to serve you for some reason.
If you are using an Ethernet line, make sure you specified the correct Ethernet
standard or *ALL.
v VFYTCPCNN: Unknown host, xxxxxx where xxxxxx is the host name.
Check the local host table or the remote name servers (if you are using a name
server) for the remote host’s entry.
Working with the Job Log and Message Queues
TCP/IP is shipped with several job descriptions.
The job descriptions are stored in the QSYS or QTCP library. They are shipped with
a message logging level of 4, a message logging severity of 0, and a message
logging text value of *NOLIST. They are shipped with these values to prevent job
logs from being created with only job started and job ended messages in them.
If you are having problems with the operation of TCP/IP, one of the first things to do
is to change the message logging level on the job description for the application
you are having problems with to a message logging text value of *SECLVL.
Changing the message logging level generates a job log for that application. You
438 OS/400 TCP/IP Configuration and Reference V4R4
|
|
|
|
|