Results for WHENEVER


1 to 20 of 998 results. Prev  Next
Results per page:   20  | 40 | 60


Precompilers, 9i Release 2 (9.2.0.2)

Writing User Exits

Using WHENEVERcalled from other Oracle tools. Using WHENEVER You can use the WHENEVER statement in an exit to detect

Pro*C/C++ Programmer's Guide, 9i Release 2 (9.2.0.2)

Handling Runtime Errors

WHENEVER Actionsthe default action, equivalent to not using the WHENEVER directive. You can use it to turn off … error handler invoked by an EXEC SQL WHENEVER... DO... directive, and the function can return a … the WHENEVER condition is met, your program exits the loop it is inside. DO CONTINUE An actual … \"continue\" statement is placed in

Pro*C/C++ Programmer's Guide, 9i Release 2 (9.2.0.2)

User Exits

Using WHENEVERYou can use the WHENEVER statement in an exit to detect invalid datatype conversions (SQLERROR

Pro*COBOL® Programmer's Guide, 9i Release 2 (9.2.0.2)

Error Handling and Diagnostics

WHENEVER Directive… To do automatic condition checking and error handling, you need the WHENEVER statement. With the … WHENEVER statement you can specify actions to be taken when Oracle9 i detects an error, warning … | ANSI14}. To use WHENEVER SQLWARNING, however, you must declare the SQLCA. Note: You have to have included … statement if

Pro*C/C++ Programmer's Guide, 9i Release 2 (9.2.0.2)

Handling Runtime Errors

WHENEVER Examplesfollowing WHENEVER directives before the first executable SQL statement: EXEC SQL WHENEVER NOT FOUND … GOTO close_cursor; EXEC SQL WHENEVER SQLWARNING CONTINUE; EXEC SQL WHENEVER SQLERROR GOTO … error_handler; In the following example, you use WHENEVER...DO directives to handle specific errors:... EXEC

Pro*C/C++ Programmer's Guide, 9i Release 2 (9.2.0.2)

Handling Runtime Errors

WHENEVER Conditionsoptional when MODE=ANSI. To use WHENEVER SQLWARNING, however, you must declare the SQLCA. SQLERROR

SQL*Plus® User's Guide and Reference, 9i Release 2 (9.2.0.2)

SQL*Plus Command Reference

WHENEVER OSERROR{EXIT [ SUCCESS |FAILURE| n | variable |:BindVariable ] [ COMMIT |ROLLBACK] |CONTINUE [COMMIT|ROLLBACK| NONE ]} Performs the specified action (exits SQL*Plus by default) if an operating system error occurs (such as a file writing error). In i SQL*Plus, performs the specified action (stops the current script by default) and returns focus to the Input area if an operating system error occurs.

SQL*Plus® User's Guide and Reference, 9i Release 2 (9.2.0.2)

SQL*Plus Command Reference

WHENEVER SQLERROR{EXIT [ SUCCESS |FAILURE|WARNING| n | variable |:BindVariable ] [ COMMIT |ROLLBACK]|CONTINUE [COMMIT|ROLLBACK| NONE ]} Performs the specified action (exits SQL*Plus by default) if a SQL command or PL/SQL block generates an error. In i SQL*Plus, performs the specified action (stops the current script by default) and returns focus to the Input area if a SQL command or PL/SQL block generates an error.

Pro*COBOL® Programmer's Guide, 9i Release 2 (9.2.0.2)

New Features

WHENEVER DO CALL BranchThe WHENEVER directive now has a DO CALL action: a subprogram is called. See \"WHENEVER Directive\".

Precompilers, 9i Release 2 (9.2.0.2)

Error Handling and Diagnostics

Using the WHENEVER StatementSQL WHENEVER SQLERROR DO sql_error; -- other statements ROUTINE sql_error BEGIN -- get full text of … get the message text associated with a prior SQL statement. Using the WHENEVER Statement By default … . To perform automatic condition checking and error handling, use the WHENEVER statement.

Pro*Fortran, 9i Release 2 (9.2.0.2)

Error Handling and Diagnostics

