JBA Users Guide

Xerox Confidential Information
Job Based Accounting

Discrepancies Document
(Part two of the Xerox JBA SDK document package)
JBA SDK Part 2

Version 4.0.7 March , 2007
(Draft)
Products Covered:
DC425/430/432/440
DC 240/255/265, DC 460/470/480/490, WCP 65/75/90
DC 535/545/555, WCP 35/45/55, WCP 165/175
WC (and WCP) 232/238, 245/255, 265/275
WC 4150
Xerox 4110/4590
WCP 32/40C, WCP C2128/C2636/C3545
WC M123/M128, WCP 123/128/133, WC 7132, WC 7228/7235/7245
WC 7655/7665
Xerox Corporation
©2000-2007 by Xerox Corporation. All Rights Reserved.
Copyright protection claimed includes all forms and matters of copyrightable material and information now
allowed by statutory or judicial law or hereinafter granted including without limitation, material generated
from the software programs which are displayed on the screen, such as icons, screen displays, looks, etc.
Printed in the United States of America
Xerox® and all Xerox products mentioned in this publication are trademarks of Xerox Corporation.
Changes are made periodically to this document. Changes, technical inaccuracies, and typographic errors
will be corrected in subsequent editions.
The following terms are trademarks or registered trademarks of other companies in the United States or
other countries or both as follows: Microsoft, Windows, Windows NT; Java, Java Development Kit (JDK),
SUN Microsystems, Inc.
All other products or services mentioned in this publication are the trademarks or service marks of their
respective companies or organizations.
Xerox Confidential Information Attribute Discrepancies - Revision History
Revision History
Date Author Version/Rev Description
10/02/01 Xerox Corporation 1.0/0.1 Initial Release

