A fix is available
APAR status
Closed as program error.
Error description
RDz v80: add additional heap usage tracing rseserver.log When the heap usage is over the value specified by maximum.heap.usage.ratio, the heap usage will be logged once. After that, the heap usage will not be logged even when the heap usage is over the maximum threshold: INFO Over MaxHeapUsage: ProcessId=, Memory_Usage= When the heap usage become below the threshold after the heap usage was over the threshold, the heap usage will be logged once: INFO Below MaxHeapUsage: ProcessId=, Memory_Usage=
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: 01.All RDz users * * 02.RDz users who use SSL client certificate * **************************************************************** * PROBLEM DESCRIPTION: 01.There is not enough trace to show * * why a new threadpool server is * * started. * * 02.RDz client cannot connect to SSL * * server using client certificate. * **************************************************************** * RECOMMENDATION: * **************************************************************** 01.There is not enough trace to show why a new threadpool server is started. 02.RDz client sends a client certificate to the server but the server fails to read the certificate due to a timing issue.
Problem conclusion
01.When the heap usage is over the value specified by maximum.heap.usage.ratio,the following trace will be logged once INFO Over MaxHeapUsage: ProcessId=, Memory_Usage= When the heap usage become below the threshold after the heap usage was over the threshold, the following trace will be logged once: INFO Below MaxHeapUsage: ProcessId=, Memory_Usage= 02.RDz server must wait for the client certificate to reach the server.
Temporary fix
Comments
APAR Information
APAR number
PM80742
Reported component name
RD/Z HOST
Reported component ID
5724T0723
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-01-16
Closed date
2013-07-15
Last modified date
2013-08-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
FEKFZOS
Fix information
Fixed component name
RD/Z HOST
Fixed component ID
5724T0723
Applicable component levels
R801 PSY UK96308
UP13/08/05 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":"8.0.1","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":"8.0.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
05 August 2013