Xerox 7300DN User Guide - Page 95

Verify Tracing + Internals +Details + Looping +error

Get Xerox 7300DN - Phaser Color Laser Printer PDF manuals and user guides View all Xerox 7300DN manuals
Add to My Manuals
Save this manual to your list of manuals

Page 95 highlights

40 Looping (Tracing + Internals + Details + monitoring entrance to and exit from all looping sections of code) 50 Verify (Tracing + Internals +Details + Looping +error conditions not warranting a message being logged to the pmap.log file) A debug setting of 10 or higher initiates the *_dbg.log files. If debug is 0 for all processes, the only log maintained is pmap.log containing general status messages. Each log message is prefixed by the date/time of occurrence and name of the generated process. Maximum log file size can also be specified in the "[logfile]" parameter of the [Drive]:\[Install Directory]\pmap.ini file. Default, measured in kilobytes, is 100. Each time PrinterMap is activated, it checks the pmap.log file for size and proceeds trimming the file by 20%, The oldest historical data is trimmed first. NOTE: When debugging is activated the process must be RE-STARTED to affect the change. For example, if running Windows NT and increasing the debug level for the PrinterMap Status process, go to the Services window of the control panel. Stop and re-start PrinterMap Status service. PrinterMap User Guide 79

  • 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
79
40
Looping (Tracing + Internals + Details + monitoring
entrance to and exit from all looping sections of code)
50
Verify (Tracing + Internals +Details + Looping +error
conditions not warranting a message being logged to the
pmap.log file)
A debug setting of 10 or higher initiates the *_dbg.log files. If debug is 0 for all
processes, the only log maintained is pmap.log containing general status messages.
Each log message is prefixed by the date/time of occurrence and name of the
generated process.
Maximum log file size can also be specified in the "[logfile]" parameter of the
[Drive]:\[Install Directory]\pmap.ini
file. Default, measured in kilobytes, is 100.
Each time PrinterMap is activated, it checks the pmap.log file for size and
proceeds trimming the file by 20%, The oldest historical data is trimmed first.
NOTE:
When debugging is activated the process must be RE-STARTED to
affect the change. For example, if running Windows NT and increasing
the debug level for the PrinterMap Status process, go to the Services
window of the control panel. Stop and re-start PrinterMap Status
service.