IBM Support

PI18168: FTP ENDS WITH EZA1736I QUIT GENERATED BY UNEXPECTED END OF FILE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Issue is only with V2R1 of Communication Server using IPSTART
    and issuing the FTP command with the REXX queue.
    
    
    ISPSTART CMD(%LOC1)
    
    EZA1736I FTP
    
    EZA1450I IBM FTP CS V2R1
    EZA1456I Connect to ?
    EZA1736I QUIT generated by unexpected end of file
    

Local fix

  • 1. Change the QMFPROC PARM=('ISPSTART CMD(%LOC1)')  to
     PGM=IKJEFT01,PARM= LOC1 and use the REXX QUEUE instead of the
     INPUT DD the FTP will work just fine.
    
    Or
    
    2. Change the QMFPROC PARM=('ISPSTART CMD(%LOC1)') to
     PGM=IKJEFT01 and set SYSTSIN to specify MEM1 and use the
     REXX QUEUE instead of the INPUT DD statement.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of the IBM Communications Server                   *
    * for z/OS Version 2 Release 1 IP: FTP                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When z/OS FTP is called by ISPSTART in                       *
    * batch and FTP input is on the REXX                           *
    * queue, DD:INPUT statement not found                          *
    * error occurred if FTP is in the AUTHCMD                      *
    * section of IKJTSOxx                                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply PTF                                                    *
    ****************************************************************
    When z/OS FTP is called by ISPSTART in batch, and it is
    in the AUTHCMD section of IKJTSOxx, the existing FTP
    code has problem determining whether REXX stack
    exists.
    

Problem conclusion

  • The problem has been corrected.
    

Temporary fix

Comments

  • ž**** PE14/10/10 FIX IN ERROR. SEE APAR PI27440  FOR DESCRIPTION
    ž**** PE14/10/10 FIX IN ERROR. SEE APAR PI27440  FOR DESCRIPTION
    ž**** PE14/10/10 FIX IN ERROR. SEE APAR PI27440  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PI18168

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-19

  • Closed date

    2014-07-14

  • Last modified date

    2015-02-27

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

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

    UI19558

Modules/Macros

  • EZAFTPCY EZAFTPSM EZAFTPRX EZAFTPDM
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R210 PSY UI19558

       UP14/09/04 P F409

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
27 February 2015