Fixes are available
APAR status
Closed as program error.
Error description
Rational Developer for System z - RDz - v9.1 Enqueues are created for temporary files that are used by the RDz threadpools when filters are expanded. These enqueues are not being cleaned up until the RDz server is recycled. These enqueues do not cause any problem. They have names such as: SYS1234.T1234567.RA000.RSED1859.R0100204
Local fix
None available
Problem summary
**************************************************************** * USERS AFFECTED: 01.All RDz users * **************************************************************** * PROBLEM DESCRIPTION: 01.Enqueues for temporary files are * * not cleaned up * **************************************************************** * RECOMMENDATION: * **************************************************************** 01.Exclusive enqueues on SYSDSN are created for temporary files that are used by the RDz thread pool processes when filters are expanded. These enqueues are not being cleaned up until the RDz server is recycled. RDz server calls DYNALLOC macro to allocate a temporary data set on a specific volume serial at first. Then it calls RDJFCB and OPEN TYPE=J to override the data set name with a special name for vtoc (44X'04'). As the default, the replaced name is witten back to the system JFCB but the previous temporary data set name is forgot without adjusting the enque status. Even if RDz server unallocates the file in JFCB, it is a vtoc name and the enque on a temporary data set remains.
Problem conclusion
01.RDz server is changed to set the bit JFCNWRIT in the JFCBTSDM field to 1, not to wirte back the replaced JFCB to the system JFCB. Though setting JFCNWRIT to replace a regular data set name is not recommended as documented, it should not cause errors for vtoc data set name.
Temporary fix
Comments
APAR Information
APAR number
PI48813
Reported component name
RD/Z HOST
Reported component ID
5724T0723
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-09-15
Closed date
2016-09-28
Last modified date
2016-10-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
FEKFMAIN FEKFMAI6
Fix information
Fixed component name
RD/Z HOST
Fixed component ID
5724T0723
Applicable component levels
R910 PSY UI41212
UP16/10/01 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":"9.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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
27 October 2020