.FO OFF
.RH ON
Item Number  II08962      - INT
.SP 2
.RH OFF
  APAR Identifier ...... II08962      Last Changed ........ 98/07/23
  INFO APAR FOR PSF MVS TCP/IP 569504001 HPRF220


  Symptom ...... IN INCORROUT         Status ........... INTRAN
  Severity ................... 4      Date Closed .........
  Component .......... INFOV2LIB      Duplicate of ........
  Reported Release ......... 001      Fixed Release ............
  Component Name V2 LIB INFO ITE      Special Notice
  Current Target Date ..              Flags
  SCP ...................
  Platform ............

  Status Detail: Not Available

  PE PTF List:

  PTF List:


  Parent APAR:
  Child APAR list:


  ERROR DESCRIPTION:
  BEFORE ASSUMMING A PSF PROBLEM WITH TCP/IP, IT IS REQUIRED THAT
  YOU BE ABLE TO PING THE IP/ADDR. IF YOU CANNOT PING THE DEVICE,
  THEN CONTACT YOUR TCP/IP ADMINISTRATOR TO CORRECT & DEBUG THE
  PROBLEM.
  **************************************************************
  TCP/IP ERRNO reason codes are documented in the TCP/IP
  APPLICATION PROGRAMMING INTERFACE REFERENCE SC31-7187 and also
  TCP/IP FOR MVS - MESSAGES & CODES MANUAL SC31-7132.
  ***************************************************************
  PSF/MVS TCP/IP APARS:
  OW15599 - PSF/MVS V2.2.0 TCP/IP SUPPORT APAR
  OW16914 - PSF/MVS V2.2.0 SUPPORT FOR TCP/IP ASIDS with NAME
            other than TCPIP.
  OW17026 - PSF/MVS V2.2.0 Possible ABEND378 RC14 in EZASOK03
  OW18606 - PSF/MVS V2.2.0 Possible ABEND0C4 in APSPSEND when
            using PSF exits coded AMODE24.
  OW19765 - HIPER - FSS fails to start or appears hung.
  OW19834 - Possible ABEND024 RC0D18 with TCP/IP attached
            printer.
  OW22828 - Psf support for TCPIP release 3.2.
  **************************************************************
                  Info apar for PSF MVS TCP/IP
  ***************************************************************
                         Section - 1
  Receiving MSGAPS935I ERRNO(0). Fixed by updating the Ethernet
  network address (mac address) in some ARP table. Also found
  a hardware problem.
  ****************************************************************
                         Section - 2
  ABEND052 RC0102 at PSF startup when START=YES is coded in JES.
  This occurs because PSF is checking for TCP/IP initialization
  which has not yet completed. Also HASP700 MSGHASP700 $HASP700
  for "FSS failed to connect" is issued. To correct the timing
  problem, code SUB=MSTR and TIME=NOLIMIT in the EZAZSSI
  procedure to initialize TNF and VMCF subsystems before JES and
  PSF. The other workaround would be to code START=NO in JES so
  that PSF printers are not brought up automatically at JES
  startup.
  ****************************************************************
             TCP/IP maintenance 5655hal00 r320
  Make sure all the TCP/IP maintenance listed below is applied
  to the tcp/ip r320 to prevent known problems and hangs.
  In addition the HIPER psf apar OW22828 / UW32832
  must be applied to PSF to support TCPIP 3.2.0.
  1st) pn88249 / un94504 symptom abenda78 rc10
  2nd) pq03285 / uq03848 symptom hang
  3rd) pq01611 / uq03944 symptom hang
  4th) pq06092 / uq07907 symptom hang
  96/08/20 Added New APAR numbers. SVR


  LOCAL FIX: