Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!europa.asd.contel.com!wlbr!pete
From: pete@wlbr.imsd.contel.com (Pete Lyall)
Newsgroups: comp.os.os9
Subject: Re: Can't execute "J" - Error #000: 216
Message-ID: <1991Jun19.063541.16459@wlbr.imsd.contel.com>
Date: 19 Jun 91 06:35:41 GMT
References: <1991Jun18.033225.12476@mmm.serc.3m.com> <1991Jun18.184533.1648@urz.unibas.ch> <1991Jun18.235439.6486@ncsu.edu>
Organization: Contel Federal Systems
Lines: 19

Kevin Darling suggest having the 'J' command eat up all of the
standard input... a good suggestion (Kev - where have I seen that
before.. grin)...

Another alternative... If the OSK shell works like the OS9/6809 shell,
when a procedure file is run, a child shell is forked from the
original shell with its standard input redirected from the alleged
script/procedure file. The 'J' command could simply get a copy of its
process descriptor (F$gprdsc, or whatever), determine its parent's
process ID (the secondary shell's ID), and it could send a KILL
signal, terminating the erroneously spawned 'procedure' shell.

Pete

-- 
Pete Lyall [GTE]   Compuserve: 76703,4230   Internet: pete@wlbr.imsd.contel.com
                UUCP: {hacgate,jplgodo,voder}!wlbr!pete 
"... So I picked up my pride from beneath the pay phone, and combed his breath 
right outta my hair. And sometimes, it's not so easy ..." J. Hendrix/My Friend