PH68427: IBM EXPLORER FOR Z/OS 3.4.1 EXPIRED EXTENDED LOCK TRACKER ENTRIES IN VSAM DUE TO IDLE CLIENT TIMEOUT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Users may encounter datasets and/or members that can only be
  opened in READ-ONLY mode when their site has implemented the
  optional extended Lock tracker feature along with the rse.env
  environment variable to disconnect idle clients,
  DDSTORE_IDLE_SHUTDOWN_TIMEOUT. The same file can be edited
  directly on z/OS but not from the client when this problem is
  present.
  
  This issue occurs when a user has files opened and they leave
  the client connected. When the idle timeout is reached the user
  is disconnected but expired entries remain in the extended lock
  tracker VSAM file for the files they left opened. The files are
  then only
  available in READ-ONLY mode when the user attempts to open them
  again.
  
  To correct this and clean up the expired entries, the following
  MODIFY command must be issued:
  
  MODIFY rsed APPL=CLEAN OWNER,EXPHRS=hours,DSN=
  
  ZOS0302T/K
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 1.All users                                  *
  *                 2.All users using RSE server with extended   *
  *                 lock tracker                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. During startup, zExplorer host may   *
  *                      produce the error insufficient          *
  *                      authority message. It's just a warning  *
  *                      and does not affect zExplorer           *
  *                      functionalities.                        *
  *                      2. Users may encounter datasets and/or  *
  *                      members that can only be                *
  *                      opened in READ-ONLY mode when their     *
  *                      site has implemented the                *
  *                      optional extended Lock tracker feature  *
  *                      along with the rse.env                  *
  *                      environment variable to disconnect idle *
  *                      clients,                                *
  *                      DDSTORE_IDLE_SHUTDOWN_TIMEOUT. The same *
  *                      file can be edited                      *
  *                      directly on z/OS but not from the       *
  *                      client when this problem is             *
  *                      present.                                *
  ****************************************************************
  1. It is from the work-around to test if Daemon can achieve
  superuser authority to be used as the best effort to accommodate
  feklogs operation when the unix profile security requirement not
  met.
  2. Users with connection timeout or disconnected abnormally may
  experience the issue as the lock extended information entries
  are not automatically cleaned up.
  

Problem conclusion

• 1. feklogs operation implementation has its own way of testing
  this work-around. It can be skipped from Daemon Java component
  side. The test for the authority and its execution during
  feklogs operation is removed from Daemon Java component.
  2.Server's MVS miner now includes the automatic cleanup of the
  extended lock entry info based on the connection's cache.
  

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:

  UO05417

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 FEKFDIR  FEKFDIR6 FEKFDIVP FEKFDST0 FEKFDST1 FEKFDST2
  FEKFENVF FEKFENVI FEKFENVP FEKFENVR FEKFENVS FEKFEPL  FEKFERRF
  FEKFGDGE FEKFICUL FEKFISPF FEKFIVP0 FEKFIVPA FEKFIVPD FEKFIVPI
  FEKFIVPJ FEKFIVPT FEKFJESM FEKFJESU FEKFJLIC FEKFJSON FEKFJVM
  FEKFLATR FEKFLDSI FEKFLDSL FEKFLEOP FEKFLOGS FEKFLPTH FEKFMAI6
  FEKFMAIN FEKFMINE FEKFMNTL FEKFNTCE FEKFOMVS FEKFPATT FEKFPKCS
  FEKFPLUG FEKFPTC  FEKFRIVP FEKFRMSG FEKFRSES FEKFRSRV FEKFSCMD
  FEKFSEND FEKFSSL  FEKFSTUP FEKFT000 FEKFT002 FEKFT003 FEKFT004
  FEKFT005 FEKFT006 FEKFT007 FEKFT008 FEKFT009 FEKFTEAM 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
  FEKLOCKA FEKLOGR  FEKLOGS  FEKM00   FEKM01   FEKM02   FEKMKDIR
  FEKMOUNT FEKMSGC  FEKMSGS  FEKPKCS1 FEKRACF  FEKRSED  FEKSAPF
  FEKSAPPL FEKSBPX  FEKSCLAS FEKSCLOG FEKSCMD  FEKSCPYM FEKSCPYU
  FEKSDSN  FEKSENV  FEKSETUP FEKSISPF FEKSJCFG FEKSJCMD FEKSJMON
  FEKSJWT  FEKSJWTU FEKSLPA  FEKSPROG FEKSPTKT FEKSRSED FEKSSERV
  FEKSSTC  FEKSSU   FEKSUSER FEKXCFGE FEKXCFGI FEKXCFGM FEKXCFGT
  FEKXMAIN FEKXML   HUHFCOR6 HUHFCORE
  

Fix information

• Fixed component name

  EXP FOR Z/OS HO

• Fixed component ID

  5655EXP23

Applicable component levels

• R340 PSY UO05417

     UP25/10/24 P F510

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.