z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

|
|
Usage Note
v The quit subcommand can be run only while the dbx debug program is running.
v The quit subcommand is not supported in GUI (socket) mode (-p).
Example
To exit the dbx debug program, enter:
quit
readwritelock subcommand for dbx: Display a list of active read/write
lock objects
Format
readwritelock [number ...]
readwritelock lock
readwritelock unlock
readwritelock holder
readwrite noholder
Description
The readwritelock subcommand displays a list of active read/write lock objects for
the application program. All active read/write lock objects are listed unless you use
the number parameter to specify the read/write lock objects you want listed. You
can also select only locked or unlocked read/write locks, or read/write locks with or
without holders, by using the lock, unlock, holder, or noholder options.
In order to capture the read/write lock variables, dbx must be debugging your
program before the read/write lock variable is created. You must have coded your
application in one of the following ways:
v Add the following line at the top of the C program:
#pragma runopts(TEST(ALL))
Or:
v Code an assembler program, CEEUOPT, to invoke the CEEXOPT macro, which
specifies TEST(ALL). For examples of how to code this program, see z/OS XL
C/C++ Programming Guide .
Or:
v Specify test(all) in the _CEE_RUNOPTS environment variable:
export _CEE_RUNOPTS="test(all)"
Usage Note
The readwritelock subcommand can be run only while the dbx debug program is
running.
Examples
1. To display all read/write lock objects, enter:
readwritelock
2. To display read/write lock objects number 1 and number 4, enter:
readwritelock 1 4
3. To display all locked read/write lock objects, enter:
readwritelock lock
4. To display all unlocked read/write lock objects, enter:
readwritelock unlock
5. To display all read/write lock objects with holders, enter:
dbx: quit
Chapter 2. Shell command descriptions 211