A fix is available
APAR status
Closed as program error.
Error description
IBM Explorer for z/OS - zExpl Using the RSE Daemon Remote Resource API for gathering remote resource information takes too much time.
Local fix
None available
Problem summary
**************************************************************** * USERS AFFECTED: 01.All zOS Explorer and IDz users * * 02.All zOS Explorer and IDz users * * 03.All zOS Explorer and IDz users * * 04.All zOS Explorer and IDz users * * 05.All zOS Explorer and IDz users * **************************************************************** * PROBLEM DESCRIPTION: 01.A sequence of TSO commands executed * * via RDz's IRemoteCommand API * * performs much slower than it would * * if the commands were executed * * directly. * * 02.The timestamp used to create the * * RSEDAEMON log file name is 2 hours * * off when TZ=Israel. * * 03.In zOS Explorer, OC4 abends may * * occur in libfekmain.so after call * * for trace. * * 04.When many users use zOS Explorer * * server simultaneously, fixed sized * * reserved area to convert characters * * between ebcdic and utf-8 is all * * used in some cases and * * FFSJNI_syncOpenConver() generates * * too many ceedump generated in zOS * * Explorer causes /tmp file to get * * full. * * 05.In zOS Explorer, sockets between * * RSED and JMON may be left in left * * in a close_wait state after a * * period of inactivity. * **************************************************************** * RECOMMENDATION: * **************************************************************** 01.A sequence of TSO commands executed via RDz's IRemoteCommand API performs much slower than it would if the commands were executed directly. 02.GMT time is used instead of IST. 03.When zOS Explorer host code is writing log information to trace files and some kinds of exceptions occur, the condition handler to handle the exceptions is called, it will call the same trace and the same exception occurs. The exception may be recursively raised and zOS Explorer RDz host process is killed. 04.When many users use zOS Explorer server simultaneously, fixed sized reserved area to convert characters between ebcdic and utf-8 is all used in some cases and FFSJNI_syncOpenConver() generates too many ceedump generated in zOS Explorer causes /tmp file to get full. 05.In zOS Explorer, the sockets with which RSED communicates with the JMON server may be not closed properly by the client side and left in a close_wait state. This happens if JMON has closed the connection after a timeout due to inactivity.
Problem conclusion
01.There are two reasons why the TSO commands have performance problems. First, the reading and writing to and from the ISPF client gateway is suboptimal (reading and writing only 1 byte at a time). Second, an artificial 1 second delay had been introduced by RDz in 2011 to circumvent an ISPF client gateway concurrency issue. That ISPF issue was resolved as of v2r1 so my solution is implemented to only avoid the artificial delay if the os is v2r1 or beyond. 02.All of the logics in the native host modules are updated to calculate timestamps based on the time zone offset information provided from java modules. All of timestamp information generated from zOS Explorer should be controlled by Java after applying the fix. 03.The host code is updated to stop output trace lines if they are requested from the condition handler triggered by an exception in the same trace code. 04.zOS Explorer server is updated to allocate the area for character conversions dynamically for each user session and to ensure each area freed after it is used with success or errors. 05.RSE server is updated to periodically check if each JMON connection has been closed by JMON server or not.
Temporary fix
Comments
APAR Information
APAR number
PI69402
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
2016-09-19
Closed date
2016-09-21
Last modified date
2017-03-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
FEKFCORE FEKFCOR6 FEKFJESM FEKFMAIN FEKFMAI6 FEKFMINE FEKFT005
Fix information
Fixed component name
EXP FOR Z/OS HO
Fixed component ID
5655EXP23
Applicable component levels
R300 PSY UI40951
UP16/09/30 P F702
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:
02 March 2017