Youneed to tie this location to APPC over TCP/IP by adding the remote
location to the remote configuration list. See the

Communications

Configuration

book for details.
If the host table or remote name server do not contain the location name to IP
address mapping, the APPC over TCP/IPjob is not able to resolve the TCP/IP
routing to the remote location. ATCP4F05 message is logged as a
QSYSOPR message. Additionally,the QAPPCTCP job in the QSYSWRK
subsystem logs both a TCP4F04 and TCP4F05 message.
Youneed to tie this location to a particular IP address by adding the remote
location to IP address mapping in the host table or remote name server.
vWhen APPC over TCP/IPis running, the QAPPCTCP job is started in the
QSYSWRK subsystem, and for the most part will be in TIMW status. Also you
can use the Work With Connection Status option of NETSTATto show the APPC
over TCP/IP connections. Before there are any activeAPPC over TCP/IP
connections, you will find an APPCoverTCPIP entry for both a *UDPand Listen
State connection on local port 397. These are both waiting for incoming APPC
over TCP/IP traffic.
If both of these situations are not true, make sure TCP/IP is started and that the
ALWANYNET(Allow AnyNet) network attribute is set to *YES.
Tracing APPC over TCP/IP Problems
When a valid APPC over TCP/IPproblem occurs, you may need to perform a SLIC
trace to capture the problem.
Multiprotocol Transport Network (MPTN) is an option of the Component Trace
option of SLIC Trace (just as TCP/IPis). Choosing MPTN and the option beneath it
called APPC over TCP/IPwill take a SLIC trace of APPC over TCP/IP traffic.
Collecting a Communications Trace
A communications trace can be used to isolate errors. Communications traces can
be run from SST or using the following CL commands:
vCheck Communications Trace (CHKCMNTRC)
vDelete Communications Trace (DLTCMNTRC)
vEnd Communications Trace (ENDCMNTRC)
vPrint Communications Trace (PRTCMNTRC)
vStart Communications Trace (STRCMNTRC)
Youshould be able to use the communications line while the communications trace
is running. Youshould know the name of the line before starting the procedure. In
order to determine the line that you need to trace for TCP/IP problems, look at the
interface you defined and what line description that interface uses.
Note: Contact the security officer or system administrator to get service authority to
use SST.This authority is necessary to use SST.
Planning to Set up a Trace
Before starting to work with a communications trace:
1. If you have not created the library IBMLIB or output queue IBMOUTQ, enter the
following commands:
Chapter21. TCP/IP Problem Analysis 493