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
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
|
<pre>Network Working Group R. Bergman
Request for Comments: 2708 Dataproducts Corp.
Category: Informational November 1999
<span class="h1">Job Submission Protocol Mapping Recommendations</span>
<span class="h1">for the Job Monitoring MIB</span>
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved.
Abstract
This document defines the recommended mapping for many currently
popular Job submission protocols to objects and attributes in the Job
Monitoring MIB.
Table of Contents
<a href="#section-1.0">1.0</a> INTRODUCTION.................................................<a href="#page-2">2</a>
<a href="#section-2.0">2.0</a> LINE PRINTER DAEMON (LPR/LPD) PROTOCOL.......................<a href="#page-4">4</a>
<a href="#section-2.1">2.1</a> jmJobSubmissionID Mapped to LPR/LPD..........................<a href="#page-4">4</a>
<a href="#section-2.2">2.2</a> jmJobIndex Mapped to LPR/LPD.................................<a href="#page-5">5</a>
<a href="#section-2.3">2.3</a> Other MIB Objects Mapped to LPR/LPD..........................<a href="#page-5">5</a>
<a href="#section-2.4">2.4</a> The Attribute Group Mapped to LPD............................<a href="#page-5">5</a>
<a href="#section-3.0">3.0</a> APPLETALK PROTOCOL...........................................<a href="#page-6">6</a>
<a href="#section-3.1">3.1</a> jmJobSubmissionID Mapped to AppleTalk........................<a href="#page-6">6</a>
<a href="#section-3.2">3.2</a> Other AppleTalk Mappings.....................................<a href="#page-6">6</a>
<a href="#section-4.0">4.0</a> INTERNET PRINTING PROTOCOL (IPP).............................<a href="#page-6">6</a>
<a href="#section-4.1">4.1</a> jmJobSubmissionID Mapped to IPP..............................<a href="#page-7">7</a>
<a href="#section-4.2">4.2</a> jmJobIndex Mapped to IPP.....................................<a href="#page-7">7</a>
<a href="#section-4.3">4.3</a> Other MIB Objects Mapped to IPP..............................<a href="#page-8">8</a>
<a href="#section-4.4">4.4</a> The Attribute Group Mapped to IPP............................<a href="#page-8">8</a>
<a href="#section-5.0">5.0</a> INTELLIGENT PRINTER DATA STREAM (IPDS)......................<a href="#page-10">10</a>
<a href="#section-5.1">5.1</a> jmJobSubmissionId Mapped to IPDS............................<a href="#page-10">10</a>
<a href="#section-5.2">5.2</a> The Attribute Group Mapped to IPDS..........................<a href="#page-11">11</a>
<a href="#section-6.0">6.0</a> DOCUMENT PRINTING APPLICATION (DPA).........................<a href="#page-11">11</a>
<a href="#section-6.1">6.1</a> jmJobSubmissionID Mapped to DPA.............................<a href="#page-11">11</a>
<a href="#section-6.2">6.2</a> jmJobIndex Mapped to DPA....................................<a href="#page-12">12</a>
<a href="#section-6.3">6.3</a> Other MIB Objects Mapped to DPA.............................<a href="#page-12">12</a>
<a href="#section-6.4">6.4</a> The Attribute Group Mapped to DPA...........................<a href="#page-13">13</a>
<span class="grey">Bergman Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
<a href="#section-7.0">7.0</a> NOVELL DISTRIBUTED PRINT SERVICE (NDPS).....................<a href="#page-14">14</a>
<a href="#section-7.1">7.1</a> jmJobSubmissionID Mapped to NDPS............................<a href="#page-14">14</a>
<a href="#section-7.2">7.2</a> jmJobIndex Mapped to NDPS...................................<a href="#page-14">14</a>
<a href="#section-7.3">7.3</a> Other MIB Objects Mapped to NDPS............................<a href="#page-15">15</a>
<a href="#section-7.4">7.4</a> The Attribute Group Mapped to NDPS..........................<a href="#page-15">15</a>
<a href="#section-8.0">8.0</a> PRINTER JOB LANGUAGE (PJL)..................................<a href="#page-17">17</a>
<a href="#section-8.1">8.1</a> jmJobSubmissionID Mapped to PJL.............................<a href="#page-17">17</a>
<a href="#section-8.2">8.2</a> jmJobIndex Mapped to PJL....................................<a href="#page-18">18</a>
<a href="#section-8.3">8.3</a> Other MIB Objects Mapped to PJL.............................<a href="#page-18">18</a>
<a href="#section-8.4">8.4</a> The Attribute Group Mapped to PJL...........................<a href="#page-18">18</a>
<a href="#section-9.0">9.0</a> POSTSCRIPT..................................................<a href="#page-18">18</a>
<a href="#section-9.1">9.1</a> jmJobSubmissionID Mapped to PostScript......................<a href="#page-19">19</a>
<a href="#section-9.2">9.2</a> Other MIB Objects and Attributes Mapped to PostScript.......<a href="#page-19">19</a>
<a href="#section-10.0">10.0</a> NETWARE PSERVER............................................<a href="#page-19">19</a>
<a href="#section-10.1">10.1</a> jmJobSubmissionID Mapped to PServer........................<a href="#page-19">19</a>
<a href="#section-10.2">10.2</a> jmJobIndex Mapped to PServer...............................<a href="#page-19">19</a>
<a href="#section-10.3">10.3</a> Other MIB Objects Mapped to PJL............................<a href="#page-20">20</a>
<a href="#section-10.4">10.4</a> The Attribute Group Mapped to PServer......................<a href="#page-20">20</a>
<a href="#section-11.0">11.0</a> NETWARE NPRINTER or RPRINTER...............................<a href="#page-20">20</a>
<a href="#section-12.0">12.0</a> SERVER MESSAGE BLOCK (SMB) PROTOCOL........................<a href="#page-21">21</a>
<a href="#section-12.1">12.1</a> jmJobSubmissionID Mapped to SMB............................<a href="#page-21">21</a>
<a href="#section-12.2">12.2</a> jmJobIndex Mapped to SMB...................................<a href="#page-21">21</a>
<a href="#section-12.3">12.3</a> Other MIB objects Mapped to SMB............................<a href="#page-21">21</a>
<a href="#section-13.0">13.0</a> TRANSPORT INDEPENDENT PRINTER/SYSTEM INTERFACE (TIP/SI)....<a href="#page-22">22</a>
<a href="#section-13.1">13.1</a> jmJobSubmissionID Mapped to TIP/SI.........................<a href="#page-22">22</a>
<a href="#section-13.2">13.2</a> jmJobIndex Mapped to TIP/SI................................<a href="#page-22">22</a>
<a href="#section-13.3">13.3</a> Other MIB Objects Mapped to TIP/SI.........................<a href="#page-22">22</a>
<a href="#section-13.4">13.4</a> The Attribute Group Mapped to TIP/SI.......................<a href="#page-22">22</a>
<a href="#section-14.0">14.0</a> SECURITY CONSIDERATIONS....................................<a href="#page-23">23</a>
<a href="#section-15.0">15.0</a> REFERENCES.................................................<a href="#page-23">23</a>
<a href="#section-16.0">16.0</a> AUTHORS' ADDRESSES.........................................<a href="#page-24">24</a>
<a href="#section-17.0">17.0</a> FULL COPYRIGHT STATEMENT...................................<a href="#page-26">26</a>
<span class="h3"><a class="selflink" id="section-1.0" href="#section-1.0">1.0</a> INTRODUCTION</span>
The Job Monitoring MIB [<a href="#ref-JobMIB" title=""The Job Monitoring MIB - V1.0"">JobMIB</a>] is intended to be implemented in a
device or server that supports any job submission protocol. However,
the information available and the method of presentation varies
significantly by job submission protocol. A common method of mapping
job submission information to the Job Monitoring MIB is essential for
interoperability of Job MIB agents and monitoring applications. This
document defines recommended mappings for most popular job submission
protocols to ensure this compatibility.
<span class="grey">Bergman Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
All mappings are unidirectional from the job submission protocol to
the MIB. It is assumed that support of the job submission protocol
in the printer implies that the reverse information flow is presently
defined and does not require interaction from the MIB. This mapping
is not defined in this document as it should be obvious.
This document refers to system configurations that are defined in the
Job Monitoring MIB [<a href="#ref-JobMIB" title=""The Job Monitoring MIB - V1.0"">JobMIB</a>]. For those readers that are familiar
with the configuration descriptions, a short summary appears here.
Please see the Job MIB document for further details.
Configuration 1: This is a simple peer-to-peer system which contains
only a client and a printer. The Job MIB agent is
resident in the printer.
Configuration 2: This system contains a client, server, and a
printer. The Jib MIB agent is resident in the
server.
Configuration 3: This system, as in configuration 2, contains a
client, server, and a printer. In this case the
Job MIB agent is implemented within the printer.
The most important object to be mapped is jmJobSubmissionID, since
this is a method for the user or client to determine the jmJobIndex
for a submitted job. Therefore, jmJobSubmissionID is specified for
all job submission protocols defined in this document. The remaining
objects mapped include only those items that have the equivalent
information presented to the printer by the job submission protocol.
While this document places a strong emphasis on jmJobSubmissionID
mapping to obtain jmJobIndex, the preferred method is through the use
of a bi-directional job submission protocol that returns the
equivalent value of jmJobIndex to the client, such as IPP. When a
bi-directional protocol that returns jmJobIndex is in use, the
jmJobSubmissionID object has no value to the client. When the
jmJobIndex cannot be returned, the use of a client defined
jmJobSubmissionID is preferred over an agent derived value. The
client defined version allows for retrieval of jmJobIndex using a
single SNMP Get operation, since jmJobSubmissionID is the index into
the jmJobIDTable. An agent derived value will require a search
through multiple entries in the jmJobIDTable.
The majority of the protocols mapped in this document are oriented
towards network job submission. However, the Job Monitoring MIB is
also intended to monitor print jobs received from other than network
ports, such as parallel and serial ports. Some of the job submission
protocols included that are used with non-networked ports are PJL,
<span class="grey">Bergman Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
PostScript, and TIP/SI. In addition, the Job Monitoring MIB can be
used with print jobs that are internally generated, such as self test
pages. In this latter case, no mapping is required since all job
submission protocols are bypassed.
<span class="h3"><a class="selflink" id="section-2.0" href="#section-2.0">2.0</a> LINE PRINTER DAEMON (LPR/LPD) PROTOCOL</span>
The LPR/LPD printing protocol [<a href="#ref-LPD" title=""Line Printer Daemon Protocol"">LPD</a>] is used with BSD UNIX systems in
the client-server-printer configuration. Usage of the Job Monitoring
MIB with LPR/LPD will most likely conform to Configuration 3, where
the monitor application or the server uses SNMP to obtain job
information from the printer. The client communicates with the UNIX
server using the existing LPD protocol to obtain job information.
The LPR/LPD protocol is also used in the Windows environment to
implement peer-to-peer printing, as shown in configuration 1. In
this case, SNMP is used by the client and/or the monitor application
to obtain the job information.
One of the major problems of LPR/LPD is the large number of vendor
unique extensions currently used with the protocol and the resulting
compatibility issues between available implementations. To avoid
these issues, this mapping of LPR/LPD is restricted to the protocol
as defined by <a href="./rfc1179">RFC 1179</a>.
The LPR/LPD protocol transfers print job data and control information
in separate files, known as the Data File and Control File,
respectively. Most of the information concerning the print job is
contained in the Control File. In many LPD implementations, the
Control File is transferred following the Data File. Thus much of
the information concerning the job may not be available until the
completion of the data transmission.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> jmJobSubmissionID Mapped to LPR/LPD</span>
The LPR/LPD Receive Data File command contains a parameter which
defines the name of the data file. This name field is structured as
follows:
dfaXXX<host-name> or daXXXX<host-name>
Where XXX or XXXX is the numeric job number assigned by the network
entity submitting the print job to the printer. The recommended
mapping of this name field to jmJobSubmissionID is:
<span class="grey">Bergman Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
octet 1: '9'
octets 2-40: Contains the <host-name> portion of the name field. If
the <host-name> portion is less than 40 octets, the
left-most character in the string shall appear in octet
position 2. Any unused portion of this field shall be
filled with spaces. Otherwise, only the last 39 bytes
shall be included.
octets 41-48: '00000XXX' or '0000XXXX', where XXX or XXXX is the
decimal (ASCII coded) representation of the LPR/LPD job
number.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> jmJobIndex Mapped to LPR/LPD</span>
The job index (jmJobIndex) is assigned by the SNMP job monitoring
agent and is independent of the XXX (or XXXX) index assigned by the
LPR/LPD client. This will allow the SNMP agent to track jobs
received from multiple sources.
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a> Other MIB Objects Mapped to LPR/LPD</span>
MIB Object | LPR/LPD Parameter
------------------------------+----------------------------------------
jmJobKOctetsPerCopyRequested | Number of bytes as defined in the Data
| File
jmJobOwner | Control file command code = P (User Id)
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a> The Attribute Group Mapped to LPD</span>
Other attributes that are applicable, but not defined in this section
such as attributes that map to a vendor unique extension, may also be
included.
MIB attribute | LPR/LPD information | Data type
----------------------+---------------------------------+--------------
jobName | Job Name (notes 1, 2) | Octet String
queueNameRequested | Queue name from the Data File | Octet String
fileName | Source File Name (notes 1, 3) | Octet String
Notes:
------
1. The information is optional in the Control File. The attribute
should be included if present in the Control File.
2. Control file command code = J. If this optional field is omitted
from the control file, then the agent returns the file name
(command code = N), if present.
3. Control file command code = N.
<span class="grey">Bergman Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
<span class="h3"><a class="selflink" id="section-3.0" href="#section-3.0">3.0</a> APPLETALK PROTOCOL</span>
AppleTalk was originally developed as a peer-to-peer network
protocol, as described in configuration 1, for use with Apple
Macintosh computers. Today, print spoolers are also available for
use with Macintosh computer networks that conform to configurations
2/3. In addition, printing with the AppleTalk protocol is supported
from both Windows NT servers and Novell servers also per
configurations 2/3.
The AppleTalk protocol provides very little information that can be
used with the Job Monitoring MIB. The Macintosh print drivers are
able to provide information concerning the user and document name but
imbed this information in the PDL, which is typically PostScript.
The preferred jmJobSubmissionID is constructed from the information
in the PostScript file, as defined in <a href="#section-9.0">section 9.0</a>.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> jmJobSubmissionID Mapped to AppleTalk</span>
An alternative jmJobSubmissionID may be constructed from the
Connection Identifier contained in the AppleTalk Printer Access
Protocol (PAP) header. Since the Connection Id is not readily
available in any of the defined AppleTalk implementations, this
approach may be of little utility.
octet 1: 'A'
octets 2-40: Contains the AppleTalk printer name, with the first
character of the name in octet 2. AppleTalk printer
names are a maximum of 31 characters. Any unused
portion of this field shall be filled with spaces.
octets 41-48: '00000XXX', where 'XXX' is the decimal (ASCII coded)
representation of the Connection Id.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> Other AppleTalk Mappings</span>
No other Job MIB objects or parameters can be derived from
information available in the AppleTalk headers
<span class="h3"><a class="selflink" id="section-4.0" href="#section-4.0">4.0</a> INTERNET PRINTING PROTOCOL (IPP)</span>
The Internet Printing Protocol [<a href="#ref-IPP" title=""The Internet Printing Protocol/1.0: Model and Semantics"">IPP</a>] supports printing using any one
of the three possible configurations. For configuration 2, the
mapping defined herein is performed on an agent within the server.
Otherwise, the mapping is performed on an agent within the printer.
<span class="grey">Bergman Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> jmJobSubmissionID Mapped to IPP</span>
IPP contains a rich set of parameters which allow several methods of
creating the jmJobSubmissionID object. To prevent interoperability
problems, the preferred method is to use the IPP job-uri attribute as
follows:
octet 1: '4'
octets 2-40: Contains the IPP job-uri job description attribute
generated by the printer. (The job-uri is returned to
the client by IPP.) If the job-uri is less than 40
octets, the left-most character in the string shall
appear in octet position 2. Any unused portion of this
field shall be filled with spaces. Otherwise, only the
last 39 bytes shall be included.
octets 41-48: Contains the decimal (ASCII coded) representation of
the job-id job description attribute. Leading zeros
shall be inserted to fill the entire 8 octet field.
NOTE - Since IPP returns the "job-identifier" attribute with the
jmJobIndex value for a job when the job is submitted, the use of the
jmJobSubmissionID table should not be needed by a management
application. See <a href="#section-1.0">Section 1.0</a>.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> jmJobIndex Mapped to IPP</span>
The job index (jmJobIndex) assigned by the SNMP job monitoring agent
is returned to the client by IPP as the job-id job description
attribute. (Since IPP does not require consecutively generated job-
ids, the agent may receive jobs from multiple clients and can assign
jmJobIndex in an ascending sequence independent of the submitting job
client.) The IPP job-id must be restricted to the range of 1 to
99,999,999 (decimal) to allow the value to be properly represented in
jmJobSubmissionID.
<span class="grey">Bergman Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a> Other MIB Objects Mapped to IPP</span>
MIB Object | IPP Job attribute
---------------------------------+-----------------------------------
jmJobState | job-state
jmJobStateReasons1 | job-state-reasons (note 1)
jmNumberOfInterveningJobs | number-of-intervening-jobs
jmJobKOctetsPerCopyRequested | job-k-octets
jmJobKOctetsProcessed | job-k-octets-processed
jmJobImpressionsPerCopyRequested | job-impressions
jmJobImpressionsCompleted | job-impressions-completed
jmJobOwner | job-originating-user-name
Notes:
------
1. jmJobStateReasons1 is a bit map which can describe up to 31 job
state reasons. Also the IPP "job-state-reasons" attribute is a
multi-valued attribute with each value being a keyword. The IPP
condition may change multiple bits in this object. The IPP "job-
state-reasons" attribute may also change one or more of the
jobStateReasonsN attributes (see <a href="#section-4.4">section 4.4</a>).
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a> The Attribute Group Mapped to IPP</span>
The following mappings are required if the listed IPP job template
attribute is provided.
<span class="grey">Bergman Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
MIB attribute | IPP job attribute | Data type
---------------------------+------------------------------+-------------
jobStateReasonsN(N=2, 3, 4)| job-state-reasons (note 3) | Integer
jobCodedCharSet | attributes-charset (note 1) | Octet String
jobNaturalLanguageTag | attributes-natural-language | Octet String
jobURI | job-uri | Octet String
jobName | job-name | Octet String
physicalDevice | output-device-assigned | Octet String
numberOfDocuments | number-of-documents | Integer
jobPriority | job-priority | Integer
jobHoldUntil | job-hold-until | Octet String
sides | sides (note 2) | Integer
finishing | finishings | Integer
printQualityRequested | print-quality | Integer
printerResolutionRequested | printer-resolution | Integer
jobCopiesRequested | copies (note 4) | Integer
documentCopiesRequested | copies (note 4) | Integer
jobCollationType | multiple-document-handling | Integer
sheetsRequested | job-media-sheets | Integer
sheetsCompleted | job-media-sheets-completed | Integer
mediumRequested | media | Octet String
jobSubmissionTime | time-at-submission | Integer
jobStartedProcessingTime | time-at-processing | Integer
jobCompletionTime | time-at-completed | Integer
Notes:
------
1. jobCodedCharSet is an enum from the IANA registry which is also
used in the Printer MIB. The IPP attributes-charset is the name
(MIME preferred name) of the character set.
2. The Job MIB sides attribute uses the integer values "1" and "2".
The IPP sides attribute uses three keywords.
3. jobStateReasonsN are three attributes (N=2, 3, 4). Also the IPP
"job-state-reasons" attribute is a multi-valued attribute with
each value being a keyword. The IPP condition may change multiple
bits in one or more of these Job MIB attributes. See also
jmJobStateReasons1 in <a href="#section-4.3">section 4.3</a>.
4. The IPP "copies" attribute maps to the Job MIB:
(1) jobCopiesRequested when the job has only one document OR IPP
"multiple-document-handling" is 'single-valued'
(2) documentCopiesRequested, in which case the MIB value is the
total number of document copies that the job will produce as a
whole.
<span class="grey">Bergman Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
<span class="h3"><a class="selflink" id="section-5.0" href="#section-5.0">5.0</a> INTELLIGENT PRINTER DATA STREAM (IPDS)</span>
The IPDS datastream facilitates a close relationship between the
print supervisor (Print Services Facility - PSF) and the printer.
There are PSF applications for UNIX, Windows, OS/2, OS/400 and host
operating systems such as VM, MVS and VSE. Together, PSF and IPDS
represent a complete, mature and robust job management framework
which includes font and resource management, page progress tracking,
job cancellation, complete error recovery and end-user notification.
Because PSF and the printer correspond via the use of locally
assigned IDs, there is a limited amount of clear text information
provided during submission for use by the Job MIB.
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a> jmJobSubmissionId Mapped to IPDS</span>
For IPDS on the MVS or VSE platform:
octet 1: 'E'
octets 2-40: Contains bytes 2-27 of the XOH Define Group Boundary
Group ID triplet. Octet position 2 must carry the
value x'01'. Bytes 28-40 must be filled with spaces.
octets 41-48: Contains a decimal (ASCII coded) representation of the
jmJobIndex assigned by the agent. Leading zeros shall
be inserted to fill the entire 8 octet field.
For IPDS on the VM platform:
octet 1: 'F'
octets 2-40: Contains bytes 2-31 of the XOH Define Group Boundary
Group ID triplet. Octet position 2 must carry the
value x'02'. Bytes 32-40 must be filled with spaces.
octets 41-48: Contains a decimal (ASCII coded) representation of the
jmJobIndex assigned by the agent. Leading zeros shall
be inserted to fill the entire 8 octet field.
For IPDS on the OS/400 platform:
octet 1: 'G'
octets 2-40: Contains bytes 2-36 of the XOH Define Group Boundary
Group ID triplet. Octet position 2 must carry the
value x'03'. Bytes 37-40 must be filled with spaces.
<span class="grey">Bergman Informational [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
octets 41-48: Contains a decimal (ASCII coded) representation of the
jmJobIndex assigned by the agent. Leading zeros shall
be inserted to fill the entire 8 octet field.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a> The Attribute Group Mapped to IPDS</span>
For MVS/VSE:
MIB attribute | IPDS XOH DGB Group ID | Data type
----------------------------------+-----------------------+-------------
jobSourcePlatformType sptMVS(7) | Byte 2 = x'01' | Integer
jobName | Bytes 4-11 | Octet String
For VM:
MIB attribute | IPDS XOH DGB Group ID | Data type
----------------------------------+-----------------------+-------------
jobSourcePlatformType sptVM(8) | Byte 2 = x'02' | Integer
fileName | Bytes 4-11 | Octet String
For OS/400:
MIB attribute | IPDS XOH DGB Group ID | Data type
----------------------------------+-----------------------+-------------
jobSourcePlatformType sptOS400(9) | byte 2 = x'03' | Integer
fileName | Bytes 23-32 | Octet String
jobName | Bytes 37-46 | Octet String
<span class="h3"><a class="selflink" id="section-6.0" href="#section-6.0">6.0</a> DOCUMENT PRINTING APPLICATION (DPA)</span>
The ISO 10175 Document Printing Application (DPA) [<a href="#ref-DPA" title=""Information technology - Text and office systems - Document Printing Application (DPA) - Part 1: Abstract service definition and procedures"">DPA</a>] supports
printing using any one of the three possible configurations. For
configuration 2, the mapping defined herein is performed on a server.
Otherwise, the mapping is performed on an agent within the printer.
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a> jmJobSubmissionID Mapped to DPA</span>
DPA contains a rich set of parameters which allow several methods of
creating the jmJobSubmissionID object. To prevent interoperability
problems, the preferred method is to use the DPA job-owner attribute
as follows:
<span class="grey">Bergman Informational [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
octet 1: '0'
octets 2-40: Contains the DPA job-owner attribute supplied by the
submitter. If the job-owner is less than 40 octets,
the left-most character in the string shall appear in
octet position 2. Any unused portion of this field
shall be filled with spaces. Otherwise, only the last
39 bytes shall be included.
octets 41-48: Contains an 8-digit sequential decimal number.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a> jmJobIndex Mapped to DPA</span>
The job index (jmJobIndex) assigned by the SNMP job monitoring agent
is returned to the client by DPA as a decimal digit string as the
value of the DPA job-identifier attribute. (Since DPA does not
require consecutively generated job-identifiers, the agent may
receive jobs from multiple clients and can assign the jmJobIndex in
an ascending sequence independent of the submitting job client.) The
DPA job-identifier must be restricted to the range of 1 to 99,999,999
(decimal) to allow the value to be properly represented in
jmJobSubmissionID.
NOTE - Since DPA returns the "job-identifier" attribute with the
jmJobIndex value for a job when the job is submitted, the use of the
jmJobSubmissionID table should not be needed by a management
application. See <a href="#section-1.0">Section 1.0</a>.
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a> Other MIB Objects Mapped to DPA</span>
MIB Object | DPA Job attribute
---------------------------------+------------------------------------
jmJobState | job-state
jmJobStateReasons1 | job-state-reasons (note 2)
jmNumberOfInterveningJobs | intervening-jobs
jmJobKOctetsPerCopyRequested | total-job-octets (notes 1, 3)
jmJobKOctetsProcessed | job-octets-completed (note 1)
jmJobImpressionsPerCopyRequested | job-impression-count (note 3)
jmJobImpressionsCompleted | impressions-completed
jmJobOwner | job-owner
Notes:
------
1. jmJobKOctetsPerCopyRequested and jmJobKOctetsProcessed is in K
octets while the DPA job-total-octets and job-octets-completed is
in octets and is 63-bits of significance.
<span class="grey">Bergman Informational [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
2. jmJobStateReasons1 is a bit map which can describe up to 31 job
state reasons. Also the DPA "job-state-reasons" attribute is a
multi-valued attribute with each value being an object identifier
(OID). The DPA condition may change multiple bits in this object.
The DPA condition may also change one or more of the
jobStateReasonsN attributes (see <a href="#section-4.4">section 4.4</a>)
3. DPA octets include the multiplication factor due to job and
document copies, while the MIB values do not.
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a> The Attribute Group Mapped to DPA</span>
The following mappings are required if the listed DPA job attribute
is provided.
MIB attribute | DPA job attribute |IPP Data type
---------------------------+------------------------------+-------------
jobStateReasonsN(N=2, 3, 4)| job-state-reasons (note 2) | Integer
jobCodedCharSet | (note 1) | Octet String
jobAccountName | accounting-information | Octet String
jobName | job-name | Octet String
deviceNameRequested | printer-name-requested | Octet String
physicalDevice | printers-assigned | Octet String
numberOfDocuments | number-of-documents | Integer
fileName | file-name | Octet String
documentName | document-name | Octet String
jobComment | job-comment | Octet String
documentFormat | document-format | Octet String
jobPriority | job-priority | Integer
jobProcessAfterDateAndTime | job-print-after | Octet String
outputBin | results-profile.output-bin | Octet String
sides | sides (note 3) | Integer
finishing | job-finishing, finishing | Integer
printQualityRequested | print-quality | Integer
printerResolutionRequested | default-printer-resolution | Integer
| (note 4) |
jobCopiesRequested | results-profile.job-copies | Integer
jobCopiesCompleted | job-copies-completed | Integer
documentCopiesRequested | copy-count (note 5) | Integer
documentCopiesCompleted | copies-completed (note 6) | Integer
sheetsRequested | job-media-sheet-count | Integer
sheetsCompleted | job-media-sheets-completed | Integer
pagesRequested | job-page-count | Integer
pagesCompleted | pages-completed | Integer
mediumRequested | page-media-select, | Octet String
| default-medium |
jobSubmissionTime | submission-time (note 7) | Octet String
jobStartedProcessingTime | started-printing-time (note 7) Octet String
jobCompletionTime | completion-time (note 7) | Octet String
<span class="grey">Bergman Informational [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
Notes:
------
1. Every DPA attribute is tagged indicating the coded character set
to be used for that attribute.
2. jobStateReasonsN are three attributes (N=2, 3, 4). The DPA
condition may change one or more of the bits in one or more of
these Job MIB items. Also the DPA job-state-reasons is a multi-
valued attribute with each value being an OBJECT IDENTIFIER (OID).
3. The Job MIB sides attribute is an integer '1' or '2' while the DPA
sides attribute has one of six OID values that includes plex.
4. printerResolutionRequested has x and y resolution and is intended
to override the resolution instruction in the document, if any,
while the DPA default-printer-resolution is the same in x and y
and only takes effect if the document does not contain a
resolution instruction
5. The DPA "copy-count" attribute is a per-document attribute, so the
MIB value is the sum of the documents' "copy-count" values times
the job's "results-profile.job-copies" value.
6. The DPA "copies-completed" attribute is a per-document attribute,
so the MIB value is the sum of the documents' "copies-completed"
values times the job's "results-profile.job-copies" value.
7. The DPA GeneratlizedTime data type is defined by ISO 8824 (ISO-
8824) while the MIB DateAndTime is defined by SNMPv2-TC (SNMPv2-
TC).
<span class="h3"><a class="selflink" id="section-7.0" href="#section-7.0">7.0</a> NOVELL DISTRIBUTED PRINT SERVICE (NDPS)</span>
Novell Distributed Print Services is a DPA based job submission
protocol that conforms to configuration 3.
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a> jmJobSubmissionID Mapped to NDPS</span>
NDPS supports the generation of a properly formatted
jmJobSubmissionID for use in the Job MIB, via the attribute ndps-
att-job-identifier.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a> jmJobIndex Mapped to NDPS</span>
NDPS defines the attribute ndps-att-job-identifier-on-printer that
can be used to return the value of jmJobIndex to the NDPS client. See
<a href="#section-1.0">Section 1.0</a>.
<span class="grey">Bergman Informational [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
<span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a> Other MIB Objects Mapped to NDPS</span>
MIB Object | NDPS Parameter
---------------------------------+--------------------------------------
jmJobState | ndps-att-current-job-state (note 1)
jmJobStateReasons1 | ndps-att-job-state-reasons (note 2)
jmNumberOfInterveningJobs | ndps-att-intervening-jobs
jmJobKOctetsPerCopyRequested | ndps-att-total-job-octets (notes 3,4)
jmJobKOctetsProcessed | ndps-att-octets-completed (note 3)
jmJobImpressionsPerCopyRequested | ndps-att-job-impressions-count
jmJobImpressionsCompleted | ndps-att-impressions-completed
jmJobOwner | ndps-att-job-owner (note 5)
Notes:
------
1. Some of the NDPS job states must be represented by both a
jmJobState and a jmJobStateReasons1 object or a jobStateReasonsN
attribute (N=2, 3, 4).
2. The NDPS job state reasons may be mapped to either the object
jmJobStateReasons1 or the attribute jobStateReasonsN (N=2, 3, 4).
3. jmJobKOctetsPerCopyRequested and jmJobKOctetsProcessed is in K
octets while the NDPS ndps-att-job-total-octets and ndps-att-job-
octets-completed is in octets and is 63-bits of significance.
4. NDPS octets include the multiplication factor due to job and
document copies, while the MIB values do not.
5. The Job MIB object must be multiplied by the attribute
jobCopiesRequested to obtain the NDPS attribute value, if multiple
copies have been requested.
<span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a> The Attribute Group Mapped to NDPS</span>
The following mappings are required if the listed PJL attribute or
command option is provided.
<span class="grey">Bergman Informational [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
MIB attribute | NDPS parameter | Data type
---------------------------+------------------------------+-------------
jobStateReasonsN(N=2, 3, 4)| ndps-job-state-reasons | Integer
jobAccountName | ndps-att-job-owner | Octet String
jobName | ndps-att-job-name | Octet String
jobOriginatingHost | ndps-att-job-originator | Octet String
deviceNameRequested | ndps-att-printer-name-- | Octet String
| requested |
numberOfDocuments | ndps-att-number-of-documents | Integer
fileName | ndps-att-document-file-name | Octet String
documentName | ndps-att-document-name | Octet String
jobComment | ndps-att-job-comment | Octet String
documentFormatIndex | ndps-att-prtInterpreterIndex | Integer
documentFormat | ndps-att-document-format | Integer
jobPriority | ndps-att-job-priority | Integer
jobProcessAfterDateAndTime | ndps-att-job-print-after | Octet String
outputBin | ndps-att-results-profile | Integer
| (note 1) |
sides | ndps-att-sides (note 2) | Integer
finishing | ndps-att-job-finishing | Integer
printQualityRequested | ndps-att-print-quality | Integer
printerResolutionRequested | ndps-att-default-printer-- |
| resolution (note 3) | Integer
printerResolutionUsed | ndps-att-default-resolutions--
| used | Integer
jobCopiesRequested | ndps-att-results-profile | Integer
| (note 4) |
jobCopiesCompleted | ndps-att-job-copies-completed| Integer
documentCopiesRequested | ndps-att-copy-count (note 5) | Integer
documentCopiesCompleted | ndps-att-copies-completed | Integer
| (note 6) |
sheetsRequested | ndps-att-job-media-- |
| sheet-count | Integer
sheetsCompleted | ndps-att-media-sheets-- |
| completed | Integer
mediumConsumed | ndps-att-media-used | Integer
jobSubmissionToServerTime | ndps-att-submission-time | Octet String
| (note 7) |
jobSubmissionTime | ndps-att-started-printing-time Octet String
| (note 7) |
jobCompletionTime | ndps-att-completion-time | Octet String
| (note 7) |
Notes:
------
1. The output-bin field in ndps-att-results-profile is to be used.
2. The Job MIB sides attribute is an integer '1' or '2' while the
NDPS sides attribute has one of six OID values that includes plex.
<span class="grey">Bergman Informational [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
3. printerResolutionRequested has x and y resolution and is intended
to override the resolution instruction in the document, if any,
while the ndps-att-default-printer-resolution is the same in x and
y and only takes effect if the document does not contain a
resolution instruction
4. The job-copies field in ndps-att-results-profile is to be used.
5. The NDPS "copy-count" attribute is a per-document attribute, so
the MIB value is the sum of the documents' "copy-count" values
times the job's "results-profile.job-copies" value.
6. The NDPS "copies-completed" attribute is a per-document attribute,
so the MIB value is the sum of the documents' "copies-completed"
values times the job's "results-profile.job-copies" value.
7. The NDPS GeneratlizedTime data type is defined by ISO 8824 (ISO-
8824) while the MIB DateAndTime is defined by SNMPv2-TC (SNMPv2-
TC).
<span class="h3"><a class="selflink" id="section-8.0" href="#section-8.0">8.0</a> PRINTER JOB LANGUAGE (PJL)</span>
PJL [<a href="#ref-PJL">PJL</a>] has been developed by Hewlett-Packard to provide job
control information to the printer and status information to
applications, independent of the PDL.
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a> jmJobSubmissionID Mapped to PJL</span>
PJL has defined the SUBMISSIONID option for the JOB command which
indicates a properly formatted jmJobSubmissionID for use in the Job
MIB. The PJL JOB command is presented at the start of a print job
with options that apply only the attached job. The syntax for this
command option is:
@PJL JOB SUBMISSIONID = "id string"
Driver software that implements this PJL command option must provide
the "id string" in one of the client version formats specified in the
Job MIB for jmJobSubmissionID.
For drivers that are not able to create the SUBMISSIONID option, it
is recommended that jmJobSubmissionID format 0 be created by the
agent using the PJL attribute DocOwner or DocOwnerId.
octet 1: '0'
octets 2-40: Contains the string associated with DocOwner or
DocOwnerId. If the string is less than 40 octets, the
left-most character in the string shall appear in octet
<span class="grey">Bergman Informational [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
position 2. Otherwise, only the last 39 bytes shall be
included. Any unused portion of this field shall be
filled with spaces. If DocOwner or DocOwnerId cannot
be obtained, this field shall be blank.
octets 41-48: Contains the value of jmJobIndex associated with the
job. Leading zeros shall be inserted to fill the
entire 8 octet field.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a> jmJobIndex Mapped to PJL</span>
PJL does not provide a value that can be mapped to jmJobIndex.
<span class="h3"><a class="selflink" id="section-8.3" href="#section-8.3">8.3</a> Other MIB Objects Mapped to PJL</span>
MIB Object | PJL Job attribute
----------------------+------------------------------------
jobOwner | DocOwner or DocOwnerId attribute
<span class="h3"><a class="selflink" id="section-8.4" href="#section-8.4">8.4</a> The Attribute Group Mapped to PJL</span>
The following mappings are required if the listed PJL attribute or
command option is provided.
MIB attribute | PJL attribute or command option | Data type
----------------------+----------------------------------+--------------
serverAssignedJobName | DocName attribute or the command | Octet String
| @PJL JOB Name = "string" | Octet String
submittingServerName | SrcServerName attribute | Octet String
jobOriginatingHost | SrcPort attribute | Octet String
queueNameRequested | SrcQ attribute | Octet String
fileName | JobFName attribute | Octet String
jobComment | JobDesc attribute | Octet String
jobSubmissionTime | TimeSubmit attribute | Octet String
<span class="h3"><a class="selflink" id="section-9.0" href="#section-9.0">9.0</a> POSTSCRIPT</span>
The PostScript PDL permits comment fields which can be used by
application drivers to include job information. Although there are
no restrictions or requirements as to what information may be
included, many drivers include job owner and/or document name.
<span class="grey">Bergman Informational [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a> jmJobSubmissionID Mapped to PostScript</span>
The use of a standard format job submission id comment string will
allow interoperability of printers and drivers from multiple vendors.
The following comment string format is recommended for use with
PostScript level 1 and level 2 data streams.
%%JMPJobSubmissionId:(id-string)
where "id string" can be any jmJobSubmissionID format reserved for
clients.
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a> Other MIB Objects and Attributes Mapped to PostScript</span>
No Other mappings from PostScript comment strings are recommended,
but many Job MIB objects and attributes can be defined using vendor
unique comment strings.
<span class="h3"><a class="selflink" id="section-10.0" href="#section-10.0">10.0</a> NETWARE PSERVER</span>
The NetWare PServer job submission protocol is implemented in a
client- server-printer system on the server to printer link as
defined in configuration 3.
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a> jmJobSubmissionID Mapped to PServer</span>
octet 1: 'B'
octets 2-40: Contains the Directory Path Name of the agent as
recorded by the Novell File Server in the queue
directory. If the string is less than 40 octets, the
left-most character in the string shall appear in octet
position 2. Otherwise, only the last 39 bytes shall be
included. Any unused portion of this field shall be
filled with spaces.
octets 41-48: '000XXXXX' The decimal (ASCII coded) representation
of the Job Number as per the NetWare File Server Queue
Management Services.
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a> jmJobIndex Mapped to PServer</span>
The job index (jmJobIndex) is assigned by the SNMP job monitoring
agent and is independent of the Job Number assigned by the NetWare
File Server Queue Management Services. This will allow the SNMP
agent to track jobs received from multiple sources.
<span class="grey">Bergman Informational [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
<span class="h3"><a class="selflink" id="section-10.3" href="#section-10.3">10.3</a> Other MIB Objects Mapped to PJL</span>
MIB Object | PServer Job attribute
----------------------+--------------------------------------------
jobOwner | Client Id Number
<span class="h3"><a class="selflink" id="section-10.4" href="#section-10.4">10.4</a> The Attribute Group Mapped to PServer</span>
The following mappings are required if the listed PServer parameter
is provided in the Novell File Server queue directory.
MIB attribute | PServer parameter | Data type
---------------------------+-----------------------------+--------------
serverAssignedJobName | Job File Name | Octet String
queueNameRequested | Queue Id | Integer
physicalDevice | Server Id Number | Integer
jobComment | Job Description | Octet String
jobPriority | (note 1) | Integer
jobProcessAfterDateAndTime | Target Execution Time | Octet String
jobCopiesRequested | Number of Copies | Integer
mediumRequested | Form Name | Octet String
jobSubmissionToServerTime | Job Entry Time | Octet String
Notes:
------
1. The job priority is determined by the priority assigned to the
queue that contains the job. Each queue can be assigned a unique
priority and the priority of the job is inherited from the queue.
<span class="h3"><a class="selflink" id="section-11.0" href="#section-11.0">11.0</a> NETWARE NPRINTER or RPRINTER</span>
The NetWare NPrinter/RPrinter protocol was designed to transfer print
data from a Novell File Server to a printer attached directly to a
local port (e.g. parallel or serial) on a PC. NPrinter/RPrinter is
an extremely lightweight printing protocol. Consequently, no
information required by the Job Monitoring MIB is provided and a
meaningful jmJobSubmissionID cannot be generated.
It is recommended that an additional job submission layer, such as
PJL or another vendor private protocol, be included on top of
NPrinter/RPrinter to provide the required information. The mapping
should then be performed according to the recommendations of the
higher layer submission protocol.
<span class="grey">Bergman Informational [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
<span class="h3"><a class="selflink" id="section-12.0" href="#section-12.0">12.0</a> SERVER MESSAGE BLOCK (SMB) PROTOCOL</span>
The Server Message Block protocol is used with several PC Network
operating systems, such as Microsoft Windows for Workgroups, IBM LAN
Server, and Artisoft Lantastic. SMB systems supporting the Job
Monitoring MIB will conform to either configuration 1 or 3.
<span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a> jmJobSubmissionID Mapped to SMB</span>
octet 1: 'C'
octets 2-40: Contains a decimal (ASCII coded) representation of the
16 bit SMB Tree Id field, which uniquely identifies the
connection that submitted the job to the printer. The
most significant digit of the numeric string shall be
placed in octet position 2. All unused portions of
this field shall be filled with spaces. The SMB Tree
Id has a maximum value of 65,535.
octets 41-48: Contains a decimal (ASCII coded) representation of the
File Handle returned from the printer agent to the
client in response to a Create Print File command.
Leading zeros shall be inserted to fill the entire 8
octet field.
<span class="h3"><a class="selflink" id="section-12.2" href="#section-12.2">12.2</a> jmJobIndex Mapped to SMB</span>
It is strongly recommended that the File Handle returned from the
printer agent be identical to jmJobIndex. If these items are
identical, there is no need for the client application to perform a
search on jmJobSubmissionID. To be compatible with the 16 bit field
allocated to this value by SMB, the maximum jmJobIndex is 65,535.
<span class="h3"><a class="selflink" id="section-12.3" href="#section-12.3">12.3</a> Other MIB objects Mapped to SMB</span>
MIB Object | SMB Parameter
----------------+------------------------------------------------
jmJobOwner | SMB User Id field (note 1)
Notes:
------
1. A decimal (ASCII coded) representation of the SMB User Id numeric
shall be presented as jmJobOwner.
<span class="grey">Bergman Informational [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
<span class="h3"><a class="selflink" id="section-13.0" href="#section-13.0">13.0</a> TRANSPORT INDEPENDENT PRINTER/SYSTEM INTERFACE (TIP/SI)</span>
The TIP/SI protocol, although currently specified as a part of the
IEEE 1284 parallel port standards [TIP/SI], was originally developed
as a network protocol. TIP/SI thus has the potential of being
integrated into any network or non-network configuration.
<span class="h3"><a class="selflink" id="section-13.1" href="#section-13.1">13.1</a> jmJobSubmissionID Mapped to TIP/SI</span>
octet 1: 'D'
octets 2-40: Contains the Job Name from the Job Control-Start Job
(JC-SJ) command. If the Job Name portion is less than
40 octets, the left-most character in the string shall
appear in octet position 2. Any unused portion of this
field shall be filled with spaces. Otherwise, only the
last 39 bytes shall be included.
octets 41-48: Contains a decimal (ASCII coded) representation of the
jmJobIndex assigned by the agent. Leading zeros shall
be inserted to fill the entire 8 octet field.
<span class="h3"><a class="selflink" id="section-13.2" href="#section-13.2">13.2</a> jmJobIndex Mapped to TIP/SI</span>
jmJobIndex is returned to the client as the Printer Assigned Job Id
in a Job Control-Start Job (JC-SJ) response packet. To be compatible
with the 16 bit field allocated to this value by TIP/SI, the maximum
jmJobIndex is 65,535.
<span class="h3"><a class="selflink" id="section-13.3" href="#section-13.3">13.3</a> Other MIB Objects Mapped to TIP/SI</span>
MIB Object | TIP/SI Parameter
-----------------------+---------------------------------------------
jmJobOwner | User string
<span class="h3"><a class="selflink" id="section-13.4" href="#section-13.4">13.4</a> The Attribute Group Mapped to TIP/SI</span>
MIB attribute | TIP/SI information | Data type
----------------------+---------------------------------+-------------
jobName | Job Name string | Octet String
jobComment | Additional Information string | Octet String
<span class="grey">Bergman Informational [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
<span class="h3"><a class="selflink" id="section-14.0" href="#section-14.0">14.0</a> Security Considerations</span>
This document provides mapping recommendations of job submission
protocols for use with the Job Monitoring MIB. The mapping procedures
defined do not enhance or compromise any security provisions
available within the job submission protocols contained within this
document.
The security considerations specified for the Job Monitoring MIB
[<a href="#ref-JobMIB" title=""The Job Monitoring MIB - V1.0"">JobMIB</a>] are also unaffected by any of the recommendations in this
document.
The security provisions available in the job submission protocols are
documented in the appropriate specifications that define the
protocols. The degree of security available varies from very good,
for protocols such as the Internet Printing Protocol [<a href="#ref-IPP" title=""The Internet Printing Protocol/1.0: Model and Semantics"">IPP</a>], to non-
existent, for example the Line Printer Daemon Protocol [<a href="#ref-LPD" title=""Line Printer Daemon Protocol"">LPD</a>].
Since the defined mapping operation occurs as a secondary operation
after the user has been authenticated and there is no storage of any
authorization credentials other than the user name, no security
breaches are anticipated. Also, the Job MIB does not provide any
back-door mechanism for access to any other security parameters.
However, implementers must always consider the impact of the defined
mapping procedures upon the security model desired from the protocol.
<span class="h3"><a class="selflink" id="section-15.0" href="#section-15.0">15.0</a> REFERENCES</span>
[<a id="ref-DPA">DPA</a>] ISO/IEC 10175-1:1996(E), "Information technology - Text
and office systems - Document Printing Application (DPA)
- Part 1: Abstract service definition and procedures",
JTC1/SC18.
[<a id="ref-IPP">IPP</a>] deBry, R., Hastings, T., Herriot, R., Issaacson, S. and
P. Powell, "The Internet Printing Protocol/1.0: Model
and Semantics", <a href="./rfc2566">RFC 2566</a>, April 1999.
[<a id="ref-ISO-8824">ISO-8824</a>] ISO/IEC 8824:1990, "Information technology - Open
Systems Interconnection - Specification of Abstract
Syntax Notation (ASN.1)".
[<a id="ref-JobMIB">JobMIB</a>] Bergman, R., Hastings, T., Isaacson, S. and H. Lewis,
"The Job Monitoring MIB - V1.0", <a href="./rfc2707">RFC 2707</a>, November
1999.
[<a id="ref-LPD">LPD</a>] McLaughlin, L., "Line Printer Daemon Protocol", <a href="./rfc1179">RFC</a>
<a href="./rfc1179">1179</a>, August 1990.
<span class="grey">Bergman Informational [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
[<a id="ref-PJL">PJL</a>] Printer Job Language Technical Reference Manual,
Hewlett-Packard part number 5021-0328.
[<a id="ref-PrtMIB">PrtMIB</a>] Smith, R., Wright, F., Hastings, T., Zilles, S. and J.
Gyllenskog, "Printer MIB", <a href="./rfc1759">RFC 1759</a>, March 1995.
[<a id="ref-SNMPv2-TC">SNMPv2-TC</a>] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Textual Conventions for SMIv2", STD 58, <a href="./rfc2579">RFC 2579</a>, April
1999.
[TIP/SI] IEEE Standard 1284.1, Transport Independent
Printer/System Interface.
<span class="h3"><a class="selflink" id="section-16.0" href="#section-16.0">16.0</a> Authors' Addresses</span>
This document was created with significant contributions from the
following individuals.
Ron Bergman (Editor)
Dataproducts Corp.
1757 Tapo Canyon Road
Simi Valley, CA 93063-3394
Phone: 805-578-4421
Fax: 805-578-4001
EMail: rbergman@dpc.com
Tom Hastings
Xerox Corporation, ESAE-231
701 S. Aviation Blvd.
El Segundo, CA 90245
Phone: 310-333-6413
Fax: 310-333-5514
EMail: hastings@cp10.es.xerox.com
Scott A. Isaacson
Novell, Inc.
122 E 1700 S
Provo, UT 84606
Phone: 801-861-7366
Fax: 801-861-4025
EMail: scott_isaacson@novell.com
<span class="grey">Bergman Informational [Page 24]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
Harry Lewis
IBM Corporation
6300 Diagonal Hwy
Boulder, CO 80301
Phone: (303) 924-5337
Fax: (303) 924-4662
EMail: harryl@us.ibm.com
Bob Pentecost
Hewlett-Packard Corporation
11311 Chinden Boulevard
Boise, ID 83714
Phone: (208) 396-3312
Fax: (208) 396-4122
EMail: bpenteco@boi.hp.com
Send comments to the printmib WG using the Job Monitoring Project
(JMP) Mailing List: jmp@pwg.org
For further information, access the PWG web page under "JMP":
<a href="http://www.pwg.org/">http://www.pwg.org/</a>
Other Participants:
Chuck Adams - Tektronix
Keith Carter - IBM Corporation
Angelo Caruso - Xerox
Jeff Copeland - QMS
Andy Davidson - Tektronix
Mabry Dozier - QMS
Lee Farrell - Canon
David Kellerman - Northlake Software
Rick Landau - Digital
Jay Martin - Underscore
Ira McDonald - Xerox
Stuart Rowley - Kyocera
Bob Setterbo - Adobe
Gail Songer - EFI
Mike Timperman - Lexmark
William Wagner - DPI/Osicom
Chris Wellens - Interworking Labs
Rob Whittle - Novell
Don Wright - Lexmark
Lloyd Young - Lexmark
<span class="grey">Bergman Informational [Page 25]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
<span class="grey"><a href="./rfc2708">RFC 2708</a> Job Submission Protocol Mapping November 1999</span>
<span class="h2"><a class="selflink" id="section-17" href="#section-17">17</a>. Full Copyright Statement</span>
Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Bergman Informational [Page 26]
</pre>
|
