IB Statements/noexcp
From CometWiki
(Difference between revisions)
Line 1: | Line 1: | ||
- | ''' | + | '''NOEXCP option on file system statements''' |
- | + | Parameter: NOEXCP | |
- | Parameter: NOEXCP | + | |
- | Discussion: Introduced with Comet32 this parameter may be used in file system statements to specify that if a non-fatal runtime exception occurs it should be ignored. This option is available for: ERASE, ENTER, EXTRACT, CREATE, CREATEKEY, DELETE, INPUT, INPUTFILE, INQUIRE, INSERT, POSITION, PRINTFILE, PRINT, OPEN, UPDATE, READ, RENAME, REWRITE, RUN, LOCK, UNLOCK, and WRITE. | + | Discussion: Introduced with Comet32 this parameter may be used in file system statements to specify that if a non-fatal runtime exception occurs it should be ignored. This option is available for: ERASE, ENTER, EXTRACT, CREATE, CREATEKEY, DELETE, INPUT, INPUTFILE, INQUIRE, INSERT, POSITION, PRINTFILE, PRINT, OPEN, UPDATE, READ, RENAME, REWRITE, RUN, LOCK, UNLOCK, and WRITE. |
+ | |||
For information about handling specific exceptions, see Exception Handling. | For information about handling specific exceptions, see Exception Handling. | ||
Revision as of 22:26, 28 May 2009
NOEXCP option on file system statements
Parameter: NOEXCP
Discussion: Introduced with Comet32 this parameter may be used in file system statements to specify that if a non-fatal runtime exception occurs it should be ignored. This option is available for: ERASE, ENTER, EXTRACT, CREATE, CREATEKEY, DELETE, INPUT, INPUTFILE, INQUIRE, INSERT, POSITION, PRINTFILE, PRINT, OPEN, UPDATE, READ, RENAME, REWRITE, RUN, LOCK, UNLOCK, and WRITE.
For information about handling specific exceptions, see Exception Handling.
Also see EXCPSUB=.
Example: ERASE file$ dir=dir$ NOEXCP
See system variables and EXCP for more information.