PH54962: IBM EXPLORER FOR Z/OS V3.2 ABEND 0C4 AFTER APPLYING MAINTENANCE WITH CEE3204S PROTECTION EXCEPTION MESSAGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In z/OS Explorer 3.2 for the JMON started task, customers
  updating FEK.SFEKAUTH may experience an ABEND 0C4 when JMON is
  started up again after applying new maintenance. The following
  LE message is seen in the joblog:
  
  CEE3204S The system detected a protection exception (System
  Completion Code=0C4).
  From entry point LOADCSA at compile unit offset +0000009C at
  entry offset +0000009C at address 0F82D48C.
  
  This applies to customers that have FEK.SFEKAUTH in their
  LINKLIST (instead of a STEPLIB) and dynamically update the
  LINKLIST with UNALLOCATE. This method of updating the LINKLIST
  can cause errors in fetch module processing resulting in an
  ABEND106 or ABEND0F4. The LOADCSA routine which loads the module
  FEJENF70 into CSA is unable to handle non-abend load failures
  that can occur in the described scenario. LOADCSA will need to
  be updated to provide better error handling.
  
  Workaround:
  Adding a STEPLIB to the JMON PROC will temporarily resolve the
  issue. To fix this the system must be IPL'd so that the LINKLIST
  definitions and control blocks are rebuilt.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 1. N/A                                       *
  *                 2. IBM support                               *
  *                 3. all z/OS Explorer users                   *
  *                 4. The IBM Developer for z/OS Remote         *
  *                 Resource API                                 *
  *                 5. All users                                 *
  *                 6. All users allocate a dataset that a       *
  *                 LISTDS returns RC 4 (partial success)        *
  *                 7. All users                                 *
  *                 8. All users                                 *
  *                 9. users getting system activity report      *
  *                 10. sysprog                                  *
  *                 11. sysprog                                  *
  *                 12. All users                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. RSED includes non--existing          *
  *                      bin/classic directory when using        *
  *                      Java 11                                 *
  *                      2. FEKLOGS does not gather java.        *
  *                      security file for Java 11               *
  *                      3. JMON S0C4 abend during startup       *
  *                      4. IBM EXPLORER FOR Z/OS 3.3.X ADD      *
  *                      SUPPORT TO REMOTE RESOURCE API METHOD   *
  *                      TO ALLOW RETRIEVING JOB OUTPUT FOR A    *
  *                      STILL RUNNING JOB                       *
  *                      5. IVP Daemon failed at the second      *
  *                      step of the test to connect to          *
  *                      ServerThread.                           *
  *                      6. RSE mistreats LISTDSI RC 4 as        *
  *                      error while reporting back to client    *
  *                      query, causing client to display all    *
  *                      characteristics of the dataset as       *
  *                      "undetermined"                          *
  *                      7. RSE message listener could shut      *
  *                      down when encounter error in parsing    *
  *                      non-standard message format.            *
  *                      8. During client connection             *
  *                      establishment, when ThreadPool          *
  *                      retrieving user info using              *
  *                      ZosOmvsService, the service C program   *
  *                      fekfomvs may crash with a CEE dump.     *
  *                      The operation can recover but the new   *
  *                      fekfomvs would be under the current     *
  *                      userID.                                 *
  *                      9. user connection with JMON might be   *
  *                      terminated with S0CF when requesting    *
  *                      system activity report                  *
  *                      10. fekfivpi falsely report missing     *
  *                      DD SYSPROG when using LANG=Ja_JP        *
  *                      11. JMON may suffer S0C4 ABEND when     *
  *                      loaded from updated LINKLIST            *
  *                      12. Some dataset and members when       *
  *                      created with its ISPF statistic         *
  *                      filled with certain invalid data may    *
  *                      cause RSED detection of its SCLM        *
  *                      control bit incorrectly, causing        *
  *                      unexpected result for the operation     *
  *                      on the dataset member.                  *
  ****************************************************************
  1. z/OS Explorer RSED includes non--existing bin/classic
  directory when using Java 11
  2. z/OS Explorer FEKLOGS does not gather java.security file
  for Java 11
  3. ABEND0C4 at FEJJMON+1460 during JMON startup
  4. For developers working with the IBM Developer for z/OS
  Remote Resource API:
  
  Package: com.ibm.ftt.jes.util.core
  Interface: IJESJobUtil
  Method: getJobContents
  
  The getJobContents method can be used by developers to return
  the job contents for a job that has finished on the JES spool.
  It throws an exception if the job is still running. The
  getJobContents needs to be updated to return the job contents of
  a job that is still running since the Remote Systems Explorer
  already supports this functionality.
  5. In the second step connecting to ServerThread, IVP Daemon
  does not configure the gsk environment properly, causing the
  handshake and the connection failed.
  6. RSE mistreats LISTDSI RC 4 as error case.
  7. RSE message listener expects the message from TSO SEND and
  user EXIT routine in standard format. Messages with unexpected
  format either from original sender or issue with TSO SEND, or 
  user EXIT, or backend message listener could choke up and shut
  down the RSE Java message listener.
  8. A coding error in the routing to retrieve user information
  could lead to memory violation, leading to a crash and
  improper spawning the new fekfomvs under end user ID.
  9. the user connection with JMON might be terminated with S0CF
  ABEND when requesting a system activity report
  The first step in the test to connect to Daemon is working fine.
  10. fekfivpi, the z/OS Explorer IVP for ISPF Gateway fails
  reading ISPF.conf when using LANG=Ja_JP, resulting in RC 8 and
  a message that DD SYSPROC is not defined
  11. JES Job Monitor (JMON) may suffer S0C4 ABEND in LOADCSA
  when loaded from an updated LINKLIST
  12. When RSED reads the ISPF statistics of a dataset member
  for SCLM control bit, it missed to have the existing standard
  check on version and modification level.
  For some invalid ISPF data, RSED detects the SCLM control bit
  of the dataset member incorrectly as ON.
  

