At 11:36 AM -0800 2/3/00, [log in to unmask] wrote:
>I've been debugging a command file which uses a msg file to read a STD file.
>Occasionally in the process of debugging the command file will read an empty
>msg file, causing the command file (and session) to hang.
>
>Is there an easier way of "aborting" this situation other than a) aborting
>the session and logging on again, or b) debugging the command file which
>hangs from a child CI (RUN CI.PUB.SYS from the logon CI)?
>
>How would others approach this problem?


Hi,

1) In your command file check the eof of the msg file before reading it.
   Only if > 0 do your processing:

   if finfo('msgfile','eof') > 0
      <do some stuff>
   endif

2) If for some reason this isn't possible, and you must abort the
   child CI, and you're on MPE/iX 6.0, then you can abort the child
   CI using the ABORTPROC command, without aborting the whole session:

   abortproc pin=<ci pin>

3) If you don't want to abort the child CI and you still want to
   "unhang" your command file that's waiting on an empty message file,
   then from another session, just put some dummy data into the
   message file:

   :file m=msgfile,old
   :echo stuff >*m

HTH,


Barry Lake                                 [log in to unmask]
Allegro Consultants, Inc.                  www.allegro.com
(408)252-2330