Ansicht
Dokumentation

CPFBB78 - API request &1 cannot be processed in cluster &2. ( OS/400 )

CL_GUI_FRONTEND_SERVICES - Frontend Services   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by IBM.


Message : CPFBB78
API request &1 cannot be processed in cluster &2.

Message Long Text :

Cause . . . . . : The API request &1 cannot be processed in cluster &2. The reason code is &3. Possible reason codes are:
1 -- All nodes in the device domain must be active to complete this request.
2 -- The node &4 must be IPLed before this request can be completed because of an internal data mismatch.
3 -- Could not communicate with at least one device domain node.
4 -- Internal system resource not available.
5 -- Node &4 has an auxiliary storage pool not associated with a cluster.
6 -- Node &4 cannot be added to a device domain with existing auxiliary storage pools.
7 -- Auxiliary storage pools are missing.
8 -- Disk unit configuration changes are occurring.
9 -- Node &4 has an auxiliary storage pool number greater than 99 which is not compatible with current cluster version.
10 -- Node &4 owns a cross site mirrored copy of an auxiliary storage pool which is varied on.
11 -- Hardware associated with auxiliary storage pool has failed.
12 -- Node &4 has an internal mismatch in the device domain.
Recovery . . . : Recovery actions for the reason codes are:
1 -- Try the request again when all nodes in the device domain are active.
2 -- IPL the node and try the request again.
3 -- Try the request again.
4 -- Try the request again after increasing the size of the machine pool. If the problem recurs, call your service organization and report the problem.
5 -- If a node has an existing auxiliary storage pool, that node must be the first node added to the device domain. Delete any auxiliary storage pools from other nodes being added to the device domain and try the request again.
6 -- Remove the auxiliary storage pools from the device domain nodes or re-install and initialize the node being added.
7 -- Identify and fix the missing auxiliary storage pools on each system.
8 -- Wait until disk unit configuration changes are complete and try the request again.
9 -- Upgrade the current cluster version to a higher level using the QcstAdjustClusterVersion API or delete all auxiliary storage pools which have number greater than 99 on node &4. Then try the request again.
10 -- Vary off the auxiliary storage pool.
11 -- Use the product activity log to find entries for the failed hardware. Fix the failing hardware.
12 -- Remove node &4 from device domain even though it is no longer in the device domain, IPL the node, then try the request again.

Message File : QCPFMSG
Library Message File : QSYS2924


General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by IBM.

Length: 3279 Date: 20240420 Time: 010905     sap01-206 ( 3 ms )