z/VM: System Messages and Codes Š CP - z/VM - IBM
z/VM: System Messages and Codes Š CP - z/VM - IBM
z/VM: System Messages and Codes Š CP - z/VM - IBM
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
H<strong>CP</strong>2702I H<strong>CP</strong>2708I<br />
v The other system went down.<br />
v The domain controller at the other system went<br />
down.<br />
<strong>System</strong> Action: The link is no longer available for<br />
communications.<br />
Operator Response: Issue the ACTIVATE ISLINK<br />
comm<strong>and</strong> for the link. If the link is still down, this may<br />
indicate a hardware failure.<br />
H<strong>CP</strong>2702I Link rdev came up.<br />
Explanation: The link group got a response from the<br />
other end of this link.<br />
<strong>System</strong> Action: The system will use the new link.<br />
Operator Response: None.<br />
H<strong>CP</strong>2703I Node nodeid deleted from collection.<br />
Explanation: The node nodeid has been deleted from<br />
the collection table of each node in the CS collection. If<br />
this happens after a detected partition, the collection<br />
management structures of nodeid no longer agree with<br />
the rest of the collection or are not available because<br />
nodeid stopped communicating. If nodeid is still<br />
communicating, no sessions are broken. As long as all<br />
components are still working correctly, the system<br />
corrects the problem.<br />
<strong>System</strong> Action: Node nodeid is removed from the<br />
collection table. The system attempts to rejoin the node<br />
using h<strong>and</strong>shake messages.<br />
Operator Response: None.<br />
H<strong>CP</strong>2704I Node nodeid added to collection.<br />
Explanation: The node nodeid has been added to the<br />
collection table of each node in the CS collection. This<br />
means that the remote domain controller is now defined<br />
to the local z/<strong>VM</strong> domain controller.<br />
<strong>System</strong> Action: Node nodeid is added to the CS<br />
collection. The local <strong>and</strong> remote domain controllers<br />
exchange gateway names, resource names, <strong>and</strong> pacing<br />
count information. The domain controllers can now<br />
communicate over the data link.<br />
Operator Response: None.<br />
H<strong>CP</strong>2705I Monitor response not received on link<br />
rdev. Link status: {Busy |Fatal I/O on<br />
link|H<strong>and</strong>ling link<br />
attention|Idle|Initialization in<br />
progress|Read in progress|Reset in<br />
progress|Write in progress}.<br />
Explanation: A frame sequence error was detected.<br />
<strong>System</strong> Action: None. Processing continues.<br />
Operator Response: Record the error message <strong>and</strong><br />
296 z/<strong>VM</strong>: <strong>System</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong> — <strong>CP</strong><br />
notify your system programmer.<br />
<strong>System</strong> Programmer Response: If the problem<br />
persists, contact your <strong>IBM</strong> Support Center Personnel.<br />
H<strong>CP</strong>2706I {Link rdev | Link (rdev,rdev) |<br />
Conversation convid} { activated |<br />
deactivated } by user userid.<br />
Explanation: This is a response to the ACTIVATE<br />
ISLINK, DEACTIVE ISLINK, or DEACTIVE CONV (for<br />
conversation) comm<strong>and</strong> <strong>and</strong> indicates the user initiating<br />
the comm<strong>and</strong>.<br />
Operator Response: None.<br />
<strong>System</strong> Programmer Response: None.<br />
H<strong>CP</strong>2707I Link rdev suspended to verify duplicate<br />
node nodeid.<br />
Explanation: This message is displayed on the<br />
system console when an ISFC link (rdev) receives a<br />
message identifying a remote node with the same name<br />
(nodeid) as another node in this collection. This could<br />
mean either of the following:<br />
v The new identification could have been sent by a<br />
system that was shutdown, <strong>and</strong> a re-IPL occurred so<br />
quickly that the old instances of that node have not<br />
yet been flushed from the collection. If that is the<br />
case, the “old” node will not respond. The link will be<br />
automatically reset every 30 seconds so it will come<br />
up when the obsolete references to this node have<br />
been deleted.<br />
v The new node could have the same name as another<br />
node in this collection. If that is the case, the “old”<br />
node will respond <strong>and</strong> the system will deactivate this<br />
link (issuing message H<strong>CP</strong>2708I). This represents a<br />
true duplicate node in the collection.<br />
<strong>System</strong> Action: Any subsequent resource messages<br />
from this link (rdev) are ignored. If the established node<br />
(nodeid) in this collection responds, the system issues<br />
message H<strong>CP</strong>2708I <strong>and</strong> deactivates this link.<br />
Otherwise, this link is reset with every link monitor test<br />
cycle, <strong>and</strong> should initialize completely when the<br />
obsolete references to the node have been removed<br />
from this collection.<br />
Operator Response: Wait for the system to determine<br />
if a duplicate node really exists. Within five minutes or<br />
so, you should see either the link start normally, or the<br />
link deactivated with message H<strong>CP</strong>2708I.<br />
H<strong>CP</strong>2708I Link rdev deactivated because of<br />
duplicate node nodeid.<br />
Explanation: This message is displayed on the<br />
system console soon after message H<strong>CP</strong>2707I if the<br />
established node in the collection with this name<br />
(nodeid) is still active. This is because a node on the<br />
“other” side of this link (rdev) has the same name<br />
(nodeid) as a node that already exists in the collection.