A fix is available
APAR status
Closed as program error.
Error description
v32 internal defects fix and enhancement
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: 01.All z/os Explorer and IDz users * * 02.z/OS sysprog * * 03.All IDz and zExpl users * * 04.All z/OS Explorer and IDz users * * 05.All zExpl and IDz users * * 06.All zExpl and IDz users * * 07.All zExpl and IDz users * **************************************************************** * PROBLEM DESCRIPTION: 01.FEKLOGS do not concatenate * * DSTORE_LOG_DIRECTORY with * * userlog/dstorelog/$LOGNAME/ when it * * is set to a value other than none * * 02.Conditionally initialize key * * environment variables * * 03.TLS 1 and 1.1 is no longer * * considered secure, so in RSE we * * will disable them by default * * 04.Due to zOS 2.4 announcement, we * * need to have RSE adding support for * * TLS 1.3 * * 05.A change in DGRAM socket writing * * and reading required to fix the * * issue in logon message length * * limitation has caused a side * * effect, resulting the delay in the * * reading end in the processing of * * the message client listing * * responses from the threadpool to * * daemon. * * 06.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. * * 07.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. * **************************************************************** 01.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 02.Enhancement to conditionally initialize key environment variables PATH, LIBPATH, CLASSPATH, and STEPLIB. Initialization can be prevented by defining environment variable RSE_NO_INIT before RSE startup, e.g. RSE_NO_INIT="PATH:STEPLIB" 03.TLS 1 and 1.1 is no longer considered secure, so in RSE we will disable them by default 04.Due to zOS 2.4 announcement, we need to have RSE adding support for TLS 1.3 05.When the condition happens, the message receiving timing is unexpectedly. As a result, it may lead to an out-of-sync delay for other message flows using the same inter-process communication channel such as lock owner information queries required in opening a dataset member. 06.A timeout thread pool is hardly considered for next connection request; its message pipe might also be out of sync. 07.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.
Problem conclusion
01.Fixed the feklogs script bug as well as modifying ExistsUSS Access syscall rc code check from R_OK to F_OK 02.Enhancement to conditionally initialize key environment variables 03.Updated the corresponding rse environment variables 04.Added TLS 1.3 support, it can be used once supported Java is installed. 05.The additional msg length peeking while reading from a DGRAM socket might cause a failure in read-ready status of the socket in the next subsequent read. When the condition happens, the message receiving timing is unexpectedly. The change of msg length peeking is removed; the logon message upper bound has been increased as a replacement fix. Note that further investigation and change for socket communication would be needed for a much larger communication load as needed. 06.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. 07.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.
Temporary fix
Comments
APAR Information
APAR number
PH18993
Reported component name
EXP FOR Z/OS HO
Reported component ID
5655EXP23
Reported release
320
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-11-08
Closed date
2019-11-08
Last modified date
2019-11-30
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI66345
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 FEKFDBGM FEKFDIR FEKFDIR6 FEKFDIVP FEKFDST0 FEKFDST1 FEKFDST2 FEKFENVF FEKFENVI FEKFENVP FEKFENVR FEKFENVS FEKFEPL FEKFERRF FEKFICUL FEKFISPF FEKFIVP0 FEKFIVPA FEKFIVPD FEKFIVPI FEKFIVPJ FEKFIVPT FEKFJESM FEKFJESU FEKFJVM FEKFLATR FEKFLDSI FEKFLDSL FEKFLEOP FEKFLOGS FEKFLPTH FEKFMAI6 FEKFMAIN FEKFMINE FEKFMNTL FEKFNTCE FEKFOMVS FEKFPATT FEKFPLUG FEKFPTC FEKFRIVP FEKFRMSG FEKFRSES FEKFRSRV FEKFSCMD FEKFSEND FEKFSSL FEKFSTUP FEKFT000 FEKFT001 FEKFT002 FEKFT003 FEKFT004 FEKFT005 FEKFTIVP FEKFTSO FEKFUTIL FEKFVERS FEKFXITA FEKFXITL 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
R320 PSY UI66345
UP19/11/19 P F911
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":"320","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":"320","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
30 November 2019