Xerox 6180N DocuSP Common Controller System Guide - Page 123

LP/LPR and the ASCII job tickets

Page 123 highlights

ep_exception_log and ep_primary_log Troubleshooting These logs contain a list of faults. The ep_exception_log contains a listing of all logged faults. The ep_primary_log contains exceptions that are the primary cause of the problem. The format of these files is as follows: Logging Module /t# Absolute Time /t# Microseconds /t# Instance ID:Module TD /t# Exception ID /t# Service Code LPR logs The following logs are important for troubleshooting problems in mapping NPS and DocuSP: • LPR logs that contain information related to the LPR gateway such as missing jobs or communications problems. Examples: /opt/XRXnps/log/XLP/Debug.Log • JPM logs that contain information related to the Job Pool Manager (JPM). The attribute set by the LPR Gateway can be checked and verified by looking at this log: /opt/ XRXnps/log/JPM.Debug.Log. Printing the accounting log Print the Accounting log to gather information and recover from various accounting problems. Either the entire Accounting log or a portion of the log may be printed. This can be completed on the DocuSP interface in the [Administration] section. LP/LPR and the ASCII job tickets The following procedure is used to verify that the attributes and options are correct: 1. Open a terminal and login as root 2. Enter: setenv LD_LIBRARY_PATH/opt/XRXnps/lib 3. Enter: [/home/rlech/bin]getAttrsTv 4. The program executes and lists valid options. System Guide 8-15

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

Troubleshooting
System Guide
8-15
ep_exception_log and ep_primary_log
These logs contain a list of faults. The ep_exception_log
contains a listing of all logged faults. The ep_primary_log
contains exceptions that are the primary cause of the
problem.
The format of these files is as follows:
Logging Module /t# Absolute Time /t#
Microseconds /t# Instance ID:Module TD /t#
Exception ID /t# Service Code
LPR logs
The following logs are important for troubleshooting problems
in mapping NPS and DocuSP:
LPR logs that contain information related to the LPR
gateway such as missing jobs or communications
problems.
Examples:
/opt/XRXnps/log/XLP/Debug.Log
JPM logs that contain information related to the Job Pool
Manager (JPM). The attribute set by the LPR Gateway
can be checked and verified by looking at this log: /opt/
XRXnps/log/JPM.Debug.Log.
Printing the accounting log
Print the Accounting log to gather information and recover
from various accounting problems. Either the entire
Accounting log or a portion of the log may be printed. This
can be completed on the DocuSP interface in the
[Administration] section.
LP/LPR and the ASCII job tickets
The following procedure is used to verify that the attributes
and options are correct:
1.
Open a terminal and login as root
2.
Enter: setenv LD_LIBRARY_PATH/opt/XRXnps/lib
3.
Enter: [/home/rlech/bin]getAttrsTv
4.
The program executes and lists valid options.