12/31/01 Xerox Corporation 3.0.3 • 1.4 – updated related documents
• 3.1
- added DC460/470/480 7.0.19.1.504
(Refresh), DC460/470/480/490ST
7.0.19.2.503 (Refresh),
- added DC460/470/480/490ST 7.0.19.5.26
(MFF launch), DC535/545/555ST
0.14.52.0 (Launch and DC535/545/555ST
0.26.32.000 (SMP2)
- Documented a workaround
• 3.2, 3.3
- Added DC460/470/480 7.0.19.1.504
(Refresh), DC460/470/480/490ST
7.0.19.2.503 (Refresh)
- added DC460/470/480/490ST 7.0.19.5.26
0.14.52.0 (Launch and DC535/545/555ST
0.26.32.000 (SMP2)
3.3 - Corrected reference jobs for
added 7.19.05.021, DC535/545/555ST
0.14.52.0 (Launch and DC535/545/555ST
0.26.32.000 (SMP2) .
• 3.4
- added DC460/470/480 7.0.19.1.504 (Refresh),
DC425/432/440ST GENERAL RELEASE
(SV65) and DC425/432/440ST GENERAL
RELEASE 3_21 NASG/DMO: 701P38453
- - Corrected reference jobs for
DC460/470/480/490ST 7.0.19.5.26 (MFF
launch), DC535/545/555ST 0.14.52.0 (Launch
and DC535/545/555ST 0.26.32.000 (SMP2)
• 3.5
- included jobs with login errors in the
discrepancy’s description
- added DC460/470/480 7.0.19.1.504
(Refresh), 7.19.02.503,
DC460/470/480/490ST 7.0.19.5.26 (MFF
launch)
- ,DC425/432/440ST GENERAL RELEASE
(SV65)
- added DC425/432/440ST GENERAL
- clarified reference jobs
- 3.6
Page i Xerox Corporation
i
- Added “Intenet-Receive” to section title

- DC535/545/555ST 0.14.52.0 (Launch . and
DC535/545/555ST 0.26.32.000 (SMP2)
• 3.7 – added DC460/470/480/490ST
7.0.19.2.503 (Refresh),DC460/470/480/490ST
7.0.19.5.26 (MFF launch)
- Corrected reference jobs for
3_21 NASG/DMO: 701P38453
And DC535/545/555ST 0.14.52.0 (Launch
and DC535/545/555ST 0.26.32.000
(SMP2)
• 3.8 – added DC425/432/440ST GENERAL
RELEASE (SV65)
3_21 NASG/DMO: 701P38453
• 3.9
- updated workaround to include reference to
new section (3.21)
RELEASE (SV65), DC425/432/440ST
GENERAL RELEASE 3_21 NASG/DMO:
701P38453
- corrected reference jobs
701P38453
• 3.11 – modified job status from “terminated” to
“deleted” in the discrepancy’s description
3_21 NASG/DMO: 701P38453
• 3.12
– added DC425/432/440ST GENERAL
701P38453
– clarified and corrected reference jobs
701P38453
• 3.15.1
701P38453
– updated reference jobs
• 3.15.2
- removed DC425/432/440ST LAUNCH
from known versions affected

- corrected reference jobs
• 3.17
RELEASE (SV65)
- clarified reference jobs
• 3.18, 3.19
RELEASE (SV65). DC425/432/440ST
701P38453
• added sections 3.21, 3.22, 3.23, 3.24, 3.25
• Appendix A – updated software version tables
to include DC425/432/440ST GENERAL
RELEASE (SV65), DC460/470/480
7.0.19.1.504 (Refresh), DC460/470/480/490ST
7.0.19.2.503 (Refresh),
Page iii Xerox Corporation

iii
05/31/02 Xerox Corporation 3.0.4 1.4 – updated related documents

• 3.1, 3.2, 3.4, 3.5, 3.6
- added DC460/470/480/490ST 7.0.19.4.039
• 3.5, 3.7, 3.8, 3.9, 3.11, 3.12, 3.16, 3.17, 3.18,
3.19, 3.21, 3.23, 3.24, 3.25
- added DC460/470/480/490ST 7.0.19.4.039
• 3.3
- Noted that the discrepancy has been fixed
in DC460/470/480/490ST 7.0.19.4.039
- Removed DC425/432/440ST GENERAL
RELEASE (SV65) from Known Versions
Affected – no such job on
(SV65)
• 3.4
- Removed names of duplicate reference jobs
• 3.11
- Added “Scan-to-Email” to section title
(SV65)
• 3.14 .1
in
• Added section 3.26
10/25/02 Xerox Corporation 3.2.1 • 1.4 – updated related documents

• 3.1, 3.2,
- added 7..19.05.021, DC535/545/555ST
0.14.52.0 (Launch and DC535/545/555ST
0.26.32.000 (SMP2)
• 3.3, 3.4
in DC460/470/480/490ST 7.0.19.5.26
0.14.52.0 (Launch and DC535/545/555ST
0.26.32.000 (SMP2)
• 3..5, 3.9, 3.10, 3.12, 3.13, 3.14, 3.15.1,
3.15.2, 3.18, 3.19, 3.20, 3.22, 3.23, 3.26,
-added DC425/432/440ST GENERAL
• 3..6
- Added “Internet-Receive” to section title
for DC535/545/555ST 0.14.52.0
(Launch and DC535/545/555ST
0.26.32.000 (SMP2) .
• 3..7
-added 7.19.05.021
-Noted that the discrepancy has been fixed in
3_21 NASG/DMO: 701P38453 and
DC535/545/555ST 0.14.52.0 (Launch and
DC535/545/555ST 0.26.32.000 (SMP2).
• 3.8, 3.11
-Noted that the discrepancy has been fixed in
3_21 NASG/DMO: 701P38453.
Appendix A
Updated document Center Software
07/21/03 Xerox Corporation 3.3.1 Summarized Changes For Revision 3.3.1

• Updated device software release reference
naming throughout the document.
• Added discrepancies sections 3.28 – 3.32
• Added new product references for WCP
32/40 and WCP 56/75/90.
• Updated existing discrepancies for newly
added products.

Add device discrepancies for
1) WorkCentre Pro35/45/550.3.28.11 (launch),
2) WorkCentre Pro 35/45/55 3.084.16.000 (sp1)
3) WorkCentre Pro 65/75/90 1.01.02.027 (sp2)
4) WorkCentrePro 32/40 C 0.01.01.10 (sp1)
Page v Xerox Corporation

v

1) “WorkCentrePro 32/40 C 0.1.2.028 (sp2)
Pages 34, 35

“WorkCentrePro 32/40 C 0.001.02.059 (sp2.1)
Sections 3.37, 3.38.3.39.3.40

Add products:
WorkCentrePro 165/175 7.047.33.000
WorkCentrePro 2128/2636/3545C0.001.04.044
WorkCentre Pro 65/75/90 1.001.02.63 (sp2.1)
WorkCentrePro M123/M128 1.202..0 (see the JBA API/SDK
spec for details on this product, discrepancies for this
product are not covered here for this release only.)
Replace the product table and copy the main JBA SDK
document. This saves duplication of table updates and effort.
• Add product software releases for WCP 255

• WCP M123/M128
• Moved all SDK content from the JBA API
specification into this document.
• Version number jump to V4.0.0 to match
API.
• Re named this doc to “Job Based
Accounting SDK Discrepancies Document”.
• Deleted section on attribute deltas from this
spec, material is covered in job attribute
discrepancies
• The attribute Fax-Call-Record block added to

describe that a product does not yet use it.
• Version numbers update for this changed.
• Section added 3.1.1.9
• Previous Limit of 10 lines per set_auth in

section 3.1.1.6 changed to 200 lines at
partner requests and after field data history,
lab testing, and development review
approval.
• Added section 4.4.6 copy duplex to duplex

job does not report the jba-image-block
• Added products: 4110/4590, WC 4150,

Launch and SMP 1 WC 232/238, 245/255,
265/275, WC 7132 WC7228/7235/7245,
WC 7655/7665 (All launch and software
upgrade SMP versions for these products)
• Updated product applicability table.
• JBA API deviations table updated, material
added.
• JBA API deviations for WC 4150 added.
(several pages)
• Sections 4.47 – 4.52 added re: WC 4150
• Updated the entire document for recently
added device data discrepancies.
• Corrected device name prefixes. WCP to WC
• Moved the system attributes version table to
the same location as the job attributes table.
• Appendixes A, B created to better organize
the volume of new information necessary to
capture API version vs First use of attributes
and for the set_config startup algorithm of
use.
• Added description of chucked encoding
problem affecting WC (and WCP) 232/238,
245/255, 265/275 products.
• Update changes for products WC 4150 and

Products WC 7132, WC 7228/7235/7245. This
release also contains JBA API attribute
additions., Refer to the JBA API specification
for a list of new attributes in Version 4.0.7.
REVISION HISTORY..................................................................................................................................I
TABLE OF CONTENTS.............................................................................................................................1
1. INTRODUCTION.....................................................................................................................................1
1.1. AUDIENCE................................................................................................................................................1
1.2. PURPOSE..................................................................................................................................................1
1.3. REFERENCE DOCUMENTS............................................................................................................................1
1.4. ORGANIZATION.........................................................................................................................................1
2. ATTRIBUTE DELTAS.............................................................................................................................2
2.1. JOB ATTRIBUTE DELTAS............................................................................................................................2
3. JBA API DEVIATIONS DETAILED ....................................................................................................9
3.1.1. All Xerox Document Centre Products .........................................................................................9
Page vii Xerox Corporation
vii
3.1.1.1 System Accounting Data Loss Problems..................................................................................9

3.1.1.2 get_acct Job Log Data File Increase .....................................................................................10
3.1.1.3 set_config Attribute Recording Problem................................................................................11
3.1.1.4 Multiple Accounting Servers For Single Document Center Data Loss Problem....................11
3.1.1.5 set_auth, set_config Syntax Error Handling Problem.............................................................11
3.1.1.6 set_auth Sub-Command Problems or Limitations..................................................................11
3.1.1.7 Blank User ID and Account ID Problem................................................................................12
3.1.1.8 Regarding Attributes Accounting Configuration Setup (set_config)......................................13
3.1.1.9 Regarding Job Attribute Support in API V 4.0.2 API Section 6.10.0.2. .........................13
3.1.1.10 Set_config use: Issues Applicable to All Xerox DC/WCP Products..................................14
3.1.2. API Discrepancies Affecting Specific Document Centre or Work Centre or Work Centre Pro
Products.................................................................................................................................................15
3.1.2.1 DC420/425/432/440...............................................................................................................15
3.1.2.2 DC460/470/480/490...............................................................................................................16
3.1.2.3 DC240/255/265......................................................................................................................17
3.1.2.4 WorkCentre Pro 32/40 C, WorkCentre Pro 65/75/90, WorkCentre Pro 35/45/55,
DocumentCentre 460/470/480, DC432/440, DC535/545/555...........................................................17
3.1.2.5 WorkCenter WCP 232/238, 245/255, 265/275265/275 ......................................................19
3.1.2.6 Device does not send responses to data in “chunked” HTTP/HTTPS format .......................20
3.1.2.7 Regarding Work Centre Pro Models that Do not Support Embedded Fax Job Records........21
3.1.2.8 Regarding : WCP 123/128, WC M123/M128, WCP 7228/7235//7245, ..............................23
3.1.2.9 WCP 4150 10.099.05.000 (launch and other releases as marked).........................................26
3.1.2.9.1 Incorrect +u Operation (problem in Launch, and SMP1, and SMP1a releases)............26
3.1.2.9.2 New get_auth Format Not Supported..............................................................................27
3.1.2.9.3 Get_config response contains carriage return line feeds.................................................27
3.1.2.9.4 Set_auth wild card account is not treated as an account..................................................28
3.1.2.9.5 Print Jobs Terminated Before Printing Do Not Create Job Log Enties ..........................28
3.1.2.9.6 Get_auth Command Returns the Stream with incorrect Character Counts embedded in
the stream........................................................................................................................................28
3.1.2.9.7 Get_auth Command Returns Data For All Users, Only One Was Selected...................29
3.1.2.9.8 Postcript Print and WebUI Jobs Uncollated multi set jobs Are Not Recorded In JBA. 29
3.1.2.9.9 JBA Off-Box Authentication Does Not Work In Launch...............................................29
3.1.2.9.10 User Database Upload (set_auth ) fails on 20,000 users and 20,000 accounts if 16
Character User Usernames Used....................................................................................................29
3.1.2.9.11 WC4150 Produces No Accounting Record If The Device Is Powered Off or Looses
Power Prior To the End Of a Job....................................................................................................30
3.1.2.9.12 WC4150 Does Not Record Different Paper Sizes Manually Scanned .........................30
3.1.2.9.13 WC4150 Does Not Record Different Paper Sizes Auto Size Detect Scanned ............30
3.1.2.9.14 WC4150 set_config Data is Sometimes Returned in Response To a “get_acct”
Command........................................................................................................................................31
3.1.2.9.15 WC4150 JBA Mode Disabled Without Warning If HTTP is turned Off On Web UI. 31
4. JOB ATTRIBUTE PROBLEMS IDENTIFIED...................................................................................32
4.1. COVER (BLANK) SHEETS COUNTED AS SIMPLEX SHEETS ..............................................................................32
4.2. IRREGULAR SIZED ORIGINALS MISCOUNTED................................................................................................33
4.3. INCORRECT IMAGES TRANSFERRED COUNT.................................................................................................34
4.4. IMAGES FILED NOT RECORDED.................................................................................................................34
4.5. INCORRECT STATUS FOR SCAN-TO-FILE......................................................................................................35
4.6. INCORRECT IMAGE AND PAGE COUNT FOR INTERNET-RECEIVE......................................................................36
4.7. ACCOUNTING INFORMATION NOT RECORDED..............................................................................................37
4.8. FINISHING NOT RECORDED.......................................................................................................................37
4.9. INCORRECT PAGE & SHEET COUNTS FOR ONE-TO-TWO-SIDED COPYING.......................................................38
4.10. INCORRECT SHEET COUNTS FOR TWO-SIDED PRINTING..............................................................................39
4.11. INCORRECT STATUS FOR CANCELED COPY................................................................................................40
4.12. INPUT SIZES AND PAGE COUNTS NOT RECORDED FOR FAX, SCAN-TO-FILE, AND SCAN-TO-EMAIL ...................41
4.13. INPUT SIZES AND PAGE COUNT ATTRIBUTES MISUSED...............................................................................42
4.14. AMBIGUOUS ATTRIBUTE VALUE FOR FAX.................................................................................................42
4.15. INCORRECT STATUS FOR FAX..................................................................................................................43
4.15.1. Non-working Phone Numbers..................................................................................................43
4.15.2. Working Phone Numbers.........................................................................................................43
4.16. PHONE NUMBER COUNT NOT RECORDED.................................................................................................44
4.17. FAX PHONE NUMBER NOT RECORDED CORRECTLY...................................................................................44
4.18. DUPLICATE JOB IDENTIFIERS...................................................................................................................44
4.19. NUMBER OF PAGES SCANNED NOT RECORDED CORRECTLY........................................................................45
4.20. MAIL RECIPIENTS NOT RECORDED..........................................................................................................46
4.21. MISSING JOB LOG ENTRY......................................................................................................................46
4.22. INCORRECT COPIES COMPLETED COUNT...................................................................................................47
4.23. COPIES COMPLETED NOT RECORDED.......................................................................................................47
4.24. INCORRECT FINISHING VALUE RECORDED.................................................................................................48
4.25. INCORRECT STATUS FOR CANCELED JOBS................................................................................................48
4.26. MULTIPLE JOB LOG ENTRIES RECORDED..................................................................................................49
4.27. SCAN-TO-FILE POLICY ERROR NOT DETECTED..........................................................................................49
4.28. INCORRECT SCAN DIMENSIONS RECORDED................................................................................................50
4.29. DEVICE NAME ATTRIBUTE MISSING .......................................................................................................50
4.30. INCORRECT PRINTED MEDIA TYPE AND COLOR RECORDED ........................................................................51
4.31. INCORRECT COPY COUNT RECORDED FOR PRINT JOBS WITH BANNER SHEETS.............................................52
4.32. FINISHING RECORDED WHEN FINISHING NOT APPLIED ..............................................................................52
4.33. INCORRECT STATUS FOR COMPLETED PRINT JOBS.....................................................................................53
4.34. INCORRECT IMAGE COUNT ON DUPLEX ODD NUMBER OF ORIGINAL PRINT JOBS.........................................54
4.35. INCOMPLETE FILE DESTINATION PATH LOGGED.........................................................................................55
4.36. SIMPLEX PRINTING DOUBLES IMPRESSION COUNTS....................................................................................56
4.38. INCORRECT PRINTING OF DUPLEX PRINT JOBS WITH BLANK COVER SHEETS.................................................56
4.39. MISSING “JBA-IMAGE-BLOCK-N” IN COPY BUILD JOB................................................................................57
4.40. ERROR IN “JBA-IMAGE-BLOCK-N” COUNTS...............................................................................................57
4.41. ERROR IN SIMPLEX PRINT IMAGE COUNTS ..............................................................................................57
4.42. EMBEDDED FAX JOBS INFORMATION IS NOT RECORDED.............................................................................58
4.43. INCORRECT COPY JOB COMPLETED STATUS..............................................................................................59
4.44. INCORRECT MEDIA SIZE RECORDED FOR COPY BUILD JOB........................................................................59
4.45. COPY JOB INCORRECT COLOR IMPRESSIONS..............................................................................................59
4.46. FAX CALL RECORD ATTRIBUTE NOT SUPPORTED........................................................................................60
4.47. MISSING IMAGE BLOCK ATTRIBUTE ON DUPLEX JOBS...............................................................................60
4.48. DUPLEX AND SIMPLEX COUNT ERROR WHEN FRONT COVER SELECTED......................................................61
4.49. SCANNED IMAGES NOT COUNTED AS B&W AND COLOR...........................................................................62
4.50. INCORRECT JOB STATUS FOR SCAN JOB TERMINATED BECAUSE OF FAULT.................................................62
4.51. INCORRECT NUMBER OF COPIES COMPLETED IF JOB ENDS BEFORE FULL COMPLETION................................63
4.52. SCAN TO FILE REPORTS ONLY THE MOST SIGNIFICANT DESTINATION IN JBA-NET-DEST..................................63
SYSTEM ATTRIBUTE PROBLEMS IDENTIFIED.............................................................................64
4.53. ‘AUTHORIZATION-WEB-LOCATION’ PARTLY FUNCTIONAL..............................................................................64
4.54. ‘AUTHORIZATION-WEB-LOCATION’ DEFAULT MODE IS NOT AVAILABLE.........................................................64
4.55. ‘AUTHORIZATION-WEB-SERVER’ ATTRIBUTE AND OFF-BOX MODE IS INOPERATIVE .......................................65
A. DOCUMENT CENTRE SOFTWARE VERSIONS............................................................................66
A.1. PRODUCT APPLICABILITY.........................................................................................................................66
B. DETERMINATION OF DEVICE ATTRIBUTE CAPABILITIES (SET_CONFIG
INITIALIZATION ALGORITHM)...........................................................................................................70
B.1. REGARDING ATTRIBUTES TO USE FOR DOCUMENT CENTRE ACCOUNTING CONFIGURATION SETUP (SET_CONFIG).70
Page ix Xerox Corporation

ix
B.2. JOB ATTRIBUTE FIRST USED IN API VERSION......................................................................................71

B.2.1. Job Attribute Table Listing Of Attribute First Use....................................................................71
B.3. SYSTEM ATTRIBUTE FIRST USED IN API VERSION.....................................................................................72
B.3.1. System Attribute Table Listing Of Attribute First Use..............................................................72
Xerox Confidential Information Attribute Discrepancies - Contents
Table of Contents
REVISION HISTORY..................................................................................................................................I
TABLE OF CONTENTS.............................................................................................................................1
1. INTRODUCTION.....................................................................................................................................1
1.1. AUDIENCE................................................................................................................................................1
1.2. PURPOSE..................................................................................................................................................1
1.3. REFERENCE DOCUMENTS............................................................................................................................1
1.4. ORGANIZATION.........................................................................................................................................1
2. ATTRIBUTE DELTAS.............................................................................................................................2
2.1. JOB ATTRIBUTE DELTAS............................................................................................................................2
3. JBA API DEVIATIONS DETAILED ....................................................................................................9
3.1.1. All Xerox Document Centre Products .........................................................................................9
3.1.1.1 System Accounting Data Loss Problems..................................................................................9
3.1.1.2 get_acct Job Log Data File Increase .....................................................................................10
3.1.1.3 set_config Attribute Recording Problem................................................................................11
3.1.1.4 Multiple Accounting Servers For Single Document Center Data Loss Problem....................11
3.1.1.5 set_auth, set_config Syntax Error Handling Problem.............................................................11
3.1.1.6 set_auth Sub-Command Problems or Limitations..................................................................11
3.1.1.7 Blank User ID and Account ID Problem................................................................................12
3.1.1.8 Regarding Attributes Accounting Configuration Setup (set_config)......................................13
3.1.1.9 Regarding Job Attribute Support in API V 4.0.2 API Section 6.10.0.2. .........................13
3.1.1.10 Set_config use: Issues Applicable to All Xerox DC/WCP Products..................................14
3.1.2. API Discrepancies Affecting Specific Document Centre or Work Centre or Work Centre Pro
Products.................................................................................................................................................15
3.1.2.1 DC420/425/432/440...............................................................................................................15
3.1.2.2 DC460/470/480/490...............................................................................................................16
3.1.2.3 DC240/255/265......................................................................................................................17
3.1.2.4 WorkCentre Pro 32/40 C, WorkCentre Pro 65/75/90, WorkCentre Pro 35/45/55,
DocumentCentre 460/470/480, DC432/440, DC535/545/555...........................................................17
3.1.2.5 WorkCenter WCP 232/238, 245/255, 265/275265/275 ......................................................19
3.1.2.6 Device does not send responses to data in “chunked” HTTP/HTTPS format .......................20
3.1.2.7 Regarding Work Centre Pro Models that Do not Support Embedded Fax Job Records........21
3.1.2.8 Regarding : WCP 123/128, WC M123/M128, WCP 7228/7235//7245, ..............................23
3.1.2.9 WCP 4150 10.099.05.000 (launch and other releases as marked).........................................26
3.1.2.9.1 Incorrect +u Operation (problem in Launch, and SMP1, and SMP1a releases)............26
3.1.2.9.2 New get_auth Format Not Supported..............................................................................27
3.1.2.9.3 Get_config response contains carriage return line feeds.................................................27
3.1.2.9.4 Set_auth wild card account is not treated as an account..................................................28
3.1.2.9.5 Print Jobs Terminated Before Printing Do Not Create Job Log Enties ..........................28
3.1.2.9.6 Get_auth Command Returns the Stream with incorrect Character Counts embedded in
the stream........................................................................................................................................28
3.1.2.9.7 Get_auth Command Returns Data For All Users, Only One Was Selected...................29
3.1.2.9.8 Postcript Print and WebUI Jobs Uncollated multi set jobs Are Not Recorded In JBA. 29
3.1.2.9.9 JBA Off-Box Authentication Does Not Work In Launch...............................................29
11/13/2008 Xerox Corporation Contents 1

3.1.2.9.10 User Database Upload (set_auth ) fails on 20,000 users and 20,000 accounts if 16
Character User Usernames Used....................................................................................................29
3.1.2.9.11 WC4150 Produces No Accounting Record If The Device Is Powered Off or Looses
Power Prior To the End Of a Job....................................................................................................30
3.1.2.9.12 WC4150 Does Not Record Different Paper Sizes Manually Scanned .........................30
3.1.2.9.13 WC4150 Does Not Record Different Paper Sizes Auto Size Detect Scanned ............30
3.1.2.9.14 WC4150 set_config Data is Sometimes Returned in Response To a “get_acct”
Command........................................................................................................................................31
3.1.2.9.15 WC4150 JBA Mode Disabled Without Warning If HTTP is turned Off On Web UI. 31
4. JOB ATTRIBUTE PROBLEMS IDENTIFIED...................................................................................32
4.1. COVER (BLANK) SHEETS COUNTED AS SIMPLEX SHEETS..............................................................................32
4.2. IRREGULAR SIZED ORIGINALS MISCOUNTED................................................................................................33
4.3. INCORRECT IMAGES TRANSFERRED COUNT.................................................................................................34
4.4. IMAGES FILED NOT RECORDED.................................................................................................................34
4.5. INCORRECT STATUS FOR SCAN-TO-FILE......................................................................................................35
4.6. INCORRECT IMAGE AND PAGE COUNT FOR INTERNET-RECEIVE......................................................................36
4.7. ACCOUNTING INFORMATION NOT RECORDED..............................................................................................37
4.8. FINISHING NOT RECORDED.......................................................................................................................37
4.9. INCORRECT PAGE & SHEET COUNTS FOR ONE-TO-TWO-SIDED COPYING.......................................................38
4.10. INCORRECT SHEET COUNTS FOR TWO-SIDED PRINTING..............................................................................39
4.11. INCORRECT STATUS FOR CANCELED COPY................................................................................................40
4.12. INPUT SIZES AND PAGE COUNTS NOT RECORDED FOR FAX, SCAN-TO-FILE, AND SCAN-TO-EMAIL...................41
4.13. INPUT SIZES AND PAGE COUNT ATTRIBUTES MISUSED...............................................................................42
4.14. AMBIGUOUS ATTRIBUTE VALUE FOR FAX.................................................................................................42
4.15. INCORRECT STATUS FOR FAX..................................................................................................................43
4.15.1. Non-working Phone Numbers..................................................................................................43
4.15.2. Working Phone Numbers.........................................................................................................43
4.16. PHONE NUMBER COUNT NOT RECORDED.................................................................................................44
4.17. FAX PHONE NUMBER NOT RECORDED CORRECTLY...................................................................................44
4.18. DUPLICATE JOB IDENTIFIERS...................................................................................................................44
4.19. NUMBER OF PAGES SCANNED NOT RECORDED CORRECTLY........................................................................45
4.20. MAIL RECIPIENTS NOT RECORDED..........................................................................................................46
4.21. MISSING JOB LOG ENTRY......................................................................................................................46
4.22. INCORRECT COPIES COMPLETED COUNT...................................................................................................47
4.23. COPIES COMPLETED NOT RECORDED.......................................................................................................47
4.24. INCORRECT FINISHING VALUE RECORDED.................................................................................................48
4.25. INCORRECT STATUS FOR CANCELED JOBS................................................................................................48
4.26. MULTIPLE JOB LOG ENTRIES RECORDED..................................................................................................49
4.27. SCAN-TO-FILE POLICY ERROR NOT DETECTED..........................................................................................49
4.28. INCORRECT SCAN DIMENSIONS RECORDED................................................................................................50
4.29. DEVICE NAME ATTRIBUTE MISSING .......................................................................................................50
4.30. INCORRECT PRINTED MEDIA TYPE AND COLOR RECORDED ........................................................................51
4.31. INCORRECT COPY COUNT RECORDED FOR PRINT JOBS WITH BANNER SHEETS.............................................52
4.32. FINISHING RECORDED WHEN FINISHING NOT APPLIED ..............................................................................52
4.33. INCORRECT STATUS FOR COMPLETED PRINT JOBS.....................................................................................53
4.34. INCORRECT IMAGE COUNT ON DUPLEX ODD NUMBER OF ORIGINAL PRINT JOBS.........................................54
4.35. INCOMPLETE FILE DESTINATION PATH LOGGED.........................................................................................55
4.36. SIMPLEX PRINTING DOUBLES IMPRESSION COUNTS....................................................................................56
4.38. INCORRECT PRINTING OF DUPLEX PRINT JOBS WITH BLANK COVER SHEETS.................................................56
4.39. MISSING “JBA-IMAGE-BLOCK-N” IN COPY BUILD JOB................................................................................57
4.40. ERROR IN “JBA-IMAGE-BLOCK-N” COUNTS...............................................................................................57
4.41. ERROR IN SIMPLEX PRINT IMAGE COUNTS ..............................................................................................57
11/13/2008
Xerox Corporation Page 2
Xerox Confidential Information Attribute Discrepancies - Contents
4.42. EMBEDDED FAX JOBS INFORMATION IS NOT RECORDED.............................................................................58

4.43. INCORRECT COPY JOB COMPLETED STATUS..............................................................................................59
4.44. INCORRECT MEDIA SIZE RECORDED FOR COPY BUILD JOB........................................................................59
4.45. COPY JOB INCORRECT COLOR IMPRESSIONS..............................................................................................59
4.46. FAX CALL RECORD ATTRIBUTE NOT SUPPORTED........................................................................................60
4.47. MISSING IMAGE BLOCK ATTRIBUTE ON DUPLEX JOBS...............................................................................60
4.48. DUPLEX AND SIMPLEX COUNT ERROR WHEN FRONT COVER SELECTED......................................................61
4.49. SCANNED IMAGES NOT COUNTED AS B&W AND COLOR...........................................................................62
4.50. INCORRECT JOB STATUS FOR SCAN JOB TERMINATED BECAUSE OF FAULT.................................................62
4.51. INCORRECT NUMBER OF COPIES COMPLETED IF JOB ENDS BEFORE FULL COMPLETION................................63
4.52. SCAN TO FILE REPORTS ONLY THE MOST SIGNIFICANT DESTINATION IN JBA-NET-DEST..................................63
SYSTEM ATTRIBUTE PROBLEMS IDENTIFIED.............................................................................64
4.53. ‘AUTHORIZATION-WEB-LOCATION’ PARTLY FUNCTIONAL..............................................................................64
4.54. ‘AUTHORIZATION-WEB-LOCATION’ DEFAULT MODE IS NOT AVAILABLE.........................................................64
4.55. ‘AUTHORIZATION-WEB-SERVER’ ATTRIBUTE AND OFF-BOX MODE IS INOPERATIVE .......................................65
A. DOCUMENT CENTRE SOFTWARE VERSIONS............................................................................66
A.1. PRODUCT APPLICABILITY.........................................................................................................................66
B. DETERMINATION OF DEVICE ATTRIBUTE CAPABILITIES (SET_CONFIG
INITIALIZATION ALGORITHM)...........................................................................................................70
B.1. REGARDING ATTRIBUTES TO USE FOR DOCUMENT CENTRE ACCOUNTING CONFIGURATION SETUP (SET_CONFIG).70
B.2. JOB ATTRIBUTE FIRST USED IN API VERSION......................................................................................71
B.2.1. Job Attribute Table Listing Of Attribute First Use....................................................................71
B.3. SYSTEM ATTRIBUTE FIRST USED IN API VERSION.....................................................................................72
B.3.1. System Attribute Table Listing Of Attribute First Use..............................................................72
11/13/2008 Xerox Corporation Contents 3

Xerox Confidential Information Attribute Discrepancies - Introduction
1.Introduction
1.1.Audience
This document is targeted at developers of accounting applications. Readers are assumed to have a good
understanding of the Job Based Accounting API Specification document
1.2.Purpose
This document details system and job attribute discrepancies across Xerox Devices and provides
workarounds for identified problem discrepancies where applicable.
This document describes known discrepancies with system and job attributes associated with the Xerox Job
Based Accounting API Specification.
1.3.Reference Documents
Related documents include:
Job Based Accounting API Specification (latest version)
1. .
2. .
1.4.Organization
The document is divided into two main subsections.
Section 2, Attribute Deltas provides tables of all attribute names as defined in Appendix A of the SDK/API
specification. Where applicable, table entries contain information on context and use of an attribute.
Section 3 Known Problems details job data differences from those stipulated in Appendix A of document
Job Based Accounting Communication Specification - SDK and API.
11/13/2008
Xerox Confidential Information Attribute Discrepancies - Attribute Deltas
2.Attribute Deltas
2.1.Job Attribute Deltas

Variances of Xerox products with regard to job attributes are shown in the Job Attribute Delta table below.
This table should be used in conjunction with the section 3 of this document titled “Known Problems”.
Attribute Name Description Of Difference Product: Product Version Value Difference

Descriptions
Note: Version / device type
information may be obtained for
Xerox products using SNMP tools
published by Xerox.
accounting- For some job types the DC432, DC440 and DC425 The Configuration
information userID and accountID may (all versions) Report is listed as a
not be the ID of the locally “print” job type and
logged in user but may be the userID and
the system “generic” ID. accountID of these
jobs is
set by the system to
be the generic Ids.
DC240,DC255,DC265,DC460, The Configuration

DC470,DC480,DC490 Report job may use
(all versions). either the logged in
userID or the
generic ID.
jba-device-name
completion-time
11/13/2008
Xerox Confidential information Attribute Discrepancies - Attribute Deltas

Descriptions
job-name
jba-finishing 1) The attribute “jba- 1) DC420/432/440ST SMP2

finishing” is used in version only records jba-
selected products. finishing
finishing
2) The attribute “finishing” 2) DC420/432/440ST
used in selected SMP2.1and DC425 version
products. DC425/432/440ST LAUNCH do
not record either jba-finishing or
the finishing attributes.
jba-completed-
reasons
job-copies-
completed
media-sheets-
completed
11/13/2008

Descriptions
jba-media- 1) Certain products are 1) All Document Centre products 1)Range is limited to
block-1… limited in the number of jba-media-block-1
jba-media-block-N media blocks that can be …jba-media-
recorded per/job. block-6.
2) All Document Centre products 2)The optional jba-

