Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!CITHEX.CALTECH.EDU!carl From: carl@CITHEX.CALTECH.EDU (Carl J Lydick) Newsgroups: comp.os.vms Subject: Re: Command tables for subprocesses Message-ID: <880516155721.92e@CitHex.Caltech.Edu> Date: 16 May 88 23:22:52 GMT References: <880421145148.000002CB091@naif.JPL.NASA.GOV> Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 27 > Any command that I have defined in my session with a "SET COMMAND > " command is unknown to a subprocess that I create with > "SPAWN/NOWAIT". Since I would like to do background processing with these > commands, the only way I know to make the commands available would be to > spawn a command procedure that contained the SET COMMAND command. This > would usually take enough time that it takes the edge off the efficiency I > am aiming for. Is there another solution that lets me type "SPAWN/NOWAIT > "? That depends on whether you have CMKRNL priv or on how friendly a system manager you have. If, when you modify your process's command tables with the SET COMMAND command, you make a copy of the new tables on disk via a command of the form $ SET COMMAND/TABLE=old_table/OUTPUT=new_table cld_file then install the new command table (/OPEN/HEADER/SHARE), you can use the command: $ SPAWN/TABLE=new_table to have your subprocess start out with the new commands already defined. On the other hand, I don't understand why you think the SET COMMAND command is slow, unless you're having it parse the human-readable definitions in .CLD files each time; if that's the case, you should be quite happy to learn about the other variations of the SET COMMAND command. The one described above generates a file containing a new set of compiled command tables. The command $ SET COMMAND/TABLE=new_table replaces your process's old command tables with those found in the new table. Replacing the whole set of command tables this way takes only about three seconds on a moderately loaded 780.