Art Arruda: 		HH to fix direct connected printers:

(With some additional comments from AC)

(To be used when:
          lpstat -t reports: "printer LP04 faulted", and
          dm_recon shows ok, lpc shows printer: enabled, queueing and printing,
 then:)

Use this procedure if all the other stations (different from printer
host) are reporting LP04 as faulted. 
Restart tcp listen process on printer host, and then,
Restart scheduler on the other stations

If the problem is reported by only one station, try to restart scheduler:
lpshut, /usr/lib/lpsched


Checking the port monitor status:

# sacadm -l
PMTAG          PMTYPE         FLGS RCNT STATUS     COMMAND
tcp            listen         -    0    ENABLED    /usr/lib/saf/listen tcp #
zsmon          ttymon         -    0    ENABLED    /usr/lib/saf/ttymon #


Killing the tcp port monitor:

# sacadm -k -p tcp
# sacadm -l
tcp            listen         -    0    NOTRUNNING  /usr/lib/saf/listen tcp #


Restarting the tcp port monitor:

# sacadm -s -p tcp
# sacadm -l           (Check port monitor status)
tcp            listen         -    0    STARTING   /usr/lib/saf/listen tcp #
zsmon          ttymon         -    0    ENABLED    /usr/lib/saf/ttymon #

... 2-3 minutes later...:

tcp            listen         -    0    ENABLED    /usr/lib/saf/listen tcp #

At this moment, LP04 should not be reported as faulted!!!                 

System printers also use 'lpNet' (listed with ps -ef)
/etc/lp/Systems    defines system printers

AC Note: The result of command "pmadm -l" is different on the printer Host 
than from a remote station. See below:

            HOST                            REMOTE CLIENT
pmadm -l:
   tcp  listen  lp  -  root  ...
   tcp  listen  lpd -  root  ...
   tcp  listen  0   -  root  ...
   zsmon ttymon ttyb u root  ...       zsmon ttymon ttyb u root ...