Re: SNMP vs. IPP

Kaj Julius wrote:

SNMP is better because it allows sharing between files (if you specify
*IBMSHRCNN on the USRDFNOPT attribute of the printer device). SNMP uses two ports. A data port, and a status port (actual SNMP). This allows you to know why the printer writer has stopped processing the spooled file (like out of paper condition, printer offline, etc.).




Rodney,

Just curious, does this also mean that a spool file is deleted only when the print job (spool file) has completed printing. We use IPDS printers mainly because we want to be absolutely sure that even if a printer, for whatever reason, has to be turned off the print job (spool file) can still be resumed. In other words, (if I remember correctly) in the past when we still used the PCL/PJL driver, if a printer lost power, sometimes print jobs just disappeared (cached in printer memory). Does the SNMP driver do the job of protecting us from this situation as well as IPDS?

TIA,
Kaj




SNMP waits only for acknowledgement from the TCP/IP layer that the last packet of data was successfully received by the NIC. Thus if the printer is shut off at the right time, you still could lose the file.

Unfortunately IPP also has the same limitation, and in fact might be worse, in that once the whole file is there iSeries assumes it is printed, where as SNMP, it would only be the last few pages or buffers of data that may not get printed and are lost.

The PJL method waits for confirmation that the last page printed. Unfortunately, many printer implementations send back an "early" print complete (that is it says last page printed before the page really has been printed).

IPDS is probably the only method that make sure the last page is printed (although I have heard of problems in this area, and don't know if all those bugs have been fixed...some at software level others were at printer microcode level).

--
Rodney A Johnson Technical Team Lead for AS/400 Spool
Dept GJC
IBM Rochester, Minnesota

The contents of this message express only the sender's opinion.
This message does not necessarily reflect the policy or views of
my employer, IBM. All responsibility for the statements
made in this Usenet posting resides solely and completely with the
sender.
.

Relevant Pages

  • [NEWS] Vulnerabilities in Ciscos SNMP Message Processing
    ... The vulnerability is only present in certain IOS releases on Cisco routers ... The Simple Network Management Protocol (SNMP) defines a standard mechanism ... to the UDP destination port 162. ... Although Cisco IOS devices have community-string access lists that check ...
    (Securiteam)
  • Cisco Security Advisory: Vulnerabilities in SNMP Message Processing
    ... Cisco Security Advisory: Vulnerabilities in SNMP Message Processing ... The vulnerability is only present in certain IOS releases on Cisco ... the SNMP agent to the UDP destination port 162. ...
    (Bugtraq)
  • [Full-Disclosure] Cisco Security Advisory: Vulnerabilities in SNMP Message Processing
    ... Cisco Security Advisory: Vulnerabilities in SNMP Message Processing ... The vulnerability is only present in certain IOS releases on Cisco ... the SNMP agent to the UDP destination port 162. ...
    (Full-Disclosure)
  • RE: Printer status and monitoring (WMI , SNMP)
    ... MS provide a SNMP API and a way for SNMP to become a feeder ... The status of printers and print jobs are updated by the Win32 Spooler ... It means that if there's no print job in the print ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: Mysterious SNMP Packets
    ... It was caused by Standard TCP/IP Ports that had "SNMP Status Enabled" ... should work on a Windows XP machine (and probably all modern Windows ... the UDP destination port is constant ... if the UDP source port is not constant, ...
    (microsoft.public.win32.programmer.networks)