IBM Support

PH55322: IBM EXPLORER FOR Z/OS 3.3.0 FAILS TO CONNECT TO REMOTE SYSTEM WITH CRRZI9003E AND RSEG1057 MESSAGES AFTER THE CONNECT ATTEMPT

A fix is available

Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • For users attempting to connect to a remote z/OS system, they
may experience issues with the connection terminating after the
initial connection. The following messages will be issued from
the client side:

RSEG1057: The remote system connection has been lost
CRRZI9003E: Unable to connect to the JES Job Monitor on port {1}
of host {0}

Those messages can also be seen followed by this message in the
workspace log:

!ENTRY com.ibm.etools.zos.subsystem.jes 4 0 2023-06-07
09:29:31.351
!MESSAGE Connection failed because miner
com.ibm.etools.zos.jes.miners.JESMiner was not active on remote
system.

The JMON started task will show both a failed attempt to connect
and right after a successful connection attempt. The disconnect
was caused by the trusted TCP/IP function in JESMiner when
attempting to authenticate a connection to JMON. The recovery
logic on a failed attempt sends a disconnect request before the
reattempt to connect. The trusted TCP/IP function logic needs to
be updated to resolve this.

Workaround
The following Java property can be added to rse.env:

_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DJES_ENABLE_TRUSTED_TCPIP=false"

Make sure to recycle to RSED and JMON started tasks so that the
change is picked up.

Local fix

  • 



Problem summary


    

  • ****************************************************************
* USERS AFFECTED: 1. z/OS Explorer                             *
****************************************************************
* PROBLEM DESCRIPTION: 1. Users are disconnected from remote   *
*                      system when JES connection failed       *
****************************************************************
1. Users are disconnected from remote system when JES
connection failed

    



Problem conclusion


    

  • 1. When users are trying to connect JES from client, the
client will be disconnected from RSE server when the JES
connection failed due to the unexpected client disconnect
request sent by the JESMiner.  The resolution is to avoid
sending client disconnect request when the JES connection
fails in JESMiner.

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    PH55322
    • 

  • Reported component name
    EXP FOR Z/OS CL
    • 

  • Reported component ID
    5655EXP00
    • 

  • Reported release
    330
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2023-06-21
    • 

  • Closed date
    2023-10-16
    • 

  • Last modified date
    2023-11-01
    • 





    

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

    • 

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

    • 



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  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 FEKFPLUG FEKFPTC  FEKFRIVP FEKFRMSG FEKFRSES
FEKFRSRV FEKFSCMD FEKFSEND FEKFSSL  FEKFSTUP FEKFT000 FEKFT002
FEKFT003 FEKFT004 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


    

  • R330  PSY  UI94017
       UP23/10/21  P  F310
    • 



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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"330","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            02 November 2023
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback