Filter
Top Products
1. Look in the job log of the user that issued the STRTCPPTP command for errors.
Errors found during point-to-point configuration profile validation will be logged in
this job log. Press F1 on the error message issued and follow the recovery
section.
2. Look in the SLIP session job log. Use the Work with Point-to-Point TCP/IP
(WRKTCPPTP) command to display a list of profiles. Find the point-to-point
profile, and select option 14. When you select option 14, the Work with Job
(WRKJOB) display is shown. If the job is still active, you can select option 10 to
display the current job log. If the job is no longer active, select option 4 to work
with spooled files for this job. Display the QPJOBLOG spooled file and look for
any error messages that have occurred. Refer to “Working With Point-to-Point
Jobs” on page 136 for more information on working with point-to-point jobs and
session job logs.
3. When the STRTCPPTP command is issued, the default for the OUTPUT
parameter is *ERROR. When OUTPUT is set to *ERROR, a script dialog is
printed if any errors occur during the modem initialization, call establishment,
modem synchronization or connection script dialog phases. This spooled file
contains information about any errors that have occurred during this process.
To see if a spooled file was created, use option 14 of the WRKTCPPTP
command for the point-to-point profile that failed to complete.
Select option 4 on the Work with Job display to show the Work with Job
Spooled Files display. On this display look for the spooled file with the USER
DATA field set to STRTCPPTP. Display the spooled file and look for any errors.
Examples of typical errors include:
v Rejected modem commands (examples are shown in Figure 250).
v Connection rejected by remote system due to incorrect userid or password
sent (examples are shown in Figure 251 on page 441).
v Mismatches in connection scripts with missing data or out of sequence data
(shown in Figure 252 on page 441). In Figure 252, the remote system
prompted for the password but the connection script on the local system was
not set up properly to look for this prompt. Therefore the remote system
timed out and closed the connection.
Refer to “Working With Point-to-Point Jobs” on page 136 for more information
on working with the connection script dialog spooled file.
1 Wed May 1 11:46:30 1996 ==> Attempting modem reset.
2 Wed May 1 11:46:30 1996 ==> AT&FS0=0
3 Wed May 1 11:46:30 1996 ==> Reading modem response.
4 Wed May 1 11:46:33 1996 ==> Reading modem response.
5 Wed May 1 11:46:33 1996 ==> AT&FS0=0 OK
6 Wed May 1 11:46:37 1996 ==> Attempting modem initialization.
7 Wed May 1 11:46:37 1996 ==> AT&D2&C1X4V1Q0S7=70W2\N3&K3&S1
8 Wed May 1 11:46:37 1996 ==> Reading modem response.
9 Wed May 1 11:46:40 1996 ==> Reading modem response.
10 Wed May 1 11:46:40 1996 ==> AT&D2&C1X4V1Q0S7=70W2\N3&K3&S1 ERROR
Figure 250. Rejected modem commands — Examples
440 OS/400 TCP/IP Configuration and Reference V4R4