16.12.2012 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

number parameter to specify the condition variables you want listed. You can also<br />

select condition variables with or without waiters by using the wait or nowait<br />

options.<br />

In order to capture the condition variables, dbx must be debugging your program<br />

before the condition variable is created. You must have coded your application in<br />

one of the following ways:<br />

v Add the following line at the top of the C program:<br />

#pragma runopts(TEST(ALL))<br />

Or:<br />

v Code an assembler program, CEEUOPT, to invoke the CEEXOPT macro, which<br />

specifies TEST(ALL). For examples of how to code this program, see z/<strong>OS</strong> XL<br />

C/C++ Programming Guide .<br />

Usage Note<br />

The condition subcommand can be run only while the dbx debug program is<br />

running.<br />

Examples<br />

1. To display all condition variables, enter:<br />

condition<br />

2. To display condition variables number 1 and number 4, enter:<br />

condition 1 4<br />

3. To display all condition variables with waiters, enter:<br />

condition wait<br />

4. To display all condition variables without waiters, enter:<br />

condition nowait<br />

cont subcommand for dbx: Continue program execution<br />

Format<br />

cont [signalnumber | signalname]<br />

dbx: condition<br />

Description<br />

The cont subcommand continues the execution of the program from the current<br />

stopping point until either the program finishes, another breakpoint is reached, a<br />

signal is received that is trapped by the dbx command, or an event occurs (such as<br />

a fork, an exec, or a program abend).<br />

If a signal is specified, either by the number specified in the signalnumber argument<br />

or by the name specified in the signalname argument, the program continues as if<br />

that signal had been received by the focus thread.<br />

If a signal is not specified, the dbx debug program variable $sigblock is set, and a<br />

signal caused the debugged program to stop, then the program resumes execution.<br />

If a signal is not specified, the dbx debug program variable $sigblock is not set,<br />

and a signal caused the debugged program to stop, then typing in the cont<br />

command with no signal causes the program to continue as if it had received the<br />

original signal.<br />

Signal names are not case-sensitive, and the SIG prefix is optional. If no signal is<br />

specified, the program continues as if it had not been stopped.<br />

Chapter 2. Shell command descriptions 193

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!