Ansicht
Dokumentation

CPF694F - Communications failed with reason code &10. ( OS/400 )

CPF694F - Communications failed with reason code &10. ( OS/400 )

Vendor Master (General Section)   Vendor Master (General Section)  
This documentation is copyright by IBM.
SAP E-Book


Message : CPF694F
Communications failed with reason code &10.

Message Long Text :

Cause . . . . . : The remote journal request failed. The journal is &3 in library &4 on system &6 in Auxiliary Storage Pool (ASP) group &9. The remote journal is &1 in library &2 on system &7 in ASP group &8.
The reason code is &10.
1 - Time out waiting for a response from the target system
2 - The source system detected a takedown of the remote journal environment from the target system
3 - The source system could not detect the target system
4 - Communication line error or target system error
5 - Communication validity checking failed
6 - Data port services error
7 - Node identifier &12 is unavailable for data port services
8 - Connections down for data port services
9 - Internet address unavailable locally for data port services
10 - Destination internet address unreachable for data port services
11 - Hardware error for data port services
12 - Insufficient memory to perform data port services request
13 - Client closed for data port services
Recovery . . . : If a firewall exists, verify that port 3777 and any additional ports used by the relational database are allowed access through the firewall to allow for remote journal communications.
For reason code:
1 - Use the CHGRMTJRN command to increase the synchronous sending time out or to change the delivery to asynchronous replication. Then try the request again.
2 and 3 - Verify that the target system is up and the communications line is active. Then try the request again.
4 - Refer to the previous message in the job log and perform the appropriate recovery. If no previous messages exist, verify that the target system is up and the communications line is active. Then try the request again.
5 - Examine the communication hardware and verify that the line can reliably transfer data. Replace any failing communication hardware. Then try the request again.
6, 7, 11, and 13 - Verify that a cluster environment is configured and that the node identifier for the source system is active. Verify that the specified node identifier &12 exists, is active, and resides on the target system. When using data port services, node identifier &12 must not reside on the source system. Also use the NETSTAT command on the target system to verify that the specified data port IP addresses exist and are active. Then try the request again.
8, 9, and 10 - Use the NETSTAT command to verify that TCP/IP is up and running on both systems. Verify the data port internet addresses are established from the source system to the target system. Then try the request again.
12 - Free available memory. Then try the request again.
Technical description . . . . . . . . : The transport mechanism is &11. The relational database name is &5. The data port node identifier is &12.

Message File : QCPFMSG
Library Message File : QSYS2924


BAL Application Log Documentation   ABAP Short Reference  
This documentation is copyright by IBM.

Length: 3271 Date: 20240329 Time: 063830     sap01-206 ( 3 ms )