2) Certain products do not
media-block-N
support production of all
attribute value for
of the attribute field
“IMAGE-AREA-
values
SQUARE-IN-MM”
is not supported.
3) API/SDK version 3.3.1. 3)The attribute

content was added
Products:
to: Black and white
WorkCentre Pro 32/40 C and color impression
0.001.00.060 counts added to this
attribute
WorkCentre Pro 65/75/90
1.001.00.60
See also, jba-media-block-N syntax
in Appendix A of the JBA API/SDK
specification.
jba-media-other-
pages
jba-total-simplex-
sheets
jba-total-duplex-
sheets
11/13/2008

Descriptions
jba-image- 1) Certain products are 1) All Document Centre Products 1)Range is limited to
block-1…. jba- limited in the number of jba-image-block-1
image-block-N scan image blocks that …jba-image-block-3
can be recorded per/job.
2)The optional jba-
2) All Document Centre Products
image-block-N value
for “SCAN-TIME-
2) Certain products do not
IN-SECONDS” and
support production of all
“IMAGE-FILE-
of the attribute field
SIZE” is not
values
supported.
3)Black and white

3) In API/SDK version 3.3.1 .
and color image
Products: counts added to this
attributes syntax.
WorkCentre Pro 32/40 C
0.001.00.060
WorkCentre Pro 65/75/90 See jba-image-
1.001.00.60 block-N syntax
jba-image-other-
size
fax-destination-
phone
jba-net-dest-1… Certain products are limited 1) All Document Centre Products The range of jba-
jba-net-dest-N in the number of network net-dest-N is limited
destination blocks that can be to jba-net-dest-1 …
recorded per/job. jba-net-dest-6.
scan-other-pages
11/13/2008

Descriptions
lakes-number-of- Not produced on certain 1) Attribute is not used on Xerox
images products wide format printer products:
8825/8830/8850/8855
job-type For the job type proof-print. DC432, DC440 all versions except
Cover sheets are not DC425/432/440ST LAUNCH
recorded. e.g. No job log (DC425)
entry for this component of a
proof print job.
jba-num-phone-
numbers
job-identiifier
total-number-of- 1. “total-number-of-images- 1. DC490, DC425 all versions.

images-filed filed“ attribute only used
All products using version
on certain products
DC460/470/480/490ST 7.0.19.2.51
or releases
(Launch 490) (19.2) of software.
API/SDK version 3.2.1
lakes-total-images- 2. “lakes-total-images-
filed filed” attribute only used
2. DC480 version DC460/470/480
on certain products.
7.0.19.1.20 and subsequent
prouct versions
total-number-of- Usage of this attribute begins
DC490 and software versions
smtp-recipients on listed products
subsequent to the release
DC460/470/480/490ST 7.0.19.2.51
(Launch 490)
11/13/2008

Descriptions
smtp-recipient-to This will first appear on the DC490 and subsequent versions
products listed.
DC460/470/480/490ST 7.0.19.2.51
(Launch 490) of software
smtp-recipient-cc This will first appear on DC490 and subsequent versions

products listed.
DC460/470/480/490ST 7.0.19.2.51
smtp-recipient-bcc This will first appear on DC490 and subsequent versions

products listed.
DC460/470/480/490ST 7.0.19.2.51
Table 2-1: Job Attribute Delta Table
11/13/2008
11/13/2008
3.JBA API Deviations Detailed

Note: This section concerns API deviations only. This section does not cover the deviations of
job attributes from the JBA API.
3.1.1.All Xerox Document Centre Products

DC420/425/430/432/440
DC 240/255/265, DC 460/470/480/490, WCP 65/75/90
DC 535/545/555, WCP 35/45/55, WCP 165/175
WCP 232/238, 245/255, 265/275
WC 4150
Xerox 4110/4590
WCP 32/40C, WCP C2128/C2636/C3545
WCP 123/128/133, WC 7132, WC 7228/7235/7245
WCP 7655/7665
Note: This section records deviations from the Job Based Accounting SDK/API Specification.
Work-around solutions to noted problems are provided if available. The deviations noted in this
section may be planned for correction in future Xerox product releases. The versions of products
supporting these fixes will be periodically published and will appear in this section.
3.1.1.1System Accounting Data Loss Problems

Note: Exception, the problem defined in this section is not seen on the following devices. These
devices operate according to the API spec:
WCP 123/128/133, WC 7132, WC 7228/7235/7245 and the
and Xerox 4110/4590
In the JBA API section on Purge Request, Purge specifies that job data will be saved on an XD
until it is purged with the Purge command.
There are the following known exceptions to this:
Under certain conditions if the job record size limit is reached (normally this will be 30,000 job
log entries) , if additional ‘walk-up’ jobs such as copy, scan, fax are run at the device, the data
for these jobs will not be recorded.
Problem 1:
In Appendix B of the JBA API Specification, when the accounting job log is full and needs
to be purged” the XD UI displays “Insufficient system resource” and the web UI displays the
message “The server is busy and cannot currently process the request. Please try again later”
The message does not warn the user that the server is full and needs attention.
Note: this problem is corrected on WCP 232/238, 245/255, 265/275 13.027.24.000 (launch)
and on WCP 7655/7665
Work Around The application (EAS) should collect job log data and purge the DC data often
enough to assure that the DC never fills to capacity.
11/13/2008
a) Make sure that a ‘set_config’ command has been used to setup the DC with 15,000 file
entries as per the section on ‘set_config’ in the API section of this specification. After
rebooting the WCP/ DC, verify that set_config worked by checking with a ‘get_config’
command. Examine the attribute value for the attribute: ‘accounting-maximum-log-entry’
to verify that the value is now set. Note: Reboot of the device can be performed remotely
(programmatically) by the EAS application.
b) The system attribute ‘accounting-disable-server-when-log-full’ (see Appendix B)
should be set to ‘TRUE’. This will mean that the DC will not accept new print jobs once
it reaches the 30,000 limit. Note: as per item 1) above, the DC will still run but not
record job data on Copy, Scan Fax and other walk-up jobs.
1) There are two job record data files used to record job data as described in the get_acct Data
Stream Format section of the API spec. In the case where job data is recorded in both files
but not yet collected, data will be automatically purged from the older file when a get_acct is
sent to the DC. Work Around: Although there is no fail safe work around to this problem,
the risk of data loss may be reduce by following these rules:
a) The application (EAS) should always process job data after each get_acct.
b) The application (EAS) should avoid sending two get_acct commands in row. Always
incorporate data and follow each get_acct command with a purge command even if the
device returns no data after the get_acct request.
c) The application (EAS) should poll the job log with get_acct as often as reasonable given
network traffic and server resource usage conditions. Don’t allow job log data to collect
on the DC. Harvest job data on the DC often. Note: there is a planned fix for this
problem however at the time of this writing, (Feb 2004) the fix (SPAR) is only available
on machines termed to be E3.0 SMP2 or later. Contact Xerox for more information about
this problem and possible solutions.
NOTES: (Use the fixes listed in the following section if possible.)
This problem (2 above) is corrected/fixed with SPARs on selected DC and WCP products.
Most fixes listed below became available in March 2004. Products launched after March,
2004 should already contain the fixes. (No need to load SPAR software to fix the problem)
WCP55, SPAR 972325540 - Fixed in x.093.32.003
DC555, SPAR 763310494 Fixed in 27.18.013
DC490, SPAR 541318726 Fixed in 19.5.515
DC440, SPAR 274509716 Fixed in 3_45 ESS 3.2.26_UI 3.84
WCP32/40C, SPAR 083093559 Fixed in WCP 32/40 1.02.059
2) Earlier releases of Document Centre Accounting could lose job log data if a power loss or
power cycle occurred. This was corrected after versions DC 490/480/470 7.19.02.503 and
later. Customers who have accounting should upgrade (if possible) to a software release in
which this problem is fixed. The WC 4150 version 10.099.02.000 (launch release) will loose
job data (auto purge) if power loss occurs prior to the end of a currently running job.
Upgrade the WCP4150 to a post launch version to fix this problem
3.1.1.2get_acct Job Log Data File Increase

Section 2.7 of the Job Based Accounting API specifies that one or more get_acct commands will
return exactly the same job data until a purge request is performed. However, on all Xerox
products with JBA job data continues to be added to the Job Data Log until a purge is performed.
11/13/2008
This means that successive get_accts will contain previously retrieved data and will also have
new data if job data for jobs that have been completed since the last get_acct was done.
3.1.1.3set_config Attribute Recording Problem

The JBA API Specification states that an XD will immediately begin logging the attributes
specified by the set_config file however on most models the changes to attributes collected will
not occur until the Document Centre device is powered off and back on or restarted/rebooted.
Note: Partner applications may send a soft-boot command instead of powering the device off/on.
3.1.1.4Multiple Accounting Servers For Single Document Center Data Loss Problem
For all Document Centre products, accounting data may be lost if more than one accounting
server is setup to manage a single Document Centre. E.. Document Centre ‘A’ is managed by
Accounting Server ‘B’ but ‘A’ is also being managed by Accounting Server ‘C’. Data could be
lost.
Specifically, if data is not retrieved by the legitimate managing accounting server it could be
‘purged’ by a second server. It is relatively easy for users of the accounting system to set up more
than one server. This problem might be difficult to diagnose in the field but should be ruled out
prior to debugging customer data loss situations.
3.1.1.5set_auth, set_config Syntax Error Handling Problem

The JBA API set_config and the set_auth file formats sections 2.9 and 2.10 specify that if a
syntax error is found when parsing a set_auth or set_config file, an error will be generated and no
change will be made to the XD database. This is not true on Document Centre and on some Work
Center products. In these products the set_auth and set_config streams are not pre-parsed to
check syntax. If an error occurs in mid file the XD database will already have been altered and
the changes will not be undone. Since it will be difficult for the EAS to ‘know’ where / what the
error was, it is probably best that the entire database be rebuilt if this situation has occurred.
Note: In the described case, an HTTP error would still be generated notifying the EAS that a
problem had occurred. If the EAS implementation follows the syntax rules of the API, it is very
unlikely that this error will ever occur.
3.1.1.6set_auth Sub-Command Problems or Limitations

Section 2.7 of the JBA API Specification has the following limitations / restrictions for
Document Centre and Work Centre, Work Center Pro Products except WC 4150
Xerox 4110/4590, WCP 123/128/133, WC 7132, WC 7228/7235/7245. These products may have other
limitations, please see the problems lists for specific products of interest.
a) The command –al should not be used the performance of this command for use in large
database maintenance is not consistently supported by all Xerox devices. It is recommended
that for larger numbers of users and accounts that –al be avoided and instead use
purge/rebuild of the entire device database. On newer products ‘Off-Box’ database
management may be used for situations where a user needs constant updates to the user and
account database. See the JBA API specification for details on use of Off-Box JBA
authentication.
11/13/2008
b) Each set_auth transaction (file) must be less than 100,000 bytes in total size. If it is necessary
to send more data than the 100K limits, this must be done in more than one set_auth HTTP
transaction.
c) Each user must have no more than 1 megabyte of characters total for accountID storage. This
includes the double quote separator character used to delineate accountIDs. Example:
+m”U1”A1”A2”. The content of this is A1”A2”
d) In order to prevent HTTP server timeout, it is recommended that each line in the set_auth file
should be limited to 50 accounts per line or less. This will allow the Document Centre time
to process the changes and return an HTTP response to the EAS. Multiple set_auth
commands may be used in separate HTTP requests to build the database of user and account
Ids.
e) The number of lines per set_auth file should be limited to 200 or less. Multiple set_auth
commands may be used in separate HTTP requests to build the database of user and account
Ids.
f) Document Centres will respond (process) EAS set_auth commands at approximately half of
normal speed when in power saver mode.
g) The commands m+ and m- requires approximately 4 seconds /per accountID to complete. It
is recommended that these commands be used only to manage very small numbers of
additions or deletions of accounts.
h) Other notes on set_auth command use:
It is recommended that the database of users and accountIDs be purged and rebuilt when a
large number of changes must be made.
3.1.1.7Blank User ID and Account ID Problem

In section 4.2.2 of the Job Based Accounting API Specification, the commands “+u” “+a”, “+al”,
“+m”, “m+” will create blank account or userIDs on XD products prior to version:
DC460/470/480/490ST 7.0.19.2.51 (Launch 490).
Blank IDs do not interfere with IDs sent by the EAS except that blank IDs take some memory
space and should not exist unless specified in the set_auth command.
11/13/2008
3.1.1.8Regarding Attributes Accounting Configuration Setup (set_config)
Problem: Document Centres need to be set up with different lists of attributes depending on the
DC model and software version number. Also, some XDs do not properly self initialize with all
system and job attributes. The latest (newest) Xerox devices will not reject unknown attributes,
but will set all attributes that are sent that are valid and that the device can support. The
get_config may be used to determine if the correct attributes are set.
For this problem, there is a workaround that may be used to assure that devices are recording the
desired attributes.
Work Around:
The “get_config” command may be sent to read the device list of job attributes and determine the
list that is set on the device. By default, nearly all devices except a few older legacy devices,
record their default maximum set of attributes. Extra attributes that do appear may be ignored by
the parsing application. If attributes are missing from the expected list, then the application may
try to “set_config” the missing attributes using the list on page 41, section 3.5.6.
If this approach fails, resort to the basic job attribute set which is all of the job attributes on page
41, section 3.5.6 except the following accounting-job-field=total-number-of-smtp-recipients,
accounting-job-field=smtp-recipient-to, accounting-job-field=smtp-recipient-cc, accounting-job-
field=smtp-recipient-bcc, fax-call-record, job-owner
Advantages of this approach: It does not rely on error responses to determine the correct attribute
set. It is relatively simple. It will work with newest and with legacy Xerox devices.
3.1.1.9 Regarding Job Attribute Support in API V 4.0.2 API Section 6.10.0.2.
At the time of the release of this SDK, V4.0.2, there is no Xerox JBA supporting models, which report jobs
as required by JBA API section 6.10.1.1 Version 4.0.2.
In legacy Xerox devices, jobs terminated before use of any machine resources (printing, scanning etc) do
not report all of the mandatory attributes as required according to API V4.0.2 section 6.10.1.1.
The second difference is that attributes that a legacy device does not support but which are mandatory
according to the JBA API V4.0.2 may not follow section 6.10.1.1 behavior as follows:
They will not use double quotes "" to indicate that a value cannot be produced by the device.
This will be corrected in future releases. The products that support API V4.0.2 section 6.10.1.1 will be
listed here as they are released.
Note: Since this mainly concerns jobs that are never printed scanned or use device resources. The impact of
this deviation should be minimal to application writers and users of the information.
11/13/2008
3.1.1.10Set_config use: Issues Applicable to All Xerox DC/WCP Products

The set_config system attribute “accounting-maximum-log-entry” is set to 15,000 even though some
devices will allow somewhat less total job log entries. E.g. the WCP 123/128/133, WC 7132, WC
7228/7235/7245 devices only allows 14,000 job log entries total. For these devices the 15,000 limit (if set)
is ignored and these devices will only record up to 14,000 jobs log entries total.
It is recommended that application writers read the get_config “accounting-maximum-log-entry” data
stream to check the value to assure it is within the range of 14,000 to 15,000. If less than 14,000 then the
set_config can be used to set the value to 15,000 and it should be transparent to the application that the
device may only be able to collect up to 14,000 job logs.
Note also: A device that cannot support 15,000 job log entries will not reject the set_config that specifies
15,000.
11/13/2008
3.1.2. API Discrepancies Affecting Specific Document Centre or Work

