OW28374: IST680I CONNECTION REQUEST DENIED - ID = ***NA*** PU GEN NOT SUPPORTED, DOES NOT GIVE ENOUGH INFO TO DEBUG PROBLEM

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In a DLUR environment, XIDs are encapsulated in an REQACTPU
  PIU that does not have a GROUP or LINEs element address
  associated with it but VTAM still treats the DLUR served PU as
  if it were a real switched PU. When the XID is received by VTAM
  and no match can be found using the IDBLK/IDNUM that the XID
  contains, VTAM will also look to see if the CS EXIT is
  available and if so, pass the XID to the EXIT. However, if no
  match can be found and no EXIT exist then the request is failed
  and IST680I is issued but the message does not give any data
  from the XID which makes it impossible for anyone to know which
  PU in the network is sending in this data. The only way to see
  it is by runing traces.
   More messages need to be issued giving as much information as
  possibly can be obtained from the XID so that a correct VTAM
  definition can be installed to stop the flood of IST680I
  messages.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All using DLUR/DLUS.                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: An attempt is made to connect in        *
  *                      (REQACTPU) by a DLUR served device, but *
  *                      the switched major node containing the  *
  *                      PU definition is not active.  VTAM      *
  *                      issues MSG680I CONNECTION REQUEST       *
  *                      DENIED - ID = ***NA*** PU GEN NOT       *
  *                      SUPPORTED, but no other messages are    *
  *                      issued.  This makes it difficult to     *
  *                      know what device failed to connect.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In non-DLUR scenarious when IST680I is issued it is part of a
  message group whick gives additional information (CPNAME,
  STATION ID, etc.)  For DLUR served resources which fail with
  IST680I the same kind of information needs to be provided so
  that the problem can be diagnosed without taking traces.
  

Problem conclusion

• VTAM now issues IST1354I, IST1394, and IST314I in addition to
  IST680I when a DLUR device fails to connect.
  
  The following publication changes accompany this fix:
  
  VTAM V4R4 Messages (GC31-8368-00)
  VTAM V4R3 Messages and Codes (SC31-6546-00)
  VTAM V4R2 Messages and Codes (SC31-6493-01)
  
  IST680I CONNECTION REQUEST DENIED - ID = nodename text
  ------------------------------------------------------
  Explanation, add a new message group between the two samples
  given:
  
   o 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
  
  Explanation, IST680I, text INVALID NETWORK ID needs to be
  changed to NETID MISMATCH and moved below MAXLU INADEQUATE.  It
  should now say:
  
   NETID found in REQCONT/REQACTPU RU does not match the NETID of
   the host.
  
  Explanation, IST680I, text INVALID NETWORK NAME needs to be
  changed to say:
  
   This error can occur for one of the following reasons:
  
   o 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.
  
   o nodename is attempting to establish a connection with itself.
     This can occur in response to an operator takeover request.
  
  Explanation, IST680I, text PUTYPE MISMATCH needs to be added:
  
   PUTYPE found in REQCONT/REQACTPU RU does not match the PUTYPE
   in the switched PU definition.
  
  Explanation, IST1354I, needs to be added (just before
  IST1394I):
  
   dlurname is the network-qualified CP name (in the form
   netid.name) of the dependent LU requestor (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.
  
  Operator response for IST680I, INVALID NETWORK ID needs to be
  changed to NETID MISMATCH and moved below MAXLU INADEQUATE.
  
  Operator response for IST680I, PUTYPE MISMATCH needs to be
  added:
  
   Save the system log for problem determination.
  
  Programmer response for IST680I, INVALID NETWORK ID needs to be
  changed to NETID MISMATCH and moved below MAXLU INADEQUATE.  It
  should now say:
  
   NETID should be the same as the host (see XNETALS in VTAM
   Resource Definition Reference).  If it is not, then the NETID
   in the REQCONT/REQACTPU RU is incorrect.  If cpname is not
   network-qualified, then NETID will default to the host NETID.
  
   See the product documentation for the device for information
   on coding cpname and NETID if they are not correct in the
   REQCONT/REQACTPU RU.
  
  Programmer response for IST680I, INVALID NETWORK NAME needs to
  be changed to say:
  
   o If nodename is not a valid name, check for a CPNAME mismatch
     between the switched major node/model 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.
  
   o 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 "SSCP
     Takeover" in the VTAM Network Implementation Guide for more
     information.
  
   o If this error is due to a name conflict, correct the
     duplicate names.
  
  Programmer response for IST680I, PUTYPE MISMATCH needs to be
  added:
  
   PUTYPE as indicated in the XID received on the REQCONT/
   REQACTPU RU should match PUTYPE as defined on the switched PU
   (see PUTYPE in VTAM Resource Definition Reference).
  
   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.
  
  IST1354I DLUR NAME = dlurname      MAJNODE = majnode
  ----------------------------------------------------
  Change majornodename to majnode as shown above.  Also, change
  the explanation to say:
  
   This message is part of several message groups that VTAM
   issues in response to a DISPLAY ID=dlur_pu command, or when
   a connection request for a DLUR served physical unit is
   rejected.  For DLUR served physical unit connection request
   rejection the first message in the group is IST680I - see
   the explanation of that message for a complete description.
   The following description applies for DISPLAY ID=dlur_pu.
  
   dlurname is the network-qualified CP name of the dependent LU
   requestor (DLUR) in the form netid.name.  dlurname is the DLUR
   associated with the physical unit specified on the ID operand
   of the command.
  
   majnode is the name of the switched major node of the physical
   unit specified on the ID operand of the command.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  VM61980 DY45025

Modules/Macros

• ISTACCDB ISTACCRQ ISTCFCML ISTCFCMM ISTINCNO
  ISTMSCGC ISTVTMEU IST650C
  

Fix information

• Fixed component name

  VTAM V4 MVS/ESA

• Fixed component ID

  569511701

Applicable component levels

• R201 PSY UW41349

     UP97/09/19 P F709

• R301 PSY UW41350

     UP97/09/19 P F709

• R401 PSY UW41351

     UP97/09/19 P F709

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.