APAR status
Closed as program error.
Error description
APAR Error Description: Abstract: Rational Developer for System z (RDz) server V7.6.2.3 may raise an out of memory error when trying to open a MVS member in LPEX editor if it contains hexadecimal characters which cannot be round tripped from the host code page to the client code page and back. Problem: An error similar to the following can be found in rsecomm.log: ERROR MVSDownloadHandler: java.lang.OutOfMemoryError java.lang.OutOfMemoryError at java.lang.StringBuffer.ensureCapacityImpl(StringBuffer.java:338) at java.lang.StringBuffer.append(StringBuffer.java:131) at com.ibm.ftt.rse.mvs.util.FFSResponse.suppressNewLine(FFSResponse .java:506) at com.ibm.ftt.rse.mvs.util.FFSResponse.getResultsForXML(FFSRespons e.java:378) at com.ibm.ftt.rse.mvs.server.miners.MVSFileSystemMiner.getFileAndA ttribute(MVSFileSystemMiner.java:2707) If a heapdump is generated, it will show a significant amount of memory within a StringBuffer in MVSDownloadHandler. Local fix: Do NOT use System z Lpex editor to edit data files.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: 1. All RDz users * * 2. All RDz users * * 3. RDz support * * 4. RDz support * * 5. all users using LPEX editor to open data * * files * * 6. All RDz users * **************************************************************** * PROBLEM DESCRIPTION: 1. RDz receives FEK105E Error in * * sending audit data (rc=EOTHER) in * * z/OS system log as RSE failed to * * update the audit.log. * * 2. APPL=D P,CPU command uses BPXEKDA * * macro, but its non-zero return code * * is not logged * * 3. Setting debug_level to 3 dynamically * * is not possible for RSL/RDL commands * * 4. wrong error message upon faulty * * F RSED,APPL=D P,CPU command * * 5. RDz server may raise an out of * * memory error when trying to open an * * MVS member in LPEX editor if it * * contains hexadecimal characters * * which cannot be round tripped from * * the host code page to the client * * code page and back. * * 06.RDz "Display Client" header shows * * the number of the active clients per * * server process. But the actual * * number of clients can differ from * * what is listed. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. RDz receives FEK105E Error in sending audit data (rc=EOTHER) in z/OS system log as RSE failed to update the audit.log. 2. APPL=DISPLAY Process,CPU command uses BPXEKDA macro, but its non-zero return code is not logged 3. Setting debug_level to 3 dynamically is not possible for RSL/RDL commands 4. wrong error message upon faulty F RSED,APPL=D P,CPU command 5. RDz server may raise an out of memory error when trying to open an MVS member in LPEX editor if it contains hexadecimal characters which cannot be round tripped from the host code page to the client code page and back. An error similar to the following can be found in rsecomm.log ERROR MVSDownloadHandler: java.lang.OutOfMemoryError java.lang.OutOfMemoryError at java.lang.StringBuffer.ensureCapacityImpl StringBuffer.java at java.lang.StringBuffer.append(StringBuffer.java:131) at com.ibm.ftt.rse.mvs.util.FFSResponse.suppressNewLine FFSRes at com.ibm.ftt.rse.mvs.util.FFSResponse.getResultsForXML FFSRe at com.ibm.ftt.rse.mvs.server.miners.MVSFileSystemMiner.getFil If a heapdump is generated, it will show a significant amount of memory within a StringBuffer in MVSDownloadHandler. 06.The number of the clients which is shown as a header is managed by RDz daemon, not RDz server.
Problem conclusion
1. rc=EOTHER means that other code was returned by send API. In fact, the return code was EMSGSIZE (Message too long). MVSminer tried to write a big data for nonroundtrippable characters. Now, RDz will truncate the audit log data to 256 bytes. 2. Now, the non-zero return code from BPXEKDA will be logged. 3. Now, RSL/RDL command can be used to set log level to debug 4. problem has been resolved 5. The problem has been resolved. 6. Now, the number of the clients which is shown as a header is the actual number of clients.
Temporary fix
Comments
APAR Information
APAR number
PM66258
Reported component name
RD/Z HOST
Reported component ID
5724T0723
Reported release
760
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-06-06
Closed date
2012-08-23
Last modified date
2012-08-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
FEKFCMSG FEKFCORE FEKFCOR6 FEKFDIR FEKFDIR6 FEKFMAIN FEKFMAI6 FEKFMINE FEKFOMVS FEKFRIVP FEKFUTIL FEKFZOS
Fix information
Fixed component name
RD/Z HOST
Fixed component ID
5724T0723
Applicable component levels
R760 PSY UK81273
UP12/08/28 I 1000
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":"SSJK49","label":"IBM Developer for z Systems"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6","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":"7.6","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
27 October 2020