Using the WHENEVER StatementDATA BUFLEN /200/ EXEC SQL WHENEVER SQLERROR GO TO 9000... * Handle SQL execution errors. 9000 WRITE … the message text associated with a prior SQL statement. Using the WHENEVER Statement By default, the … possible). To do automatic condition checking and error handling, you need the WHENEVER statement.

Pro*PL/I Supplement to the Oracle Precompilers Guide, 9i Release 2 (9.2.0.2)

Error Handling and Diagnostics

Using the WHENEVER Statementprocessing if possible. To do automatic condition checking and error handling, you need the WHENEVER … statement. With the WHENEVER statement you can specify actions to be taken when Oracle detects an error … statement, calling a procedure, branching to a labeled statement, or stopping. You code the WHENEVER … statement using

Pro*C/C++ Programmer's Guide, 9i Release 2 (9.2.0.2)

Handling Runtime Errors

Guidelines for WHENEVERgeneral, code a WHENEVER directive before the first executable SQL statement in your program. This ensures … that all ensuing errors are trapped because WHENEVER directives stay in effect to the end of a file … loop, as follows: EXEC SQL WHENEVER NOT FOUND DO break; for (;;) { EXEC SQL FETCH... } EXEC SQL CLOSE … catch that condition,

Pro*C/C++ Programmer's Guide, 9i Release 2 (9.2.0.2)

Handling Runtime Errors

Using the WHENEVER Directiveif possible. To do automatic condition checking and error handling, you need the WHENEVER directive … . With the WHENEVER directive you can specify actions to be taken when Oracle detects an error … , calling a routine, branching to a labeled statement, or stopping. You code the WHENEVER directive using the following syntax: EXEC SQL

Pro*C/C++ Programmer's Guide, 9i Release 2 (9.2.0.2)

Embedded SQL Statements and Directives

WHENEVER (Embedded SQL Directive)a loop when the condition is met. Usage Notes The WHENEVER directive allows your program to transfer … warning. The scope of a WHENEVER directive is positional, rather than logical. A WHENEVER statement … of the program logic. A WHENEVER directive remains in effect until it is superseded by another … WHENEVER

Pro*PL/I Supplement to the Oracle Precompilers Guide, 9i Release 2 (9.2.0.2)

Error Handling and Diagnostics

Scope of WHENEVERBecause WHENEVER is a declarative statement, its scope is positional, not logical. That is, it … the WHENEVER statement before the first executable SQL statement you want to test. A WHENEVER … statement stays in effect until superseded by another WHENEVER statement checking for the same condition … . Helpful Hint

Pro*COBOL® Programmer's Guide, 9i Release 2 (9.2.0.2)

Error Handling and Diagnostics

Coding the WHENEVER StatementCode the WHENEVER statement using the following syntax: EXEC SQL WHENEVER END-EXEC. DO PERFORM … When using the WHENEVER... DO PERFORM statement, the usual rules for PERFORMing a paragraph or … following WHENEVER... DO statement is invalid: PROCEDURE DIVISION. * Invalid statement EXEC SQL WHENEVER

Pro*COBOL® Programmer's Guide, 9i Release 2 (9.2.0.2)

Embedded SQL Statements and Precompiler Directives

WHENEVER (Embedded SQL Directive)subprogram parameters separated by blanks. The WHENEVER directive enables your program to take one of … of a WHENEVER statement is positional, rather than logical. A WHENEVER statement applies to all … logic. A WHENEVER statement remains in effect until it is superseded by another WHENEVER statement

Pro*C/C++ Programmer's Guide, 9i Release 2 (9.2.0.2)

Handling Runtime Errors

Scope of WHENEVERBecause WHENEVER is a declarative statement, its scope is positional, not logical. That is, it … program logic. So, code the WHENEVER directive before the first executable SQL statement you want to … test. A WHENEVER directive stays in effect until superseded by another WHENEVER directive checking for … the same

Pro*C/C++ Programmer's Guide, 9i Release 2 (9.2.0.2)

New Features

New Actions in WHENEVER StatementThe DO BREAK and DO CONTINUE actions are now supported by the embedded SQL directive WHENEVER. See … \"Using the WHENEVER Directive\" and \"WHENEVER (Embedded SQL Directive)\".





Was this page helpful?

Integrated Cloud Applications & Platform Services