LPD

Explanation

LPD is the enclosing tag for all lpd entries.

Parent

OSAGENT

allowed values

• LPD2CHECK

Count

0 or 1. If you don't define lpd, no queues will be checked.

Example

<LPD>
  <LPD2CHECK>
    <HOST>some.print.server.org</HOST>
    <PORT>515</PORT>
    <Q2CHECK>
      <QNAME>LPT1</QNAME>
      <ERRORLEVEL>WARNING</ERRORLEVEL>
    </Q2CHECK>
    <Q2CHECK>
      <QNAME>LPT2</QNAME>
      <ERRORLEVEL>WARNING</ERRORLEVEL>
    </Q2CHECK>
  </LPD2CHECK>
  <LPD2CHECK>
    <HOST>printsrv.important.net</HOST>
    <PORT>515</PORT>
    <Q2CHECK>
      <QNAME>MYQ1</QNAME>
      <ERRORLEVEL>ERROR</ERRORLEVEL>
   </Q2CHECK>
   <Q2CHECK>
     <QNAME>MYQ2</QNAME>
    <ERRORLEVEL>ERROR</ERRORLEVEL>
   </Q2CHECK>
  </LPD2CHECK>
</LPD>
	

LPD2CHECK

Explanation

for every LPD daemon you want to check you define one LPD2CHECK XML tag pair. please consider that you might want to check multiple queues on the same LPD daemon. in this case just add one LPD2CHECK XML tag pair for the daemon containing the queues.

Parent

LPD

allowed values

• HOST

• PORT

• Q2CHECK

• The common XML tags as described in Section 9.8, “Tags Common to All Checks and/or Checkpoints”

Count

As many as you like.

Example

Look at LPD

Q2CHECK

Explanation

The sub-tags of LPD2CHECK describing the speficic queues we are going to check on this LPD. This tags have sub-tags of their own so that we can configure different error levels for each queue without supplying the hostname and the LPD port over and over again.

Parent

LPD2CHECK

Allowed VALUES

Count

As many as you like.

Example

Look at LPD

QNAME

Explanation

If child tag from Q2CHECK (in lpd): queue name defined in lpd.

If child tag from MQEUE (in mqs): MQ-Series queue name.

Parent

• Q2CHECK

• MQUEUE

Allowed Values

valid LPD queue names.

For MQSeries: perl regular expressions describing one or more MQS queue names.

Count

1

Example

Look at LPD or MQS