| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 155.1 | | SMAUG::THOMPSON | | Thu Aug 29 1985 21:16 | 6 |
| Having given this no thought at all ... how about defining ctrl-z as an
"out-of-band" character and catching it that way?
It should work if you're running your own s/w, otherwise you will need
some other method.
Mark
|
| 155.2 | | TOOLS::STAN | | Fri Aug 30 1985 02:16 | 2 |
| Shutting of CTRL/Z is a bad idea and will cause certain programs
to hang with no way out of them.
|
| 155.3 | | PIGGY::BROUILLETTE | | Tue Sep 10 1985 17:47 | 16 |
| Here is the background of the system.
The system is a material tracking system used by the Distribution group
of DEC and is written in COBOL. The system is used by alot of outside vendors
that feed our system with all types of info. Because of the outside vendors,
the company is worried about hackers getting in thru there (not my prime worry)
My prime worry is that if they hit a CTRL/Z in the middle of building a record
in the record structure I have inherited with this system, that they will
corrupt the database.
What I am looking for is a tool that I can envoke at login time. As for the
possible problem with a user locking the system, I have ways around that alreadyon the system
thanks in advance,
Mike B.
|
| 155.4 | | TURTLE::GILBERT | | Tue Sep 10 1985 18:47 | 5 |
| COBOL supports the AT END option (on READ and ACCEPT), so you can
process EOFs however you wish. If you simply want to abort, you
could establish a condition handler to check for unexpected EOFs.
This seems too easy; perhaps I don't fully appreciate the problem.
|
| 155.5 | | SHOGUN::BLUEJAY | | Wed Sep 11 1985 09:45 | 7 |
| I'd suggest that you set up the program so that no database structures are
in 'undefined' states when input is being gotten from a user. That way, a
CTRL/Z won't mess things up. This also minimizes your exposure to aborts
due to system failures, since you're not sitting there for 15 minutes holding
on to a bunch of records.
- Bluejay Adametz, CFII
|