II10791: DSNL015I: VTAM SETLOGON FAILED RTNCD=X'10' FDBK2=X'19' DURING START DDF PROCESSING

APAR status

• Closed as canceled.

Error description

• DSNL015I VTAM SETLOGON FAILED RTNCD=x'10' FDBK2=x'19'
  received at DDF START processing.  The combination
  RTNCD and FDBK2 codes indicate the host is not a member
  of the sysplex.
  
          ACF/VTAM V4.4 Programming Manual :  SC31837300
  ________________________________________________________________
  | RTNCD     | FDB2      | Explanation
  |___________|___________|_______________________________________
  | 16(X'10') | 25(X'19') | Host (VTAM) is not member of Sysplex
  |___________|___________|_______________________________________
  The application issued one of the following macroinstructions:
   INQUIRE  OPTCD=SESSNAME
   CHANGE   OPTCD=ENDAFFIN
   SETLOGON OPTCD=GNAMEADD|GNAMEDEL|GNAMESUB
  This error message implies that the SYSPLEX Coupling Facility
  for the associated VTAM HOST is inaccessible.  The Coupling
  Facility maybe inaccessible for one of the following reasons:
  
   (1) A coupling facility does not physically exist.
   (2) A CFRM policy for the required Coupling Facility Structure
       was NOT active.
   (3) VTAM is not defined as an APPN node.
   (4) VTAM has lost connectivity to the required SYSPLEX
       Coupling Facility Structure.
  ----------------------------------------------------------------
     If your operating systems are NOT configured in a SYSPLEX,
  then you CANNOT run DB2 R410 or R510 DataSharing.  But note,
  several MVS/ESA | OS390 components are set to DEFAULT to
  SYSPLEX operation, ie: IEFSSNxx.  If your system is NOT
  physically configured inside of a SYSPLEX, and if you are
  setting up DB2 R410 or R510 DDF, and you receive this
  particular msgDSNL015I noting this particular RETURN/FEEDBACK
  code, then you can use the following procedure to get around
  this particular error message:
  
  In the IEFSSNxx parmlib member, check to make sure group-attach
  entry is deleted and SCOPE should have 'M' (single system)
  instead of 'X' (sysplex scope).  Both group-attach entry and
  'X' are specific to a SYSPLEX DataSharing environment.
     Another parameter to check is the generic luname given
  to one of the members.  This needs to be deleted.  Use DSNJU003
  Change Log Inventory to remove the GENERICLU=gluname from the
  BSDS.  See II10645 for CLI syntax.
  For deleting GENERICLU from BSDS, use DSNJU003
  utility with option NGENERIC .
  
     More information regarding the setup of DDF in an actual
  SYSPLEX DataSharing environment can be found in PQ04666.
  All DDF DataSharing users should install PQ04666 in put9709.
  
  
  
  
  
  
  
  
  
  Note: Disregard any 'LOCAL FIX' information noted in this apar.
  

Local fix

• In the IEFSSNxx parmlib member, check to make sure group-attach
  entry is deleted and SCOPE should have 'M' (single system)
  instead of 'X' (sysplex scope).  Both group-attach entry and
  'X' are specific to a data-sharing environment.
  Another parameter to check is the genericlu name given to one
  of the member.  This needs to be deleted.  Use DSNJU003 utility
  to remove the genericlu name.
  

Problem summary

Problem conclusion

Temporary fix

Comments

• closed for DB2INFO retention
  

APAR Information

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

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

Fix information

Applicable component levels