Centre or Work Centre Pro Products
3.1.2.1DC420/425/432/440
Problem:
The system attribute “accounting-version”. This attribute does not work. It does not provide
device type or version information of the Document Centres.
Work Around:
For API support of version number information for Work Centres and Document Centres, Xerox
provides tools (version tool) that will report the device type and software versions Xerox devices.
The tool may be used in place of this API version number until such time that the API attribute
for version number is supported. Note: the version number tool uses SNMP and will not work on
XES products.
Problem:
In Section 3.5.6 page 41 of the Job Based Accounting API Specification, the system attribute
"accounting-maximum-log-entry" is set in the Set_conf command data stream to a Maximum of
80000 records per job data file. Fixed in DC425/432/440ST General Release 3_21
NASG/DMO: 701P38453 and later versions.
Work around:
Reset the default Maximum file size to 15000 using the Set_Config command. Reboot the DC.
Note: Section 4.3.6 of the Job Based Accounting API Specification See default Attributes for
Set_Config.
Problem:
Section 3.3 of the Job Based Accounting API Specification, set_auth specifies that the +g
command may be used to set a generic userId and accountID. This function does not work on the
products listed in the table below. On these products the generic ID can not be set using the
set_auth +g command.. The same IDs will be reported by these devices for job types not
associated with user and account IDs. The IDs will be recorded in the attribute accounting-
information in hexadecimal format as “__GenericUserId__” for the account ID and
“__GenericAccountID__”. Note: each word is preceded and followed with the two underscore
characters.
The hexadecimal string of these IDs will appear in the accounting log as:
accounting-information=”5f 5f 47 65 6e 65 72 69 63 55 73 65 72 49 64 5f 5f 22 5f 5f 47 65 6e
65 72 69 63 41 63 63 6f 75 6e 74 49 64 5f 5f “
Note: DC420/425/432/440 devices will respond with a “400” client request error (review table
below please) if the application tries to set the generic ID using the set_auth +g command. The
application should be able to gracefully handle this type of error and continue functioning. On
the DC420/425/432/440 devices, an example of a job type that contains a generic ID is a
configuration report.
DC420/432/440ST
11/13/2008
Model and System Software Release ESS In this release +g command results
(helpful info in parens) * = untested for SDK in HTTP ‘400’ error
DC420/432/440ST Launch 2_1_2s YES
DC420/432/440ST SMP2 2_2_6s YES
DC420/432/440ST SMP2.1 2_2_6s YES
DC425/432/440ST
Model and System Software Release ESS
DC425/432/440ST Launch 3_0_5_4s YES
DC425/432/440ST General Release (SV65) 3_0_7_1s YES
DC425/432/440ST General Release 3_21 NASG/DMO: 3_2_1_3s YES
701P38453
Work Around:
Use the default generic IDoutput by the device.
3.1.2.2DC460/470/480/490
Problem:
The default generic ID on certain DC460/470/490 devices is not the same as specified in section
2.7.2.9“Add Generic ID” of the API
The generic ID name produced by earlier Document Center products is: (excluding double quote
marks)
“ [MANAGER [CREDIT “
Which appears in the job log in the accounting-information attribute in hexadecimal format as:
accounting-information=”5b 4d 41 4e 41 47 45 52 22 5b 43 52 45 44 49 54”
Products Affected: All Document Centre Products including and older than version
DC460/470/480/490ST 7.0.19.5.26 (MFF launch)
Work Around: Avoid specifying generic IDs in the client print stream headers. Instead use
commands that allow fax or other printing for all devices with no user or account ID s. See
section Appendix H re: print stream header insertions.
Work Around: When parsing and reading the job log, look for the common three specified
generic strings. These are:
“[MANAGER [CREDIT “ and
“GenericUserId_GenericAccountId” and
”__GenericUserId__ “ “__GenericAcctId__”.
The hexadecimal values for these names are used in the job log. Please refer to section
2.7.2.9Adding Generic IDs in the API section of this spec.
11/13/2008
Problem:
If the Document Centre has power loss, or is powered down normally, or rebooted, data not
retrieved will be lost.
Work Around: This problem is corrected on Document Center field releases beginning with
model version DC460/470/480/490ST 7.0.19.2.503 (Refresh), and later.
Customers may be upgraded to the versions of software specified in this section.
The data collection interval may be decreased so that the Document Centre is polled every 2
minutes or less.
3.1.2.3DC240/255/265
Problem:
If the Document Centre has power loss, or is powered down normally, or rebooted, data not
retrieved will be lost.
Work Around:
1) Upgrade Document Centre to newer model with software release DC460/470/480/490ST
7.0.19.2.503 (Refresh) and later.
2) The data collection interval may be decreased so that the Document Centre is polled every 2
minutes or less.
3.1.2.4WorkCentre Pro 32/40 C, WorkCentre Pro 65/75/90, WorkCentre Pro 35/45/55,

DocumentCentre 460/470/480, DC432/440, DC535/545/555
Problem:
When network accounting is enabled or re-enabled in SA setups, data will not be retrievable
with a ‘get_acct’ command until a “purge” command is sent.
Workaround Options: (two listed)
1)
Load SPAR release for the appropriate product line to fix this problem.
SPAR # 083093559 for WCP 32/40 0.001.02.028 (SP2)
SPAR # 222864044 for WCP 65/90 1.001.02.027 (SP2)
SPAR # 274509716 for 432/440 ESS/UI 2.2.9s/S2.63
SPAR # 541318726 for 460/470/480/490 07.19.05.906 ESS19.05.906 UI19.05.511

SCS19.05.906
SPAR # 763310494 for 535/545/555 0.20.53 General Release
SPAR # 972325540 for WCP 35/55 x.028.11.001 (Spar 01)
2)
11/13/2008
When initializing a Xerox device after accounting has been enabled or in another mode such as
Foreign Interface Mode, the network accounting application may send a get_acct command
followed by a “purge” command after which the device will report job data normally.
Product Model Releases Affected By this Problem
ESS UI API/SDK
Model and System Software Release
version
WorkCentre Pro 32/40 C 0.1.2.28 (sp2) 01.02.028.01 0.1.2.28, 3.3.3
WorkCentre Pro 32/40 C0.001.02.059 (sp2.1) 1.02.058.04 001.02.059 3.3.4

ESS UI API/SDK
version
WorkCentre Pro 65/75/90 1.01.02.027 (sp2) 1.02.027.01 001.02.026 3.2.2
WorkCentre Pro 65/75/90 1.001.02.063 (sp2.1) 1.02.063.03 001.02.063 3.4.4

ESS UI API/SDK
version
WorkCentre Pro 35/45/55 3.094.16.000 (smp1) 01.02.329.01 0.002.84.014 3.3.3
WorkCentre Pro 35/45/55 3.097.20.0 (smp2) 1.001.02.063 001.02.063 3.4.4
DC535/545/555ST
ESS UI API/SDK
version
DC535/545/555ST 0.20.53.0 (SMP1) 0.19.11.010.1 0.10.20.7 3.2.1
DC535/545/555ST 0.26.32.000 (SMP2) * 0.19.12.003.1 0.10.20.7 3.2.1
DC460/470/480
ESS UI API/SDK
version
DC460/470/480 7.0.19.1.20 0.19.01.018 0.19.01.017 3.2.1
DC460/470/480 7.0.19.1.504 (Refresh) 0.19.01.502.4 0.19.1.504 3.2.1
DC460/470/480/490
ESS UI API/SDK
version
DC460/470/480/490ST 7.0.19.5.26 (MFF launch) 0.19.05.021.1 0.19.05.024 3.2.1
Other: DC432/440
SPAR # 274509716 for 432/440 ESS/UI 2.2.9s/S2.63
11/13/2008
3.1.2.5 WorkCenter WCP 232/238, 245/255, 265/275265/275

ESS UI API
version
WorkCentrePro 255 13.027.24.000 (launch) 040.010.50930 012.27.022 V4.0.2 (1)
WorkCentrePro 255 13.050.30.000 SMP1 040.010.511.72 012.50.3 V4.0.2
WorkCentrePro 255 13.060.17.000 SMP2 V4.0.2
Note: Other devices have exhibited the problem noted below however these were non-
manufacturing release versions. If these situations are noted in the field, it is advisable to upgrade
the Xerox Device to the latest software release.
Problem: When the get_acct command is sent to the XD, the device does not report accounting
data even when there is accounting data stored on the XD. The problem occurs only after JBA
accounting is activated in the local UI SA setups AND after it has been re-booted. There is a
workaround for this problem. (see next paragraph) This problem will be corrected in a post
launch software releases.
Workaround:
When a ‘get_acct’ command is sent by an EAS to an XD after the conditions explained in the
problem statement, if the system did not report data (no data was retrieved) then a JBA ‘purge’
command may be safely sent by the EAS. When the next get_acct command is sent to the XD,
all missing data will be reported. Once the data is reported, the problem is not seen again unless
JBA accounting is disabled , the device is re-booted and then JBA accounting is re-enabled. To
fix the problem, it is necessary to send a ‘purge’ even if no data is retrieve. If the software
version is known using the XDC library SDK, this workaround can be specifically targeted to
that device and software version.
11/13/2008
3.1.2.6Device does not send responses to data in “chunked” HTTP/HTTPS format
WorkCenter WCP 232/238, 245/255, 265/275265/275

ESS UI API
version
Also seen in:
Xerox WC 7655/7665
ESS UI API
version
Xerox WC 7655/7665 0.40.32.50855 (launch) 40.32.50855 40.32.50855 V4.0.6
Xerox WC 7655/7665 040.032.51032 (SMP) 40.32.51032 40.32.51032 V4.0.6
Problem: Data is never returned in HTTP “chunked” transfer-encoding format even for very
large data transactions. Chunked encoding is not working in the listed products. For very large
data transfers this may become a problem if an HTTP timeout occurs.
Workarounds: Set HTTP timeouts to greater values (longer) to avoid rejection/timeout.
Contact Xerox if the timeout solution does not work.
Reference: Xerox database AR (DDTS) CDDub09613
11/13/2008
3.1.2.7Regarding Work Centre Pro Models that Do not Support Embedded Fax Job Records
Table Of Job Types related to embedded fax Information for the listed job types are not recorded.
Job Type Description Local Device Resources Records In JBA /

Used Does Not record in
(Jba user/ initiator JBA
known unknown)
Embedded Fax Send User logs in to send a phone line, scanner or Not
fax job, phone line is memory
used (jba user known)
Embedded Fax Receive Phone line is used, it’s phone line, printer Not
(and print) an incoming job, user (jba user unknown)
IDs may or may not be
present
Print Local Mailbox User goes to local mb memory, printer Not
device, selects mailbox (jba user known)
they want and print jobs
from there that have
already been transferred
there.
Print Poll Store Print images that have printer Not
already been transferred (jba user known)
from remote machine
(phone line is used)
Poll Remote Mailbox User enters phone Printer, phone line Not
number and mailbox of (jba user known)
remote fax machine and
prints images from
remote machine (phone
line is used)
Poll Remote Fax Same as above but not printer, phone line, Not
specific to mailboxes (jba user known)
Store to Mailbox Scan images to mailbox scanner, mb memory Not
(no phone line usage) (jba user known
Store for Poll Scan images to be polled scanner, poll memory Not
(no phone line usage) (jba user known
Embedded Fax Send to Send images over phone phone line, scanner or Not
Remote Mailbox line to a remote mailbox memory
(jba user known)
Fax Reports: User selects a report to printer. Not
a) activity print (real time) (jba user known)
b) dial directory Regarding fax history or
c) group dial other fax related
d) option
e) pending jobs
Auto Print Fax Reports An automatically printer. Not
generated printed report (jba user unknown)
occurs. E.g.
confirmation report,
11/13/2008 activity report
List Of Xerox Devices That Are Not Recording Embedded Fax Problem:
ESS UI API/SDK
version
Work WorkCentre Pro 35/45/55 3.028.11.000 01.01.308.01 002.27.019 3.3.3
WorkCentre Pro 35/45/55 3.094.16.000 (smp1) 01.02.329.01 0.002.84.014 3.3.3
DC535/545/555ST
ESS UI API/SDK
version
DC535/545/555ST 0.14.52.0 0.19.10.047.1 0.10.14.51 3.2.1
DC535/545/555ST 0.20.53.0 (SMP1) 0.19.11.010.1 0.10.20.7 3.2.1
DC535/545/555ST 0.26.32.000 (SMP2) * 0.19.12.003.1 0.10.20.7 3.2.1
DC535/545/555ST 0.27.18.0 0.19.12.011.1 0.10.27.31 3.2.1
WorkCentrePro 2128/2636/3545C
ESS UI API/SDK
version
WorkCentrePro 2128/2636/3545C0.001.04.044 03.04.044.01 0.01.04.43 3.3.5
WorkCentrePro 165/175
ESS UI API/SDK
version
WorkCentrePro 165/175 7.047.33.000 1.03.664.02 006.40.010 3.3.5
Note DocumentCentre 432/440 and the recent WorkCenterPro 123/128 family devices collect
embedded fax job information according to the SDK/API. (they record embedded fax job
information)
11/13/2008
3.1.2.8Regarding : WCP 123/128, WC M123/M128, WCP 7228/7235//7245,

WorkCenterPro WCP M123/M128, WCP 7228/7235//7245,
ESS MFsys API/SDK
version
WorkCentrePro M123/M128 1.202.0 1.202.0 1.64.0 3.3.5
WorkCentrePro M123/M128 1.204.7 1.204.7 3.3.6
The listed products (Green Controller from Fuji Xerox) support the JBA API with the following
deviations.
Re: Purge API command, API section 2.5.1
Devices listed in this section do not use the purge command to actually purge data on the device.
Pointers are used to track the range of data retrrieved by the application. This should be
transparent to any/ all accounting applications using these devices or other types of JBA enabled
devices.
Re: Adding Users with “Set_auth” With the Same Login As The SA
Devices listed in this section will not allow the system administrator setups user password /name
to be added to the JBA database.
Re: Job Record Range Overview 2.12.2

Devices listed in this section can store only 14000 job entries total before memory limitations are
reached. Additionally, these devices use more than 2 files to record the data. These devices use
up to 300 Data Files instead of the two files specified in section 3.7 Each Job Data File will have
up to 50 job records (e.g. 300 files times 50 jobs = 14,000 job log entries. None of these
differences should impact a properly designed JBA accounting application.
Re: Job Record Range Syntax 2.12.2.2Devices listed in this section have up to 300 files each
containing 50-job log entries. Typically legacy Xerox devices supported only 2 files each
allowing up to 14,000 jobs log entries. The syntax of the API job record range has been changed
to indicate the greater numbers of files that may be created and used by a device. This should be
transparent to a robustly designed JBA application. Devices listed in this section will increment
to the next file number as a files data is completely retrieved. (The data will not continue to
build in the same file). Again this should not adversely affect partners JBA operation
Re: get_acct example section 2.12.3.7Devices listed in this section return the oldest (time
stamped) job logs first (top of file) and the newest at the bottom of the file.
Re: HTTP Format section 3
HTTP commands on devices listed do not send server name (optional header) in the HTTP
stream. There should be no effect on partner applications.
Re: finishing attribute in JBA API Appendix A

Devices listed emit different enumerated values for finishing than XC. The values are:
"stapleTopLeft" | "stapleBottomLeft" | "stapleCenterLeft" | "stapleTopRight" |
"stapleBottomRight" | "stapleCenterRight" | "stapleCenterTop" | "staple-dual-top" | "staple-dual-
11/13/2008
bottom" | "staple-dual-left" | "staple-dual-right" | "staple-dual-saddle" | "staple-tail-left" | "staple-

tail-right" | "staple-tail-center".
It is in Xerox plans to map these to existing (legacy) finishing attributes and then obsolete these
values.
Re: jba-completed-reasons attribute in JBA API Appendix A

Devices listed will not report job status of " not-completed”.
The devices listed in this subsection will make one parent job and separate child jobs for each
phone number when the job type is an embedded-fax send job. Each child job of a fax broadcast
will record the job log data when the FAX for the specified phone number has completed. The
parent job will record the job log when all child jobs have finally completed.
Re: jba-media-block attribute in JBA API Appendix A
1) Devices in this section may have up to 11 media blocks. (11 instances of jba-media-
block in one job log)
2) There are minor differences in detected and registered sizes of documents because the
algorithms for rounding to the nearest standard size vary for these devices.
3) There will be separate jba-media-blocks for jobs containing color images vs jobs with
B&W images.(the total information would be the same) Blocks will conform to syntax of
this API specification.
4) Media type will sometimes be reported as “Other” when the media type is not known.
5) Media color is not supported in this attribute.
6) These devices do not support IMAGE-AREA_SQARE_IN_MM
Re: jba-simplex sheets attribute and duplex sheets in JBA API Appendix A
Are not supported by these devices , use jba-media-block to derive the simplex and duplex
sheets attributes. Note: These attributes appear in the JBA log however they are populated with
‘nil’.
Example: jba-simplex-sheets = “”
Re: jba-image-block attribute in JBA API Appendix ADevices in this section may have
up to 11 image blocks. (11 instances of jba-image-block in one job log)
No support for # of sheets produced in version WorkCentrePro M123/M128 1.202.0 ,
No support for scan time in seconds, or for image file size in any version
There will be separate jba-image-blocks for jobs containing color images vs jobs with B&W
images. (The total information would be the same)
11/13/2008
Re: Fax-destination-phone attribute in JBA API Appendix A
The devices listed in this subsection will make one parent job and a separate child job for each
phone number when the job type is an embedded-fax send job. Each child job of a fax broadcast
will record the job log data when the FAX for the specified phone number has completed. The
parent job will record the job log when all child jobs have finally completed.
Re: jba-net-destination-1…n attributes in JBA API Appendix A
These devices only are capable of scanning to one network destination. Other Xerox devices may
scan to and record up to 6 network destinations. (Repositories)
Re: scan-other-pages attribute in JBA API Appendix A
The attribute “scan-other-pages” is not used in these devices
Re: job-type attribute in JBA API Appendix A
For jobs stored on this device hard disk for later printing, a job log is produced. Later, when the
jobs are printed from hard disk, another job entry is produced. The entry in job log for hard disk
stored jobs will record zero printed pages in the jba-media-block attributes.
Re: jba-num-phone-numbers attribute in JBA API Appendix A
This attribute not supported in these devices. Each job log entry contains one phone number,
these may be totaled to form the number of phone numbers.
Re: job-identifier attribute in JBA API Appendix A
Job identifier range for these devices is range is 1 through 4,292,967,296(end of uint32)
Re: smtp-recipient-to attribute in JBA API Appendix A
The devices listed only support one destination address and the address will not be more than 64
characters in length.
Re: smtp-recipient-cc attribute in JBA API Appendix A
This attribute not supported by the listed devices.
Re: smtp-recipient-bcc attribute in JBA API Appendix A
This attribute not supported by the listed devices.
Re: accounting-maximmum-log-entry attribute in JBA API Appendix A
The devices in this section only support 15,000 job log entries.
Re: job-copies-completed attribute in JBA API Appendix A
This attribute reports 1 copy completed even when a copy was incomplete at job end.
Re: Job status attribute in JBA API Appendix A
11/13/2008
The job status of proof print jobs is completed –normal even for the proof print segment. These
devices log this job type as two different jobs.
The devices in this section use the MIB "Sys Object ID" and "Sys Descr".
These are comma separated. This may save applications extra steps to look these values up in
MIB tables.
Example: accounting-version = " 1.3.6.1.4.1.297.1.11.93.1.21.2.1.1, FUJI XEROX DocuCentre
Color 400 ESS_1.0.11,_IOT_10.0.1"
Special Limitations of devices Listed in This Section:

