(Optional) Extended lock tracker
Starting from z/OS® Explorer 3.2.0.16 (PTF UI75741), you can use the extended lock tracker service to help RSE API gather data set lock information. When this service is enabled in z/OS Explorer, it is automatically available to RSE API as well.
- For the data set lock owners who are connecting to the same RSEAPI server, the server resolves the lock owner ID to user ID.
- For the lock owners outside of the RSEAPI server, the server resolves the lock owner ID to the job name of the owner task.
Create the lock data set
Customize and submit the z/OS Explorer
sample FEK.SFEKSAMP(FEKLOCKA)
member to define the lock tracking data set. The
required customization steps are described within the member.
Refer to the output of the z/OS Explorer SMP/E installation jobs to learn the exact location of the SFEKSAMP
data
set.
Copy environment variables
Copy the commented RSE_EXTENDED_LOCK*
environment variables from the z/OS Explorer sample
/usr/lpp/IBM/zexpl/samples/rse.env
file to your rseapi.env
configuration file.
Refer to the output of the z/OS Explorer SMP/E installation jobs to learn the exact location of the zexpl/samples
directory.
rseapi.env
is located in /etc/zexpl/
, unless you specified a
different location when you customized and submitted the HUH.SHUHSAMP(HUHSETUP)
job. For more details, see Customization setup. You can edit the file with the TSO
OEDIT command.
Update rseapi.env
The extended lock tracker service is enabled when you specify environment variable
RSE_EXTENDED_LOCK=TRUE
in rseapi.env
. The lock tracking data set
is specified in the environment variable RSE_EXTENDED_LOCK_DSN
. For more details
and other extended lock tracker related environment variables, see rse.env, the RSE configuration file in the IBM® Explorer for z/OS Host Configuration Guide.