A fix is available
APAR status
Closed as program error.
Error description
Rational Developer for System z - RDz - v8.0.3. Client used Windows taskmanager to end the RDz client because a Edit/save operation of a pds-member did not finish. The lock on the host for this member was not released. After a new connect of the client the lock had to be released by terminating the rDz threadpool that held the lock. This problem can also occur if a user keeps the RDz client logged onto the host overnight, and during the night the workstation is restarted because of automatic installations. The next day the user may still have a lock on the user's Source PDS-Library. *************************************************************** Local fix: To release the lock the applicable RDz threadpool has to be terminated.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: 01.All RDz users * * 02.All RDz users editing z/OS UNIX files * * 03.All RDz users * **************************************************************** * PROBLEM DESCRIPTION: 01.data set lock not released when * * client ends * * 02.backup file causes problem when * * parent folder is read-only * * 03.Multiple RDz RSE servers get * * *timeout* status, which is never * * reset. * **************************************************************** * RECOMMENDATION: * **************************************************************** 01.data set lock not released when client ends due to NPE in finish processing java.lang.NullPointerException at org. eclipse.rse.internal.dstore.universal.miners.command. CommandMinerThread.sendExit(CommandMinerThread.java:1066) followed later by java.lang.NullPointerException at org.eclipse.rse.internal. dstore.universal.miners.command.CommandMinerThread. cleanupThread(CommandMinerThread.java:1114) 02.creation of a backup file causes a problem when editing a file in a read-only folder (not allowed to create a new file) 03.OpenRSE thread and MVSminer thread are in contention in writing traces onto standard.out.
Problem conclusion
01.NPE is caused by _stdOutputHandler being null. The code has changed to accept a null value. 02.v8033 PTF UK81498 altered the way backups were created. The problem that was introduced is now resolved. problem bypass: add the following to rsed.envvars to disable the creation of the backup file _RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dbackupfiles=false" 03.Now, OpenRSE is changed so that it should not write any data onto standard.out
Temporary fix
Comments
APAR Information
APAR number
PM80840
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-17
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
FEKFCLIE FEKFDST0 FEKFDST1 FEKFDST2
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