1)These devices will no allow more than 200 accounts to be associated with each user
With the +m command.
2)These devices store userIDs and accountIDs on RAM or NVRAM (Default is NVRAM for
quick authentication response.)
3)NVRAM can store only < 1000 UserIDs.
4)Hard Disk may hold up to a maximum of < 10,000 UserIDs for all products if key operator
selects HDD for UserID storage. (note: this does not work on M123/M128) the limit is 1000
users on this device.
AccountIDs are always stored on hard disk. A maximum 60,000 AccountIDs can be stored on
hard disk storage. Newest XC devices can store up to 80,000 combined users and accounts.
5)Applications should not exceed the numbers of users, accounts in NVM or HD modes
6)PJL print stream headers produced by these devices are incompatible with other XC devices.
Headers must be specified in the format of:
UserID: @PJL SET JOBATTR="@JOAU=<string>" <string> is up to 32bytes
AccountID: @PJL SET JOBATTR="@DAID=<string>" <string> is up to 32bytes
7)Exceeding the capacity of the device in numbers of accounts and users may cause the device to
stop working. This is an intermittent problem
8)The set_config command does not actually set all parameters but if the parameter set for the
device is acceptable , it returns an HTTP ‘Ok’ response.
Performance Limitations:
These devices upload large numbers of users at a slower rate than other devices.
The speed measured in Xerox lab tests was about 20,000 users and accounts in 15-20 minutes.
3.1.2.9WCP 4150 10.099.05.000 (launch and other releases as marked)
3.1.2.9.1Incorrect +u Operation (problem in Launch, and SMP1, and SMP1a releases)
Problem:
The +u command does not overwrite /replace accounts associated with the user, If a user already exists and
is sent again the accounts that were previously associated are not deleted even if they are not the same.
This is detailed in 1 and 2 below.
1.) Duplicate entries in the database if the same user ID/Account ID combination is added again, or
11/13/2008
2.) Incorrect user ID/Account ID combinations present in the database if different account names are added
for an already existing userIDname since the older ones should have been replaced by the newer ones, not
appended to.
Workarounds:
If the +u command will be used to make delta updates to the device then prior to any update the database
should be completely purged and rebuilt. This will help prevent not duplicate or extra entries from
occurring. It is possible that other set-auth commands could be used to remove all accounts associated with
a user that is being updated however this option has not been thoroughly tested/explored by Xerox for this
model product. Use ‘delta’ updating cautiously, it is more reliable to purge all and rebuild. Contact Xerox
to fix this problem. Reference: Xerox Zackdart # 4806. Load/install the latest software post launch release.
(SMP2 or later)
Reference: JBA API V4.0.6 and newer Spec Sections:

2.7, “Set_auth Command and Data Stream Format Discrepancies”
2.7.2, “Database Management Commands”
“Addition Of User With One Or More Accounts”
Corrected In: Planned fix for SMP2
3.1.2.9.2New get_auth Format Not Supported
Problem:
The WC 4150 does not support the JBA API get_auth new format (section 2.9.1.2) it uses the default or
legacy format defined in section 2.9.1.3
Workaround:
1)Application software should accept either the legacy format or the new format.
2)Use the “Off-Box” authentication protocol to validate and manage the database. (only available on post
launch WC4150 versions)
3)Contact Xerox for fix to theis problem.
Reference: Xerox Zackdart problem # 5145, JBA API 4.0. section 2.9..1.2 “Data Stream Format For
Get_aauth (new format)
Corrected In: The new format will not be used in this product; the JBA API default format should be used.
3.1.2.9.3Get_config response contains carriage return line feeds
Problem:
This problem may prevent HTTP parsers from working correctly. The get_config information may not be
properly received . The difficulty receiving HTTP data will depend on how forgiving the HTTP entity
body parser may be.
Workaround:
1)Experiment with other HTTP transport classes / libraries to find one that works with extra carriage
returns.
2)Upgrade to a newer version of the WC 4150 software with an implemented fix for this problem.
3)Contact Xerox to fix the problem within the ‘SPAR’ system.
11/13/2008
Reference: Xerox Zackdart problem # 5612, JBA API 4.0.6 and later section “get_config Data Stream
Format.
This problem is corrected in the SMP1, SMP1a and later releases.
3.1.2.9.4Set_auth wild card account is not treated as an account.
This problem prevents proper use of the wildcard account. The wildcard account is not registered as an
account in the WC4150 database and does not allow the user access to other acconts.
Workarounds:
Use association of individual users to individual accouts .
Use Off-Box authentication if available in the device software upgrade.
Upgrade the device to post launch software.
Contact Xerox and ask for a SPAR fix for this problem if a customer needs this fixed.
Reference: Xerox Zackdart problem # 5613, JBA API 4.0.6 spec or more recent, section 2.7 (all)
Corrected In: SMP1 and SMP1A post launch WC 4150 software upgrade.
3.1.2.9.5Print Jobs Terminated Before Printing Do Not Create Job Log Enties
When a network print job is terminated because the user / account IDs were not validated, the deleted job is
not logged in the JBA log.
Workarounds:
This not regarded as a serious problem. Although the WC4150 is not JBA API compliant in in how it does
not log jobs deleted prior to printing, it is doubtful that the lack of a job log will create issues for users.
Contact Xerox iand ask for a SPAR fix for this problem if a customer needs this fixed.
Reference Xerox Zackdart problem # 5778 , JBA API specification V4.0.6 or more recent , appendix J
3.1.2.9.6Get_auth Command Returns the Stream with incorrect Character Counts embedded in
the stream.
The get_auth command returns incorrect character counts for IDS or users. This means that a parser reling
on the count numbers will find IDs in the database that were no submitted.
Workarounds:
Don’t use get_auth command to verify the database of users and accounts on the WC 4150.
Reference Xerox Zackdart problem # 5782 , JBA API specification V4.0.6 or more recent , appendix J
11/13/2008
3.1.2.9.7Get_auth Command Returns Data For All Users, Only One Was Selected
The get_auth sub-command request for data for one user does not work.
Workarounds:
Don’t use get_auth command for single user, only use the command for retrieving all user.
Reference Xerox Zackdart problem # 5783 , JBA API specification V4.0.6 or more recent , section 2.9
get_auth
Corrected In: TBD
3.1.2.9.8Postcript Print and WebUI Jobs Uncollated multi set jobs Are Not Recorded In JBA
Postscript print jobs uncollated or Web UI prints do not appear in the JBA log
Workarounds:
None.
Don’t use web UI job submission or Postscript Driver. Use PCL driver
Contact Xerox and ask for a SPAR fix for this problem if a customer needs this fixed.
Reference Xerox Zackdart problem # 5800 , JBA API specification V4.0.6 or more recent
3.1.2.9.9JBA Off-Box Authentication Does Not Work In Launch
Off-Box JBA authentication fails, does not work in WC4150 launch, 10.099.02.000
Workarounds:
Load the post launch software release on the WC 4150 or call Xerox.
Reference Xerox Zackdart problem # 5834, 6061, 6062 , JBA API specification V4.0.6 or more recent
Appendix B
3.1.2.9.10User Database Upload (set_auth ) fails on 20,000 users and 20,000 accounts if 16
Character User Usernames Used.
Setup/upload of the user /account database fails for 20,000 users, 20,000 accounts, 16 char names.
Workarounds:
Use substantially less users and accounts. Reccomendation: Don’t exceed a combined 30,000 users and
accounts with 16 characters or less in user and account names. Limits of numbers of users and accounts
may be higher if shorter user and account names are used.
11/13/2008
Contact Xerox iand ask for a SPAR fix for this problem if a customer needs this fixed Reference Xerox
Zackdart problem # 5864, JBA API specification V4.0.6 or more recent
3.1.2.9.11WC4150 Produces No Accounting Record If The Device Is Powered Off or Looses

Power Prior To the End Of a Job.
If power loss occurs on WC4150, the job-in-progress will not be recorded. (job not charged) It is possible
to run to the last page of a job and turn off the WC 4150 power to avoid the JBA log (charges).
Workarounds:
Use an uninterruptible power supplys for WC4150 if possible.
Always make sure the machine is completed all jobs prior to shutting it down.
Check wit hXerox to see if this problem is fixed on later releases of WC4150.
Contact Xerox iand ask for a SPAR fix for this problem if a customer needs this fixed Reference Xerox
Zackdart problem # 5959, JBA API specification V4.0.6 or more recent.
3.1.2.9.12WC4150 Does Not Record Different Paper Sizes Manually Scanned .
If manual paper size is selected for a copy job, the paper size reported is always 8.5” x 11”
Workarounds:
Paper size scanned will not always be accurate for WC4150 accept the erroneous data.
Check with Xerox to see if this problem is fixed on later releases of WC4150.
Contact Xerox iand ask for a SPAR fix for this problem if a customer needs this fixed. Reference Xerox
Note: This device can only record 8.5 x 11” , legal sizes or manual sizes. It works correctly on SMP 1 and
SMP1A WC 4150 release.
3.1.2.9.13WC4150 Does Not Record Different Paper Sizes Auto Size Detect Scanned .
If auto paper size is selected for a scan job, the size reported is always 8.5” x 11”
Workarounds:
Paper size scanned will not always be accurate for WC4150 accept the erroneous data.
Select manual setting for scan to file job types.
Contact Xerox iand ask for a SPAR fix for this problem if a customer needs this fixed. Reference Xerox
Corrected In: SMP1 nad SMP1A post launch WC 4150 software upgrade.
11/13/2008
3.1.2.9.14WC4150 set_config Data is Sometimes Returned in Response To a “get_acct”

Command
Occasionally/ intermittently, the data requested with a “get_acct” command returns JBA device config data.
Work around:
Create applications with robust parsing of JBA data and rejection/retry of a Xerox device’s inappropriate
data response. Note: A second get_acct (if sent) will pull actual job data.
Contact Xerox and ask for a SPAR fix for this problem if a customer needs this fixed. Reference Xerox
Corrected In: TBD
3.1.2.9.15WC4150 JBA Mode Disabled Without Warning If HTTP is turned Off On Web UI
JBA is disabled if HTTP is turned off on Web UI. No warning popup is given.
Workarounds:
Contact Xerox and ask for a SPAR fix for this problem if a customer needs this fixed. Reference Xerox
Not corrected in post launch release.
11/13/2008
4.Job Attribute Problems Identified
Described below are known discrepancies associated with job attributes that pertain to a subset of Document
Centre software releases. In some cases, workarounds are provided so that accurate attribute values can be
computed. However, in order to determine whether the workaround should be applied, the Document Centre
software release version must be known. A technique for obtaining version information is provided in reference
[2], Document Centre Software Version Tool - Programmer's Guide.
For each discrepancy discussed below, the following information is provided:
• Description
• Attributes Affected
• Workaround
• Known Versions Affected
• Reference Job
Description describes the discrepancy.
Attributes Affected identifies the job attributes that are impacted by the discrepancy.
Workaround provides a technique to correct the discrepancy.
Known Versions Affected identifies the known Document Centre software release versions to which the
discrepancy applies.
Reference Job identifies one or more accounting job logs that illustrate the discrepancy. These job logs (as well
as non-discrepancy job logs) are provided with the Xerox JBA Simulator. They contain actual data obtained
from various Document Centre devices. See reference [3], Job Based Accounting Simulator - User's Guide, for
more information on the simulator.
4.1.Cover (Blank) Sheets Counted as Simplex

Sheets
Description
Copy or print jobs that call for blank cover sheet(s) result in a simplex sheet count that includes blank sheets.
This is inaccurate, as blank sheets are "unmarked", while simplex sheets are "marked".
Attributes Affected
jba-total-simplex-sheets
Workaround
The number of marked simplex sheets and the number of blank sheets cannot be computed without knowing
the Document Centre software version. If the version is known, the value can be computed as follows:
number-of-marked-simplex-sheets = lakes-number-of-images – (jba-total-duplex-sheets * 2)number-
of-blank-sheets = jba-total-simplex-sheets – number-of-marked-simplex-sheets
11/13/2008
Xerox Confidential Information Discrepancies - Known Problems
Known Versions Affected

