Perhaps its a matter of versions, but when I issue MPEX's 'showproc' command
against a process that I KNOW has called the 'pause' intrinsic, I get the
following:

showproc #s2669

QPRI  CPUTIME   STATE  JOBNUM  PIN  (PROGRAM) STEP

                      #s2669, xtidis,manager.sys,sleepstg (ldev 90)
B152  0:00.137  WAIT   S2669   522  (JSMAIN.PUB.SYS)
C152  0:00.534  WAIT   S2669     272  :RUN slpr;parm=6;info="back0;nomail"
C152  0:00.146  PAUSE  S2669       207  (SLPR.SLEEPSTG.SYS) back0;nomail

OS version:  MPE/iX 5.5 PP7   & MPEX  version:  28N90803

Could it have to do something with the 'TIMERS' reported by the 'THMGR' (thresh
hold manager)?

Regards
Paul Christidis







> -----Original Message-----
> From: Bill Cadier [mailto:[log in to unmask]]
>
> According to our code (I checked up to 6.5) the MPE SHOWPROC
> command only displays BLKCB, BLKMM, WAIT and READY. We don't
> display a "TIMER" .  Unless that was the result of some patch I cannot
> find.
>
> >C152  0:00.388  WAIT   S613    311  :RUN NU010.PROG.BSI;LIB=G
> >C152  0:00.627  WAIT   S613      227  (NU010.PROG.BSI)
> >C200  0:01.141  TIMER  S613        586  (IRIS502.PUB.IRIS)
> >%SHOWQ;STATUS
>   ^
>    Is this the MPE version of SHOWPROC?

Nope -- the "%" is the tell-tale -- it is the default prompt used by MPEX.
Vesoft has "enhanced" the output of commands such as showproc to show
additional and/or more informative information on the "state" of a process.

> If I had to guess I'd say TIMER may be indicating a call to PAUSE() or
> a like function, say some form of timed wait. For example, a
> timed read
> of a message file. However the MPE SHOWPROC would only show this
> as "WAIT".

Exactly.  MPEX's showproc gets the info from various AIF's and system calls,
then presents them to the user "as found".  It appears MPE itself is
grouping various "states" into catchall-classes such as simply "WAIT".
Different strokes, I suppose -- some users are happy knowing "my process is
waiting for something", others want to know WHY it's waiting.

Tom