PH15383: IDZ 14.1.7 DATASET OPENING NEEDS 20 SECONDS FROM IDZ CLIENT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The following work-items are included in the APAR
  - Enhancement - Internal RFE 24731: Query lockowner userid from
  threadpool - Ref: Internal RFE 22441
     - Enhancement - Internal RFE 24772: RSE optional
  configuration to skip the inter-process communication in
  lockowner userid discovery
  
  These two work-item fixes are to skip the inter-process
  communication in the file lock owner information discovery. The
  effect is to improve the performance in opening or editing a
  file.
  RSE server now uses a local call in discovery when users are
  from the same threadpool.
  When the file is locked by a user from a different threadpool,
  to enable a local-only discovery call, set the following RSE
  option when starting up the server:
     _RSE_JAVAOPTS="$_RSE_JAVAOPTS
  -Dprocess.skip.inter.lockInfo.disc=true"  (default to 'false')
     Note: the jobname would be returned in the discovery when the
  option is enable, not the user id.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 01.Users of MVS dataset operations.          *
  ****************************************************************
  * PROBLEM DESCRIPTION: 01.Users using IDz GUI to open or edit  *
  *                         a dataset (or dataset member) may    *
  *                         experience a delay of ~20 sec due    *
  *                         to timeout in the dataset lockowner  *
  *                         information query. The lock owner    *
  *                         information may not be filled in     *
  *                         the dataset property.                *
  ****************************************************************
  01.In the query for the dataset lockowner information as
     requested by IDz client for dataset operations, to exchange
     the information obtained RSE uses the inter-process
     communication between RSE daemon and threadpools. This
     communication mechanism could be affected by other
     operations of the daemon and threadpools, causing timeout
     and delay in processing the information in exchange.
  

Problem conclusion

• 01.For local users of the same threadpool, turn the
     inter-process communication to local call to avoid the
     possible delay in processing the information exchange. For
     users from different threadpools, if jobname instead of user
     id being returned is acceptable for the lock owner
     information, then using the optional new RSE configuration
     as a work-around also helps. Issues with inter-process
     communication is under investigation.
  

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:

  UI64702

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 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
  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 UI64702

     UP19/08/16 P F908

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.