HP 5100tn Printer Job Language - Technical Reference Manual - Page 209

timed status need to work properly with printer sharing

Page 209 highlights

know which I/O interface to use when sending solicited printer responses. When the printer sharing device sends data to the printer from a different I/O interface, the printer sharing device must know to the exact byte boundary what printer response data should be sent to the previous I/O interface and what data should be sent to the current I/O interface. Before the printer sharing device sends the printer data from a different I/O interface than the source of the current print job, the printer sharing device can inject a PJL ECHO command. All solicited printer responses received before the PJL ECHO response should be sent to the previously active I/O interface. All solicited printer responses received after the PJL ECHO response should be sent to the currently active I/O interface. The printer sharing device should consume the PJL ECHO response which was a result of the PJL ECHO command injected by the printer sharing device. Applications that use unsolicited PJL device, job, page, or timed status need to work properly with printer sharing devices that do not support unsolicited printer-to-host responses. 3. A printer sharing device that can route solicited responses as described in 2 above, plus send all unsolicited responses to all attached host computers. Applications must be designed to properly ignore unexpected printer status readback responses. Ideas on how to design an application to ignore unexpected printer status readback responses are described in the next section. Programming Tips 10-29

  • 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
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309

know which I/O interface to use when sending solicited
printer responses. When the printer sharing device sends
data to the printer from a different I/O interface, the
printer sharing device must know to the exact byte
boundary what printer response data should be sent to
the previous I/O interface and what data should be sent
to the current I/O interface.
Before the printer sharing device sends the printer data
from a different I/O interface than the source of the cur-
rent print job, the printer sharing device can inject a PJL
ECHO command. All solicited printer responses received
before the PJL ECHO response should be sent to the pre-
viously active I/O interface. All solicited printer re-
sponses received after the PJL ECHO response should be
sent to the currently active I/O interface. The printer
sharing device should consume the PJL ECHO response
which was a result of the PJL ECHO command injected
by the printer sharing device.
Applications that use unsolicited PJL device, job, page, or
timed status need to work properly with printer sharing
devices that do not support unsolicited printer-to-host re-
sponses.
3. A printer sharing device that can route solicited re-
sponses as described in 2 above, plus send all unsolicited
responses to all attached host computers. Applications
must be designed to properly ignore unexpected printer
status readback responses. Ideas on how to design an ap-
plication to ignore unexpected printer status readback re-
sponses are described in the next section.
Programming Tips
10-29