Problem conclusion

• 1. rse.final.env detects Java version and only includes
  bin/classic for J8
  2. FEKLOGS now detects Java version and selects correct
  directory
  3. corrected reentrant issue
  4. Updated the IBM Developer for z/OS Remote Resource API
  com.ibm.ftt.jes.util.core.IJESJobUtil.getJobContents to allow
  getting the job spool contents when the job is still active
  5. IVP Daemon does not set up the gsk environment properly for
  the ServerThread connection test, causing the handshake and
  test failure. In AT-TLS mode, it was logged explicitly in
  syslog with the TTLS 406 error.
  By preparing a correct gsk environment for the ServerThread
  connection, the handshake and the connection to the
  ServerThread port is fine.
  Note that as the connection in the test is not a complete
  client connection establishment, the pseudo connection will be
  shutdown from the server side as it does not receive the
  client message as expected in a standard client connection
  with corresponding messages logged in user logs.
  6. LISTDSI specification defines RC 0 and RC 4 as successful
  with RC 4 as partially successful, but RSE treats non-0 RC as
  error. Correct to have it treat RC 4 as successful when
  returning to client query.
  7. RSE message listener expect that TSO SEND and user EXIT
  construct message following a standard format. It works as
  expected when the original sender follows the valid syntax and
  rule of TSO SEND. In some conditions, such as when original
  message errors may escape the detection of TSO SEND and/or
  issues in user EXIT in constructing the forwarding message, or
  issue in RSE backend message listener, the message could
  arrive at RSE Java message listener in unexpected format.
  The RSE Java message listener has been modify to tolerate more
  with unexpected format message.
  8. Coding error in getting user info routine is fixed, and
  fekfomvs spawning now is done by a thread to have the process
  (ThreadPool) user ID ownership properly.
  9. added check to avoid division by 0
  10. With LANG=Ja_JP, shell scripting fails filtering on "^*"
  to exclude lines starting with "*". Updated fekfivpi to deal
  with this.
  11. added ERRET to LOADCSA
  12. RSED now validate the ISPF statistics of a dataset member
  based on the existing check on version and modification level
  before retrieving the SCLM control bit.
  In addition to that, a loose check on valid day is added to
  the validation of the ISPF statistic.
  

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:

  UI94690

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 FEKFT001
  FEKFT002 FEKFT003 FEKFT004 FEKFT005 FEKFT006 FEKFT007 FEKFT008
  FEKFT009 FEKFT010 FEKFT011 FEKFT012 FEKFT013 FEKFT014 FEKFT015
  FEKFT016 FEKFT017 FEKFT018 FEKFT019 FEKFT020 FEKFT021 FEKFT022
  FEKFT023 FEKFT024 FEKFT025 FEKFT026 FEKFT027 FEKFT028 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  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   HUHFCOR6
  HUHFCORE
  

Fix information

• Fixed component name

  EXP FOR Z/OS HO

• Fixed component ID

  5655EXP23

Applicable component levels

• R320 PSY UI94690

     UP24/01/02 P F312

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.