II12369: OS/390 IBM COMMUNICATION SERVER V2R10: SC31-8674-05 IP MESSAGES VOLUME 3 TCPIPINFO BOOKAPAR

APAR status

• INTRAN

Error description

• OS/390 IBM COMMUNICATION SERVER V2R10: IP MESSAGES VOLUME
  3 (SC31-8674-05) TCPIPINFO BOOKAPAR
  Z/OS COMMUNICATION SERVER V1R1: SC31-8785-00
  

Local fix

• ************************************************************
  Message EZZ4312, changed book reference in system programmer
  response as follows:
    Refer to the documentation for your LCS device for more
    information about the start lan return code.
  ************************************************************
  ***********************************************************
  This information apar is available in the OS/390 DOC APARs
  and ++HOLD DOC data document, which can be found at:
  http://www.s390.ibm.com/os390/bkserv/new_tech_info.html
  ***********************************************************
  EZY1258I  module ENTRY POINT IS address
  EXPLANATION:  This message displays the entry point address
    of a module.
    module is the name of the module.
    address is the entry point address of the module.
  SYSTEM ACTION:  Processing continues.
  USER OR OPERATOR RESPONSE:  None.
  SYSTEM PROGRAMMER RESPONSE:  None.
  SOURCE DATA SET:  EZACIC01, EZACIC02
  ***********************************************************
  Message EZZ4312, changed book reference in system programmer
  response as follows:
    Refer to the documentation for your LCS device for more
    information about the start lan return code.
  ***********************************************************
  Message EZZ4312I - added another possible cause of error and
    changed into bulleted lists as follows:
  EXPLANATION: The LAN adapter was not successfully started.
    Possible reasons are:
    * There is an error on the LINK statement in the TCPIP
      profile.
    * The LAN adapter is not connected to a live LAN.
  SYSTEM PROGRAMMER RESPONSE:
    * Verify that the link_number on the LINK statement matches
      the slot position within the LCS device. If necessary,
      correct the link_number parameter on the LINK statement,
      and restart the LCS device.
    * Verify that the LAN adapter is connected to a live LAN.
  ***********************************************************
  In message EZZ7056E, the variable 'reason' was renamed to
    'errno' and the following was added to the explanation:
  
    One possible cause of this error is that the TCP/IP stack
    must be started before TIMED.
  
    errno is the Return Code. Return Codes are listed and
    described in the OS/390 UNIX System Services Messages
    and Codes.
  ************************************************************
  ***********************************************************
  Message EZZ7908I - Added a definition for type.
     <type> is the OSPF packet type as described in RFC 1583.
  ***********************************************************
  ************************************************************
  In message EZZ6034I, in the definition of the luname variable
  add the following 2 sentences.
  ***********
  To avoid flooding your console, luname will be MULTIPLE if
  action is CONN DROP and more than one connection was dropped
  for the same reason within a 15 second interval.  If you want
  to see a message for each connection being dropped, specify
  the DEBUG SUMMARY statement.  Refer to the OS/390
  Communications Server: IP Configuration Guide for more
  information about Telnet Diagnostics.
  ************************************************************
  ************************************************************
  In message EZZ6238I -
  added the following Paragraph to Explanation:
     The SNMP agent is attempting to establish an AF_UNIX
     socket for use in communicating with subagents.  The
     AF_UNIX socket is represented by a file name, which
     defaults to /tmp/dpi_socket.  The file name may be
     specified either on the -s parameter at SNMP agent
     initialization or by setting the DPIPATHNAMEFORUNIXSTREAM
     value in the OSNMPD.DATA file.
  
  New User or Operator Response:
     Restart the SNMP agent with tracing by specifying -d 255
     at agent invocation.  Use the errnojr shown in the traces
     for additional help in diagnosing the problem.
  ************************************************************
  ************************************************************
  Added the following sentences to explanation of EZZ3205I
       The subagent is automatically started at TCP/IP
       initialization unless SACONFIG DISABLED is specified in
       the TCP/IP Profile data set.  So when the TCP/IP address
       space is stopped, the subagent issues this message and
       then ends.
  ************************************************************
  ************************************************************
  In message EZZ6476I, changed explanation and system action:
    EXPLANATION: The number of possible sockets (file
      descriptors) supported the system (as defined by
      MAXFILEPROC in BPXPRMxx) exceeds the maximum allowed by
      the name server.
    SYSTEM ACTION: The domain name server continues normal
      processing. The maximum number of sockets supported by
      the name server is adjusted to the hard coded maximum
      of 2048.
  ************************************************************
  EZZ6037I is new
  ***************
  EZZ6037I PROFILE ERROR ON PORT port - source errparm
           INCONSISTENT WITH PORT TYPE OR CONNECTION TYPE.
  EXPLANATION: A parameter specified in TELNETPARMS or a
      PARMSGROUP conflicts with the port or connection type.
  
      port is the port number with the inconsistent parameter.
  
      source is the TELNETPARMS or the name of the ParmsGroup
      that contains the error.
  
      errparm is the parameter in error.
  SYSTEM ACTION: The parameter in error is ignored.  Profile
      processing continues.
  USER OR OPERATOR RESPONSE: Contact the system programmer to
      diagnose this error.
  SYSTEM PROGRAMMER RESPONSE: Verify that the correct CONNTYPE
      is specified.  If this is the correct conntype, the
      parameter is not valid for the port type or connection
      type.
  SOURCE DATA SET: EZAZMTNS
  PROCEDURE NAME: TELNET
  ************************************************************
  ************************************************************
  added the following messages (the descriptions are the same
  for all 7 messages):
  ***************************
  EZY3829I pre   xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
                 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
  
  EZY3830I       xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
                 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
  
  EZY3831I       xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
                 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
  
  EZY3832I       xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
                 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
  
  EZY3833I       xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
                 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
  
  EZY3834I       xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
                 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
  
  EZY3835I post  xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
                 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
  
  The following is the description for all 7 messages
  
  EXPLANATION:This message is part of the socket trace used
       for problem analysis and can be generated by specifying
       trace socket in the TCPIP.DATA configuration file.
  SYSTEM ACTION: TCPIP continues.
  USER OR OPERATOR RESPONSE: None.
  SYSTEM PROGRAMMER RESPONSE: Contact IBM Software Support
       Center and, if requested to do so, provide this
       information.
  SOURCE DATA SET: CMIUCSOC
  PROCEDURE NAME: hpns_common_select,  hpns_do_init,
       hpns_do_term, hpns_sock_request, getibmopt
  ************************************************************
  In message EZZ7899I changed the system programmer response
  to the following:
  Ensure that space is available in the HFS directory defined
  in the TMPDIR environment variable or in
  /tmp if TMPDIR is not defined.
  ************************************************************
  ************************************************************
  Message EZZ8314 was added:
  **********
  EZZ8314I DVIPA action for ipaddress failed with ERRNO=errno
           ERRNO2=errnojr
  
  EXPLANATION: The MODDVIPA utility failed to create or delete
    a Dynamic VIPA.
  
    action is the utility function and socket call that failed.
    ipaddress iis the Dynamic VIPA address or TCPIP stack name
    that is not valid.
  
    errno is the Sockets Return Code. These return codes are
    listed and described in the OS/390 Communications Server:
    IP and SNA Codes.
  
    errnojr is the hexadecimal Reason Code. The format of the
    4-byte Reason Code is explained in the introduction to the
    Reason Code section of the OS/390 UNIX System Services
    Messages and Codes.
  
  SYSTEM ACTION: TCP/IP continues. The utility ends.
  
  USER OR OPERATOR RESPONSE: If the IP address or TCPIP stack
    name was incorrectly specified, correct the error and run
    the utility again, otherwise contact your system programmer.
  
  SYSTEM PROGRAMMER RESPONSE: See the OS/390 UNIX System
    Services Messages and Codes for more information about the
    errnojr. See the OS/390 Communications Server: IP and SNA
    Codes for the specific reason for failure reported by errno.
  
  SOURCE DATA SET: EZBXFDVP
  
  PROCEDURE NAME: main
  ************************************************************
  ************************************************************
  Messages EZA5564I, EZA5565I, EZA5566I are new.
  ************
  EZA5564I date time Processing spool file filename
  EXPLANATION: This message is written to the SMTP sysdebug
    data set specified in the SYSDEBUG statement in
    hlq.SEZAINST(SMTPPROC). This message is generated whenever
    debug is active and SMTP is processing data from the JES
    spool.
  
    date is the current date.
  
    Time is the current time.
  
    Filename is the spool file name being processed by SMTP.
  
  SYSTEM ACTION: SMTP continues.
  USER OR OPERATOR RESPONSE: None.
  SYSTEM PROGRAMMER RESPONSE: None.
  SOURCE DATA SET: ServiceReaderMVS
  PROCEDURE NAME: SMTPBTCH
  ************
  EZA5565I date time Read spool file filename sent by userid
           at nodeid using TSO XMIT
  EXPLANATION: This message is written to the SMTP sysdebug
    data set specified in the SYSDEBUG statement in
    hlq.SEZAINST(SMTPPROC). This message is generated whenever
    debug is active and SMTP is processing data from the JES
    spool. The message indicates that the spool file was sent
    using the TSO/E TRANSMIT(XMIT) command. This command puts
    certain information in its headers indicating who and where
    the XMIT command was issued from. The XMIT command must be
    set up properly to contain the correct information.
  
    date is the current date.
  
    time is the current time.
  
    filename is the name of the spool file being processed by SMTP
  
    userid is the user identification taken from the XMIT headers.
  
    nodeid is the NJE node identification taken from the XMIT head
  
  SYSTEM ACTION: SMTP continues
  USER OR OPERATOR RESPONSE: If userid or nodeid is incorrect then
  contact the system programmer.
  SYSTEM PROGRAMMER RESPONSE: If userid or nodeid is incorrect the
  check the XMIT command setup parameters.
  SOURCE DATA SET: ServiceReaderMVS
  PROCEDURE NAME: SMTPBTCH
  ************
  EZA5567I filename.ADDRBLOK was incomplete and was deleted.
  EXPLANATION: This message is written to the SMTP output data
    set specified in the OUTPUT statement in hlq.SEZAINST
    (SMTPPROC). This message  is generated whenever SMTP detects
    partial control block data set (filename.ADDRBLOK) exists.
    The control block data set must have the following records:
      * record 1 - header information.
      * record 2 - sender information.
      * record 3 - recipient information. At least one recipient
                   record must be present.
  
    If SMTP detects a partial data set it will delete
    filename.ADDRBLOK and any corresponding filename.NOTE data
    set. Partial data sets might be created by failures to get
    space on the DASD.
  
    filename.ADDRBLOK is the name of the data set being deleted by
  SYSTEM ACTION: SMTP continues.
  USER OR OPERATOR RESPONSE: None.
  SYSTEM PROGRAMMER RESPONSE: Ensure that there is enough DASD
     space available for SMTP to continue.
  SOURCE DATA SET: EnqueueForDelivery
  PROCEDURE NAME: SMTPQUEU
  ************************************************************
  In Message EZZ6035I, added new value for description
  ***********************************
  2035 UNBIND or CLEAR ended a RECEIVE request.
    The VTAM Application has issued an UNBIND or CLEAR request
    that ended the RECEIVE RPL request. The connection is kept,
    waiting for the followup process from the application.
    Parm1, Parm2, and Parm3 may be set to return code, reason code
    and RPLrtncd/RPLfdbk2 which are defined in the OS/390 IBM
    Communications Server: SNA Programming.
  

Problem summary

Problem conclusion

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:

Fix information

Applicable component levels