hildum@iris.ucdavis.edu (Eric Hildum) (04/02/88)
I have run into a rather interesting problem with debugging a program which uses the SMG$ routines to control the screen. Normally, I would simply define DBG$INPUT and DBG$OUTPUT to a terminal I had allocated; however, at our facility, all the terminal lines are connected to a Develcon switch - thus there is no correspondence between a terminal and a port, nor is there a way (that I know of) to cause the Develcon to connect to a particular physical port from a terminal, nor to connect to a particular terminal from a port. The solution I have found is as follows: 1. Log in on two adjacent terminals, and use the show terminal command to determine the physical ports (we are running virtual terminals on all lines to allow processes to disconnect). 2. After setting the appropriate privledges, set one of the physical terminals to /PERMANENT/NOHANGUP and log out - with /NOHANGUP, the Develcon will not see a signal indicating that the process has gone away, and the terminal remains connected. 3. From the other terminal, allocate the port, and do a SET TERMINAL/INQUIRE to set the terminal type information. I may then define the logicals above and proceed with debugging. 4. Once done debugging, reset the permanent attributes to /HANGUP. The problem is that I need privledges to do this. What I would like to know is if anybody has a suggestion as to how I might set up a debugging environment without requiring special privledges (eg, log_io or phy_io to set the terminal attributes). Eric Hildum dehildum@ucdavis.ucdavis.edu (Internet) dehildum@ucdavis.bitnet (BITNET) ucbvax!ucdavis!dehildum (uucp)