IBM Support

PI83491: IBM Z/OS EXPLORER : JES NOTIFICATION IS NOT CORRECTLY WORKING ACROSS LPARS WITHIN THE SAME SYSPLEX

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • IBM z/OS Explorer - v3.0.1.2
    
    The JCL notification is not working in a Sysplex environment
    when the LPAR which triggers the job is not the same LPAR
    which executes the JOB.
    
    The process "JES Job Notify XXXXXX" is not displayed in the
    workbench even if the job is already completed on host.
    
    You can see the following messages:
    
    In the zOS SYSLOG:
    FEJE004I JOB27705 No notify request search due to wrong queue
    
    In the .log:
    !ENTRY org.eclipse.equinox.p2.core 4 0 2017-02-23 10:11:49.701
    !MESSAGE Exception during event notification
    !STACK 0
    java.lang.IllegalArgumentException: Location must be absolute:
    %25Update-Site-URL
    

Local fix

  • To have the job running on the local system use the SYSAFF=*
    parameter on the JOB card
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: 1. All zOS Explorer and IDz users            *
    *                 2. All zOS Explorer and IDz users            *
    *                 3. z/OS Explorer support                     *
    *                 4. All zOS Explorer and IDz users            *
    *                 5. SYSPLEX users utilizing job completion    *
    *                    Notify                                    *
    *                 6. All zOS Explorer and IDz users            *
    *                 7. All zOS Explorer and IDz users            *
    *                 8. All zOS Explorer and IDz users            *
    *                 9. All zOS Explorer and IDz users            *
    *                 10. z/OS system programmer                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. IBM z/OS Explorer Unused sockets are *
    *                         kept in storage.                     *
    *                      2. When a user deletes .eclipse         *
    *                         directory with all his files in his  *
    *                         uss home directory and connects to   *
    *                         RSE server, the syslog message       *
    *                         ICH408I on STATVFS may be shown      *
    *                      3. Enhance log gathering tool           *
    *                      4. Users who know exact dataset names   *
    *                         cannot access the data sets without  *
    *                         having access to any catalog,        *
    *                         including the one where that dataset *
    *                         is defined.                          *
    *                      5. job completion Notify only works for *
    *                         jobs running on the local system     *
    *                      6. IBM z/OS Explorer RSE user logs may  *
    *                         be written to the user's home        *
    *                         directory rather than the location   *
    *                         specified by the user.log server     *
    *                         config property                      *
    *                      7. In IBM zOS Explorer, a Remote        *
    *                         Systems view MVS filter that does    *
    *                         not contain wildcard characters may  *
    *                         incorrectly display GDG, VSAM or     *
    *                         ALIAS datasets as empty.             *
    *                      8. In z/OS Explorer, specifying a long  *
    *                         list of ciphers in                   *
    *                         GSK_V3_CIPHER_SPECS may prevent the  *
    *                         RSE server from starting.            *
    *                      9. In IBM z/OS Explorer, the TSO Logon  *
    *                         dialog may be shown when making an   *
    *                         RSE connection, even if the          *
    *                         interactive CEA gateway is not       *
    *                         enabled on the host                  *
    *                      10. Enhancement to simplify disabling   *
    *                          reusable Legacy ISPF Gateway        *
    *                          sessions.                           *
    ****************************************************************
    1. RSE server does not check the result of close() when it
       closes a socket connected from a client. As a result, even if
       tcp connection are correctly moved to the closed state,
       socket descriptors for unsuccessful close() remain in zos.
    2. When a user deletes .eclipse directory with all his files in
       his uss home directory and connects to RSE server, the syslog
       message as below may be shown.
    
    17199 17:03:17.60 S0082344 01000000  ICH408I USER(WDZT    )
    GROUP (STC1  ) NAME(RDZ                 )
       318 ..    /u/user1/.eclipse/RSE_TEST/user1/
       318 ..  CL(DIRSRCH ) .....
       318 ..  INSUFFICIENT AUTHORITY TO  STATVFS
       318 ..  ACCESS INTENT(--X)  ACCESS  ALLOWED(OTHER ---)
       318 ..  EFFECTIVE UID(1000000005)   EFFECTIVE GID(0000002000)
    3. Enhancements and bug fixes for log gathering tool:
       InList avoid substr(list,0), bug show server log, skip
       validation if PTC or ISPF don't exist, always init
       UpdatedSince, verify file permits, verify HLQ
    4. Users who know exact dataset names cannot access the data
       sets without having access to any catalog, including the one
       where that dataset is defined. Unlike ISPF, RDz always
       searches catalogs to process filters.
    5. job completion Notify only works for jobs running on the
       local system, not jobs that run on other systems within the
       SYSPLEX
    6. IBM z/OS Explorer RSE user logs may be written to the user's
       home directory rather than the location specified by the
       user.log server config property.  Using the RSE server with
       some versions of Java 8 may write the logs into an incorrect
       location
    7. In IBM zOS Explorer, a Remote Systems view MVS filter that
       does not contain wildcard characters may incorrectly display
       GDG, VSAM or ALIAS datasets as empty.  A code path that deals
       with non-wildcard MVS filesystem queries may not handle GDG,
       VSAM or ALIAS types correctly.
    8. In z/OS Explorer, specifying a long list of ciphers in
       GSK_V3_CIPHER_SPECS may prevent the RSE server from starting.
       Unexpectedly long option strings were truncated, leading to
       NullPointerExceptions in RSE server startup
    9. In IBM z/OS Explorer, the TSO Logon dialog may be shown when
       making an RSE connection, even if the interactive CEA gateway
       is not enabled on the host.  Client and server were not
       correctly identifying when the CEA gateway was enabled
    10. Enhancement to simplify disabling reusable Legacy ISPF
        Gateway sessions. After applying this update, reusable
        Legacy ISPF Gateway sessions can be disabled by adding the
        following to rse.env
    _RSE_ISPF_OPTS=""
    

