IST680I

Explanation
 VTAM® issues
this message when a connection request for resource nodename has
been rejected. This message is issued as both a single line message
and as part of message groups.  If nodename is a local SNA physical unit, the
following message group is displayed.   IST680I     CONNECTION REQUEST DENIED - ID = nodename text
[IST1394I   CPNAME = cpname  STATION ID = stationid]
[IST352I    LOCAL SNA MAJOR NODE = majornode ]
 IST314I     END

If nodename is a DLUR served physical unit,
the following message group is displayed. IST680I    CONNECTION REQUEST DENIED - ID = nodename text
IST1354I   DLUR NAME = dlurname  MAJNODE = majnode
IST1394I   CPNAME = cpname  STATION ID = stationid
IST314I    END

For all other types of nodes, the following message group is displayed.
  IST680I     CONNECTION REQUEST DENIED - ID = nodename text
[IST1394I   CPNAME = cpname  STATION ID = stationid]
[IST081I    LINE NAME = linename, LINE GROUP = groupname, MAJNOD = nodename ]
[IST1544I   DIAL OUT PURGE IN PROGRESS - ID = nodename]
 IST314I     END

 IST081I  linename is the line to which nodename is
connected.
groupname is the line group to which the line linename belongs.
nodename is the major node with which the
line is associated.

 IST352I  majornode is the local SNA major node (local
cluster controller).

 IST680I  text can be one of the following:  CALL SECURITY ERROR
A dial in or dial out request was rejected because the required
information for call security verification was missing or not valid.
DIAL OUT IN PROGRESS
The dial out for the switched physical unit nodename is
already in progress over another line. For a manual dial, see IST679A.
For an auto dial, the dial in will fail.
INVALID NETWORK NAME
This error can occur for one of the following reasons:  nodename is not a valid name. Either the CPNAME
passed in the REQCONT/REQACTPU RU could not be found (matched to a
switched PU definition), or the network ID or CPNAME passed in the
REQCONT/REQACTPU RU is not valid. This is the most frequent reason
for the error.
nodename is attempting to establish a connection
with itself.  This can occur in response to an operator takeover request.

LINK NOT IN EAM
A dial in request was not honored for the switched physical unit nodename because
the link was not in enable answer mode (EAM).
MAXLU INADEQUATE
The dial in request was not honored because the link cannot support
the number of logical units required by the switched physical unit nodename that
dialed in. 
NETID MISMATCH
NETID found in REQCONT/REQACTPU RU does not match the NETID of
the host. 
NO USABLE PATH FOUND
Call ID verification was indicated on a PATH definition statement
for nodename and a usable PATH definition could
not be found. 
PU ALREADY ACTIVE
A REQACTPU is received for a DLUR PU that is already active.
PU GEN NOT SUPPORTED
This error can occur for one of the following reasons:  The host could not identify the switched PU for one of the following
reasons:  The PU is not defined in a switched major node.
The switched major node in which the PU is defined is not active.
The PU is not able to be dynamically defined for the following
reasons:  Non-genned terminal support is not available because ASDP=YES
is not specified on the PU definition statement in the switched major
node.
DYNPU=YES is not specified on the GROUP definition statement in
a major node such as NCP or XCA.

The network-qualified name of the node that the PU represents,
as specified in the XID3 received from the adjacent node, does not
match the name defined in the switched major node on the NETID and
CPNAME operands on the PU definition statement.
The idblk and idnum,
as specified in the XID3 received from the adjacent node, do not match
the idblk and idnum defined
in the switched major node on the IDBLK and IDNUM operands on the
PU definition statement.

PU STATE CHANGED
The PU state of a predefined PU changed while the c services (CS)
exit was in control. When a REQCONT for a predefined PU is sent to
the CS exit, the state of the PU is set to Pending REQCONT. If an
INOP is received on that PU or its LINE before returning from the
CS exit, the state of the PU changes. This indicates that the connection
setup cannot continue.
PUTYPE MISMATCH
PUTYPE found in REQCONT/REQACTPU RU does not match the PUTYPE
   in the switched PU definition.
REQCONT RU NOT VALID
The station ID (nodename) passed in the REQCONT
RU could not be found (that is, matched to a switched PU definition).
This indicates a hardware or software problem in the switched physical
unit nodename attempting the connection. 
T2.1 NOT SUPPORTED
A connection request for a PU type 2.1 node, nodename,
with independent LUs was received from an NCP that does not provide
the required level of support.
TG NUMBER NOT USABLE
An EE model PU with predefined TG numbers was used, but the specified
TGNs could not be used.  The REQCONT RU fails with sense 08070000
or 10160016.

 IST1354I  dlurname is the network-qualified CP name
(in the form netid.name) of the dependent LU requester (DLUR) associated
with the DLUR served physical unit nodename in
message IST680I.
majnode is the name of the switched major
node for the DLUR served physical unit nodename in
message IST680I.

 IST1394I  cpname is the network-qualified name of the
