| Title: | FOCUS, from INFORMATION BUILDERS |
| Moderator: | ZAYIUS::BROUILLETTE |
| Created: | Thu Feb 19 1987 |
| Last Modified: | Mon May 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 615 |
| Total number of notes: | 1779 |
I am looking for a way to signal a process at the vms level
when an exception occurs from within the TABLE utility.
Does anyone have a subroutine that will do this?
Mike
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 153.1 | there ain't none... | MEMV02::COPPERSMITH | It's an allegory... | Thu Nov 17 1988 11:57 | 7 |
All you can do is run the table under the control of a dcl command
procedure, then use dcl error handling. There is no communication
between focus and vms handlers or any unwind capability.
Curtis Coppersmith
232-2246
MEMCL1::COPPERSMITH
| |||||
| 153.2 | This gets the job done. | TUNER::CARNEY | Wed Nov 23 1988 14:55 | 22 | |
I was able to screw around with the system variable &retcode.
When a table request bombs it sets &retcode to 8. Here is a routine
that I wrote with dialogue manager to signal to vms that an error
occured.
mike
-* This routine will run a focus table request and do error trapping.
-* If there is a problem with the request, &RETCODE will be set to 8
-* and execution will goto tablerr, where the logical fex$stat will be set
-* to 1.
-TOP
-INCLUDE FEX:
-RUN
-IF &RETCODE EQ '8' THEN GOTO TABLERR;
-EXIT
-TABLERR
-VMS DEFINE/JOB FEX$STAT 1
| |||||