Problem conclusion

  • 1. RSE server has been updated to retry calling close() for
       sockets when the previous call return errno=EAGAIN.
    2. The host module is updated to make the logging thread with
       the correct user authority be the only one that writes to
       rsecomm.log file.
    3. Enhancements and bug fixes for log gathering tool
    4. z/OS Explorer host code is updated to process filters by
       LOCATE macro if there is no wild card character in a filter
       string.
    5. JMON is updated to receive SYSPLEX signals as well. Requires
       matching ENF exit (v1.0.2)
    6. z/OS Explorer host code has been updated
    7. The zOS Explorer server modules are updated
    8. The zOS Explorer server modules are updated
    9. z/OS Explorer host and client modules have been updated
    10. Enhancement to simplify disabling reusable Legacy ISPF
        Gateway sessions.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI83491

  • Reported component name

    EXP FOR Z/OS HO

  • Reported component ID

    5655EXP23

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-22

  • Closed date

    2018-01-18

  • Last modified date

    2018-03-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI53287

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 FEKA040  FEKA0406 FEKA041
    FEKA0416 FEKA042  FEKA0426 FEKA043  FEKA0436 FEKA044  FEKA0446
    FEKA045  FEKA0456 FEKA046  FEKA0466 FEKA047  FEKA0476 FEKA048
    FEKA0486 FEKA049  FEKA0496 FEKA050  FEKA0506 FEKA051  FEKA0516
    FEKA052  FEKA0526 FEKA053  FEKA0536 FEKA054  FEKA0546 FEKA055
    FEKA0556 FEKAPPCC FEKAPPCL FEKAPPCX FEKDSI   FEKEESX0 FEKFASIZ
    FEKFBLD  FEKFCIPH FEKFCLIE FEKFCMOD FEKFCMPR FEKFCMSG FEKFCOMM
    FEKFCOPY FEKFCOR6 FEKFCORE FEKFDBGM FEKFDIR  FEKFDIR6 FEKFDIVP
    FEKFDST0 FEKFDST1 FEKFDST2 FEKFENVF FEKFENVI FEKFENVP FEKFENVR
    FEKFENVS FEKFEPL  FEKFICUL FEKFISPF FEKFIVP0 FEKFIVPA FEKFIVPD
    FEKFIVPI FEKFIVPJ FEKFIVPT FEKFJESM FEKFJESU FEKFJVM  FEKFLDSI
    FEKFLDSL FEKFLEOP FEKFLOGS FEKFLPTH FEKFMAI6 FEKFMAIN FEKFMINE
    FEKFMINS 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 FEKFTIVP FEKFTRKS FEKFTSO
    FEKFUNIV 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

  • R300 PSY UI53287

       UP18/02/03 P F802

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":"3.0.0","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":"3.0.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 March 2018