A fix is available
APAR status
Closed as program error.
Error description
z/OS Explorer 3.1.1.19 and IDz 14.1.7 FEKLOGS doesn't concatenate DSTORE_LOG_DIRECTORY in userlog/dstorelog/$LOGNAME/ when it is set to a value FEKLOGS job fails whatever the variable DDSTORE_LOG_DIRECTORY contains: _RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDSTORE_LOG_DIRECTORY=.eclipse/RSETEST/" _RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDSTORE_LOG_DIRECTORY=.eclipse/RSE/"
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: 01.All IDz and zExpl users * * 02.All z/OS Explorer and IDz users * * 03.All z/OS Explorer and IDz users * * 04.All zExpl and IDz users * * 05.All zExpl and IDz users * * 06.All z/os Explorer and IDz users * **************************************************************** * PROBLEM DESCRIPTION: 01.TLS 1 and 1.1 is no longer * * considered secure, so in RSE we * * will disable them by default * * 02.Due to zOS 2.4 announcement, we * * need to have RSE adding support for * * TLS 1.3 * * 03.Due to Java 6 out of support, we * * will now make Java 8 31bit as * * default java version * * 04.RSE is normally started up with * * default _BPX_SHAREAS=YES * * environment setting to optimize the * * cost in spawning supported * * processes by requesting the same * * address space as parent. System * * with the program /bin/sh, which is * * used for ThreadPool creation, * * having sticky bit unset would have * * the created ThreadPool terminated * * by SIGKILL (9) issued by Daemon * * shortly after it is created or * * after a client connection attempt. * * 05.Thread pool process is marked as * * timeout when it is stuck in a new * * client connection request and * * Daemon is time out while waiting * * for its response. * * 06.FEKLOGS do not concatenate * * DSTORE_LOG_DIRECTORY with * * userlog/dstorelog/$LOGNAME/ when it * * is set to a value other than none * **************************************************************** 01.TLS 1 and 1.1 is no longer considered secure, so in RSE we will disable them by default 02.Due to zOS 2.4 announcement, we need to have RSE adding support for TLS 1.3 03.Due to Java 6 out of support, we will now make Java 8 31bit as default java version 04.When ThreadPool is created within the same address space as that of Daemon, the ThreadPool would be terminated by SIGKILL issued by Daemon. _BPX_SHAREAS=YES setting is not in effect when the program file used in spawning has the sticky bit set. A system with a sticky-bit-on /bin/sh still creates the ThreadPool within its own address space. A system with a sticky-bit-off /bin/sh would have all ThreadPool created within the same address space as Daemon and would experience the SIGKILL problem shortly after it is started up. 05.A timeout thread pool is hardly considered for next connection request; its message pipe might also be out of sync. 06.When -DDSTORE_LOG_DIRECTORY is set, FEKLOGS fails to concatenate host server log and user log, as a result FEKLOGR will return ** INFO ** <user log path> does not exist, <user> has not used the product with return code 8. This is due to incorrect intermediate processing in the FEKLOGS rex script
Problem conclusion
01.Updated the corresponding rse environment variables 02.Added TLS 1.3 support, it can be used once supported Java is installed. 03.Modified the java_home values to make Java 8 31bit as default java version as default 04.It is a requirement that a ThreadPool must be created in an address space different from Daemon; otherwise, it would be terminated shortly after created. Furthermore, dataset lock owner information tracking based on ThreadPool address space id (ASID) unique indexing scheme. Daemon now creates ThreadPool with A _BPX_SHAREAS=NO in environment argument for in spawning call to have the ThreadPool created within its own address space regardless /bin/sh sticky bit setting. 05.The server module is updated to operate as a thread and drop a stuck connection request when informed by Daemon on the timeout. In the next configurable-interval pinging request from Daemon, if the thread pool is able to respond, its timeout status is reset and it would be considered to be re-selected for the next connection request. 06.Fixed the feklogs script bug as well as modifying ExistsUSS Access syscall rc code check from R_OK to F_OK
Temporary fix
Comments
APAR Information
APAR number
PH16725
Reported component name
EXP FOR Z/OS CL
Reported component ID
5655EXP00
Reported release
311
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-09-12
Closed date
2019-11-27
Last modified date
2020-01-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI66683
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 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 UI66683
UP19/12/07 P F912
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSBDYH","label":"IBM Explorer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"311","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"311","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 January 2020