DC240/255/265ST 6.08 (L18.6)
DC240/255/265ST 6.04 (L18.1)
DC460/470 7.01 (Launch)
DC460/470/480 7.0.19.1.20
DC460/470/480 7.0.19.1.504 (Refresh)
DC460/470/480/490ST 7.0.19.2.51 (Launch 490)
DC460/470/480/490ST 7.0.19.2.503 (Refresh)
DC460/470/480/490ST 7.0.19.4.039
DC460/470/480/490ST 7.0.19.5.26 (MFF launch)
DC535/545/555ST 0.14.52.0 (Launch
DC535/545/555ST 0.26.32.000 (SMP2)
WorkCentre Pro 32/40 C0.001.00.060
WorkCentre Pro 65/75/90 1.001.00.60
All other products
See Appendix A for version information.
Reference Job
copy-5in-1to2-1x.atc, copy-5in-1to2-3x.atc, print-3in-2sided-1x.atc, print-3in-2sided-1x.atc
4.2.Irregular Sized Originals Miscounted

Description
Input sheets sized at 8.5" x 13" are counted as 8.5" x 14" sheets. This is due to the physical characteristics of
the sensors in the document feeder.
Attributes Affected
jba-image-block-1, jba-image-block-2, jba-image-block-3
Workaround
Accept the value produced. Accuracy of image size is not assured in any case.
DC240/255/265ST 6.08 (L18.6)
DC240/255/265ST 6.04 (L18.1)
DC460/470 7.01 (Launch)
DC460/470/480 7.0.19.1.20
DC460/470/480 7.0.19.1.504 (Refresh)
DC460/470/480/490ST 7.0.19.2.51 (Launch 490)
DC460/470/480/490ST 7.0.19.2.503 (Refresh)
DC460/470/480/490ST 7.0.19.4.039
DC460/470/480/490ST 7.0.19.5.26 (MFF launch)
DC535/545/555ST 0.14.52.0 (Launch
DC535/545/555ST 0.26.32.000 (SMP2)
WorkCentre Pro 32/40 C0.001.00.060
WorkCentre Pro 65/75/90 1.001.00.60
Other products may vary in algoritm for how they record irregular sized originals. Since this is a hardware
and design limitation there is little that can be done to change this outcome.

Reference Job
copy-buildJob-4in-1sided-1x-3ib-6mb.atc
11/13/2008
4.3.Incorrect Images Transferred Count

Description
A scan-to-file job that specifies more than six destinations results in incorrect counts for the number of images
transferred.
Attributes Affected
scan-other-pages, lakes-total-images-filed
Workaround
scan-other-pages (the total count of images transferred to the seventh destination and beyond) can be
computed if the Document Centre software version is known:
scan-other-pages
less
the sum of the images transferred values from jba-net-dest-1, ..., jba-net-dest-6
lakes-total-images-filed (the count of images transferred to all destinations) can be computed if the Document
Centre software version is known:
use the uncorrected value for scan-other-pages
DC240/255/265ST 6.08 (L18.6)
DC240/255/265ST 6.04 (L18.1)
DC460/470 7.01 (Launch)
DC460/470/480 7.0.19.1.20
DC460/470/480 7.0.19.1.504 (Refresh)
DC460/470/480/490ST 7.0.19.2.51 (Launch 490)
DC460/470/480/490ST 7.0.19.2.503 (Refresh)
Note that this discrepancy has been corrected in version DC460/470/480/490ST 7.0.19.4.039,Version
DC460/470/480/490ST 7.0.19.5.26 (MFF launch), Version DC535/545/555ST 0.14.52.0 (Launch and
DC535/545/555ST 0.26.32.000 (SMP2)
And in WorkCentre Pro 32/40 C0.001.00.060
WorkCentre Pro 65/75/90 1.001.00.60
Other products fixed: (any not listed in the “known version” list but listed in Appendix A)

Reference Job
scanfile-4in-1sided-10dest.atc
4.4.Images Filed Not Recorded

Description
A scan-to-file job that contains invalid login information (name, password) or encounters a network error
does not record the number of images transferred. Additionally, a scan-to-email job that completes
successfully does not record a value for the number of images transferred or records a value of zero.
Attributes Affected
lakes-total-images-filed, total-number-of-images-filed
11/13/2008
Workaround
None.
DC240/255/265ST 6.08 (L18.6)
DC240/255/265ST 6.04 (L18.1)
DC460/470 7.01 (Launch)
DC460/470/480 7.0.19.1.20
DC460/470/480 7.0.19.1.504 (Refresh)
DC460/470/480/490ST 7.0.19.4.039
DC425/432/440ST LAUNCH
DC425/432/440ST GENERAL RELEASE (SV65)
DC420/432/440ST SMP2.1DC425/432/440ST GENERAL RELEASE 3_21 NASG/DMO: 701P38453
Note that this discrepancy has been corrected in version DC460/470/480/490ST 7.0.19.5.26(MFF launch),
Version DC535/545/555ST 0.14.52.0 (Launch and VersionDC535/545/555ST 0.26.32.000 (SMP2) and
WorkCentre Pro 32/40 C 0.001.00.060
WorkCentre Pro 65/75/90 1.001.00.60

Reference Job
all versions above except DC425/432/440ST GENERAL RELEASE (SV65): scanfile-loginError.atc, scanfile-
networkError.atc, scanfile-policyError.atc
DC425/432/440ST LAUNCH: faxBroadcast-3in-2sided-2goodPhoneNums.atc,

faxBroadcast-3in-2sided-3badPhoneNums.atc, faxBroadcast-3in-2sided-5mixedPhoneNums.atc,
faxSend-3in-2sided-1badPhoneNum.atc, faxSend-3in-2sided-1goodPhoneNum.atc,
scanemail-1in-1sided-2dest.atc
DC425/432/440ST GENERAL RELEASE (SV65): scanemail-1in-1sided-2dest.atc
DC420/432/440ST SMP2.1: *fax*.atc, *scan*.atc
4.5.Incorrect Status for Scan-to-File

Description
A scan-to-File job that cannot complete because of a Login Error, network error, or filing policy error has a
status of “Completed-normal” instead of “Error”
Attributes Affected
jba-completed-reasons
Workaround
None.
DC240/255/265ST 6.08 (L18.6)
DC240/255/265ST 6.04 (L18.1)
DC460/470 7.01 (Launch)
DC460/470/480 7.0.19.1.20
DC460/470/480 7.0.19.1.504 (Refresh)
DC460/470/480/490ST 7.0.19.2.51 (Launch 490)
DC460/470/480/490ST 7.0.19.2.503 (Refresh)
DC460/470/480/490ST 7.0.19.4.039
11/13/2008
DC420/432/440ST SMP2.1
DC425/432/440ST GENERAL RELEASE 3_21 NASG/DMO: 701P38453Note that this discrepancy has
been corrected in version DC460/470/480/490ST 7.0.19.5.26 (MFF launch), Version
DC535/545/555ST 0.14.52.0 (Launch and Version DC535/545/555ST 0.26.32.000 (SMP2) and in
WorkCentre Pro 65/75/90 1.001.00.60
4.6.Incorrect Image and Page Count for Internet-

Receive
Description
The Internet fax receive job with cover sheets selected (setups) does not record the cover sheets
Attributes Affected
Lakes-number-of-images
Media-sheets-completed
Jba-total-simplex-sheets
Jba-media-block
Workaround
Turn the job cover sheet off on local UI in System Administrator setups
DC535/545/555ST 0.14.52.0 (Launch
DC535/545/555ST 0.26.32.000 (SMP2)
Reference Job
InternetfaxRecieve.atc
11/13/2008
4.7.Accounting Information Not Recorded

Description
A scan-to-email job does not record attribute accounting information.
Attributes Affected
accounting-information
Workaround
1) Assign the job to the generic account and/ or
2) set the job aside in an error log as “malformed” in case a user wants to understand why miscounting
occurred.
DC460/470/480/490ST 7.0.19.2.51 (Launch 490)
DC460/470/480/490ST 7.0.19.2.503 (Refresh)
DC460/470/480/490ST 7.0.19.4.039
DC460/470/480/490ST 7.0.19.5.26 (MFF launch)
Note that this discrepancy has been corrected in version DC425/432/440ST GENERAL RELEASE 3_21
NASG/DMO: 701P38453, Version DC535/545/555ST 0.14.52.0 (Launch and Version DC535/545/555ST
0.26.32.000 (SMP2) and following releases.
Reference Job
scanemail-1in-1sided-2dest.atc (confirmation sheet on DC425/432/440ST LAUNCH )
4.8.Finishing Not Recorded

Description
Finishing (e.g., stapling) operations are not recorded.
Attributes Affected
finishing, jba-finishing
Workaround
None.
DC420/432/440ST SMP2.1
NASG/DMO: 701P38453 and following releases.
11/13/2008
. Other products fixed: (any not listed in the “known version” list but listed in Appendix A)
Reference Job
DC425/432/440ST LAUNCH, DC425/432/440ST GENERAL RELEASE (SV65), : print-proof.atc
DC420/432/440ST SMP2.1: *.atc
4.9.Incorrect Page & Sheet Counts For One-to-Two-

Sided Copying
Description
The number of marked pages, simplex sheets, and duplex sheets is incorrect for 1-to-2 sided copy jobs.
Attributes Affected
jba-total-simplex-sheets, jba-total-duplex-sheets, lakes-number-of-images
Workaround
The number of marked pages output (lakes-number-of-images) cannot be computed without knowing the
Document Centre software version. If the version is known, the value can be computed as follows:
Let x = the number of input pages1
Let y = x * job-copies-completed
if x is odd and y > media-sheets-completed then
lakes-number-of-images = lakes-number-of-images less job-copies-completed
otherwise
lakes-number-of-images is correct
The number of simplex sheets output (jba-total-simplex-sheets) cannot be computed without knowing the
jba-total-simplex-sheets = job-copies-completed
otherwise
jba-total-simplex-sheets is correct
The number of duplex sheets output (jba-total-duplex-sheets) cannot be computed without knowing the
jba-total-duplex-sheets = jba-total-duplex-sheets less job-copies-completed
otherwise
jba-total-duplex-sheets is correct
Note:This workaround cannot be applied without applying the workaround described in section 3.21
(Incorrect Copies Completed Count).
1
The number of input pages can be computed by taking the sum of input pages from jba-image-block-1, ...,
jba-image-block-3 and adding the value for attribute jba-image-other-size.
2
3
11/13/2008
Note: Win XPand Win 2000 Operating Systems automatically insert a an extra image ‘blank’ page for jobs
with an odd number of input images. Example: Three (actual) image pages with 1 copy printed from a Win
XPor Win 2000 workstation to an XD will result in print count of two duplex pages. The correct number of
pages would be one duplex and one simplex page. In the example above ” lakes-number-of-images” attribute
would also be affected adversely and would report “4” images rather than the correct value of “3”.
This is a problem with the driver print stream, not with the Xerox device. Microsoft plans a fix for this. The
date of the fix release is not known at the time of this writing. No work around known.
Affects all odd page number jobs submitted from Win XP and Win 2000 OS using Xerox windows print drivers
.The problem does not occur with Linux/Unix Os.
DC420/432/440ST SMP2.1
DC425/432/440ST GENERAL RELEASE 3_21 NASG/DMO: 701P38453

Reference Job
copy-5in-1to2-1x.atc, copy-5in-1to2-3x.atc
4.10.Incorrect Sheet Counts For Two-Sided Printing

Description
The number of simplex and duplex sheets is incorrect for two-sided print jobs.
Attributes Affected
jba-total-simplex-sheets, jba-total-duplex-sheets
Workaround
The number of simplex sheets output (jba-total-simplex-sheets) cannot be computed without knowing the
if lakes-number-of-images > media-sheets-completed then
jba-total-simplex-sheets = job-copies-completed
otherwise
jba-total-simplex-sheets is correct
The number of duplex sheets output (jba-total-duplex-sheets) cannot be computed without knowing the
if lakes-number-of-images > media-sheets-completed then
jba-total-duplex-sheets = jba-total-duplex-sheets less job-copies-completed
otherwise
jba-total-duplex-sheets is correct
11/13/2008
Note: Win XPand Win 2000 Operating Systems automatically insert an extra image ‘blank’ page for jobs with
an odd number of input images. Example: Three (actual) image pages with 1 copy printed from a Win XP or
Win 2000 workstation to an XD will result in print count of two duplex pages. The correct number of pages
would be one duplex and one simplex page. In the example above ” lakes-number-of-images” attribute
would also be affected adversely and would report “4” images rather than the correct value of “3”.
This is a problem with the driver print stream, not with the Xerox device. Microsoft plans a fix for this. The
date of the fix release is not known at the time of this writing. No work around known.
Affects all odd page number jobs submitted from Win XPand Win 2000 OS using Xerox windows print
drivers .The problem does not occur with Linux/Unix Os.

DC420/432/440ST SMP2.1

Reference Job
print-3in-2sided-1x.atc, print-3in-2sided-3x.atc, proof-print.atc
4.11.Incorrect Status for Canceled Copy

Description
A copy job that is canceled has a status of "completed-normal" instead of "deleted".
Attributes Affected
Workaround
None.
DC420/432/440ST SMP2.1
NASG/DMO: 701P38453. and following releases.

Reference Job
copy-cancel.atc
11/13/2008
4.12.Input Sizes and Page Counts Not Recorded for

Fax, Scan-to-File, and Scan-to-Email
Description
Input media sizes and page counts are not recorded for job type "scan".
Attributes Affected
jba-image-block-1,-2, -3
Workaround

DC420/432/440ST SMP2.1

Reference Job
DC420/432/440ST SMP2.1: *scan*.atc, except scanfax-scanfile-3in-1dest-3phoneNums.atc and
scanfile-4in-1sided-1dest.atc.
DC425/432/440ST LAUNCH: *scan*.atc, except scanfile-4in-1sided-1dest.atc.
DC425/432/440ST GENERAL RELEASE (SV65): *scan*.atc, except scanfile-4in-1sided-1dest.atc
: scanfile-loginError.atc, scanfile-networkerror.atc, see 4.27 for scanfile-policyError.atc
11/13/2008
4.13.Input Sizes and Page Count Attributes Misused

Description
The attributes for recording input media sizes and page counts are misused. Specifically, although multiple
sheets of the same size were scanned, attributes jba-image-block-n, where 1<= n <= 3, and attribute jba-
image-other-size appear in the log. Since the job contained only one unique input size, only attribute jba-
image-block-1 should appear in the log.
Attributes Affected
jba-image-block-1,-2, -3 and jba-image-other-size
Workaround
None.

Reference Job
All versions above: scanfile-4in-1sided-1dest.atc
: *scan*.atc, except scanfile-loginError.atc, scanfile-networkerror.atc (see see 4.27 for scanfile-

policyError.atc)
4.14.Ambiguous Attribute Value for Fax

Description
The value assigned to attribute lakes-number-of-images is ambiguous for fax jobs.
Attributes Affected
lakes-number-of-images
Workaround
None.
DC420/432/440ST SMP2.1

Reference Job
faxBroadcast-3in-2sided-2goodPhoneNums.atc, faxBroadcast-3in-2sided-3badPhoneNums.atc,
faxBroadcast-3in-2sided-5mixedPhoneNums.atc, faxBroadcastViaScanfile-5in-1sided-2goodPhoneNums.atc,
faxBroadcastViaScanfile-5in-1sided-3badPhoneNums.atc,
faxBroadcastViaScanfile-5in-1sided-5mixedPhoneNums.atc, faxReceive-viaBoard.atc,
faxSend-3in-2sided-1badPhoneNum.atc, faxSend-3in-2sided-1goodPhoneNum.atc,
faxSendViaScanfile-5in-1sided-1badPhoneNum.atc, faxSendViaScanfile-5in-1sided-1goodPhoneNum.atc,
scanfax-scanfile-3in-1dest-3phoneNums.atc, scanfaxBroadcast-5in-1sided-2goodPhoneNums.atc,
11/13/2008
scanfaxBroadcast-5in-1sided-3badPhoneNums.atc, scanfaxBroadcast-5in-1sided-5mixedPhoneNums.atc,
scanfaxSend-5in-1sided-1badPhoneNum.atc, scanfaxSend-5in-1sided-1goodPhoneNum.atc
4.15.Incorrect Status for Fax

4.15.1.Non-working Phone Numbers
Description
A fax job with a non-working phone number has a status of "completed-normal" instead of "error".
Attributes Affected
Workaround
None.
DC420/432/440ST SMP2.1
SNP3.2.1_3s
Note that this discrepancy has been corrected in version SV3-83.
Reference Job
faxBroadcast-3in-2sided-3badPhoneNums.atc, faxBroadcast-3in-2sided-5mixedPhoneNums.atc,
faxBroadcastViaScanfile-5in-1sided-3badPhoneNums.atc, faxSend-3in-2sided-1badPhoneNum.atc,
faxSendViaScanfile-5in-1sided-1badPhoneNum.atc, scanfax-5in-1sided-5phoneNums.atc, scanfax-
scanfile-3in-1dest-3phoneNums.atc, scanfax-scanfile-3in-5dest-3phoneNums.atc,
scanfaxBroadcast-5in-1sided-3badPhoneNums.atc, scanfaxSend-5in-1sided-1badPhoneNum.atc
4.15.2.Working Phone Numbers

Description
A fax job with a working phone number has a status of "completed-errors" instead of "normal".
Attributes Affected
Workaround
None.
DC420/432/440ST SMP2.1
Reference Job
faxBroadcast-3in-2sided-5mixedPhoneNums.atc, faxBroadcastViaScanfile-5in-1sided-5mixedPhoneNums.atc
11/13/2008
4.16.Phone Number Count Not Recorded

Description
Fax entries with multiple phone numbers do not record the number of fax phone numbers.
Attributes Affected
jba-num-phone-numbers
Workaround
Count the number of fax-destination-phone attribute occurrences to obtain the value for jba-num-phone-
numbers.
DC420/432/440ST SMP2.1
Reference Job
faxBroadcastViaScanfile-5in-1sided-2goodPhoneNums.atc,
faxBroadcastViaScanfile-5in-1sided-3badPhoneNums.atc,
faxBroadcastViaScanfile-5in-1sided-5mixedPhoneNums.atc, scanfax-scanfile-3in-1dest-3phoneNums.atc,
scanfaxBroadcast-5in-1sided-2goodPhoneNums.atc, scanfaxBroadcast-5in-1sided-3badPhoneNums.atc,
scanfaxBroadcast-5in-1sided-5mixedPhoneNums.atc
4.17.Fax Phone Number Not Recorded Correctly

Description
Fax phone number is not recorded correctly - attribute value contains "garbage". This is an intermittent
problem - in some cases, the phone number is correct. In yet other cases, the phone number attribute itself is
omitted (i.e., not recorded).
Attributes Affected
fax-destination-phone
Workaround
None.
SV3-89
Reference Job
*scan*.atc
4.18.Duplicate Job Identifiers

Description
Two log entries - both with the same job identifier - are recorded.
11/13/2008
Attributes Affected
job-identifier
Workaround
None.
DC420/432/440ST SMP2.1
Reference Job
print-proof.atc, print-secure.atc
4.19.Number of Pages Scanned Not Recorded

Correctly
Description
The number of pages scanned is recorded incorrectly.
Attributes Affected
lakes-number-of-images
Workaround
None.

Reference Job
All versions above: faxBroadcast-3in-2sided-3badPhoneNum.atc,
faxBroadcast-3in-2sided-5mixedPhoneNums.atc, faxSend-3in-2sided-1badPhoneNum
All versions above except SV3-89: scanemail-1in-1sided-2dest.atc
11/13/2008
4.20.Mail Recipients Not Recorded

Description
Email recipients are not recorded.
Attributes Affected
total-number-of-smtp-recipients, smtp-recipient-to, smtp-recipient-cc, smtp-recipient-bcc
Workaround
None.
SV3-89 (records total-number-of-smtp-recipients only; no other smtp attributes are recorded – this is because
set_config fails when the smtp attributes are specified).
DC425/432/440ST GENERAL RELEASE 3_21 NASG/DMO: 701P38453 , 7.19.05.26

Reference Job
scanemail-1in-1sided-2dest.atc
4.21.Missing Job Log Entry

Description
A job log entry for a printed cover sheet is missing.
Attributes Affected
All printing-related attributes.
Workaround
None.
DC420/432/440ST SMP2.1
Reference Job
print-proof.atc
11/13/2008
4.22.Incorrect Copies Completed Count

Description
The number of copies completed is incorrect for canceled copy jobs (jba-completed-reasons = “completed-
deleted” or “deleted” and job-type = “copy”).
Attributes Affected
job-copies-completed
Workaround
If jba-completed-reasons = “completed-deleted” or “deleted” and job-type = “copy”, then subtract 1 from
job-copies-completed. Or,Use other attributes if job status is not “completed-normal” to determine copy
count. Copy count is not consistant across Xerox devices if the job is uncollated

This discrepancy would also apply to version DC420/432/440ST SMP2.1 except that version does not record
jba-completed-reasons correctly (see section 4.11).
All models have variations in behavior (The variations are not documented in this SDK)
The copy count is not accurate for any device if a job is cancelled/ terminated before last page out and if the
job selection was uncollated, Use the jba-media-block attribute instead. All models affected.
Reference Job
copy-cancel.atc, copy-cancel-finishing.atc
4.23.Copies Completed Not Recorded

Description
The number of copies completed is not recorded for canceled print jobs (jba-completed-reasons =
“completed-deleted” or “deleted” and job-type = “print”).
Attributes Affected
Workaround
None.

DC420/432/440ST SMP2.1

All models have variations in behavior (The variations are not documented in this SDK)
The copy count is not accurate for any device if a job is cancelled/ terminated before last page out and if the
job selection was uncollated, Use the jba-media-block attribute instead. All models affected.
11/13/2008

Reference Job
print-cancel.atc
4.24.Incorrect Finishing Value Recorded

Description
The value recorded for finishing is incorrect for canceled copy and print jobs (jba-completed-reasons =
“completed-deleted” or “deleted” and job-type = “copy” or “print”) when at least one complete document
set is produced.
Attributes Affected
finishing, jba-finishing
Workaround
None, although this discrepancy is benign when job-copies-completed is used to determine finishing charges
since its value is zero when less than one document set is produced. However, be sure to apply the
workaround described in section 3.21, Incorrect Copies Completed Count.

Reference Job
copy-cancel-finishing.atc, print-cancel-finishing.atc
4.25.Incorrect Status For Canceled Jobs

Description
A value of “completed-deleted” is recorded instead of “deleted”.
Attributes Affected
Workaround
Map “completed-deleted” to “deleted”.
DC420/432/440ST SMP2.1
Reference Job
DC425/432/440ST LAUNCH: copy-cancel.atc, print-cancel.atc, print-proof.atc
DC425/432/440ST GENERAL RELEASE (SV65): copy-cancel-finishing.atc, copy-cancel.atc, print-
cancel-finishing.atc, print-proof.atc
SV3-89: copy-cancel-finishing.atc, copy-cancel.atc, print-cancel-finishing.atc, print-cancel.atc, print-
proof.atc
DC420/432/440ST SMP2.1: print-cancel.atc, print-proof.atc
11/13/2008
DC425/432/440ST GENERAL RELEASE 3_21 NASG/DMO: 701P38453: copy-cancel.atc, print-cancel.atc,

print-proof.atc, copy-cancel-finishing.atc,
Print-cancel-finishing.atc,
4.26.Multiple Job Log Entries Recorded

Description
Multiple job log entries are recorded when only a single job log entry is required. Thus, duplicate attribute
values are recorded as well.
Attributes Affected
Multiple attributes (see reference jobs for examples).
Workaround
Examine job logs for the same time/date stamp and job ID.
DC420/432/440ST SMP2.1

Reference Job
All versions: faxBroadcast-3in-2sided-2goodPhoneNums.atc, faxBroadcast-3in-2sided-3badPhoneNums.atc,
faxBroadcast-3in-2sided-5mixedPhoneNums.atc
DC420/432/440ST SMP2.1: faxSendViaScanfile-5in-1sided-1badPhoneNum.atc,

faxSendViaScanfile-5in-1sided-1goodPhoneNum.atc, scanfaxSend-5in-1sided-1badPhoneNum.atc,
scanfaxSend-5in-1sided-1goodPhoneNum.atc
4.27.Scan-to-File Policy Error not Detected

Description
A scan-to-file job that encounters a policy error is recorded as though the job completed successfully.
Specifically, filing policy “Overwrite Existing File” does not overwrite read-only files, although the
accounting job log indicates that such jobs are successful.
Attributes Affected
Multiple attributes (see reference job for examples).
Workaround
None.

Reference Job
scanfile-policyError.atc
11/13/2008
4.28.Incorrect Scan Dimensions Recorded

Description
A scan-to-file job records incorrectly records the input paper size. The short edge dimension is recorded as a
value of “0” for all scan job types. Copy jobs are not affected by this problem.
Attributes Affected
jba-image-block-1,-2, -3
Workaround
None

WorkCentre Pro 65/75/90 1.001.00.60
WorkCentre Pro 35/45/ 0.3.28.11
This problem is Fixed in device release:

WorkCentre Pro 65/75/90 xxxxxxxxxxTBD SMP2 final MFG release
WorkCentre Pro 35/45/553.84.16.000
Reference Job
Scan*.atc (all scanning job types)
4.29.Device Name Attribute Missing

Description
The attribute “device-name” is not recorded when the XD does not have a factory default serial number.
Attributes Affected
Device-name
Workaround
Field technical service rep should install/ refresh the device serial number.
Note: It is highly unlikely that this problem will occur in customer Xerox devices.

WorkCentre Pro 65/75/90 1.001.00.60
Reference Job
Effects all copy jobs
11/13/2008
4.30.Incorrect Printed Media Type and Color

Recorded
Description
The” jba-media-block-1…n” attribute records values of “unspecified” or “system-default” rather than the
actual media.type and color used in printing.
Attributes Affected
jba-media-block-1…n
Workaround
None, this problem will be fixed in future Xerox devices releases.
All Xerox devices except:

DC420/432/440ST SMP2.1 (SV-91)
DC425/432/440ST GENERAL RELEASE (SV65DC425/432/440ST GENERAL RELEASE 3_21
NASG/DMO: 701P3845
Still noted on WCP255 all versions.
Still Noted on
WCP 232/238, 245/255, 265/275
WorkCentrePro 232/238, 245/255, 265/275 13.027.24.000 (launch)
WorkCentrePro 232/238, 245/255, 265/275 13.050.30.000 SMP1
WorkCentrePro 232/238, 245/255, 265/275 13.060.17.000 SMP2
Reference Job
Effects all network ‘print’ job types,, web print jobs.
Other:
Xerox AR 61970
11/13/2008
4.31.Incorrect Copy Count Recorded For Print Jobs

With Banner Sheets
Description
Print jobs with print driver ‘banner’ sheets record one extra copy completed.
Attributes Affected
Workaround
None

WorkCentre Pro 65/75/90 1.001.00.60
WorkCentre Pro 35/45/553.84.16.000
Reference Job
All network initiated Print jobs with banner sheets
4.32.Finishing Recorded When Finishing Not

Applied
Description
Print jobs with no finishing applied (output) record finishing attributes.
Attributes Affected
Finishing
Workaround
None , this problem will be fixed in future Xerox devices releases.

Al lXerox devices except:
DC420/432/440ST SMP2.1 (SV-91)
DC425/432/440ST GENERAL RELEASE (SV65DC425/432/440ST GENERAL RELEASE 3_21
NASG/DMO: 701P38453
Reference Job
All network initiated Print jobs with banner sheets
11/13/2008
Other:
Refererence: Xerox AR 65252 and 57776
4.33.Incorrect Status For Completed Print Jobs

Description
Print jobs incorrectly report job as “completed with errors” when a job printed correctly.
Attributes Affected
Finishing
Workaround
None

WorkCentre Pro 32/40 C 0.01.01.10 (sp1)

WorkCentre Pro 32/40 C 0.1.2.28 (sp2)
WorkCentre Pro 32/40 C0.001.02.059 (sp2.1)
Reference Job
print-3in-2sided-1x.atc, print-3in-2sided-3x.atc, proof-print.atc
11/13/2008
4.34.Incorrect Image Count On Duplex Odd Number

Of Original Print Jobs
Description
Network duplex print jobs with an odd number of original pages are recorded with an extra image page in the
JBA log.. Occurs only with printed jobs submitted from Xerox drivers for operating systems of WinXP and ,
Win 2000. Does not occur on Win NT or Win 9x or other non-Microsoft operating system drivers .
Refer to the device job logs/ JBA simulator for details on how other attributes are affected
Attributes Affected
lakes-number-of-images,
Additional Adversely Affected Attributes:
jba-total-duplex-sheets, jba-total-simplex-sheets, jba-media-block…
Workaround
The problem is caused by the Microsoft Print Processor. Xerox may provide a print processor fix for this
problem in the near future.
Note users may now load a new driver that is available on Xerox.com to get around this problem. The driver
includes a custom print processor that fixes this accounting problem

WorkCentre Pro 65/75/90 1.001.00.60
WorkCentre Pro 35/45/553.84.16.000
Other devices not tested but may exhibit this problem if jobs are submitted on Win XP or Win 2000 Operating
Systems
Reference Job
print-3in-2sided-1x.atc
11/13/2008
4.35.Incomplete File Destination Path Logged

Description
All scanning job types report an incomplete file path rather than a full file path.
Attributes Affected
Jba-net-dest-1…6
Workaround
None

All versions of DocumentCentre and Work Centre Pro
Reference Job
*scan*.atc (All scan job types)
11/13/2008
4.36.Simplex Printing Doubles Impression Counts

Description
Simplex printing job types misreport the impressions counts. Simplex job impression counts are doubled.
Attributes Affected
jba-media-block-xx
Workaround
None. Upgrade device SW to SPAR release TBD, or downgrade device SW release to WorkCentre Pro
65/75/90 1.001.00.60
Known Version Affected

WorkCentre Pro 65/75/90 1.01.02.027 (smp2)
Note: A SPAR (Xerox Fix) release exists for this problem. Customers who have this release will need to be upgraded to the SPAR fix
release. SPAR # 510829142 Applies to WCP65/75/90 only. This is the only version of machine where the
problem is found..
Reference Job
All printing jobs that produce single sided output. This includes scan confirmation reports, configuration
sheets, client prints, fax prints etc .
4.37.
4.38.Incorrect Printing Of Duplex Print Jobs with

Blank Cover Sheets
Description
Duplex print jobs with blank (no image) covers selected print the first two pages of regular document on
front cover. The same pages are printed again (normally) in the document.
Although the job should not print images on the cover sheet it is counted correctly for what was produced by
the accounting system.
Workaround:
None this problem will be fixed on upgrade versions of the product.
Products Affected:
WorkCentrePro 32/40 C 0.01.01.10 (smp1)
11/13/2008
4.39.Missing “jba-image-block-n” In Copy Build Job

Description
Copy Build jobs types do not report all “jba-image-block-n” attributes for the various scanned media sizes.
Workaround:
None. This problem will be corrected on future device releases.
Products Affected:
WorkCentre Pro 32/40 C 0.1.2.028 (smp2)
Reference Job:
copy-buildJob-4in-1sided-1x-3ib-6mb.atc
4.40.Error In “jba-image-block-n” Counts

Description
Copy jobs report the wrong number of Black and White scans and the wrong number of Color scans in the JBA
attribute “jba-image-block-n”
Workaround:
None.
This problem will be corrected on future device releases.
Products Affected:
Reference Job:
copy-5in-1to2-1x.atc
4.41.Error In Simplex Print Image Counts

Description
A simplex print job is incorrectly recorded in Lakes Number Of Images. An extra image is added to the Lakes-
number-of-images count.
Workaround:
Use the jba media block attribute information.
This problem will be corrected on future device releases.
Products Affected:
WCP 65/75/901.001.02.027 (SP2)
11/13/2008

Reference Job:
print-secure.atc
4.42.Embedded Fax Jobs Information Is Not

recorded
Description
Jobs initiated started in the UI embedded fax mode dialog are not recorded. Lan fax jobs, fax Reports and
Fax Receive jobs are not recorded.
Note: Server fax works normally, however embedded fax mode fails to record any JBA job information
Workaround:
Use a fax intercept solution. (Scan to Fax).
Contact Xerox to request feature addition / correction of this problem.
This problem will be fixed in other or future WCP product lines. See the list below on products not affected by
this problem.
Products Affected:
WorrkCentrePro 2128/2626/3545C All versions
WorkCentrePro35/445/55 All versions
WorkCenterPro 165/175 All versions
WorkCentrePro 35/45/55 All versions
DC535/545/555 Al l versions
Products Not affected:
DC440 and DC432 , DC430 product line, all
WorkCentrePro M123/M128 products, all
WorkCenterPro 7228/7235/7245, all
WorkCenterPro 7132, all
WorkCenterPro 4150, all
Attributes Affected:
All attributes for fax jobs initiated within the fax job dialog on the products affected list.
Summary Of the Condition:
No attributes are recorded for any embedded fax jobs or for any jobs started in the embedded fax pathway.
Reference Job:
NA
Other:
Xerox reference AR
11/13/2008
AR Not written. A change request is in the Xerox system to correct this problem.
Please contact Xerox Solutions and SDK group if this is causing a problem for you or your customers.
4.43.Incorrect Copy Job Completed Status

Description
A copy job reports “completed with errors” when no errors were present in the job.
Workaround:
None. To be corrected in future releases
Products Affected:
WorkCentrePro 2128/2636/3545_0.001.04.044
Reference Job:
copy-5in-1to2-1x-atc
Other:
Xerox AR 74453 and AR 84891
4.44.Incorrect Media Size Recorded For Copy Build

Job
Description
A copy build job reports incorrect image size scanned for a job.
An A4 sized document was scanned but reported as 8.5 x 11”
Workaround:
None. To be corrected in future releases
Products Affected:
WorkCentrePro 65_75_90_1.1.2.63
Reference Job:
Copy-buildJob-4in-1sided-1x-3+ib-5mb.atc
Other:
Xerox Reference AR DDTS 60636 (was slated to be fixed in this release.)
4.45.Copy Job Incorrect Color Impressions

Description
A copy job attribute jba-media-block records the incorrect number of color impressions.
Workaround:
11/13/2008
For JBA recording accuracy, return to the launch release version. 001.04.044
Products Affected:
WorkCentre Pro .001.04.505 (SPAR release only, the launch version recorded this correctly)
Reference Job:
A simplex copy job
Other:
Xerox Reference ICSS 753245017
4.46.Fax Call Record attribute not supported

Description
The JBA API V4.0.X job attribute: “Fax-Call-Record” (recording embedded fax send) is not supported on any
of the devices listed in the device table of this specification.
The devices supporting this attribute will be specified in future updates to this specification.
Workaround:
Don’t use this attribute until products that support it are released.
Products Affected:
All WCP, DC, models/ products EXCEPT WCP4150,
(all versions of WCP4150 support Fax Call record attribute)
Reference Job:
NA
Other:
NA
4.47.Missing Image Block Attribute On Duplex Jobs

Description
The JBA API job attribute: “jba-image-block” is not reported on select devices for copy jobs duplex input to
duplex output. The attribute is missing from the job log.
Workaround:
Attributes that are listed as mandatory in the JBA API but are missing in the device JBA job data should be
handled by the partner application strategy for dealing with device data errors or data faults.
The situations where this may happen are:
• The Xerox device has become incapable (by fault /error) of supplying the attribute.
• The Xerox device does not or can not support the attribute (for design reasons or API version resons).
Products Affected:
11/13/2008
WorkCentrePro 2128/2636/3545C_0.001.04.044, WorkCentre Pro 32/40 C 0.001.00.060, WorkCentre Pro

32/40 C 0.01.01.10 (sp1). WorkCentre Pro 32/40 C 0.1.2.28 (sp2). WorkCentre Pro 32/40 C0.001.02.059
(sp2.1)
Is Corrected After (Date) & Models:

Reference Job:
Copy duplex-to-duplex single page input.
4.48.Duplex and Simplex Count Error When Front

Cover Selected
Description
A network (postscript) duplex output print job with a front printed cover and three image sides causes
incorrect duplex counts in the JBA log.
If the cover selection is for front cover only (printed on green paper), then the output is as follows on WCP
4150:
Page 1 image is applied on the front of the green cover paper
Pages 2 and 3 duplexed on the next sheet of paper (white paper)
And 1 additional sheet of white paper with nothing printed on it..
Problem: The JBA log records zero duplex sheets., 3 simplex It should record 1 duplex., 2 simplex
Attributes Affected: ”jba-total-simplex-sheets”, “jba-total-duplex-sheets”
Workaround:
1)Accept a miscount of duplex and simplex or
2)Contact Xerox to fix this in the WCP4150 product. It is scheduled to be
Products Affected:
WCP4150, Launch Only.
Fixed on SMP1 release.
11/13/2008
4.49.Scanned Images Not Counted as B&W and

Color
Description
On the WC4150 B&W product , scan jobs don’t automatically record the number of Color and B&W images
in the JBA-image-block attribute.
The jba-image-block attribute will record either color images (if full color was manually selected) or B&W
images, not both in the same jba-image-block.
Problem:
Images are recorded as B&W or Color but not both. (unlike other XD models) The device does parse/record
B&W vs color images.
“jba-image-block”
Workaround:
None, except use the B&W count totals.
Products Affected:
WCP4150 (all versions) The WCP 4150 has a color scanner and B&W print engine.
Reference Job:
NA
4.50.Incorrect Job Status For Scan Job Terminated

Because Of Fault
Description
If a a scan job faults while scanning and the device requires reboot. the device JBA log may record the job as
“completed normal” even though the job was “terminated”.
Problem:
See description
“jba-completed-reasons” ( reports “completed-norma”l when it should report “terminated”)
Workaround:
None, Note: this problem happens very rarely.
Products Affected:
11/13/2008
WCP4150 launch, , SMP1
4.51.Incorrect Number Of Copies Completed If Job

Ends Before Full Completion.
Description
A copy uncollated job will report the wrong number of copies completed if it ends before the job completes all
printing.
“job-copies-completed” (reports erroneous values for uncollated jobs, works ok for collated jobs.)
Workaround:
If status of “job-copies-completed” is not “completed-normal”. Then ignore the copies completed attribute
value. Instead use JBA-media-block-x or other attributes.
Products Affected:
WCP4150 launch, release 10.099.02.000
4.52.Scan to File Reports Only The Most Significant

Destination In jba-net-dest
Description
A scan to file job reports only part of the destination address (the IP or host name) This means that multiple
destinations to the same IP /host will not be distinguishable except that there will be separate destination
address blocks in the JBA log.
“jba-net-dest-n” (multiple instances of” jba-net-dest-n” may contain the same network location..)
Workaround:
Treat each destination block as unique even if the destination address appears to be the same
Products Affected:
WCP4150 launch, release 10.099.02.000, SMP 1
11/13/2008
System Attribute Problems Identified
4.53.‘authorization-web-location’ Partly Functional

Problem Description
The values accepted by authorization-web-server “are not JBA API compliant. The HTTP or HTTPS prefixes
specified in the JBA API Appendix B, attribute: “authorization-web-server” do not work. The only available
mode is HTTPS using the “legacy” mode. Example: authorization-web-server = “13.135.125.221” (this mode
works because the HTTP or HTTPS prefix is not used. Communication should be done in HTTPS mode.
Suggested Workarounds:
1) Request fix for this device (SPAR) from Xerox if it is critical for a partner application.
2) Use the IP or Host mode only. Example: “13.135.125.80”, or hostname OR IP address string +
custom_port . These will setup the Xerox device for use in the specified IP and port in HTTPS mode.
.
Products Affected:
WCP 232/238, 245/255, 265/27513.050.30.000 (launch)
Fixed on After (Date) & Models:
SMP1 release fixed
4.54.‘authorization-web-location’ Default Mode is

Not Available
Problem Description
The HTTP or HTTPS prefixes specified in the JBA API Appendix B, # 7 “authorization-web-server” work
correctly however the default mode (not using the HTTP or HTTPS prefix) as used in (launch) and post launch
releases does not authenticate and causes “pink screen reset” when a user attempts login at the LUI.
1) Request fix for this device (SPAR) from Xerox to support the default web server location mode if it is
critical for a partner application.
2) Use the prefixes HTTPS . Example: “https:/13.135.125.80:443”, or “prefix:/hostname OR
IP”:custom_port these will setup the Xerox device for use in the specified IP and port in HTTPS
mode.
Products Affected:
Xerox WC 7655/7665 10.099.02.000 (launch) 40.32.50854

Xerox WC 7655/7665 040.032.50869 40.32.50869
Fixed in Post Launch Release: TBD (a fix is planned, please load the latest software release)
11/13/2008
4.55.‘authorization-web-server’ Attribute and Off-

Box Mode is Inoperative
Problem Description
This attribute is non-functional on the product listed below. This means that Off-Box JBA authentication does
not work for the product listed.
Use only the on-board database (set_auth database management) on the WC 4150 launch release.
Products Affected:
WCP 4150 launch, release 10.099.02.000
After (Date) & Models:
Fixed in SMP launch
11/13/2008
A.Document Centre Software Versions
A.1.Product Applicability
The tables below show various Document Centre software releases. The version numbers used in this document
refer to the 'Release' column of the tables. If you are interested in writing an application that queries a
Document Centre for version information, see reference [2], Document Centre Software Version Tool -
Programmer's Guide.
Values in the 'Common Name' are used primarily by the JBA Simulator (see reference [3], Job Based
Accounting Simulator - User's Guide) and in conversation. However, the definitive name for a Document
Centre software version is given in the 'Release' column.
432/440ST
Model and System Software Release ESS UI API/SDK
version
(helpful info in parens) * = untested for SDK
DC432/440ST Launch 2_1_2s S236a 3.0
DC432/440ST SMP1 2_1_7 S243a 3.0
DC432/440ST SMP2 2_2_6s S2.50 3.0
DC432/440ST SMP2.1 2_2_6s S2.62 3.0
DC432/440ST General Release 2_4 2_3_11_1s S2.75 3.0
DC425/432/440ST
ESS UI API/SDK
version
DC425/432/440ST Launch (SV-59) 3_0_5_4s S3.46b 3.0
DC425/432/440ST General Release (SV-65) 3_0_7_1s S3.46b 3.2.1
DC425/432/440ST General Release 3_21 3_2_1_3s S3.69 3.2.1
NASG/DMO: 701P38453
DC240/255/265ST
ESS UI API/SDK
version
DC240/255/265ST 6.04 (L18.1) 0.18.1.24.2 0.18.1.25 3.0
DC240/255/265ST 6.08 (L18.6) 0.18.6.05.3 0.18.6.4 3.0
DC460/470
API/SDK
version
DC460/470 7.01 (Launch) 0.19.0.28.2 0.19.0.27 3.0
DC460/470/480
ESS UI API/SDK
version
DC460/470/480 7.0.19.1.20 0.19.01.018 0.19.01.017 3.2.1
11/13/2008
DC460/470/480 7.0.19.1.504 (Refresh) 0.19.01.502.4 0.19.1.504 3.2.1
DC460/470/480/490
ESS UI API/SDK
version
DC460/470/480/490ST 7.0.19.2.51 (Launch 490) 0.19.02.050.1 0.19.2.49 3.2.1
DC460/470/480/490ST 7.0.19.2.503 (Refresh) 0.19.02.503.6 0.19.2.503 3.2.1
DC460/470/480/490ST 7.0.19.4.038 0.19.04.034.3 0.19.04.037 3.2.1
DC460/470/480/490ST 7.0.19.5.26 (MFF launch) 0.19.05.021.1 0.19.05.024 3.2.1
DC460/470/480/490ST 7.0.19.5.509 (General) 0.19.05.909 0.19.5.502 3.2.1
DC460/470/480/490ST 7.0.19.5.26 (General) 0.19.05.512 0.19.05.511 3.2.1
DC535/545/555ST
ESS UI API/SDK
version
DC535/545/555ST 0.14.52.0 (Launch 0.19.10.047.1 0.10.14.51 3.2.1
DC535/545/555ST 0.20.53.0 (SMP1) 0.19.11.010.1 0.10.20.7 3.2.1
DC535/545/555ST 0.26.32.000 (SMP2) * 0.19.12.003.1 0.10.20.7 3.2.1
DC535/545/555ST 0.27.18.1 0.19.12.11.1 0.10.27.31 3.2.1
WorkCentre Pro 32/40 C

ESS UI API/SDK
version
WorkCentre Pro 32/40 C 0.001.00.060 1.00.60.3 001.00.060 3.3.1
WorkCentre Pro 32/40 C 0.01.01.10 (sp1) 1.01.010.01 001.00.060 3.2.2

WorkCentre Pro 32/40 C 0.1.2.28 (sp2) 01.02.028.02 00.1.02.028, 3.3.3
WorkCentre Pro 32/40 C0.001.02.059 (sp2.1) 1.02.058.04 001.02.059 3.3.4

ESS UI API/SDK
version
WorkCentre Pro 65/75/90 1.001.00.60 1.00.060.1 001.00.060 3.3.1
WorkCentre Pro 65/75/90 1.01.02.027s (p2) 1.02.027.01 001.02.026.02 3.2.2
WorkCentre Pro 65/75/90 1.001.02.63 (sp2.1) 1.02.063.03 001.02.063 3.3.5
WorkCentre Pro 65/75/90 1.001.02.716 1.08.016.0100 001.02.714 3.3.5

ESS UI API/SDK
version
WorkCentre Pro 35/45/ 0.3.28.11 (launch) 1.01.308.01 002.27.019 3.3.2
WorkCentrerPro 35/45/55 3.097.20.0 (smp2) 1.02.058.04 002.92.012 3.3.5
11/13/2008
WorkCentre Pro C2128/C2636/C3545

ESS UI API/SDK
version
WorkCentrePro 2128/2636/3545C_0.001.04.044 03.04.044.01 0.01.04.43 3.3.5
WorkCentrePro 2128/2636/3545C_0.001.04.052 03.04.049.02 0.01.04.051 3.3.5
WorkCentrePro 2128/2636/3545C_0.001.04.511 03.04.049.02 0.01.04.510.01 3.3.5
WorkCentre Pro 165/175

ESS UI API/SDK
version
WorkCentrePro 165/175 7.047.33.000 (US) 1.03.664.02 006.40.010 3.3.5
WorkCenter M123/M128 Work Center Pro 123/128

ESS Mfsys API/SDK
version
WorkCentrePro M123/M128 1.204.7 1.204.7 3.3.5
WorkCentrePro M123/M128/133 1.205.0 1.204.7 3.3.5
WorkCenterPro WCP 232/238, 245/255, 265/275

ESS UI API
version
WorkCenterPro WC 7132
ESS UI API/SDK
version
WorkCenterPro 7132 1.201.0 (launch) 1.201.0 V3.3.5
WorkCenterPro 7132 1.202.1 (post launch) 1.202.1 V3.3.5
WorkCenterProWC 7228/7235/7245
ESS UI API/SDK
version
WorkCenterPro 7245 1.239.1 V3.3.5
WorkCenterPro 7245 1.208.0 V3.3.6
Xerox 4110/4590
ESS UI API/SDK
version
Xerox 4110 1.202.6 V3.3.5
11/13/2008
Xerox WC 4150
System Software UI JBA API
Release version
Xerox 4150 10.099.05.000 (launch) 10.099.05.000 na V4.0.6
Xerox 4150 10.100.06.000 (SMP1) 10.100.06.000 na V4.0.6
Xerox 4150 10.100.14.000 (SMP1a) 10.100.14.000 na V4.0.6
Xerox WC 7655/7665
ESS UI API
version
Xerox WC 7655/7665 0.40.32.50855 (launch) 40.32.50855 40.32.50855 V4.0.6
Xerox WC 7655/7665 040.032.51032 (SMP) 40.32.51032 40.32.51032 V4.0.6
API Version History and Feature Differences Summary:

Version 4.0.1
1) First API version with “Off Box” authentication capability.
2) API and Descrepancies documents separated
11/13/2008
B.Determination Of Device Attribute

Capabilities (set_config initialization
Algorithm)
B.1.Regarding Attributes to Use For Document

Centre Accounting Configuration Setup
(set_config)
Problem: Document Centres need to be set up with different lists of attributes depending on the
model type and software version number. Also, some machines do not properly self-initialize with
all system and job attributes.
Work Around: Using the set_config command, set various DCs up to use / collect different
attributes. The complete list of all attributes may be found in the “Default Attributes” section 2.10.6
of the JBA API spcefication .
The ‘D’ list will always work for all devices although for example: SMTP attributes will not be
collected.
An application can programmatically determine the appropriate set_config attribute list by following
this procedure: The application may send (set_config) the ‘A’ list to the XD and if there is no error
response, this list will be ok to use. If there is an error, then list ‘B’ may be sent. If list ‘B’ causes an
error, then list ‘C’ should be used etc, etc.
Note this section refers to Job attributes only. There will be system attributes that need to be set if off-box
authentication is used.
1) Job Attribute List ‘A’ = all attributes listed in the ‘Default Attributes’ list in the latest JBA API
specification.
2) Job Attribute List ‘B’ = all attributes listed in the ‘Default Attributes’ list in the latest JBA API
specification except (not including) the following: job-owner-domain
3) Job Attribute List ‘C’ = all attributes listed in the ‘Default Attributes’ list in the latest JBA API
specification. except (not including) the following: job-owner-domain, job-owner, fax-call-
record, accounting-information-avp,
4) Job Attribute List ‘D’ = all attributes listed in the ‘Default Attributes’ list in the latest JBA API
specification. Except (not including) the following: job-owner-domain, job-owner, fax-call-
record, accounting-information-avp,accounting-job-field=total-number-of-smtp-
recipients,accounting-job-field=smtp-recipient-to, accounting-job-field=smtp-recipient-cc,
accounting-job-field=smtp-recipient-bcc
11/13/2008
B.2. Job Attribute First Used In API Version

