| Title: | "ASK THE WIZARDS" |
| Moderator: | QUARK::LIONEL |
| Created: | Mon Oct 30 1995 |
| Last Modified: | Mon May 12 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1857 |
| Total number of notes: | 3728 |
Return-Path: "VMS001::WWW"@vms001.das-x.dec.com Received: by vmsmkt.zko.dec.com (UCX V4.1-12, OpenVMS V6.2 VAX); Wed, 15 Jan 1997 14:00:15 -0500 Received: from vms001 by mail11.digital.com (8.7.5/UNX 1.5/1.0/WV) id NAA15952; Wed, 15 Jan 1997 13:52:57 -0500 (EST) Date: Wed, 15 Jan 1997 13:52:31 -0500 Message-Id: <[email protected]> From: "VMS001::WWW"@vms001.das-x.dec.com (15-Jan-1997 1352) To: [email protected], [email protected], [email protected] Subject: Ask the Wizard: '[email protected]' X-VMS-To: [email protected] Remote Host: gw-DFO.iplink.net Browser Type: Mozilla/3.0 (Win95; I) Remote Info: <null> Name: Leonard Wilson Email Address: [email protected] CPU Architecture: VAX Version: v 6.2 Questions: Greetings; I was wondering if there was anyway to detect if the debug option was used in compiling a program "WITHOUT" running the program? Occassionally programs do not run in batch because they lack the RUN/NODEBUG. If there is not a way of detecting for debug, any thoughts on haulting a batch job if a program does not run due to debug? One more if I may. Here at work we have several reports which we allow people to view using the EDT editor. I would like to use the TPU editor instead. However, that is not possible unless I can turn off TPU commands such as SPAWN and DCL. These are not the commands everyone should have. Any suggestions? Thanks in advance.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1506.1 | ANALYZE/IMAGE; CAPTIVE or RESTRICTED Username | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Mon Feb 10 1997 17:29 | 28 |
There is a flag present in the image header that indicate that debugging support is present in the image. $ analyze/image/out=sys$scratch:img.tmp file $ search sys$scratch:img.tmp lnkdebug $ if $status ... ... ... handle search success (or failure) ... ... $common_exit: $ delete sys$scratch:img.tmp; If you choose to pursue direct access to the image header, look in the $IHDDEF (VAX) or $EIHDDEF (Alpha) module. (This is neither a supported nor a documented interface.) -- Given your comments around TPU and the desire to prevent SPAWN, this appears to be an environment where the use of CAPTIVE (or RESTRICTED) may be of interest. One can set the username CAPTIVE (or RESTRICTED), to `lock' the user into a command procedure. See the /TRUST qualifer on SPAWN, and see the system manager's manual for further information on captive command procedures. Also, one can set the username quotas to prevent the creation of a subprocess. | |||||