IBM 6400-I15 User Manual - Page 141

Printer and Print Job Monitoring, Printer Logging Through Logpaths

Page 141 highlights

Printer and Print Job Monitoring To view the current status of an I/O port on the Ethernet Interface, two methods are available: 1. Selecting the desired I/O port on the "Status" HTML form (i.e. "http://EthernetInterfaceIPaddress/indexStatus.html"; e.g. "http://192.75.11.9/indexStatus.html") that comes with the Ethernet Interface. 2. "lpstat" command directly on the print server once logged in as "guest" or "root." In each case, you are given a description of each I/O port status and a list of queued jobs. Table 1 describes some of the common terms you may encounter wh Table 8-1. Key Printer Logging Terms Term "idle" "blocked" "waiting" Description There is no job queued for the Ethernet Interface I/O port. The printer is not allowing the Ethernet Interface to send data to it. Check that there is not a printer error and it is online and ready to go. The Ethernet Interface knows about a print job but is waiting for the host to send more data or to send an expected packet. Printer Logging Through Logpaths Within the Ethernet Interface product manual, destinations are described as logical queues with associated models and logpaths. Models determine if any extra processing is needed with the print jobs passing through and logpaths determine whether any logging is needed for each job. Each logpath on the Ethernet Interface consists of two parts: Type The type of log information to be captured. The choices are "job" for job ID and username, "user" for user ID (and three messages per job), "pgcnt" for total pages printed in a job, "cksum" for file checksums, "printer" for special printer feedback, and "ioport" for parallel printer status messages. Extra Features 8-5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154

8–5
Extra Features
Printer and Print Job Monitoring
To view the current status of an I/O port on the Ethernet Interface, two methods
are available:
1.
Selecting the desired I/O port on the “Status” HTML form
(i.e. “
http://
EthernetInterfaceIPaddress
/indexStatus.html
”;
e.g. “
”) that comes with the
Ethernet Interface.
2.
lpstat
” command directly on the print server once logged in as “
guest
or
root
.”
In each case, you are given a description of each I/O port status and a list of
queued jobs. Table 1 describes some of the common terms you may encounter
wh
T
able 8–1.
Key Printer Logging Terms
Term
Description
“idle”
There is no job queued for the Ethernet Interface I/O port.
“blocked”
The printer is not allowing the Ethernet Interface to send data to it. Check
that there is not a printer error and it is online and ready to go.
“waiting”
The Ethernet Interface knows about a print job but is waiting for the host to
send more data or to send an expected packet.
Printer Logging Through Logpaths
Within the Ethernet Interface product manual, destinations are described as
logical queues with associated models and logpaths. Models determine if any
extra processing is needed with the print jobs passing through and logpaths
determine whether any logging is needed for each job.
Each logpath on the Ethernet Interface consists of two parts:
Type
The type of log information to be captured. The choices are
job
” for job ID and username, “
user
” for user ID (and three
messages per job), “
pgcnt
” for total pages printed in a job,
cksum
” for file checksums, “
printer
” for special printer
feedback, and “
ioport
” for parallel printer status messages.