<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Interpreting Print log file in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/interpreting-print-log-file/m-p/4558948#M649816</link>
    <description>hppi is an hp-ux utility for all printer types.</description>
    <pubDate>Wed, 06 Jan 2010 16:03:18 GMT</pubDate>
    <dc:creator>Michael Steele_2</dc:creator>
    <dc:date>2010-01-06T16:03:18Z</dc:date>
    <item>
      <title>Interpreting Print log file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/interpreting-print-log-file/m-p/4558945#M649813</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Can someone help me interpret this log file of a failed printing using LPD on hpux?(/var/adm/lp/log). I know lpd is obsolete but it has worked somewhat before and we have few alternatives. &lt;BR /&gt; The job # 386 initiated on printer LPHOLA1 did not print. Nothing seems to print anymore but the VPN is up and running. The printer was re-booted. It`s a Canon C2880i  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:55  r 5521 1262638516 0 386 0 7 188 maryjane - LPHOLA1 -&lt;BR /&gt;LPHOLA1-386     hs585   LPHOLA1 Jan  4 15:55&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  r 2827 1262638561 0 812 0 7 445 maryjane - EMAIL -&lt;BR /&gt;EMAIL-812       bgouldsb        EMAIL   Jan  4 15:56&lt;BR /&gt;/usr/sbin/lpsched:      CHILD: Jan  4 15:56  EMAIL 812 0000&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  m EMAIL c 15202&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  c f LPHOLA1 . .&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  r 2291 1262638586 0 813 0 7 445 maryjane - EMAIL -&lt;BR /&gt;EMAIL-813       sprince EMAIL   Jan  4 15:56&lt;BR /&gt;/usr/sbin/lpsched:      CHILD: Jan  4 15:56  EMAIL 813 0000&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  m EMAIL c 20151&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  c f LPHOLA1 . .&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:56  n&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:57  r 3426 1262638621 0 814 0 7 445 maryjane - EMAIL -&lt;BR /&gt;EMAIL-814       crobinso        EMAIL   Jan  4 15:57&lt;BR /&gt;/usr/sbin/lpsched:      CHILD: Jan  4 15:57  EMAIL 814 0000&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:57  m EMAIL c 26031&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:58  r 418494 1262638682 0 815 0 7 445 maryjane - EMAIL -&lt;BR /&gt;EMAIL-815       dngai   EMAIL   Jan  4 15:58&lt;BR /&gt;/usr/sbin/lpsched:      CHILD: Jan  4 15:58  EMAIL 815 0000&lt;BR /&gt;/usr/sbin/lpsched:      FIFO: Jan  4 15:58  m EMAIL c 7170</description>
      <pubDate>Tue, 05 Jan 2010 22:24:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/interpreting-print-log-file/m-p/4558945#M649813</guid>
      <dc:creator>Renaud Belanger</dc:creator>
      <dc:date>2010-01-05T22:24:14Z</dc:date>
    </item>
    <item>
      <title>Re: Interpreting Print log file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/interpreting-print-log-file/m-p/4558946#M649814</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;The way to trouble shoot a printer in HP-UX is with HPPI or JetAdmin.  You mention old.  Well JetAdmin was the OLD add on utility while HPPI is the NEW add on utility.  Regardless, they work the same way when it comes to diagnostics.&lt;BR /&gt;&lt;BR /&gt;#################&lt;BR /&gt;a) lpstat -p queuename (* might be P. *)&lt;BR /&gt;b) cancel any jobs&lt;BR /&gt;c) disable queuename&lt;BR /&gt;d) ls -l | hpnpf -x 'ipaddress' 9100 -n&lt;BR /&gt;&lt;BR /&gt;e) if it hangs =&amp;gt; there's a network problem. If it prints then delete and add in queuename, contact the sappers, and,&lt;BR /&gt;&lt;BR /&gt;f) enable queuename&lt;BR /&gt;################&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;a) create a one page test file:  name phone # call me&lt;BR /&gt;&lt;BR /&gt;b) type in hppi -or- jetadmin to main menu&lt;BR /&gt;c) diagnostics &lt;BR /&gt;d)  examine spooler operations (* menu option # 2 *)&lt;BR /&gt;4) select your printer&lt;BR /&gt;5) answer 'yes' to everything and observe the test print job running through the queue.&lt;BR /&gt;6) view /tmp/hpnpflog (* if there *)&lt;BR /&gt;</description>
      <pubDate>Wed, 06 Jan 2010 01:55:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/interpreting-print-log-file/m-p/4558946#M649814</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2010-01-06T01:55:03Z</dc:date>
    </item>
    <item>
      <title>Re: Interpreting Print log file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/interpreting-print-log-file/m-p/4558947#M649815</link>
      <description>We can use HPPI with a non-hp printer ?</description>
      <pubDate>Wed, 06 Jan 2010 15:33:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/interpreting-print-log-file/m-p/4558947#M649815</guid>
      <dc:creator>Renaud Belanger</dc:creator>
      <dc:date>2010-01-06T15:33:51Z</dc:date>
    </item>
    <item>
      <title>Re: Interpreting Print log file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/interpreting-print-log-file/m-p/4558948#M649816</link>
      <description>hppi is an hp-ux utility for all printer types.</description>
      <pubDate>Wed, 06 Jan 2010 16:03:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/interpreting-print-log-file/m-p/4558948#M649816</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2010-01-06T16:03:18Z</dc:date>
    </item>
    <item>
      <title>Re: Interpreting Print log file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/interpreting-print-log-file/m-p/4558949#M649817</link>
      <description>It was my understanding that Jetadmin/HPPI was for printers that support JetDirect only. It does lpd also on port 515 ?</description>
      <pubDate>Wed, 06 Jan 2010 16:39:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/interpreting-print-log-file/m-p/4558949#M649817</guid>
      <dc:creator>Renaud Belanger</dc:creator>
      <dc:date>2010-01-06T16:39:05Z</dc:date>
    </item>
    <item>
      <title>Re: Interpreting Print log file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/interpreting-print-log-file/m-p/4558950#M649818</link>
      <description>fine, don't use it.  Its on every single box but you don't have to use it.</description>
      <pubDate>Wed, 06 Jan 2010 17:02:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/interpreting-print-log-file/m-p/4558950#M649818</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2010-01-06T17:02:38Z</dc:date>
    </item>
  </channel>
</rss>

