PI49060: FTP EZA1475I/EZA1735I ERRORS, POTENTIAL S0C4-11/U4039 ABENDS, AND POTENTIAL DATA LOSS/CORRUPTION WHEN USING FILETYPE=JES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When submitting a JES job through FTP GET (FILETYPE=JES) with
  JCL data that exceeds 180K bytes in DD:INPUT, abends S0C4-11 and
  U4039 can potentially occur. Also, there is potential JCL data
  loss or corruption depending on where the new line (NL) record
  delimiters are placed or if there were no record delimiters in
  the JCL data for the JES writes. Here's an example scenario
  resulting in the EZA1475I and EZA1735I errors and potential
  S0C4-11 or U4039 abend during the FTP GET for local file
  containing the JCL data:
  
    QUOTE SITE FILETYPE=JES
    QUOTE SITE JESJOBNAME=*
    GET foreign_file local_file  (size is > 180K bytes)
  
    EZA1475I CONNECTION WITH foreign_host TERMINATED
    EZA1735I STD RETURN CODE = 16125, ERROR CODE = 00010
  
  A traceback report from IPCS VERBX LEDATA 'CEEDUMP NTHREADS(*)'
  in a S0C4-11 or U4039 abend dump can look like the following:
  
   DSA Entry        E  Offset Loadmod  PgmUnit  Service  Status
    1  CEEHSDMP     +000000DE CEEPLPKA CEEHSDMP HLE7790  Call
    2  CEEHDSP      +000046A0 CEEPLPKA CEEHDSP  UI18451  Call
  > 3  jesWrite     +0000041C EZAFTPLS          EZAFTPJ  Exception
    4  jesWrtStream +000005FA EZAFTPLS          EZAFTPJ  Call
    5  jes_submit_job
                    +0000058C EZAFTPLS          EZAFTPJ  Call
    6  jesPutGet    +00000720 EZAFTPLS          EZAFTPJ  Call
    7  jesGet2      +00000D84 EZAFTPLS          EZAFTPJ  Call
    8  retrieve     +000002A4 EZAFTPLS          EZAFTPR  Call
  
  Abend S0C4-11 or U4039 occurs in the LE's stack area (STKL)
  for protection exception when the size of the JCL input data
  has exceeded 180K bytes during the JES write processing.
  
  Additional symptoms:
  --------------------
  1) Problem occurrence depends on how the storage is
     structured.
  
  2) The JCL data transfer during the FTP GET might result in a
     data loss or corruption depending on the placement of the
     record delimiters in the JCL data. If there are no record
     delimiters in the JCL data, the error message "451-Record
     is too long to process" might get issued.
  

Local fix

• 1) Do not put JCL data with size > 180 bytes in DD:INPUT card
     in a JCL for JES but rather put the JCL data in a MVS data
     set or file and reference that as the input to JES. This is
     the best and preferred method to deal with large input JCL
     data for the file transfer with FILETYPE=JES.
  
  2) See possible relief options under additional symptoms.
  
  KEYWORDS:
  EZAFTPJM JESWRITE EZA1475I EZA1735I FTP GET FILETYPE JES FTPJES
  S0C4 U4039 ABENDS0C4 ABENDU4039 180K TLSMECHANISM AUTH TLS SSL
  ATTLS TTLS UI25684 PI36109 CEE CEE0198S CEE3204S
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of the IBM Communications                          *
  * Server for z/OS Version 2 Release 1                          *
  * and 2: FTP with JES                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * FTP GET/PUT with JCL data sometimes abends                   *
  * with S0C4-11 and U4039.                                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply PTF.                                                   *
  ****************************************************************
  The problem can be summarized as below
  1. A JES job (FILETYPE = JES) is submitted through FTP GET/PUT
  2. The JCL data exceeds 180K bytes
  3. FTP abends with S0C4-11 and U4039
  

Problem conclusion

• FTP server code has been updated to ensure FTP does not look
  past
  the 180K buffer.
  

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:

  UI31965 UI31966

Modules/Macros

• EZAFTPJM
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R210 PSY UI31965

     UP15/12/15 P F512

• R220 PSY UI31966

     UP15/12/15 P F512

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.