Pathway/iTS System Management Manual (G06.24+)

Tuning Your System Using Statistics

HP NonStop Pathway/iTS System Management Manual—426748-002

5-16

REQ CNT

The following subsections describe the entries for REQ CNT. (Note that requests

waiting on the $RECEIVE queue of a server process are not collected for statistical

purposes.)

TERMPOOL and SERVERPOOL

For TERMPOOL and SERVERPOOL, REQ CNT indicates the number of requests for

buffer allocation that were queued, and implies the number of SEND statements.

MEMMAN

For MEMMAN, REQ CNT indicates the number of requests for SCREEN COBOL code

that were queued. This number should be small after startup.

When a terminal task is about to execute, it asks the TCP to fetch all its defined

segments. This counts as a single request in the REQ CNT entry for MEMMAN.

LINK

For LINK, REQ CNT indicates the number of requests for a link that were queued.

For each SEND statement that finds no server available, the number for REQ CNT is

incremented by 1.

REQ CNT does not indicate the number of SEND commands executed by the TCP or

how often link requests are sent to the PATHMON process (because the task on the

LINK queue might be taken off that queue before the TCP relays its request to the

PATHMON process).

You get better performance if you tune your system to make %WAIT zero or less.

DELINK

For DELINK, REQ CNT indicates the number of times a dynamic server was idle and

the DELETEDELAY timer was started.

REQ CNT does not indicate how often the DELINK requests are sent to the

PATHMON process because the request might be taken off the DELINK queue before

the DELETEDELAY timer expires.

CHECKPOINT

For CHECKPOINT, REQ CNT indicates the number of requests for a checkpoint.

(All checkpoints join the queue whether the checkpointer task is busy or not.)

% WAIT

The following subsections describe the entries for %WAIT.