(Optional) Extended lock tracker

This customization task does not require assistance, special resources, or special customization tasks.

With the single-server setup of z/OS® Explorer, where multiple users are assigned to a single thread pool address space, z/OS lost the ability to track who owns a lock on a data set or member with the DISPLAY GRS,RES=(*,dataset*) operator command. System commands stop at address space level, which is the thread pool.

To address this problem, z/OS Explorer provides the MODIFY rsed APPL=DISPLAY OWNER,DATASET=dataset operator command, as described in Operator commands. The operator command can resolve all data set and member locks done by RSE users, as well as locks done by other products such as ISPF.

However, non-Eclipse clients, like IBM® Remote System Explorer API (RSE API) cannot access this information. And in situations with multiple RSE daemons, you need to know which RSE daemon to send the operator command too, because each of them only knows about their own locks.

The extended lock tracker addresses these problems. When enabled, RSE will store lock information in a lock tracking data set, which can be shared with other RSE. To reduce I/O to the data set, RSE buffers lock data in a timed cache.

To enable extended lock tracking services, follow these steps:
  • Create the lock tracking data set using the sample JCL FEKLOCKA.
  • Update rse.env to reference the data set and enable the extended lock tracker service.

Create the lock tracking data set

Customize and submit the sample FEKLOCKA member to define the lock tracking data set. The required customization steps are described within the member.

FEKLOCKA is located in FEK.#CUST.JCL, unless you specified a different location when you customized and submitted the FEK.SFEKSAMP(FEKSETUP) job. For more details, see Customization setup.

Update rse.env

The extended lock tracker service is enabled when you specify the environment variable RSE_EXTENDED_LOCK=TRUE in rse.env. The lock tracking data set is specified in environment variable RSE_EXTENDED_LOCK_DSN. For more details, see rse.env, the RSE configuration file.

rse.env is located in /etc/zexpl/, unless you specified a different location when you customized and submitted the FEK.SFEKSAMP(FEKSETUP) job. For more details, Customization setup. You can edit the file with the TSO OEDIT command.

Note: For the changes to take effect, you must restart the RSED started task.