PH34966: RSE STARTED TASK THREAD POOL IS KILLED AFTER A "RESPONSE TIMEOUT"

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Using IBM Explorer for z/OS host, a heap damage due to an error
  in a file operation (i.e. a request for information of a
  dataset/member that does not yet exist) may cause the RSE
  threadpool to crash.
  
  In the syslog, the process "time out" is observed prior to the
  "killed process" message and error CEE0374C with
  CONDITION=CEE0810S can be seen.
  In the CEEDUMP, the traceback of the error condition shows the
  problem in
  Java_com_ibm_ftt_rse_mvs_server_miners_FFSJNI_getFileInfo from
  libfekfmain.so. Here is an example of the traceback:
  
  Traceback:
      DSA   Entry       E  Offset  Statement   Load Mod
  Program Unit                   Service  Status
      1     CEEHDSP     +00004A4C              CEEPLPKA
  CEEHDSP                        HLE77B0  Call
      2     CEEHSGLT    +00000060              CEEPLPKA
  CEEHSGLT                       HLE77B0  Exception
      3     CEEVFRST    +000000A4              CEEPLPKA
  CEEVFRST                       HLE77B0  Call
      4     CEEHSMSF    +00000072              CEEPLPKA
  CEEHSMSF                       HLE77B0  Call
      5
  Java_com_ibm_ftt_rse_mvs_server_miners_FFSJNI_getFileInfo
                        -27C665F8              libfekfmain.so
  Call
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 01.All zExpl and IDz users                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: 01.When operate on a dataset file in a  *
  *                         sequence of calls, including some    *
  *                         error cases such as non-existing     *
  *                         dataset file, RSE threadpool may     *
  *                         crash. This issue may affect all     *
  *                         calls that involve a                 *
  *                         getFFSResponse(), especially in      *
  *                         error cases when pMsg starts to get  *
  *                         set from init NULL state.            *
  ****************************************************************
  01.The pMsg of the FILE_INFO field of the input file handle
     used in a client command is not reset after used to generate
     the FFSResponse message and freed. (The field is *char with
     memloc as needed.) The field is double-freed when the file
     handle is reused through different JNI calls, pMsg got freed
     incorrectly when not reset to NULL after being freed.
  

Problem conclusion

• 01.Reset the pMsg field to NULL when its memory is freed to
     flag for the next possible message construction not to free
     it when it is indeed was not used previously.
  

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:

Modules/Macros

• FEJENF70 FEJJCNFG FEJJJCL  FEJJMON  FEJTSO   FEK1SMPE FEK2RCVE
  FEK3ALOC FEK4ZFS  FEK5MKD  FEK6DDEF FEK7APLY FEK8ACPT FEK@CERR
  FEK@CONE FEK@CONF FEK@CUST FEK@DEB  FEK@DESC FEK@FLOW FEK@GEN
  FEK@GENW FEK@ISPF FEK@IVP  FEK@IVPD FEK@IVPW FEK@JCN1 FEK@JCNE
  FEK@JESJ FEK@MAIN FEK@MIGO FEK@OPTE FEK@OPTG FEK@OPTN FEK@PRIM
  FEK@RSE1 FEK@RSEO FEK@STRT FEK@TAB1 FEK@TAB2 FEK@TAB3 FEK@WRK1
  FEK@WRK2 FEK@WRK3 FEK@WRK4 FEK@WRK5 FEKAPPCC FEKAPPCL FEKAPPCX
  FEKATTR  FEKDSI   FEKEESX0 FEKFASIZ FEKFATT1 FEKFBLD  FEKFCIPH
  FEKFCLIE FEKFCMOD FEKFCMPR FEKFCMSG FEKFCOMM FEKFCOPY FEKFCOR6
  FEKFCORE FEKFDBBF FEKFDBBP FEKFDBG  FEKFDBG6 FEKFDBGM FEKFDIR
  FEKFDIR6 FEKFDIVP FEKFDST0 FEKFDST1 FEKFDST2 FEKFENVF FEKFENVI
  FEKFENVP FEKFENVR FEKFENVS FEKFEPL  FEKFICUL FEKFISPF FEKFIVP0
  FEKFIVPA FEKFIVPD FEKFIVPI FEKFIVPJ FEKFIVPT FEKFJESM FEKFJESU
  FEKFJVM  FEKFLATR FEKFLDSI FEKFLDSL FEKFLEOP FEKFLOGS FEKFLPTH
  FEKFMAI6 FEKFMAIN FEKFMINE FEKFMINS FEKFMNTL FEKFNTCE FEKFOMVS
  FEKFPATT FEKFPRDS FEKFPTC  FEKFRIVP FEKFRMSG FEKFRSES FEKFRSRV
  FEKFSCMD FEKFSEND FEKFSSL  FEKFSTUP FEKFT000 FEKFT001 FEKFT002
  FEKFT003 FEKFT004 FEKFT005 FEKFT006 FEKFT007 FEKFT008 FEKFT009
  FEKFT010 FEKFT011 FEKFT012 FEKFT013 FEKFT014 FEKFT015 FEKFT016
  FEKFT017 FEKFT018 FEKFT019 FEKFT020 FEKFT021 FEKFT022 FEKFT023
  FEKFT024 FEKFT025 FEKFT026 FEKFT028 FEKFTIVP FEKFTRKS FEKFTSO
  FEKFUTIL FEKFVERS FEKFXITA FEKFXITL FEKFZME  FEKFZMF  FEKFZOS
  FEKHCONF FEKHCUST FEKHDEB  FEKHDESC FEKHFLOW FEKHGEN  FEKHISPF
  FEKHIVP  FEKHIVPD FEKHJESJ FEKHMAIN FEKHMIGO FEKHOPTE FEKHOPTN
  FEKHPRIM FEKHRSE1 FEKHRSEO FEKHSTRT FEKHTAB1 FEKHTAB2 FEKINIT
  FEKKEYS  FEKLOGR  FEKLOGS  FEKM00   FEKM01   FEKM02   FEKMKDIR
  FEKMOUNT FEKMSGC  FEKMSGS  FEKRACF  FEKRSED  FEKSAPF  FEKSAPPL
  FEKSBPX  FEKSCLAS FEKSCLOG FEKSCMD  FEKSCPYM FEKSCPYU FEKSDSN
  FEKSENV  FEKSETUP FEKSISPF FEKSJCFG FEKSJCMD FEKSJMON FEKSLPA
  FEKSPROG FEKSPTKT FEKSRSED FEKSSERV FEKSSTC  FEKSSU   FEKSUSER
  FEKXCFGE FEKXCFGI FEKXCFGM FEKXCFGT FEKXMAIN FEKXML
  

Fix information

• Fixed component name

  EXP FOR Z/OS HO

• Fixed component ID

  5655EXP23

Applicable component levels

• R310 PSY UI74253

     UP21/03/06 P F103

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.