Don asks:
>
> Anyone ever seen this before?
>
> The rest of the error is as follows:
>
> **** Unknown trap (TRAPS 69).
>
> ABORT: PGCMXFIX.PUB77.BETAMSS
> NM USER  454.00801084 U_get_unwind_table
> NM SYS  a.0021e098 px_getsig_lowpri_$1a8
>  --- Interrupt Marker
> NM SYS  a.00e0049c ?pi_call_2_handler_$8
>  --- Interrupt Marker
 
If this is repeatable, and you don't mind using Priv Mode, with its
attendant warnings/caveats, here's one approach to solving the problem:
 
   1) either logon to a user.account with PM capability;
      or: logon as normal and run a good "GOD" utility.
 
      (and, setup your environment as necessary for running the program)
 
   2) enter:  run PGCMXFIX.PUB77.BETAMSS;debug    [;PARM=...;INFO=... etc]
 
      If you don't pop up in Debug quickly (well, up to a minute on a
      slow, loaded machine), then you don't have sufficient capabilities
      (try releasing the program file, perhaps)
 
   3) enter:  b trap_handler            NOTE the lowercase!
 
      If you get an error, you don't have PM.
 
   4) enter:  c
 
now, your program should be running as normal.  If it traps, you should
pop up into Debug.  At that point, do:
 
   5) enter:  tr, i, d
 
      and, enter:   dr
 
      Post/email the results  (or call me :)
 
This approach leverages of the fact that all internal traps go first
through trap_handler, and then into the user's handler (if any) or
the system's handler.
 
You can clear the breakpoint and continue by doing:
 
      bd @
      c
 
You can get out of Debug and abort the program by entering:
      abort
 
 
NOTE: setting a breakpoint at trap_handler means you're setting a breakpoint
in low level MPE/iX internal code ... this could cause problems, although
that is rather unlikely.  I suggest trying this after hours.
 
--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html