> -----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



> FWIW I hope this helps!
> +-------------------------------------------------------------
> --------+
> |Bill Cadier                  | Today is one of the "good old
> days"   |
> |Hewlett-Packard Co.          | you will be longing for in
> the future.|
> |Commercial Systems Division  |
>         |
> |Albuquerque, New Mexico      |
>         |
> [log in to unmask]   |
>         |
> +-------------------------------------------------------------
> --------+
>
> -----Original Message-----
> From: John Myers <[log in to unmask]>
> To: [log in to unmask] <[log in to unmask]>
> Date: Wednesday, March 29, 2000 7:20 AM
> Subject: TIMER State in SHOWPROC
>
>
> >Greetings,
> >
> >   Our users run an interactive program which sometimes
> makes them wait
> >for over 10 minutes for the next prompt. Below is the
> results of SHOWPROC
> >for one example along with our queue setup:
> >
> >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
> >
> >                    ------QUANTUM-------
> >QUEUE  BASE  LIMIT  MIN    MAX    ACTUAL  BOOST  TIMESLICE
> >-----  ----  -----  ---    ---    ------  -----  ---------
> > CQ    152    200   1      1000   6       DECAY    200
> > DQ    202    238   2000   2000   2000    DECAY    200
> > EQ    240    255   2000   2000   2000    DECAY    200
> >
> >What is TIMER? Does that mean that since this pin has the
> lowest priority
> >number in the C queue, it will remain in TIMER for a long
> wile until it
> >finally gets another timeslice? (Doing "HELP SHOWPROC
> OPERATION" showed a
> >list of Execution States, but TIMER was not in the list.)
> >
> >Thanks,
> >
> >John Myers
> >Christopher Newport University
> >
>