p 2 block 260 in block 250 if the source node 11 determines that the plunge response has been received the operation 200 moves to block 265 and the source node 11 reconfigures the path p 2 for normal transactions the operation then returns to block 240 and any pending transactions in the retransmit buffer 13 for which an acknowledgement has not been received are sent to the destination node 12 fig6 is a flow chart of an operation 300 for at the destination node 12 for receiving and responding to a plunge transaction the operation 300 begins in block 305 in block 310 the destination node 12 receives a plunge transaction in block 315 the destination node 12 determines if the path and flow control class from the source node 11 is deconfigured turned off if the path and flow control class is deconfigured the operation 300 moves to block 320 and the destination node 12 sends a plunge response back to the source node 11 along the same path the plunge transaction used in block 320 if the destination node 12 cannot send a plunge response immediately because for example the receive buffer 17 is full the destination node 12 may use the flag bit in the receive_seqid table 18 to indicate when to send the plunge response to the source node 11 the destination node 12 then reconfigures the path p 2 for sending and receiving normal transactions the operation 300 then ends block 330 in block 315 if the path is not deconfigured the operation 300 moves to block 325 and the destination node 12 notes an uncorrectable error notifies the source node 11 and deconfigures the path.