B.2.1.Job Attribute Table Listing Of Attribute First Use
Attribute Name Attribute First Appears in API Version
accounting-information Inception–to-current
accounting-information-avp 3.6 & V4.0.1 (First use in WC and WCP
232/238, 245/255, 265/275, July 2005)
System Software 13.027.24.000
jba-device-name Inception–to-current
completion-time Inception–to-current
job-name Inception–to-current
jba-finishing OR finishing
Inception–to-current
jba-completed-reasons Inception–to-current
job-copies-completed Inception–to-current
media-sheets-completed Inception–to-current
jba-media-block-1… jba-media-block-N
jba-media-other-pages Inception–to-current
jba-total-simplex-sheets Inception–to-current
jba-total-duplex-sheets Inception–to-current
jba-image-block-1…. Jba-image-block-N
jba-image-other-size Inception–to-current
fax-destination-phone Inception–to-current
jba-net-dest-1…jba-net-dest-N Inception–to-current
scan-other-pages Inception–to-current
lakes-number-of-images Inception–to-current
11/13/2008
Attribute Name Attribute First Appears in API Version
job-type Inception–to-current
jba-num-phone-numbers Inception–to-current
job-identiifier Inception–to-current
total-number-of-images-filed or Inception–to-current
lakes-total-images-filed
total-number-of-smtp-recipients JbacomspecE2.1.doc (First use in DC490
7.0.19.2.51
smtp-recipient-to JbacomspecE2.1.doc (First use in DC490
7.0.19.2.51
smtp-recipient-cc JbacomspecE2.1.doc (First use in DC490
7.0.19.2.51
smtp-recipient-bcc JbacomspecE2.1.doc (First use in DC490
7.0.19.2.51
job-owner 3.6 & V4.0.1 (First use in WCP WCP 232/238,
245/255, 265/275, July 2005)
System Software 13.027.24.000
job-owner-domain V4.0.5 (as of December 31, 2006 no XD
supported this attribute)
fax-call-record 3.6 & V4.0.1 (First use in WCP WCP4150,
September 2006, launch)
B.3.System Attribute First Used In API Version

B.3.1.System Attribute Table Listing Of Attribute First Use
System Attribute Comments Products API Version Of

Name 1rst Use
accounting-maximum- All Document Centre API 3.5 and older
log-entry Products
accounting-version The format of this is not All Document Centre API 3.5 and older
specified or tracked, Products
tested or controlled
accounting-disable- Does not disable copy All Document Centre API 3.5 and older
server-when-log-full jobs even when log-full Products
limit is reached
accounting-enabled Not used by Document Used only in Wide Not documented
attribute Centre Products Format Printer
products only
Used only in Wide
Format Print products
only
authorization-off-box Added attribute Added in:WCP API V3.6 and more
7655/7665 recent
11/13/2008
WC 4150
authorization-timeout- Added attribute API V3.6 and more

sec recent
authorization-failure- Added attribute API V3.6 and more

policy-acceptjob recent
authorization-server. Added attribute API V3.6 and more
recent
authorization-web- Added attribute API V3.6 and more
location recent
print-authorization- Added attribute API V3.6 and more

bypass recent
11/13/2008

JBA Users Guide

Uploaded by

Copyright:

Available Formats

You might also like

JBA Users Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

JBA Users Guide

Uploaded by

Copyright:

Available Formats

Xerox Confidential Information

Job Based Accounting

JBA SDK Part 2

10/02/01 Xerox Corporation 1.0/0.1 Initial Release

- Added “Intenet-Receive” to section title

- added DC425/432/440ST GENERAL

Page iii Xerox Corporation

05/31/02 Xerox Corporation 3.0.4 1.4 – updated related documents

10/25/02 Xerox Corporation 3.2.1 • 1.4 – updated related documents

07/21/03 Xerox Corporation 3.3.1 Summarized Changes For Revision 3.3.1

12/19/03 Xerox Corporation 3.3.2 Summarized Changes For Revision 3.3.2

Page v Xerox Corporation

02/03/04 Xerox Corporation 3.3.3 Summarized Changes For Revision 3.3.3

09/05/04 Xerox Corporation 3.3.4 Summarized Changes For Revision 3.3.4

04/19/05 Xerox Corporation 3.3.5 Summarized Changes For Revision 3.3.5

10/15/05 Xerox Corporation 4.0.1 Summarized Changes For Revision 4.0.1

• Add product software releases for WCP 255

10/25/05 Xerox Corporation 4.0.2 Summarized Changes For Revision 4.0.2

• The attribute Fax-Call-Record block added to

• Version numbers update for this changed.

• Section added 3.1.1.9

• Previous Limit of 10 lines per set_auth in

• Added section 4.4.6 copy duplex to duplex

11/01/06 Xerox Corporation 4.0.6 Summarized Changes For Revision 4.0.6

• Added products: 4110/4590, WC 4150,

11/01/06 Xerox Corporation 4.0.6 Summarized Changes For Revision 4.0.7

• Update changes for products WC 4150 and

3.1.1.1 System Accounting Data Loss Problems..................................................................................9

Page ix Xerox Corporation

B.2. JOB ATTRIBUTE FIRST USED IN API VERSION......................................................................................71

11/13/2008 Xerox Corporation Contents 1

4.42. EMBEDDED FAX JOBS INFORMATION IS NOT RECORDED.............................................................................58

11/13/2008 Xerox Corporation Contents 3

2.1.Job Attribute Deltas

Attribute Name Description Of Difference Product: Product Version Value Difference

DC240,DC255,DC265,DC460, The Configuration

Attribute Name Description Of Difference Product: Product Version Value Difference

jba-finishing 1) The attribute “jba- 1) DC420/432/440ST SMP2

Attribute Name Description Of Difference Product: Product Version Value Difference

2) All Document Centre products 2)The optional jba-

3) API/SDK version 3.3.1. 3)The attribute

Attribute Name Description Of Difference Product: Product Version Value Difference

3)Black and white

Attribute Name Description Of Difference Product: Product Version Value Difference

total-number-of- 1. “total-number-of-images- 1. DC490, DC425 all versions.

Attribute Name Description Of Difference Product: Product Version Value Difference

smtp-recipient-cc This will first appear on DC490 and subsequent versions

smtp-recipient-bcc This will first appear on DC490 and subsequent versions

Table 2-1: Job Attribute Delta Table

3.JBA API Deviations Detailed

3.1.1.All Xerox Document Centre Products

3.1.1.1System Accounting Data Loss Problems

3.1.1.2get_acct Job Log Data File Increase

3.1.1.3set_config Attribute Recording Problem

3.1.1.5set_auth, set_config Syntax Error Handling Problem

3.1.1.6set_auth Sub-Command Problems or Limitations

3.1.1.7Blank User ID and Account ID Problem

3.1.1.8Regarding Attributes Accounting Configuration Setup (set_config)

3.1.1.10Set_config use: Issues Applicable to All Xerox DC/WCP Products

DC420/432/440ST SMP2.1: fax.atc, scan.atc