Ansicht
Dokumentation

CPFBB12 - Cluster node &1 in cluster &2 could not be started. ( OS/400 )

Vendor Master (General Section)   ROGBILLS - Synchronize billing plans  
This documentation is copyright by IBM.


Message : CPFBB12
Cluster node &1 in cluster &2 could not be started.

Message Long Text :

Cause . . . . . : Cluster node &1 in cluster &2 could not be started because there is no active cluster interface associated with the cluster node, or the line description associated with the TCP/IP interface is not supported for a cluster interface.
Recovery . . . : You can use the Start TCP/IP Interface (STRTCPIFC) command to start the TCP/IP interface or correct the cluster interface address associated with node &1 and try the request again.
Technical description . . . . . . . . : The cluster interface address associated with the specified node ID is defined on the system as one of the following types which cannot be used for cluster communications:
- *LOOPBACK
- *VIRTUALIP

Message File : QCPFMSG
Library Message File : QSYS2924


BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by IBM.

Length: 3239 Date: 20240419 Time: 141156     sap01-206 ( 2 ms )