control point (CP) that was passed in the XID from the node attempting
the connection. VTAM displays cpname in
the form netid.name. ***NA*** is displayed
if no CP name is provided.
stationid is the 4-byte station identifier
in the following format: Byte 1 = PUtype, Byte 2 = reserved, Byte
3 and 4 = IDBLK/IDNUM . For more information on station identifier
formats, see the descriptions of the IDBLK and IDNUM operands in the z/OS Communications Server: SNA Resource Definition
Reference.

 IST1544I  nodename is the physical unit (PU) that dialed
out on the associated line. A dial in and a dial out over the same
line were attempted at the same time and both requests were rejected.
 There
are two possible causes for the problem:  A physical unit (PU) performed a dial out, but the request contact
information (cpname or stationid)
received in contact RU (REQCONT) matches a different PU that is defined
in VTAM.
Two different PUs, one performing dial out and the other performing
dial in over the same line, cause a race condition.

 In both cases, the PU that attempted to dial out is displayed.

System action
 Processing continues. If the physical unit is
offline, the session establishment remains pending. Otherwise, the
connection request and any associated session establishment attempts
fail.
 For message IST1544I, the dial in is rejected and the
dial out is purged. 

Operator response
 For IST1544I: Save the system log
for problem determination.
 For IST680I  CALL SECURITY ERROR
Save the system log for problem determination. 
DIAL OUT IN PROGRESS
Attempt to dial in on another line.
INVALID NETWORK NAME
Save the system log for problem determination.
LINK NOT IN EAM
If dial in requests are to be honored on link link,
enable answer mode by using the VARY ANS=ON,ID=link command. 
MAXLU INADEQUATE
Save the system log for problem determination.
NETID MISMATCH
Save the system log for problem determination.
NO USABLE PATH FOUND
If dial in or dial out requests are to be honored for the node,
enable the PATH definitions for nodename by using
the VARY PATH=USE,ID=nodename, PID=pathid command. 
PU GEN NOT SUPPORTED
Try activating the switched major node containing the PU nodename.
If problems persist, save the system log for problem determination.
PUTYPE MISMATCH
Save the system log for problem determination.
REQCONT RU NOT VALID
Save the system log for problem determination. 
T2.1 NOT SUPPORTED
Save the system log for problem determination.

System programmer response
 For IST1544I , ensure that the correct
CP name or station ID (IDBLK/IDNUM) is specified on the switched PU
definition statement for the PU performing the dial out.
 For
IST680I  CALL SECURITY ERROR
Verify that all nodes involved in the dial process are of a level
that supports call security verification. See the PRTCT operand on
the PU definition statement in the switched major node definition.
DIAL OUT IN PROGRESS
None. 
INVALID NETWORK NAME
 If nodename is not a valid name, check for
a CPNAME mismatch between the switched major nodeor mocel major node
and the NCP major node definitions. Verify that the network ID passed
in the REQCONT/REQACTPU RU matches the network ID specified in the
PU definition statement. Line information or I/O trace information
or both might be necessary to determine the cause of the problem. 
If this error is due to an operator takeover request, APPN or
LEN connectivity is not available until the failing host regains control
or another host takes control. See the z/OS Communications Server: SNA Network Implementation
Guide for more information. 
If this error is due to a name conflict, correct the duplicate
names.

LINK NOT IN EAM
Put the link in enable answer mode (EAM). 
MAXLU INADEQUATE
Check for a MAXLU mismatch in the switched major node and NCP
major node definitions. Either update the switched major node to match
the NCP major node or instruct the remote user of the PU not to dial
in over that link.
NETID MISMATCH
NETID should be the same as the host.  If it is not, then the
NETIDin the REQCONT/REQACTPU RU is incorrect.  If cpname is
not network-qualified, then NETID will default to the host NETID.
 See the z/OS Communications Server: SNA Resource Definition
Reference for information about XNETALS. See the
product documentation for the device for information on coding cpname
and NETID if they are not correct in the REQCONT/REQACTPU RU.

NO USABLE PATH FOUND
Check the PATH definition statements in the switched major node
containing nodename. 
PU GEN NOT SUPPORTED
Check the definition statements for the switched PU and revise
as needed. Deactivate and reactivate the switched major node to use
the revised definitions.
PUTYPE MISMATCH
PUTYPE as indicated in the XID received on the REQCONT/REQACTPU
RU should match PUTYPE as defined on the switched PU.   See z/OS Communications Server: SNA Resource Definition
Reference for information about PUTYPE. See the
product documentation for the device for information on PUTYPE if
it is not indicated correctly in the XID received on REQCONT/REQACTPU
RU.

REQCONT RU NOT VALID
Check for an IDBLK or IDNUM mismatch between the device and the
switched major node.
T2.1 NOT SUPPORTED
Check the PATH and LU definition statements in the switched major
node containing nodename.

Routing code
 8

Descriptor code
 4 