Xerox 7300DN User Guide - Page 94

Log Files and Debug Functionality

Page 94 highlights

Log Files and Debug Functionality When PrinterMap encounters a problem, a pop-up message appears referring the user to the pmap.log. which contains general application status messages. Several process-specific logs can be generated by activating PrinterMap's debugging facility, for which several debug levels are available. The application initialization file, [Drive]:\[nstall Directory]\pmap.ini contains debug parameter settings and can be edited using any standard ASCII file editor. Debugging is available for the following processes: Table 11 Processes Eligible for Debug Parameter Process Log Files Topology Discover Status Reporting Main PrinterMap application Discover process Status polling process Report polling process pmap.log, topology.log* pmap.log, discover.log* pmap.log, status.log* pmap.log, reporting.log* * Generated only when debug level is > 0. See valid values in the following table. The following are valid debug settings for any of the above processes: Table 12 Debug Parameter Values Parameter Value 0 10 20 30 Information Type Debugging Off (status messages -initialization and process termination messages- only in pmap.log Tracing (entrance to and return from functions) Internals (Tracing + any function input parameter values the developer anticipated being significant) Details (Tracing +Internals + any variables or conditions the developer anticipated being significant) PrinterMap User Guide 78

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

PrinterMap User Guide
78
Log Files and Debug Functionality
When PrinterMap encounters a problem, a pop-up message appears referring the
user to the pmap.log. which contains general application status messages. Several
process-specific logs can be generated by activating PrinterMap's debugging
facility, for which several debug levels are available. The application initialization
file,
[Drive]:\[nstall Directory]\pmap.ini
contains debug parameter settings and
can be edited using any standard ASCII file editor.
Debugging is available for the following processes:
Table 11 Processes Eligible for Debug
Parameter
Process
Log Files
Topology
Main PrinterMap application
pmap.log,
topology.log*
Discover
Discover process
pmap.log,
discover.log*
Status
Status polling process
pmap.log,
status.log*
Reporting
Report polling process
pmap.log,
reporting.log*
*
Generated only when debug level is > 0. See valid values in the following table.
The following are valid debug settings for any of the above processes:
Table 12 Debug Parameter Values
Parameter Value
Information Type
0
Debugging Off (status messages -initialization and
process termination messages- only in pmap.log
10
Tracing (entrance to and return from functions)
20
Internals (Tracing + any function input parameter values
the developer anticipated being significant)
30
Details (Tracing +Internals + any variables or conditions
the developer anticipated being significant)