ImageMark Transaction Manager 4.2 - Susan E. Smith

Transcription

ImageMark Transaction Manager 4.2
System Administration
B004-0000-0609
December 1, 2006
The product described in this book is a licensed product of NCR Corporation. Other brand and product names
appearing in this publication are the trademarks or registered trademarks of their respective holders.
It is the policy of NCR Corporation (NCR) to improve products as new technology, components, software, and
firmware become available. NCR, therefore, reserves the right to change specifications without prior notice.
All features, functions, and operations described herein may not be marketed by NCR in all parts of the world. In
some instances, photographs are of equipment prototypes. Therefore, before using this document, consult with your
NCR representative or NCR office for information that is applicable and current.
To maintain the quality of our publications, we need your comments on the accuracy, clarity, organization, and value
of this book.
Address correspondence to:
NCR Waterloo
Attention: Information Engineering
580 Weber Street North
P.O. Box 1611
Waterloo, Ontario, Canada
N2J 4G5
Copyright © 2006
By NCR Corporation
Dayton, Ohio U.S.A.
All Rights Reserved
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Who this Book is For . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
How this Book is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Site-Specific Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Revision Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chapter 1: Start-of-Cycle Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Exporting Suspense Items to the Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Archiving Report Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Check System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Storage Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Free a Storage Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Initialize a Storage Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Associate Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening a Freed Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
17
18
19
20
21
22
23
23
Chapter 2: Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Starting Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Workload by Operator Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Workload by Unit-of-Work Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Workflow Interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a New Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening a New Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening an Existing Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing a Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing a Cycle’s State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a Cycle’s Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ImageMark Transaction Manager 4.2 System Administration
26
28
28
35
43
45
45
46
47
47
48
48
51
3
Contents
Managing Cycle Deadlines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Invalid Posting Dates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exporting Suspense Pool Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exporting IQ Rejects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Aging Out Second Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the Host Entry Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing the SuperMICR Job Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Moving an Entry to a Different Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exporting Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Image Quality Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing the Print Spooler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Redirecting Reports to Print Spooler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Redirecting Reports Back to Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Loading Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Shutting Down Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unloading Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reassigning a Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reassigning a Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restoring a Station to its Original Station Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Implementing Parameter and Environment Variable Changes . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stopping an Auto-Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restarting an Auto-Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Server Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Server Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing Server Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
External Capture Station Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing External Capture Station Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the External Capture Station Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Application Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Loading an Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unloading an Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Work Export Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Export Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Export Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Import Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Import Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the Cycle Number of Import File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Retrying Files and Reloading Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ignoring Import Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying File Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Archive Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Second Source Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Second Source Processing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resubmitting Work to SMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pushing Work Past SMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling Shuffle Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabling Shuffle Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
52
53
55
55
56
57
57
58
59
60
62
64
64
66
68
68
69
71
71
72
72
73
74
74
76
77
77
77
78
78
78
79
79
80
81
81
84
85
85
86
87
87
88
88
89
90
91
93
93
95
95
95
96
Contents
Viewing Item Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Holding Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Workflow Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Chapter 3: Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Starting Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
The Order for Configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Adding and Modifying a Station Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Planning Station Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Viewing Station Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Adding a Station Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Modifying a Station Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Removing a Station Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Adding and Modifying a Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Adding a Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Modifying a Station's Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Switching EPUs or ESUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Removing a Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Managing Storage Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Storage Space Manager Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Initializing a Storage Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Freeing a Storage Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Excluding a Server in a Storage Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Monitoring the State of Storage Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Adding and Removing Application Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Configuring Software by Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Configuring Software by Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Adding and Removing Parameter Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Notes on Adding Parameter Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Configuring Parameter Sets by Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Configuring Parameter Sets by Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Chapter 4: Access Security Manager . . . . . . . . . . . . . . . . . . . . . . . . . 143
Starting Access Security Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing User Workgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Workgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Workgroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a Workgroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a Workgroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Passwords and Security Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing User Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning Permissions by User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning Permissions by Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing Permissions by User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing Permissions by Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
144
145
145
146
146
147
148
148
150
151
151
152
152
154
156
157
5
Contents
Chapter 5: Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Changing Reporting Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How To Change Reporting Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting Reports Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automatically Printing or Saving Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manually Printing End-of-Cycle Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manually Printing Operator Performance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting Generated Reporting Periods for Operator Statistics . . . . . . . . . . . . . . . . . . . . . . .
Viewing Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cancelling Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing End-of-Cycle Reports After the End of the Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Reports Before the End of the Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Auto-Activity Reports on Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Entry Item Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Tray Set Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
If the Printer Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing ATM Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Matched Records Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
End-of-Cycle Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adjustment Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Amount Suspect Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Audit Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automatic Codeline Completion Statistics Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BIE, EIE, and SIE Deadline Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTM Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bundle List Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Daily Corrections Export Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EPU Exception Item Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Forced Adjustment Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Image Quality Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Items Aged Out Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Items Not Received Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Items Pull Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Non-Negotiable Items Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pocket Listing Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recognition Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Second Source Match and Merge Performance Summary Report . . . . . . . . . . . . . . . . . . . .
Truly Missing and Free Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Permission and Login Information Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator Performance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ECU Transport Performance Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EPU and ESU Transport Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Image Quality Review Performance Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reconciliation Operator Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resource Allocation Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auto-Activity Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entry Item Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6
160
161
163
164
165
165
166
168
170
171
173
173
174
174
176
178
180
180
180
181
182
183
183
184
185
193
194
196
200
201
206
208
209
211
211
212
213
213
215
219
219
220
221
221
222
224
225
237
240
241
241
Contents
Tray Set Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MIE Exception Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing the Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Report Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
249
253
254
254
254
Chapter 6: System Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Managing ImageMark Transaction Manager Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Powering Off the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Powering On the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing the System Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Perl Script Interpreter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Organizational Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ImageMark Transaction Manager Access Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing ImageMark Transaction Manager Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Password Registry Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supporting Different Active Directory Organizational Units . . . . . . . . . . . . . . . . . . . . . . . . . .
Domain Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Integrating the Distributed Capture Consolidation Server . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing the Recognition Sub-System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restarting the Recognition Sub-System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Testing the Recognition Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing and Modifying System Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Capacity Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Capacity Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running the Set Stale Date Script with Task Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up a Set Stale Date Script for a Regular Environment . . . . . . . . . . . . . . . . . . . . . . .
Setting Up a Set Stale Date Script for a Time-of-Day Sort Environment . . . . . . . . . . . . . . . .
Advice Notice Export Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Your System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Location and Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resetting the System Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedures for Distributed Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Validating Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing Corrupt EIPS Files on the DS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing Host Entry # for a Duplicate Host Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cleaning Up Capture Files on the DS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cleaning Up Files on the Transports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administration Tasks for a Server Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ImageMark Package Version Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up Diagnostic Alerts for a Server Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting and Stopping ImageMark Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Scheduled Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
258
258
259
260
260
260
261
262
262
268
269
269
270
271
271
272
273
273
273
275
276
278
280
280
282
284
285
286
286
287
288
290
291
292
292
293
295
296
Chapter 7: Backup, Restore, and Recovery Procedures . . . . . . . . . . . 297
Creating a Backup of Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Backup of File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resending Work to the Host Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resending a String Using a Different Host Cycle Number . . . . . . . . . . . . . . . . . . . . . . . . . .
298
299
300
300
7
Contents
Recovering from a Lost BIE Entry on the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recovering from a Lost SIE Transmission to the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recovering from a Lost EIE Entry on the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recovering from Duplicate Entry Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recovering from Duplicate CPCS Entry Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recovering from Duplicate SuperMICR Entry Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Recovery for IDT and TSS Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restarting Host Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing a Restore of Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing the BAP Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
301
303
305
311
311
311
312
313
315
315
Chapter 8: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Starting Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Filtering Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Filtering Messages by Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Filtering Messages by Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Filtering Messages by Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Filtering messages by Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying More Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Acknowledging Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting Freeing and Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reading Capture Error Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Where to Find ImageMark Transaction Manager Error Log Files . . . . . . . . . . . . . . . . . . . . .
Reading Error Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Severity Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting with Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
If a Recognition Sub-System Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Placing CAR Auto-Activity Into Shuffle Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Placing CAR Auto-Activity in Normal Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Identifying SMM Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
If an Activity or Auto-Activity Fails Spontaneously . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Emergency Recovery Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Start-of-Day Backup and Archive Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Emergency Logical Log Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recovering from a System Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
318
319
319
319
319
320
321
321
321
323
324
325
326
327
327
327
330
330
332
332
334
335
337
338
338
338
339
Appendix A: Report Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
End-of-Cycle Report Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator Performance Report Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auto-Activity Report Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MIE Exception Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
342
391
407
424
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
8
Preface
About this Book
This book tells you how to manage the ImageMark Transaction Manager software application.
This book includes instructions on daily start-up procedures, managing workflow, printing and
interpreting reports, managing stations, managing users, installing and configuring components,
and troubleshooting.
Who this Book is For
This book is intended for system administrators, supervisors and anyone else responsible for
managing the day-to-day operations of a system. It assumes that you have attended the ImageMark
Transaction Manager System Administration course.
This book also assumes that you are familiar with over-the-counter proof-of-deposit operations as
well as with the operations described in the ImageMark Transaction Manager Operations course.
You also need to be familiar with administering Windows systems and with the CPCS or SuperMICR
mainframe check processing system.
How this Book is Organized
This book has the basic and most frequently used tasks first, such as the start-of-day procedures.
Following these are chapters that outline the step-by-step procedures of how to use various utilities
to do basic tasks. Less frequent administrative tasks are covered in later chapters of the book.
Conventions
Within the procedures described in this book, conventions help you to identify different types of
information.
Bold
Bold identifies anything you must select, choose, run, press, or type. For example:
Type dbscrpt, then press Enter.
9
Preface
Chevrons
Chevrons (>) indicate a series of menu selections. For example:
Choose File > Import > Formats.
Italics
Italics identify a placeholder that must be replaced with your own specific information. For example:
device=c:\path\7780mint.sys type=H.
Italics are also used for emphasis.
Notes, Tips, Important, Cautions, Warnings
Notes, cautions, and warnings alert you to important or critical information. Each is displayed in a
different way:
Note: Notes contain information that has special importance.
*
Tip: Tips contains useful advice for the user on tasks or procedures.
!
Important: Important text contains information to which the reader should pay close attention.
Caution: Cautions alert you to procedures or conditions that could damage equipment or data.
Warning: Warnings alert you to procedures or conditions that could cause personal injury.
Related Information
To administer an ImageMark Transaction Manager system, you may need, in addition to this book,
the following ImageMark Transaction Manager publications:
10
!
ImageMark Transaction Manager 4.2 Parameter Generation: Application Generator
!
ImageMark Transaction Manager 4.2 Parameter Generation: ASCII Files
!
ImageMark Transaction Manager 4.2 Parameter Generation: Host Emulator
Preface
Site-Specific Procedures
Like every other ImageMark Transaction Manager system, your system has been customized to
meet site-specific requirements. Hence, some of the procedures in this book may have to be adapted
to meet your site’s needs. In addition, to meet your site’s specific requirements, you may have to
carry out other system administration procedures that fall outside the scope of this book.
11
Preface
12
Revision Record
Document Title
December 1, 2006
Page No.
Remarks
All
First release for ImageMark Transaction Manager 4.2.
13
Revision Record
14
1
Start-of-Cycle Procedures
To prepare your system so that operators can process documents, follow the procedures outlined
in this chapter:
!
Export the suspense items to the archive (Repass Capture only).
!
Print the previous work cycle’s reports.
!
Archive the report and other files, if your site requires.
!
Check for messages in Diagnostics.
!
Free a storage space.
!
Initialize the storage space.
!
Associate the cycles you wish to use in the storage space.
!
Start your new work cycle.
Note: To carry out the procedures in this chapter, and many of your other tasks, you must have an
ImageMark Transaction Manager administrator user account (imadmin) on the Base
Application Processor (BAP). Unless otherwise stated, procedures assume that you are
logged on to the BAP as imadmin.
15
Chapter 1: Start-of-Cycle Procedures
Exporting Suspense Items to the Archive
Exporting Suspense Items to the Archive
For Repass Capture processing, you may need to archive the items in the Suspense Pool before
the system is reinitialized (otherwise the data in the databases will be lost and there will be no record
of the physical item in the database).
Use Application Manager to export Suspense Pool items to the archive. See “Exporting Suspense
Pool Items” on page 55.
16
Printing Reports
Printing Reports
To print the required reports for the previous day’s work:
1
Open Application Manager.
2
Choose View > Work In Progress.
The system displays the Work In Progress dialog.
Work in Progress Dialog
3
You can use the Interaction filter to ensure that all units of work are At End.
If any units of work have not completed workflow, locate where the work is held up. See
“Managing Workload by Unit-of-Work Type” on page 35 and “Managing Activities” on page 71.
4
Ensure the state of the cycles containing the work are set to “End”. To change the cycle state,
see “Changing a Cycle’s State” on page 48.
5
Use the Report utility to print the reports required for your site. See Chapter 5, “Reports”.
!
If your site makes use of the Automatic Report Print utility, simply open the Report utility
and choose File > Automatic Print.
17
Archiving Report Files
Archiving Report Files
Archive the report files that your site policy requires. For example, you may need to archive some
or all of the End-of-Cycle reports that ImageMark Transaction Manager saves to the
%IMAGEMARK_ROOT%\opt\siips\archive directory on the BAP.
!
18
Important: The disk space allocated for the %IMAGEMARK_ROOT%\opt\siips\archive directory
on the BAP is not automatically cleaned up. You should clean this directory regularly
so that there is enough space for reports.
Check System Messages
Check System Messages
Check for system messages in case problems arose from the previous work cycle:
1
In Task Manager, choose Diagnostics from the Utilities list.
The system displays the Diagnostics window.
2
Acknowledge all outstanding messages and take the suggested corrective action. See Chapter
8, “Troubleshooting,” for more information on handling error messages.
3
Minimize Diagnostics.
If error messages are received during the day, this icon will flash and beep to alert you. A
Messages button in the Diagnostics window will also flash to alert you of new messages.
4
Return to Application Manager.
5
Keep the Application Manager window open throughout the day to monitor and manage
workflow, as described in Chapter 2, “Application Manager.”
19
Storage Spaces
Storage Spaces
A storage space is a place on the system where all the work carried out by ImageMark Transaction
Manager is stored. It is an administration tool that provides a virtual re-usable container for the logical
grouping of production data spanning multiple databases across all servers (BAP/DAP/DS) in the
system. A specific storage space contains all production information related to any cycles assigned
to it, and it provides a mechanism to retain or delete that entire set of data as required by the bank.
Before you can begin a new work cycle, you must ensure there is space on the system to store the
new work. To make space on the system, a storage space must be free of any previously completed
work and must be initialized so it can process the new work.
The freeing and initialization processes are supported by two or more storage spaces on the system.
To utilize space on the system, proceed in one of the following ways as you see appropriate:
20
!
Initialize a storage space that is not in use and is marked with a status of “Free”. See “Initialize
a Storage Space” on page 22.
!
Free a storage space from a previously completed work session to make room for the new work
cycle session. See “Free a Storage Space” on page 21.
Free a Storage Space
Free a Storage Space
When you free a storage space, you also free the cycles associated with the storage space.
To free a storage space, ensure that the cycles associated with the storage space have a status of
“End”. If they do not, set the cycle to the “End” state using Cycle Manager. See “Ending a Cycle” on
page 50 for instructions.
Free the storage space using Storage Space Manager. See “Freeing a Storage Space” on page 124
for instructions on how to so this. When the storage space has been successfully freed, its state will
change to “Free”.
Once a storage space has been freed, you can initialize the storage space. See “Initialize a Storage
Space” on page 22.
If freeing fails and continues to fail, see “Troubleshooting Freeing and Initialization” on page 326 for
troubleshooting information.
21
Initialize a Storage Space
Initialize a Storage Space
When you initialize a storage space, you are enabling the storage space to receive work.
If a storage space is marked with a status of “Free”, it is ready to be initialized at any time.
To initialize a storage space, see “Initializing a Storage Space” on page 122. When the storage space
has been successfully initialized, its state will change to “Initialized”.
Note: In Cycle Manager, you will notice that the cycles you freed from the storage space are marked
with a status of “Free”. You can associate these cycles with your storage space.
If initialization fails and continues to fail, see “Troubleshooting Freeing and Initialization” on page
326 for troubleshooting information.
22
Associate Cycles
Associate Cycles
When the storage space has been initialized, associate (or add) the cycles you want to use in your
session with the storage space.
When you free a storage space, cycles previously associated with the storage space are
disassociated from the storage space and freed of any previous data, as marked with a status of
“Free” in Cycle Manager. Once your storage space has been initialized, you can associate (or add)
the cycles of your choice to the available or “Initialized” storage space.
Note: You can also add new cycles to the storage space at any time when more cycles are needed.
If you already have cycles that are free in the storage space, reuse them to keep the Storage
Space Manager from becoming cluttered with unused cycles. To add cycles to a storage
space, see “Adding a New Cycle” on page 45. If you have added a new cycle, it must also
be opened. For instructions, see “Opening a New Cycle” on page 46.
Opening a Freed Cycle
In order to use the freed cycles, they must be opened and modified.
To open an existing cycle:
1
Choose Cycle > Manager....
The system displays the Cycle Manager dialog. The Cycle Manager lists the cycles and their
status in the system.
Note: You can only open a cycle that has a “Free” status.
Cycle Manager Dialog
2
Select the cycle from the list, and choose Open....
23
Associate Cycles
The system displays the Open Cycle dialog.
Note: The cycle number cannot be modified as the cycle already exists and is only being opened.
Open Cycle Dialog
3
Set the date in the Posting date field to today’s date, or to the appropriate posting date.
4
Set the deadline in the Posting deadline field to the desired time.
5
Select the storage space you want to store the cycle in from the Storage space list box.
6
Select a region name from the list box if different from the current setting.
7
Choose OK.
The cycle is opened and ready to receive work.
You may now begin your work session. If you want to run the new cycle session from another
instance of the application, see “Starting Application Manager” on page 26.
24
2
Application Manager
This chapter describes how to use Application Manager to manage the flow of documents and data
through the system.
The chapter describes how to start Application Manager and how to use Application Manager to
accomplish the following tasks:
!
manage the flow of work through the system
!
manage cycles
!
manage report printing
!
manage the system activities running on the stations
!
reassign workstations to balance workload, reduce bottlenecks, and make processing more
efficient
!
manage application instances
25
Chapter 2: Application Manager
Starting Application Manager
To start Application Manager:
1
In Task Manager, choose Application Manager from the Utilities list.
The system displays the Application Manager window.
Application Manager Window
2
Choose Application > Display....
The system displays the Display Application dialog.
Display Application Dialog
3
From the Loaded copies of application list, select the application instance that you want to
display.
The system updates the Application Status buttons to show whether this copy is currently Active
or Inactive.
4
26
Choose OK.
The system opens the Application Display window with the name of this application instance
displayed in the title bar.
Application Display Window
27
Managing Workload
Managing Workload
Once you have an Application Display window open on your running copy of ImageMark Transaction
Manager, you can open two different windows that let you view and manage workload either by
activity (Codeline Completion, Amount Keying, and so on) or by unit-of-work (entry, tray set, and so
on).
Managing Workload by Operator Activity
To manage workload by activity, choose View > Load.
The system displays the Load dialog.
Load Dialog
The Load dialog shows how much work is waiting to be processed or is being processed at each of
the operator-based activities. You can use this information to identify bottlenecks and balance
resources to match workloads.
The Load dialog is divided into four separate tabs:
28
!
Summary
!
Operators
!
Volume
!
Completion
Managing Workload
Notes: !
The Summary, Operators and Completion tabs present special information for the autoassigned activities. By default, the auto-assigned activities are Codeline Completion,
Amount Keying, Balancing and Expert Balancing; however, during system
configuration, auto-assign can be turned off for one or more of these activities and turned
on for additional activities.
!
Parameters control the display of the Load dialog. Unused roles can be suppressed
from appearing in the Load dialog by changing parameters in the
MANAGE_LOAD_PARMS keyword. Conversely, roles can also be extended to appear
in the Load display by changing the parameters in the EXT_MANAGE_LOAD_PARMS
keyword. For more information, see ImageMark Transaction Manager Parameter
Generation: ASCII Files. However, if work is available at a role, that role will show up
regardless of your site’s parameter settings.
29
Managing Workload
Summary Tab
The Summary tab provides the following information for all activities (except Advice Notice), including
remote activity types:
!
Volume: the number (in thousands) of documents being processed or waiting to be processed
!
Throughput: the rate (in thousands per hour) at which documents are currently being processed
!
Operators: the number of operators working at each of the activities
Note: Remote activity types listed on this screen begin with the letter R (e.g., Remote Expert
Balancing is listed as REBAL).
In addition, the Summary tab shows the following information for the auto-assigned activities:
!
Optimal: the optimal distribution of operators across the keying activities given current resources
and queued volumes of work at the roles
For Advice Notices, the Summary tab provides the following information:
!
Total: the current number of advice notices in the system
!
Printed: the number of those notices that have been printed
Select any activity to display detailed operator information in the window on the right:
!
Operator name and keying rate for keying activities
!
Station name, operator name and throughput for other activities
Summary Tab
30
Managing Workload
Workload Indicators
(+) and (-) indicators in the Optimal column can be very helpful for managing workload.
!
(+): You may want to move operators to this activity from other activities to process the work
more quickly. For example, (+3) means three more operators are required.
!
(-): You may be able to move operators from this activity to another one where work is being
processed too slowly. For example, (-1) means one operator is available for reassignment.
Note: These indicators are designed only to give you a general idea of where bottlenecks may be
occurring and where extra resources may be available. You must still rely on your own
experience and judgment when deciding how to deploy resources and balance workload.
Identifying Bottlenecks
The volume statistics in the Load dialog can also help you to identify the causes of bottlenecks. To
make the most of this information, you must also apply what you learned about workflow in your
ImageMark Transaction Manager System Administration course.
Suppose, for example, that the Load dialog shows an unusually large volume of work accumulating
for Codeline Completion operators. Knowing that the Recognition Subsystem lies upstream from
CLC in the workflow, you may want to check whether the Recognition Subsystem in this workgroup
has failed.
31
Managing Workload
Operators Tab
The Operators tab provides the following information on operators currently signed onto an autoassigned activity:
!
the activity name with the current throughput for the activity in parentheses
!
Operator: a list of operators at each activity with an indicator beside operators whose stations
are currently idle
!
Rate: the workflow throughput for the activity, in documents per minute (based strictly on batch
size throughput, not item keying rate)
!
Total: the total number of operators at each activity with the maximum number of operators that
the system will recommend to you for a given activity (you can set this value based on the
number of operators available)
!
the system's recommendation on whether to add or remove operators (to improve overall system
efficiency)
Select an operator to display more detailed information about that operator. This pop-up dialog
includes operator login, operator ID, operator display name, name of station currently logged into,
session start time, and effective throughput for the current activity and for the other auto-assigned
activities that the operator has performed.
Operators Tab
32
Managing Workload
Volume Tab
The Volume tab displays the following information:
!
a graph that shows the volume of work (in thousands of items) at each activity
!
Count: the number of units-of-work at each activity
!
Value: the dollar value of the work at each activity in $1000’s of dollars
You can narrow your view by setting the following filters:
!
Entry Number: view work according to its entry number
!
Parameters: view work according to its parameter set or bank name
!
Servers: view work based on the server on which it was captured
Volume Tab
33
Managing Workload
Completion Tab
The Completion tab displays how much time remains before the rest of the work in the system is
processed by Expert Balancing. The information includes:
!
a graph that shows the time required to process the remaining work for each of the keying
activities
!
Percent: the percentage of all the work in the system that was processed at each of the keying
activities. This is calculated as the number of items in batches presented to the Expert Balancer,
divided by the total number of items in all batches captured
!
Estimated Completion Time: the estimated time at which all work will be completed. The system
also takes into account the worktype of the units-of-work queued at each role when calculating
the estimated completion time.
!
Vol., UOW and Time: the volume of work, number of units-of-work, and time remaining to
complete the work at the selected stage two activity types
!
Total and Printed: the total number of Advice Notices and the number already printed
Completion Tab
34
Managing Workload
Managing Workload by Unit-of-Work Type
You can view and manage workload by unit-of-work type and sub-type. Here are examples of some
situations where this can be helpful:
!
If work has not reached the ESU in a sufficient amount of time, view the current entry by tray,
to see where the tray units-of-work have become stuck in the workflow.
!
If reports are not printing through the Entry Item Report automatic report program, view the
current entry by Document Data Record and Image (DI), to see if some work may be stuck in
Balancing (BAL DI IN).
To manage workload by unit-of-work, choose View > Work In Progress.
Work In Progress Dialog
The Work In Progress dialog shows all of the work currently in the system. This dialog has several
list boxes and buttons to filter the work. These help you find specific units-of-work when the system
is processing a lot of documents. In general, you will want to select a unit-of-work type that lets you
look at workload from a high enough level that you don’t get overwhelmed by detail, but from a low
enough level that you don’t miss important information.
To view a specific type of work, you can filter the work by cycle, entry number, state (e.g., On Hold),
parameter set, and by:
!
Unit-of-Work Type, where:
!
Entry shows all work currently in the system.
!
Tray Set shows all tray sets currently in the system.
!
Tray shows all trays currently in the system.
35
Managing Workload
!
DDR with Images shows all of the batch units-of-work currently in the system. DDR unitsof-work are internal representations of documents, and do not carry an image by
themselves. The DDR with Images unit-of-work includes the image.
Note: When you select this work type, a new column called Large Batches is displayed. Batches
of this type generally require more time to balance than regular batches. As a result you
should consider changing the priority of large batches to high. See “Changing Work Priorities”
on page 38.
!
*
!
DDR shows all batch units-of-work currently in the system that have been successfully
balanced.
!
Advice Notice shows all advice notice letters currently in the system.
Unit-of-Work Sub-Type, where:
!
All shows all of the units-of-work in the current unit-of-work type
!
For trays and tray sets only, Input Ready shows only those units-of-work that are ready to
be processed by the ESU, Input Processed shows only those units-of-work that have been
processed by the ESU, Output shows only those units-of-work that have been created by
the ESU.
!
For DDR with images only, Batch shows only the batch units-of-work that have been
processed at the EPA. The displayed batch units-of-work could be at Amount Keying,
Codeline Completion, or Balancing. Transaction shows the status and location of deposits
with items that are subject to review for negotiability and holds.
!
The Sub-Type column tells you what unit-of-work subtype applies to the work, including:
!
A – all
!
DRA – DRA Transaction
!
N – normal
!
O – offline
!
P – prime
Tip: Sub-type options listed in this pull-down filter vary depending on type of work selected.
!
Interaction, where:
!
In Progress shows all work currently working its way through the system.
!
At end shows all work currently sitting at the end of workflow.
The system updates the Work In Progress dialog to show all the units-of-work that meet the criteria
you specify. (For example, if you want to focus on just the work “In Progress” rather “All” work in the
system, then you could choose the appropriate Interactions setting to filter out work already
considered to be “At end”.)
36
Managing Workload
Viewing Unit-of-Work Details
To view the details of a unit-of-work:
1
2
Select the Unit-of-work type and Unit-of-work sub-type from the lists, then choose UoW Details.
The system displays the Unit of Work Details dialog. The fields displayed in this dialog vary
depending on the Unit-of-work sub-type chosen.
UoW Details Dialog
37
Managing Workload
Changing Work Priorities
All of the work flowing through the system is sent from process to process on a first-in, first out basis.
In the priority scheme, this is called normal priority. But sometimes you may need to change a unitof-work’s priority, for example, to push it through the system to meet a deadline.
Note: When changing priorities, remember to apply your knowledge of workflow. For example,
raising the priority of a particular DI unit-of-work won’t necessarily get work through the Entry
Item Reports (EIR) auto-activity more quickly, because this auto-activity is triggered only
when the entire entry is processed.
To change the priority of a unit-of-work:
1
2
Select the unit-of-work from the list, then choose Set Priority.
The system displays the Set Priority dialog.
Set Priority Dialog
3
4
Select a priority from the Set Priority dialog:
!
High: high-priority work gets processed before normal and low priority work. To push a DI
unit-of-work through the system, you might change its priority from normal to high.
!
Normal: normal-priority work gets processed before low priority work, but after high priority
work. All units-of-work are automatically set to normal priority when they are created in the
system.
!
Low: low-priority work will be processed after all normal and high priority work is finished.
Choose OK.
The system changes the selected unit-of-work’s priority.
38
Managing Workload
Holding Back Work
Sometimes you may want to hold units-of-work at their current location in workflow instead of letting
them be passed on automatically. For example, say the transport operator ran work on the EPU that
should have gone to some other department, so now you realize that you want to abandon
processing that work in TM. Another example: you are in testing mode, and there's a particular batch
of work you want to stay put for some time while you run other work, then come back to it later.
Note: You cannot put units of work on hold that are already in process.
Caution: When putting work on hold, be careful to apply your knowledge of workflow to avoid
unintended results. Here are two examples:
!
If you put a balanced DI unit-of-work on hold while it is at the Copy-to-AP auto-activity, this will
prevent the BIE auto-activity from sending data to the host application and releasing the entry
to the EIR auto-activity.
!
If you put an entry on hold at CON, this will not stop tray and tray set units-of-work from
proceeding to the ESU.
To place work on hold:
1
2
Select the unit-of-work from the list, then choose Hold.
3
At the confirmation dialog, choose Yes.
The system changes the state of the selected unit-of-work at its current position in the system
to On Hold. No further processing will be done on it until you release it.
39
Managing Workload
Releasing Work
To release a held unit-of-work and resume its processing:
1
2
Select a held unit-of-work from the list, then choose Release.
3
The system changes the state of the selected unit-of-work to Avail. The system resumes
processing the unit-of-work.
Resending Work to the Image Archive
To resend ETI batches or entries to the image archive (during disaster recovery, for example):
1
From the Application Display window of Application Manager, choose View > Work In
Progress.
Work in Progress Dialog
2
Select the entry or batch (that is to be resent to the archive) from the list, then choose UoW
Details.
The system displays the Unit of Work Details dialog.
40
Managing Workload
Unit of Work Details Dialog
3
Choose Resend.
The system displays the following dialog, listing all units of work that are available to resend.
Resend UoW Dialog
41
Managing Workload
4
Select the unit of work to resend (one only), then choose OK.
The system displays the following dialog:
Resend Confirmation Dialog
5
Choose Yes.
The system resends the unit of work to the image archive and returns you to the Unit of Work
Details dialog.
42
Managing Workload
Viewing Workflow Interactions
Occasionally, the best way to analyze workflow or troubleshoot workflow problems is to look at the
interactions that pass units-of-work from one activity to the next.
Application Manager gives you two ways of viewing these interactions:
!
Choose an activity and view all the units-of-work inbound to and outbound from it (in this context,
the units-of-work are also known as interaction components).
!
Choose one interaction from a list, and view all the activities sending work to or receiving work
from this interaction.
Viewing Interactions by Activity
To view all the units-of-work inbound to and outbound from one particular activity:
1
Choose Workflow > Activity.
The system displays the Activity Routing Table dialog.
Activity Routing Table Dialog
2
Select an activity from the Activities list.
The system updates the Interaction Components, IN/OUT, and Interaction columns to show the
information for the activity that you selected.
43
Managing Workload
Viewing Activities for an Interaction
To view all the activities sending work to or receiving work from a particular interaction:
1
Choose Workflow > Interaction.
The system displays the Interactions Routing Table dialog.
Interactions Routing Table Dialog
2
Select an interaction from the Interactions list.
The system updates the window to show the information for the interaction that you selected.
44
Managing Cycles
Managing Cycles
The largest physical unit-of-work in the system is a cycle. Typically, a cycle comprises all the entries
processed at a site on a particular day or during a particular time period. But the definition of a cycle
can be customized. For example, the site may treat a cycle as the equivalent of one deposit date.
So, if today the site were processing checks that must be deposited by the bank on July 3rd, all of
those items would be grouped into one cycle.
Adding a New Cycle
If you need to create a new cycle at any time:
1
Choose Cycles > Manager....
The system displays the Cycle Manager dialog. The Cycle Manager lists each cycle, their
corresponding host cycle, the storage space that the cycle is located in, and the cycle’s status
in the system.
2
Type a new cycle number in the Cycle number box, then choose Add.
The system creates the cycle with a status of “Free” and is added to the Cycles currently in the
system list.
45
Managing Cycles
Opening a New Cycle
In order to use the new cycle, it must be opened. To open a new cycle at any time:
1
Select the new cycle from the list of cycles, and choose Open....
Open Cycle Dialog
!
If your system is configured for time-of-day sort processing, the Open Cycle dialog displays
the default posting deadline beneath the posting date.
!
If the default posting date is invalid, the posting deadline will not contain any data. To set
the posting date, enter the desired date in the Posting Date fields. For information about
invalid dates, see “Managing Invalid Posting Dates” on page 53.
!
If your system has enabled the HOST_CONNECT_PARMS keyword, the Open Cycle dialog
displays the region list box.
Note: The host cycle number defaults to the same number as the cycle number. To modify the host
cycle number, use the Cycle Manager. See “Modifying a Cycle’s Attributes” on page 51.
2
3
Set the desired time in the Posting deadline field.
4
5
If you have set your system to display the regions, select a region name from the list box.
6
Choose Open.
The system opens the new cycle.
46
Managing Cycles
Opening an Existing Cycle
When you free a storage space in your start of day procedures, you also free the cycles within that
storage space. In order to use these cycles, they must be opened and modified.
To open an existing cycle:
1
Ensure a storage space and its cycles are free. To do this, see “Freeing a Storage Space” on
page 124.
2
The system displays the Cycle Manager dialog. The Cycle Manager lists the cycles and their
status in the system.
Note: You can only open a cycle that has a “Free” status.
3
Select the “Free” cycle from the list, and choose Open....
4
5
6
7
Select a region name from the list box if different from the current setting.
8
Choose OK.
The cycle is opened and ready to receive work.
Removing a Cycle
A cycle may be removed from the system when:
!
All the units-of-work belonging to the cycle have been processed and deleted from the system.
!
The cycle’s state has been set to “Free”.
Note: Some system administrators choose not to remove free cycles from the system, since they
are not consuming any resources. They simply leave these cycles free until such time as
they want to open them.
To remove a cycle:
1
Set the cycle you wish to remove to the “Free” state. See “Freeing a Storage Space” on page
124 for more information.
2
The system displays the Cycle Manager dialog.
3
Select the cycle, then choose Remove.
4
At the confirmation dialog, choose Remove Cycle.
The system removes the selected cycle from the cycles list in Cycle Manager.
47
Modifying Cycles
Modifying Cycles
You may need to modify a cycle for various reasons:
!
You may need to change the host cycle number if you encounter problems at BIE or SIE, and
need to resend work with a different number.
!
You may need to change the cycle’s state when all work for the cycle has been processed and
you wish to delete the cycle.
!
You may need to change the processing date so that you can process work from yesterday to
recover from a software failure.
Changing a Cycle’s State
To modify a cycle’s state, choose Cycles > Manager....
The system displays the Cycle Manager dialog, which lists the currently defined cycles.
48
Modifying Cycles
Opening a Cycle
You can only open cycles with a state of “Free” or “Closed”. To open a cycle:
1
Select the cycle you wish to open, then choose Open....
Open Cycle Dialog
2
3
4
Note: If the selected storage space has a state of “In Use”, the system will prompt a warning dialog.
You may continue on with the current storage space or cancel to select another storage
space.
5
If your system is configured to display a region selection field, select a region name from the
list box (if different from the current setting).
6
Choose Open.
The system opens the cycle. The state of the cycle in Cycle Manager changes to “Open”.
Closing a Cycle
Close a cycle when you are no longer capturing work for that posting date. You can reopen the cycle
later if you choose to add more work to the cycle. You can only close cycles that have a state of
“Open”.
!
Important: To avoid confusion or possible selection errors by EPU operators, it is usually best to
have only one open cycle for them to choose.
To close a cycle:
1
Select the cycle you wish to open, then choose Close Cycle.
The system sets the cycle’s state to “Closed”.
49
Modifying Cycles
Ending a Cycle
End a cycle if you have no more work to put into the cycle and all the reports have been completed.
To end a cycle, the work within the cycle must also be completed or be at “End”.
To end a cycle:
1
Select the cycle you wish to end, then choose End.
The system sets the cycle’s state to “End”.
Reopening a Cycle
A closed cycle must be reopened in order to continue to add more work to the cycle. You can only
reopen cycles that have a state of “Closed”. To reopen a cycle:
1
Select the cycle you wish to reopen, then choose Reopen.
The system sets the cycle’s state to “Open”.
50
Modifying Cycles
Modifying a Cycle’s Attributes
You can only modify cycles that have a state of “Open” or “Closed”. You can change the following
cycle attributes:
!
host cycle number
!
posting date
!
posting deadline
!
region name
To modify a cycle:
1
The system opens the Cycle Manager.
2
Select a cycle from the list, then choose Modify....
The system displays the Modify Cycle dialog.
Modify Cycle Dialog
3
To change the host cycle number, type a new number in the Host cycle number field.
4
To change the posting date, set the date in the Posting date field to today’s date, or to the
appropriate posting date.
5
To change the posting deadline (if set on your system), set the desired time in the Posting
deadline field.
6
To change the region name (if set on your system), select a region name from the list box.
7
Choose Save.
The system modifies the cycle information.
51
Modifying Cycles
Managing Cycle Deadlines
In a time-of-day sort environment, BIE transmission does not take place until the ESU operator
selects the prime pass sort pattern for that entry.
As the posting deadline nears, if there are items that must still be sent to the host application, the
system generates a warning. If the posting deadline is reached and BIE has still not received the
necessary entries, BIE automatically selects the default sort pattern for the next deadline and
uploads its data to the host application. After this occurs, operators can no longer select a sort
pattern.
If you do not want automatic BIE transmission to occur, you can modify the default posting deadline
to allow the ESU operator the flexibility to select an ESU sort pattern. You must modify the posting
deadline prior to BIE transmission. Once BIE transmission takes place for an entry, the ESU operator
can no longer select a sort pattern for that entry. The sort pattern defaults to the same sort pattern
that BIE used.
Changing the values in the Posting deadline fields overrides, for that cycle, the posting deadline
specified for the processing day in the POSTING_DEADLINE keyword. You should ensure that your
changes allow the work to be processed and uploaded to the host application on time.
To modify the posting deadline, see “Modifying a Cycle’s Attributes” on page 51.
Notes: !
!
52
The hour is measured from 00:00 on the processing date for the current cycle.
If you modify the process date, the posting deadline changes to the default deadline for
the specified day.
Modifying Cycles
Managing Invalid Posting Dates
The invalid posting date utilities allow you to define which posting dates are invalid. Examples of
invalid posting dates include weekends and holidays for most banks. Defining these dates prevents
the system from creating a cycle with an invalid posting date.
You can either specify a single invalid posting date, or you can specify the name of a file that contains
multiple invalid posting dates.
Creating Invalid Posting Dates
To create an invalid posting date:
1
Change to the directory on your system for these types of files. For example, this might be a
directory under %IMAGEMARK_ROOT%\opt\siips\home or %IMAGEMARK_ROOT%\home.
2
Create a file that contains the invalid cycle posting dates.
Note: You only need to create this file if you intend to add multiple dates to the database. To add
a single date to the database, see step 3.
a
Create a new text file or use the sample dates configuration file in:
%IMAGEMARK_ROOT%\opt\siips\imdates.sample
The syntax of this configuration file is as follows:
# This is a sample ImageMark Invalid Cycle Posting Dates configuration file.
# Blank lines or lines beginning with a # character are ignored
# Invalid cycle posting dates can be in any Month, Day, Year format supported
by Informix
# i.e. 11/04/1999, 11041999, Nov. 4, 1999
11/04/1999
11041999
Nov. 4, 1999
Note: Invalid posting dates can be in any Month, Day, Year format that is supported by Informix.
For example any one of the following is valid: 11/04/2001, 11042000, Nov. 4, 2000.
b
Enter all the invalid posting dates that you would like to add to the database.
3
Change to the %IMAGEMARK_ROOT%\bin directory.
4
Run imloaddates -f filename | -p postingdate
where:
!
-f filename is the name of the file that contains the list of invalid cycle posting dates
!
-p postingdate is a single invalid cycle posting date
The system displays a status line for each date processed. There are three possible status lines:
01/01/2000
Date Loaded
01/02/2000
Already Exists
53
Modifying Cycles
01/03/2000
Failed
Note: If the import fails because of a badly formatted date, the utility will continue to add new entries
to the database. However, if the import fails for any other reason, the utility will terminate and
not process any further dates.
Deleting Invalid Posting Dates
To delete an invalid posting date from the database:
1
2
Run imdeletedates -f filename | -p postingdate | -t olderthan
where:
!
-f filename is the name of the file that contains the list of invalid cycle posting dates to be
deleted from the database
!
-p postingdate is a single invalid cycle posting date to be deleted from the database
!
-t olderthan is number of days before the current day’s date that are to be deleted from the
database. For example, to delete the records from yesterday and the day before, you would
enter 2. To delete only yesterday’s date, you would enter 1.
The system displays a status line for each date processed. There are two possible status lines:
01/01/2000 Date Deleted
01/02/2000 Failed
Note: If the deletion fails because of a badly formatted date, the utility will continue to delete entries
from the database. However, if the deletion fails for any other reason, the utility will terminate
and not process any further dates.
Displaying Invalid Posting Dates
To display invalid posting dates:
1
2
Run imdisplaydates.
The system displays all invalid dates in the database from oldest to newest. The dates are
displayed as MM/DD/YYYY.
54
Modifying Cycles
Exporting Suspense Pool Items
You can export suspense items to the archive prior to reinitializing the databases (otherwise, the
document data and image for the items will be lost and you will have no record of the items). When
you export suspense items to the archive, the document data and images for the items will be put
into the archive.
To export suspense pool items:
1
Choose Cycles > End of Cycle > Export Unresolved Suspense > Cycle number
where Cycle number is a list of all cycles with a state of “Closed” or “End”. Choose the cycle
number you want to export unresolved suspense items to.
2
The system exports any unresolved suspense items to the archive.
Note: Exporting unresolved suspense items creates a file that can be sent to an archive through
ImageMark Passport.
Exporting IQ Rejects
To export an Image Quality Reject:
1
Choose Cycles > End of Cycle > Export Image Quality Reject.
55
Modifying Cycles
Aging Out Second Source
The probability of a second source record being matched to an item decreases over time. Therefore
to improve database efficiency, you should periodically delete second source records.
Note: If the EXPORT_SS_UNMATCHED keyword is active, the records will be exported, as well
as aged out.
To delete second source records:
1
Choose Cycles > End of Cycle > Age Out SMM Records....
The system displays the Age Out Second Source Records dialog, which lists the posting dates
for unmatched second source records.
Age Out Second Source Records Dialog
2
Select the posting date you want to age out. The associated PSet name is also displayed in the
list.
3
Select the cycle you want to associate with the aged out records, then choose Age Out.
Note: Only cycles with a state of “Open”, “Closed” or “End” will be displayed in the Associate with
this cycle list box.
4
The system deletes the selected second source records.
Note: Exporting second source records creates a file that can be sent to an archive through
ImageMark Passport.
56
Modifying Entries
Modifying Entries
You can modify the entry information without directly modifying the cycle the entry is located in.
Occasionally, you may want to move entries to a different cycle or change the host entry number
for an entry.
Changing the Host Entry Number
To change the host entry number, do the following:
1
Choose Entry > Host Entry.
The system displays the Host Entry Number dialog, which contains a list of the currently defined
cycles.
Host Entry Number Dialog
2
From the Cycles list, select the cycle for the entry that you want to modify.
The system displays a list of the entries for the selected cycle.
3
From the Entry Number list, select the entry for the host entry that you want to modify, then
choose Change....
The system displays the New Host Entry Number dialog.
New Host Entry Number Dialog
4
Obtain a new set of tracer documents with an unused entry number.
57
Modifying Entries
5
Type the new number for the Host entry, then choose OK.
The system displays the Host Entry Number dialog with an ‘M’ beside the entry number in the
Modified column.
Note: After the physical tracer documents in the entry have been processed at the ESU, replace
the original physical tracer documents with the new tracer documents.
Viewing the SuperMICR Job Number
For a SuperMICR application, you can view the job numbers that the host system assigned to the
entries that the system sent to it.
To view the SuperMICR job number:
1
Choose Cycles > Host Entry.
The system displays the Host Entry Number dialog.
SuperMICR Host Entry Number Dialog
2
From the Cycles list, select the cycle for the entry that you want to view.
The system displays a list of the entries for the selected cycle.
58
Modifying Entries
Moving an Entry to a Different Cycle
If an EPU operator selects the wrong cycle for an entry, you can correct the error by moving the
entry to a different cycle.
Note: You can only do this if the entry has not started processing at the ESU.
To move an entry to a different cycle:
1
Choose Entry > Entry Cycle.
The system displays the Entry Cycle dialog.
Entry Cycle Dialog
2
Select the original cycle.
The Entry Number list displays all entry numbers for that cycle.
3
Select the entry number that is to be moved to a different cycle, then choose Change....
The system displays the Change Entry Cycle Number dialog.
Change Entry Cycle Number Dialog
59
Modifying Entries
4
Select the cycle you want to use, then choose OK.
The system displays the Entry Cycle dialog with the new cycle number next to the entry number.
T
Note: The system displays the Cannot Change Processed Entry dialog if the entry has already
begun processing at the ESU. Choose OK to return to the Entry Cycle dialog. The entry you
chose cannot be moved to another cycle.
Notes: !
!
Trays from this entry cannot be stacked at the ESU.
Trays from this entry are displayed at the ESU under the Original Cycle.
A supervisor alert is logged to record the fact than an entry has been moved to a different cycle.
This alert contains the entry number, the original cycle number, and the new cycle number.
Exporting Entries
To export a normal entry unit of work:
1
From the Application Display window, choose View > Work In Progress.
2
For the Unit of work type, choose Entry.
The system displays only the Entry units of work in the table.
3
For the Unit of work sub-type, choose Normal.
The system displays only the Normal Entry units of work in the table.
4
Select the Normal Entry unit-of-work (that is to be exported), then choose UoW Details.
The system displays the Unit of Work Details screen.
60
Modifying Entries
Unit of Work Details: Exporting an Entry
5
Choose Export.
The system creates a duplicate Entry unit of work to the one selected, with a UoW Subtype of
“Export”.
61
Viewing Image Quality Status
The Unit of Work Details screen displays the Image Quality Status of the selected unit of work. These
are the possible statuses:
IQ Status Value
What It Means
0
all items are good image quality
1
contains Image Quality rejects
2
contains Image Quality rejects that must be hand-moved from their
original pocket to the end of their new reassigned pocket
3
contains Image Quality Suspects
4
contains high priority Image Quality suspects
5
Image Quality tests required
6
contains Image Quality rejects that cannot be changed
7
review by an expert balancer required
To view the Image Quality Status:
1
Progress.
2
From the Unit of work type field, choose DDR with Images.
The system displays DDRI units of work in the table.
62
3
Select a DDRI Unit of Work from the table, then choose UoW Details.
The system displays the Unit of Work Details screen, with IQ Status displayed in the lower righthand corner.
UoW Details Dialog
63
Managing the Print Spooler
If you are having problems with the printer that is used for printing reports, you can redirect Entry
Item and Tray Set reports to a temporary spooler directory
(%IMAGEMARK_ROOT%\opt\siips\spool) so that you can view them or print them later when the
printer is working.
Redirecting Reports to Print Spooler
To redirect report printing, you must have an Application Display window open on your running copy
of ImageMark Transaction Manager.
1
To redirect the EIR, TSR, and BDL reports to the spooler directory:
a
Choose View > Print Spooler.
The system displays the Print Spooler dialog.
Print Spooler Dialog
b
Choose Configure....
The system displays the Configure Spooler dialog.
64
Configure Spooler Dialog
2
c
Select the reports listed in the Output to Printer list.
d
Choose << to move the reports to the Output to Spooler list, then choose OK.
e
After redirecting the EIR and TSR reports, you must unload, then re-load report auto-activities
to effect the changes:
a
Choose Maintain > Activities.
The system displays the Activities dialog.
Activities Dialog
b
In the Auto-Activity list, find the Entry Item Reports auto-activity and check its status in the
Status column.
65
c
If this status is “Failed” or “Not Running”, go on to the next step. Otherwise, complete the
following:
!
Select the auto-activity, then choose Unload.
!
The status then changes, first to “Terminating”, then to “Not Running”.
d
3
Repeat steps 2 and 3 for the Tray/Trayset Reports auto-activity.
Once the auto-activities have stopped, you can restart them:
a
b
Select the Entry Item Reports auto-activity, then the Tray/Trayset Reports auto-activity, so
that both of them are highlighted.
c
Choose Load.
The two report auto-activities print the reports to the spool device.
Viewing Reports
Once you have redirected the reports you can view them:
1
The system displays the Print Spooler dialog displaying all available reports for printing.
Print Spooler Dialog
Since there can be several reports for multiple entries, tray sets, or parameter sets, it can be
difficult to find the ones you need. Therefore, to help you limit which reports are shown in the
Print Spooler dialog, you can filter the report criteria by report type, entry number, parameter
set, and by unit-of-work type where:
!
66
Entry shows all the types of reports
!
2
Tray Set shows the Capture Reconciliation Run report
Select the report, then choose View....
The system displays the report in Notepad. You can print the report from this window or go back
to the Print Spooler dialog.
Viewing Report in Notepad
*
Tip: To properly read reports in Notepad, you may want to resize the window or turn off word wrap.
67
Printing Reports
Once you have redirected the report(s) you can print them:
1
2
Select the report(s), then choose Print.
The system displays the Print dialog.
Print Dialog
3
Select the printer you wish to use.
!
Line specifies the first available printer in the line printer class—the lpsiips printer may or
may not be the first
!
FILE specifies the directory %IMAGEMARK_ROOT%\opt\siips\archive
Note: The FILE output directory is not the same as printing to Spool. The Spool directory is used
for temporary storage while the FILE directory is used for long-term storage.
!
4
lpsiips specifies the printer that was configured during the ImageMark Transaction Manager
installation
Choose OK.
The system prints the report(s).
Deleting Reports
To delete reports from the spool directory:
1
2
Select the report, then choose Delete.
3
The system deletes the selected report(s) from the spool directory.
Note: The contents of the %IMAGEMARK_ROOT%\opt\siips\spool directory (i.e., reports printed
to spooler) are periodically deleted by the system.
68
Redirecting Reports Back to Printer
Once the printer problem has been resolved, you can redirect the EIR and TSR reports back to the
original print device.
1
To redirect the reports to the printer:
a
b
Choose Configure....
The system displays the Configure Spooler dialog.
Configure Spooler Dialog
2
c
Select the reports listed in the Output to Spooler list.
d
Choose >> to move the reports to the Output to Printer list, then choose OK.
e
Now you can restart the EIR and TSR auto-activities:
a
b
In the Auto-Activity list, find the Entry Item Reports auto-activity and check its status in the
Status column.
c
If this status is “Failed” or “Not Running”, go on to the next step. Otherwise:
!
Select this auto-activity, then choose Unload.
!
The status then changes, first to “Terminating”, then to “Not Running”.
d
3
Repeat steps 2 and 4 for the Tray/Trayset Reports auto-activity.
Once the auto-activities have stopped, you can restart them:
a
69
Activities Dialog
b
Select the Entry Item Reports auto-activity, then the Tray/Trayset Reports auto-activity, so
that both of them are highlighted.
c
Choose Load.
The two report auto-activities now print the reports to the spool device.
70
Managing Activities
Managing Activities
Another way to manage ImageMark Transaction Manager workflow involves monitoring the activities
that are running on the various stations.
From a workflow management standpoint, an activity is simply a running copy of an ImageMark
Transaction Manager software component. For example, a copy of Codeline Completion running
on an IDT is displayed as an activity in Application Manager.
Viewing Activities
To view activities, choose Maintain > Activities.
Activities Dialog
The top list in the Activities dialog displays auto-activities (activities that run automatically in the
background). The Station control lets you display these activities for all stations or only for the station
you specify.
The bottom list is for activities (activities that are run by operators). The Work Group control lets you
display these activities for all work groups or only for the work group you specify.
You use these two lists to monitor these activities.
71
Managing Activities
Loading Activities
To load a new activity, or to restart an activity that you had previously shut down:
1
2
Select the activity, then choose Load.
3
The system loads the activity and allocates system resources for it. If it is an operator activity,
the corresponding operators can now see it on their screens and select it.
Shutting Down Activities
Sometimes you may want to temporarily stop an activity from processing any work. For example,
suppose Central Processing asks you to stop sending balanced I-string data to the host, and you
do not want to put the units-of-work themselves on hold. You can shut down the BIE auto-activity
instead.
Caution: We recommend that whenever possible, you use the shutdown procedure in this section
instead of the unloading procedure in the next section. When you shut down an activity,
the system lets it finish whatever work it has in process before it shuts down. When you
unload an activity, it stops immediately, and you have to recover the work later.
To shut down an activity:
1
2
Select the activity, then choose Shutdown.
3
The system shuts down the selected activity.
72
Managing Activities
Unloading Activities
If you try to shut down an activity and the shutdown is taking much too long, you can unload it instead,
in an emergency. Unloading is less graceful than a shutdown, but it does happen immediately.
Caution: We recommend that whenever possible, you use the shutdown procedure in the
preceding section instead of the unloading procedure given below. When you shut down
an activity, the system lets it finish whatever work it has in process before it shuts down.
When you unload an activity, it stops immediately, and you have to recover the work later.
To unload an activity:
1
2
Select the activity, then choose Unload.
3
The system unloads the selected activity.
73
Reassigning a Station
Although ImageMark Transaction Manager can automatically reassign IDTs to a DS that has work
available, you may on occasion want to reassign a station to run services for a different station group.
You can reassign any of the following types of stations from one station group to another:
!
IDTs
!
TSSs
!
EPUs
!
ESUs
Once the situation that prompted you to reassign the station has passed, you may want to restore
the station to its original group.
Before you reassign a station, you must:
!
if reassigning an IDT, decide which of the keying activities you want it to perform for the new
station group
!
determine what database services you need for each of these activities
!
determine which servers provide these services in the new station group
To reassign a station for another group:
1
Choose Configuration > Station.
The system displays the Stations dialog.
Stations Dialog
74
2
In the Stations list, select the station that you want to reassign.
3
In the Installed activities list, select the first activity that you want the station to perform in its
new station group, then choose Services....
The systems displays the Services dialog that you use to access services from the new station
group’s servers.
Services Dialog
4
For each database service required by the activity you chose:
a
Select the name of the service, then choose Modify....
The system displays the Modify Current Station dialog, which lists all available servers for
this service.
Modify Current Station Dialog
b
Select the database server that provides this service in the new station group, then choose
OK.
The system updates the station in the Services dialog. The Station column shows the new
server that you have assigned for each service required by this activity.
5
In the Services dialog, choose OK.
75
Restoring a Station to its Original Station Group
To restore a station to its original group:
1
Choose Configuration > Restore Configuration.
2
The station returns to its original configuration.
Note: The Restore Station command takes care of all required changes for you. You do not need
to reassign activities and services manually.
76
Implementing Parameter and Environment Variable Changes
Implementing Parameter and Environment
Variable Changes
When changes to your system’s parameters or environment variables are made by your parameter
analyst, the changes do not take effect immediately. You need to implement the changes by stopping
and restarting the affected auto-activity(s).
Stopping an Auto-Activity
To shut down an auto-activity:
1
2
Select the auto-activity, then choose Shutdown.
3
The system shuts down the selected auto-activity.
Restarting an Auto-Activity
To restart the auto-activity:
1
2
Select the auto-activity, then choose Load.
3
The system loads the auto-activity and allocates system resources for it.
77
Server Status
Server Status
The Server Status dialog is used to the availability of a specific server. A check mark in the check
box beside a server name indicates that the server is available and work will be distributed to it.
Viewing Server Status
To view the list of available servers on your instance of ImageMark Transaction Manager, choose
Configuration > Server Status.
Server Status Dialog
Changing Server Status
You can change the availability status of a server on the system. To make a server unavailable on
the system:
1
Choose Configuration > Server Status.
The system displays the Server Status dialog.
2
Clear the check box beside the name of the server you want to make unavailable on the system.
3
Choose OK.
To make a server available on the system:
1
Choose Configuration > Server Status.
The system displays the Server Status dialog.
78
2
Place a check in the check box beside the server you want to make available on the system.
3
Choose OK.
External Capture Station Status
You can view the status of the External Capture Unit (ECU) (or ATM) station. This display shows
the availability of each ECU, and allows management of this status.
Viewing External Capture Station Status
To view the ECU (ATM, CS, etc.) station status, choose Configuration > External Capture....
The system displays the External Capture Station dialog.
External Capture Station Dialog
For each station, the following information is displayed:
!
The Number column shows the Station ID
!
The Node Name column shows the assigned network node name
!
The Display Name column shows the display name configured
!
The State column shows whether the ECU (or ATM) is currently available, unavailable, or not
configured.
The stations may be filtered by State:
!
When All is selected for State, the system displays each ECU (or ATM) regardless of its current
state
!
When Available is selected for State, the system displays ECUs (or ATMs) that have been
configured and are active
!
When Unavailable is selected for State, the system displays ECUs (or ATMs) that are currently
marked as unavailable (i.e., data captured from that ECU or ATM is not imported).
79
The order of station information within the table can be toggled between Transport Order and
Transport Name.
Note: To review details about the work received from an ECU, see “Viewing Import Status” on page
87.
Changing the External Capture Station Status
You can refuse capture files from any ECU (or ATM). For instance, a banking center may be sending
corrupt data files, or improperly captured data files (i.e., incorrect processing date). The system
allows you to select a specific station and suspend the importing of their data into the ImageMark
Transaction Manager databases.
To change the state of a station:
1
Choose Configuration > External Capture....
The system displays the External Capture Station dialog.
2
Select the appropriate station.
Note: To change the state of multiple stations simultaneously, all stations selected must have the
same status.
3
Choose Change State.
4
The system changes the state of the selected stations.
80
Managing Application Instances
Under certain circumstances, you may be required to load or unload an application instance.
Loading an Instance
Typically, the only time you load an instance is when you want to switch from one application type
to another.
Before you can load an instance:
!
the parameter files associated with its application type must be generated and installed
!
the ASCII files associated with its application type must be translated
!
the application type itself must be installed
To load an instance:
1
Check whether any other instances are active:
a
In the Application Manager window, choose Application > Display....
The system displays the Display Application dialog, showing all the copies of instances that
are currently loaded on the system.
b
Select each loaded copy in turn.
The Active/Inactive radio buttons tell you whether the instance you selected is active or
inactive.
81
2
For each instance that is active, make it inactive:
a
Select the instance in the Loaded copies of application list, then choose OK.
The system displays an Application Display window for this instance.
b
Choose Maintain > Application > Shutdown.
Respond appropriately to any messages or confirmation dialog boxes.
The system displays the Activities dialog. This dialog remains open until all the autoactivities have terminated.
c
Wait until all the auto-activities have stopped.
The Activities dialog closes automatically.
d
3
To close the Application Display window, choose Maintain > Exit.
When you have finished making all other instances inactive, go back to the Application Manager
window and choose Application > Load....
The system displays the Load Application dialog.
Note: The Application name will be different for your site.
Load Application Dialog
4
Select the desired instance from the Application list, then choose OK.
The system displays an Application dialog, where you must type a name for the new instance.
Name New Instance Dialog
82
5
Type in the name that you want to assign to this instance (for example, “MyBank, Version 2”),
then choose OK.
The system creates the instance and displays the Create Cycle dialog.
Create Cycle Dialog
6
Type the cycle number in the Cycle Number field, then press Tab.
The Host Cycle Number defaults to the same number you entered for the Cycle Number.
7
Select a Cycle State:
!
Open: a cycle must be open to allow operators to create work at the EPU
!
Close: if a cycle is closed, new entries cannot be created at the EPU, though unfinished
work can still be processed
!
Empty: an empty cycle is a closed cycle that has had all of its work processed and deleted.
Once a cycle has been set to EMPTY, it can be deleted.
8
If you are opening a new cycle, ensure that the date in the Posting Date field is set to today’s
date, or to the appropriate posting date.
9
Choose OK.
The system creates the cycle instance.
10 To use this instance now, choose Maintain > Application > Restart.
The instance is restarted and the system displays the Activities dialog.
83
Activities Dialog
11 Wait until all the auto-activities have started, then choose Close.
The selected instance has been loaded and the system displays the Application Display window
for that instance.
Unloading an Instance
Unloading an instance clears its records from the databases and frees the system resources that
are allocated for it. Also, the next time you want to run an instance of this application type, you have
to load it again, which takes longer than restarting one that you have only shut down.
Note: Before you can unload an instance, you must do an orderly shutdown as described in
“Archiving Report Files” on page 18.
1
Choose Maintain > Application > Unload.
2
The system unloads the instance, and the resources it was using are released.
84
Viewing Work Export Status
You can view the status of work sent to the host application during the Balanced Item Export (BIE)
or Sub-Pass Item Export (SIE) auto-activities.
Viewing Export Log
To view the status of work sent to the host application, choose View > Export Log.
The system displays the Export Log dialog, which displays the status of all work sent to the host
application during BIE or SIE. The dialog refreshes every fifteen seconds.
Export Log Dialog
You can filter the information displayed in the Export Log dialog by export activity, parameter set,
entry number, cycle, and by UoW flag, where:
!
All views all UoW types
!
Resend views only units-of-work resubmitted to BIE and SIE
!
Export views only normal BIE and SIE units-of-work
Note: The summary information varies depending on the originating auto-activity and the type of
message generated. If you receive a Miscellaneous message for a UoW, that is the only
message you will receive for that work. For each successful upload, you should receive two
messages: Start and Finish. If you receive Start and Fail, consult Diagnostics for details.
85
Viewing Export Details
To view the export details for a UoW:
1
Choose View > Export Log.
The system displays the Export Log dialog.
2
Select the item you want to view, then choose Details.
The system displays the Export Log Details dialog.
Export Log Details Dialog
86
Viewing Import Status
You can monitor the status of image capture files from external capture units (ECU). This display
identifies import problems (such as an invalid cycle or invalid station) and allows you to manage
some of these problems by retrying the import or remapping cycle numbers.
To view the status, choose View > Import Status.
The system displays the Import Status dialog.
Import Status Dialog
Changing the Station/Location setting allows you to display only those items captured on a specific
transport or at a specific location. Changing the State setting allows you to view the current state of
the import file.
Notes: !
!
If you have both the Transports toggle and State toggle set to All, the dialog will not
show files with the state of “imported”.
To see the status of all files for a particular type of transport, sort by Capture Type
column (click on the column heading) to group the entries for that transport.
87
Changing the Cycle Number of Import File
If you have image capture files with an “invalid cycle” it may mean that they were captured (at the
ECU) under the wrong posting date. In this case, you need to move the entries to the correct cycle
number.
1
Choose View > Import Status.
2
Select the entry with an invalid cycle, then choose Change Cycle....
The system displays the Change Cycle dialog.
Change Cycle Dialog
3
Select a cycle number from the list, then choose OK.
The system updates the number of the cycle and automatically retries the import.
Note: The Modified Entry report shows the entries that were moved to another cycle.
Retrying Files and Reloading Work
If you have an image capture file that has not been processed, you can try to process it again. For
example, a “blocked” file means that the ECU station has been made inactive for service. Once the
station is active again, you can retry the file by performing the following steps:
1
2
Select the entry you want to retry, then choose Retry.
The system reprocesses the capture image file.
88
You can perform the same procedure to reload work that you previously held over. Any holdover
units-of-work will be marked with a status of “holdover”.
Notes: !
If the unit-of-work does not match a currently open cycle, the work will reappear with a
status of “invalid cycle”. See “Changing the Cycle Number of Import File” on page 88
for information on handling this.
!
If a storage space is not available on the system, the work will return with a status of
“No Storage Space”. See “Managing Storage Spaces” on page 120 for information on
how to handle this.
Ignoring Import Files
If you no longer want image capture files to be imported into the system, you can set the files to be
ignored by the system. Once applied, this process is not reversible as the files will be deleted from
the importing queue. To set files to be ignored:
1
Import Status Dialog
2
Select the entry (or entries) you want to be ignored by the system, then choose Ignore.
3
At the confirmation dialog, choose OK.
The system ignores the capture image file(s).
Note: You can only ignore entire runs. If you have not selected all the files in a run to be ignored,
an error dialog will appear and not allow you to proceed until all the files in the run are selected
and set to “Ignore”.
89
Displaying File Details
To display the details of a capture file:
1
2
Select the entry whose details you want to view, then choose Details.
The system displays the File Details dialog.
File Details Dialog
90
Viewing Archive Status
While an Application Display window is open on a running copy of ImageMark Transaction Manager,
you can view each ETI auto-activity’s progress with the units-of-work that are bound for the archive
system.
To view the archive status, choose View > Archive Status.
Archive Status Dialog
This dialog shows you each ETI auto-activity as it progresses through the processing of units-ofwork for archive.
!
The Generated column shows how many units-of-work of each type there are in the system.
!
The Archived column shows how many units-of-work of each type have been archived.
!
The Complete column signifies that all generated units-of-work have been successfully or
unsuccessfully archived and all cycles associated with the current view in the dialog are closed.
The Cycle list box allows you to display units-of-work to be archived for a specific cycle (or posting
day) or for all cycles.
91
To view status changes to the archive as it updates, choose Refresh.
Note: This dialog is enabled by setting the ArchiveInSystem parameter (AMCLASSA_PARMS
keyword). If you enable ArchiveInSystem, you must also set ArchiveDocumentItem,
ArchiveAdvice, and ArchiveOperatorAudit. The ArchiveDocumentItem parameter settings let
you determine whether a document type will be archived and let you assign a unit-of-work
type to document type (either DDRI or Entry units-of-work).
92
Managing Second Source Matching
You can monitor and manipulate units-of-work that fail to match second source data records during
SMM processing. This display shows you “held” batches and allows you to retry or push the batches.
There are two options for work moving past SMM, controlled by parameters. A DI unit of work can
move on if either of the following is true:
!
the ReturnUnlessAllMatched parameter (EXT_SECOND_SOURCE_BANK_PARMS keyword)
is set to 0, and one item has been matched
!
the ReturnUnlessAllMatched parameter (EXT_SECOND_SOURCE_BANK_PARMS keyword)
is set to 1, and the entire unit of work has been matched
Viewing Second Source Processing Information
You can monitor the progress of SMM processing in the Second Source View dialog. The dialog
lists all DI units-of-work that did not have a single match to a second source data record item.
To view Second source information, choose View > Second Source....
The system displays the Second Source Status dialog, which lists all batches with images units-ofwork that contain items that require matching but are not yet matched.
Second Source Status Dialog
To manage workload by unit-of-work, choose View > Work In Progress.
The system displays the Work in Progress dialog.
93
On the Work in Progress dialog, the Item Viewer button is enabled only when both of the following
are true:
!
only one unit of work is selected
!
that unit of work is a DDR+I unit of work that is either On Hold or At End
From either of these screens, choose Item Viewer to display the item’s image and field information.
Item Viewer
94
Resubmitting Work to SMM
If SMM processes a unit-of-work without locating the associated second source data, you can
resubmit the unit-of-work to SMM. During the second submission to SMM, the auto-activity will
reprocess the work and try to locate its second source data.
To resend a unit-of-work to SMM:
1
Choose View > Second Source....
The system displays the Second Source Status dialog.
2
Select the unit(s)-of-work you want to resend, then choose Retry.
The system resends the unit(s)-of-work to SMM.
Pushing Work Past SMM
To push a unit-of-work past SMM:
1
2
Select the unit(s)-of-work you want to push past SMM, then choose Push.
The system pushes the unit(s)-of-work past SMM without matching second source data.
Note: You can have the system automatically push a unit-of-work that has been waiting at SMM
for its second source file to arrive for a certain amount of time (for example, 75 minutes) using
the EXT_SECOND_SOURCE_BANK_PARMS parameter.
Enabling Shuffle Mode
You can put SMM into shuffle mode to have all units-of-work bypass the auto-activity.
Note: You can customize the Second Source Status dialog interface for shuffle mode using the
Spare1 parameter for the AMCLASSA_PARMS keyword.
To enable shuffle mode:
1
2
Choose Enable Shuffle Mode.
3
The button toggles to Disable Shuffle Mode.
4
For the change to take effect, stop and restart SMM.
95
Disabling Shuffle Mode
To disable shuffle mode:
1
2
Choose Disable Shuffle Mode.
3
The button toggles to Enable Shuffle Mode.
4
For the change to take effect, stop and restart SMM.
Viewing Item Images
You can view the front and back images of items to determine why a unit-of-work is missing second
source data.
To view SMM item images:
1
2
Select the unit-of-work that contains items you wish to view, then choose Details.
The system displays the Second Source Details dialog.
Second Source Details Dialog
3
96
Manipulate the images in any of the following ways:
!
Select the image to display its reverse side.
!
Choose <<Previous to view the previous item’s image in the unit-of-work.
!
Choose Next>> to view the next item’s image in the unit-of-work.
Holding Work
To hold a unit-of-work for processing on a future date:
1
2
Select the unit(s)-of-work you want to holdover for future processing, then choose Holdover.
The system will push the unit(s)-of-work past SMM without matching second source data, but
indicates that it needs to be held over for a future processing date.
97
Workflow Diagrams
Workflow Diagrams
These ImageMark Transaction Manager 4.2 workflow diagrams are shown on the following pages:
98
!
Standard OTC
!
Unencoded Large Deposit / Block Balancing
!
Pre-encoded / Block Balancing (with PIE)
!
Pre-encoded with Regular Batch Balancing
EPU
ESU
ESU_TS_IN
11
82
Image Quality
Tests
ETF_ANY_OUT
ESU_TS
ESU_T
** ESU_IN_T
** ESU_IN_TS
ESU_T_IN
ESE
9
"61: ESI IN"
EPA_IN
EPA_IN
(R,A,Q)
EPA_OUT (T)
EPA_OUT (TS)
ESI
** EPA_OUT (I/P_T)
RSS_DI
15
16
(A)
CPR
CPR_T/IN
CPR_TS/IN
CON_E_OUT
CON_D_OUT
CON_E_IN
RSS
(B,U)
CPR_O/P_TS_IN
CPR_O/P_T_IN
17
CON
CON_TS/H_OUT
CON_T/H_OUT
** EPA_OUT (I/P_TS)
60
1
CON_TS/J_OUT
CON_T/J_OUT
CON_TS_IN
CON_T_IN
(U,S,B)
ACC
10
ETF_ANY_IN
ETF_ANY_IN
ACC_DI
(A)
(U,S,B)
"60: ESE ANY IN"
61
CON_T/K_OUT
CON_TS/K_OUT
EPA_OUT (TS)
EPA_OUT (T)
ETF_ANY_OUT
12
80
(R,Q)
IQA
EPA_OUT (E)
IQA_DI
EPA
EPA_OUT (DI)
22
35
SIE_TS_IN
CPR_O/P_T/OUT
CPR_O/P_TS/OUT
CPR_TS_OUT
36
SIE_PUSH_TS_OUT
7
(B,U)
(A)
27
3
26
CPR_T/HO_IN
CPR_TS/HO_IN
SIE_TS_OUT
SIE_T_OUT
EIR
32
AK
END_D_IN
CRD_TS/HI_IN
CRD_T/HI_IN
14
(*extension
options)
CRD_TS_K/*_OUT
ETI_IN
37
33
TSR_T_IN
END_TS_IN
ETI_OUT
SCU_E_OUT
20
TSR_TS_OUT
SCU
39
31
END_DI_IN
8
(U)
5
EBAL
( DI not in proof )
SCU_DI_OUT
(B)
ADV
ADV_A_IN
xxx_DI
Entry
xxx_E
Batch
xxx_D
xxx_T
Advice Notice
xxx_ADV
Tray Set
xxx_TS
Tray
Units of Work:
EPA - Entry Processing Autorole
ACC - Auto Codeline Completion
IQA - Image Quality Analysis
RSS - Recognition
STG - Stager
SCU - Suspense Copy & Update
CTA - Copy to AP
CON - Consolidation
ESE - Encode & Sort Export
ESI - Encode & Sort Import
BIE - Balanced Item Export
SIE - Sub-pass Item Export
EIR - Entry Item Report
CRD - Coordination
ETI - Export to Image Archive
TSR - Tray Set Report
SER - Statistical Extract
Auto-Activity
XXX
ADV_A_OUT
EBAL_DI
21
B004-0000-0457
05.01.00
2005.06.03
BBL_ADV
Batch & Images
"Regular Balancing
Overflow"
END OF
WORKFLOW
END_ANY_IN
SER_E_OUT
(*extension
options)
( DI in proof )
SCU_DI_OUT
(U,B)
BBL_ADV
SER
TSR_T_OUT
SER_E_IN
ETI_OUT
TSR
BAL
SCU_E_IN
BAL_DI
BAL_DI
ETI_OUT
ETI
ETI
ETI
TSR_TS_IN
END_T_IN
29
30
(*extension
options)
CRD_TS_E/O_OUT
(R,U,A)
Transaction Manager 2005
Standard Over-the-Counter (OTC) Workflow
(*multiples possible)
(B)
ETI_IN
101
101
101 ETI_IN
STG
CRD_T_E/O_OUT
CRD_E/K_OUT
CRD_E_IN
13
CRD
EIR_E_OUT
STG_DI
CTA_DI/DS
4
24
OCTA
OCTA
CTA
6
(B,U)
- Rejected
- Amount Required
- Unbalanced
- Supervisor Approval Req’d
- Image Quality Suspects
- Balanced
CRD_T_K/*_OUT
25
Interaction
DI Unit of Work States:
R
A
U
S
Q
B
CTA_DI/B_IN
EIR_D_OUT
CTA_D/AP
AK_DI
EIR_D_IN
EIR_E_IN
28
SIE
19
BIE_D_OUT
BIE_E_OUT
CLC
SIE_T_IN
BIE
SIE_PUSH_T_OUT
BIE_E_IN
CLC_DI
CON_D_IN
BIE_D_IN
2
CPR_T_OUT
23
37
(R,Q)
Activity
EPU - Entry Processing
CLC - Codeline Completion
BAL - Balancing
EBAL -Expert Balancing
ADV - Advice Notices
ESU - Encode & Sort
CPR - Capture Reconciliation
AK - Amount Keying
#
EPU
ESU
ESU_TS_IN
11
ESE
ESU_TS
ESU_T
** ESU_IN_T
** ESU_IN_TS
ESU_T_IN
12
ETF_ANY_OUT
ETF_ANY_OUT
ETF_ANY_IN
ETF_ANY_IN
9
10
"61: ESI IN"
EPA_IN
EPA_IN
(R,A,Q)
EPA_OUT (T)
EPA_OUT (TS)
ESI
** EPA_OUT (I/P_T)
RSS_DI
(A)
CLC_DI
*
35
36
SIE_TS_IN
SIE_T_IN
7
(B,U)
(A)
27
3
26
CPR_T/HO_IN
CPR_TS/HO_IN
SIE_TS_OUT
SIE_T_OUT
EIR
32
AK
END_D_IN
CRD_TS/HI_IN
(*extension
options)
CRD_TS_K/*_OUT
CRD_TS_E/O_OUT
CRD_T_E/O_OUT
CRD_E/K_OUT
72
ETI_IN
30
END_TS_IN
END_T_IN
TSR_TS_IN
TSR_T_IN
ETI_IN
B004-0000-0457
05.02.00
2005.06.03
TSR
20
ETI_OUT
TSR_T_OUT
SCU_DI_OUT
31
END_DI_IN
( DI in proof )
SCU_DI_OUT
END OF
WORKFLOW
END_ANY_IN
SER_E_OUT
(*extension
options)
( DI not in proof )
BBL_E_OUT
BBL_DI_OUT
EBBL
BBL_E_IN
SCU_E_IN
38
SCU
39
SCU_DI_IN
BBL_E_OUT
SER
TSR_TS_OUT
BBL_ADV
BBL_DI_OUT
SCU_E_OUT
73
BBL
SER_E_IN
ETI_OUT
ETI_OUT
BCTA_IN
BCTA_IN
70
BBL_DI
BBL_DI
BBL_E_IN
BBL_E_IN
Block
Balancing
8
78
BBL_ADV
OBBL_E_IN
( DI in proof )
OSCU_DI_OUT
75
( DI not in proof )
OSCU_DI_OUT
OSCU_DI_IN
OSCU
OSCU_E_IN
OSCU_E_OUT
77
OBBL_DI_OUT
OBBL_DI_OUT
OBBL_DI
74
OCTA_OUT
OBBL_DI
OEBBL
OBBL_E_OUT
OBBL_E_IN
OBBL
OBBL_E_OUT
76
OCTA_OUT
ADV
Offline Work
OCTA
OCTA
OCTA
ADV_A_OUT
OCTA_OUT
XXX
Auto-Activity
RSSR - Recognition for Rejects
RSSA - Reco for Amount Suspects
STG - Stager
CTA - Copy to AP
CON - Consolidation
CRD - Coordination
PIE - Prime Item Export
MIE** - Modified Item Export**
**(for SuperMIRC only)
ADV_A_IN
OCTA_IN
21
Unencoded Large Deposit / Block Balancing Workflow
ETI
ETI
ETI
BCTA
(B only)
101
101
101 ETI_IN
29
(B)
(A,U)
STG_E_OUT
STG
(not B)
STG_E_OUT
(*extension
options)
BCTA_OUT
STG_DI
STG_E_IN
71
- Rejected
- Amount Required
- Unbalanced
- Balanced
BCTA_OUT
CRD_E_IN
13
CRD
14
CRD_T_K/*_OUT
25
CRD_T/HI_IN
EIR_E_OUT
#
Interaction
R
A
U
S
Q
B
CTA_DI/DS
4
24
OCTA
OCTA
CTA
6
(B,U)
Advice Notice
xxx_ADV
Entry
xxx_E
Tray Set
xxx_TS
Tray
xxx_T
Batch
xxx_D
Batch & Images
xxx_DI
Units of Work:
CTA_DI/B_IN
EIR_D_OUT
CTA_D/AP
AK_DI
EIR_D_IN
EIR_E_IN
28
SIE
Activity
BAL - Balancing
ESU - Encode & Sort
IQR - Image Quality Review
AK - Amount Keying (ASV)**
(Amount Suspect Validation)
19
BIE_D_OUT
BIE_E_OUT
CLC
CPR_O/P_T/OUT
CPR_TS_OUT
CPR_T_OUT
SIE_PUSH_TS_OUT
SIE_PUSH_T_OUT
BIE_E_IN
SuperMICR
may include
MIE here
BIE
CON_D_IN
BIE_D_IN
2
15 CPR_O/P_TS_IN
22
23
37
(R,Q)
CPR_O/P_TS/OUT
CPR
CPR_T/IN
CPR_TS/IN
CON_E_OUT
CON_D_OUT
CON_E_IN
RSS
(B,U)
CPR_O/P_T_IN
16
17
CON
CON_TS/H_OUT
CON_T/H_OUT
** EPA_OUT (I/P_TS)
60
1
CON_TS/J_OUT
CON_T/J_OUT
CON_TS_IN
CON_T_IN
(U,S,B)
ACC
"60: ESE ANY IN"
61
CON_T/K_OUT
CON_TS/K_OUT
EPA_OUT (TS)
EPA_OUT (T)
80
(A)
(U,S,B)
ACC_DI
IQA
(R,Q)
EPA_OUT (E)
IQA_DI
EPA
82
Image Quality
Tests
EPA_OUT (DI)
EPU
ESU
ESU_TS_IN
11
ESE
ESU_TS
ESU_T
** ESU_IN_T
** ESU_IN_TS
ESU_T_IN
12
ETF_ANY_OUT
ETF_ANY_OUT
9
"61: ESI IN"
EPA_IN
EPA_IN
(R,Q)
EPA_OUT (T)
EPA_OUT (TS)
ESI
** EPA_OUT (I/P_T)
(R,Q)
CPR
CPR_T/IN
CPR_TS/IN
CON_E_OUT
CON_D_OUT
CPR_O/P_TS_IN
22
*
35
SIE_TS_IN
CPR_O/P_T/OUT
CPR_O/P_TS/OUT
CPR_TS_OUT
36
SIE_PUSH_TS_OUT
7
RSS_DI
27
26
EIR
32
CPR_T/HO_IN
CPR_TS/HO_IN
SIE_TS_OUT
SIE_T_OUT
3
AK
END_D_IN
CRD_TS/HI_IN
BCTA_OUT
(*extension
options)
CRD_TS_K/*_OUT
CRD_TS_E/O_OUT
CRD_T_E/O_OUT
CRD_E/K_OUT
72
ETI_IN
30
END_TS_IN
END_T_IN
TSR_TS_IN
TSR_T_IN
ETI_IN
TSR
20
ETI_OUT
TSR_T_OUT
SCU_DI_OUT
31
END_DI_IN
( DI in proof )
SCU_DI_OUT
END OF
WORKFLOW
END_ANY_IN
SER_E_OUT
(*extension
options)
( DI not in proof )
BBL_E_OUT
BBL_DI_OUT
EBBL
BBL_E_IN
SCU_E_IN
38
SCU
39
SCU_DI_IN
BBL_E_OUT
SER
TSR_TS_OUT
BBL_ADV
BBL_DI_OUT
SCU_E_OUT
73
BBL
SER_E_IN
ETI_OUT
ETI_OUT
BCTA_IN
BCTA_IN
70
BBL_DI
BBL_DI
BBL_E_IN
BBL_E_IN
Block
Balancing
8
78
BBL_ADV
OBBL_E_IN
( DI in proof )
OSCU_DI_OUT
75
( DI not in proof )
OSCU_DI_OUT
OSCU_DI_IN
OSCU
OSCU_E_IN
OSCU_E_OUT
77
OBBL_DI_OUT
OBBL_DI_OUT
OBBL_DI
74
OCTA_OUT
OBBL_DI
OEBBL
OBBL_E_OUT
OBBL_E_IN
OBBL
OBBL_E_OUT
76
OCTA_OUT
ADV
Offline Work
OCTA
OCTA
OCTA
ADV_A_OUT
OCTA_OUT
XXX
Auto-Activity
STG - Stager
CTA - Copy to AP
CON - Consolidation
CRD - Coordination
ADV_A_IN
OCTA_IN
21
B004-0000-0457
05.03.00
2005.06.03
Pre-Encoded / Block Balancing Workflow (with PIE)
ETI
ETI
ETI
BCTA
(B only)
101
101
101 ETI_IN
29
(B)
(A,U)
STG_E_OUT
STG
(*extension
options)
BCTA_OUT
STG_DI
STG_E_IN
71
(not B)
STG_E_OUT
- Rejected
- Amount Required
- Unbalanced
- Balanced
CTA_DI/DS
4
#
Interaction
R
A
U
S
Q
B
CRD_E_IN
13
CRD
14
CRD_T_K/*_OUT
25
CRD_T/HI_IN
EIR_E_OUT
24
OCTA
OCTA
CTA
6
(B,U)
Advice Notice
xxx_ADV
Entry
xxx_E
Tray Set
xxx_TS
Tray
xxx_T
Batch
xxx_D
Batch & Images
xxx_DI
Units of Work:
CTA_DI/B_IN
AK_DI
EIR_D_OUT
CTA_D/AP
(A)
EIR_D_IN
(B,U)
RSS
(asv)
EIR_E_IN
28
SIE
Activity
BAL - Balancing
ESU - Encode & Sort
19
BIE_D_OUT
1
BIE_E_OUT
SIE_T_IN
BIE
SIE_PUSH_T_OUT
BIE_E_IN
SuperMICR
may include
MIE here
(B,U)
(A)
(A,U,B)
CON_D_IN
CLC
PIE
BIE_D_IN
CLC_DI
(R,Q)
CPR_T_OUT
23
37
2
(A,U,B,S)
79
CON_E_IN
RSSR
(IQ known)
CPR_O/P_T_IN
17
15
16
(A,U,B)
For PIE Upload
CON
CON_TS/H_OUT
CON_T/H_OUT
CON_TS/J_OUT
CON_T/J_OUT
** EPA_OUT (I/P_TS)
60
CON_T_IN
CON_TS_IN
RSSR_DI
(R,Q)
IQR
81
IQR_DI
P_Entry
83
(A,U,B,S)
ACC
10
ETF_ANY_IN
ETF_ANY_IN
ACC_DI
Suspect
IQ_HighPriority
(A,U,B)
( PIE Upload, no IQ high priority suspects)
"60: ESE ANY IN"
61
CON_T/K_OUT
CON_TS/K_OUT
EPA_OUT (TS)
EPA_OUT (T)
80
IQA
(R,Q)
EPA_OUT (E)
IQA_DI
EPA
82
Image Quality
Tests
EPA_OUT (DI)
EPU
ESU
ESU_TS_IN
11
ETF_ANY_OUT
ESU_TS
ESU_T
** ESU_IN_T
** ESU_IN_TS
ESU_T_IN
ESE
ACC_DI
ETF_ANY_IN
ETF_ANY_IN
9
10
"61: ESI IN"
EPA_IN
EPA_IN
(R,Q)
EPA_OUT (T)
EPA_OUT (TS)
ESI
** EPA_OUT (I/P_T)
16
(A,U,B)
CPR
CPR_T/IN
CPR_TS/IN
CON_E_OUT
CON_D_OUT
15
CPR_O/P_TS_IN
CPR_O/P_T_IN
17
(R,Q)
22
*
35
SIE_TS_IN
CPR_O/P_T/OUT
CPR_O/P_TS/OUT
CPR_TS_OUT
36
SIE_PUSH_TS_OUT
7
RSS_DI
26
EIR
32
CPR_T/HO_IN
CPR_TS/HO_IN
SIE_TS_OUT
SIE_T_OUT
3
AK
END_D_IN
BCTA_OUT
STG_DI
(*extension
options)
CRD_TS_E/O_OUT
CRD_TS_K/*_OUT
ETI_IN
TSR_TS_IN
END_TS_IN
END_T_IN
29
30
Transaction Manager 4.2
71
SCU_E_OUT
ETI_OUT
TSR
20
ETI_OUT
TSR_TS_OUT
TSR_T_OUT
SER_E_IN
SER
BAL
SCU_E_IN
BAL_DI
ETI_OUT
33
BAL_DI
31
SCU
39
(B)
END_DI_IN
( DI not in proof )
8
(U)
5
EBAL
"Regular Balancing
Overflow"
SCU_DI_OUT
END OF
WORKFLOW
END_ANY_IN
SER_E_OUT
(*extension
options)
( DI in proof )
SCU_DI_OUT
(U,B)
BBL_ADV
EBAL_DI
BBL_ADV
STG - Stager
CTA - Copy to AP
CON - Consolidation
CRD - Coordination
Auto-Activity
XXX
ADV
ADV_A_IN
21
B004-0000-0643
02.01.00
2006.09.07
ADV_A_OUT
Pre-Encoded with Regular Batch Balancing Workflow
ETI
ETI
ETI
TSR_T_IN
ETI_IN
101
101
101 ETI_IN
(*extension
options)
CRD_T_E/O_OUT
CRD_E/K_OUT
(R,U,A)
STG
(B)
- Rejected
- Amount Required
- Unbalanced
- Balanced
CTA_DI/DS
4
#
Interaction
R
A
U
S
Q
B
CRD_E_IN
13
CRD
14
CRD_T_K/*_OUT
25
CRD_TS/HI_IN
CRD_T/HI_IN
EIR_E_OUT
24
OCTA
OCTA
CTA
6
(B,U)
Advice Notice
xxx_ADV
Entry
xxx_E
Tray Set
xxx_TS
Tray
xxx_T
Batch
xxx_D
Batch & Images
xxx_DI
Units of Work:
CTA_DI/B_IN
AK_DI
EIR_D_OUT
CTA_D/AP
(A)
EIR_D_IN
(B,U)
RSS
(asv)
EIR_E_IN
28
SIE
27
Activity
BAL - Balancing
ESU - Encode & Sort
19
BIE_D_OUT
1
BIE_E_OUT
SIE_T_IN
BIE
SIE_PUSH_T_OUT
BIE_E_IN
SuperMICR
may include
MIE here
(B,U)
(A)
(A,U,B)
CON_D_IN
CLC
PIE
BIE_D_IN
CLC_DI
(R,Q)
CPR_T_OUT
23
37
2
(A,U,B,S)
79
CON_E_IN
RSSR
(IQ known)
For PIE Upload
CON
CON_TS/H_OUT
CON_T/H_OUT
** EPA_OUT (I/P_TS)
60
CON_TS/J_OUT
CON_T/J_OUT
CON_TS_IN
CON_T_IN
RSSR_DI
(R,Q)
IQR
81
IQR_DI
P_Entry
83
(A,U,B,S)
ACC
"60: ESE ANY IN"
61
CON_T/K_OUT
CON_TS/K_OUT
EPA_OUT (TS)
ETF_ANY_OUT
12
80
Suspect
IQ_HighPriority
(A,U,B)
( PIE Upload, no IQ high priority suspects)
EPA_OUT (E)
(R,Q)
IQA
EPA_OUT (T)
IQA_DI
EPA
82
Image Quality
Tests
EPA_OUT (DI)
3
Configuration Manager
Configuration Manager enables you to tell the system about the resources available to it. These
resources include:
!
station hardware, such as the EPUs, ESUs and IDTs
!
applications, such as Image Capture, Balancing and Capture Reconciliation
!
services, such as the DSs and IPCS
!
parameter sets, which are also called application types
!
storage spaces
This chapter tells you how to start Configuration Manager and discusses the following Configuration
Manager tasks:
!
creating and modifying station groups, which includes naming a station group, then adding
stations to it
!
adding a workstation, which includes adding any adapters required, and assigning it a service
resource, if applicable
!
changing a workstation, which includes switching the identification, changing its type, and adding
or deleting adapters
!
deleting a workstation, which requires removing parameter sets and application software first
!
managing storage spaces on the system, which includes freeing and initializing the databases
!
adding and removing application software, which can be done by package and by station
!
adding and removing parameter sets, which can be done by package and by station and includes
assigning one or more stations to provide Host emulator and/or database services
!
configuring the required IDTs with the Second Source Browser software and ImageMark
Transaction Manager parameter set
103
Chapter 3: Configuration Manager
Starting Configuration Manager
To start Configuration Manager from the Task Manager, choose Configuration Manager from the
Utilities list.
The system displays the Configuration Manager window.
Configuration Manager Window
104
Process Overview
The basic process for configuring stations in ImageMark Transaction Manager is as follows:
!
create station groups and assign the stations to them
!
assign the required software and parameter sets to each station in each group
The Order for Configuring
When you configure the system by adding or deleting components with Configuration Manager,
follow the order implied by these rules and recommendations:
!
You must define a station group before you can configure any stations in it.
!
You can add all of the stations to a station group before adding the software and parameter
sets. However, before you add stations requiring database or sort simulator services from a
different station group, you should ensure that the other group has been configured with the
stations that provide the service.
!
Before you add a parameter set, you must have configured the station(s) with the applicable
software.
!
Before you can delete a station group, you must remove all workstations assigned to that station
group.
!
Before you delete a workstation, you must first remove all parameter sets assigned to that
workstation, then remove all application software assigned to that workstation.
!
If your EPU is a 779x, sort simulator services must be run on the local host (to maintain the
speed of the 779x). They cannot be obtained from a different station group. An instance of the
sort simulator must be run on the transport controller box for each transport.
105
Adding and Modifying a Station Group
This section describes how to add and modify station groups. A station group is a collection of work
stations.
The initial installation automatically creates a “system station group” that includes the BAP.
You can use Configuration Manager to add another station group and to modify the original system
station group, if required. For example, you may want to add a station group to organize the
workstations that are normally used by a particular group of users.
Planning Station Groups
When ImageMark Transaction Manager is first installed, the system station group is automatically
created, and the BAP is assigned to it. ESUs are manually assigned to the system group.
Technically, you could assign all the other stations to this same group. However, we strongly
recommend you organize the stations into smaller, logical groupings, so that Configuration Manager
can offer you more reasonable default selections later in the configuration process.
Each additional station group consists of one DS plus the following other stations:
!
the EPU that sends document data and images to this DS
!
the IDTs that access document data and images from this DS
!
the DAP with which this DS interacts
At a typical site, each DAP is assigned to up to three station groups.
The following illustration shows a large site. Station groups 1 to 3 share DAP 1, groups 4 to 6 share
DAP 2, and group 7 uses DAP 3.
106
Sample Grouping Configuration
Whatever scheme you use, you should record it so that when you need to change the configuration
you are aware of all stations that might be affected by the change.
107
Viewing Station Groups
To view the stations that are configured on a particular station group, choose Station Group > View.
The system displays the View Station Groups dialog.
View Station Groups Dialog
Adding a Station Group
To add a station group:
1
Choose Station Group > Add....
The system displays the Add Station Group dialog.
Add Station Group Dialog
2
Type a name for the station group. The name can contain up to 30 alphanumeric characters
including spaces.
3
Type a unique number for the station group, then choose OK.
Configuration Manager adds the name to the list of defined physical station groups.
108
Modifying a Station Group
To change the name or number of a station group:
1
Choose Station Group > Modify....
The system displays the Modify Station Group dialog.
Modify Station Group Dialog
2
Select the name of the station group to be changed, then choose Modify....
The system displays the Modify Station Group dialog.
Modify Station Group Dialog
3
Change the name or number of the station group, then choose OK.
The system updates the name and number selected station group in the Modify Station Group
dialog.
109
Removing a Station Group
Before you can remove a station group, you must first remove all workstations assigned to that
station group. Then you can use the Remove command from the Station Group menu.
To remove a station group:
1
Remove all stations that have been assigned to the station group. See “Removing a Station” on
page 119.
2
Choose Station Group > Remove....
The system displays the Remove Station Groups dialog.
Note: If the Remove command is not available, some stations have not been removed. Return to
step 1.
Remove Station Groups Dialog
3
Select the name of the station group to be removed, then choose OK.
4
The system removes the station group from the system.
110
Adding and Modifying a Station
Stations are added to the system and configured one at a time. The basic process for adding a
station is as follows (detailed instructions are given in the following sections):
!
Identify the station by giving it a name and number.
!
Assign the station to a station group.
!
Assign the station a station type.
!
Exit from the Add Station dialog. Configuration Manager then rebuilds the system configuration.
You can change a station’s configuration by:
!
removing it from the system
!
changing its name and number
!
changing its type
!
changing its adapter configuration
111
Adding a Station
The Add Station dialog lists all station groups that have been defined for Capture. When adding a
new station, you must assign it to one of these groups (if the station is a DAP, you may assign it to
more than one group). The station identification includes a name and a number. This name and
number should be consistent with the ones assigned when the existing stations were first installed.
To add a station to the system:
1
Choose Station > Add....
The system displays the Add Station dialog.
Add Station Dialog
2
Choose Browse... to locate a node name.
The system displays the Select Computer dialog.
112
Select Computer Dialog
3
Enter the station name, or select one from the list, then choose OK.
The system returns to the Add Station dialog where the selected station name is populated into
the Node Name and Station Name fields in the dialog.
Note: You may change the station name if you wish. The name cannot have more than 30
characters and must not include “wildcard” characters such as ? and *.
4
Type the number of the station to be added in the Station Number field. This number can be
any 2-digit number (from 1 to 99, inclusive).
5
Select the desired station group in the Options list within the Select station groups area of the
dialog, then choose <<.
The selected station group moves to the Selected list.
6
Select desired station type in the Options list within the Select station types area of the dialog,
then choose <<.
The selected station type moves to the Selected list.
Note: You can assign more than one type to a station (for example, a station used as an EPU and
as an ESU can be assigned both the Image Capture and Encode and Sort Station types).
7
When you are finished, choose OK.
8
The system creates the station. At this point, Configuration Manager automatically rebuilds the
network configuration.
Note: When a storage space is defined on the new station, it will have a status of “Free” in the
Storage Space Manager dialog.
113
Modifying a Station's Attributes
An installed and configured station has a name, an identifying number, a classification (type), and
at least one network address. It is also assigned to a station group (a DAP may be assigned to more
than one station group).
You can change any of these attributes in the Modify/Remove Station dialog which lists all the
stations and the attributes for a selected station.
Changing a Station's Identification
To modify a station’s name and number:
1
Choose Station > Modify/Remove....
The system displays the Modify/Remove Stations dialog.
Modify/Remove Stations Dialog
2
Select the station you want to change, then choose Modify....
The system displays the Modify Station dialog for the selected station. This displays the station
number and name, the station types assigned, the workgroup the station belongs to.
114
Modify Station Dialog
3
Type the new station name and number in the Station name and Station number fields
respectively, then choose OK.
The system updates the station’s identification in the Modify/Remove Station dialog.
115
Changing Station Types
To modify the station type(s):
1
2
The system displays the Modify Station dialog for the selected station.
3
To add a type:
a
Select the station type(s) in the Options list, then choose <<.
The system moves the station type to the Selected list and is added to the list of types for
the selected station.
b
4
When you are finished adding types, choose OK.
To remove a type:
a
Select the station type(s) in the Selected list, then choose >>.
The system removes the type from the list of types for the selected station.
Note: You cannot remove a station type if software that requires this type is installed on the station.
b
When you are finished removing types, choose OK.
Changing Station Groups
To modify the station group(s):
1
2
The system displays the Modify Station dialog for the selected station.
To add a station group, do the following:
a
Select the station group(s) in the Options list, then choose <<.
The system moves the station group to the Selected list and is added to the list of station
groups for the selected station.
b
When you are finished adding station groups, choose OK.
To remove a station group, do the following:
a
Select the station group(s) in the Selected list, then choose >>.
The system removes the station group from the list of groups for the selected station.
b
116
When you are finished removing station groups, choose OK.
Switching EPUs or ESUs
If a transport hardware problem occurs in the middle of a run, you may have to take the EPU or ESU
offline even though there is work left to be done on it. In this case, ImageMark Transaction Manager
has already associated the work with this particular station number, and the system expects to
complete that work with the same station number information.
To work around this problem, Configuration Manager lets you switch the station number of the offline EPU or ESU with the station number of another transport that is free. You can then finish your
work on the other unit.
Before You Begin
Before switching transports please review the following:
!
A transport station may only be switched with another transport station that is configured with
the same application software.
For example, a station that is configured to run an ESU application may only be switched with:
!
another ESU
!
an EPSU that is configured with the ESU software
!
The transport station cannot already be switched with another station.
!
If you have switched an EPU transport with an EPSU, you cannot run the EPSU as an ESU until
you have switched the EPSU back to the original station ID. The same is true if you have switched
an ESU with and EPSU: you cannot run an EPU application until you have switched the EPSU
back to its original station ID.
!
You must ensure that the active transport you want to switch to has properly completed its
previous run.
Switching a Transport
To switch an EPU or ESU:
1
Ensure that operators exit from the Image Capture or Encode and Sort activity and sign-off their
stations.
Notes: 1 When signing-off Image Capture, do not end the entry.
2
3
When signing-off Encode and Sort, do not end the trayset.
Choose Station > Switch Stations.
The system displays the Switch Station Numbers dialog. It lists all the stations by name and
number.
117
Switch Station Numbers Dialog
4
In the First Station list, select the EPU or ESU that you are taking out of service.
5
In the Second Station list, select the EPU or ESU that you are going to use instead.
Note: You cannot switch a station that is already switched. To see if a station is switched, open the
Modify/Remove Stations dialog. If the Current Station ID is different than the Original Station
ID, then the station is currently switched with another station.
6
Choose Switch.
The system switches the selected stations.
Note: To ensure that the switch has been done correctly, display the Modify/Remove Stations dialog
for the station you switched. Check the Original Station ID and Current Station ID fields and
make sure that the numbers are different. Then record the change in your site configuration
records.
7
Move all documents (in the hopper and pockets) from the failed transport to the working
transport.
8
Start the destination transport.
The recovery screen lists the last good item captured, and may ask the operator to re-run certain
items.
You can now use the new transport controller to run the work for the failed transport controller.
Switching Back
The procedure for switching back to the original transport is the same as above.
118
Removing a Station
When you delete a station from the system configuration, you must first remove its parameter sets,
then software. You should also consider the impact on other stations (for example, if you are deleting
a station that provides a service to other stations, you must modify the other station configurations
to receive the service from another source).
To delete a station:
1
Remove any parameter sets that have been configured for that station. See “Adding and
Removing Parameter Sets” on page 133.
2
Remove the software that has been configured for that station. See “Adding and Removing
Application Software” on page 128.
3
The system displays the following dialog, which lists the configured stations and displays
information about the selected station.
Modify/Remove Stations Dialog
4
Select the station that you want to delete. If the parameter sets and application software have
been removed from the station, the Remove button becomes active.
5
Choose Remove.
6
The system removes the station from the list of station names.
Note: If you try to remove a station (server) while any of the storage spaces on the station are in
the “Freeing” or “Initializing” state, the system displays an error dialog indicating that the
station cannot be removed until its state has changed.
119
Managing Storage Spaces
The Storage Space Manager allows the operator to initialize and free storage spaces in the system,
depending on the status of each storage space.
Storage Space Manager Dialog
The Status column shows the status of each storage space. Each status indicates the following
information about the storage space:
!
Free: Storage space is free (storage space on all servers is free)
!
Initializing: Storage space is in the initializing process (either whole storage space or storage
space on selected servers)
!
Initializing Failed: Storage space has failed the initialization process (at least one storage space
on a server failed initialization)
!
Initialized: Storage space has been successfully initialized and is ready to be associated with
cycles (either whole storage space or storage space on included servers)
!
In Use: Storage space is associated with at least one cycle (either whole storage space or
storage space on included servers)
!
In Use/Initializing: Storage space is associated with at least one cycle and the storage space
on at least one of the excluded servers is in the initializing process
!
Freeing: Storage space is in the freeing process (either whole storage space or storage space
on selected servers)
!
Freeing Failed: Storage space has failed the freeing process (at least one storage space on a
server failed freeing)
Note: A red asterisk (*) beside a storage space indicates that some servers have been excluded
from the initialization for that particular storage space. The asterisk should disappear the next
time this Storage Space is initialized.
120
The Storage Space Manager also provides the following information:
!
Initialize Date: Indicates what date the storage space was successfully initialized.
!
Initialize Time: Indicates what time the storage space was successfully initialized.
Note: If the storage space is initialized successfully after excluding a failed server and the user
successfully initializes the storage space on the failed server later, the date and time shown
does not change. If a storage space is not in either the “Initialized”, “In Use” or “In
Use/Initializing” state, the date and time are blank.
Storage Space Manager Security
Access security checks have been added for the Storage Space Manager. Before using this tool to
initialize and free storage spaces, you must be added to the Administration workgroup using Access
Security Manager.
Adding a User to the Administration Workgroup
See “Modifying a User Account” on page 150.
If the user has not been added to this workgroup, the system displays the following error message
when they try to run the Storage Space Manager:
Storage Space Manager Security Error
121
Initializing a Storage Space
You can initialize a storage space if:
!
the Status column says the storage space is “Free”
!
no other storage spaces have a status of “Freeing”, “Initializing”, or “In Use/Initializing”
As a special case, a storage space can be initialized if it has both a status of .Initialized. and it is
marked by a red asterisk (*).
In all other cases, you must free the storage spaces before you can initialize them. See “Freeing a
Storage Space” on page 124.
Note: If you receive an error message while attempting to initialize a storage space, the status of
the storage space changes to “Initialization Failed”. For more information about handling
initialization errors, see “Troubleshooting Freeing and Initialization” on page 326.
To initialize a storage space:
1
Choose Storage > Space Manager.
The system displays the Storage Space Manager dialog.
2
Select a storage space, then choose Initialize....
The system displays the Initialize Storage Space dialog. This dialog serves as a progress
monitor of each server during the initialization process of a storage space and as an interface
from which users can exclude or attempt initializing of selected servers during a failed (or
incomplete) state.
122
Initialize Storage Space Dialog
The Server Status column indicates if the server was made unavailable outside of the Storage Space
Manager.
The Status column provides the following status information as each storage space initializes:
!
Initializing: Storage space on the server is in the initializing process
!
Initializing Failed: Storage space on the server has failed the initialization process
!
Initialized: Storage space on the server has successfully initialized
!
In Use: Storage space has been initialized and is In Use (another server may not have had their
storage space initialized successfully)
!
Free: A new server has been added to the system and has not been initialized
The Excluded column indicates if the server has been excluded from the initialization of the Storage
Space by providing the following specifics:
!
User Excluded: The user decided to exclude the server from the Initialization process
!
Auto Excluded: The system excluded the server from the Initialization process. For example, if
a DAP failed initialization and the user excluded it, all Data Servers that belong to the same
Station group as the DAP must be excluded.
3
Select the server you want to initialize on the storage space, then choose Initialize....
Note: The server you choose must have at least one Storage Space Status on the server as
“Initializing Failed” or “Free”, and its Server Status as “Available”. Otherwise, the system will
not allow you to initialize the storage space.
The system displays the Initialize dialog. This dialog lists only the servers with a status of
“Initializing Failed”.
123
Initialize Dialog
4
Select the server(s) from the list that you want to initialize, then choose Initialize.
The system begins the initialization process for the selected servers. The system returns to the
Initialize Storage Space dialog where the status of the selected servers changes to “Initializing”.
When all servers are initialized successfully, the status of the storage space changes to
“Initialized”.
Note: If the storage space on all the servers that are not excluded is in the “Initialized” status, the
status of the storage space in the Storage Space Manager dialog shall change to “Initialized”.
Freeing a Storage Space
A storage space may be freed if the following conditions are met:
!
The storage space has a status of “In Use”.
!
All cycles associated with the storage space are at the “End” state.
!
No other storage spaces have a status of “Freeing”, “Initializing”, or “In Use/Initializing”.
Besides the conditions described above, a storage space may also be freed in either of the following
cases:
!
The storage space is in the “Freeing” state.
!
The storage space has a status of “Freeing Failed”, and no other storage spaces are in the
“Freeing”, “Initializing” or “In Use/Initializing” state
If you receive an error message while attempting to free a storage space, the status of the storage
space will change to “Freeing Failed”. For more information on handling freeing errors, see
“Troubleshooting Freeing and Initialization” on page 326.
To free a storage space:
1
2
Select a storage space, then choose Free....
The system displays the Free Storage Space dialog.
124
Free Storage Space Dialog
The Storage Space Status column provides the following information about the storage space
on each server:
!
Freeing: The Storage space on the server is in the freeing process
!
Freeing Failed: The Storage space on the server has failed the freeing process
!
Free: The Storage Space on the server has been successfully freed
A storage space can be freed if at least one storage space has a status of “Freeing Failed” and
its server status is “Available”.
3
Select the server you want to free in the storage space, then choose Free….
The system displays the Free dialog. This dialog lists only the servers with a “Freeing Failed”
status and whose server status is “Available”.
Free Dialog
4
Select the server(s) from the list that you want to free, the choose Free.
The system frees the selected server(s). The system returns to the Free Storage Space dialog
where the status of the server(s) changes to “Freeing”.
When all servers are freed successfully, the status of the storage space will change to “Free”.
At any time, you can refresh the window to view the storage space as it updates by choosing Refresh.
125
Excluding a Server in a Storage Space
A server within a storage space can be excluded from the initialization process. Servers that can be
excluded must have a storage space status of “Initializing Failed”, a server status of “Available”, and
not have been excluded.
Note: BAPs cannot be excluded from the system.
To exclude a storage space:
1
The system displays the Storage Space Manager dialog.
2
Select a storage space, then choose Initialize....
The system displays the Initialize Storage Space dialog.
Initialize Storage Space Dialog
3
126
Select the server you want to exclude, then choose Exclude.
The system updates the status of the selected server to “User Excluded” and is marked with a
red * in the Storage Space Manager dialog.
Note: Any sub-servers of the excluded server (e.g., a DS that is a sub-server of a DAP) will have
a status of “Auto Excluded”.
At any time, you can refresh the window to view the storage space as it updates by choosing Refresh.
Monitoring the State of Storage Spaces
The system continually monitors and updates the state of storage spaces using a monitoring script.
The script makes a connection to each server on the list and verifies if the initializing or freeing
process is still running. If the process is not running on a server, the monitoring script checks the
%IMAGEMARK_ROOT%\opt\siips directory for an output file that was modified after the state of
the storage space on the server was last changed to the “Initializing” or “Freeing” state. If the file
exists (identified by server name and storage number), the monitoring script searched the file for
errors.
If an error message is found, the script will change the state of the storage space to “Initializing
Failed” or “Freeing Failed”.
If no error is found, the script will search the file for a success message. If a success message is
found, the script will change the state of the storage space to “Initialized” or “Free”.
127
Adding and Removing Application Software
Whether you add or remove software, you can do it in two ways:
!
Select a package of software and configure it on one or more stations in a single operation. This
is the best method to use if the same software is on several stations.
!
Select a station and configure one or more packages on the one station in a single operation.
This is the best method to use if you have just added a station or are removing just one station.
If you are removing software from a station's configuration, you must remove any related parameter
sets first.
Configuring Software by Package
A package consists of the software programs required to perform a particular activity (activity or
auto-activity), such as Image Capture, or Balanced I-String Extract. Configuration Manager knows
which packages can be configured on which types of stations. For example, it will not allow the EPU
Image Capture software package to be configured on an IDT. However, it may allow it to be
configured on an ESU since the ESU could have been configured as an EPU type also.
Adding Software by Package
Before adding software to the configuration, ensure that the software has actually been installed on
the applicable stations.
1
Choose Software > By Package....
The system displays the Configure Software by Package dialog that lists all available software
packages.
Configure Software by Package
The Stations where configured list is empty if a software package is selected, but not yet
assigned to any station.
2
128
Select the package that you want to configure.
The Stations where configured list displays the stations on which that package is already
configured.
3
Choose Add....
The system displays the Add Package on Stations dialog. This dialog lists the names of any
stations which do not have the selected software configured.
Note: The Add Package on Stations dialog does not list a station of a type that is not allowed to
use that software package.
Add Package on Stations Dialog
4
Select the station(s) which are to be configured, then choose OK.
5
The stations you configured with the software package are listed in the Stations where
configured list.
129
Removing Software by Package
Before attempting to remove software by package from more than one station, ensure that the
parameter sets have been removed from the stations.
1
Choose Software > By Package....
The system displays the Configure Software by Package dialog.
Configure Software by Package Dialog
2
Select the package that is to be removed from the configuration of one or more stations.
The Stations where configured list displays the names of stations which are configured with the
selected package.
3
Select the station(s) from which you want to remove the software, then choose Remove.
4
The selected stations are removed from the Stations where configured list.
130
Configuring Software by Station
If you have added one station, use the By Station command from the Software menu to add the
required software packages to the new station's configuration. Similarly, if you plan to delete a
station, use this command to delete the software from the station.
Adding Software By Station
To add one or more packages of software to a station:
1
Choose Software > By Station....
The system displays the Configure Software by Station dialog that lists all the configured
stations.
Configure Software by Station Dialog
2
Select a station.
The Packages list displays the packages already configured on the selected station in the
Stations where configured list.
3
Choose Add....
The system displays the Add Packages on Station dialog.
Add Packages on Station Dialog
131
4
Select the software package(s) to be added to this station's configuration, then choose OK.
5
The selected software packages are added to the Packages list for that specific station.
Removing Software
Before removing software from a station configuration, ensure that the parameter sets have been
removed from that station.
1
Choose Software > By Station....
The system displays the Configure Software by Station dialog.
2
Select a station.
The Packages list displays the names of software already configured on the selected station in
the Stations where configured list.
3
Select the software package(s) from the Packages list, then choose Remove.
4
The selected software packages are removed from the Packages list for that specific station.
132
Adding and Removing Parameter Sets
Similar to the software procedure, you can add and remove parameter sets by package and by
station, but only one set or station at a time. This restriction is because you must assign a service
to each set/station.
Some parameter sets are required by every station in the system. Others are exclusive to one type
of station. Some parameters in some sets also require information from other services that may be
located on other priority stations.
You may need to modify the sources of services used by parameter sets on the various stations.
For example, a server that provides services to many stations may become overloaded. If the same
type of service is available from more than one server, you can change the server they use.
Notes on Adding Parameter Sets
These notes pertain to adding parameter sets either by station or by package
Notes: 1 Since higher priority stations provide services to lower priority stations, we recommend
that you configure stations in the following order:
!
BAP
!
DAP, which uses services provided by BAP
!
DS, which uses services provided by DAP
!
TSS and IDT, which use services provided by DAP and DS
!
EPU and ESU, which provide services for themselves
This makes the overall configuration easier because once you configure services for a
higher priority station, the system will provide those services by default when you set
up a lower priority station.
2
When adding parameters to a station, we recommend that you add their Application
Services before adding their Application Components because once the services are
configured, the system can use them to set defaults for the components.
For example, when you add parameters to a new EPU, you have the following choices:
! Image Capture (the Application Component)
!
Item Edits IPCS Service (the Application Service)
In this case, add Item Edits IPCS Service first, then add Item Capture. This way, the
system will automatically set up the Image Capture application to access services
provided by Item Edits IPCS on the same EPU rather than accessing services provided
by a remote station.
133
Configuring Parameter Sets by Package
You can add or remove parameter packages from a station using the By Package command from
the Parameter Sets menu.
Note: You can also use this command to view what stations have been configured with a specific
parameter package.
Adding a Parameter Set by Package
To add a parameter set by package:
1
Choose Parameter Sets > By Package....
The system displays the Configure Parameter Sets by Package dialog.
Configure Parameter Sets by Package Dialog
2
Select the application type from the Application list.
3
Select the package that is to be configured from the Packages list.
The Stations where configured list displays the stations that have already been configured with
this parameter set.
4
Choose Add....
The system displays the Add Parameter Sets dialog. The Available stations list shows the
stations on which the selected parameter set can be configured.
134
Add Parameter Set Dialog
5
Select a station, then choose OK.
The system displays the Services dialog. This dialog lists the services that are required by the
parameter set being added. It also displays the name of the package, name of the station, service
type, and status of the service that you selected.
Services Dialog
The Station list displays a station adapter name for each default service based on the following
priority:
!
loopback (if applicable to the service)
!
stations in the current station group (secondary network, then primary)
!
other stations (secondary network, then primary)
Note: When you select a default service from the listed services, the Current station field below
this list shows the current service that the station is using. If the name of this service is different
than the name of the selected default service, it means that the station has been configured
with a different station group.
135
6
If the default services are satisfactory, choose OK. Otherwise, do the following to select a
different station:
a
Select a service class, then choose Edit....
The system displays the Select an Adapter dialog. This dialog lists the adapters for the
stations that offer the selected service.
Note: For effective response times, you should consider the total demand for these services on a
station when deciding which station is to provide the selected service.
Select an Adapter Dialog
b
Select an adapter name for the required service, then choose OK.
The system updates the station for the selected service in the Services dialog.
c
7
When you have completed defining the sources for services, choose OK.
The system adds the selected parameter set to the station.
Modifying Services By Package
To modify a service by package:
1
2
Select the application type from the Application list.
3
Select the parameter package you want to modify from the Packages list.
The Stations where configured list displays the stations that have already been configured with
this parameter set.
4
Choose Services....
The system displays the Services dialog. This dialog lists the name of the parameter set, the
name of the station on which the set is configured, the services required by this parameter set,
and the servers that are currently providing them.
136
5
Select the service that you want the station to obtain from a different server, then choose
Modify....
The system displays the Modify Services dialog. This dialog lists the adapter names of all servers
of the type that you just selected.
Modify Services Dialog
6
Select an alternative server from the Adapters list, then choose OK.
The Services dialog displays the service and the name of the server that you selected.
7
When you are finished, choose OK.
8
The system updates the parameter set and places an ‘M’ in the Status column for the selected
service.
Removing a Parameter Set
To remove a parameter set from a station:
1
2
Select the parameter package that is to be removed from the configured stations.
The Stations list displays the stations that have already been configured with this parameter set.
3
Select a station, then choose Remove.
4
The station on which the selected parameter set was configured is removed from the Stations
where configured list.
137
Configuring Parameter Sets by Station
You can also add or remove a parameter set from a station with the By Station command.
Note: You can also use this command to view what parameter sets are configured on specific
stations.
Adding a Parameter Set by Station
When you add parameter sets by station, you also add any services that the parameter sets require.
Note: Add services to stations before adding the other kinds of parameter sets.
To add a parameter set by station:
1
Choose Parameter Sets > By Station....
The system displays the Configure Parameter Sets by Station dialog.
Configure Parameter Sets By Station Dialog
2
Select a station from the Stations list.
The Packages configured list displays the parameter set or sets already configured on the
selected station.
3
Choose Add....
The system displays the Add Package on Station dialog. The Available packages list shows all
the parameter sets available for the selected station's type.
138
Add Package on Station Dialog
4
Select a parameter set, then choose OK.
The system displays the Services dialog. This dialog lists the services that are required by the
parameter set being added. It also displays the name of the package and the name of the station
that you had selected.
Services Dialog
The Station list displays a station adapter name for each default service based on the following
priority:
5
!
loopback (if applicable to the service)
!
stations in the current station group (secondary network, then primary)
!
other stations (secondary network, then primary)
If the default services are satisfactory, choose OK. Otherwise, do the following to select a
different station:
a
To select a different station which is to provide the service, select a service class, then
choose Edit....
139
The Select an Adapter dialog lists the adapter names for the stations that offer the selected
service.
Note: For effective response times, you should consider the total demand for these services on a
station when deciding which station is to provide the selected service.
Select an Adapter Dialog
b
Select an adapter name for the required service, then choose OK.
The Services dialog displays the name of the servicing station after the service that you had
selected.
c
6
When you have completed defining the sources for services for each package being
configured on the station, choose OK.
The system displays the Configure Parameter Sets by Station dialog. The parameter sets you
had selected now appear in the Packages configured list for the station you had selected.
140
Modifying Services By Station
1
The system displays the Configure Parameter Sets by Station dialog.
2
Select a station from the Stations list.
The Packages configured list displays the parameter set(s) already configured on the selected
station.
3
Select the parameter package you want to modify from the Packages configured list.
4
Choose Services....
The system displays the Services dialog. This dialog lists the name of the parameter set, the
name of the station on which this set is configured, the services that this set requires, and the
servers that are currently providing these services.
5
Select the service that you want the station to obtain from a different server, then choose
Modify....
The system displays the Modify Services dialog.
Modify Services Dialog
6
Select a new server from the Adapters list, then choose OK.
The Services dialog displays the service and the name of the server that you selected.
7
The system updates the parameter set with the new station and places an ‘M’ in the Status
column for the selected service.
141
Removing Parameter Sets
1
The system displays the Configure Parameter Sets by Station dialog. All stations are listed in
the Stations list.
2
Select a station from the list.
The Packages configured list displays the parameter set or sets already configured on that
station.
3
Select a parameter set, then choose Remove.
4
The parameter set you removed no longer appears in the Packages configured list for the station
you selected.
142
4
Access Security Manager
This chapter tells you how to use the Access Security Manager to create, modify, and delete user
accounts and assign permissions to use ImageMark Transaction Manager activities and services.
143
Chapter 4: Access Security Manager
Starting Access Security Manager
Starting Access Security Manager
To perform any of the tasks described in this chapter, you must use the ImageMark Transaction
Manager Access Security Manager utility.
To start Access Security Manager, proceed as follows:
In Task Manager, choose Access Security Manager from the Utilities list.
Note: If the Utilities list is not already displayed, choose Tasks > Utilities.
The system displays the Access Security Manager window.
Access Security Manager Window
144
Managing User Workgroups
Every user working on the ImageMark Transaction Manager system must be assigned to a
workgroup. Before you can create user accounts, you must therefore use Access Security Manager
to create the workgroups themselves.
Viewing Workgroups
To view the workgroups that exist on the system, choose Workgroups > View.
The system displays the View Workgroups dialog.
View Workgroups Dialog
145
Creating a Workgroup
To create a new workgroup:
1
Choose Workgroups > Add....
The system displays the Add Workgroup dialog.
Add Workgroup Dialog
2
Type a name for the workgroup in the Workgroup Name field.
3
Type a number for the workgroup in the Workgroup Number field, then choose OK.
The system adds the new workgroup.
Modifying a Workgroup
You may need to change the name or number of a workgroup if, for example, you are reorganizing
the operators.
To modify a workgroup:
1
Choose Workgroups > Modify....
The system displays the Modify Workgroup dialog.
Modify Workgroup Dialog
2
Select a workgroup, then choose Modify....
The system displays the Modify Workgroup dialog.
146
Modify Workgroup Dialog
3
Type the new workgroup name in the New name field.
4
Type the new workgroup number in the New number field, then choose OK.
5
The system modifies the selected workgroup.
Deleting a Workgroup
Occasionally, you may need to remove a workgroup if, for example, you reorganized the operators
into fewer workgroups.
Note: A workgroup cannot be deleted if users are assigned to it.
To delete a workgroup:
1
Choose Workgroups > Remove....
The system displays the Remove Workgroups dialog.
Remove Workgroups Dialog
2
Select the workgroup(s) you want to remove, then choose Remove.
3
The system deletes the workgroup(s).
147
Managing User Accounts
Before anyone can work on an ImageMark Transaction Manager system, you must use Access
Security Manager to create a user account for them. Each account will specify the user name, full
name, description, and user ID.
Note: Before you can create an ImageMark Transaction Manager user account, the user must have
a Windows user account.
Creating a User Account
To create a new user account:
1
Choose Users > Add....
The system displays the Add User dialog.
Add User Dialog
2
Choose Browse... to select a Windows user name.
The system displays the Select User dialog.
148
Select User Dialog
3
Select the location, then choose OK.
The system returns to the Add User dialog where the selected user name is populated into the
User name field.
Add User Dialog With User Name Added
4
Type a user ID in the User ID field (a number from 0 to 999).
Note: Full name and Description are provided by Windows.
5
Select a workgroup from the Select workgroup list, then choose OK.
6
The user is added to the system.
149
Modifying a User Account
You may need to change a user’s account if, for example, they change their name. You may also
need to change someone’s password if they forget it.
To modify a user account:
1
Choose Users > Modify/Remove....
The system displays the Modify/Remove User dialog.
Modify/Remove User Dialog
2
Select the user whose account you want to modify, then choose Modify....
The system displays the Modify User dialog.
Modify User Dialog
3
Type the user’s new ID in the Modify user ID field.
4
Select a new workgroup from the Modify workgroup list box.
5
Choose OK.
The system modifies the user account with the new user ID and workgroup.
150
Deleting a User Account
Delete a user account whenever that user permanently leaves the workgroup, for example, if they
leave the company or get transferred to another department.
To delete a user account:
1
Choose Users > Modify/Remove....
The system displays the Modify/Remove User dialog.
2
Select the user you want to remove, then choose Remove.
3
The system deletes the selected user account.
User Passwords and Security Procedures
In the ImageMark Transaction Manager Operations course, operators learn how to perform the
following security-related procedures:
!
signing on with their user name and password
!
locking their terminal when leaving on a break
!
signing off at the end of their shift
As system administrator, you may wish to establish site-specific policies to ensure that these
procedures are followed.
151
Managing User Permissions
Once you have created users’ accounts, you must assign them permissions for the activities and
services they need to use. There are two ways to assign permissions:
!
By user: one user at a time, assigning permissions for each activity or service that user needs
!
By activity: one activity (or service) at a time, assigning permissions to all of the users who need it.
Assigning Permissions by User
To assign permissions by user:
1
Choose Permissions > By User....
The system displays the Assign Permissions by User dialog.
Assign Permissions by User Dialog
2
From the Users list, select the user to whom you want to assign permissions.
The Activities Permitted list is updated to show the activities for which this user already has
permissions.
3
Choose Add....
The system displays the Add Permissions by User dialog.
152
Add Permissions by User Dialog
4
Select the application you want to use from the Applications list box.
5
Select the activity or service you want to assign the user permissions to, then choose OK.
Note: You may choose more than one activity or service.
The activity or service is added to the user’s Activities Permitted list.
153
Assigning Permissions by Activity
To assign permissions by activity:
1
Choose Permissions > By Activity....
The Assign Permissions by Activity dialog appears.
Assign Permissions by Activity Dialog
2
Select the application you want to use from the Applications list box.
3
Select the activity or service for which you want to assign permissions.
Note: You may choose both a service and an activity.
The Current users list is updated to show who already has permission to use this activity or
service.
4
Choose Add....
The system displays the Add Permissions by Activity dialog.
154
Add Permissions by Activity Dialog
5
Select the user(s) to whom you want to give permission to use the selected activity or service,
then choose OK.
The users for the selected activity or service are added to the Current users list.
155
Removing Permissions by User
To remove a user’s permissions for one or more activities or services:
1
Choose Permissions > By User....
The system displays the Assign Permissions by User dialog.
Assign Permissions by User Dialog
2
Select the user for whom you want to remove permissions.
The Activities Permitted list is updated to show the activities and services for which this user
currently has permissions.
3
Select an activity or service for which you want to remove this user’s permission, then choose
Remove.
4
The selected service or activity is removed from the Activities Permitted list.
156
Removing Permissions by Activity
To remove a user’s permissions for one or more activities or services, proceed as follows.
1
Choose Permissions > By Activity....
The system displays the Assign Permissions by Activity dialog.
Assign Permissions by Activity Dialog
2
Select the activity or service for which you want to remove permissions.
The Current users list is updated to show who already has permission to use this activity or
service.
3
Select the user(s) for whom you want to remove permissions to the selected activity or service,
then choose Remove.
4
The selected user(s) is removed from the Current users list for the selected activity or service.
157
158
5
Reports
ImageMark Transaction Manager offers a wide variety of reports. The reports fall into these
categories:
!
end-of-cycle reports
!
operator performance reports
!
auto-activity reports
Note: There is one report that does not fall into any of these categories. For details, see “To locate
and print the Modified Item Export report:” on page 254.
End-of-cycle reports and operator performance reports are printed by the Report utility, while autoactivity reports are generated and printed automatically or manually by the command line.
You can change the reporting period for operator statistics using the set_rpt_defn.pl utility.
Instructions are included in this chapter.
This chapter tells you how to use the Report utility to select and print the end-of-cycle and operator
performance reports and to generate and print auto-activity reports. This chapter also provides
detailed descriptions of all reports.
Note: Report samples are included in Appendix A.
159
Chapter 5: Reports
Changing Reporting Periods
You can change the reporting periods used to generate operator performance reports. This lets you
ensure that these reports take into account such site-specific variables as hours of operation, and
different operators working different shifts.
rptperiod.cfg_sample file
# These default values represent a reporting period for each
# normal working day plus one for the weekend
NumOfPeriods = 6
RptPeriodNum = 1
RptPeriodName = “Monday”
StartDay = 1
StartTime = 10:00
RptPeriodNum = 2
RptPeriodName = “Tuesday”
StartDay = 2
StartTime = 10:00
RptPeriodNum = 3
RptPeriodName = “Wednesday”
StartDay = 3
StartTime = 10:00
RptPeriodNum = 4
RptPeriodName = “Thursday”
StartDay = 4
StartTime = 10:00
RptPeriodNum = 5
RptPeriodName = “Friday”
StartDay = 5
StartTime = 10:00
RptPeriodNum = 6
RptPeriodName = “Weekend”
StartDay = 6
StartTime = 10:00
This sample file defines 6 reporting periods: one for each weekday, plus one for the weekend. This
is typical of a traditional OTC Capture environment, where reports are printed at end of day.
160
Chapter 5: Reports
Example
In the following example, the sample configuration file has been modified to include 14 reporting
periods (2 per day). This represents a typical 24-hour ImageMark environment. Errors detected
across reporting periods will be reflected in the operator statistics reports.
modified rptperiod.cfg file
# These default values represent 2 reporting periods for each
# day of the week
NumOfPeriods = 14
RptPeriodNum = 1
RptPeriodName = “Monday Noon to Monday Midnight”
StartDay = 1
StartTime = 12:00
RptPeriodNum = 2
RptPeriodName = “Monday Midnight to Tuesday Noon”
StartDay = 1
StartTime = 24:00
RptPeriodNum = 3
RptPeriodName = “Tuesday Noon to Tuesday Midnight”
StartDay = 2
StartTime = 12:00
RptPeriodNum = 4
RptPeriodName = “Tuesday Midnight to Wednesday Noon”
StartDay = 2
StartTime = 24:00
RptPeriodNum = 5
RptPeriodName = “Wednesday Noon to Wednesday Midnight”
StartDay = 3
StartTime = 12:00
RptPeriodNum = 6
RptPeriodName = “Wednesday Midnight to Thursday Noon”
StartDay = 3
StartTime = 24:00
RptPeriodNum = 7
RptPeriodName = “Thursday Noon to Thursday Midnight”
StartDay = 4
StartTime = 12:00
RptPeriodNum = 8
RptPeriodName = “Thursday Midnight to Friday Noon”
StartDay = 4
StartTime = 24:00
161
Chapter 5: Reports
RptPeriodNum = 9
RptPeriodName = “Friday Noon to Friday Midnight”
StartDay = 5
StartTime = 12:00
RptPeriodNum = 10
RptPeriodName = “Friday Midnight to Saturday Noon”
StartDay = 4
StartTime = 24:00
RptPeriodNum = 11
RptPeriodName = “Saturday Noon to Saturday Midnight”
StartDay = 6
StartTime = 12:00
RptPeriodNum = 12
RptPeriodName = “Saturday Midnight to Sunday Noon”
StartDay = 6
StartTime = 24:00
RptPeriodNum = 13
RptPeriodName = “Sunday Noon to Sunday Midnight”
StartDay = 7
StartTime = 12:00
RptPeriodNum = 14
RptPeriodName = “Sunday Midnight to Monday Noon”
StartDay = 7
StartTime = 24:00
In this example:
!
operator 1 works 2:00 p.m. to 10 p.m., but some of this work is not balanced until after midnight
!
operator 2 works 6:00 p.m. to 2:00 a.m.
!
operator 3 works 12:00 a.m. to 8:00 a.m.
After reporting period 1, the 1st report would include:
!
data for operator 1
!
some data for operator 2
After reporting period 2, the 2nd report would include:
!
any errors found for operator 1
!
some data for operator 2
!
data for operator 3
The data in each report is mutually exclusive. Therefore, the data for operator 1 contained in the
2nd report would include only the errors found at balancing after midnight.
162
Chapter 5: Reports
How To Change Reporting Periods
To change reporting periods:
1
Copy %IMAGEMARK_ROOT%\opt\siips\rptperiod.cfg_sample to rptperiod.cfg on the BAP.
2
Modify rptperiod.cfg to meet your site’s needs (see example above).
3
Run set_rpt_defn.pl.
The utility makes the necessary updates.
163
Chapter 5: Reports
Starting Reports Utility
Starting Reports Utility
The Reports utility allows you to select and print the end-of-cycle reports and operator performance
reports.
To start the Reports utility:
1
In Task Manager, choose Tasks > Applications.
2
From the Applications running list, choose the name of the application for which you want to
generate reports.
The system updates the Application activities list.
3
Choose Reports Utility from the Application activities list.
The system displays the Reports utility window.
Reports Utility Window
164
Chapter 5: Reports
Printing Reports
Printing Reports
Automatically Printing or Saving Reports
The Automatic Report Print utility generates all end-of-cycle reports and Operator Performance
reports in one step. The type of reports to print, and the print destination (printer or file), are specified
in the rptutil.dat file, under the RPT_UTIL_GEN keyword.
To run the Automatic Report Print utility:
1
Choose File > Automatic Print....
The system displays the confirmation dialog.
Confirmation Dialog
2
The system processes the reports.
In addition to being able use the Report utility to automatically print or save end-of-cycle reports and
operator performance reports, you can also initiate the process from the command line using the
autorpt Perl script. For details, contact NCR Support.
165
Chapter 5: Reports
Printing Reports
Manually Printing End-of-Cycle Reports
To manually print a report or save it as a file:
1
Choose File > Print > End Of Cycle Reports....
The system displays the Print End Of Cycle Report(s) dialog.
Print Report(s) Dialog for End-of-Cycle Reports
2
Select the report that you want to print or save, then choose Options.
The system displays the Options dialog for end-of-cycle reports.
Note: Although all print options are enabled for all reports, some options have no effect on some
reports.
166
Chapter 5: Reports
Printing Reports
Print Options Dialog for End-of-Cycle Reports
3
In the Cycles list, specify whether you want the report to include all cycles or one of the listed
cycles. This list is restricted to cycles with a state of Open, Closed, or End.
Note: If “All” is selected, then all cycles with a state of Open, Closed, and End will be used in the
report.
4
In the Database hosts list, specify whether you want the report to include data for all hosts or
one of the listed hosts.
5
In the Printer list, select the desired printer queue to print the report or select FILE to save the
report as a file. (The filename reflects the report type. By default, the file is saved under the
directory %IMAGEMARK_ROOT%\opt\siips\archive.)
6
Choose OK.
7
In the Print Report(s) dialog, choose Print.
The system proceeds to print or save the reports.
167
Chapter 5: Reports
Printing Reports
Manually Printing Operator Performance Reports
To manually print a report or save it as a file:
1
Choose File > Print > Operator Statistics....
The system displays the Print Operator Statics dialog.
Print Report(s) Dialog for Operator Performance Reports
2
Select the report that you want to print or save, then choose Options.
The system displays the Options dialog for operator performance reports.
Note: Although all print options are enabled for all reports, some options have no effect on some
reports.
168
Chapter 5: Reports
Printing Reports
Print Options Dialog for Operator Performance Reports
3
In the Reporting period list, select the reporting period(s) you want to print.
Note: To help you find the desired reporting period, the Reporting period list box provides additional
information for each reporting instance, such as the start date and start time.
4
In the Workgroups list, specify whether you want the report to cover all workgroups or one of
the listed workgroups.
5
In the Printer list, select the desired printer queue to print the report or select FILE to save the
report as a file. (The filename reflects the report type. By default, the file is saved under the
directory %IMAGEMARK_ROOT%\opt\siips\archive.)
6
Choose OK.
7
In the Print Report(s) dialog, choose Print.
The system proceeds to print or save the reports.
169
Chapter 5: Reports
Printing Reports
Deleting Generated Reporting Periods for Operator
Statistics
Once you have generated an operator performance report, you have the option to delete the
reporting period(s) that were generated or printed in the report.
Note: For more information on Delete Cycle, refer to “Managing Cycles” and “Modifying Cycles” in
chapter 2: Application Manager. For information on changing the reporting periods used to
generate operator performance reports, refer to “Changing Reporting Periods”, earlier in this
chapter.
To delete the generated reporting period statistics:
1
Choose File > Delete Statistics.
The system displays the Delete Statistics dialog. The dialog lists all reporting periods that have
been previously printed.
Delete Statistics Dialog
2
Select the reporting period you wish to delete, then choose Delete.
The system displays the Options dialog for end-of-cycle reports.
Note: An error dialog may appear warning you that reports have not been generated for the selected
reporting period. Choose Cancel if you do not wish to delete the reporting period or choose
OK to proceed in deleting the reporting instance.
170
Chapter 5: Reports
Printing Reports
Viewing Print Jobs
You can display a list of the reports that have been sent to the printer to see, for example, if a report
was printed or if other reports are ahead of it in the print queue.
To view the print jobs, choose Status > Print Jobs.
Print Job Status Dialog
The system lists the reports and displays one of the following statuses for each report:
!
Processing
!
Spooled
!
Failed
!
Deleting
!
Deleted
The system does not automatically remove spooled, deleted, or failed print jobs from this dialog. To
remove these jobs:
1
Select the print job you want to remove, then choose Clear.
2
171
Chapter 5: Reports
Printing Reports
Reports Could Not Be Generated
If a report fails to generate, the following dialog will appear after you choose Print:
Report Printing Status Dialog
1
Choose Close.
2
To fix this problem and regenerate the report:
a
Check if the Print Manager service is running. If it is not, start the Print Manager service.
b
Ensure the parameter entry in the rptutil.dat file is as mentioned in the ImageMark
Transaction Manager Parameter Generation: Application Generator manual.
c
Change to the %IMAGEMARK_ROOT%\bin directory
d
Run podrpts.
The report should now generate successfully.
172
Chapter 5: Reports
Printing Reports
Viewing Reports
To view an end-of-cycle report or operator performance report on screen after it has been printed
or saved to a file:
1
Choose File > Files....
The system displays the Report File Selection dialog, which lists the available reports.
Report File Selection Dialog
2
Select the desired report, then choose View.
The system displays the report in Notepad. Use the scrollbars to view the rest the report if it is
too big for the window.
Cancelling Print Jobs
A print job can be cancelled only when the status of the print job is in “Processing”. To cancel a print
job that is processing (waiting to be printed):
1
Choose Status > Print Jobs.
The system displays the Print Job Status dialog.
2
From the list of print jobs, select the one that you want to cancel, then choose Delete.
3
The system cancels the selected print job.
173
Chapter 5: Reports
Printing Reports
Printing End-of-Cycle Reports After the End of the Cycle
You can use Windows Task Scheduler to print the end-of-cycle reports after the end of the
processing cycle.
To print the end-of-cycle reports using Windows Task Scheduler:
1
Choose Start > Settings > Control Panel > Scheduled Tasks > Add Scheduled Task.
The system displays the Scheduled Task wizard.
2
Choose Next.
3
Select autorpt from the list, then choose Next.
4
Use the wizard to specify your desired print frequency, then choose Finish.
The end-of-cycle reports print to the printer defined for each individual report on the BAP.
Printing Reports Before the End of the Cycle
Once the entire cycle’s work has been processed, you should print all of the reports generated with
the Report utility. During the cycle, you can also print any of the following reports:
!
Unresolved Suspense Items report
!
Research Items - Exception Items in Kill Pocket report
!
Truly Missing and Free report
Note: If you print any of these reports before the end of the cycle, the report may show data for
only those entries that have been completely processed.
To determine which entries have been completely processed, proceed as follows:
1
2
174
Chapter 5: Reports
Printing Reports
3
Select the application instance that you want to display, then choose OK.
The system displays the Application Display window.
4
5
Choose Entry from the Unit of work type list box.
The entries that have been completely processed show a value of END ANY IN in the Interaction
column and Available in the State column.
175
Chapter 5: Reports
Printing Reports
Printing Auto-Activity Reports on Request
Auto-activity reports print automatically, but there are two commands that you can run on the DAP
to print out Entry Item and Tray Set reports on request. See “Printing Entry Item Reports” on page
178 and “Printing Tray Set Reports” on page 180. For example, you might use these commands to:
!
print a second copy of a set of reports that has already been printed once automatically
!
print a set of these reports that did not get printed automatically, for any of the following reasons:
!
the printer ribbon is faded and the report is unreadable
!
the printer paper is jammed, causing lines to be printed on top of each other
Note: These commands print out all Entry Item and Tray Set reports that are enabled in the report
parameters for the current application type. For more details, see the report parameter
information in ImageMark Transaction Manager Parameter Generation: ASCII Files.
The following sections tell you:
!
how to determine which DAP to run these commands on (if your system has more than one DAP)
!
how to run these commands
Identifying the DAP and Tray Set ID
If your system has only one DAP, skip this procedure. Otherwise, you must run the EIR and TSR
print commands on the DAP that processed the entry in question. To identify this DAP:
1
In the Application Display window, choose View > Work In Progress.
2
In the Unit of work type list box, select Entry.
The system displays the units-of-work classified under the Entry type.
3
Select the entry for which you want to print Entry Item or Tray Set reports, then choose UoW
Details.
The system displays the Unit-of-Work Details dialog.
176
Chapter 5: Reports
Printing Reports
UoW Details Dialog
4
Find the DAP server ID, write it down, then choose Close.
5
To determine the station name from the DAP server ID on the system:
a
Run dbaccess with the database name (for example,
dbaccess siips_base).
b
Exit dbaccess.
When printing tray set reports, you need to determine the ID of the tray set for which you want to
print the report.
To find the Tray Set ID:
1
In the Application Display window, choose View > Work In Progress.
2
Set the Unit of work type to Tray Set.
The system displays the units-of-work classified as a Tray Set type.
3
Select the Exception tray set from the list, then choose UoW Details.
The system displays the Unit-of-Work Details dialog.
4
Find the Tray Set ID, write it down, then choose Close.
177
Chapter 5: Reports
Printing Reports
Printing Entry Item Reports
You can print a complete set of Entry Item reports for any entry on request. But to make sure the
reports are meaningful, do not print them until the entry has been processed past the BIE autoactivity at least. (Use the Work In Progress dialog to check this.)
To print the Entry Item reports for an entry:
1
Log on to the DAP. (If your system has more than one DAP, use the one that you have identified
as described in “Identifying the DAP and Tray Set ID” on page 176.)
2
Progress.
3
Select the Entry unit-of-work from the list, then choose UoW Details.
The system displays the UoW Details dialog.
178
Chapter 5: Reports
Printing Reports
UoW Details Dialog
4
Note the Entry Key displayed on this screen.
5
Type eirPrint apptype EntryKey
where:
!
apptype is the name of the subdirectory under %IMAGEMARK_ROOT%\opt\siips\classa
that contains the parameter files for the current application type;
!
EntryKey is the number you obtained from the Unit of Work Details dialog.
The system displays a message asking you to confirm.
6
Choose Yes.
The system prints the Entry Item reports for that entry.
179
Chapter 5: Reports
Printing Reports
Printing Tray Set Reports
You can print Tray Set reports on request for any set of exception trays that has been processed
by the Tray Set Reports auto-activity:
To print the Tray Set reports for an entry:
1
Log on to the DAP that processed this tray set’s entry. (If your system has more than one DAP,
use the one that you have identified as described in “Identifying the DAP and Tray Set ID” on
page 176.)
2
Type tsrPrint apptype TraySetID
where:
!
apptype is the name of the subdirectory under %IMAGEMARK_ROOT%\opt\siips\classa
that contains the parameter files for the current application type
!
TraySetID is the tray set ID that you looked up previously
If the Printer Fails
If the system printer fails and is out of service, redirect the Entry Item and Tray Set reports to spool
so that the system can finish processing the units of work in progress.
To redirect the reports, see “Managing the Print Spooler” on page 64.
Printing ATM Reports
You can now generate and print ATM reports that include matched records only.
ATM reports are generated at end-of-cycle using a command-line script (not the GUI-based Report
utility).
Command Usage
This command has the following usage:
ssreport.pl -a class_name/app_type_name [-p path_string] [-h] [-D] [-w work_type] [-M]
where:
180
!
class_name is the name of the subdirectory under %IMAGEMARK_ROOT%\opt\siips\classa
that contains the parameter files for the current application type
!
app_type_name is the name of the directory from which to get parameters
!
-p path_string says to place the files in the directory path_string
!
-h displays a help screen.
!
-D turns on the debug output.
!
-w work_type lets you specify a type of work to include in the SSD files (to be included in the
reports). These are the work types:
!
0 – OTC POD
!
1 – OTC POD with SMM
!
2 – ATM
Chapter 5: Reports
Printing Reports
!
!
3 – BTM)
-M specifies to include matched records only
Printing Matched Records Only
To print reports showing matched records only:
1
Log on to the BAP.
2
Type ssreport.pl -a <class_name/app_type_name> -M
181
Chapter 5: Reports
End-of-Cycle Reports
When you generate the end-of-cycle reports after the system has processed all of the cycle’s work,
they provide a complete overview of a cycle’s work.
The main categories of end-of-cycle reports are as follows:
182
!
Adjustment Summary report
!
Amount Suspect Summary report
!
ATM reports
!
Audit reports
!
Automatic Codeline Completion Statistics report
!
BIE, EIE, and SIE Deadline reports
!
BTM reports
!
Bundle List report
!
Daily Corrections Export reports
!
EPU Exception Item reports
!
Forced Adjustment report
!
Image Quality reports
!
Items Aged Out report
!
Items Not Received report
!
Items Pull reports
!
Non-Negotiable Items report
!
Pocket Listing report
!
Recognition Performance Statistics reports
!
RIR Document Distribution report
!
Second Source Match and Merge Performance Summary report
!
!
User Permission and Login Information report
Chapter 5: Reports
Adjustment Summary Report
This report shows the total number of adjustments per entry, broken down by adjustment reason
code. This lets you see how many adjustments operators are making and for what reason.
The following columns are displayed:
!
Entry: the number of the entry in which the adjustment was made
!
Block: the number of the block in which the adjustment was made
!
# Adjustments: number of adjustments made within this entry for this particular reason
!
Adj. Code: adjustment reason code, followed by the adjustment name
!
Account Number: the number of the customer account that was adjusted
Totals are given for each entry. A grand total for the cycle is also given.
Amount Suspect Summary Report
This Block Balancing report lists items with suspect amounts. There is one section for each cycle.
For each entry per cycle, the following information is given:
!
Total Items: total number of items processed
!
Total AK: total number of items presented at Amount Keying
!
Total Misread: number of misread MICR amounts
!
Misenc: number of misencoded amounts
!
Miskey: number of miskeyed amounts
!
Less Digits: number of items with too few digits
!
Less Dig Wrong: number of items with too few digits AND incorrect amounts
!
Key at CLC: number of amounts keyed at Codeline Completion
!
Key at AK: number of amounts keyed at Amount keying
!
Block BAL: number of amounts changed at Balancing
!
Items SUSP: number of items moved to the Suspense Pool
!
Showouts Adjust: number of showouts
!
Reclass Non-proof: number of items reclassified to non-proof
The last section of the report gives the total number of each type of adjustment that was made.
183
Chapter 5: Reports
ATM Reports
ImageMark Transaction Manager provides reports that support ATM Envelope Balancing.
Note: ATM reports are generated at end-of-cycle using a metascript command (not the Report
utility). For instructions on running this command, contact NCR Professional Services.
There is one report that operators use:
!
Unmatched ATM Envelope Report
And, there are several reports that operators do not view:
!
Processed Envelopes in Posting Sequence report
!
Processed Envelopes by Transaction Number Sequence report
!
ATM Adjustments File report
Unmatched ATM Envelope Report
Operators use this report to research ATM envelope deposits that were not received at the bank for
processing.
Information is grouped as follows:
!
By ATM Number: all unmatched envelopes from this ATM, with totals at the end
!
By Posting Date: all ATM groupings for this posting date, with grand totals at the end
For each item, the report shows:
!
Trans Date: date of the ATM transaction
!
Trans Time: time of the ATM transaction, in 24-hour format (HH:MM:SS)
!
Trans Num: identification number assigned to that transaction
!
Card Number: number of the bank card used to complete the transaction
!
Type: type of transaction. Can be any of the following:
!
DDA Deposit
!
SAV Deposit
!
Foreign Deposit
!
Payment
!
Account Number: customer account used for the transaction
!
Amount: amount of the deposit or payment
!
FIID: Financial Institution Identification (Account Owning Bank Number)
!
Ref: a bank-specific reference field
The following totals are given for each ATM:
!
Total # envelopes: number of unmatched envelopes deposited at this ATM
!
Total amount: dollar total of all unmatched envelopes deposited at this ATM
The following totals are given for each Posting Date:
!
184
Grand total # envelopes: number of unmatched envelopes deposited at all ATMs on this posting
date
Chapter 5: Reports
!
Grand total amount: dollar total of all unmatched envelopes deposited at all ATMs on this posting
date
Processed Envelopes in Posting Sequence Report
This report is created by Perl scripts which filter the Second Source data file. The Second Source
data file is produced by an end-of-cycle utility, to be used by the Second Source Browser.
The format of this report is determined by the Second Source file.
This report:
!
is sorted by ATM number, Entry number, Transaction date, and Transaction time
!
contains sections for each unique ATM number
Processed Envelopes by Transaction Number Sequence Report
This report is created by Perl scripts which filter the Second Source data file. The Second Source
data file is produced by an end-of-cycle utility, to be used by the Second Source Browser.
This report:
!
is sorted by ATM posting date, ATM number, and Transaction number
!
contains sections for each unique ATM posting date, and subsections for each unique ATM
number
ATM Adjustments File Report
This report is created by a Perl script which filters and reformats the Second Source Adjustment file.
The Second Source Adjustment file is produced by an end-of-cycle utility, to be used by the Second
Source Browser. Operators do not view this report.
This report:
!
is sorted by ATM number and Transaction number
!
contains sections for each unique ATM number
Audit Reports
The following Audit Reports are available:
!
ImageMark Audit report
!
Audit Exceptions report
!
Modified Entry report
!
Deposit Review Audit report
The ImageMark Audit report, Audit Exceptions report, and Deposit Review Audit report provide an
audit trail for the items that pass through the system. The ImageMark Audit report generates by
cycle on the DS, and the Audit Exception report generates by cycle on the DAP or DS.
The Modified Entry report identifies all items that have moved to a different cycle. The Modified Entry
report generates by cycle on the DAP or DS.
185
Chapter 5: Reports
ImageMark Audit Report
The ImageMark Audit report (also referred to as the full audit report) lists every item processed in
the system and indicates all changes made to the items and which operator made the changes. The
ImageMark Audit report must be run separately for each application instance.
The item information (the first six report fields) displays on one line, and the change information
related to the item (the remaining fields) displays beneath the item information.
Note: Because this report takes a while to print, you may want to run it using Windows Task
Scheduler. See Chapter 5 of ImageMark Transaction Manager 4.2 Parameter Generation:
ASCII Files (B004-0000-0610).
For each item, the report shows:
!
DRN: the document reference number
!
186
Res. Susp. = resolved suspense item
!
AMOUNT: the item final amount
!
STAT: the way the final amount was entered in the system:
!
M = read by the EPU MICR reader
!
R = read by RSS recognition software
!
C = keyed by Codeline Completion operator
!
K = keyed by Amount Keying operator
!
B = keyed by Balancing operator
!
E = keyed by Expert Balancing operator
!
F = resulted from a field manipulation directive
!
S = assigned by SMM
!
X = assigned or keyed at Reconciliation
!
D = resulted from a Deposit Review
!
I = EPA has imported an auto-select tracer from a 3890-captured entry
!
OPER: the operator’s number, if the final amount was entered through keying
!
1234567890: the first source of each of the 10 item fields (for example, 1=AMOUNT,
2=TRANCODE, 3=ACCOUNT, 4=TRANSIT, 5=SERIAL, and so on):
!
!
!
!
!
F = resulted from a field manipulation directive
!
!
M = read by the EPU MICR reader
!
!
S = assigned by SMM
!
X = assigned or keyed at reconciliation
Chapter 5: Reports
!
!
CODELINE: the item codeline read at the EPU
!
! = transport reject character
Note: The codeline may wrap to the next line.
For each item changed, beneath the item information, the report shows:
!
CHG: the number of the field that was changed (1—10) or the reason for the change:
!
11 = free item resolved
!
12 = suspense item added
!
13 = suspense item removed
!
14 = item reclassified as an image reject
!
15 = field marked as non-encode
!
16 = item reclassified
Note: The field reclassified is labelled with a corresponding reclassify code 41—50.
!
17 = adjustment created
!
18 = adjustment confirmed
!
19 = adjusment deleted
!
20 = physical adjustment created
!
21 = item has been reimaged
!
22 = front piggyback item has been reimaged
!
23 = rear piggyback item has been reimaged
!
24 = forced match item
!
25 = forced missing item
!
26 = transport image reject
!
27 = IDT operator reject
!
28 = deposit review required at DRA
!
29 = no deposit review required at host
!
30 = deposit review required at host
!
31 = reclassified to non-negotiable item
!
32 = audit change block split
!
33 = audit change batch split
!
34 = audit change batch moved
!
35 = audit change adjustment moved
!
36 = audit change keying error
!
37 = audit change misread
!
38 = audit change misencode
!
39 = audit change force adjustment deleted
187
Chapter 5: Reports
!
40 = codeline replaced
!
41—50 = field 1—10 reclassify
!
51 = IQA image suspect
!
52 = IQA image suspect confirm
!
53 = IQA image suspect cleared
!
54 = IQA image suspect reimaged
!
55 = OSD suspect cleared
!
56 = OSD suspect confirm
!
57 = OSD suspect reimaged
!
58 = OSD suspect
!
59 = physical item moved (this is the old and new logical pocket number)
!
60 = DDRI Unit of Work marked as damaged
!
61 = protected item prompt ignored by autorole
!
62 = amount field change not allowed (protected)
!
63 = field 2 to 10 change not allowed (protected)
!
64 = image change not allowed
!
65 = pocket change not allowed
!
66 = operator changed an item that had a “Protected” warning
!
67 = operator did not change an item that had a “Protected” warning
!
68 = physical item moved (this is the old and new tray number)
!
69 = physical item moved (this is the old tray sequence number)
!
!
71—80 = auto-select field change 1—10
!
81—90 = field 1—10 change not allowed
!
91 = supplemental amount changed
!
92 = hold removed
!
97 = block change
!
110 = suspect amount validated
Note: If the initial value is not modified, there is no change code.
!
!
188
DATA BEFORE: the field value before the change:
!
? = system reject character
!
If the change is an adjustment, this field displays the adjustment code.
!
If the final amount was initially entered at an operator activity, this field is blank.
DATA AFTER: the field value after the change:
!
!
If the change is an adjustment, this field displays the adjustment amount.
Chapter 5: Reports
!
!
OPER: one of the following codes.
Note: If the code is not an autorole, it is followed by the number of the operator who made the
change.
!
!
!
!
!
F = resulted from a field manipulation directive in CTA auto-activity
!
!
!
S = assigned by SMM
!
X = assigned or keyed at reconciliation
!
Audit Exceptions Report
The Audit Exceptions report provides the same type of information as the ImageMark Audit report,
but only for items that include a change made by an operator. For each item of this kind, the Audit
Exception report provides the following information:
!
Cycle: the number of the cycle the entry belongs to
!
Host Entry: the number of the host entry (CPCS) or host job (SuperMICR) the work belongs to
!
Entry: the number of the entry the work belongs to
!
!
Oper. No.: the number of the operator who made the change
!
Activity: the activity during which the operator made the change (Codeline Completion, Amount
Keying, Balancing, Entry Processing Autorole, or Expert Balancing)
!
Chg Code: the number of the field that was changed (1 to 10) or the reason for the change:
!
11 = free item resolved
!
12 = suspense item added
!
13 = suspense item removed
!
14 = IDT reject
!
15 = field marked as non-encode
!
16 = item reclassified
Note: the field reclassified is labelled with a corresponding reclassify code between 41-50
!
17 = adjustment created
!
18 = adjustment confirmed
!
19 = adjustment deleted
189
Chapter 5: Reports
!
!
!
20 = physical adjustment created
!
21 = item has been reimaged
!
22 = front piggyback item has been reimaged
!
23 = rear piggyback item has been reimaged
!
24 = forced match item
!
25 = forced missing item
!
26 = transport image reject
!
!
28 = deposit review required at DRA
!
29 = no deposit review required at host
!
30 = deposit review required at host
!
31 = reclassified to non-negotiable item
!
41 to 50 = field 1 to 10 reclassify
!
71 to 80 = field 1 to 10 changed to valid on auto-select tracer
!
81 to 89 = reserved for customer use
Before: the field value before the change
!
!
If the change is an adjustment, the field displays the adjustment code.
!
After: the field value after the change
!
!
If the change is an adjustment, this field displays the adjustment amount.
!
Example: The example on the next page shows a line for an EPA audit when an auto-select tracer
was seen with an invalid account field.
190
Chapter 5: Reports
Modified Entry Report – SuperMICR
The Modified Entry report identifies all entries that were moved to a cycle (posting date) different
from the one selected when the images were captured.
For a SuperMICR host, this report also identifies all entries whose Host Entry Number was changed
after it was captured by the EPU or EPA.
For each entry, the Modified Entry report – SuperMICR provides the following information:
!
Entry No.: the original entry number for the unit of work
!
Primary Job: the modified (if the entry was resent to the host)
!
ORIGINAL Cycle No.: the original cycle number for the entry
!
CYCLE Posting Date: the original posting date for the entry
!
HOST Cycle No.: the modified cycle number for the entry
!
CYCLE Posting Date: the modified posting date for the entry
!
Primary Job Identifier: the BIE identifier for the entry
Modified Entry Report – CPCS
The Modified Entry report identifies all entries that were moved to a cycle (posting date) different
from the one selected when the images were captured.
For a CPCS host, this report also identifies all entries whose Host Entry Number was changed after
it was captured by the EPU or EPA.
For each entry, the Modified Entry report – CPCS provides the following information:
!
Orig. Entry: the original entry number for the entry
!
Host Entry: the modified entry number (if the entry was resent to the host). If blank, then the
entry was not resent.
!
ORIGINAL Cycle No.: the original cycle number for the entry
!
CYCLE Posting Date: the original posting date for the entry
!
HOST Cycle No.: the modified cycle number for the entry. If the entry was not moved, this column
is blank.
!
CYCLE Posting Date: the modified posting date for the entry. If the entry was not moved, this
column is blank.
!
Balanced I-String: the BIE identifier for the entry
191
Chapter 5: Reports
Deposit Review Audit Report
This report lists every item in every ATM deposit against which either a hold was applied or an item
was identified as non-negotiable during a session. DRA starts a new page for each operator.
If DRA applies a hold, the report identifies the operator as operator 0 to show that it was DRA and
not a Deposit Review operator that applied the hold.
The report has two sections:
Deposit Review Hold Audit section:
This three-part section provides information about each item against which a hold was applied.
!
!
!
The Hold Information part includes:
!
DRN: the document reference number for the item
!
R/T: the trancode for the item
!
Account: the account number
!
Amount: the amount of each hold
!
RefID: your bank may use this as the FIID (if your bank does not use an FIID, ignore this
column)
!
Reason Code: the reason code assigned by the operator
!
OperID: identifies the operator who made the change
!
Comments: information entered by operator when reviewing item
The Deposit Information part includes:
!
DRN: the document reference number for the deposit
!
R/T: the trancode for the deposit
!
Account: the account number of the deposit
!
Amount: the amount of the deposit
The Totals part includes:
!
Total Hold Amount: the total amount of all holds listed in the report
!
Total # Holds: the total number of holds listed in the report
Deposit Review Non-Negotiable Items Audit section:
This three-part section provides information about each non-negotiable item.
!
192
The Non-Negotiable Item part includes:
!
DRN: document ref. no. for each non-negotiable item in deposit
!
R/T: trancode for each non-negotiable deposit item
!
Account: account number of the non-negotiable item
!
RefID: your bank may use this as the FIID (if your bank does not use an FIID, ignore this
column)
!
Amount: amount of each non-negotiable deposit item
!
Reason Code: identifies the reason that the item was non-negotiable
!
OperID: identifies the operator who made the change
Chapter 5: Reports
!
Comments: information entered by operator when reviewing item
!
For the Deposit Information part, see description of headings above.
!
The Totals part includes:
!
Total Non-Negotiable Amount: total amount of all non-negotiable items listed in the report
!
Total # Non-Negotiable Items: total number of non-negotiable items listed in the report
Automatic Codeline Completion Statistics Report
This report gives statistics for items that had fields automatically repaired. It includes the following
information:
1This
!
Bank Name: name of the bank at which ACC took place
!
Cycle: host cycle number
!
Date: date this report was generated
!
Posting Date: date this report was uploaded to the server
!
ACC Assigned (SWOCR F1 – F10): The number of fields that Automatic Codeline Completion
(ACC) used Software Optical Character Recognition (SWOCR) to repair, by field
!
Operator Modified ACC Field (SWOCR F1 – F10): Number of fields ACC repaired using
SWOCR, since modified by an operator
!
ACC Skipped (SWOCR F1 – F10): The number of fields that CLC Corrected that were not
assigned by ACC or RSSR
!
ACC Assigned (CAR/LAR F1): The number of fields that RSSR repaired using CAR/LAR.
!
Operator Modified ACC Field (CAR/LAR F1): Number of fields RSSR repaired using CAR/LAR
that have since been modified by an operator
!
ACC Skipped (CAR/LAR F1): The number of fields CLC corrected that were not assigned by
ACC or RSSR1
will allow for an understanding of the labour displacement that ACC provides.
193
Chapter 5: Reports
BIE, EIE, and SIE Deadline Reports
The BIE, EIE, and SIE Deadline reports provide data that will assist in identifying problems in float
so they can be investigated within the system.
BIE Deadline Report
The BIE Deadline report shows the transit dollar amounts for captured items and the time that data
was transmitted to the host by BIE and SIE.
Notes: !
There is a line for each Sub-pass Item Export (SIE) entry even if the tray set was stacked
after another entry’s tray set into a single SIE.
!
For 3890 Capture, the report does not include SIE information, since no sub-pass item
I-strings are transmitted by ImageMark. All rehandles are done on the 3890. Documents
that go to the reject pocket are re-run on the ESU.
For each data transmission, the reports list the following information:
!
Cycle: the cycle number the data belongs in
!
HOST ENTRY (CPCS) or JOB NUMBER (SuperMICR): the entry number for CPCS or the job
number for SuperMICR
!
EPU START TIME: the time that the EPU started processing the entry (CPCS) or job
(SuperMICR)
!
PIE, BIE, SIE TIME: the time that the string was transmitted to the host by PIE, BIE, or SIE
Note: In the case of 3890 Capture, no sub-pass I-strings are transmitted to the host by SIE, so SIE
TIME is left blank.
!
EPU TO EXPORT DIFFERENCE: the elapsed time from when the EPU began processing the
string until it was sent to the host
!
TRANSIT AMOUNT: the dollar amount of transit items in the string (in thousands of dollars)
!
TOTAL # ITEMS: the number of items in the string
!
IDENTIFIER: the BIE data identifier. The first four digits are the entry number, and the next five
groupings are the pocket pass history. The first pocket pass history is for the EPU. The remaining
passes are for the ESU.
Note: In the case of 3890 Capture, BIE is sending a 00-M string, which is reflected in the name of
the string
194
Chapter 5: Reports
EIE Deadline Report
The EIE Deadline report shows the transit dollar amounts for captured items and the time that data
was transmitted to the host by EIE.
Note: There is a line for each Encoded Item Export (EIE) identifying the first item in the run.
For each data transmission, the reports lists the following information:
!
CYCLE: the cycle number the data belongs in
!
HOST ENTRY (CPCS) or PRIMARY/SECONDARY JOB (SuperMICR): the entry number for
CPCS or the job number for SuperMICR
!
EIE TIME: the time that EIE completed transmission of the string to the host
!
TRANSIT AMOUNT: the sum of the transit amount (in thousands of dollars)
!
TOTAL # ITEMS: the sum of all stacked tray sets in a run
!
IDENTIFIER: The EIE data identifier. The first four digits are the entry number followed by the
pass number, which is 1. The four groupings that follow the pass number are for pocket history,
but are not used for the EIE data identifier.
Note: The EIE identifier references the first entry number in a run.
SIE Deadline Report
The SIE Deadline report shows the transit dollar amounts for captured items and the time that data
was transmitted to the host by SIE.
Notes: !
!
There is a line for each Sub-pass Item Export (SIE) identifying the first item in the run.
No SIE Deadline Report is generated for 3890 Capture.
For each data transmission, the reports list the following information:
!
!
HOST ENTRY (CPCS) or JOB NUMBER (SuperMICR): the entry number for CPCS or the job
number for SuperMICR
!
SIE TIME: the time that the string was transmitted to the host by the SIE
!
TRANSIT AMOUNT: the sum of the transit amount (in thousands of dollars)
!
TOTAL # ITEMS: the sum of all stacked tray sets in a run
!
IDENTIFIER: the SIE data identifier The first four digits are the entry number, and the next five
groupings are the pocket pass history. The first pocket pass history is for the EPU. The remaining
passes are for the ESU (currently only one pass at the ESU is supported)
Note: The SIE identifier references the first entry number in a run.
195
Chapter 5: Reports
BTM Reports
ImageMark Transaction Manager provides reports that support BTM processing.
Note: BTM reports are generated at the end of the cycle using a metascript command (not the
Report utility). For instructions on running this command, contact NCR Professional Services.
There are several BTM end-of-cycle reports:
!
BTM Batches Not Received report
!
Next Day BTM Batches Received report
!
Items Missing from BTM Batches Received Today report
!
Items Received without BTM Batches Today report
!
BTM Batches Aged Out report
!
BTM Branch Rankings report
!
BTM Teller Rankings report
!
Incorrectly Matched Items report
!
Teller Keying Errors Detail report
BTM Batches Not Received Report
This report lists batches of BTM work that were processed at the branch, for which there is a second
source record, but the credit (BTM batch ticket) has not been matched.
The following information for each BTM batch is shown in this report:
!
Teller: the ID number for the teller who processed the BTM batch
!
Branch: the number of the branch where the BTM batch originated
!
BTM Batch: the BTM batch that the item belongs to
!
BTM Posting Date: the date the BTM batch was processed at the branch
!
BTM Amount: the value of the amount field
!
No. of Debits: the number of debits in the BTM batch represented by the credit
!
No. of Debits Unmatched: the number of unmatched debits in the BTM batch represented by
the credit
Next Day BTM Batches Received Report
This report lists batches of BTM work for which the credit (BTM batch ticket) has been matched to
the second source record. Only the current day’s work is included in this report.
The following information for each BTM batch is shown in this report:
196
!
!
!
!
!
CPCS Posting Date: the date the cycle was created that contains the BTM batch
!
Chapter 5: Reports
Items Missing from BTM Batches Received Today Report
This report lists debit items that are missing from batches of BTM work for which the credit (BTM
batch ticket) has been matched. This list may include items that were matched on previous days
and purged by the delete cycle process.
The following information for each missing debit item is shown in this report:
!
!
!
!
!
!
BTM Item Number: the number assigned to the missing item during BTM processing
!
Customer ID Number: the customer account number into which the missing item was deposited
This report provides information on BTM batches for which there is an unmatched credit and one
or more matched debits.
For each debit item only, this report shows the following information:
!
!
!
!
!
!
!
BTM Item Number: the number assigned to the aged out item during BTM processing
!
Customer ID Number: the customer account number into which the aged out item was deposited
BTM Batches Aged Out Report
This report provides information on BTM batches for which unmatched second source records have
been aged out.
For each aged out item, this report shows the following information:
!
!
!
!
!
!
BTM Item Number: the number assigned to the aged out item during BTM processing
!
Customer ID Number: the customer account number into which the aged out item was deposited
197
Chapter 5: Reports
BTM Branch Rankings Report
This report ranks the bank branches according to exceptions found in their work (teller errors and
unmatched items).
For each branch, this report shows the following information:
!
Final Ranking: the branch’s position relative to all other branches in terms of total errors
produced (an averaging formula is used)
!
Branch Number: the number of the branch where the BTM batch originated
!
Number of Items Not Received: the number of unmatched debit items
!
Number of Batches Not Received: the number of unmatched BTM batch tickets
!
Number of Teller Keying Errors: the number of adjustments that were made to the BTM amount
for matched items
This is how the totals are calculated:
For example, if branch XYZ is rank 10 of 100 for batches not received, rank 50 of 100 for items not
received, and rank 80 of 100 for teller keying errors, then the ranking sum is 10 + 50 + 80 = 140.
This value is only used for later sorting.
The final ranking is generated as the report is generated, starting at 1. Note that if more than one
branch has the same summed ranking, then they will have the same value of final ranking.
For example, if there are three branches with summed ranks of 4, 7, and 9, they will be ranked 1,
2, 3 in the report.
Teller Ranking Report
This report ranks the tellers at each bank branch according to problems found in their work (teller
errors and unmatched items).
For each branch (printed on a separate page), this report shows the following information:
198
!
Teller Number: the ID number for the teller who processed the BTM batch
!
Final Ranking Within Branch: the teller’s position relative to all other tellers in the branch in terms
of total errors produced (an averaging formula is used)
!
Final Ranking Across All Branches: the teller’s position relative to all other tellers in all branches
in terms of total errors produced (an averaging formula is used)
!
Number of Items Not Received: the number of unmatched debit items in today’s work for this
teller
!
Number of Batches Not Received: the number of BTM batch tickets not matched in today’s work
for this teller
!
Number of Teller Keying Errors: the number of adjustments that were made to the BTM amount
for matched items in today’s work for this teller
!
Number of Force Matched Items per Thousand Items: the number of items per thousand in
today’s work for this teller that were force matched
Chapter 5: Reports
Incorrectly Matched Items Report
This report provides information on BTM batches containing incorrectly matched items.
Balancers can flag incorrectly matched items, and the system can automatically unmatch them, as
long as the match was made within the same entry. For items incorrectly matched to second source
records in a different entry, reconcilers must use this report to identify them.
For each branch, this report shows the following information:
!
!
!
!
!
!
BTM Amount: the value of the amount field for the item
!
DRN: the Document Reference Number of the incorrectly match item
!
Mismatch Type: tells if the mismatch was automatic or manual.
!
Operator ID: if the mismatch was manual, the operator ID number is listed.
!
BTM Item Number: the number assigned to the item during BTM processing
!
Customer ID Number: the customer account number into which the item was deposited
Teller Keying Errors Detail Report
This report provides information on teller keying errors in today’s work.
For each item, this report shows the following information:
!
Teller: the ID number for the teller who processed the item
!
Branch: the number of the branch where the item originated
!
!
BTM Posting Date: the date the item was processed at the branch
!
CPCS Posting Date: the date the cycle was created that contains the item
!
BTM Amount: the value of the amount field, from the second source data file
!
Posted Amount: the amount that was entered by the teller
!
BTM Item Number: the number assigned to the item during BTM processing
!
Customer ID Number: the customer account number into which the item was deposited
Note: Items with a very small difference between the BTM amount and the posted amount may be
left out of this report (determined by parameters).
199
Chapter 5: Reports
Bundle List Report
You can use the Bundle List report as an alternative to the Pocket Listing report.
The Bundle List report lists items that were originally processed on a 3890 reader/sorter, then
balanced and physically repaired on ImageMark Transaction Manager. These items must be reprimed on the 3890.
This report is generated for each ESU output-processed tray set containing repaired reject items.
You can use this report to prepare items for re-priming at the 3890, based on the position of Cutslips
(Universal Batch Headers) in the ESU output pocket. Create a General Ledger ticket from the totals
in the report and re-block the work into new entries for re-priming on the 3890.
This report also helps to identify if any items have gone missing between the ESU and the 3890.
To save space, this report is formatted with three groups of three columns of item data (DRN, BSB,
AMOUNT) spread horizontally across the page. The system fills the first group of three columns to
the bottom of the page before starting to fill the second group of columns.
The report lists the following information:
200
!
Cycle Date: cycle process date
!
Pocket: destination pocket of the item on the 3890
!
Station ID: identification number for the 3890 that processed the item
!
Run: date and time when the 3890 run ended
!
Receiving Bank: Bank that the item was received from
!
DRN: the Document Reference Number of the item
!
R/T: the Routing/Transit number of the item
!
AMOUNT: the amount of the item
Chapter 5: Reports
Daily Corrections Export Reports
The Daily Corrections Export reports include the following reports:
!
End of Day Daily Corrections Export report
!
Entry Level Daily Corrections report
End of Day Daily Corrections Export Report
This is a new End of Cycle report that combines the files generated by the EIR daily corrections
report into one file, sorted by the advice reference number.
Output from this report is sent to this file:
dailyex.cycle_key.cycle_process_date
(where cycle_process_date is in YYYYMMDD format)
in this location:
/opt/siips/archive/bac (%SIIPS_BASE%/archive/bac in ImageMark 4.x)
The first line in the combined file is a header record consisting of the following information:
Column Name
Description
Justification/Fill
Length
(total
chars)
Position
From: To:
Header
Indicates that this record is the
header.
Fixed value of HDR.
Left = 'HDR'
3
1
3
Site Identifier
ImageMark Site where the file
originated. This will likely be a
parameter either in
BANKSITE or
APP_TYPE_PSETS.
Left =
'LA00004580'
10
4
13
Date
(DB) CYCLE:process_date in
format MMDDYYYY
Left = '07252005'
8
14
21
The last line in the combined file is a trailer record consisting of the following information:
Column Name
Description
Justification/Fill
Length
(total
chars)
Position
From: To:
Trailer
Fixed value of 'TRL'
Left = 'TRL'
3
1
3
Record Count
Count of the number of data
records in the file. Does not
include the header or trailer
records.
Right = '00014'
5
4
13
201
Chapter 5: Reports
Entry Level Daily Corrections Report
This is a new End of Cycle report that lets you create a master report of all information in all the
Entry Level reports, to use for back-end processing.
Output from this report is sent to this file:
dailyexeir.cycle_key.entry_key
in this location:
%SIIPS_BASE%/archive/bac
Note: Refer to the PCS extension package release bulletin for instructions on configuring and
activating this report.
The output file lists the following information as a record for each adjustment. There is one record
per line, each of which contains all of the following information:
202
Column Name
Source
(DB) = Database
(PA) = Parameter
Length
(total
chars)
Position
From:
To:
Bank ID
(DB) ADVICE:bank_id
Left, space filled
i.e. '8888
'
10
1
10
Transaction Office
(DB) ADVICE:branch_num
Left, space filled
i.e. '1
'
10
11
20
Account Number
(DB) ADVICE:dep_acct_no
Left, space filled
i.e. '2222
30
21
50
Justification/Fill
'
Sub-Account
Number
(DB) ADVICE:sub_acct_no
Left, space filled
i.e. '
'
10
51
60
Correction ID
(DB)
ADVICE:adj_reason_code
Right, zero filled
i.e. '001'
3
61
63
Entry Amount 1
(DB) ADVICE:dep_slip_amt
Right, zero filled
i.e. '000000000654'
12
64
75
Entry Amount 2
Right, zero filled
i.e. '000000000654'
12
76
87
Entry Amount 3
Right, zero filled
i.e. '000000000654'
12
88
99
Adjustment
Amount
(DB) ADVICE:corr_amt
Right, zero filled
i.e. '000000000044'
12
100
111
Credit OR Debit
'C' or 'D' using (DB)
ADVICE:corr_class
Full. i.e. 'C'
1
112
112
Direct Fees
Not used - zero fill
Full =
'000000000000'
12
113
124
Analysis Fees
Full =
'000000000000'
12
125
136
Chapter 5: Reports
Column Name
Source
(DB) = Database
(PA) = Parameter
Length
(total
chars)
Position
From:
To:
Wave Fees
Full =
'000000000000'
12
137
148
In or Out
Not used - zero fil
Full = ' '
1
149
149
Application Code
(DB)
ADVICE:application_code
Left, space filled.
i.e. 'DDA'
3
150
152
Teller ID
(DB) ADVICE:teller_num.
Left, space filled
i.e. '1
'
10
153
162
Adjustment String
(DB) PRINCIPAL:login
(obtained using
ADVICE:oper_number)(DB) ADVICE:advice_ref
Left, space filled
i.e. '123-900001
'
55
163
217
Adjustment
Number
(DB) ADVICE:advice_ref
Full = '900001'
16
218
233
Proof Operator ID
(DB) PRINCIPAL:login
(obtained using
ADVICE:oper_number)
Left, space filled
i.e. '1
'
10
234
243
Transaction
Number
(DB)
ADVICE:transaction_num
Left, space filled
i.e. '1
'
16
244
259
Maker
Payor name of the check in
error.
Not used - blank fill
Full = '
'
40
260
299
Bank
R/T from check in error
Full = '
'
40
300
339
MICR Code
Left = '1 '
3
340
342
Comments
(DB)
ADVICE:advice_comment
Left, space filled
255
343
597
Account Name
Left = '
'
40
598
637
Address Line 1
Left = '
'
40
638
677
Address Line 2
Left = '
'
40
678
717
Address Line 3
Left = '
'
40
718
757
Address Line 4
Left = '
'
40
758
797
Address Line 5
Left = '
'
40
798
837
Office ID
(DB) ADVICE:proc_date
Left = '
10
838
847
Created Date
Amount from item before the
item in error.
Full = '12/22/1998'
10
848
857
Justification/Fill
'
203
Chapter 5: Reports
204
Column Name
Source
(DB) = Database
(PA) = Parameter
Length
(total
chars)
Position
From:
To:
Listed Between B
Full =
'000000000000'
12
858
869
Listed Between A
Full =
'000000000000'
12
870
881
Alternate Name
Left = '
'
40
882
921
Alternate Address
Line 1
Left = '
'
40
922
961
Alternate Address
Line 2
Left = '
'
40
962
1001
Alternate Address
Line 3
Left = '
'
40
1002
1041
Alternate Address
Line 4
Left = '
'
40
1042
1081
Alternate Address
Line 5
Left = '
'
40
1082
1121
Reason
Description
(PA) IDT_ADJUSTMENT_
CODES:AdjustmentText
look up using (DB) ADVICE
:adj_reason_code
Left, space filled
i.e. 'Check was
Listed for Wrong
Amount
'
40
1122
1161
Reason Text
Format
Left = '
255
1162
1416
Charge to Account
Number
(DB) AP_DDR:field3
Left, space filled
i.e. '123456
'
30
1417
1446
Serial Number
(DB) AP_DDR:field5
Left, space filled
i.e. '00118 '
10
1447
1456
Breakdown
Left = '
30
1457
1486
Hundreds
Left =
'000000000000000
0000'
25
1487
1511
Fifties
"
Left = '0000000'
25
1512
1536
Twenties
"
Left = '00000000'
25
1537
1561
Tens
"
Left = '00000000'
25
1562
1586
Fives
"
Left = '00000000'
25
1587
1611
Twos
"
Left = '00000000'
25
1612
1636
Ones
"
Left = '000000000'
25
1637
1661
Justification/Fill
'
'
Chapter 5: Reports
Column Name
Source
(DB) = Database
(PA) = Parameter
Justification/Fill
Length
(total
chars)
Position
From:
To:
Coins
"
Left = '000000000'
25
1662
1681
Total Breakdown
"
Left = '000000000'
25
1687
1711
TOTALS:
205
Chapter 5: Reports
EPU Exception Item Reports
The EPU Exception Item reports include the following reports:
!
!
Merchant Summary report
!
Research Items – Exception Items in Kill Pocket report
These reports generate by cycle on the DAP database.
Unresolved Suspense Items Report
The Unresolved Suspense Items report shows all items that were left in the Suspense Pool after
Balancing.
For each item, this report shows:
!
Cycle: the number of the cycle the work belongs to
!
!
AMOUNT: the item amount
!
CR/DB/NP: a code indicating whether the item was a credit (CR), a debit (DB), or a non-proof
(NP) item
!
ENTRY: the number of the entry to which this item belongs
!
POCKET: the number of the kill pocket in which the item was placed at the EPU
!
3890 PKT: the 3890 equivalent of the of the ImageMark EPU pocket
!
the item’s codeline: a dot-separated pseudo codeline, generated by EPA (! = transport reject
character)
The TOTALS line of this report shows the total number of credit, debit and non-proof items that were
processed, and the sum of these three numbers.
Note: Any suspense items that you export to ETF will appear in the Unresolved Suspense Items
report.
206
Chapter 5: Reports
Merchant Summary Report
This report shows item information for each item that has had at least one side re-imaged or marked
as an IQ Reject.
The report lists the following information for each item:
!
Bank Name: name of the bank that will be debited for this item
!
Date: date this report was generated (dd/mm/yyyy)
!
Distribution Name: the type of item, as defined by the DOCUMENT_DISTS parameters
!
DRN: Document Reference Number of the item
!
Merchant: name of the merchant who deposited the item
!
Amount: the amount of this deposited item, as defined by the RPT_FIELD_DEFNS parameters
!
Collecting Bank: name of the bank of first deposit
!
Total Fee: The total of the per-item fees that the bank will receive from the merchant for handling
these items (defined by the MERCHSUM_RPT_PARMS parameters)
Note: Only items with a defined distribution are shown on the report (controlled by the
MERCHSUM_RPT_PARMS parameters).
Research Items – Exception Items in Kill Pocket Report
The Research Items – Exception Items in Kill Pocket report shows all items that were flagged as
research items at Balancing and that are physically located in EPU kill pocket trays.
For each item, this report shows:
!
Cycle: the number of the cycle the work belongs to
!
!
!
(NP) item
!
ENTRY: the number of the entry to which this item belongs
!
POCKET: the number of the pocket in which the kill document was placed
!
the item’s codeline (! = transport reject character)
207
Chapter 5: Reports
Forced Adjustment Report
This report is used by the research department to help make day 2 corrections. For each entry, it
lists all units of work that were forced into balance, and shows what information was changed to
make the work balance.
This is a two-part report. The first part shows Online Block Balancing activity, and the second part
shows Offline Block Balancing activity.
These columns appear in both parts of the report and list the auto adjustments made to meet
deadlines:
!
DRN: document reference number of the force-balanced item
!
Block: block number of the force-balanced item
!
Batch: batch number of the force-balanced item
!
SERIAL: the force-balanced item’s serial number
!
BANK: the force-balanced item’s transit number
!
ACCOUNT: the force-balanced item’s account number
!
TRNCOD: the force-balanced item’s transaction code
!
AMOUNT: the force-balanced item’s amount
These columns appear in the second part of the report only and list the changes made in Offline
Block Balancing to reflect the real problem:
!
208
CHG: change code representing the modification made to the batch, block, or item:
!
32 = block split
!
33 = batch split
!
34 = batch moved
!
Data Before: codeline of the item as read by the system, before it was modified
!
Data After: the portion of the codeline that was modified by the operator
!
Oper: operator number for the operator who made the change
!
Field1 to Field5: specific fields from the codeline (defined by the RPT_FIELD_DEFNS keyword)
Chapter 5: Reports
Image Quality Reports
The Image Quality End-of-Cycle reports include the following reports:
!
Image Quality Failure Detail report
!
Image Quality Test Performance Summary report
!
Image Quality Transport Performance Summary report
Image Quality Failure Detail Report
This report shows item information for each item that has had at least one side reimaged or marked
as an IQ Reject.
The report lists the following information for each item:
!
Bank Name: name of the bank at which the testing took place
!
!
!
!
DRN: Document Reference Number of the reimaged or rejected item
!
Image Face: side of the image that failed (front or rear)
!
PSet: parameter set the item was run against
!
Transport Number: ID number of the capture transport
!
R/T: routing/transit number of the item
!
Account: account number of the item
!
Codeline: codeline of the reimaged or rejected item
!
Vendor: test vendor
!
Type: test type
!
Test Num: test number
!
Face: front or back of item
!
Binary/Gray: image type
!
Test ID: ID number of the IQ test that failed
!
Score: the score the test received. when the test type is HUMAN, this column also lists the
message associated with the measurement. for a human test, the measurement is the IQ reason
code (explaining why the item was reimaged or marked as a reject)
!
Threshold 1: lower limit for the test (e.g. minimum, left)
!
Threshold 2: upper limit for the test (e.g. maximum, right)
!
Result: Image Quality Test results (pass or fail) for the original scanned image (not the good
image obtained at Reimage)
Note: Not all fields may be displayed at your site (this is controlled by parameters).
209
Chapter 5: Reports
Image Quality Test Performance Summary Report
The Image Quality Test Performance Summary report details the results of the tests performed on
the images.
The report is grouped by Block Type within the Pset. Each new Pset is started on a new page. All
fields have grand totals given for the cycle.
This report lists the following information for each IQ Test that was executed (either by the capture
transport (EPU, Passport or 3rd party) or by IQA):
!
!
!
!
!
Vendor: test vendor
!
Type: test type
!
Test Num: test number
!
Test Description: description of the test performed
!
Face: front or back of item
!
Binary/Gray: image type
!
#Passed Images: number of images with a true test result
!
#Passed Images Rejected/Reimaged: number of images with a true test result that ended up
being reimaged or marked as IQ Rejects
!
#Failed Images: number of images with a false test result
!
#Failed Images Rejected/Reimaged: number of images with a false test result that ended up
being reimaged or marked as IQ Rejects
Image Quality Transport Performance Summary Report
This report shows, for every transport which captured items in that cycle, how many items were
captured and, of those, how many items were reviewed as IQ Suspects, reimaged, or marked as
IQ Rejects. The data is grouped by block type within the pset.
Each new Pset is started on a new page. All fields have grand totals given for the cycle.
Note: Printing this report is not recommended due to the high number of devices included (too
many pages).
210
!
!
!
!
!
Station Number: ID number of the transport that processed these items
!
# Captured Items: total number of items captured
!
# Reviewed: total number of items reviewed
Chapter 5: Reports
!
# Reimaged/Rejected: total number of items that were reimaged or marked as IQ Rejects
!
% Reviewed: percentage of total number of items captured that were reviewed
!
% Reimaged/Rejected: percentage of total number of items captured that were reimaged or
marked as IQ Rejects
Items Aged Out Report
The Items Aged Out report provides information on which unmatched second source records have
been aged out.
For each second source file, this report shows the following information:
!
Source: source bank or batch of the second source file
!
Posting Date: the item’s posting date
!
Host Sequence: the item’s sequence number
!
Type: the type of work (2 for Repass Capture second source files)
!
EX: not used
!
SERIAL: the item’s serial number
!
TRANSIT: the item’s transit number
!
ACCOUNT: the item’s account number
!
AMOUNT: the item’s amount
!
GROUP: the ATM number for each second source file listed in the report
Items Not Received Report
The Items Not Received report provides information on which second source records have not been
matched to physical items. The date on this report reflects the current system date when the report
is printed.
The Items Not Received report shows the following information:
!
Source: source bank or batch of the second source file
!
Posting Date: the item’s posting date
!
Host Sequence: the item’s sequence number
!
Type: the type of work (2 for Repass Capture second source files)
!
EX: information from Second Source files or teller files (field 6 of SS_DRR table)
!
SERIAL: the item’s serial number
!
BANK: the item’s bank number
!
ACCOUNT: the item’s account number
!
TRNCODE: the item’s trancode
!
AMOUNT: the item’s amount
!
GROUP: the ATM number for each second source file listed in the report
211
Chapter 5: Reports
Items Pull Reports
These reports get printed at the end of the day, either by the supervisor as part of the Report utility
or using Windows Task Scheduler.
Items Pull Report
The codeline fields displayed in this report are determined by the parameter keyword
RPT_FIELD_DEFNS.
Other information included in this report (such as title and which distributions are included) also
depends on parameters. For more information, see “Customizing Items Pull Reports” in ImageMark
Transaction Manager Parameter Generation: Appliction Generator.
The following information is included in this report by default:
!
!
EX: information from Second Source files or teller files (field 6 of SS_DRR table)
!
Codeline fields 1 to 5 (SERIAL, TRANSIT, ACCOUNT, TRNCOD, AMOUNT)
!
Tray Number: the number of the tray the item belongs to
!
Tray Sequence: the location of the item in the tray (e.g., 4.00 means the item is the fourth item
in the tray)
The last page of the report includes subtotals (by usercode) and a Grand Total line at the bottom.
The totals given are:
!
Total Name: lists all the banks in the report
!
Total Items: total number of checks
!
Total Amount: total amount for all checks
!
Total DRCnt: total number of proof debits
!
Total Debits: totals for proof debits
!
Total CRCnt: total number of proof credits
!
Total Credits: totals for proof credits
!
Total NP Debits: totals for non-proof debits
!
Total NP Credits: totals for non-proof credits
A sample report follows, but the content of the report is determined by parameters.
212
Chapter 5: Reports
Non-Negotiable Items Report
Use this report to match each non-negotiable item with its corresponding advice notice. There are
three parts:
!
!
!
!
!
Advice Notice that includes:
!
Branch #: the number that identifies the bank branch where the customer making the deposit
has their account
!
Advice Reference #: the reference number that appears on the advice notice sent to the
customer
Non-Negotiable Item that includes:
!
DRN: the document reference number for each item in a deposit that is identified as nonnegotiable
!
Amount: the amount of each item that is non-negotiable
!
Reason Code: the reason code that identifies the reason that the item was identified as nonnegotiable
!
Reason: the description of the reason for making the item non-negotiable
Deposit Information that includes:
!
DRN: the document reference number of the deposit
!
R/T: the trancode
!
Account: the account number of the deposit
Location Information that includes:
!
Tray #: the number of the final tray that the non-negotiable item was in
!
Entry #: the number of the entry that the work belongs to
!
Host Entry: the number of the host entry (CPCS) that the work belongs to
!
EPU Kill:
!
Yes indicates the item was identified as non-negotiable and sorted to a kill pocket at EPU
!
No indicates the item was not identified as non-negotiable at EPU. Instead the item was
identified later as non-negotiable and sorted to a kill pocket at ESU.
Totals that include:
!
Total Amount: total amount of all non-negotiable items listed in the report
!
Total # Items: total number of non-negotiable items listed in the report
Pocket Listing Report
The Pocket Listing report lists items that were originally processed on a 3890 reader/sorter, then
balanced and physically repaired on ImageMark Transaction Manager. These items must be reprimed on the 3890.
This report is generated for each ESU output-processed tray set containing repaired reject items.
The report identifies all entries stacked as part of the output tray set.
You can use the page totals to prepare balancing General Ledger credits and/or batch headers for
the ESU’s transit kill pocket, and for the ESU’s on-us pockets if necessary. You can then re-block
work into new entries for re-priming on the 3890.
213
Chapter 5: Reports
This report also helps to identify if any items have gone missing between the ESU and the 3890.
Notes: !
For the transit pocket, the pocket includes only transit items, so the on-us DB and onus CR totals will be zero.
!
For on-us pockets, the pockets include only on-us items, so the transit total will be zero.
!
To save space, this report is formatted with three groups of three columns of item data
(DRN, R/T, AMOUNT) spread horizontally across the page. The system fills the first
group of three columns to the bottom of the page before starting to fill the second group
of columns.
!
Tracer group and cutslip records are not included in the report.
!
The item type is identified as on-us or transit by the following fields: ESU Pocket,
Endpoint ID, and the type code following the Amount columns.
!
MultiBankName: the bank name
!
!
Cycle Date: cycle process date
!
ESU Pocket: destination pocket of the item on the ESU
!
Endpoint ID: identification number for the ESU pocket that the item was intended for
!
ESU Station ID: identification number for the ESU that processed the item
!
ESU Run: date and time when the ESU run ended
!
Routing Information: can be used to provide routing instructions to the supervisor or operator
who has finished processing the 3890 Reject tray through the ESU. Controlled by the
POCKET_RPT_PARMS parameters. For example, the parameters can be set as follows:
!
RoutingInfo1 = “3890 Transit Rejects”
!
RoutingInfo2 = “3890 Re-Prime Required”
!
RoutingInfo3 = “Prepare G/L Credits from Subtotals”
!
RoutingInfo4 = “Prepare Batch Header from Grand Total”
!
From Entry(s): list of entry numbers for trays stacked into this run on the ESU
!
DRN: the Document Reference Number of the item
!
R/T: the Routing/Transit number of the item (this is an example column heading; column heading
can be changed using FieldName parameter (RPT_FIELD_DEFNS keyword))
!
AMOUNT: the amount of the item (this is an example; column name can be changed using
FieldName parameter (RPT_FIELD_DEFNS keyword))
!
%T (type of item, follows amount): CR (credit), DR (debit), or NP (non-proof)
At the end of each page, a Subtotal line gives the count and sum of amounts from transit, on-us
debit, and on-us credit items printed on that page.
At the end of the report, a Grand Total line gives the count and grand total sum of amounts from
transit, on-us debit, and on-us credit items for the entire report.
214
Chapter 5: Reports
Recognition Performance Statistics
The Recognition Performance Statistics reports provide detailed information about the performance
of each Recognition Subsystem at your site. For each RSS, you can generate the following reports:
!
RSS Performance Summary report
!
CAR Performance Summary report
!
CAV Performance Summary report
!
RSS Reclassification report
These reports can be very useful for tuning recognition performance.
You can select to generate these reports for a specific workgroup, for a specific cycle, or on a specific
database; however, for the best results, generate these reports by workgroup.
RSS Performance Summary Report
The RSS Performance Summary report summarizes how well each RSS performed with each type
of item that it handled.
For each DS (or each Recognition Unit, if there is more than one on a DS), this report provides the
following information:
!
Recognition Station: the Recognition Station to which the statistics apply
!
Total Proof Items: the total number of proof items in all units of work processed by this workgroup
!
Items Shuffled: the percentage of proof items that were supposed to be processed by the RSS
but were made to bypass it
!
Items Reco Processed: the percentage of proof items that were sent to the RSS for processing.
A value greater than 90% indicates optimal recognition performance.
!
AMOUNT RSS Assigned: the percentage of proof items whose amounts were assigned by the
RSS (that is, not rejects). A low number may indicate a problem with Recognition parameter
tuning, document preparation, or the EPU image lift camera.
!
AMOUNT Force Keyed: the percentage of proof items whose amounts were forced to be
manually keyed because of RSS parameter settings
!
AMOUNT RSS Only: the percentage of proof items whose amounts were determined solely by
the Recognition software and were not keyed by Amount Keying, Codeline Completion, or
Balancing. This is the most stringent measure of Recognition software performance.
!
AMOUNT EPU Only: the percentage of proof items whose amounts were determined solely by
the EPU (for example, pre-encoded amounts)
!
AMOUNT KLD: the percentage of proof items whose amounts were not manually keyed at
Codeline Completion or Amount Keying. Does not include RSSV statistics.
215
Chapter 5: Reports
CAR Performance Summary Report
The CAR Performance Summary report summarizes how each recognition distribution performed
on each Recognition Unit. If more than one field is read for a particular distribution, separate statistics
are provided for each field.
For each distribution, this report provides the following information:
!
RSS Dist: the recognition distribution
!
Field Number: the item field number:
!
1 = amount
!
2 = transaction code
!
3 = account
!
4 = transit
!
5 = serial
!
Number of Items: the total number of items processed
!
Number of Fields Read: the total number of item fields read correctly (the amount supplied by
the Recognition software matched the final balanced amount)
!
Number of Fields Misread: the total number of item fields misread
!
Number of Fields Rejected: the total number of fields rejected by CAR
!
Number of Items Failed Rec: the total number of items that the RSS failed to process because
of a bad image
!
Number of Items with Prior Data: the number of items with valid (pre-encoded) data in the field,
read by the EPU prior to recognition
At the end of this report, a CAR Performance Grand Totals Summary report shows the cumulative
totals of the above information for all RSSs in the system.
CAV Performance Summary Report
The CAV Performance Summary report summarizes how well each RSS performed with each type
of item field when it had second sources (images of adding machine tapes and deposit slips) to work
with.
This report shows:
216
!
Field Number: recognition field which is offset to DDR
!
Recognition Station: the Recognition Station to which the statistics apply
!
No. of Items Procs’d: the total number of items processed by the Recognition software on this DS
!
No. of Items Comb’d with Add Tape: the number of items for which the recognized amount was
combined with an adding machine tape image
!
No. of Items Comb’d to Deposit Slip: the number of items for which the recognized amount was
combined with a deposit slip image
!
No. of Items accp’d with Second Source: the total number of fields that were matched to a
second source value (for example, adding machine tapes + deposit slips)
!
No. of Items Accp’d without Second Source: the number of fields for which there was no second
source value, so the ‘raw’ Recognition Unit result was used
Chapter 5: Reports
!
No. of Items Accp’d by CAV: the number of fields for which the post-CAV result was correct (the
same as the final proof amount)
!
No. of Items Misread: the number of fields for which the post-CAV result was incorrect (different
than the final proof amount)
!
No. of Field Rejects: the number of fields that were rejected because the confidence value for
the post-CAV result was less than the confidence threshold
!
No. of Items Force Key Rej’d: the number of fields rejected because of the forced keying
parameters (singles and high-dollar values)
!
No. of Items with Prior Data in Field: the number of items where prior data were captured in the
target field
At the end of this report, a CAV Performance Grand Totals Summary shows the cumulative totals
of the above information for all RSSs in the system.
RSS Reclassification Report
The RSS Reclassification report summarizes the results for each recognition distribution that has
enabled the reclassification feature.
For each DS (or each Recognition Unit, if there is more than one on a DS), this report provides the
following information:
!
RSS Station: the name of DS system for retrieving data and the display name of the data server
!
RSS Dist.: the recognition distribution
!
Total Credits: total number of items of this distribution that end up as credits
!
Total Debits: total number of items of this distribution that end up as debits
!
Number of Credits Reclassified: number of items that end up as credits and have been
reclassified by RSS
!
Number of Debits Reclassified: number of items that end up as debits and have been reclassified
by RSS
!
Credit Accuracy: RSS credit reclassification accuracy on credits
!
Debit Accuracy: RSS credit reclassification accuracy on debits
At the end of each DS, a subtotal table shows the totals across the data server. At the end of this
report, a RSS Reclassification Summary report shows the cumulative totals on a separate page for
all groups across all PSet numbers and DS servers.
Note: If the DS server is in an invalid state or unable to establish a connection to this server, this
fact should be put into the report.
217
Chapter 5: Reports
RIR Document Distribution Report
The RIR Document Distribution report lists items that have been reimaged for the current batch, by
the current operator. The report lists the items in the order that they were reimaged.
Expert Balancers use this report to place the physical documents after reimaging.
!
Date: date and time the report was generated and printed
!
Cycle: cycle number the reimaged items belong in
!
Entry: entry number the reimaged items belong in
!
Batch: batch number the reimaged items belong in
!
PSET: Pset number associated with these items
!
far left column: indicates the source of the item
!
ri = regular reimaged item or regular front piggyback item
!
ins = reimaged adjustment, insert associated with the reimaged adjustment, real piggyback
associated with the front piggyback
!
3 = account
!
4 = transit
!
5 = serial
!
DRN: Document Reference Number of the reimaged item
!
Codeline: codeline of the reimaged item
!
Pocket Number: number of the transport pocket that this item belongs in
!
Tray Number: number of the tray that this item belongs in
!
Tray Sequence: tells the EBAL operator where to put the reimaged item within its tray as follows:
!
if the tray sequence is displayed, place the reimaged item in its original location
!
if the word “back” is displayed, place the reimaged item in the back of the reject pocket
Note: You determine what is displayed in the Tray Sequence column using the ManualDistribution
parameter, APP_TYPE_PSETS keyword.
218
Chapter 5: Reports
Second Source Match and Merge Performance Summary
Report
The Second Source Match and Merge Performance Summary report summarizes the processing
information for the Second Source Match and Merge auto-activity.
This report generates on the BAP database.
For each item, this reports shows the following information:
!
Classification: the type of item
!
Total Records: the total number of the SMM records imported into the database for the current
processing date (including items carried over from the previous day)
!
Matched To Items %: the percentage of deposit slips and debit items that were matched to the
physical items by SMM
!
Not Matched To Items %: the percentage of deposit slips and debit items that were not matched
to the physical items by SMM
!
Matched To Deposit Slips %: the percentage of deposit slips that were matched to the physical
items by SMM
!
Forced Matches %: the percentage against volume of this type of item that were force matched
by operators
Truly Missing and Free Report
The Truly Missing and Free report shows all of the items that could not be matched at Capture
Reconciliation and therefore defined as truly missing or truly free. This report generates by cycle on
the DAP database.
The following information is shown in this report:
!
!
!
Entry: the entry number, followed by the pocket pass history
!
MATCH: value is TRUMIS if the item is Truly Missing, TRUFRE if it is Truly Free
!
EXCEPTION: the item’s exception reason
!
ORIENT = outsorted because of orientation problem
!
OEP = outsorted because of over-encode protection
!
OR&OEP = outsorted because of both orientation and over-encode protection
!
SUSPENSE = resolved suspense item
!
OR&SUSP = resolved suspense item that was also an orientation problem
!
OEP&SUSP = resolved suspense item that was also an over-encode protection problem
!
OR&OEP&SU = resolved suspense item that was also both an orientation problem and
over-encode protection problem
!
!
ON-US: whether the item is on-us
!
YES = on-us item
219
Chapter 5: Reports
!
NO = transit item
!
a blank indicates a truly free or reconciled free item
!
!
(NP) item
!
FROM ENTRY: the number of the entry in which the item record was created. This field is blank
unless the item is resolved to an entry other than the one it was captured in at the EPU.
!
RECONCILED TRAY: the number of the tray in which the physical item would have been placed
(if a missing item). This is the tray it should have gone to, where it should have been pocketed
had it been seen at the ESU or resolved at Capture Reconciliation. If the item is truly free, this
field is blank.
!
the item’s codeline
!
! = transport reject character
User Permission and Login Information Report
The User Permission and Login Information report lists each operator, what workgroup they are in,
and what permissions they have.
220
!
Print Date: date the report was printed
!
Application Type: type of application (report has a section for every application type that is
installed on the system)
!
Work Group Name: the name of the work group the operator belongs to
!
Work Group Number: the number of the work group the operator belongs to
!
Operator Name: the operator’s ImageMark user name
!
Operator Number: the ID number assigned to that operator
!
Date of Last Login: date when that operator last logged in to the ImageMark system, in
mm/dd/yyyy format
!
Date of Password Change (UNIX systems only): date on which that operator’s current password
was set
!
Permissions: the ImageMark activities that operator is allowed to work on
Chapter 5: Reports
Operator Performance Reports
You can generate the operator performance reports after the system has processed all of the
reporting period’s work. They provide a complete overview of a reporting period’s work.
The main categories of operator performance reports are as follows:
!
ECU Transport Performance report
!
EPU and ESU Transport Performance Statistics reports
!
Image Quality Review Performance Summary report
!
Operator Statistics reports
!
Reconciliation Operator reports
!
Resource Allocation report
ECU Transport Performance Report
This report shows the following information for each ECU operator session:
!
Start Date and Time: date and time batch started in banking center
!
Stop Time: time batch ended in banking center
!
No. Jams: number of times this processing batch that the transport stopped due to a jam
(including track jams, hardware problems, and control item problems such as a missing expected
control item or an unexpected control item).
Totals row shows number of jams for all runs.
!
Start Seq. No.: sequence number of first item in batch
Totals row shows sequence number of the first item processed (the lowest sequence number).
!
End Seq. No.: sequence number of last item in batch
Totals row shows sequence number of the last item processed (the highest sequence number).
!
No. Items: number of physical items captured
Totals row shows number of physical items captured for all runs.
!
No. Rejects: number of capture application rejects
Totals row shows number of rejected items for all runs.
!
No. Unknown Items: number of EPA reject items
Totals row shows number of EPA reject items for all runs.
!
Items Per Minute: transport capture rate
Totals row shows average number of documents processed per minute.
!
Reject Rate: % of total number of physical items rejected at the transport
Totals row shows % of total processed documents rejected at capture.
The data for each transport is shown on a separate page. The report is ordered sequentially
according to the transport number.
The report does not include information about hold over units of work that have been re-loaded into
the system.
221
Chapter 5: Reports
EPU and ESU Transport Performance Statistics
The EPU and ESU Transport Performance reports provide information about transport performance
in the system.
These reports generate on the BAP database.
EPU Transport Performance Reports
Capture has two EPU Transport Performance reports:
!
EPU Transport Sessions Performance report
!
EPU Transport Performance Summary report
Note: For 779x transports, jam recovery times are not subtracted from the total transport run time.
This will result in the statistics figures in these two reports being inflated for a 779X transport.
EPU Transport Sessions Performance:
This report shows the following information for each operator session on each EPU:
!
Session Start Time: the time the operator started this activity
!
Session End Time: the time this activity terminated
!
Session Run Time: the total time spent processing entries or tray sets. Note that this total does
not include the time in between processing, such as when the transport is idle, suspension due
to hardware problems, or while the transport is being serviced.
!
Total No. Items: number of physical items processed
!
Average No. of Items per hour: average number of items processed per hour, based on the
session run time
!
No. of Transport Jams: number of times this session the transport stopped due to a jam. A jam
is a situation that stops the track during processing, including track jams, hardware problems,
and control item problems (for example, a missing expected control item or an unexpected
control item).
!
Downtime from Jams: total time spent recovering from jams
!
Average Downtime from Jams: average time spent recovering from a jam
!
No. of Other Transport Failures: number of failures other than jams
!
Downtime from Transport Failures: total time spent recovering from all transport failures except
those resulting from jams
!
Average Downtime from Transport Failures: average time to recover from a transport failure
!
No. of Rejected Images: number of images captured by the EPU and later rejected by an IDT
operator due to poor image quality. This option is only available if the associated parameter is
enabled in IDT_RECLASSIFY_CODES.
!
No. of Fields Rejected: number of fields rejected
!
No. of Fields Misread: number of fields misread
EPU Transport Performance Summary:
This report shows the same information as the EPU Transport Sessions Performance report, but
accumulates the data across all sessions of all EPUs in the system.
222
Chapter 5: Reports
ESU Transport Performance Reports
Capture has two ESU Transport Performance reports:
!
ESU Transport Sessions Performance report
!
ESU Transport Performance Summary report
ESU Transport Sessions Performance
This report shows the following information for each operator session on each ESU:
!
!
!
Session Run Time: the total time spent processing entries or tray sets. Note that this total does
NOT include the time in between processing, such as when the transport is idle, while the
operator is waiting for work within the activity, after a tray set has ended (while Stacking Selection
screen is displayed), suspension due to hardware problems, or while the transport is being
serviced.
!
Total No. Items: number of physical items processed
!
Average No. of Items per hour: average number of items processed per hour (not including idle
time)
!
No. of Transport Jams: number of times this session the transport stopped due to a jam. A jam
is a situation that stops the track during processing, including track jams, hardware problems,
and control item problems (for example, a missing expected control item or an unexpected
control item).
!
Downtime from Jams: total time spent recovering from jams
!
Average Downtime from Jams: average time spent recovering from each jam
!
No. of Other Transport Failures: number of failures other than jams
!
Downtime from Transport Failures: total time spent recovering from all transport failures except
those resulting from jams
!
Average Downtime from Transport Failures: average time spent recovering from each transport
failure
!
No. of MICR Verify Errors: number of times this ESU’s MICR Verifier found an encoding error
ESU Transport Performance Summary:
This report shows the same information as the ESU Transport Sessions Performance report, but
accumulates the data across all sessions of all ESUs in the system.
223
Chapter 5: Reports
Image Quality Review Performance Summary Report
This report shows, for every IQR operator who processed images in the current cycle, how many
items were reviewed and, of those, how many items were flagged as IQ Rejects. There is one row
for each operator per reporting period.
The total time taken to review the images, and the corresponding images reviewed per hour rate
are also be included in this report. All fields have grand totals for the reporting period.
This report lists the following data for each operator:
224
!
Reporting Period: time range during which this data was recorded
!
!
Operator Number: number that identifies the operator doing IQR
!
Action Time: total amount of time the operator was doing IQR
!
Total Number of Images: number of images reviewed by the operator
!
Average Hourly Rate: calculated hourly rate of image review by the operator
!
Total No. Images Rejected: number of images that the operator marked as bad
Chapter 5: Reports
Operator Statistics
The Operator Statistics reports provide performance statistics for the operators who work on the
IDT activities: Codeline Completion, Optional Field Completion, Amount Keying, Balancing, Expert
Balancing, and Deposit Review. There are four types of reports for each of these activities:
!
Operator Sessions Activity report
!
Operator Performance Summary report
!
Grand Total Performance report
!
Operator Performance Detail report
There is one additional report that is only for Balancing:
!
Balancing Operator Enhanced Performance Detail report
These reports generate by reporting period and workgroup on the BAP database.
Operator Sessions Activity Report
The Operator Sessions Activity report shows how each operator’s time was spent during each
session of the specified activity (working, waiting for work within an activity, and not working for
some other reason). This report has the same format for all IDT activities.
!
!
!
Session Duration: the time lapse between operator logon and activity termination
!
Session Action Time: total elapsed time in the session available for the operator to work (this
total does not include idle time, suspend time, or lost action time)
!
Lost Action Time: session time lost to abnormal termination (if any)
!
Wait For Work Time: total time that the operator was idle waiting for work within an activity
!
System Overhead: total time that the system was busy on overhead tasks, such as loading
parameters or retrieving work
!
Total Suspend Duration: total time that the operator had the software activity in a suspend state
(for example, for breaks). Not all suspend activities necessarily contribute to this total.
Parameters can be set to allow work to continue.
!
Suspend Start Time: the time the operator selected a suspend activity
!
Suspend Duration: the duration of each period that the operator had the software in a suspend
state
!
Activity Reason: activity code chosen by the operator, indicating why the system was suspended
(for example, taking a regularly scheduled break). This code is customized for each site through
the Operator Activity parameters.
225
Chapter 5: Reports
Operator Performance Summary Report
The Operator Performance Summary report shows each operator’s individual cumulative
performance for all the sessions that the operator has worked on the specified activity. Because of
the similarities in the work involved, the Operator Performance Summary reports for Balancing and
Expert Balancing have a common format.
Codeline Completion and Optional Field Completion:
The Operator Performance Summary reports for Codeline Completion and Optional Field
Completion contain the following information for each operator:
!
Operator Number: unique operator number
!
Action Time: total time available for operator to work in all sessions covered by this report (this
!
Total No. Items Pres’d: total number of items presented at Codeline Completion in these
sessions. Both keyed and rekeyed items are included in this total.
!
Avg. Hourly Rate: total number of items divided by action time
!
Total No. Items Rekeyed: total number of items that were rekeyed so that non-CDV (Check Digit
Verification) protected fields could be validated. This option is parameterized; if it is not enabled,
this field is blank.
!
Total Keyed Fields Corr’d: number of fields (NOT items) keyed incorrectly by this operator and
corrected later in workflow by other operators (check the ImageMark Transaction Manager Audit
report for details of the changes made and how they were subsequently corrected)
!
No. Actual Key Strokes: total number of buttons pressed by this operator. For example, pressing
1, 00, 00 is three actual keystrokes.
!
No. Key Strokes Credits: number of characters credited to the operator. If a field is keyed and
accepted, the operator is credited for the characters keyed for that field. For example, pressing
1, 00, 00 is five keystroke credits.
!
Avg. Hourly Key Strokes: number of actual keystrokes divided by action time
!
No. of EXP P/C Keyed/Errors: total number of EXP P/C fields (field 6) keyed, displayed over
the number of EXP P/C fields keyed incorrectly by this operator
!
No. of SERIAL Keyed/Errors: total number of SERIAL fields (field 5) keyed, displayed over the
number of SERIAL fields keyed incorrectly by this operator
!
No. of TRANSIT Keyed/Errors: total number of TRANSIT (field 4) fields keyed, displayed over
the number of TRANSIT fields keyed incorrectly by this operator
!
No. of ACCOUNT Keyed/Errors: total number of ACCOUNT (field 3) fields keyed, displayed
over the number of ACCOUNT fields keyed incorrectly by this operator
!
No. of TRANCOD Keyed/Errors: total number of TRANCODE (field 2) fields keyed, displayed
over the number of TRANCODE fields keyed incorrectly by this operator
!
No. of AMOUNT Keyed/Errors: total number of AMOUNT fields (field 1) keyed, displayed over
the number of AMOUNT fields keyed incorrectly by this operator
Note: The field names shown here are the default names found in RPT_FIELD_DEFNS
(rptdefn.dat). Fields 7 through 10 are not displayed, because they are turned off (field size
0) by default in this file. The report utility truncates the field name to fit the column width in
the report.
226
Chapter 5: Reports
Amount Keying:
The Operator Performance Summary report for Amount Keying contains the following information
for each operator:
!
!
!
Total No. Items: total number of items processed at Amount Keying in these sessions
!
!
Total Keyed Fields Corr’d: number of fields keyed incorrectly by this operator and corrected later
in workflow by other operators
!
!
!
Fields additional to the AMOUNT field are also displayed in the Amount Keying Operator
Performance Summary report. The Amount Keying Activity can be parameterized so that the
operator is not restricted to keying the AMOUNT field.
!
!
!
!
!
No. of TRNCODE Keyed/Errors: total number of TRANCODE (field 2) fields keyed, displayed
!
the number of AMOUNT fields keyed incorrectly by this operator. This total may be lower than
the Total No. Items because it only includes items the operator keyed the amount for. The
discrepancy between this number and the total number may be due to the operator using the
reject key to reject items.
the report.
227
Chapter 5: Reports
Balancing and Expert Balancing:
The Operator Performance Summary reports for Balancing and Expert Balancing contain the
following information for each operator:
!
!
!
Total No. Items: total number of items processed in these sessions. For Balancing and Expert
Balancing this number reflects the total number of items in the batches the operator worked on.
If more than one operator works on the same batch, both operators get credit for the number of
items in that batch.
!
!
Total No. Batches: total number of batches processed
!
Total No. Items Inserted: total number of balancing adjustments, including showouts
!
Total No. Fields Keyed: total number of fields keyed by this operator
!
Total No. Keyed Flds Corrected: number of fields keyed incorrectly by this operator and
corrected later in workflow by other operators
!
No. Images Rejected: number of images rejected by this operator
!
No. Actual Keystroke: total number of buttons pressed by this operator. For example, pressing
!
No. Keystroke Credits: number of buttons credited to the operator. If a field is keyed and
accepted, the operator is credited for the buttons pressed for that field. For example, pressing
1, 00, 00 is three keystroke credits.
Block Balancing and Expert Block Balancing:
The Operator Performance Summary reports for Block Balancing and Expert Block Balancing
provide a one-line summary for each operator. The report data is a cumulative total of the listed data
for all Block Balancing and Expert Block Balancing sessions for each operator.
Both Block Balancing and Offline Block Balancing activities can be included in this report (with a
separate section for each activity).
!
Operator Number: operator’s ID number
!
Action Time: time in the session available to operator for working
!
Total No. Items: number of items processed in this session
!
Avg. Hourly Rate: total number of items divided by action time. If multiple operators per entry,
average hourly rate is based on:
no. of changes done by this operator x total no. of items in the entry
no. of changes done by all operators
228
!
Total No. Items Inserted: number of adjustments made in this session
!
Total No. Fields Keyed: number of fields keyed by this operator
!
Total No. Keyd Flds Corrected: number of fields keyed incorrectly by this operator
!
No. Images Rejected: number of images this operator rejected during this session
!
Blocks Split: number of blocks split by this operator
Chapter 5: Reports
!
Batches Split: number of batches split by this operator
!
Batches Moved: number of batches moved to different blocks by this operator
These columns reflect suspect validation statistics:
!
MICR Misreads: number of MICR misreads that were detected in this session
!
Misenc: number of misencoded amounts that were detected in this session
!
Miskey: number of amount keying errors that were detected during this session
Deposit Review
The Operator Performance Summary report for Deposit Review contains the following information
for each operator:
!
!
!
Total No. Deposits Reviewed: total number of deposits processed in this session
!
!
Total No. Deposits Hold Reviewed: total number of deposits hold reviewed by this operator in
this session
!
Total No. Deposits NonNegotiable Reviewed: total number of non-negotiable deposits reviewed
by this operator in this session
!
Total No. Holds Applied: total number of holds applied to confirmed hold deposits in this session
(up to 4 holds are allowed per deposit)
!
Total No. Holds Removed: total number of holds removed from hold deposits in this session
!
Total No. Items Made Non-Negotiable: total number of items reclassified as non-negotiable in
this session
!
Total No. of Hold Deposits no Change: total number of deposits that were marked for hold review,
in which the operator made no hold change
!
Total No. of Non-Negotiable Deposits No Change: total number of deposits that were marked
for non-negotiable review in which the operator made no hold change
!
Total No. Deposits Returned Incomplete: total number of deposits that were presented for review
but were returned as incomplete
!
Total No. Deposits Returned Completed: total number of deposits that were presented for review
and were returned as complete because of a timed-out Web session or work timeout
!
Total No. of Deposits Timed Out: total number of deposits that were presented for review and
were returned because of a timed-out Web session or work timeout
the report.
229
Chapter 5: Reports
Operator Performance Detail Report
The Operator Performance Detail reports show the same kind of information for each IDT operator
as the Operator Performance Summary reports. But for each operator, instead of showing a single
line of cumulative data for all sessions, the Detail report shows a separate line for each session.
The Operator Performance Detail reports for Codeline Completion and Optional Field Completion
contain the following information for each operator:
!
!
Total No. Items Pres’d: total number of items presented in these sessions. Both keyed and
rekeyed items are included in this total.
!
!
Total No. Items Rekeyed: total number of items that were rekeyed so that non-CDV (Check Digit
Verification) protected fields could be validated. This option is parameterized; if it is not enabled,
this field is blank.
!
in workflow by other operators
!
!
!
!
!
!
!
!
!
the number of AMOUNT fields keyed incorrectly by this operator
the report.
Amount Keying:
The Operator Performance Detail report for Amount Keying contains the following information for
each operator:
230
Chapter 5: Reports
!
!
Total No. Items: total number of items processed in these sessions
!
!
by other operators
!
!
!
!
!
!
!
!
!
the number of AMOUNT fields keyed incorrectly by this operator. This total may be lower than
the Total No. Items because it only includes items the operator keyed the amount for. The
the report.
The Operator Performance Detail reports for Balancing and Expert Balancing contain the following
information for each operator:
!
!
Total No. Items: total number of items processed in these sessions. For Balancing and Expert
Balancing this number reflects the total number of items in the batches the operator worked on.
If more than one operator works on the same batch, both operators get credit for the number of
items in that batch.
231
Chapter 5: Reports
!
!
Total No. Batches: total number of batches processed in this session
!
Total No. Items Inserted: total number of balancing adjustments, including showout made
!
Total No. Fields Keyed: total number of fields keyed by this operator
!
Total No. Keyd Flds Corrected: total number of fields keyed incorrectly by this operator and
corrected later in workflow by other operators
!
No. Images Rejected: total number of images this operator rejected during this session
!
No. Actual Keystroke: total number of buttons pressed by this operator. For example, pressing
!
No. Keystroke Credits: number of buttons credited to the operator. If a field is keyed and
accepted, the operator is credited for the buttons pressed for that field. For example, pressing
1, 00, 00 is three keystroke credits.
The Operator Performance Detail reports for Block Balancing and Expert Block Balancing give the
same information as the Block Balancing and Expert Block Balancing Operator Performance
Summary Reports, in greater detail. Instead of providing one line per operator, these reports provide
one section for each operator. Each section contains several lines of information, one for each
session performed by that operator.
!
Action Time: time in the session available to operator for working
!
Total No. Items: number of items processed in this session
!
!
Total No. Items Inserted: number of adjustments made in this session
!
Total No. Fields Keyed: number of fields keyed by this operator
!
Total No. Keyd Flds Corrected: number of fields keyed incorrectly by this operator
!
No. Images Rejected: number of images this operator rejected during this session
!
Blocks Split: number of blocks split by this operator
!
Batches Split: number of batches split by this operator
!
Batches Moved: number of batches moved to different blocks by this operator
!
MICR Misreads: number of misread MICR amounts that occurred in this session
!
Misenc: number of misencoded amounts that occurred in this session
!
Miskey: number of amount keying errors by this operator during this session
Deposit Review
The Operator Performance Detail report for Deposit Review contains the following information for
each operator:
!
232
Chapter 5: Reports
!
Total No. Deposits Reviewed: total number of items presented in these sessions. Both keyed
and rekeyed items are included in this total.
!
!
Total No. Deposits Hold Reviewed: total number of deposits hold reviewed by this operator in
this session
!
Total No. Deposits NonNegotiable Reviewed: total number of non-negotiable deposits reviewed
by this operator in this session
!
Total No. Holds Applied: total number of holds applied to confirmed hold deposits in this session
(up to 4 holds are allowed per deposit)
!
Total No. Holds Removed: total number of holds removed from hold deposits in this session
!
Total No. Items Made Non-Negotiable: total number of items reclassified as non-negotiable in
this session
!
Total No. of Hold Deposits no Change: total number of deposits that were marked for hold review,
in which the operator made no hold change
!
Total No. of Non-Negotiable Deposits No Change: total number of deposits that were marked
for non-negotiable review in which the operator made no hold change
!
Total No. Deposits Returned Incomplete: total number of deposits that were presented for review
but were returned as incomplete
!
Total No. Deposits Returned Completed: total number of deposits that were presented for review
and were returned as complete
!
Total No. of Deposits Timed Out: total number of deposits that were presented for review and
were returned because of a timed-out Web session or work timeout
the report.
Grand Total Performance Report
The Grand Total Performance report for each IDT activity is similar to the Operator Performance
Summary reports, but rather than showing a separate line of cumulative data for each operator, the
Grand Total report shows combined cumulative data for all operators and all sessions of the activity
since this application instance was first loaded.
The Grand Total Performance reports for Codeline Completion and Optional Field Completion
contain the following information:
!
Cum. Action Time: cumulative time available for all operators to work in all sessions covered by
this report (this total does not include idle time, suspend time, or lost action time)
!
Cum. Total No. Items Pres’d: cumulative number of items presented in these sessions, including
both keyed and rekeyed items
!
Cum. Avg. Hourly Rate: cumulative number of items divided by action time
!
Cum. Total No. Items Rekeyed: cumulative total number of items that were rekeyed so that nonCDV (Check Digit Verification) protected fields could be validated. This option is parameterized;
if it is not enabled, this field is blank.
233
Chapter 5: Reports
!
Cum. Total Keyed Fields Corr’d: cumulative number of fields keyed incorrectly and corrected
later in workflow
!
Cum. No. Actual Key Strokes: cumulative number of buttons pressed. For example, pressing
!
Cum. No. Key Strokes Credits: cumulative number of characters credited to all operators. If a
field is keyed and accepted, the operator is credited for the characters keyed for that field. For
example, pressing 1, 00, 00 is five keystroke credits.
!
Cum. Avg. Hourly Key Strokes: cumulative number of actual keystrokes in all operator sessions
divided by action time
!
Cum. No. of EXP P/C Keyed/Errors: total number of EXP P/C fields (field 6) keyed, displayed
over the number of EXP P/C fields keyed incorrectly by this operator
!
Cum. No. of SERIAL Keyed/Errors: total number of SERIAL fields (field 5) keyed, displayed over
the number of SERIAL fields keyed incorrectly by this operator
!
Cum. No. of TRANSIT Keyed/Errors: total number of TRANSIT (field 4) fields keyed, displayed
over the number of TRANSIT fields keyed incorrectly by this operator
!
Cum. No. of ACCOUNT Keyed/Errors: total number of ACCOUNT (field 3) fields keyed,
displayed over the number of ACCOUNT fields keyed incorrectly by this operator
!
Cum. No. of TRNCODE Keyed/Errors: total number of TRANCODE (field 2) fields keyed,
displayed over the number of TRANCODE fields keyed incorrectly by this operator
!
Cum. No. of AMOUNT Keyed/Errors: total number of AMOUNT fields (field 1) keyed, displayed
over the number of AMOUNT fields keyed incorrectly by this operator
the report.
Amount Keying:
The Grand Total Performance report for Amount Keying contains the following information:
!
!
Cum. Total No. Items: cumulative number of items processed in these sessions
!
Cum. Avg. Hourly Rate: cumulative number of items divided by action time
!
Cum. Total Keyed Fields Corr’d: cumulative number of fields keyed incorrectly and corrected
later in workflow
!
Cum. No. Actual Key Strokes: cumulative number of buttons pressed. For example, pressing
!
Cum. No. Key Strokes Credits: cumulative number of characters credited to all operators. If a
field is keyed and accepted, the operator is credited for the characters keyed for that field. For
!
Cum. Avg. Hourly Key Strokes: cumulative number of actual keystrokes keyed in all operator
sessions divided by action time
234
Chapter 5: Reports
!
Cum. No. of EXP P/C Keyed/Errors: total number of EXP P/C fields (field 6) keyed, displayed
over the number of EXP P/C fields keyed incorrectly by this operator
!
Cum. No. of SERIAL Keyed/Errors: total number of SERIAL fields (field 5) keyed, displayed over
the number of SERIAL fields keyed incorrectly by this operator
!
Cum. No. of TRANSIT Keyed/Errors: total number of TRANSIT (field 4) fields keyed, displayed
over the number of TRANSIT fields keyed incorrectly by this operator
!
Cum. No. of ACCOUNT Keyed/Errors: total number of ACCOUNT (field 3) fields keyed,
displayed over the number of ACCOUNT fields keyed incorrectly by this operator
!
Cum. No. of TRNCODE Keyed/Errors: total number of TRANCODE (field 2) fields keyed,
displayed over the number of TRANCODE fields keyed incorrectly by this operator
!
Cum. No. of AMOUNT Keyed/Errors: total number of AMOUNT fields (field 1) keyed, displayed
over the number of AMOUNT fields keyed incorrectly by this operator. This total may be lower
than the Total No. Items because it only includes items the operator keyed the amount for. The
the report.
The Grand Total Performance reports for Balancing and Expert Balancing contain the following
information:
!
Cum. Action Time: cumulative time available for all operator sessions (this total does not include
idle time, suspend time, or lost action time)
!
Cum. Total No. Items: cumulative number of items processed in all operator sessions. This
number reflects the total number of items in the batches the operators worked on.
!
Cum. Avg. Hourly Rate: cumulative number of items processed divided by the sum of the action
time for all operator sessions
!
Cum. Total No. Batches: cumulative number of batches processed in all operator sessions
!
Cum. Total No. Items Inserted: cumulative number of adjustments, including showouts, made
in all operator sessions
!
Cum. Total No. Fields Keyed: cumulative number of fields keyed in all operator sessions
!
Cum. Total No. Keyd Flds Corrected: cumulative number of fields keyed incorrectly in all operator
sessions
!
Cum. No. Images Rejected: cumulative number of images rejected in all operator sessions
!
Cum. No. Actual Keystroke: cumulative number of buttons pressed. For example, pressing 1,
00, 00 is three actual keystrokes.
!
Cum. No. Keystroke Credits: cumulative number of characters credited to all operators. If a field
is keyed and accepted, the operator is credited for the characters keyed for that field. For
235
Chapter 5: Reports
The Grand Total Performance reports for Block Balancing and Expert Block Balancing provide a
performance summary for all Block Balancing and Expert Block Balancing operators across all
sessions in a specified date range.
!
Cum. Action Time: total time in all sessions available to operators for working
!
Cum. Total No. Items: total number of items processed in all operator sessions
!
Cum. Avg. Hourly Rate: sum of total number of items processed divided by sum of action time
across all operator sessions
!
Cum. Total No. Items Inserted: sum of total number of adjustments made in all operator sessions
!
Cum. Total No. Fields Keyed: total number of fields keyed by all operators in all sessions
!
Cum. Total No. Keyd Flds Corrected: total number of fields keyed incorrectly by all operators in
all sessions
!
Cum. No. Images Rejected: total number of images rejected by all operators in all sessions
!
Cum. Blocks Split: total number of blocks split by all operators in all sessions
!
Cum. Batches Split: total number of batches split by all operators in all sessions
!
Cum. Batches Moved: total number of batches moved to different blocks by all operators in all
sessions
!
Cum. MICR Misreads: total number of misread MICR amounts that occurred in all operator
sessions
!
Cum. Misenc: total number of misencoded amounts that occurred in all operator sessions
!
Cum. Miskey: total number of amount keying errors by all operators during all sessions
Deposit Review
The Grand Total Performance report for Deposit Review contains the following information:
236
!
!
Cum. Total No. Deposits Reviewed: cumulative number of deposits reviewed in these sessions
!
Cum. Avg. Hourly Rate: cumulative number of deposits reviewed divided by action time
!
Cum. Total No. Deposits Hold Reviewed: cumulative number of deposits hold reviewed by all
operators in this session
!
Cum. Total No. Deposits Non-Negotiable Reviewed: cumulative number of deposits nonnegotiable reviewed by all operators in this session
!
Cum. Total No. Holds Applied: cumulative number of holds applied to deposits by all operators
in this session. Up to 4 holds are allowed per item.
!
Cum. Total No. Holds Removed: cumulative number of holds removed from deposits by all
operators in this session
!
Cum. Total No. Items Non-Negotiable: cumulative number of items reclassified as nonnegotiable in all operator sessions
Chapter 5: Reports
!
Cum. Total No. of Hold Deposits No Change: cumulative number of deposits in this session that
were marked for hold review, in which an operator made no hold change
!
Cum. Total No. of Non-Negotiable Deposits No Change: cumulative number of deposits in this
session that were marked for non-negotiable review, in which an operator made no hold change
!
Cum. Total No. Deposits Returned Incomplete: cumulative number of deposits that were
presented for review but were returned as incomplete in this session
!
Cum. Total No. of Deposits Returned Completed: cumulative number of deposits that were
presented for review and were returned as complete in this session
!
Cum. Total No. of Deposits Timed Out: cumulative number of deposits that were presented for
review but were returned because of a timed out web session or work timeout in this session
!
Total No. Deposits Created for Review: number of deposits that the deposit review autorole
flagged for review
!
Total No. Deposits Created for Hold Review: number of deposits that the deposit review autorole
flagged for hold review
!
Total No. Deposits Created for Nonnegotiable Review: number of deposits that the deposit
review autorole flagged for negotiable review
!
Total No. Automatic Holds Applied: Number of automatic holds applied by the autorole
!
Total No. Automatic Nonnegotiable Changes: number of automatic non-negotiable changes
applied by the autorole
!
Total No Deposits Flagged for ReReview: number of deposits that the autorole flagged for rereview by operators
!
Total No. Deposits Processed: number of deposits that the autorole processed
the report.
Reconciliation Operator Reports
The Reconciliation operator reports provide a summary of each operator’s session that matches
Reconciliation or Expert Reconciliation operator statistics. These reports are essentially enhanced
versions of the Balancing/Expert Balancing operator statistics reports with some additional data.
The following information for reconciliation operators (and expert reconciliation operators, if
applicable to your environment) is included in the Performance Summary and Performance Detail
reports listed previously in this section:
!
Total No. Images Reimaged: total number of images this operator reimaged
!
Total No. Items Missing: total number of items matched through second source matching that
this operator unmatched
The following information for reconciliation operators (and expert reconciliation operators, if
applicable to your environment) is included in the Grand Total Performance reports:
!
Cum. No. Items Reimaged: cumulative total number of images all operators re-imaged
!
Cum. No. Items Missing: cumulative number of items matched through second source matching
that all operators unmatched
237
Chapter 5: Reports
Balancing Operator Enhanced Performance Detail Report
This report is an operator statistics report that provides additional balancing statistics for each
operator. For each balancing operator who processed work during the processing day, the report
has one line of output that combines the results of all sessions during the processing day for that
operator.
The report is a comma separated flat-file, so the information can be easily imported into another
application for further processing.
Note: Operators do not view this report.
Each line in the file consists of the operator number followed by these 29 fields of information:
!
total amount of time in seconds the operator spent balancing transactions
!
total number of batches the operator completely balanced
!
total number of items in the batches balanced by the operator
!
total number of batches the operator sent to Expert Balancing
!
total number of items in the batches the operator sent to Expert Balancing
!
total number of batches returned by the operator
!
total number of items in the batches returned by the operator
!
total number of credits in the batches balanced by the operator
!
total number of debits in the batches balanced by the operator
!
total number of items corrected by the operator
!
total number of fields corrected by the operator
Note: A field is considered corrected if the operator changes the value in a field, the value is changed
during re-imaging, or the operator reclassifies the item. An adjustment is not considered a
correction.
!
total number of keystrokes made by the operator
!
total number of items the operator reclassified to non-proof
!
total number of items the operator moved into the suspense pool
!
total number of items the operator moved out of the suspense pool
!
total number of items the operator moved between transactions
Note: Moving an item from one transaction to another and then back again counts as two moves.
238
!
total number of tape substitute documents
!
total number of type 1 adjustments made by the operator
!
!
!
!
!
!
Chapter 5: Reports
!
!
!
Note: The adjustment type refers to a group of adjustments that maps to the
IDT_ADJUSTMENT_CODES AdjReasonCode parameter. Duplicate adjustment reason
codes are allowed across groupings. If the adjustment type is not defined, the report shows
a 0.
!
total number of items the operator located by pressing Suspect
!
total number of items that were changed after being located by pressing Suspect
239
Chapter 5: Reports
Resource Allocation Report
The Resource Allocation report provides a summary of session activity for individual operators within
a workgroup and the totals for all operators in that workgroup.
The session activity information provides the following information for each activity on which the
operator worked:
!
ACTV: the activity on which the operator worked
!
SESSION START TIME: the time the operator started the activity
!
SESSION END TIME: the time the activity terminated
!
SESSION DURATION: the time lapse between activity start and activity termination
!
SESSION ACTION TIME: the total elapsed time in the session available for the operator to work
(this total does not include idle time, suspend time, or lost action time)
!
WAIT FOR WORK TIME: total time that the operator was idle waiting for work within an activity
!
WAIT FOR WORK %: percentage of total time that the operator waited for work
!
WORK READY TIME: total time that available work was not selected by the operator (ESU or
Capture Reconciliation only)
!
WORK READY %: percentage of total time that available work was not selected by the operator
(ESU or Capture Reconciliation only)
!
SUSPEND DURATION: total time that the operator had the software activity in a suspended
state (for example, for breaks)
!
SYSTEM OVERHEAD %: the percentage of time the system was busy on overhead tasks, such
as loading parameters or retrieving work
For each operator, a summary line shows totals for:
!
Duration: the total time that the operator was logged onto the system components
!
Action Time: the total time that the operator was actually working
!
Wait For Work Time: the total time that the operator waited for work
The final entry for each workgroup contains the same fields as the individual operator reports, but
shows cumulative totals for every operator at each activity. The totals for all activities are displayed
at the bottom of the entry.
240
Chapter 5: Reports
Auto-Activity Reports
ImageMark Transaction Manager automatically generates auto-activity reports. Auto-activity reports
can be categorized by the background programs (auto-activities) that create them. ImageMark
Transaction Manager can automatically print two sets of reports:
!
Entry Item reports
!
Tray Set reports
!
ATM reports
This section contains samples of the auto-activity reports and descriptions of their contents.
Note: The term “host entry” in the following samples is equivalent to “host job” for SuperMICR
systems.
Depending on how your system has been configured, the system may print any or all of the Entry
Item and Tray Set reports described on the following pages. For more information, see the report
parameter information in ImageMark Transaction Manager Parameter Generation: ASCII Files.
For instructions on how to manually view and print auto-activity reports using Application Manager,
see “Managing the Print Spooler” on page 64.
Entry Item Reports
The Entry Item reports provide information about all of the items in each entry processed at each
EPU. The Entry Item Reports (EIR) auto-activity creates these reports once all the batches in an
entry have been balanced. These reports use information from Balanced Item Export and Sub-Pass
Item Export auto-activities and the Capture Reconciliation activity. These are the Entry Item reports:
!
Entry Summary report
!
All Items report
!
Batch Proof List report
!
Adjustment/Corrections report
!
Suspense Items In EPU Kill Pockets report
!
Suspense Items in EPU Reject Pocket report
!
Items Reassigned from EPU Kill Pocket report
!
Items Pull reports
!
SMM Results report
!
EIR Deposit Corrections report
!
EIR Deposit Review Host report
!
Misencode Detail report
!
Low-Speed Items in High-Speed Pockets report
241
Chapter 5: Reports
You should print the All Items and Batch Proof List reports to file instead of paper. In high-production
environments, these reports slow the system down. To avoid printing these reports every time, you
can change the parameters in the report file.
Note: You can enable or disable these reports in EIR_RPT_GEN (eirgen.dat).
Entry Summary Report
The Entry Summary report provides summary information for each batch within an entry. This report
also shows totals for the entry as a whole.
!
!
!
!
Block: the number of the block the entry belongs to
!
BATCH No.: identifying number of batch
!
TOTAL ITEMS: the total number of items in the batch, not including items in the Suspense Pool.
!
CR COUNT: the number of credits in the batch
!
DR COUNT: the number of debits in the batch
!
TOTAL DR+CR COUNT: the total number of debits and credits in the batch
!
CR TOTAL: the amount total for the credits
!
DR TOTAL: the amount total for the debits
Note: Blocks shown with $0.00 and 0 credits and debits are control items. They are listed
separately.
At the end of the report, similar totals are given for the entry as a whole.
All Items Report
The All Items report provides detailed information for every item in an entry.
Note: Printing to file will not result in a performance decline, but, due to the volume of data generated
for this report, printing to paper may slow the system.
242
!
!
!
!
BATCH No.: identifying number of batch
!
DRN: the Document Reference Number
!
TYPE: item classification
!
CR = credit
!
NP = non-proof
Chapter 5: Reports
!
(no value) = debit
!
RECORD: document record ID
!
DISTRIBUTION NAME: the name of the distribution to which this item belongs
!
EXPT: if an exception item, this code identifies the type:
!
O = unresolved suspense item or outsort item
!
U = orientation item
!
G = control ghost item
!
S = suspense ghost item (resolved suspense)
!
A = adjustment ghost item
!
P = physical adjustment item (for example, a piggyback item)
!
M = moved item
Note: A ghost item is a non-physical item (an electronic record).
!
SERIAL, FRDABA, ACCOUNT No., TRAN: values for any or all of these fields, if captured
!
AMOUNT: the value of the amount field
(rptdefn.dat). The report utility truncates the field name to fit the column width in the report.
Batch Proof List Report
The Batch Proof List report resembles the All Items report, but is organized by batches.
Note: Printing to file will not result in a performance decline, but, due to the volume of data generated
for this report, printing to paper may slow the system.
For each batch, this report first shows the following summary information:
!
!
!
!
Block: the number of the block the work belongs to
!
Batch: the number of the batch the work belongs to
!
Items in Batch: total number of items in batch
!
Header Amount: the amount on the batch header
!
Total Debits: total debit amount for the batch
!
Total Credits: total credit amount for the batch
!
Total NPDR: NP debit amount from Batch table
!
Total NPCR: NP credit amount from Batch table
For each item in the batch, this report then shows:
!
!
AMOUNT: value of the amount field
243
Chapter 5: Reports
!
TYPE: item classification from document data record
!
EXPT: if an exception item, this code identifies the type:
!
O = unresolved suspense item or outsort item
!
U = orientation item
!
G = control ghost item
!
S = suspense ghost item (resolved suspense)
!
A = adjustment ghost item
!
P = physical adjustment item (for example, a piggyback item)
!
M = moved item
Note: A ghost item is a non-physical item (an electronic record).
Adjustment/Corrections Report
The Adjustment/Corrections report summarizes all adjustments and corrections (for example,
suspense items) made during Balancing.
For each entry in the cycle, this report shows the following information:
!
!
!
!
BATCH No.: the batch number of the item for which the adjustment or correction was made
!
!
ADJ: a code indicating the reason for the adjustment (adjustment reason codes are customdefined through the Balancing parameters at each site). A blank value indicates a resolved
suspense item.
!
ADJ_TYPE: type of adjustment
!
CR = credit
!
(no value) = debit
!
FIELD 10, FIELD 9, SERIAL, FRDABA, ACCOUNT No., TRAN: values for any or all of these
fields, if captured
!
(rptdefn.dat). The report utility truncates the field name to fit the column width in the report.
Suspense Items In EPU Kill Pockets Report
The Suspense Items In EPU Kill Pockets report shows Suspense Pool items in the entry that were
sorted to the EPU kill pocket.
244
!
!
Chapter 5: Reports
!
!
TRAY No.: the EPU kill tray number
!
POCKET: the number of the pocket in which the kill document was placed
!
!
CLASSIFICATION: the item classification
!
!
CODELINE: the item codeline
Note: This report has also been customized for BTM processing. The report will show the BTM
batch number for each item listed under the following field heading:
!
BTM BATCH NO.: the BTM batch that the item belongs to
Suspense Items in EPU Reject Pocket Report
The Suspense Items in EPU Reject Pocket report lists all suspense items in the entry that were sent
to the EPU reject pocket.
In this report, the items are listed by document reference number. The following information is shown
in this report:
!
!
!
!
TRAY NO.: the EPU Reject Pocket tray number
!
TRAY SEQ: the location of the item in the tray (e.g., 4.00 means the item is the fourth in the tray)
!
!
SERIAL, BANK, ACCOUNT, TRNCODE, AMOUNT: the values captured for these fields
Note: This report has also been customized for BTM processing. The report will show the BTM
batch number for each item listed under the following field heading:
!
Items Reassigned from EPU Kill Pockets Report
The Items Reassigned from EPU Kill Pockets report lists all items in an entry that were sent to the
EPU kill pocket and that have had their distribution changed due to one of the reasons listed below.
In this report, the items are listed by tray number and document record number. The following
information is shown in this report:
!
!
!
!
TRAY NO.: the account number field of the first tracer in the 3890 kill pocket. If there is no tracer,
then it is an ImageMark-assigned tray number.
!
ORIG PKT: the pocket the item was originally assigned to
245
Chapter 5: Reports
!
NEW PKT: the pocket the item is reassigned to, based on the new distribution
!
3890 PKT: the 3890 equivalent of the of the ImageMark reassigned pocket
!
REASON: a code indicating the reason for the item reclassification
!
U = unknown/other
!
F = field manipulation directive
!
R = research reclassify
!
D = data entry post-EPU
!
!
CLASSIFICATION: the item classification
!
!
CODELINE: a dot-separated pseudo codeline, generated by EPA
Items Pull Reports
ImageMark Transaction Manager provides the ability to print an Items Pull report as an Entry Item
report. For more details about Items Pull reports, see “Items Pull Report” on page 212 and
“Customizing Items Pull Reports” in ImageMark Transaction Manager Parameter Generation:
Application Generator.
SMM Results Report
This report is a CSV flat file. It is currently used only in the BTM environment.
The smmresults script, which generates the SMM Results report, is launched automatically by EIR.
If you need to generate this report manually, refer to “Printing Entry Item Reports” on page 178.
EIR Deposit Corrections Report
The EIR Deposit Corrections Report is a delimited data output file (not a formatted, printable report).
At end of cycle, this file can be uploaded to your host system or imported into a third party tool to
aid with analysis and/or research of customer deposit corrections that resulted in Advice Notices
being generated.
The output file contains the following parts:
!
one header record
!
one detail record for each adjustment item that has been parameterized to be exported as part
of the output file
!
one trailer record
EIR Deposit Review Host Report
This report is a CSV flat file. It is used by the host system to process holds applied against ATM
deposits.
The last line of the report contains trailer information that the host system uses to verify the content
of the file (for example, to verify that the amounts of the holds have not been corrupted).
246
Chapter 5: Reports
Misencode Detail Report
Operators use this report to find misencoded items and pull them from the work. Complete
transactions are listed in this report, including all credits and debits, whether misencoded or not. If
the credit is not misencoded, then the Actual Amnt. for that item is left blank.
This report is:
!
organized by entry
!
grouped by the sending bank (with each bank on a separate page)
!
used to provide feedback for work coming in with too many misencodes
This report gives the following information for each misencoded item:
!
CR/DB/NP: item type (credit, debit, or non-proof). “DEP CR” is the credit item where a misencode
occurred (not a misencode).
!
DRN: Document Reference Number of the misencoded item
!
Field2 to Field5: column titles and content are controlled by the RPT_FIELD_DEFNS keyword
!
Encoded Amnt.: the misencoded amount for the item
!
Actual Amnt.: the actual amount of the item, as keyed by the operator
!
Pocket: pocket in which to find the item
!
Tray: tray in which to find the item
!
ON-US: YES indicates an on-us item; No indicates a transit item
!
Cnt: consecutive number for debit items within a transaction (reset to 1 for each new transaction)
247
Chapter 5: Reports
Low-Speed Items in High-Speed Pockets Report
This new Entry Item report is generated for any pre-encoded or inclearings entries. The report lists
non-reject items whose fields were changed at Balancing. Use the report to find these items which
should have been pulled at Balancing and put into a central area. Once you find these items, you
can adjust the bundle list and cash letter for trays containing these items. Prepare Balancing credits
to go with them, and put them at the back of the prepared ESU pocket (prepared using the Bundle
List report or the Pocket Listing report).
If you cannot find an item listed on this report, it may not have been pulled at Balancing. Try to find
it in its original tray (if the tray is still available). If the item has already left the building, you should
subtract it from your General Ledger item total.
For each data transmission, the report lists the following information:
248
!
Date: the cycle process date
!
!
Host Entry: the 3890 entry number (same as Entry for 3890 entries)
!
Entry: the ImageMark entry number (same as Host Entry for 3890 entries)
!
Orig Pkt: the original 3890 capture pocket
!
Tray No.: either the first tracer in that pocket, or an internal ImageMark tray number (if no tracers
go to that pocket)
!
Low-Speed Pkt: the item’s “low-speed” pocket, assigned when a field is keyed
!
Type: type of item: CR (credit), DR (debit), or NP (non-proof)
!
DRN: the document reference number of the item
!
Serial: the item’s serial number
!
Bank: the item’s bank number
!
Account: the item’s account number
!
Trncode: the item’s trancode
!
Amount: the item’s amount
Chapter 5: Reports
Tray Set Reports
The Tray Set report auto-activity generates reports on tray and tray set units-of-work. The Tray Set
reports, which are printed automatically as processing of each tray set is completed, are:
!
Capture Reconciliation Audit report
!
Capture Reconciliation Audit Pocket Summary report
!
ESU Pocket Total report
!
ESU Operator Matched Item Audit report
Note: You can enable or disable these reports in TSR_RPT_GEN (tsrgen.dat).
Capture Reconciliation Audit Report
The Capture Reconciliation Audit report shows how the Capture Reconciliation operators dealt with
each of the items in each ESU exception pocket tray. To do so, this report groups these items into
the following categories:
!
!
Reconciled/Dispatched
!
all reconciled on-us items
!
all reconciled transit items
Reload
!
all pushed on-us items
!
all pushed transit items
!
Research: all research items
!
Exception
!
!
unresolved suspense items
!
truly missing items
!
truly free items
Sort Pattern Errors
!
!
sort pattern error items (time-of-day sort)
Non-Negotiable Items
!
items identified as non-negotiable
!
Cycle: the cycle the work belongs to
!
!
MATCH: the item’s match status:
!
ESUMAT = document record and physical item matched by ESU; see EXCEPTION for
outsort reason
!
MISSNG or TRUMIS = missing document record reconciled to physical item (free record
following) or truly missing document record with no physical item
!
FREE or TRUFRE = physical free item reconciled to preceding Cap Rec audit entry or truly
free physical item with no matching document record
249
Chapter 5: Reports
!
!
ESUPIG = missing document record reconciled to an ESU piggyback (free record following)
!
DUPLIC = missing document record reconciled to a duplicate codeline (free record
following)
!
NONNEG = non-negotiable item recognized by Cap. Rec.
EXCEPTION: the reason that the item was outsorted to the ESU exception tray:
!
!
OEP = outsorted because of over-encode protection problem
!
!
UNRSLV = unresolved suspense item
!
SPER = sort pattern error
!
NN = outsorted because the item is non-negotiable
Note: Iitems that were outsorted due to more than one problem are identified by the codes for each
problem, separated by an & symbol. For example,
OR&SUSP: a resolved suspense item that was also an orientation problem
NN&OEP: item was outsorted because of over-encode protection problem, and later
identified as a non-negotiable item
!
!
!
YES = on-us item
!
NO = transit item
!
!
!
(NP) item
!
FROM ENTRY: the number of the entry in which this item belongs
!
RECONCILED TRAY: the number of the tray in which the physical item was placed (if reconciled)
!
processed at Capture Reconciliation, and the total of these three categories.
The following example shows the section of this report that covers reconciled/dispatched transit
items.
250
Chapter 5: Reports
Capture Reconciliation Audit Pocket Summary Report
The Capture Reconciliation Audit report shows all of the items of a specified ESU exception pocket
tray that were modified by the Capture Reconciliation operators.
!
Cycle: the cycle the work belongs to
!
!
!
!
YES = on-us item
!
NO = transit item
!
!
SERIAL, BANK, ACCOUNT, TRNCOD: values for any or all of these fields, if captured
!
!
PKT: the exception pocket tray number
!
(NP) item
The TRAY TOTALS line of this report shows the total number of credit, debit and non-proof items
that were processed at Capture Reconciliation, and the total amount that was reconciled.
ESU Pocket Total Report
The ESU Pocket Total report provides pocket information about each tray in the tray set.
Note: This report references only the first entry in a stacked ESU run.
This report provides the following information:
!
Entry Number: the original entry number for the unit of work
!
Host Entry Number: the number of the host entry (CPCS) or host job (SuperMICR) the work
belongs to
!
Input Tray Amount: the expected total amount for the input tray items
Note: This amount may be from multiple entries.
!
TRAY HEADER NUMBER (CPCS) or POCKET SEPARATOR NUMBER (SuperMICR): the
number of the tray header item for CPCS or the number of the pocket separator item for
SuperMICR
!
ESU POCKET NUMBER and 3890 POCKET NUMBER: the pocket into which the ESU sorted
the items and the corresponding 3890 pocket
!
TOTAL AMOUNT: the total dollar amount of all items in the tray
251
Chapter 5: Reports
!
TOTAL NUMBER ITEMS: the number of items in the tray
If the Input Tray Amount and the sum of the Total Amount column are not equal it means you have
unresolved suspense items or truly missing items.
ESU Operator Matched Item Audit Report
The ESU Operator Matched Item Audit report provides information about every item matched by
Operator Assisted Item Matching at the ESU.
!
!
!
MATCH: the item’s match status:
!
252
!
FREE = physical free item that the ESU operator matched to preceding audit entry
!
DUPLIC = missing document record reconciled to a duplicate codeline (free record
following)
!
MISSNG = missing document record reconciled to physical item (free record following)
EXCEPTION: the reason that the item was outsorted to the ESU exception tray:
!
ADJ = adjustment item
!
!
OEP = outsorted because of over-encode protection
!
OR&OEP = outsorted because of both orientation and over-encode protection
!
!
UNRSLV = unresolved suspense item
!
OR&SUSP = resolved suspense item that was also an orientation problem
!
OEP&SUSP = resolved suspense item that was also an over-encode protection problem
!
OR&OEP&SU = resolved suspense item that was also both an orientation problem and
over-encode protection problem
!
!
!
YES = on-us item
!
NO = transit item
!
!
!
CR/DB/NP: a code indicating whether the item is a credit (CR), a debit (DB), or a non-proof (NP)
item
!
FROM ENTRY: the number of the entry in which this item belongs
!
RECONCILED TRAY: the tray in which the reconciled item belongs
!
Chapter 5: Reports
ATM Reports
There is one auto-activity report that has been customized for ATM processing:
!
Putaway Transaction report
Putaway Transaction Report
Once an entry is balanced, a Putaway Transaction report is printed for that entry. Operators use
this report to research and locate the physical documents for complete transactions (putaways) that
have been moved to the Suspense Pool. This report is similar to the Unresolved Suspense Items
report, with two additional features:
!
it is printed as soon as an entry is balanced, rather than at the end of the day, so that research
can begin promptly
!
it includes indents and blank lines to clearly separate each complete transaction
!
!
!
!
!
SERIAL, BANK, ACCOUNT, TRAN: values for any or all of these fields, if captured
!
!
CR/DB/NP: item classification
!
CR = credit
!
NP = non-proof
!
DB = debit
!
TRAY No.: the number of the tray the item belongs to
!
PKT: the number of the pocket the item was sent to
The TOTALS line of this report shows the total number of credit, debit, and non-proof items
processed for this entry, as well as the sum of these three numbers.
253
Chapter 5: Reports
MIE Exception Report
The purpose of this report is to provide a record of changed items (in the batch that MIE uploads to
the SuperMICR host) that exceed the maximum number specified by the MaxChangesPerBatch
parameter (XML_GATEWAY_PARMS keyword). The default maximum value is 20. When
MaxChangesPerBatch is set to 1 or higher, and the number of changes in the batch exceeds this
number, the system splits the batch. Changes that occur after the split are recorded in this report.
Notes: !
For details on the XML_GATEWAY_PARMS parameters, see chapter 1 of ImageMark
Transaction Manager 4.2 Parameter Generation, ASCII Files (B004-0000-0610).
!
For information on FIELD_DEFNS parameters see chapter x of ImageMark Transaction
Manager 4.2 Parameter Generation, Application Generator (B004-0000-0611).
This report is an ASCII file, saved in Windows format.
Printing the Report
To locate and print the Modified Item Export report:
1
Go to the Landing Zone for requests, specified by the ReqPath parameter
(XML_GATEWAY_PARMS keyword).
2
In any text editor, open the report file, named xxxx100000000hhmmssd0bbb.ble, where
xxxx = the entry_number;
hhmmssd = the EPU start time in hours, minutes, seconds and day of the week;
bbb = the banksite system id
3
Print from the text editor.
Report Contents
The report contains the following information about each item (after the split) that was changed:
Notes: !
!
254
The following field mappings are default only. You can use the FIELD_DEFNS
parameters to map any column to a different 3890 field. The FIELD_DEFNS parameters
can be changed using Application Generator.
For a summary of what does and does not count as a change, see the description of
the MaxChangesPerBatch parameter (XML_GATEWAY_PARMS keyword).
!
DocType: the document type. Can be Block, Batch, C (credit), D (debit), or NP (non-proof).
!
RecID: the record ID, in hex format (for example, 0x91)
!
CorCD: the correction code, in hex format, plus the correction code mnemonic. The mnemonic
indicates an action to be applied to the non-negotiable item, identified by the host sequence
number (in the POD column) and the TM sequence number (in the DRN column). The
mnemonics are explained in a legend at the end of the report.
!
DRN: the TM sequence number of the item
!
POD: the host document sequence number of the item (in full format)
Chapter 5: Reports
!
Amount: the amount of the item
!
PC: process control
!
ACCT: the account number of the item
!
FLD4: ImageMark field 4.
!
TR: the transit routing number of the item
!
FLD6: ImageMark field 6.
!
SER: the serial number of the item
!
Pkt: 3890 pocket module. This is generated using the following formula:
3890PktModule= 4 * (3890PktEquiv / 6) + 3890PktEquiv + 11
Translation from 7780 pkt to 3890 pkt is done using the FIELD_DEFN parameters.
!
HiLo: H indicates a high-speed flag. L indicates a low-speed flag.
!
CapBnk: the capture bank of the non-negotiable item
!
Commgl: the commingle bank of the non-negotiable item
255
Chapter 5: Reports
256
6
System Maintenance
This chapter describes non-routine procedures that you may need to perform from time to time.
257
Chapter 6: System Maintenance
Managing ImageMark Transaction Manager Hardware
Managing ImageMark Transaction Manager
Hardware
Under certain circumstances, you may be required to turn the hardware on or off.
Powering Off the Hardware
At most ImageMark Transaction Manager sites, you never turn off all the hardware in the system.
(Typically, only the IDTs and TSSs get turned off at night.) However, if you ever have to power down
the whole system, turn off the hardware in the following order to prevent possible data loss and
hardware damage:
1
IDT
2
TSS
3
EPU and ESU
4
Recognition Unit (RU)
5
DS
6
DAP
7
BAP
Caution: Turning off the hardware has complex implications for the system. Never attempt it unless
you are sure you have to.
The servers and workstations follow the same procedure for powering down. To power down the
hardware:
1
Exit all activities and utilities.
2
In Task Manager, choose Security > Sign Off.
The system signs off ImageMark Transaction Manager.
258
3
Shut down Windows.
4
Turn off the computer, monitor, and any other associated hardware (e.g., tape scanner,
transport).
Managing ImageMark Transaction Manager Hardware
Powering On the Hardware
Power on the hardware in the following order to ensure the system will work properly:
1
BAP
2
DAP
3
DS
4
Recognition Unit (RU)
5
EPU and ESU
6
IDT
7
TSS
The servers and workstations follow the same procedure for powering on. To power on the hardware:
1
Turn on the monitor.
2
Turn on the computer and any other associated hardware (e.g., tape scanner, transport).
The system starts up Windows.
3
Log into Windows and ImageMark Transaction Manager.
Note: If you have registered with ImageMark Transaction Manager and log into Windows as user
base or user imadmin, the system will automatically log you into ImageMark Transaction
Manager. The system will then display the ImageMark Transaction Manager Task Manager.
If you are not registered with ImageMark Transaction Manager, the system will display the
ImageMark Transaction Manager Sign-On dialog.
259
Managing the System Environment
Perl Script Interpreter
Under Windows, ImageMark Transaction Manager has adopted the convention of invoking Perl
scripts by filename in order to mimic the behavior of Perl scripts in the Unix environment. If the
Windows Perl script interpreter is not set up on your system, contact Professional Services to set
up the interpreter.
Active Directory
Windows Active Directory is a directory service that manages all the objects (e.g., users, computers,
etc.) in the ImageMark Transaction Manager Windows network environment. It provides data
storage for these objects in the network as well as support for locating and working with them. It has
a logical directory structure (or hierarchy), and is extensible, so objects and attributes can be added
by the user.
Active Directory allows users to log on to different systems using a single account and password to
gain access to them.
For selecting directory objects, Active Directory uses a tool called an Object Directory Picker. See
“Creating a User Account” on page 148 for instructions on how to use the Directory Object Picker.
For more information on Active Directory, go to
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/netdir/ad/active_directory.asp
Active Directory Users and Computers
260
The following lists the basic components of Active Directory:
!
Object: anything in the windows network environment that you want to manage in the Active
Directory. Printers, users, computers, and groups are all examples of objects.
!
Domain: a group of objects that have the same security or user account policy
!
Tree: a hierarchical arrangement of domains in the same namespace
!
Forest: a group of domains that have intrinsic common trust relationship between them (i.e.,
they share the same schema and global catalogue, but have distinct namespaces)
!
Organizational Unit: a container that stores a collection of objects in a domain that share common
system administration policies
!
Site: a topographical location in your network characterized by local, high-speed access links
(each site must replicate Active Directory data from other sites, therefore what constitutes a
“site” in you network is critical)
For information on security using Active Directory, see “Domain Security Requirements” on page
269.
Organizational Units
An Organizational Unit (OU) is a grouping of objects within a domain. An OU acts as a container
storing the objects in the domain. Printers, file shares, users, groups, and applications are all objects
that can be contained in an OU. OUs can be nested, and the OU structure can be the same for all
domains, but they cannot cross domains).
For more information on supporting Organizational Units in ImageMark Transaction Manager, see
“Supporting Different Active Directory Organizational Units” on page 269.
261
ImageMark Transaction Manager Access Security
ImageMark Transaction Manager Access
Security
ImageMark Transaction Manager Access Security is tightly integrated with Windows Active
Directory. Windows uses Active Directory to add accounts and users to the system, and to manage
them once they are on the system.
Managing ImageMark Transaction Manager Accounts
An important component of maintaining your ImageMark Transaction Manager system is the number
of, nature of, and location of the various Windows accounts it uses. Using the Windows Active
Directory service, you can administer these accounts.
The Access Security Server and the uninstallation process do not remove unused ImageMarkgenerated Windows accounts, therefore you must manually remove accounts no longer needed on
the system. Use the Active Directory Users and Computers control panel to clean up these unneeded
accounts.
!
Important: Ensure that accounts you wish to remove are not being used by a remote IDT registered
with another BAP before you remove the account from the system.
The following tables describe the various ImageMark Transaction Manager accounts that are
created during system installation:
imadmin Account
Description
Special Privileges
Account Location
Password Information
IM system
administrator
account.
Member of “IM Domain
Admins” and has
control over the NCR
IM Transaction
Manager OU.
“NCR IM
Transaction
Manager” OU in the
BAP domain.
Password initially set by
master installer.
This account is to be
used by the IM
software installer,
and by IM system
administrator. This
account must be
used to run the IM
database
reinitialization
scripts, and any
other system
administrative or
special scripts.
262
Member of “Informix
Admins”.
Customer will likely
want to apply the
password policy to this
account.
See Note 1.
Local Administrator on
every IM system.
Has full access to all IM
database tables.
Permission to run IM
Transaction Manager
user interfaces.
ncr_gsc Account
Description
Special Privileges
Account Location
NCR support account.
Member of “Informix
Admins”.
“NCR IM
Transaction
Manager” OU in
the BAP domain.
master installer.
Local administrator
on every IM system.
Customer will likely want
to apply the password
policy to this account.
See Note 1.
base Account
Description
Special Privileges
Account Location
IM ‘base’ user.
Granted permission
within IM to run the
user interfaces.
“NCR IM
Transaction
BAP domain.
master installer.
This user account is
used to ‘bootstrap’ the
configuration of a new
installation. The base
user can log in to IM and
can run the base GUI
applications in order to
achieve this.
Needs to be given
login locally
privileges on the
BAP in order to run
the IM operator
interfaces.
See Note 1.
classa Account
Description
Special Privileges
Account Location
IM ‘classa’ user.
Granted file access
permissions on the
BAP to write to the
PARAMETERS
share.
“NCR IM
Transaction
BAP domain.
master installer.
The ‘classa’ user is
typically the IM
parameter analyst, and
has privileges to run
AppGen and to engage
and translate IM
parameters in the
production parameter
area.
263
as.BAPname Account
Description
Special Privileges
Account Location
IM ‘base’ user.
Granted file access
permissions (full
control) to the IM
directory tree on the
BAP.
“<bapname> Site”
OU in the BAP
domain.
Random 12-character
password, set by
installation.
This user account is
used to ‘bootstrap’
the configuration of
a new installation.
The base user can
log in to IM and can
run the base GUI
applications in order
to achieve this.
See Note 2.
Member of the
“<bapname> Site
Admins” group, so can
create/modify account
objects in the
“<bapname> Site” OU.
monitor.hostname Account
Description
Special Privileges
Account Location
IM monitor service
runs under this
account. There is
one such account for
every IM
BAP/DS/DAP and
IDT in the system.
As a member of local
‘IM Services’ group,
is granted file access
permissions (full
control) to the IM
directory tree on all
IM machines.
OU in the BAP
domain.
On the BAP, set by the
master installer. On all
other boxes, a random 12character password is set
by installation of the
monitor package by the
access security server.
See Note 2.
siips_db.DAPname Account
264
Description
Special Privileges
Account Location
Account used by
ImageMark components
to access the database.
This account has its
password changed by
the ImageMark access
security service each
time the AS service
starts. This account and
the password are
passed to ImageMark
applications in an
authenticated,
encrypted exchange
between the AS service,
and the application.
Granted access to
all ImageMark
database tables.
OU in the BAP
domain.
Random 12-character
password, set by
installation.
See Notes 2 and 3.
wm.BAPname Account
Description
Special Privileges
Account Location
IM Workflow
Management
service runs under
this account on the
BAP.
As a member of local ‘IM
Services’ group, is
granted file access
permissions (full control)
to the IM directory tree
on the server on which it
runs.
OU in the BAP
domain.
Random 12-character
password, set by
installation.
See Notes 2 and 3.
cm.BAPname Account
Description
Special Privileges
Account Location
IM Configuration
Management
service runs
under this
account on the
BAP.
granted file access
to the IM directory tree on
the server on which it
runs.
OU in the BAP
domain.
Random 12-character
password, set by
installation.
See Notes 2 and 3.
am.BAPname Account
Description
Special Privileges
Account Location
IM Application
Management
service runs under
this account on the
BAP.
granted file access
permissions (full
control) to the IM
directory tree on the
server on which it runs.
OU in the BAP
domain.
Random 12-character
password, set by
installation.
See Notes 2 and 3.
265
IMNode.hostname Account
Description
Special Privileges
Account Location
IM Node Management
service runs under this
account (BAP/DAP/DS).
Member of local
Administrators
group. The system
needs this account
in order to modify
registry and update
file (hosts.equiv)
located in system
area, as well as to
add domain
accounts to the
local IM Users and
IM Services groups.
OU in the BAP
domain.
Random 12-character
password, set by
installation.
This service is
responsible for updating
the local Informix
‘sqlhosts’ registry
settings, and the
%windir%\system32\driv
ers\etc\hosts.equiv file
needed for Informix
connectivity.
See Notes 2 and 3.
It is also responsible for
keeping the local IM
Users and IM Services
groups in sync with the
access security
registered IM users and
services.
sortsim.hostname Account
Description
Special Privileges
Account Location
IM sort simulator
service runs under
this account
(BAP/DAP/DS,
possibly IDT
instances)
granted file access
runs.
OU in the BAP
domain.
Random 12-character
password, set by
installation.
See Notes 2 and 3.
dbbe.hostname Account
266
Description
Special Privileges
Account Location
IM database backend service runs
under this account
(BAP/DAP/DS)
granted file access
runs.
OU in the BAP
domain.
Random 12-character
password, set by
installation.
See Notes 2 and 3.
xlink.BAPname Account
Description
Special Privileges
Account Location
IM ‘Expert Link’
service runs under
this account on a
BAP.
granted file access
runs.
OU in the BAP
domain.
Random 12-character
password, set by
installation.
See Notes 2 and 3.
This account executes
SNA conversations with a
mainframe.
cycle.BAPname Account
Description
Special Privileges
Account Location
IM ‘Cycle Service’
runs under this
account on a BAP.
granted file access
runs.
OU in the BAP
domain.
Random 12-character
password, set by
installation.
See Notes 2 and 3.
syslog.BAPname Account
Description
Special Privileges
Account Location
IM error logging
service runs under
this account on the
BAP.
granted file access
runs.
OU in the BAP
domain.
Random 12-character
password, set by
installation.
See Notes 2 and 3.
267
pm.hostname Account
Description
Special Privileges
Account Location
IM print manager
runs under this
account on BAP,
DAP, DS.
granted file access
runs.
OU in the BAP
domain.
Random 12-character
password, set by
installation.
See Notes 2 and 3.
advice.BAPname Account
Description
Special Privileges
Account Location
IM Advice Notice
Host Interface
service runs under
this account on
BAP.
granted file access
the BAP.
OU in the BAP
domain.
Random 12-character
password, set by
installation.
See Notes 2 and 3.
This account executes
virtual 3270 terminal
sessions with a
mainframe.
Notes: 1 The rsetup command must be run every time a password changes.
2
This account should never expire or require password changes. If it expires, then the
system will be broken (until it is re-activated).
3
The password length can be controlled by parameterizing the Access Security service.
Password Registry Settings
The access security service parameter ‘PasswordLength’ controls the length of the random
passwords that the access security server creates for the ImageMark service accounts.
The access security server installation sets the access security service parameter ‘PasswordLength’
registry key to a maximum of 12 characters.
268
Supporting Different Active Directory Organizational Units
The default “NCR ImageMark Transaction Manager” OU can be moved and renamed in the Active
Directory. If this is done, then the %IMAGEMARK_DOMAIN_ACCOUNT_CONTAINER% system
environment variable must be updated on the BAP. This particular variable must be within the same
domain as the BAP.
Note: If a subsequent new BAP is installed to the same domain, then the environment variable
would need to be set before running the master install on the new BAP, in order for the new
BAP to use the same OU.
Similarly, if you want to move or rename the default “<BAPHostName>” OU in the Active Directory,
the %IMAGEMARK_SITE_ACCOUNT_CONTAINER% system environment variable must be
updated on the BAP.
Note: As with the previous OU, the environment variable would need to be set before running the
master install on the new BAP if a subsequent new BAP is installed to the same domain.
Domain Security Requirements
Domain security for ImageMark Transaction Manager under Windows is managed by Windows
Active Directory. ImageMark Transaction Manager supports database and workstation relations
depending on the how each database is set up in its Windows domains.
Databases in Same Windows Domain
Access Security supports an ImageMark Transaction Manager installation in which all participating
ImageMark Transaction Manager databases (BAP/DAP/DS) are members of the same pre-existing
Windows domain.
Databases Across Different Windows Domains
Access Security does not support an ImageMark Transaction Manager database server installation
across different Windows domains. This means that the BAP, DAP, and DS servers must all belong
to the same Windows domain. This configuration cannot be supported because a domain account
is created by Access Security that is used by all ImageMark roles to access the database on all
servers.
Multiple BAPs Within Same Windows Domain
Access Security supports an ImageMark Transaction Manager installation into a Windows domain
that is already hosting another ImageMark installation (e.g., two or more ImageMark BAPs coexisting in the same Windows domain).
In order for the Access Security authentication to work, a trust relationship needs to be established
between the domains in question. For example, access security running on the BAP ‘B’ needs to
be able to authenticate the ‘monitor.idtA’ account which exists in domain ‘A’. In this case, a
relationship must be established between domain ‘A’ and domain ‘B’.
Note: Two-way trusts are automatically created by Windows with domains that exist within the same
Active Directory forest.
269
Remote IDT Workstations
Access Security allows you to access remote IDT workstations that are members of a different
Windows domain than the BAP you are working with. For example, if IDT workstations in BAP ‘A’,
reside in domain ‘A’, the workstations can remotely access work hosted by BAP ‘B’ in domain ‘B’.
Windows Accounts and Windows Domains
Access Security shall support an ImageMark Transaction Manager installation in which the
ImageMark Transaction Manager user accounts exist in Windows domain(s) different than that of
the BAP you are working with. However, in order for Access Security to authenticate the accounts,
a trust relationship needs to exist between the domains. See “Multiple BAPs Within Same Windows
Domain” on page 269.
Another component of access security is securing the BAP directories so users from other domains
can be permitted to access the BAP. This is accomplished by using groups to secure the ImageMark
Transaction Manager servers. For information on how to do this, contact NCR Professional Services.
Integrating the Distributed Capture Consolidation Server
The Distributed Capture Consolidation server is a non-ImageMark server that feeds files to the EPA
autorole running on a DS. The consolidation server is not part of the ImageMark Transaction
Manager system and does not use ImageMark Transaction Manager accounts to run services.
To integrate the consolidation server with ImageMark Transaction Manager, you must grant the
consolidation server service privileges to access the %IMAGEMARK_ROOT%\capture directory.
To integrate the Distributed Capture consolidation server with ImageMark Transaction Manager:
1
Place the consolidation server in the same domain as the ImageMark Transaction Manager
system.
2
Run the consolidation service (which runs on the consolidation server and is ultimately the
service that copies files to ImageMark Transaction Manager) under a known domain account.
Note: Depending on what tasks you wish the consolidation service to perform on the system, it may
be necessary to make the domain account a local administrator on the consolidation server.
3
Add the domain account to the ImageMark Services group on each DS that it will write to.
If the consolidation server cannot be put in the same domain (or a trusted domain), then use the
following technique with your accounts:
1
Create a local account on the consolidation server and on each DS with the same username
and password.
2
Run the service under this account.
3
Add the account to the ImageMark Services group on each DS.
The consolidation server mounts the ‘EPU’ share on each DS that it writes to.
270
Managing the Recognition Sub-System
Restarting the Recognition Sub-System
If you notice work backed up at the RSS auto-activity, you can restart the Recognition Sub-System.
To restart the Recognition Sub-System, complete the following steps:
1
2
3
4
Shut down the RSS auto-activity. See “Shutting Down Activities” on page 72.
5
Restart the RSS auto-activity. See “Loading Activities” on page 72.
If this fails to clear the bottleneck, proceed as follows to restart the RSS:
1
Shut down the RSS auto-activity.
2
Use the Windows Services administrative tool to stop the RSS.
The system displays in the unit’s status that it has stopped.
3
In Windows Services, start the RSS.
The unit’s status displays that it has started.
4
In Application Manager, restart the RSS auto-activity.
271
Testing the Recognition Unit
To test the software used by the RSS auto-activity, you can run the Recognition Unit self test utility
(testru). The utility validates that the recognition software is installed and functional and that the
necessary communication channels and processes are working.
While you do not need to run testru regularly, you can use it to identify the source of a problem. It
will help you localize the cause of the problem to either the client application (RSS), the server (RU),
or the network.
To test the Recognition Unit:
1
Log on to the DS as user imadmin.
2
Access the command prompt.
3
Change to the C:\usr\recognition\test directory.
4
Type testru.
The test program returns results for the installed software and Recognition components,
indicating that fields are read successfully. If the fields are not read, an error message will be
displayed.
272
Viewing and Modifying System Capacity
The number of documents that your site can process per day is determined by the capacity settings
that have been made for your DSs and DAPs.
Viewing Capacity Settings
To view the current capacity settings for your system, proceed as follows:
1
2
Change to the %IMAGEMARK_ROOT%\opt\siips\classa directory.
3
View the file dsclassa_prod.sql.
Find the line “maximum volume per DS according to user”.
The value following that line is the current capacity setting for every DS in your system.
4
View the file baclassa_prod.sql.
Find the line “maximum volume per Base AP”.
The value following that line is the current capacity setting for your entire system.
Modifying Capacity Settings
The gen_prod_sql script on the BAP lets you modify the capacity settings for your system.
Considerations for Changing System Capacity
Before using this script, consider the following points:
!
Under some conditions, increasing system capacity may slow system performance.
!
For best performance, each DAP should service no more than 3 DSs. When you run this script,
the value that you enter for maximum volume per DAP should therefore equal 3 times the value
that you enter for maximum volume per DS.
!
For the standard ImageMark Transaction Manager hardware configuration the maximum values
that you enter should not exceed:
!
230,000 documents per DS
!
690,000 documents per DAP
If you want to modify your system capacity but have a different hardware configuration, call your
NCR service provider for assistance.
273
Changing System Capacity
To modify the capacity settings for your system:
1
2
Change to the %IMAGEMARK_ROOT%\opt\siips\classa directory.
3
Run gen_prod_sql.
4
For each server type (i.e., DSs, then DAPs, then BAPs), the system prompts whether you want
to update the minimum values for any of the varchar columns in any of the tables in the database.
If you indicate that you do want to change varchar minimum values, the system will display each
table that includes a varchar column and the current minimum value and ask if you want to
change it.
If you indicate that you do want to change the varchar minimum value for a table, the system
prompts you to enter the new value.
5
For DSs, then DAPs, the system prompts you to enter the maximum volume per server in
thousands of items and displays the current setting.
Enter the appropriate maximum number of documents, in thousands, per server of the specified
type (for example, to specify 120,000 documents, enter 120).
6
The system prompts you to enter the number of DAPs at your site and displays the current
setting.
Enter the number of DAPs at your site.
Implementing Capacity Changes
To make these changes take effect:
1
Run %SIIPS_BASE_MNT%\initialize\reinitall.bank.pl
where bank is the name of your institution.
274
Running the Set Stale Date Script with Task Scheduler
Running the Set Stale Date Script with Task
Scheduler
Since you must run the set_stale_date script against your production sort patterns monthly, you
should automate this task with Windows Task Scheduler. The stale date must be reset prior to
starting ImageMark Transaction Manager on the first day of processing of each month.
The set_stale_date script sets the current date into the IPCS sort patterns. This sets the current
month and year into the sort patterns and ensures that proper date validation is performed against
government-issued checks.
Since you run the set_stale_date script for each sort pattern, you should create a script to automate
running it, and point to that script in the crontab file.
275
Setting Up a Set Stale Date Script for a Regular Environment
To set up a cron job for the set_stale_date script, add the necessary entries to the stale.sh script
and reference it in the crontab file (i.e. crontab -e) to automatically run the stale date script monthly.
To set up the cron job task:
1
Use cp -ip to copy set_stale_date from
%IMAGEMARK_ROOT%\opt\siips\classa\ag_cpcs\userexit or to
\%IMAGEMARK_ROOT%\bin.
2
In the user exit directory in your development directory, create a script called stale.sh.
3
Add the following entry to stale.sh:
\%IMAGEMARK_ROOT%\bin\set_stale_date
%IMAGEMARK_ROOT%\opt\siips\classa\agcpcs\apptype.dev\userexit\stlexit
where:
!
apptype is the Application Type name (the application’s development directory name in
%IMAGEMARK_ROOT%\opt\siips\classa)
!
stlexit is the name of the file that contains the initialization stale dated government check
exit point (for example, ststldat.usr)
This line ensures that the user exit’s date reflects the current date. So, you are not required to
run the script each time you recompile your project.
4
For each application type and bank directory, ensure stale.sh contains the following entries:
%IMAGEMARK_ROOT%\opt\siips\classa\apptype\bank\fld0040
%IMAGEMARK_ROOT%\opt\siips\classa\apptype\bank\cpat0040
where:
5
!
apptype is the Application Type name (the application’s directory name in
!
bank is the bank directory name
Add the following entry to the crontab file:
mm hh dm * * %IMAGEMARK_ROOT%\opt\siips\classa\apptype.dev\userexit\stale.sh
where:
276
!
mm is the time in minutes (0-59) after the hour when you want to set the date
!
hh is the time in hours (0-23) when you want to set the date
!
dm is the day of the month (1-31) when you want to set the date
!
Sample Cron JobTask
The following sample cron job runs the stale.sh script at 4:00 AM on the first day of each month:
0 4 1 * * %IMAGEMARK_ROOT%\opt\siips\classa\waterloo.dev\userexit\stale.sh
By running the script at 4:00 AM on the first day of each month, you ensure that the script is run
before ImageMark Transaction Manager starts and before any items are processed for that month.
The cron job calls the following sample stale.sh script:
\%IMAGEMARK_ROOT%\opt\siips\classa\waterloo.dev\userexit\ststldat.usr
%IMAGEMARK_ROOT%\opt\siips\classa\waterloo\1\fld0040
%IMAGEMARK_ROOT%\opt\siips\classa\waterloo\1\cpat0040
277
Setting Up a Set Stale Date Script for a Time-of-Day Sort
Environment
To set up a cron job for the set stale date script, add the necessary entries to the stale script (stale.sh)
and reference it in the crontab file (i.e. crontab -e) to automatically run the stale date script monthly.
To set up the cron job for a time-of-day sort environment, complete the following steps:
1
Use cp -ip to copy set_stale_date from %IMAGEMARK_ROOT%\opt\siips\classa\ag_cpcs or
%IMAGEMARK_ROOT%\opt\siips\classa\ag_smcr to \%IMAGEMARK_ROOT%\bin.
2
In the user exit directory in your development directory, create a script file called stale.sh.
3
Add the following entry to stale.sh:
%IMAGEMARK_ROOT%\opt\siips\classa\apptype.dev\userexit\
stlexit
where:
!
apptype is the Application Type name (the application’s development directory name in
!
stlexit is the name of the file that contains the initialization stale dated government check
exit point (for example, ststldat.usr).
This line ensures that the user exit’s date reflects the current date. Therefore, you are not
required to run the script each time you recompile your project.
4
For each application type and bank directory, ensure stale.sh contains the following entries:
%IMAGEMARK_ROOT%\opt\siips\classa\apptype\bank\fld0040
where:
5
!
!
For each sort pattern, ensure stale.sh contains the following entries:
%IMAGEMARK_ROOT%\opt\siips\classa\apptype\bank\sp\fld0040
%IMAGEMARK_ROOT%\opt\siips\classa\apptype\bank\sp\cpat0040
where:
278
!
!
!
!
!
!
sp is the sort pattern directory name
6
Add the following entry to the crontab file:
mm hh dm * * %IMAGEMARK_ROOT%\opt\siips\classa\apptype.dev\userexit\stale.sh
where:
!
!
!
!
279
Advice Notice Export Utility
This utility saves each Advice Notice image as a TIFF file and unloads its corresponding data to a
flat file for later viewing and printing on an IDT. Research operators use these files to justify
adjustments to customers’ ATM deposits.
Note: This utility can be run manually so you may print Advice Notices at any time during your work
cycle. You can also configure the start of cycle process to run this utility during the start of
cycle procedures.
There are two files provided to save Advice Notice data as both flat files and TIFF file images:
!
the Advice Notice Export utility (adv_unload.pl)
!
a sample configuration script if no specific configuration file is specified (adv_unload.ini_sample)
Configuring Your System
Step 1: Copy Files
To configure your system to save Advice Notices as both flat files and TIFF files:
1
Copy adv_unload.pl from %IMAGEMARK_ROOT%\usr\bin\ to
%IMAGEMARK_ROOT%\usr\bin\app-type, where app-type is the application directory on your
system (e.g. waterloo).
2
Copy adv_unload.ini_sample from %IMAGEMARK_ROOT%\opt\siips\classa\ to
%IMAGEMARK_ROOT%\opt\siips\classa\app-type\, where app-type is the application type
directory on your system (e.g. waterloo).
3
Rename this new copy of the sample file to adv_unload.ini before proceeding to Step 2 below.
Step 2: Edit Default Configuration file
You need to edit the sample configuration file provided so that:
!
the Advice Notice image files are stored in the right directory
!
all required Advice Notice database columns to unload and select criteria are listed
!
the correct network name and user profile of server (to FTP Advice Notice files) is included
!
the Advice Notice data is retained for as long as your site requires
!
a separate image directory for each PSET number that pertains to advice notices is specified
To include another field, add the ADV_SELECT Column Name for that field to the
ADV_SELECT_COLUMNS section of your new copy of adv_unload.ini. To exclude a field, delete
the ADVICE Column Name from this section.
The following rules apply:
280
!
ADV_SELECT Column Names are not case sensitive
!
ADV_SELECT Column Names must be spelled exactly as given in the Default adv_unload.ini
file (see next page).
Default adv_unload.ini File
#############################################################################
#
#
# Copyright (c) 2006 NCR Corporation
#
# $Source: \cvs\wintm\pod\pod\install\g524-1220\adv_unload.ini,v $
#
# PURPOSE: Sample configuration file for the adv_store.pl utility
#
# $Id: adv_unload.ini,v 1.2.2.1 2005/12/16 20:43:42 ppeles Exp $
#
#############################################################################
#
[General]
# The %IMAGEMARK_ROOT% environment variable may be used to denote the root
directory of ImageMark.
# Advice Notice file unload directory and file name
ADV_UNLOAD_DIRECTORY=%IMAGEMARK_ROOT%\opt\siips\classa\trn_cpcs\advice
ADV_UNLOAD_FILE_NAME=advice
# Advice Notice database columns to unload and select criteria
ADV_SELECT_COLUMNS = advice_ref, proc_date, proc_time, corr_acct_no,
dep_acct_no, dep_slip_amt, corr_amt, corr_class, adj_reason_code,
advice_notice_name, branch_num, teller_num, oper_number, entry_number, state,
advice_comment, item_amt, item_class, first_DRN, adjustment_DRN, lookup_text
ADV_WHERE_CLAUSE =
# Network name and user profile of server to FTP Advice Notice files
# Set ADV_FTP_SERVER = to disable FTP transfer
ADV_FTP_SERVER =
ADV_FTP_ACCOUNT =
ADV_FTP_PASSWORD =
# Number of days to retain Advice Notice Data
ADV_BACKUP_DAYS = 7
# For each PSET number that pertains to advice notices an accompanying image
# directory should be given in order to organize where images are placed.
# Edit to suit your needs.
[1]
DirectoryPath=%IMAGEMARK_ROOT%\opt\siips\classa\trn_cpcs\advices1
[2]
DirectoryPath=%IMAGEMARK_ROOT%\opt\siips\classa\trn_cpcs\advices2
281
Step 3: Run the Advice Notice Export Utility
To configure your system to unload Advice Notice data for each application type:
1
2
Run adv_unload.pl [-f config file] -c cycle num | -t app type
where:
-f config file
Specifies the full path and filename of a configuration file to use instead of the
default configuration file. This file must be of the same format as the default.
-c cycle num
Specifies a specific cycle number to be unloaded. This value must be followed
by a valid Application Type name.
-t app type
Specifies the Application Type name to use for the chosen Cycle number.
The utility:
!
unloads the database columns specified by the comma-separated
ADV_SELECT_COLUMNS entry in the configuration file, and
!
ensures the following columns are always unloaded (even if not specified in the configuration
file):
!
Advice_key
!
Dep_ddr_key
!
App_type_pset_num
!
Advice_ref
!
App_instance_id
Notes: !
To unload all cycles, use the following syntax:
adv_unload.pl [-f config file] -a
!
To display the usage help screen, use the following syntax:
adv_unload.pl -h
!
If you do not specify a configuration file, the utility uses the default, located here:
%IMAGEMARK_ROOT%/classa/app type/adv_unload.ini
!
If you do not specify the application type name, the system uses the default, located
here:
%IMAGEMARK_ROOT%/classa/advice/adv_unload.ini
File Location and Naming
Advice Unload File Format
The advice unload file format is as follows:
ADV_UNLOAD_FILE_NAME.yymmdd.hhmmss
The file format is a pipe separated list in which each line in the file represents one advice record
from the database.
It also filters based on an optional user specified SQL formatted where clause that is the value of
the ADV_WHERE_CLAUSE keyword in the configuration file.
282
The utility then moves the file to the directory specified by the ADV_UNLOAD_DIRECTORY keyword
in the configuration file.
TIFF Files
The system dumps the tiff files to the directories specified or the defaults defined below:
%IMAGEMARK_ROOT%\opt\siips\classa\trn_cpcs\advices1
%IMAGEMARK_ROOT%\opt\siips\classa\trn_cpcs\advices2
The utility names the Advice Notice image files that it creates as follows:
ADV.pset.yyyymmdd.advice_ref.advice_key.page_num.tif
where:
pset
Parameter set (Pset) number.
yyyymmdd
Cycle process date of the adjustment associated with the advice notice.
advice_ref
Unique reference number for the advice assigned by balancing. This number is a
2 digit machine number followed by a six digit sequence number from the adjustment
DRN.
advice_key
Unique, system assigned number serializing each individual advice record.
page_num
Advice image page number (1—N).
Example:
The following Advice Notice image files were created on December 14, 2005. The first three have
the same advice reference number, as do the last two:
ADV.21.20051214.88.21.1.tif
ADV.21.20051214.88.22.2.tif
ADV.21.20051214.88.23.3.tif
ADV.21.20051214.92.17.1.tif
ADV.21.20051214.92.18.2.tif
283
Adding Printers
Adding Printers
Windows allows you to configure printers to work with your existing ImageMark Transaction Manager
installation. You can configure Windows or Network printers. Follow the Windows procedure for
adding printers to configure a printer to your ImageMark Transaction Manager system.
Note: You cannot reconfigure SPOOL or FILE.
In Configuration Manager, add the printer as an external station, specifying a name and IP address.
See “Adding a Station” on page 112.
284
Resetting the System Date and Time
Resetting the System Date and Time
To reset the system date and time:
1
Exit all system applications on all stations.
2
Choose Start > Settings > Control Panel > Date/Time.
The system displays the Date and Time Properties dialog.
Date and Time Properties Dialog
3
Change the date and time as desired, then choose OK.
4
To avoid date and time problems, remove the following files on the BAP, DAPs, and DSs:
%IMAGEMARK_ROOT%\etc\inet\siips.hosts
%IMAGEMARK_ROOT%\etc\inet\siips.rev
5
Reboot the BAP, DAPs, DSs, EPUs, ESUs, and EPSUs, in that order. See “Managing
ImageMark Transaction Manager Hardware” on page 258 for more information on rebooting the
system and its components.
6
The system date and time is now changed.
285
Procedures for Distributed Capture
If your system has Distributed Capture, you may need to occasionally perform the following
procedures.
Caution: While the following procedures can be run at any time, ensure that they are necessary
before running them to avoid any unnecessary loss of data.
Validating Cycles
A daily system administration task is to create the processing day’s cycle, and thereby ready
ImageMark Transaction Manager to accept work.
Within Distributed Capture, parameters have been included to control the number of valid weekly
posting dates, as well as a series of scripts to control a file listing invalid posting dates. The relevant
scripts are stored in \%IMAGEMARK_ROOT%\bin and have the following descriptive names:
!
imloaddates
!
imdeletedates
!
imdisplaydates
imloaddates
This script is used to load invalid dates into the ImageMark Transaction Manager databases (i.e.,
XXCLASSA):
imloaddates [-d database] -f filename | -p postingdate
where:
-d database specifies the location of the Invalid Cycle table (i.e., XXCLASSA)
-f filename specifies a filename that stores a list of invalid posting dates. Cannot be used in
conjunction with the -p parameter.
-p postingdate specifies a single invalid posting date. Cannot be used in conjunction with the -f
parameter.
imdeletedates
This script removes dates from the invalid posting date listing:
imdeletedates [-d database] -f filename | -p postingdate | -t older than
where:
-f filename specifies a filename that stores a list of invalid posting dates to delete. Cannot be used
in conjunction with the -p or -t parameters.
-p postingdate specifies a single invalid posting date to delete. Cannot be used in conjunction with
the -f or -t parameters.
-t older than specifies the number of days older than today to delete. Cannot be used in conjunction
with the -f or -p parameters.
286
imdisplaydates
This script will display all current invalid posting dates within the ImageMark Transaction Manager
system.
imdisplaydates [-d database]
where:
Replacing Corrupt EIPS Files on the DS
If EPA is unable to import a capture file from an ECU because the file is corrupt, it is possible to
retrieve the file from the ECU as long as the ECU has not been freed and initialized for the next
processing day. If the ECU has been freed and initialized, you will be unable to copy the file, as part
of the initialization process is to delete the image capture files on the ECU.
The process to complete this file replacement is outlined below:
1
Map a network drive to the ECU from the CS.
Note: Each ECU must be set up to share its primary drive with administrators.
2
Select the folder C:\ib\Innovaconnect\export\branch on the ECU.
3
Create a copy of the required capture file within the current folder.
Note: The file name must not conform to the required EPA Import filename syntax.
4
Move the copied capture file from the ECU to the EPA Import directory on the DS.This is done
to prevent EPA from attempting to import the file while it is being transferred to the DS.
5
Rename the capture file to
eips.priorityYYYYMMDD.HHMMSS.branch.tranport.pset.run.batchseq
EPA will then attempt to import the file.
287
Changing Host Entry # for a Duplicate Host Entry
Normally, after an entry is balanced, the BIE auto-activity sends the corresponding balanced I-string
to the host application. However, sometimes you must resend the work because your entry has the
same number as one already received by the host.
If the host recognizes the entry number during the BIE transmission attempt, it refuses the work.
Because the work is not successfully sent to the CPCS host application, it is held at BIE. To ensure
the entry is uploaded to the CPCS host application, the entry number must be modified to be unique
for the host system, and resubmitted through BIE.
To ensure the assigned host entry number is unique, we recommend using an entry number from
a physical tracer document set selected at the EPU area. Selection and assignment of an entry
number from within the defined parameter range for entry numbers cannot guarantee uniqueness
as EPA assigns entry numbers from this range to imported capture runs.
To ensure that a unique host entry number is assigned with each reassignment process:
1
2
3
4
Choose Cycles > Host Entry.
The system displays the Host Entry Number dialog, which contains a list of the currently defined
cycles.
288
Host Entry Number Dialog
5
Select the cycle for the entry that is being held at BIE.
The system displays a list of the Capture entries for the selected cycle.
6
Select the Capture entry for the CPCS entry that you want to modify, then choose Change.
The system displays the New Host Entry Number dialog.
New Host Entry Number Dialog
7
Obtain a new set of tracer documents from the EPU area with an unused entry number.
8
Type the new number for the CPCS entry, then choose OK.
9
10 Discard the physical tracer documents.
!
Important: Do not replace the original tracer documents with the new tracer documents. Ghost
tracer documents with the new host entry number will be generated at BIE and SIE.
289
Cleaning Up Capture Files on the DS
Capture files are transferred from the Consolidation Server to ImageMark Transaction Manager’s
Data Server. There is no need to retain the physical capture files on the DS once they have been
imported into the ImageMark workflow.
To remove the imported capture files, Transaction Manager provides a clean-up script called
epa_cleanup.pl. This script is installed to \%IMAGEMARK_ROOT%\bin on all Data Servers.
The cleanup script reads a configuration file called epa_cleanup.cfg which contains a list of all the
folders from which capture files are cleaned up. A sample cleanup script called
epa_cleanup.cfg.sample is installed to \%IMAGEMARK_ROOT%\opt\siips\classa\epa.ext on the
BAP.
In order for the cleanup script to work on the Data Servers, the configuration file must be:
!
copied from the BAP folder \%IMAGEMARK_ROOT%\opt\siips\classa\epa.ext to the BAP folder
\%IMAGEMARK_DATA%\opt\siips\classa\epa.ext
!
renamed from epa_cleanup.cfg.sample to epa_cleanup.cfg
Cleanup as a Scheduled Task
When the TM packages are installed on the DS, a scheduled task called "Delete imported capture
files" is automatically created which runs the epa_cleanup.pl script once per day at 11 pm.
Command Line Option
You can also run the clean-up script from the command line using the following syntax:
epa_cleanup [-c config file] [-d directory] [-t days] -f
where:
-c config file names an alternate configuration file listing the directories to clean up. Cannot be used
in conjunction with the -d parameters.
-d directory names a specific directory for cleanup. Cannot be used in conjunction with the -c
parameter.
-t days specifies how many days old must imported files be to be deleted.
-f bypasses a system check to make sure the script is only run on a DS.
290
Cleaning Up Files on the Transports
Automatic Daily Cleanup
During each day’s operations, files are created on the transports that are only needed that day. At
the start of the next day, the system automatically cleans up (removes) files as needed using the
following script:
eips_cleanup.pl
This script runs automatically:
!
on the EPU, at the start of every entry
!
on the ESU, at the start of every new run
Manual Cleanup
In case you need to run a clean for any reason, the following utility is available:
cleanxprt.pl
This utility saves the files it cleans to \cleanxprt with a date and time stamp.
EPU Cleanup
To start a manual cleanup on the EPU:
1
Click Start, Run.
2
Type cmd.
The system displays a DOS window.
3
Enter the following lines:
cd \Imagemakr\bin
cleanxprt epu
ESU Cleanup
To start a manual cleanup on the ESU:
1
Click Start, Run.
2
Type cmd.
The system displays a DOS window.
3
Enter the following lines:
cd \Imagemakr\bin
cleanxprt esu
291
Administration Tasks for a Server Cluster
ImageMark Package Version Monitoring
On every server, ImageMark 4.2.1 installs a new scheduled task called “ImageMark Package Version
Monitoring”. This task runs once per hour and reports the name, LPIN and version number of every
ImageMark package installed on that server to this location:
\\bapname\PARAMETERS\base\pkgs\pkg_hostname.txt
Review these files to quickly determine the version numbers of all ImageMark packages installed
on every server.
When ImageMark 4.2.1 is installed on a Windows Server 2003 Cluster, the “ImageMark Package
Version Monitoring” task:
292
!
automatically raises a diagnostic alert when it detects a package version discrepancy
!
writes the package information from both nodes in the cluster to the version file (the package
information for each server is preceded by a section identifier [nodename])
Setting Up Diagnostic Alerts for a Server Cluster
When installed to a server cluster, the Node Monitor Service performs a new function of monitoring
events in the cluster. By editing the configuration file clusevnt.dat, you can configure the Node
Monitor to report any number of different cluster events as ImageMark diagnostic alerts.
The default clusevnt.dat file includes the following explanations of the format of each message line:
#Event Parameter file
# '#' sign is used to comment the line
#syntax:
#<EventID>,<Source>,<State>,<Severity>,<Message>
#(A)EventID: Bitmask of flags that describes the Group/Resource events to cause
notifications. Following predefined event ID values shall be used:
#CLUSTER_CHANGE_GROUP_ADDED
#CLUSTER_CHANGE_GROUP_DELETED
#CLUSTER_CHANGE_GROUP_STATE
#CLUSTER_CHANGE_RESOURCE_ADDED
#CLUSTER_CHANGE_RESOURCE_DELETED
#CLUSTER_CHANGE_RESOURCE_STATE
#A sample parameter file shall be provided to customer that shall contain sample
#event parameter records commented
#(B)Source: The name of the Group/Resource object that will trigger the event
#(C)State: This is an optional value and to be mentioned only when Group/Resource
event is a state type event.
#State value with non-state type event shall be ignored by Monitoring thread
#Following predefined state values have to be used. Event parameters with state
value other than mentioned below shall be ignored. Blank state value would mean
all state changes for the respective Group/Resource will be notified to siips log.
#(C.1)Group States
#
#State ValueDescription
#FailedAt least one resource in the group has failed.
#PendingAt least one resource in the group is in a pending state. There are no
failed resources.
#OnlineAll of the resources in the group are online.
#PartialOnlineAt least one resource in the group is online. No resources are
pending or failed.
#OfflineAll of the resources in the group are offline or there are no resources
in the group.
#
#(C.2)Resource States
#State ValueDescription
#InitializingThe resource is performing initialization.
#OnlineThe resource is operational and functioning normally
#OfflineThe resource is not operational.
#PendingThe resource is in the process of coming online or going offline
#OnlinePendingThe resource is in the process of coming online.
#OfflinePendingThe resource is in the process of going offline.
293
#
#State values of Group/Resources shall be case-insensitive.
#(D)Severity: Severity Level shall be mentioned from 0 to 6 where 0 is a fatal
down to 6 is information only.
#(E)Message: Customized messages to be logged if the respective resource changes
to the respective state for the respective event type.
This is followed by several sample message lines (all commented out):
#Example parameter records of clusevnt.dat:
#
#
#CLUSTER_CHANGE_RESOURCE_STATE, BINARIES Share,Failed,0,Client may not access
classa tools.Repair BINARIES share
#CLUSTER_CHANGE_GROUP_DELETED,ImageMark,,0,ImageMark Group Deleted..Help!!
#CLUSTER_CHANGE_GROUP_STATE,ImageMark,,1,ImageMark Group is offline!
#CLUSTER_CHANGE_RESOURCE_ADDED,Capture Share,,6 ,CAPTURE Share, added.
#CLUSTER_CHANGE_RESOURCE_DELETED,Parameters share,,0,CAPTURE Share deleted.
#CLUSTER_CHANGE_RESOURCE_STATE,Capture share,online,0,CAPTURE Share is online.
#CLUSTER_CHANGE_RESOURCE_STATE,Capture share,offline,0,CAPTURE Share is
offline.
CLUSTER_CHANGE_RESOURCE_STATE,ImageMark Transaction Manager Database BackEnd
Service,online,6,Capture db service is online
#CLUSTER_CHANGE_RESOURCE_STATE,ImageMark Transaction Manager Database BackEnd
Service,offline,6,Capture db service is offline
#CLUSTER_CHANGE_RESOURCE_STATE,scheduled tasks,online,6,scheduled tasks are
online
#CLUSTER_CHANGE_RESOURCE_STATE,scheduled TASKS,offline,6,scheduled tasks are
offline
#CLUSTER_CHANGE_RESOURCE_STATE,ImageMark Monitor Service,offline,6,monitor
service is offline
#CLUSTER_CHANGE_RESOURCE_STATE,ImageMark Monitor Service,online,6,monitor
service is offline
Each message line configures one error log message for one cluster event, and includes five commaseparated elements, in the following format:
<EventID>,<Source>,<State>,<Severity>,<Message>
To customize this file for your site, you can add one or more messages to the end of the file using
this syntax, or uncomment one or more of the sample messages.
294
Starting and Stopping ImageMark Services
On an ImageMark server cluster, one server is designated the owner of the server cluster. This is
called the active node server.
When you start ImageMark for the cluster, you must do so from this server. Task Manager will not
run from any other server in the cluster.
When installed on a Server Cluster, ImageMark services are managed as cluster resources by the
Cluster Service. In a cluster, you start ImageMark services by bringing the corresponding cluster
resource online, and you stop them by taking the corresponding cluster resource offline. You cannot
start ImageMark services in a cluster directly via the Service Control Panel.
To take ImageMark services online or offline in a server cluster:
1
Enter the following at a command prompt on the active node server:
cluadmin.exe
The system displays the Cluster Administrator window.
2
Right-click the cluster resource you want to start or stop.
The system displays a popup menu.
Taking ImageMark Services Online and Offline in a Server Cluster
3
Choose Bring Online or Take Offline.
The system starts (or stops) ImageMark Services for the selected cluster resource.
Note: If the selected cluster resource is online, only the Take Offline option is available. If the
resource is offline when selected, only the Bring Online option is available.
295
Managing Scheduled Tasks
On a clustered ImageMark server, all scheduled tasks are now managed by a cluster resource called
Scheduled Tasks.
You can use this resource to shutdown tasks on one server and startup tasks on another if there is
a server failure.
To take the scheduled tasks resource offline for a server, enter the following at the server’s command
prompt:
siipsbase stop
To put the scheduled tasks resource back online for the server, enter the following at the server’s
command prompt:
siipsbase start
296
7
Backup, Restore, and Recovery
Procedures
This chapter gives instructions for the following tasks:
!
creating a backup of the file systems from the station to tape
!
resending work to the host application
!
recovering from duplicate entry numbers
!
restarting the host link
!
performing a restore of the file systems from the backup tapes to the station
297
Chapter 7: Backup, Restore, and Recovery Procedures
Creating a Backup of Stations
Make tape backups of all stations for the following reasons:
!
Tape backups can save you a great deal of time. If a station’s storage devices fail, you can
restore its files from tape, instead of having to do a complete reinstallation from the original
media.
!
Tape backups provide additional protection if both hard disks on a station fail.
!
Tape backups can be stored off-site to protect against disasters such as fire or flooding.
Note: NCR does not recommend a separate backup procedure for the Windows-based stations
(IDTs and TSSs). If one of these stations fails, it is more practical to do a complete
reinstallation from the original media, or a ghost image.
NCR recommends that you create a backup of your ImageMark Transaction Manager Windowsbased stations according to the instructions shown in the following two tables:
Recommended Backups for BAP
Station
When to Backup
What to Backup
BAP
After initial installation
\%IMAGEMARK_ROOT%
%IMAGEMARK_ROOT%\opt\siips
298
Whenever you add, update, or delete a
software package
\%IMAGEMARK_ROOT%
Whenever you make configuration
changes (such as adding new stations or
users or changing the servers from which
stations obtain services)
\%IMAGEMARK_ROOT%
Whenever you install a new set of
parameters
\%IMAGEMARK_ROOT%
Whenever you modify an existing set of
parameters
%IMAGEMARK_DATA%\opt\siips
Recommended Backups for Other Stations
Station
When to Backup
What to Backup
DAP
\%IMAGEMARK_ROOT%
software package
DS
\%IMAGEMARK_ROOT%
software package
EPU/ESU
\%IMAGEMARK_ROOT%
software package
RU
\%IMAGEMARK_ROOT%
software package
Creating a Backup of File Systems
The backup procedure should be performed at the start of the cycle, after you have rebooted the
servers and clients, but before you have restarted the system. This helps to ensure that you get
clean copies of these databases. See Chapter 2, “Application Manager,” for the complete start-ofcycle procedure.
Note: You may wish to perform the backup procedure twice for each station: once to create a set
of backup tapes for on-site storage, and again to create a duplicate set for off-site storage.
299
Resending Work to the Host Application
It may be necessary to resend Balanced Item Export (BIE) or Sub-Pass Item Export (SIE) units-ofwork to the host application. In an ATM workflow, where EIE is used to send an Encoded Item Export
to the host, it may be necessary to resend EIE units of work. While work may successfully transmit
to the host during BIE, SIE, or EIE, the host may lose the I-string for some reason.
In ImageMark Transaction Manager, you can run the resend command line utility to retransmit the
work to the host application (replaces the resenditemexport utility). The utility creates a copy of the
lost I-string and retransmits it to the host application from BIE, SIE, or EIE. Upon successful
completion of the transmission, BIE, SIE, or EIE deletes the duplicate I-string.
The resend utility doesn't create a key. Instead, you must identify the work you want to be resent,
via it's key. That is because two entries in the system might have the same entry number (an EPU
entry and a 3890 entry). The entry key will uniquely identify which entry you want to resend.
Note: The resend can only complete if the utility determines that a Balanced Item Export, Sub-Pass
Item Export, or Encoded Item Export has been generated for that I-string.
The units-of-work corresponding to the resent I-strings are identified by an ‘R’ flag in the Export Log
dialog in Application Manager. You can also view the status of work sent to the host application.
See “Viewing Work Export Status” on page 85.
To display usage instructions for the resend utility, type the following at the command prompt:
resend.pl
Resending a String Using a Different Host Cycle Number
Use this method to resend any of the following:
!
a Sub-Pass I-string (SIE)
!
a Balanced I-string (BIE)
!
a Prime I-string (PIE)
!
a Modified I-string (MIE)
1
Unload the autorole (BIE or SIE).
2
Modify the CYCLE_OVERRIDE value in the corresponding control file (bie_pod.lst or
sie_pod.lst).
3
Resend the unit of work to the host (see next few pages).
Note: To display the syntax for the resend script at any time, enter
$ resend -h
The system displays the following:
Usage : C:\Imagemark\bin\resend.pl [BIE|PIE|MIE] -e EntryKey Usage :
C:\Imagemark\bin\resend.pl [SIE|EIE] -t TraySetID Usage :
C:\Imagemark\bin\resend.pl -H
4
300
Reload the autorole.
Recovering from a Lost BIE Entry on the Host
If the CPCS or SuperMICR host loses your BIE entry (or your 00-M string from a 3890-captured
entry), you can resend the work.
Note: To display the syntax for the resend script at any time, enter $ resend -h
The system displays the following:
Usage : C:\Imagemark\bin\resend.pl [BIE|PIE|MIE] -e EntryKey Usage :
C:\Imagemark\bin\resend.pl [SIE|EIE] -t TraySetKey Usage :
C:\Imagemark\bin\resend.pl -H
To recover lost BIE data:
1
From the Application Display window of Application Manager, choose View > Work In Progress.
2
3
Select the Entry unit-of-work (that is to be resent to the host) from the list, then choose UoW
Details.
301
UoW Details Dialog
4
5
On the BAP, open a command prompt and type the following:
resend BIE -e EntryKey
where EntryKey is the number you obtained from the Unit of Work Details screen.
302
6
If you have more than one active application instance, when prompted, select the application
instance the entry was captured in.
7
When prompted, type y to verify that you want to send a Balanced I-string for the specified entry
and pocket history.
Recovering from a Lost SIE Transmission to the Host
If the CPCS or SuperMICR host loses your SIE string upload, you can resend the work.
To recover from a lost SIE transmission to the host:
1
2
For the Unit of work type, choose Tray Set.
The system displays only the Trayset units of work in the table.
3
Select the Trayset unit-of-work (that is to be resent to the host) from the list, then choose UoW
Details.
303
UoW Details Dialog
4
Note the Trayset ID displayed on this screen.
5
On the BAP, open a command prompt and type the following:
resend SIE -t TraySetID
where TraySetID is the number you obtained from the Unit of Work Details screen.
304
6
instance the trayset was captured in.
7
When prompted, type y to verify that you want to send a Sub-Pass I-string for the specified
trayset and pocket history.
Recovering from a Lost EIE Entry on the Host
If the host loses your entry, you can resend the work.
To recover from a lost EIE entry on a host:
1
2
Select the Input Processed Trayset unit-of-work (that is to be resent to the host) from the list,
then choose UoW Details.
305
UoW Details Dialog
3
Note the Trayset ID displayed on this screen.
4
Run resend EIE -t TraySetID
where TraySetID is the number you obtained from the Unit of Work Details screen.
306
5
instance the tray set was captured in.
6
When prompted, type y to verify that you want to send an Encoded Item Export for the specified
tray set and pocket history.
Recovering from a Lost PIE Entry on the Host
To recover from a lost PIE entry on a host:
1
Progress.
2
3
Details.
307
UoW Details Dialog
308
4
5
On the BAP, open a command prompt and type resend PIE -e EntryKey
6
7
8
When prompted, type y to verify that you want to send a Prime Item Export for the specified
entry and pocket history.
Recovering from a Lost MIE Entry on the Host
To recover from a lost MIE entry on a host:
1
Progress.
2
3
Details.
309
UoW Details Dialog
4
5
On the BAP, open a command prompt and type resend MIE -e EntryKey
310
6
7
When prompted, type y to verify that you want to send a Prime Item Export for the specified
entry and pocket history.
Recovering from Duplicate Entry Numbers
Recovering from Duplicate Entry Numbers
Normally, after an entry is balanced, the BIE auto-activity sends the corresponding balanced I-strings
(CPCS) or primary job upload (SuperMICR) to the host application. However, sometimes you must
resend the work because your entry has the same number as one already received by the host.
If the host recognizes the entry number during the BIE transmission attempt, it refuses the work.
Since the work is not successfully sent to the host application, it is held at BIE.
Recovering from Duplicate CPCS Entry Number
In a CPCS environment, if the Diagnostic Interface displays a message stating that your Host entry
duplicates one already received by the host, do the following to resend the work:
1
Change the CPCS host entry number. See “Changing the Host Entry Number” on page 57.
2
Take the Unit-of-Work off hold so that BIE can send it again. See “Holding Back Work” on page
39.
Recovering from Duplicate SuperMICR Entry Number
In a SuperMICR environment, if Diagnostics displays a message stating that your Host entry
duplicates one already received by the host, do the following to resend the work:
1
2
Do one of the following to correct the problem on the SuperMICR host:
!
If the duplicate entry number is the result of a failure to run the first run-of-the-day procedures
on the SuperMICR host, ensure that those are now run.
!
If the duplicate entry number is the result of a communication failure, delete the entry from
the SuperMICR host.
Take the Unit-of-Work off hold so that BIE can send it again. See “Holding Back Work” on page
39.
311
File Recovery for IDT and TSS Workstations
File Recovery for IDT and TSS Workstations
ImageMark Transaction Manager does not provide special facilities for making a backup or
performing a restore for the two types of Windows-based system stations: IDTs and TSSs.
In the event that the files on one of these stations become corrupted, perform a complete
reinstallation.
312
Restarting Host Link
The ImageMark Transaction Manager platform software includes the following components that
provide the link to your host:
!
IBM SNA Toolkit software
!
Expert Link
Note: Expert Link is a service under Windows.
If your host link goes down, you may see a variety of messages in Diagnostics, such as “ExpertLink
halted”.
To restart the host link, you must stop and restart all of the above software components and services
and the ImageMark Transaction Manager auto-activities that work with them.
To restart the host link, complete the following steps:
1
2
3
4
In the Application Display window for the current instance, choose Maintain > Activities.
The system displays the Activities dialog, which lists the auto-activities in this instance.
313
Activities Window
5
In the Auto Activity list, select each active occurrence of Balanced Item Export (BIE) and Subpass Item Export (SIE).
6
Choose Shutdown.
7
The status changes to Terminating and then to Not Running.
8
If any occurrences fail to change to Not Running, select them and choose Unload.
9
Use the Windows Services administrative tool to make sure that the Expert Link service is
stopped.
!
If Expert Link is not stopped, use the Windows Service tool to stop it.
The system displays in the unit’s status that it has stopped.
10 Access the command prompt.
11 Enter the following commands to make sure that the IBM SNA software are stopped:
%IMAGEMARK_ROOT%\opt\siips\prodsna stop
12 To restart the IBM SNA software, type %IMAGEMARK_ROOT%\opt\siips\prodsna start
13 To restart Expert Link, use the Windows Services administrative tool.
The unit’s status displays that it has started.
14 Return to the Application Manager Activities dialog.
15 To restart the auto-activities that you stopped before, select each one, then choose Load.
314
Performing a Restore of Stations
The procedures for restoring stations depends on which server is being restored.
For the BAP:
1
Restore the file system.
2
Import the system databases.
For all other stations:
1
Restore the file system.
Importing the BAP Databases
The following procedures describe how to restore databases to the system:
1
2
3
Stop Capture processes:
a
Ensure that no one is signed onto any of the IDT, ESU, EPU or the TSS stations.
b
Stop the ImageMark Transaction Manager Base Services by typing
%IMAGEMARK_ROOT%\etc\init.d\siipsbase stop
Stop then restart Database Manager:
a
Stop Database Manager by typing %IMAGEMARK_ROOT%\etc\init.d\on7 stop
b
Restart Database Manager by typing %IMAGEMARK_ROOT%\etc\init.d\on7 start
Import the siips_base database:
a
Type dbimport siips_base -l -i %IMAGEMARK_ROOT%\home\siips_db
where:
!
-l specifies unbuffered transaction logging for the imported database (the system requires
unbuffered transaction logging)
!
-i specifies the directory to import to (if necessary)
Importing the wf# Database(s)
4
Determine the wf# database instances:
a
Run dbaccess.
b
Choose Query.
c
Select siips_base from the list.
d
Type the sql command select wfinstanceid from wfinstance.
The wf# databases will be listed.
5
For each instance of wfinstance, import the wf# database:
dbimport wf# -l -i %IMAGEMARK_ROOT%\home\siips_db
where # is the wfinstance number.
315
Restarting Capture Processes
6
316
Restart all the ImageMark Transaction Manager Base Services that you stopped earlier by typing
%IMAGEMARK_ROOT%\etc\init.d\siipsbase start.
8
Troubleshooting
This chapter tells you how to use the Diagnostics application, and the ImageMark Transaction
Manager central error log files on the system to troubleshoot problems with your ImageMark
Transaction Manager system.
317
Chapter 8: Troubleshooting
Starting Diagnostics
Starting Diagnostics
Diagnostics allows you to view Alert and Error messages in the ImageMark Transaction Manager
error log files (%IMAGEMARK_ROOT%\var\adm\usererr\asiips). While other error types are logged
in the ImageMark Transaction Manager error log file, only Alert and Error types are displayed in
Diagnostics.
To start Diagnostics from the Task Manager, choose Diagnostics from the Utilities list.
The system displays the Diagnostics window.
Diagnostics Window
Start this application at the beginning of the processing day and leave it on during item processing.
This way messages generated by the system will display right away, and any necessary action can
be taken.
Note: The Diagnostics application does not log ECU errors.
The Messages button, on the right of the dialog, flashes when Diagnostics receives new messages.
You can click on this button at any time to refresh the message display.
Note: Diagnostics initially displays Alerts only, but you can filter messages. See “Filtering
Messages” on page 319.
318
Filtering Messages
Filtering Messages
This section describes the ways in which you can filter messages in Diagnostics.
Filtering Messages by Date
To filter messages by their date:
1
Choose Messages > Select Date.
2
Select a date from the drop-down menu.
The system filters the messages by the selected date.
Filtering Messages by Type
To filter messages by their type:
1
Choose View > Type.
2
Select the type of messages you want to view.
The system filters the messages by the selected type.
Filtering Messages by Station
To filter messages by station:
1
Choose View > Station.
The system displays the Station dialog.
Station Dialog
2
Select the station whose messages you wish to view, then choose OK.
The system filters the messages by the specified station.
319
Filtering Messages
Filtering messages by Time
To filter messages by the time in which they were logged:
1
Choose View > Time.
The system displays the Time dialog.
Time Dialog
2
Select Set time range.
3
Enter the desired time range, using 24 hour clock form, in the Hour and Minute fields, then
choose OK.
The system filters the messages by the specified time.
320
Viewing Message Details
There are several areas where information can be found about a particular message.
Summary Content
The first, and most obvious place to learn about a messages is by reading the information given in
the Summary column of the Diagnostics window. This provides a general description of the problem.
Alert and Errors Summary
Displaying More Details
You can display more technical information, including details about which process failed. For some
messages, Diagnostics provides steps to fix the problem.
To view messages in more detail:
1
Select the message, then choose Messages > Details.
The system displays the Details dialog.
321
Details Dialog
2
For information on how to fix the problem, choose Help.
The system displays the Help dialog for the selected message.
Help Dialog
322
Acknowledging Messages
Acknowledging Messages
To acknowledge messages that you have already viewed, or addressed:
1
Highlight the message(s) you would like to acknowledge, and choose Messages >
Acknowledge.
An ‘A’ displays next to the selected message(s) under the Acknowledged column.
Acknowledged Messages
2
To acknowledge all messages at once, choose Messages > Acknowledge All.
An ‘A’ displays next to all of the messages under the Acknowledged column.
323
Printing Messages
Printing Messages
To print selected messages:
1
Select the message(s) you would like to print, then choose Messages > Print....
The system displays the Print dialog.
Print Dialog
2
Select the printer you wish to print the message(s) to, then choose OK.
The system proceeds to print the selected message(s).
324
Configuring Notification
Configuring Notification
To change the interval at which Diagnostics looks for new messages in the system error logs, or to
set the audible alarm on/off:
1
Choose Messages > Notify Option....
The system displays the Notify Options dialog.
Notify Options Dialog
2
Type the interval time period you would prefer.
3
Select or clear the Audible Notification check box to turn the new message audible alarm feature
on or off, then choose OK.
The system proceeds to configure notification to the specified alert interval and alarm setting.
325
Troubleshooting Freeing and Initialization
Troubleshooting Freeing and Initialization
During your start-of-cycle procedures, you may run into problems that require troubleshooting.
ImageMark Transaction Manager supports combination box configurations of a combined
BAP/DAP/DS or a combined BAP/DAP.
While running, freeall (the script that frees the storage space) initsrv (the script that initializes the
databases one at a time) may generate some of the following errors:
!
If there is not enough disk space available, initsrv will exit with a message that informs you that
more than 10% disk space must be available.
!
If you attempt to free a storage space while an application is still running on it, the script will exit
with a message that informs you that the storage space could not be freed because a cycle is
still active. You must end the cycle first before freeing the storage space.
Each time a storage space return a status of “Freeing Failed” in the Free Storage Space dialog, the
Summary column displays the reason for the failure. Depending on the error message, you may be
able to fix the problem and perform the freeing process again.
The freeing scripts save errors and status messages to an output log file in the server’s root directory
%IMAGEMARK_ROOT%\free.servername.storagenumber.out, where:
!
servername refers to the name of the server (e.g., bap01a)
!
storagenumber refers to the number assigned to the storage space.
Each time a storage space returns a status of “Initializing Failed”, the Summary column in the
Initialize Storage Space dialog displays the reason for the failure. Depending on the error message,
you may be able to fix the problem and perform the initialization again.
The initialization scripts also save errors and status messages to an output log file in the server’s
root directory %IMAGEMARK_ROOT%\init.servername.storagenumber.out, where:
!
servername refers to the name of the server (e.g., bap01a)
!
storagenumber refers to the number assigned to the storage space.
When you are freeing and initializing a storage space, the output log file(s) are scanned for possible
errors, and the appropriate status is displayed.
Note: Before the freeing and initialization scripts exit, they will save a copy of the output files to the
%SIIPS_BASE_MNT% directory, which is mapped to the %IMAGEMARK_ROOT%\opt\siips
directory on the BAP.
If you cannot fix the error, write down the messages appearing in the output log file, then contact
NCR Support.
326
Reading Capture Error Log Files
Whenever any of the ImageMark Transaction Manager subsystems encounters an error, it sends a
message to a central error log file. This file resides in a subdirectory on the BAP.
Each message tells you which subsystem the error occurred on and which software packages it
relates to, thus making it relatively easy for you to narrow down the source of a problem.
This section:
!
explains where to find the error log files
!
describes how to read the messages in these files
!
gives some advice on how to troubleshoot with error messages to decide what corrective action
to take
Where to Find ImageMark Transaction Manager Error Log
Files
ImageMark Transaction Manager maintains eight error log files: one for the current day, and seven
for the seven preceding days. They are all kept in the %IMAGEMARK_ROOT%\log directory on the
BAP.
Current Error Log Filename
The ImageMark Transaction Manager error log file for the current day is named siips.
History Error Log Filenames
Each of the seven error log history files has a numeric suffix (asiips.1 to asiips.7.) That is, today's
error file is called siips, yesterday's error file is called asiips.1, and the error file for this day in the
previous week is called asiips.7.
At the beginning of every data processing day ImageMark Transaction Manager creates a new
(current date) error log file (asiips) and increases the numeric suffixes of the error history files by
one. That is, asiips becomes asiips.1, asiips.1 becomes asiips.2 and so on.
Check the file date and time stamp to determine which error log file is valid for any particular date.
Reading Error Log Files
The most recent errors are located at the end of the error log file, the oldest at the beginning.
You can also use Diagnostics, described earlier in this chapter, to view only alert and error severity
category error messages. See “Severity Codes” on page 330 for a description of ImageMark
Transaction Manager severity codes.
Below is a typical message from the ImageMark Transaction Manager error log file with all the parts
of this message identified. The tables following the diagram describe each of these parts in more
detail.
327
Sample Message From ImageMark Transaction Manager Error Log File
Error Message Components
The following table describes each of the components of an ImageMark Transaction Manager error
log message.
ImageMark Transaction Manager Error Message Components
328
Error Message Component
Description
Date and time
Date and time that the error message was
produced.
Subsystem name
The name of the ImageMark Transaction Manager
subsystem that produced the message.
Originating process name
Name of the software program that is generating
the error message. May also include the path.
Operator identifier
The operator identifier of the person identifier who
was running the ImageMark Transaction Manager
program that caused the error.
Error Message Component
Description
Station number
Each ImageMark Transaction Manager
subsystem has a unique station number in
addition to its subsystem name. The station
number in the error message tells you which
subsystem was running the ImageMark
Transaction Manager program that caused the
error.
Instance number
Every currently loaded session of an ImageMark
Transaction Manager application is assigned an
instance number. The number in the error
message identifies the session in which the error
occurred.
Application type number
Every currently loaded combination of an
ImageMark Transaction Manager application and
its parameter set is assigned an application type.
Component type number
Every currently loaded combination of an
ImageMark Transaction Manager software
component and its parameter set is assigned a
component type.
Process identifier
The process identifier (PID) that identifies
ImageMark Transaction Manager software
running under Windows; the window handle, for
ImageMark Transaction Manager applications
running under MS-Windows.
Source module
The name of the module of the ImageMark
Transaction Manager source program code in
which the error occurred.
Source module line number
The source code line number on which the error
occurred.
Severity code
See the ImageMark Transaction Manager
Severity Codes table (following page).
Error code
A unique number that tells you on what subsystem
the error occurred and to which software program
it relates.
Error message text
The actual error message text that describes the
error.
329
Severity Codes
The following table briefly describes the meaning of the severity codes in the ImageMark Transaction
Manager error messages.
ImageMark Transaction Manager Severity Codes
Severity
Code
Category
Explanation
0
Alert
This error requires you to take some specified action
immediately.
1
Error
This is a fatal application error that causes the application
(software component) to terminate. For example, you would
expect this error if ImageMark Transaction Manager couldn't
open a database.
2
Recoverable
This is usually a serious application error from which
ImageMark Transaction Manager can recover. For example,
you would expect this error if ImageMark Transaction
Manager couldn't initially connect to a database but did so
after retrying.
3
Inconvenience
This message informs you that you have a minor ImageMark
Transaction Manager error that is easily remedied.
6
Information
This message provides information about ImageMark
Transaction Manager requiring no action on your part.
Troubleshooting with Error Messages
This section suggests one way you can use ImageMark Transaction Manager error messages to
troubleshoot problems.
View the ImageMark Transaction Manager Error Log File
First, view the current ImageMark Transaction Manager error log file
(%IMAGEMARK_ROOT%\log\asiips) to see what messages have been sent there today. Use this
manual to help interpret these messages.
Browse the History Log File
Next, browse the ImageMark Transaction Manager history error logs (asiips.1 through asiips.7, in
the same directory), to see whether any related error messages have been logged over the past
week.
330
Error Message Groupings
As you browse the log files you may notice that some of the error messages are grouped. These all
fall into the same error code range or contain similar component tags. If the error codes for several
error messages all fall in the range of one ImageMark Transaction Manager subsystem, for example,
the Recognition Subsystem, examine the error messages more closely. They can help you narrow
down the suspect software component to the Recognition Unit Manager, for example.
Error Message Text
The error message text may also tell you whether you can service the problem yourself or whether
it is an internal ImageMark Transaction Manager application problem that you must report to secondlevel support.
If the problem is internal, the error messages provide very detailed error “roadmap” information
including the source module name and line number for ImageMark Transaction Manager software
components and the line number. This information is useful to second-level support.
NCR Publications
Once you have identified the subsystem that is probably causing the problem, consult any NCR
publications provided with that subsystem. If you don't find the information you need in one of the
subsystem service books you at least can point your NCR service provider to the subsystem and
software component where the problem seems to be.
Getting the Version Number
The NCR service provider will want to know what version number of ImageMark Transaction
Manager you are running. Before phoning, look up this number by looking in the following folder:
%ImageMark_Data%/opt/siips/base/pkgs
Phoning Second-level Support
In addition to phoning your NCR service provider, you may wish to send a copy of all of the
ImageMark Transaction Manager error logs to your service provider in either printed form or
contained on some electronic medium.
331
If a Recognition Sub-System Fails
In the standard setup, each Recognition Sub-System (RSS) consists of a Recognition auto-activity
(RSS) configured with a DS. At some sites, however, there may be two Recognition auto-activities
(RSS A and RSS B).
If a Recognition auto-activity fails for any reason, there are two ways you will know:
!
error messages, typically starting with the phrase “RSS Peripheral Access: RecUnit,” will appear
in the Activities window of Application Manager
!
the Status column for the corresponding RSS CAR auto-activity will indicate that it has failed.
If you have two Recognition auto-activities on a DS and one of them fails, the DS will pass all work
to the auto-role that is still functioning. However, this will decrease the throughput. If this happens,
you may divert work to other DSs that have surplus capacity until the auto-role is fixed.
If you have only one Recognition auto-activity and it fails, you must place the RSS CAR auto-activity
into “shuffle mode” so that any work from this DS will bypass it and move directly to Codeline
Completion. If resources allow, you may also want to increase the number of Amount Keying
operators to compensate for the loss of Recognition services.
Placing CAR Auto-Activity Into Shuffle Mode
To place the RSS CAR auto-activity in shuffle mode:
1
Log onto the DS that controls the RecUnit.
2
Open the file \%IMAGEMARK_ROOT%\bin\rss and find the following lines:
setenv ShuffleIfRecOpenFail 0
setenv ShuffleIfRecIOFail 0
3
Change the values from 0 to 1, then save the file.
4
5
Choose Application > Display.
332
6
7
Choose Maintain > Activities....
Activities Dialog
8
Select the failed RSS CAR auto-activity, then choose Load.
9
The system reloads this auto-activity in shuffle mode, but workflow will bypass it.
333
Placing CAR Auto-Activity in Normal Mode
To return the RSS CAR to normal processing mode:
1
2
Choose Application > Display.
3
4
In the Application Display window, choose Maintain > Activities....
5
Select the RSS CAR auto-activity, then choose Shutdown.
6
Log in to the DS that controls the RecUnit.
7
Open the file \%IMAGEMARK_ROOT%\bin\rss and find the following lines:
setenv ShuffleIfRecOpenFail 1
setenv ShuffleIfRecIOFail 1
8
Change the values from 1 to 0, then save the file.
9
In the Application Display window, choose Maintain > Activities....
10 Select the RSS CAR auto-activity, then choose Load.
11 At the confirmation dialog, choose Yes.
The system reloads this auto-activity in normal mode, but workflow will bypass it.
334
Identifying SMM Problems
This section outlines commonly encountered errors associated with the SMM feature.
No Files Were Imported
This problem is likely due to one of the following factors:
!
The root file path directory does not have read/write permissions.
!
The input file was not downloaded from the bank’s mainframe.
!
The SMM auto-activity is not running on the BAP.
SMM is Not Picking Up Units of Work
!
The SMM auto activity is not running on the DS.
!
The UOWSource attribute is not set to -l by Workflow Manager.
Ensure that the correct version of wmserver is installed and that the application type had a
correct version of wmmgr.dat when typeinst was performed.
The Unit of Work is Held at SMM
If no matching input file is found for a unit of work, it is held at SMM.
This problem is likely due to the fact that the there was no input file available when the unit of work
was initially processed. After the required input file has been imported, choose Retry in the Second
Source View dialog to resubmit the unit of work to SMM.
SMM is Not Matching any Units of Work
!
The SMM auto-activity is in shuffle mode.
Check the smm_pod.lst file. If SMM_SHUFFLE = yes, SMM is in shuffle mode.
!
The SMM auto-activity cannot locate the input file for the unit of work.
Check the directory where branch capture input files are configured to be downloaded from the
mainframe. Also check the SS_FILE table on the BAP to see if any branch capture input files
have been successfully imported.
There are No Teller Files to Import
This problem is likely due to the fact that the file transfer process for branch capture input files did
not work.
Teller files may have to be retransmitted.
335
There are No Teller Files From a Specific Branch
!
The file transfer process for branch capture input files did not work for that branch
Check with the mainframe system administrator.
!
Communication links to the branch are no longer operational.
Check with the mainframe system administrator.
!
The branch information is incorrect or missing from the teller file.
View the unit of work items in the Second Source View Details dialog and ensure that their
branch information matches the branch information referenced in the input file.
SMM Attempts to Import a Duplicate File
This problem is likely due to the fact that the mainframe downloaded the teller files more than once.
The existence of duplicate teller files, one with the .complete file extension and one with the .bad
file extension is a symptom of this problem. You might also encounter a third duplicate file that has
no extension because it has not been imported yet.
You can address this problem by adding a .duplicate extension to the third file. This will prevent
SMM from attempting to reprocess it later.
SMM is Running Slowly
!
There are too many duplicate records for SMM to match and use for lookups. Review the
SECOND_SOURCE_FIELD_PARMS and identify additional SMM fields.
!
You are running group match mode.
This mode runs more slowly than individual match mode.
!
Performance is slow due to a high number of unmatched records in the database.
A high number unmatched records means more rows in the database for the system to match
against.
Bank Diverts Work From One Site to Another
This problem is caused by scenarios when a bank must divert its work to another site in order to
process its transactions. The ssfilter script extracts selected rows out of the SMM file and places
them into a new file. It is installed in the %IMAGEMARK_ROOT%\bin directory.
To execute the script, run \%IMAGEMARK_ROOT%\bin\ssfilter -f filename | -s site1, ... | -b
branch1, ...
where:
336
!
filename is the name of the file
!
site is the site number
!
branch is the branch number
If an Activity or Auto-Activity Fails Spontaneously
If an Activity or Auto-Activity Fails
Spontaneously
If an ImageMark Transaction Manager activity or auto-activity fails spontaneously, you may
sometimes be able to get it running again by rebooting the subsystem that it runs on.
Caution: Do not reboot a subsystem unless you have been told in your ImageMark Transaction
Manager System Administration course that this is an acceptable option in this particular
situation.
When an activity or auto-activity fails spontaneously, even if rebooting gets it running again, you
should always let your NCR service provider know about the problem. That way, we can attempt to
identify the cause and try to prevent it from recurring.
337
Emergency Recovery Procedures
ImageMark Transaction Manager has procedures to protect the logical logs and data in case of a
hardware or software failure. These procedures include the following:
!
what to do if the start-of-day backup or archive fail
!
what to do if, during the processing day, the logical logs fill up faster than the system can back
them up
!
what to do if the system server crashes or locks-up, resulting in a corrupted Data Manager
database
Start-of-Day Backup and Archive Failures
If the start-of-day Level 0 Archive or continuous logical log backup fails, the error messages are
logged to the reinit output file for that server. These are as follows:
Error Log Output Filenames
Server
Log filename
BAP
%IMAGEMARK_ROOT%\reinitbap.out
DAP
%IMAGEMARK_ROOT%\reinitdap.out
DS
%IMAGEMARK_ROOT%\reinitds.out
Note the messages appearing in the output log, then contact your NCR support person.
Emergency Logical Log Backup
In the event that the logical logs fill up faster than the system can back them up, or that the usual
storage of logical logs to disk fails, Data Manager will halt until the emergency back-up is completed.
To perform the emergency logical log backup, proceed as follows:
1
Contact your NCR support person to inform him/her that this problem has occurred.
2
Log onto the failed server.
3
At the prompt, type the emergency log backup script:
onbar -b -l
The system will save the logical logs to disk. This process will take 5-10 minutes on a DS, and
under 5 minutes on a DAP or BAP.
338
4
Open Application Manager and ensure that all the auto-activities for the application instance
are active and running properly.
5
Open Diagnostics, and note any Alerts generated by the system.
Recovering from a System Failure
In the event that your system fails, resulting in a database being corrupted on your BAP, DAP, or
DS (that is, any server where you have Data Manager installed) you must contact your NCR support
person immediately.
The recovery process has two steps:
!
restoring the Level 0 Archive
!
restoring the logical log backup
NCR Support is responsible for performing the restore of the Level 0 Archive. This procedure should
take less than 30 minutes to complete.
The second procedure, restoring the logical log backup, can be done once the Level 0 Archive has
been restored. Since this script can take up to 8 hours to run, NCR Support may ask you to run and
monitor it.
To perform the logical log restore, proceed as follows:
1
Log onto the appropriate server.
2
Type the name of the restore script:
%SIIPS_BASE_MNT%\initialize\siipsdbrestore
Any errors resulting from this script will be printed to the console. Note any messages then
contact NCR Support.
339
340
A
Report Samples
This appendix contains samples of all printable ImageMark Transaction Manager 4.2 reports. Most
reports are grouped into three categories:
!
End-of-Cycle reports
!
Operator Performance reports
!
Auto-Activity reports
Note: There is one report that does not fall into any of these categories: the MIE Exception report.
A sample of this report is included at the end of this appendix.
341
Appendix A: Report Samples
End-of-Cycle Report Samples
This section contains samples of all printable End-of-Cycle reports. This includes the following:
!
!
Amount Suspect Summary report
!
ATM reports
!
!
342
Unmatched ATM Envelope report
Audit reports
!
ImageMark Audit report
!
Audit Exceptions report
!
!
!
!
!
BTM reports
!
!
!
!
!
!
!
Teller Ranking report
!
!
!
Bundle List report
!
!
!
!
Research Items – Exception Items in Kill Pocket report
!
!
Image Quality reports
!
Image Quality Failure Detail report
!
!
Image Quality Transport Performance Summary report
!
!
!
Items Pull reports
!
!
!
!
!
CAR Performance Summary report
!
CAV Performance Summary report
!
RSS Reclassification report
!
RIR Document Distribution report
!
Second Source Match and Merge Performance Summary report
!
!
User Permission and Login Information report
343
344
Entry
----15
15
Block
---------00
00
***********END OF REPORT***************
NCR Training
6
6
Total:
Grand Total:
# Adjustments
------------1
5
Cycle: 1
Adjustment Summary Report
1
Adj. Code
-------------------------------------10
42
09/Nov/2004
Page
Account Number
-------------3616817
3289398
Total
AK
MICR
Misread
Misenc
Miskey
3
5
17
16
0
6
36
0
0
2
0
0
0
2
0
0
0
0
0
0
0
0
0
0
Less
Digits
1
0
0
0
0
3
3
0
0
0
46
192
0
67
113
0
74
0
0
0
0
0
0
0
0
0
0
0
0
Key
Block
Items
Showouts
Reclass
at
BAL
SUSP
Adjust
Nonproof
AK
------- ------- --------- ----------- ----------
26/Oct/2004
-------
Adj2
-------
END OF REPORT
-------
------Totals:
**********
Adj1
-------
Entry
-------
-------
Adj4
-------
**********
-------
Adj3
-------
-------
Adj5
-------
-------
Adj6
-------
-------
Adj7
-------
-------
Adj8
-------
-------
Adj9
-------
-------
Adj10
-------
Totals:
41
42
2
2
0
0
0
6
238
254
0
0
0
========================================================================================================================
11
13
14
16
Total
Items
Cycle:
Page 1
Less
Key
Dig
at
Wrong
CLC
------ ------- ------- ---------- ------- ------- ------ ------- -------
Entry
NCR Training
Amount Suspect Summary Report
345
346
1234567
Trans Time
12:00:45
12:00:45
12:00:45
12:00:45
1234568
Trans Time
12:00:45
12:00:45
12:00:45
12:00:45
Trans Num
459
459
459
459
Trans Num
456
457
458
459
8
4
4
1
Grand total # envelopes:
Total # envelopes:
ATM Number: 1234568
Trans Date Trans Time
042306
12:00:45
Trans Num
459
1
Total amount: $
Type
SAV Deposit
Card Number
555544443333
Total amount: $
Type
SAV Deposit
Grand total amount: $
Card Number
555544443333
Envelopes Missing for Posting Date 031506
1
Trans Num
459
Total # envelopes:
ATM Number: 1234568
Trans Date Trans Time
042306
12:00:45
Account Number
450644501909
450644501904
450644501904
012345678901234
500.00
Account Number
450644501904
450644501903
450644501902
450644501901
Total amount: $ 1,001,499.99
Type
SAV Deposit
SAV Deposit
SAV Deposit
SAV Deposit
Total amount: $
Type
DDA Deposit
SAV Deposit
Foreign Deposit
Payment
500.00
Account Number
450644501909
500.00
500.00
Account Number
450644501909
Grand total amount: $ 1,001,999.99
Card Number
555544443333
555544443333
555544443333
555544443333
Card Number
555544443333
555544443333
555544443333
555544443333
Envelopes Missing for Posting Date 031606
Grand total # envelopes:
Total # envelopes:
ATM Number:
Trans Date
042306
042306
042306
042306
Total # envelopes:
ATM Number:
Trans Date
042306
042306
042306
042306
Envelopes Aged Out Report For 061306
Unmatched ATM Envelope Report for 061306
Amount
FIID
$
500.00
1
Amount
FIID
$
500.00
1
Amount
FIID
$999,999.99
1
$
500.00 9999
$
500.00
1
$
500.00
1
Amount
FIID
$
125.00
1
$
125.00
1
$
125.00
1
$
125.00
1
Ref
123
Ref
123
Report as of 0613
Report as of 0613
Ref
123
123
M12345678901234567890
123
Ref
123
123
123
123
280000
280000
150000
50000
73161220
!!!b!!!!039
73161220
!!!b!!!!039
73161221
!!!7!!!7!!
73161222
73161223
!!!b!!!9849
80000
38546
73161163
0b!!!
----------
AMOUNT
-------------
DRN
ANY BANK
ImageMark Audit Report
K
K
K
K
K
-----
STAT
093
093
093
093
093
----
OPER
(ds01a)
KM C
K CC
K BB
KMCC
KMCC
S CMM
S
----------
1234567890
4
3
3
3
3
2
3
4
3
4
4
3
3
1
3
3
3
3
3
17
1
3
3
2
??9849
???039
50
10000000
100
06414535
06414533
02823847
10000
20964277
20503718
26276364
29603325
84366275
10000
16683
33317310
47544072
000095
061000052
26453288
13912749
09889730
38112441
2166
27103
061000010
39997544
502111002
061000010
CODELINE
CHG
DATA BEFORE
DATA AFTER
--- ----------------- ----------------12
12
12
12
3
06414535
C093
C093
C093
C093
C093
C093
B008
C093
C093
B008
C093
2!!
3!3
OPER
---B074
B074
B022
B022
C093
c42396118c d502201666d
C093
C093
K093
C093
C093
C093
C093
C093
B008
K093
C093
C093
C093
16/Apr/2003
Page 1
347
348
0108299908000147
0108299908000241
0108299908000244
0108299908000245
0108299908000246
0108299908000252
Batch: 0518
0108299908000130
0108299908000234
0108299908000240
0108299908000231
0108299908000223
0108299908000216
0108299908000204
0108299908000211
0108299908000203
0108299908000202
Batch: 0515
0108299908000195
0108299908000197
0108299908000200
-------------------Batch: 051544937
0108299908000192
DRN
Balancing
Balancing
Expert Balancing
Balancing
Expert Balancing
Balancing
Balancing
Expert Balancing
Balancing
Balancing
Expert Balancing
Balancing
Expert Balancing
Balancing
Expert Balancing
Balancing
Expert Balancing
Balancing
Expert Balancing
Balancing
Expert Balancing
Balancing
Expert Balancing
Balancing
Balancing
Balancing
Balancing
Balancing
Balancing
Codeline Completion
Balancing
Balancing
Codeline Completion
Balancing
333
111
111
333
111
Entry Processing Autorole
-------------------------------
Activity
Cycle: 1
111
111
111
111
111
111
111
111
111
111
111
111
111
111
111
111
111
111
111
111
111
111
111
111
111
111
111
111
111
Oper
No.
----
Process Date: 29/Aug/2005
Audit Exceptions Report
NCR Training
3
16
1
3
17
13
13
17
17
18
17
19
19
17
1
19
17
17
17
18
17
18
16
17
17
19
16
18
17
12
16
12
12
17
73
Chg
Code
----
Before
41
0225661
0
21500
02149943
91
3
41
0
19191
9
10000
45500
45500
10000
10000
10000
10000
19500
4500
4500
4500
43123
43123
9000
9000
8
1800
1800
1800
0
64375
64375
9
32
14
14
31
31
31
31
1950000
22
22
18
23
23
26
26
8
26
17
17
0
17
17
After
-----------------------------
Entry: 1
-----------------------------
Host Entry: 1
Page 1
Host
Entry
-----
**********
Orig.
Entry
----8661
8662
8663
END OF REPORT
HOST
Cycle
No.
----2
2
2
**********
ORIGINAL CYCLE
Cycle
Posting
No.
Date
-------------------1
06/Feb/2004
1
06/Feb/2004
1
06/Feb/2004
ANY BANK - POD -
Modified Entry Report
CYCLE
Posting
Date
Balanced I-String
----------- ----------------12/Feb/2004
12/Feb/2004
12/Feb/2004
Page 1
349
350
**********
--------8000
8000
20894
Reason
Code
-----1
2
2
END OF REPORT
**********
Total Non-Negotiable Amount: 36894
-----------0080313054
0007900844
9418663857
-----------3100000114
3100000116
3100000119
--------666666666
666666666
666666666
Amount
DEPOSIT NON-NEGOTIABLE ITEMS AUDIT:
Non-Negotiable Information:
DRN
R/T
Account
Reason
-----1
1
1
1
11/Feb/2004
Amount
--------8000
10000
16000
8000
Total Hold Amount: 42000
DEPOSIT REVIEW HOLD AUDIT:
Hold Information:
DRN
R/T
Account
------------ --------- -----------3100000109
071000013
3100000111
011500120
3100000108
011500120 11633840
3100000113
211073981 43702565
Cycle: 3
NCR Training
Deposit Review Audit Report
------------3100000112
3100000115
3100000115
--------5990-1364
5990-1364
5990-1364
Deposit Information:
DRN
R/T
DRN
R/T
------------- --------3100000107
5990-1364
3100000107
5990-1364
3100000107
5990-1364
3100000112
5990-1364
Total # Non-Negotiable Items: 3
----------------------------------
Comments
Total # Hold Items: 4
Comments
---------------------------------AUTOHOLD: Transit Item over 5000
AUTOHOLD: Transit Item over 5000
Page 1
---------4091064893
4220212063
4220212063
Account
Account
---------0010487646
0010487646
0010487646
4091064893
ACC Skipped
ACC Assigned
Operator Modifed ACC Field
Cycle: xxx
Bank Name: Bank of Anytown
F1
F2
F3
SWOCR
F4
Automatic Codeline Completion Statistics Report
F5
F6
F7
F8
F9
CAR/LAR
F10
xxxxxx
F1
Page 1
XXXXXX
Posting Date: 9/14/2005
Date: 9/13/2005
351
BIE Deadline Report
There are four samples of this report, all in CPCS format:
Example One
In this example:
!
there are two entries, each with an on-us rehandle pocket (3), a transit rehandle pocket (5),
and an EPU reject pocket (2)
!
the EPU reject pocket (2) was combo’d with the transit rehandle pocket (5)
!
at the ESU, the onus rehandle from entry 0001 was stacked after the onus rehandle from
entry 0002, and the SIE was called 0002-2-03-00-00-00-I-000
!
at the ESU, the transit rehandle from entry 0002 was stacked after the transit rehandle from
entry 0001, and the SIE was called 0001-2-05-00-00-00-I-000
Example Two
In this example:
!
the EPU reject pocket was run as a separate ESU run
!
at the ESU, the EPU reject pocket from entry 0001 was stacked after the EPU reject pocket
from entry 0002, and the SIE was called 0002-2-02-00-00-00-1-000
Example Three
In this example:
!
the EPU reject pocket was run offline
!
the reject transit items are included in the TOTALS line, but not in the On/Before or After
deadline total lines
Example Four
This example shows the format of the BIE Deadline report for 3890 Capture.
352
04:30:00
0002
03:00:00
12:45:00
09:00:00
03:15:00
12:45:00
09:00:00
06:15:00
06:00:00
11:30:00
07:00:00
11:30:00
07:00:00
04:00:00
09:30:00
05:00:00
01:45:00
07:00:00
02:30:00
1000
0
1000
2000
0
2000
EPU TO
TRANSIT
EXPORT
AMOUNT
DIFFERENCE (000s)
10000
4000
6000
11000
4500
6500
TOTAL
#ITEMS
0001-1-00-00-00-00-I-000
0002-2-03-00-00-00-I-000
0001-2-05-00-00-00-I-000
0002-1-00-00-00-00-I-000
0002-2-03-00-00-00-I-000
0001-2-05-00-00-00-I-000
IDENTIFIER
09/Mar/2006
END OF REPORT
**********
Transit Total: 3000
Transit Total: 0
**********
10:30:00 Deadline:
10:30:00 Deadline:
On/Before
After
Total # Items: 21000
Total # Items: 0
---------------------------------------------------------------------------------------TOTALS: Number Entries: 2
Transit Total: 3000
02:00:00
0001
SIE TIME
BIE TIME
EPU
HOST START
ENTRY TIME
PIE TIME
Cycle: 1
102
Process Date: 09/Mar/2000
NCR Training - Your Bank
BIE Deadline Report - Example 1
353
354
02:00:00
04:30:00
0001
0002
06:15:00
06:00:00
BIE TIME
11:00:00
11:30:00
07:30:00
11:00:00
11:30:00
07:30:00
SIE TIME
1
04:00:00
09:00:00
09:30:00
05:30:00
01:45:00
06:30:00
07:00:00
03:00:00
1000
100
0
900
2000
200
0
1800
EPU TO
TRANSIT
EXPORT
AMOUNT
DIFFERENCE (000s)
Cycle:
102
10000
100
4000
5900
11000
200
4500
6300
TOTAL
#ITEMS
0001-1-00-00-00-00-I-000
0002-2-02-00-00-00-I-000
0002-2-03-00-00-00-I-000
0001-2-05-00-00-00-I-000
0002-1-00-00-00-00-I-000
0002-2-02-00-00-00-I-000
0002-2-03-00-00-00-I-000
0001-2-05-00-00-00-I-000
IDENTIFIER
09/Mar/2006
END OF REPORT
**********
**********
10:30:00 Deadline:
10:30:00 Deadline:
On/Before
After
Transit Total: 2700
Transit Total: 300
Total # Items: 300
---------------------------------------------------------------------------------------TOTALS: Number Entries: 2
Transit Total: 3000
EPU
START
TIME
HOST
ENTRY
NCR Training - Your Bank
02:00:00
04:30:00
0001
0002
06:15:00
06:00:00
BIE TIME
11:30:00
07:30:00
11:30:00
07:30:00
SIE TIME
1
04:00:00
09:30:00
05:30:00
01:45:00
07:00:00
03:00:00
1000
0
900
2000
0
1800
EPU TO
TRANSIT
EXPORT
AMOUNT
DIFFERENCE (000s)
Cycle:
102
10000
4000
5900
11000
4500
6300
TOTAL
#ITEMS
0001-1-00-00-00-00-I-000
0002-2-03-00-00-00-I-000
0001-2-05-00-00-00-I-000
0002-1-00-00-00-00-I-000
0002-2-03-00-00-00-I-000
0001-2-05-00-00-00-I-000
IDENTIFIER
09/Mar/2006
**********
On/Before
After
END OF REPORT
**********
10:30:00 Deadline:
10:30:00 Deadline:
Transit Total: 2700
Transit Total: 0
Total # Items: 0
-----------------------------------------------------------------------------------------TOTALS: Number Entries: 2
Transit Total: 3000
EPU
START
TIME
HOST
ENTRY
NCR Training - Bank 1
355
356
99:99:99
99:99:99
9999
9999
99:99:99
99:99:99
BIE TIME
SIE TIME
Host Cycle:
.
.
.
99:99:99
99:99:99
EPU TO
EXPORT
DIFFERENCE
%cycle
09/Mar/2006
999999999
999999999
TRANSIT
AMOUNT
(000s)
99999999
99999999
TOTAL
# ITEMS
xxxx-1-00-00-00-00-M-000
xxxx-1-00-00-00-00-M-000
IDENTIFIER
On/Before
After
%bie deadline Deadline:
%bie deadline Deadline:
Transit Total: 999999999
Total # Items:99999999
Total # Items:99999999
........................................................................................................................
TOTALS: Number Entries: 99
EPU
START
TIME
HOST
ENTRY
Process Date: %process date
%Multi-Bank Name
BIE Deadline Report - Example 4 (3890)
Cycle: 1
Prosting Date: 29/Oct/2006
Cycle Region 1
: 2--02--0-0-
END OF REPORT
**********
Transit Total:
0
**********
24:00:00 Deadline -->
24:00:00 Deadline -->
On/Before
After
Total # Items:
0
TRANSIT
PRIMARY
SECONDARY
AMOUNT
TOTAL
JOB
JOB
EIE TIME
(000s)
# ITEMS
IDENTIFIER
--------------- -------- --------- ------- -----------------------3018
15:49:54
727
1445 3018-2-02-00-00-00-I-000
3021
17:03:00
1337
4126 3018-2-02-00-00-00-I-000
3293
17:27:57
961
3645 3018-2-02-00-00-00-I-000
3743
17:28:31
386
2166 3018-2-02-00-00-00-I-000
3742
17:29:21
1749
3420 3018-2-02-00-00-00-I-000
3537
17:31:14
1542
3438 3018-2-02-00-00-00-I-000
3536
17:32:43
2015
4408 3018-2-02-00-00-00-I-000
3027
21:34:28
1432
5119 3018-2-02-00-00-00-I-000
3755
21:35:33
2334
3515 3018-2-02-00-00-00-I-000
3754
22:10:34
3043
4744 3018-2-02-00-00-00-I-000
3747
22:13:22
3113
3915 3018-2-02-00-00-00-I-000
3298
22:16:32
4189
6081 3018-2-02-00-00-00-I-000
3548
22:17:57
1284
4474 3018-2-02-00-00-00-I-000
3746
22:23:58
1791
4474 3018-2-02-00-00-00-I-000
3029
22:27:46
3024
4513 3018-2-02-00-00-00-I-000
3756
22:31:29
2711
4576 3018-2-02-00-00-00-I-000
3028
00:47:02
2633
3245 3018-2-02-00-00-00-I-000
---------------------------------------------------------------------------------------TOTALS:
Number Entries: 68
30/OCT/2006
ANY BANK
EIE Deadline Report
EPU Pocket Table: 2
357
SIE Deadline Report
The following is a CPCS example.
In this example:
358
!
there were four entries, each with a transit rehandle (pkt 5) and an EPU reject pocket (pkt 2)
!
EPU reject pocket 02 was combo’d with the transit rehandle
!
the transit rehandle from entry 0002 was stacked after the transit rehandle from entry 0001,
at the ESU, and the SIE was called 0001-2-05-00-00-00-1-000
!
the transit rehandle from entry 0003 was stacked after the transit rehandle from entry 0004,
at the ESU, and the SIE was called 0004-2-05-00-00-00-1-000
07:30:00
08:00:00
0001
0004
3000
3300
TRANSIT
AMOUNT
(000s)
12500
13000
0001-2-05-00-00-00-I-000
0004-2-05-00-00-00-I-000
IDENTIFIER
Cycle: 1
09/Mar/2000
105: 05-00-00-00 EPU Pocket Table: 11
**********
On/Before
After
**********
Deadline: Transit Total: 6300
Deadline: Transit Total: 0
END OF REPORT
24:00:00
24:00:00
Total #Items: 25500
Total #Items: 0
----------------------------------------------------------------------TOTALS: Number Entries: 4 Transit Total: 6300
Total #Items: 25500
SIE TIME
HOST
ENTRY
TOTAL
#ITEMS
09/Mar/2000
NCR Training – Your Bank
SIE Deadline Report
359
360
Number
BTM
Number of
BTM
Posting
BTM
of
Debits
Teller
Branch
Batch
Date
Amount
Debits Unmatched
---------- ---------- --------- ----------- ----------- ------ --------WFF60420
8
50735
23/Sep/2002 $ 75,826.45 1
1
WFF60420
8
50734
23/Sep/2002 $ 1,908.66 10
10
WFF60420
8
50003
23/Sep/2002 $ 12,495.98 16
16
WFF60420
8
50002
23/Sep/2002 $ 20,130.62 3
3
--------------------------------------------------------------------------Subtotal
$110,361.71
BTM Batches Not Received Report for Thursday November 14, 2002
BTM
CPCS
BTM
Posting
Posting
BTM
Teller
Branch
Batch
Date
Date
Amount
---------- ---------- --------- ----------- ----------- ----------WFF60420
8
50065
12/Nov/2002 11/Nov/2002 $ 3,895.98
WFF60420
8
50064
12/Nov/2002 11/Nov/2002 $ 63,903.35
-----------------------------------------------------------------------Subtotal
$ 67,799.33
Next Day BTM Batches Received Report for Thursday November 14, 2002
361
362
BTM
BTM
Customer
BTM
Posting
BTM
Item
ID
Teller
Branch
Batch
Date
Amount
Number Number
---------- ---------- --------- ----------- ----------- ------ -------WFF60420
8
50080
23/Sep/2002 $ 2,339.96
Counter Check
WFF60420
8
50080
23/Sep/2002 $
22.14
Royal Development
WFF60420
8
50080
23/Sep/2002 $ 16,721.00
SIT Trust
WFF60420
8
50080
23/Sep/2002 $ 1,409.88
Bank of GSC
WFF60420
8
50080
23/Sep/2002 $ 1,127.19
Personal Check
WFF60420
8
50074
23/Sep/2002 $
782.63
Personal Check
WFF60420
8
50074
23/Sep/2002 $ 7,299.98
Bank of GSC
WFF60420
8
50074
23/Sep/2002 $ 5,228.00
Bank of Marketing
WFF60420
8
50074
23/Sep/2002 $ 37,883.50
WFF60420
8
50074
23/Sep/2002 $ 26,056.00
WFF60420
8
50074
23/Sep/2002 $ 2,066.72
Counter Check
WFF60420
8
50074
23/Sep/2002 $ 1,643.00
Bank of Marketing
WFF60420
8
50067
23/Sep/2002 $
917.91
Personal Check
WFF60420
8
50067
23/Sep/2002 $ 7,548.00
Bank of Marketing
WFF60420
8
50067
23/Sep/2002 $ 44,168.50
WFF60420
8
50067
23/Sep/2002 $ 3,708.12
Counter Cheque
WFF60420
8
50067
23/Sep/2002 $
311.96
Cash In Ticket
WFF60420
8
50067
23/Sep/2002 $ 2,322.90
Personal Cheque
WFF60420
8
50067
23/Sep/2002 $ 18,526.00
WFF60420
8
50067
23/Sep/2002 $ 12,353.50
WFF60420
8
50067
23/Sep/2002 $ 1,229.71
Personal Check
WFF60420
8
50067
23/Sep/2002 $ 1,220.96
Personal Check
WFF60420
8
50067
23/Sep/2002 $ 1,051.93
Personal Check
WFF60420
8
50061
23/Sep/2002 $
10.25
Personal Check
WFF60420
8
50061
23/Sep/2002 $ 1,017.42
Personal Check
-----------------------------------------------------------------------------------Subtotal
$196,967.16
Items Missing from BTM Batches Received Today Report for Thursday November 14, 2002
BTM
CPCS
BTM
Customer
BTM
Posting
Posting
BTM
Item
ID
Teller
Branch
Batch
Date
Date
Amount
Number Number
---------- ---------- --------- ----------- ----------- ----------- ------ ----------------WFF60420
8
50079
23/Sep/2002 11/Nov/2002 $ 2,579.20
Bank of GSC
WFF60420
8
50079
23/Sep/2002 11/Nov/2002 $
22.87
Royal Development
WFF60420
8
50079
23/Sep/2002 11/Nov/2002 $ 1,966.42
Bank of GSC
WFF60420
8
50073
23/Sep/2002 11/Nov/2002 $ 1,876.00
WFF60420
8
50073
23/Sep/2002 11/Nov/2002 $ 1,741.80
Personal Check
WFF60420
8
50070
23/Sep/2002 11/Nov/2002 $ 1,455.75
Personal Check
WFF60420
8
50070
23/Sep/2002 11/Nov/2002 $ 1,081.36
Bank of GSC
WFF60420
8
50064
23/Sep/2002 11/Nov/2002 $ 51,991.00
WFF60420
8
50064
23/Sep/2002 11/Nov/2002 $ 4,234.00
Bank of Marketing
WFF60420
8
50064
23/Sep/2002 11/Nov/2002 $
208.11
Cash In Ticket
--------------------------------------------------------------------------------------------------Subtotal
$ 67,156.51
Items Received without BTM Batches Today Report for Thursday November 14, 2002
363
364
BTM
BTM
Customer
BTM
Posting
BTM
Item
ID
Teller
Branch
Batch
Date
Amount
Number Number
---------- ---------- --------- ----------- ----------- ------ ----------------------WFF60420
8
50001
14/Nov/2002 $ 2,071.36
Personal Check
WFF60420
8
50001
13/Nov/2002 $ 1,926.08
Personal Check
WFF60420
8
50001
12/Nov/2002 $ 6,962.59
BTM Batch Ticket
WFF60420
8
50001
23/Sep/2002 $
94.81
Royal Development
WFF60420
8
50001
23/Sep/2002 $
846.34
Counter Withdrawal Slip
WFF60420
8
50001
23/Sep/2002 $ 2,024.00
Bank of Marketing
-------------------------------------------------------------------------------------------Subtotal
$ 13,925.18
BTM Batches Aged Out Report for Thursday November 14, 2002
Final
Ranking
------3
1
1
Branch
Number
------3
1
2
Number
of
Items
Not
Received
------1
1
0
Number
of
Batches
Not
Received
------2
0
2
Number
of
Teller
Keying
Errors
------5
5
5
Branch Rankings Report for Tuesday October 22, 2002
365
366
Final
Ranking
Across
All
Branches
------5
4
Number
of
Items
Not
Received
------0
1
Number
of
Batches
Not
Received
------0
0
Number
of
Teller
Keying
Errors
------3
2
Final
Ranking
Across
All
Branches
------6
2
1
Number
of
Items
Not
Received
------0
0
0
Number
of
Batches
Not
Received
------2
0
0
Number
of
Teller
Keying
Errors
------4
1
0
Teller
Number
------302
301
Final
Ranking
Within
Branch
------2
1
Final
Ranking
Across
All
Branches
------7
3
Number
of
Items
Not
Received
------1
0
Number
of
Batches
Not
Received
------1
1
Number
of
Teller
Keying
Errors
------4
1
Number
of
Force
Matched
Items
Per
Thousand
Items
------125.00
0
Teller Ranking Report for Branch Number 3 for Tuesday October 22, 2002
Teller
Number
------201
202
203
Final
Ranking
Within
Branch
------3
2
1
Number
of
Force
Matched
Items
Per
Thousand
Items
------0
0
0
Teller
Number
------555
102
Final
Ranking
Within
Branch
------2
1
Number
of
Force
Matched
Items
Per
Thousand
Items
------333.33
0
100
1
454229416 11/Oct/2001 29/Aug/2002 $
70.00 asd;k 23423
Manual
222
---------------------------------------------------------------------------------------------------------------------------------Subtotal
$
70.00
100
4
454229425 29/Aug/2002 29/Aug/2002 $
5.00 234ab 324d
Manual
888
---------------------------------------------------------------------------------------------------------------------------------Subtotal
$
5.00
100
5
454229431 11/Oct/2001 29/Aug/2002 $
70.00 asd;k 23423
Manual
222
---------------------------------------------------------------------------------------------------------------------------------Subtotal
$
70.00
100
8
454229434 08/Feb/2002 29/Aug/2002 $
11.00 asd;k 23423
Auto
---------------------------------------------------------------------------------------------------------------------------------Subtotal
$
11.00
100
9
454229435 08/Feb/2002 29/Aug/2002 $
5.00 asd;k 23423
Auto
---------------------------------------------------------------------------------------------------------------------------------Subtotal
$
5.00
BTM
CPCS
BTM
Custom
BTM
Posting
Posting
BTM
Mismatch Operator Item
ID
Teller
Branch
Batch
Date
Date
Amount
DRN
Type
ID
Number Number
---------- ---------- --------- ----------- ----------- ----------- -------------------- -------- -------- ------ -----100
10
454229436 08/Feb/2002 29/Aug/2002 $
5.00 asd;k 23423
Manual
222
100
10
454229436 08/Feb/2002 29/Aug/2002 $
7.00 asd;k 23423
Manual
222
---------------------------------------------------------------------------------------------------------------------------------Subtotal
$
12.00
Incorrectly Matched Items Report for Friday October 25, 2002
367
368
BTM
CPCS
BTM
Customer
BTM
Posting
Posting
BTM
Posted
Item
ID
Teller
Branch
Batch
Date
Date
Amount
Amount
Number Number
---------- ---------- --------- ----------- ----------- ----------- ----------- ------ -------101
1
454229696 08/Feb/2002 29/Aug/2002 $
1.00 $
1.01
102
1
454229696 11/Oct/2001 29/Aug/2002 $
100.07 $
100.06
------------------------------------------------------------------------------------------------------100
2
454229313 29/Aug/2002 29/Aug/2002 $
9.95 $
10.00
200
2
454229313 29/Aug/2002 29/Aug/2002 $
10.00 $
9.95
------------------------------------------------------------------------------------------------------100
3
454229439 07/Feb/2002 29/Aug/2002 $
1.00 $
2.00
101
3
454229439 07/Feb/2002 29/Aug/2002 $
2.00 $
1.00
------------------------------------------------------------------------------------------------------100
4
454229437 07/Feb/2002 29/Aug/2002 $
1.00 $
2.00
101
4
454229437 07/Feb/2002 29/Aug/2002 $
2.00 $
1.00
------------------------------------------------------------------------------------------------------100
5
454229444 07/Feb/2002 29/Aug/2002 $
2.00 $
1.00
100
5
454229444 08/Feb/2002 28/Aug/2002 $
1.00 $
2.00
101
5
454229444 07/Feb/2002 29/Aug/2002 $
1.00 $
2.00
101
5
454229444 08/Feb/2002 28/Aug/2002 $
2.00 $
1.00
------------------------------------------------------------------------------------------------------100
6
454229421 07/Feb/2002 29/Aug/2002 $
7.00 $
2.00
101
6
454229421 07/Feb/2002 29/Aug/2002 $
2.00 $
7.00
-------------------------------------------------------------------------------------------------------
Teller Keying Errors Detail Report for Monday October 28, 2002
Total
R/T
123456
987654
…
DRN
1234567890
1234567891
…
Receiving Bank: %receiving_bank1
%receiving_bank2
%receiving_bank3
%receiving_bank4
%sending_bank1
%sending_bank2
%sending_bank3
%sending_bank4
Bundle List Report
1234567890
1000000000
…
9999999999
AMOUNT
1234567890
1234567891
…
(%count)
DRN
Cycle Date: %cycle_date
Station ID: %esustn
123456
987654
…
R/T
1234567890
1000000000
…
AMOUNT
1234567890
1234567891
…
DRN
Pocket: %spmode:%pocket_label
Run: %run_date %run_time
123456
987654
…
R/T
1234567890
1000000000
…
AMOUNT
369
Note: The following example has been customized for BTM processing. BTM versions of the report
list the BTM Batch number for each item under the following field heading:
!
370
9000000
238508000020
DB
DB
CR/DB/NP
-------DB
2
2
ENTRY
----2
Cycle: 1
1
1
POCKET
-----1
4
4
3890 PKT
-------4
50001
50001
BTM BATCH NO.
------------50001
**********
END OF REPORT
**********
-----------------------------------------------------------------------------------TOTALS
CR:
0.00
DB: 180,000.00
NP:
0.00
Total # Items: 3
------------------------------------------------------------------------------------
6000000
AMOUNT
-----------3000000
238508000017
DRN
------------238508000014
Posting Date: 26/Mar/2004
NCR Waterloo
Unresolved Suspense Items Report
325219c
c062-204d 22233343c 682
c168655 c352-001d
c062-204d 22233343c 682
26/Mar/2004
Page 1
371
372
Merchant
----------------
-
AMOUNT
------------0000911931
0000498996
0000498996
0000318500
0000250000
0000250000
0000232922
0000232922
...
Collecting Bank
---------------062385
062385
062385
062385
062385
062385
062385
062385
...
-
Total Amount Total Items
Total Fee
------------ ------------ -----------5172169
25
6500
1270929
25
6500
639408
25
6500
1992
25
6500
1321
25
6500
980
25
6500
642
25
6500
319
25
6500
37
11
2860
========================================
7087797
211
54860
CBA_CHEQUE
QLD CBA Branch
1
Posting Date: 11/Aug/2005
Page
10
Posting Date: 11/Aug/2005
Page
438050018071
0000071830
062385
438050018011
0000069000
062385
================================================================
5172169 (25)
DRN
------------438050018010
438050018041
438050018097
438050018015
438050018109
438050018053
438050018112
438050018056
...
CBA_CHEQUE
QLD CBA Branch
77842
229530
405077
6000
367946
296851
08000512
08000542
08000076
08000098
08000099
08000223
CR
CR
DB
CR
CR
CR
CR/DB/NP
-------CR
1
1
1
1
3
3
ENTRY
----1
7
7
5
5
4
4
POCKET
-----4
Cycle: 1
30/Aug/1999
c009577c
c009953c
c02770376c
d612222001d0460-
d612222001d0075-
c
c
d161000017d0074-01031188 c
d161000017d0052-01372738 c
d161000017d
d161000017d
d161000017d
Page 1
96
96
96
96
96
96
**********
END OF REPORT
**********
---------------------------------------------------------------------------------------------------------------------------------TOTALS
CR:
14,772.46
DB:
60.00
NP:
0.00
Total # Items:
7
----------------------------------------------------------------------------------------------------------------------------------
AMOUNT
---------100000
DRN
------------08000130
NCR Training
Research Items - Exception Items in Kill Pocket Report
373
374
BANK
ACCOUNT
TRNCOD AMOUNT
--------- -------------- ------ ---------161000017
61221296
96
564797
161000017
61221296
96 5252432316
Page 1
26/Oct/2004
Cycle:1
**********
END OF REPORT
**********
DRN
Block
Batch
------------- ---------- -----------4000000167
00000112
57
4000000167
00000112
57
4000000189
00000112
57
26/Oct/2004
Page 2
SERIAL BANK
ACCOUNT
TRNCOD AMOUNT
CHG Data Before
Data After
------ --------- -------------- ------ ---------- --- --------------- ----------004721 161000017
054803428528
96
661177
1
0000019999
661177
161000017
054803428528
96
1000 17
10
1000
560320 161000017
021902647605
0000143299 12
Entry Number = 20
DRN
Block
Batch
SERIAL BANK
ACCOUNT
TRNCOD AMOUNT
------------- ---------- ------------ ------ --------- -------------- ------ ---------4000000167
00000112
57 004721 161000017
61221296
96
804829
NCR Training
DRN
Block
Batch
SERIAL BANK
ACCOUNT
TRNCOD AMOUNT
CHG Data Before
Data After
------------- ---------- ------------ ------ --------- -------------- ------ ---------- --- ---------------- ---------4000000021
00003336
00333336 123457 1610-0001
222222226
96
822708
1
0000258911
822708
4000000083
4
00333331
160000513
048306400926
1000
1
5252500550
1000
4000000059
4
00333334
161000017
61211297
68234 17
21
68234
SERIAL
-----123457
123458
Cycle:1
PSet Number = 1
Entry Number = 11
DRN
Block
Batch
------------- ---------- -----------4000000021
00003336
00333336
4000000059
4
00333334
NCR Training
Oper
---1
1
1
Oper
---1
1
1
Image Quality Failure Detail Report
Page 1
22/Mar/2006
Posting Date 17/Mar/2006
Vendor
----------------NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
Test
Binary
Thres
Thres
Test Type
Num Face /Gray Score
hold1
hold2
Result
----------------- ---- ----- ------ ---------------------------------- ------- ------- -----HUMAN
1 Rear Binary
1 -GETFILENAMERR
-1
-1 Fail
QUALITY
0 Front Binary
0
0
-1 Pass
QUALITY
0 Rear Binary
0
0
-1 Pass
QUALITY
1 Front Binary
0
20
-1 Pass
QUALITY
1 Rear Binary
0
20
-1 Pass
QUALITY
2 Front Binary
0
-1
-1 Pass
QUALITY
2 Rear Binary
0
-1
-1 Pass
QUALITY
3 Front Binary
0
3
-1 Pass
QUALITY
3 Rear Binary
0
3
-1 Pass
QUALITY
5 Front Binary
0
20
-1 Pass
QUALITY
5 Rear Binary
0
20
-1 Pass
QUALITY
6 Front Binary
5377
1000
5000 Pass
QUALITY
6 Rear Binary
1016
1000
5000 Pass
QUALITY
7 Front Binary
5377
100000 100000 Pass
QUALITY
7 Rear Binary
1016
100000 100000 Pass
QUALITY
9 Front Binary
0
20
-1 Pass
QUALITY
9 Rear Binary
0
20
-1 Pass
QUALITY
10 Front Binary
0
12
-1 Pass
QUALITY
10 Rear Binary
0
12
-1 Pass
QUALITY
11 Front Binary
0
12
-1 Pass
QUALITY
11 Rear Binary
0
12
-1 Pass
QUALITY
12 Front Binary
160
260
-1 Pass
QUALITY
12 Rear Binary
160
260
-1 Pass
QUALITY
13 Front Binary
160
140
-1 Pass
QUALITY
13 Rear Binary
160
140
-1 Pass
QUALITY
14 Front Binary
70
105
-1 Pass
QUALITY
14 Rear Binary
70
105
-1 Pass
QUALITY
15 Front Binary
70
55
-1 Pass
QUALITY
15 Rear Binary
70
55
-1 Pass
QUALITY
16 Rear Binary
1
2
-1 Fail
Codeline
-------------------------------------------------------------------------------------------------d1000-0010d 2222236c 123 b0000010048b
Transport
DRN
Number
BANK
ACCOUNT
----------------------- ------------ --------- -------------03170606641100179479
11 1000-0010
2222236
IQA SMCR Training
Cycle: 3
Pset Number: 2
375
376
Vendor
---------------NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR
NCR Training
Cycle: 3
Pset Number: 2
Test
Type
Num
Test Description
---------------- ----- -------------------------------HUMAN
0 Regular Operator Review
HUMAN
HUMAN
HUMAN
HUMAN
1 Expert Operator Review
HUMAN
HUMAN
HUMAN
IMAGEMARK
0 Generic Image Quality Test
IMAGEMARK
IMAGEMARK
IMAGEMARK
QUALITY
0 Partial Image
QUALITY
0 Partial Image
QUALITY
0 Partial Image
QUALITY
0 Partial Image
QUALITY
1 Excess Skew
QUALITY
1 Excess Skew
QUALITY
1 Excess Skew
QUALITY
1 Excess Skew
QUALITY
2 Piggy Back
QUALITY
2 Piggy Back
QUALITY
2 Piggy Back
QUALITY
2 Piggy Back
QUALITY
3 Streaks
QUALITY
3 Streaks
QUALITY
3 Streaks
QUALITY
3 Streaks
QUALITY
5 Bent Corner
QUALITY
5 Bent Corner
QUALITY
5 Bent Corner
QUALITY
5 Bent Corner
QUALITY
6 Img Too Small
QUALITY
6 Img Too Small
Face
----Rear
Front
Front
Rear
Front
Rear
Rear
Front
Front
Rear
Rear
Front
Rear
Front
Front
Rear
Front
Front
Rear
Rear
Front
Rear
Front
Rear
Rear
Front
Rear
Front
Front
Rear
Front
Rear
Front
Rear
Binary/ #Passed
Gray
Images
-------- ------Gray
0
Binary
31
Gray
0
Binary
26
Gray
0
Gray
0
Binary
0
Binary
0
Binary
0
Gray
0
Binary
0
Gray
0
Gray
0
Binary
167
Gray
0
Binary
167
Binary
167
Gray
0
Gray
0
Binary
167
Gray
0
Binary
167
Binary
167
Gray
0
Binary
167
Binary
167
Gray
0
Gray
0
Binary
167
Gray
0
Gray
0
Binary
165
Gray
0
Binary
129
Image Quality Test Performance Summary Report
#Passed
#Failed
Images
Images
Rejected/ #Failed Rejected/
Reimaged Images
Reimaged
---------- ------- ---------0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
44
44
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
70
0
0
0
0
0
70
0
0
70
0
0
0
0
0
0
0
0
70
0
0
0
0
0
70
0
0
70
0
0
0
0
0
70
0
0
70
0
0
0
0
0
0
0
0
70
0
0
0
0
0
0
0
0
69
2
1
0
0
0
43
38
27
22/Mar/2006
Page 1
Station
Number
------11
------Total
1
# Captured
Items
---------39
---------39
NCR Training
Cycle: 3
Pset Number:
# Reviewed
---------13
---------13
Page 1
# Reimaged/
Rejected %Reviewed
---------- ----------0
33.33%
---------- ----------0
33.33%
%Reimaged/
Rejected
----------0.00%
----------0.00%
22/Mar/2006
Posting Date:17/Mar/2006
Image Quality Transport Performance Summary Report
377
378
Host
Sequence
----------0014200001
0014617907
END OF REPORT
**********
EX
-66
66
*******
Type
---2
2
16/Apr/2003
Posting
Date
----------18/Oct/2002
18/Oct/2002
ANY BANK
Items Aged Out Report
SERIAL
-----53750
30035
TRANSIT
--------43750
43750
Source: 00
ACCOUNT
-------------38264285
81454322
AMOUNT
-----23750
61096
GROUP
----90594
90594
File: /opt/siips/classa/anybank
Page 1
**********
Posting
Date
----------07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
07/Feb/2002
NCR Training
END OF REPORT
000110
000158
000166
000181
000198
000206
000230
000242
000256
000274
000285
000313
000315
000343
000345
000347
000355
000372
000376
000383
Host
Sequence
----------EX
-0
0
0
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
SERIAL
-----0
0
0
000110
000158
000166
000181
000198
000206
000230
000242
000256
000274
000285
000313
000315
000343
000345
000347
000355
000372
000376
000383
**********
Type
---5
5
5
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
13/Jun/2002
Items Not Received Report
BANK
--------0
159955
0
Source: 00
ACCOUNT
-------------0
2
0
**************
**************
**************
**************
**************
**************
**************
**************
**************
**************
**************
**************
**************
**************
**************
**************
**************
**************
**************
**************
TRNCOD
-----446533
******
******
AMOUNT
---------7
32
45
116000
600
4321810
4000
6000
17000
16612
3000
23534
99300
18000
84713
4600
99500
180941
22145
133800
5000
16000
1100
GROUP
---------------------50144
NJ119
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
NJ131
File: /opt/siips/classa/secondsourcedata/smm20020612.nj.smm
379
380
113535
017699
001278
******
005971
001289
SERIAL
-----007979
007947
005618
050750
050733
050767
******
******
003911
0166
AMOUNT
---------16857
5673
20550
4638
4072
3980
5333
52721
6891
20000
2500
27745
69925
12665
150000
22333
Items Pull Report - High Dollar
ACCOUNT
-------------13145466
13145466
13915796
13266004
13266004
13266004
13775436
07017245
13327274
13145609
14111640
14474552
14659154
07000217
12647177
14659154
Host Entry: 3741
ANY BANK
TRANSIT
--------061000010
061000010
061000010
061000010
061000010
061000010
061000010
061000010
061000010
061000010
061000010
061000010
061000010
061000010
061000010
061000010
TRNCOD
------
Items Pull Report - High Dollar
Host Entry: 3741
ANY BANK
Entry: 3741
Tray Number
----------1701638
1701638
1701638
1701638
1701638
1701638
1701638
1701639
1701638
1701638
1701639
1701638
1701638
1701639
1701638
1701638
Entry: 3741
Tray Sequence
------------1.0000
2.0000
5.0000
6.0000
7.0000
8.0000
10.0000
1.0000
19.0000
23.0000
2.0000
186.0000
187.0000
27.0000
190.0000
191.0000
Page 69
Page 1
**********
END OF REPORT
**********
Total Name
TotalItems Total Amount TotalDRCnt Total Debits TotalCRCnt Total Credits TotNPDebits TotNPCredi
------------------------------ ---------- -------------- ---------- ------------- ---------- ------------- ----------- ---------CTL_RECID_B0_DR
0
0
0
0
0
0
0
RECID_90_DR
2835
218698837
2835
218698837
0
0
0
CTL_RECID_B2_DR
7
0
0
0
0
0
0
CTL_RECID_B3_DR
50
0
0
0
0
0
0
CTL_RECID_B4_DR
2
0
0
0
0
0
0
CTL_RECID_B5_DR
45
324271671
0
0
0
0
0
RECID_02_DR
491
48501352
491
48501352
0
0
0
=================================================================================================================================
Grand Total:
3430
591471860
3326
267200189
0
0
0
Cycle: 1
DRN
EX
------------- -74139744 66
74139745 66
74139760 66
74139766 66
74139767 66
74139768 66
74139772 66
74139881 66
74139882 66
74139894 66
74139914 66
74141105 66
74141107 66
74141108 66
74141116 66
74141117 66
.
.
.
Date: 16/Apr/2003
RECID_02_DR
Cycle: 1
Date: 16/Apr/2003
**********
--------8000
8000
20894
END OF REPORT
**********
Total Amount: 36894
-----------3100000114
3100000116
3100000119
-----123
123
123
-------2259
2260
2263
11/Feb/2004
-----1
2
2
-----------3100000112
3100000115
3100000115
--------5990-1364
5990-1364
5990-1364
DRN
R/T
Page 1
Total # Items: 3
-------------------Stale Date
Missing Signature
Missing Signature
Non-Negotiable Item:
Amount
Reason Reason
Code
DRN
Advice Notice:
Branch Advice
#
Ref #
Cycle: 3
NCR Training
Deposit Review Non-Negotiable Items Report
Location Information:
Tray #
Entry Host
#
Entry
#
---------- --------- ----- ----4091064893 11996
5061 5061
4220212063 11996
5061 5061
4220212063 11996
5061 5061
Account
---YES*
YES*
YES*
EPU
Kill
381
382
Transit:
Transit:
Grand Total:
123456789
9876-5490
R/T
Sub-Total:
1234567890
1234567891
DRN
%gtamount
%tamount
1234567890
1000000000
AMOUNT
(%gtcount)
Onus DB:
%gdamount
%T
%T
(%gdcount)
(%dcount)
1234567890
1000000000
AMOUNT
%damount
123456789
9876-5490
R/T
Onus DB:
1234567890
1234567891
(%tcount)
%T
%T
DRN
Onus CR:
Onus CR:
1234567890
1234567891
DRN
%gcamount
%camount
123456789
9876-5490
R/T
(%gccount)
(%ccount)
1234567890
1000000000
AMOUNT
%T
%T
Page %page
% MultiBankName Cycle: %cycle Cycle Date: %cycle_date
ESU Pocket::%pkt_label
Endpoint ID: %endpoint_id
ESU Station ID: %esustn
ESU Run: %tray_set_date %tray_set_time
Routing Information:
% routing_info1
% routing_info2
% routing_info3
% routing_info4
From Entry(s): 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999,
9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, 9999, ..., 9999
Pocket Listing Report
Total
Proof
Items
------56,859
81,357
49,957
59,607
92,360
-------0.00%
0.00%
0.00%
0.02%
0.00%
Items
Shuffled
Items
Reco
Processed
--------90.83%
91.50%
91.85%
92.00%
90.90%
30/Aug/1999
AMOUNT
RSS
Assigned
-------64.64%
66.72%
65.04%
66.32%
62.67%
AMOUNT
Force
Keyed
------6.39%
5.62%
5.21%
4.86%
6.64%
AMOUNT
RSS
Only
------53.34%
54.60%
53.62%
54.79%
51.45%
AMOUNT
EPU
Only
------0.00%
0.16%
0.00%
0.00%
0.00%
------56.70%
58.50%
56.61%
57.50%
54.16%
AMOUNT
KLD
Page 1
********** END OF REPORT **********
A station marked with an * indicates some data may be lost due to abnormal termination of RSS CAR/CAV Auto-Role.
--------------------------------Recognition 1/Data Server 1
Recognition 1/Data Server 2
Recognition Station
NCR BANK
RSS Performance Summary Report
383
384
Cum.
Number of
Fields
Misread
----------85,545
Cum.
Number of
Fields
Rejected
----------51,575
361
1,224
45
2,163
1,697
156
10
20
49
30
4,293
282
281
464
Number of
Fields
Misread
----------35
4
Cum.
Number of
Items
Failed Rec
-----------
629
1,241
276
3,782
2,583
672
12
27
233
48
799
167
449
572
2
Number of
Fields
Rejected
----------1
6
21/Oct/2002
Cum.
Number of
Items with
Prior Data
----------5,287
Number of
Items
Failed Rec
-----------
73
152
1
1
241
420
130
1
5
9
5
Number of
Items with
Prior Data
-----------
Page 1
********** END OF REPORT **********
A session marked with an * indicates some data may be lost due to abnormal termination of operator application.
Cum.
Number of
Fields
Read
-------------- ----------468,390
325,983
Cum.
Number of
Items
Number of
Fields
Read
-------- ------ ----------- ----------50
1
83
47
51
1
141
131
73
1
3
3
88
1
2,503
1,513
95
1
6,744
4,279
105
1
332
10
106
1
23,267
17,081
107
1
30,668
25,968
108
1
1,661
703
109
1
128
105
110
1
259
207
120
1
375
84
121
1
350
267
204
1
9,002
3,910
205
1
590
141
206
1
3,418
2,615
207
1
7,919
6,731
209
1
6
3
RSS Dist Field Number of
Number Items
RSS Station: Recognition 1/Data Server 1
ANY BANK
CAR Performance Summary Report
1
Cum.
No. of
Items
Comb’d
to
Deposit
Slip
-------
Cum.
No. of
Items
Comb’d
with
Second
Source
------1933
Cum.
No. of
Items
accp’d
without
Second
Source
------1933
Cum.
No. of
Items
Accp’d
No. of No. of No. of
Items
Field
Items
Misread Rejects Force
Key
Rej’d
------5287
Cum.
No. of
Items
with
------- ------- ------- ------61,697
2,649 29,763
2,201
62,975
2,322 27,356
3,080
60,413
2,211 23,515
2,824
72,239
2,881 30,628
3,128
22,323
1,021 11,011
1,165
No. of
Items
Accp’d
by CAV
Cum.
No. of
Field
Rejects
Key
Rej’d
No. of
Items
Accp’d
without
Second
Source
------97,024
96,343
90,189
108,748
35,328
Cum.
No. of
Items
Misread
No. of
Items
accp’d
with
Second
Source
------342
508
421
449
213
Cum.
No. of
Items
Force
Prior
Data in
Field
------- ------- ------- ------- ------466457 282396
13711 154598
12398
Cum.
No. of
Items
Accp’d
by CAV
No. of
Items
Comb’d
to
Deposit
Slip
------342
508
421
449
213
21/Oct/2002
No. of
Items
with
Prior
Data in
Field
------1,056
1,118
1,647
321
21
Page 1
********** END OF REPORT **********
Cum.
No. of
Items
Procs’d
with
Add
Tape
--------468390
No. of No. of
Items
Items
Procs’d Comb’d
with
Add
Tape
------------------- ------- ------Recognit/Data Ser
97,366
Recognit/Data Ser
96,851
Recognit/Data Ser
90,610
Recognit/Data Ser
109,197
Recognit/Data Ser
35,541
Recognition
Station
Field Number:
ANY BANK
CAV Performance Summary Report
385
386
Subtotal
Total
Debits
Total
Debits
Number of
Number of
Credit
Debit
Credits
Debits
Accuracy
Accuracy
Reclassified
Reclassified
--------- --------- -------------- -------------- ---------- ---------4,096
4,092
48
48
1.17%
98.83%
Total
Credits
Total
Credits
18/JUL/2003
Number of
Number of
Credit
Debit
Credits
Debits
Accuracy
Accuracy
Reclassified
Reclassified
------- --------- --------- -------------- -------------- ---------- ---------1000
20
0
0
0
0.00%
100.00%
1001
0
16
0
0
100.00%
100.00%
1002
4
4
0
0
0.00%
100.00%
1003
4
4
4
4
100.00%
0.00%
1004
8
8
4
4
50.00%
50.00%
1005
12
12
8
8
66.67%
33.33%
1006
16
16
4
4
25.00%
75.00%
1007
16
16
12
12
75.00%
25.00%
1008
16
16
16
16
100.00%
0.00%
1009
4,000
4,000
0
0
0.00%
100.00%
1010
0
0
0
0
100.00%
100.00%
1011
0
0
0
0
100.00%
100.00%
1012
0
0
0
0
100.00%
100.00%
1013
0
0
0
0
100.00%
100.00%
1014
0
0
0
0
100.00%
100.00%
1015
0
0
0
0
100.00%
100.00%
1016
0
0
0
0
100.00%
100.00%
1017
0
0
0
0
100.00%
100.00%
1018
0
0
0
0
100.00%
100.00%
1019
0
0
0
0
100.00%
100.00%
1020
0
0
0
0
100.00%
100.00%
1021
0
0
0
0
100.00%
100.00%
1022
0
0
0
0
100.00%
100.00%
1023
0
0
0
0
100.00%
100.00%
RSS
Dist.
RSS Station: Recognition 1 / Data Server 1
NCR Bank
RSS Reclassification Report
Page
1
ins
ri
4
4
DRN
8800101948
8800101950
8800101956
8800101958
Cycle ####
Entry ####
Batch ####
Date: 06-06-2006 16:44
Codeline
c062-204d 22233343c 682
c168655 c352-001d 325219c
c062-204d 27784893c 682
c062-204d 27789993c 682
Pocket Number
1
1
1
1
RIR Document Distribution
Tray Number
10000017
10000020
10000017
10000017
Tray Sequence
0014200001
0014300004
0014200001
0014200001
PSET # - <Pset Name>
387
388
Total
Records
Matched To
Items
% (vol)
---------------0.0% (
0)
100.0% (
1)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
100.0% (
1)
100.0% (
1)
0.0% (
0)
0.0% (
0)
0.0% (
0)
100.0% (
1)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
26/Jan/2001
----------------------------------- --------Reject Mixed Batch Header
2
Reject Mixed Batch Header
1
Reject Debit-Only Batch Header
1
2
1
Reject Credit-Only Batch Header
1
1
1
1
1
Tray Header
1
Tray Header
1
Tray Header
1
Block Trailer
1
Block Trailer
1
Block Header
1
Classification
NCR Training
Second Source Posting Date: 12/Dec/1995
Second Source Match and Merge Performance Summary Report
Not Matched
To Items
% (vol)
---------------100.0% (
2)
0.0% (
0)
100.0% (
1)
100.0% (
2)
100.0% (
1)
100.0% (
1)
0.0% (
0)
0.0% (
0)
100.0% (
1)
100.0% (
1)
100.0% (
1)
0.0% (
0)
100.0% (
1)
100.0% (
1)
100.0% (
1)
100.0% (
1)
Matched To
Deposit Slips
% (vol)
---------------0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
Forced
Matches
% (vol)
---------------0.0% (
0)
0.0% (
0)
100.0% (
1)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
0.0% (
0)
100.0% (
1)
0.0% (
0)
0.0% (
0)
100.0% (
1)
Page 1
EXCEPTION
---------
30/Aug/1999
15200
300000
AMOUNT
---------6000
AMOUNT
----------
NO
NO
ON-US
----NO
AMOUNT
---------39000
Host Entry: 3
30/Aug/1999
ON-US
----NO
Host Entry: 2
NO
NO
NO
ON-US
----NO
Host Entry: 1
30/Aug/1999
FROM ENTRY
----------
CR/DB/NP
-------DB
Operator: 222
Tray: 1000000060
Operator: 222
Page 3
d161000075d0051-03870321 c 1738
Operator: 222
d161000017d0247-02351639 c
d141000011d0053-01820702 c
RECONCILED TRAY
--------------1000000054
d161000075d0043-01608908 c 1254
c00001328c
FROM ENTRY
----------
Tray: 1000000052
Page 2
d161000075d0043-01608908 c 1254
RECONCILED TRAY
---------------
Entry: 0003-03-01-00-00-00
CR/DB/NP
--------
Tray: 329
Page 1
RECONCILED TRAY
--------------1000000038
d161000075d0051-03870321 c 1738
1000000039
c00001328c
d141000011d0053-01820702 c
1000000039
d141000011d0103-07010018 c
FROM ENTRY
----------
Entry: 0002-03-01-00-00-00
DB
DB
CR/DB/NP
-------DB
Entry: 0001-03-01-00-00-00
===================================================================================================
0108299908000551
TRUFRE
DRN
-------------------0108299908000551
0108299908000551
EXCEPTION
---------
TRUFRE
MATCH
-----TRUMIS
NCR Training
Cycle: 1
DRN
-------------------0108299908000299
MATCH
-----TRUFRE
NCR Training
Cycle: 1
0108299908000075
TRUFRE
0108299908000127
TRUMIS
DRN
-------------------0108299908000075
0108299908000077
EXCEPTION
---------
Cycle: 1
TRUMIS
MATCH
-----TRUMIS
NCR Training
389
390
Permissions:
Amount Keying
EPU Image Capture
-------------------------------------------------------------------------------Operator Name: IDT Fullname (ourbank idt operator)
Operator Number: 911
Date of Last Login:
09/01/2005
Date of Password Change:
03/19/2003
Permissions:
Codeline Completion
-------------------------------------------------------------------------------Operator Name: Grant Doe (Grant)
Date of Last Login:
04/24/2003
03/20/2003
Permissions:
Amount Keying
EPU Image Capture
-------------------------------------------------------------------------------Work Group Name: User Work Group
Work Group Number: 2
-------------------------------------------------------Operator Name: EPU operator (epsuop)
Date of Last Login:
05/07/2004
10/20/2003
Permissions:
EPU Image Capture
ESU Encode & Sort
Amount Keying
EPU Image Capture
Codeline Completion
-------------------------------------------------------------------------------Operator Name: IDT user 4 (idt04)
Operator Number: 4
Date of Last Login:
03/28/2005
03/28/2005
Operator Number: 0
09/23/2005
07/04/2001
User Permission and Login Information Report
Application Type: OurBank
---------------------------------------Work Group Name: Administration
Work Group Number: 0
-------------------------------------------------------Operator Name: ImageMark TM Base User (cp180400)
Date of Last Login:
Print date:
Operator Performance Report Samples
This section contains samples of all printable Operator Performance reports. This includes the
following:
!
!
EPU and ESU Transport Performance Statistics reports
!
!
Note: The EPU and ESU Transport Performance Summary reports show the same information as
the EPU and ESU Transport Sessions Performance reports, but accumulate the data across
all sessions of all transports in the system
!
Image Quality Review Performance Summary report
!
!
!
!
!
!
391
392
Batch
Seq.
No.
----1
1
----------12/Dec/2001
12/Dec/2001
Start
Date
-------00:00:10
00:00:10
Start
Time
-------00:00:11
00:00:11
Stop
Time
------99
99
No.
Jams
Start
Seq.
No.
-----1
1
Operator: 2
End
Seq.
No.
-----1
1
--------9,999
9,999
No.
Items
10/21/2002
------1
1
No.
Rejects
No.
Unknown
Items
------9,999
9,999
Items
Per
Min
----0
0
Rejct
Rate
%
----0.01
0.01
Page 1
Batch
Seq.
No.
----1
----------12/Dec/2001
Start
Date
-------00:00:10
Start
Time
-------00:00:11
Stop
Time
------9,999
No.
Jams
Start
Seq.
No.
-----999999
Operator: 2
End
Seq.
No.
-----999999
--------9,999
No.
Items
10/21/2002
------1
No.
Rejects
No.
Unknown
Items
------9,999
Items
Per
Min
----0
Rejct
Rate
%
----0.01
Page 2
--1
Run
No.
Batch
Seq.
No.
----1
----------12/Dec/2001
Start
Date
Banking Center: 8888
Station: 4
-------00:00:01
Start
Time
-------00:00:01
Stop
Time
------8,888
No.
Jams
Start
Seq.
No.
-----888888
Operator: 2
End
Seq.
No.
-----88
--------8,888
No.
Items
10/21/2002
------1
No.
Rejects
No.
Unknown
Items
------8,888
Items
Per
Min
----0
Rejct
Rate
%
----0.01
Page 3
================================================================================================================
9,999 999999 999999
9,999
1
9,999
0
0.01
--1
Run
No.
Banking Center: 9999
Station: 3
================================================================================================================
198 1
1
19,998
2
19,998
0
0.01
--1
1
Run
No.
Banking Center: 99
Station: 2
Session
End
Time
127
Session
Run
Time
Total
No.
Items
Session
End
Time
Total
No.
Items
Session
Run
Time
Total
No.
Items
Session
Start
Time
Station:
Session
End
Time
127
Session
Run
Time
Total
No.
Items
Downtime
from
Transport
Failures
Average No. of
Downtime Average
No. of
Transport from Jams Downtime
Items
Jams
from Jams
per hour
No. of
Other
Transport
Failures
No. of
Other
Transport
Failures
Downtime
from
Transport
Failures
Downtime
from
Transport
Failures
Downtime
from
Transport
Failures
-------- -------- ----3,182
No. of
No. of
No. o
Rejected Fields
Field
Images
Rejected Misre
150
-------- -------- ----2,858
No. of
No. of
No. o
Rejected Fields
Field
Images
Rejected Misre
-------- -------- ----1,062
No. of
No. of
No. o
Rejected Fields
Field
Images
Rejected Misre
Page 1
Average
No. of
No. of
No. o
Downtime Rejected Fields
Field
from
Images
Rejected Misre
Transport
Failures
Average
Downtime
from
Transport
Failures
--------- --------- --------- --------- --------00:54:38 00:00:08
00:00:00 00:00:00
Average No. of
Downtime Average
No. of
Items
Jams
from Jams
per hour
No. of
Other
Transport
Failures
Average
Downtime
from
Transport
Failures
--------- --------- --------- --------- --------01:03:24 00:00:11
00:00:00 00:00:00
00:00:00 00:00:00
00:00:00 00:00:00
00:03:54 00:00:04
00:00:00 00:00:00
Average No. of
Downtime Average
No. of
Items
Jams
from Jams
per hour
---------- -------- -------- -------06:30:24
100,600
15,461
344
00:15:11
00:56:16
4,821
5,141
48
Session
Run
Time
-------- -------- ---------- -------- -------- -------13:02:59 22:13:05 09:08:17
104,937
11,484
365
Session
Start
Time
127
-------20:32:54
20:50:04
21:54:46
-------12:58:37
20:34:53
20:57:46
Station:
Session
End
Time
127
Session
Start
Time
Station:
No. of
Other
Transport
Failures
Average
Downtime
from
Transport
Failures
--------- --------- --------- --------- --------00:11:42 00:00:07
00:00:00 00:00:00
Average No. of
Downtime Average
No. of
Items
Jams
from Jams
per hour
01/Jan/2003 to 02/Feb/2003
-------- -------- ---------- -------- -------- -------13:04:49 20:15:48 07:07:28
37,947
5,326
94
Session
Start
Time
Station:
ANY BANK
EPU Transport Sessions Performance Report
393
394
Session
End
Time
026
Session
Run
Time
Session
End
Time
029
Session
Run
Time
Session
End
Time
029
Session
Run
Time
Session
End
Time
039
Session
Run
Time
-------- -------- ---------16:07:21 23:29:09 04:46:16
Session
Start
Time
Station:
-------- -------- ---------16:33:56 00:31:28 05:11:34
Session
Start
Time
Station:
-------- -------- ---------15:36:43 00:26:46 07:30:47
Session
Start
Time
Station:
-------- -------- ---------20:47:44 00:26:00 03:16:00
Session
Start
Time
Station:
ANY BANK
No. of
Other
Transport
Failures
Downtime
from
Transport
Failures
Average No. of
Downtime Average
No. of
Items
Jams
from Jams
per hour
No. of
Other
Transport
Failures
No. of
Other
Transport
Failures
Downtime
from
Transport
Failures
Downtime
from
Transport
Failures
Downtime
from
Transport
Failures
Average
Downtime
from
Transport
Failures
-------- -------- --------- --------- --------- --------- --------- --------40,631
8,516
222
00:25:54 00:00:07
00:00:00 00:00:00
Total
No.
Items
Average No. of
Downtime Average
No. of
Items
Jams
from Jams
per hour
No. of
Other
Transport
Failures
Average
Downtime
from
Transport
Failures
-------- -------- --------- --------- --------- --------- --------- --------35,561
6,848
176
00:43:17 00:00:14
00:00:00 00:00:00
Total
No.
Items
Average No. of
Downtime Average
No. of
Items
Jams
from Jams
per hour
Average
Downtime
from
Transport
Failures
-------- -------- --------- --------- --------- --------- --------- --------34,500
4,592
295
00:49:16 00:00:10
00:00:00 00:00:00
Total
No.
Items
Average No. of
Downtime Average
No. of
Items
Jams
from Jams
per hour
01/Jan/2003 to 02/Feb/2003
Average
Downtime
from
Transport
Failures
-------- -------- --------- --------- --------- --------- --------- --------22,276
6,819
223
00:24:17 00:00:06
00:00:00 00:00:00
Total
No.
Items
ESU Transport Sessions Performance Report
---------
No. of
MICR
Verify
Errors
---------
No. of
MICR
Verify
Errors
---------
No. of
MICR
Verify
Errors
---------
No. of
MICR
Verify
Errors
Page 1
Avg.
Hourly
Rate
Page 1
********** END OF REPORT **********
Total
No.
Images
(keyers)
15/Feb/2006 to 22/Feb/2006
Total
No.
Images
Rejected
-------- ---------- ------- ------- --------9 00:01:54
9
284.2
7
919 00:16:40
85
306.0
8
Operator Action
Number
Time
Activity: Image Quality Review
Wells Fargo Bank
Image Quality Review Performance Summary Report
395
396
Session
End
Time
-------13:14:17
11:58:10
11:58:36
13:41:00
14:25:52
16:29:45
16:31:00
16:36:31
Session
End
Time
-------11:54:54
-------00:41:13
Session
Duration
-------00:00:05
00:44:44
00:00:22
00:00:52
00:00:05
00:06:43
00:01:14
00:05:29
Session
Duration
Session
Start
Time
---------11:10:59
11:15:16
15:26:59 *
15:28:49
15:37:38
16:46:48 *
16:52:34
16:58:01 *
Session
End
Time
-------11:14:18
11:17:14
15:27:26
15:32:04
16:08:00
16:51:26
16:56:28
17:12:17
-------00:03:19
00:01:58
00:00:27
00:03:15
00:30:22
00:04:38
00:03:54
00:14:16
Session
Duration
Station: scaw-podbuild
Session
Start
Time
---------11:13:41
Station: idt060-2
Session
Start
Time
---------13:14:12
11:13:26 *
11:58:14
13:40:08
14:25:47
16:23:02
16:29:46
16:31:02
Station: IDT060
NCR Training
Lost
Action
Time
-------00:00:00
00:12:35
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
Wait For
Work
Time
-------00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
Lost
Action
Time
-------00:00:00
Wait For
Work
Time
-------00:00:00
Session
Action
Time
-------00:03:16
00:01:47
00:00:27
00:02:14
00:28:01
00:01:08
00:03:47
00:00:21
Lost
Action
Time
-------00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:03:11
00:00:00
00:13:14
Wait For
Work
Time
-------00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
Activity: Block Balancing
Session
Action
Time
-------00:39:31
Session
Action
Time
-------00:00:03
00:30:54
00:00:16
00:00:03
00:00:03
00:06:42
00:01:12
00:05:27
Block Balancing Operator Sessions Activity Report
Total
Suspend
Duration
--------
Total
Suspend
Duration
--------
-------00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
System
Overhead
Total
Suspend
Duration
--------
Operator: 1
-------00:00:18
System
Overhead
Operator: 1
-------00:00:00
00:00:16
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
System
Overhead
Operator: 1
Suspend
Start
Time
--------
Suspend
Start
Time
--------
Suspend
Start
Time
--------
22/Oct/2004 to 26/Oct/2004
(Administration)
--------
Suspend
Duration
--------
Suspend
Duration
--------
Suspend
Duration
-----------
Reason
-----------
Reason
-----------
Reason
Page 1
Session
End
Time
-------13:14:17
11:58:10
11:58:36
13:41:00
14:25:52
16:29:45
16:31:00
16:36:31
Session
End
Time
-------11:54:54
-------00:41:13
Session
Duration
-------00:00:05
00:44:44
00:00:22
00:00:52
00:00:05
00:06:43
00:01:14
00:05:29
Session
Duration
Session
Start
Time
---------11:10:59
11:15:16
15:26:59 *
15:28:49
15:37:38
16:46:48 *
16:52:34
16:58:01 *
17:16:03 *
17:32:29 *
18:31:20 *
Session
End
Time
-------11:14:18
11:17:14
15:27:26
15:32:04
16:08:00
16:51:26
16:56:28
17:12:17
17:32:19
17:40:53
18:32:37
-------00:03:19
00:01:58
00:00:27
00:03:15
00:30:22
00:04:38
00:03:54
00:14:16
00:16:16
00:08:24
00:01:17
Session
Duration
Session
Start
Time
---------11:13:41
Station: idt060-2
Session
Start
Time
---------13:14:12
11:13:26 *
11:58:14
13:40:08
14:25:47
16:23:02
16:29:46
16:31:02
Lost
Action
Time
-------00:00:00
00:12:35
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
Wait For
Work
Time
-------00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
Lost
Action
Time
-------00:00:00
Wait For
Work
Time
-------00:00:00
Session
Action
Time
-------00:03:16
00:01:47
00:00:27
00:02:14
00:28:01
00:01:08
00:03:47
00:00:21
00:00:21
00:00:21
00:01:17
Lost
Action
Time
-------00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:03:11
00:00:00
00:13:14
00:15:52
00:07:59
00:00:00
Wait For
Work
Time
-------00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
Activity: Deposit Review
Session
Action
Time
-------00:39:31
Session
Action
Time
-------00:00:03
00:30:54
00:00:16
00:00:03
00:00:03
00:06:42
00:01:12
00:05:27
Total
Suspend
Duration
--------
Total
Suspend
Duration
--------
-------00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
System
Overhead
Total
Suspend
Duration
--------
Operator: 1
-------00:00:18
System
Overhead
Operator: 1
-------00:00:00
00:00:16
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
System
Overhead
Suspend
Start
Time
--------
Suspend
Start
Time
--------
Suspend
Start
Time
--------
Operator: 1
Station: IDT060
22/Oct/2006 to 26/Oct/2006
(Administration)
NCR Training
Deposit Review Operator Sessions Activity Report
--------
Suspend
Duration
--------
Suspend
Duration
--------
Suspend
Duration
-----------
Reason
-----------
Reason
-----------
Reason
Page 1
397
398
01:18:36
256
283
373
270
603
436
260
1,476
116
1,587
216.0
285.6
207.8
611.0
466.6
441.1
629.9
745.7
826.3
3
5
3
8
5
3
19
1
21
Total
No.
Items
Rekeyed
------- ------574.2
9
Avg.
Hourly
Rate
1
1
1
3
1
8
4
3
Total
Keyed
Fields
Corr’d
------7
2,742
3,696
2,691
5,873
4,215
2,625
14,310
1,075
15,372
No.
Actual
Key
Strokes
------6,481
2,889
3,876
2,831
6,053
4,332
2,670
14,668
1,084
16,174
No.
Key
Strokes
Credits
------6,728
29/Aug/1999
2093.1
2829.8
2070.9
5950.7
4510.7
4453.3
6106.7
6910.7
8003.9
Avg.
Hourly
Key
Strokes
------5563.1
(Training)
No. of
EXP PC
Keyed/
Errors
-------
4
6
2
12
6
4
7
48
91
92
83
73
211
1
62
No. of
TRANSIT
Keyed/
Errors
------117
1
23
299
2
10
No. of
SERIAL
Keyed/
Errors
------2
257
1
343
575
1
218
425
1,417
2
265
No. of
ACCOUNT
Keyed/
Errors
------597
3
1,430
1
115
16
1
29
14
17
1
18
1
24
65
2
No. of
TRANCOD
Keyed/
Errors
------17
3
76
10
12
2
21
1
8
25
1
14
7
5
40
No. of
AMOUNT
Keyed/
Errors
------18
Page 1
********** END OF REPORT **********
01:18:22
255
00:56:04
242
01:17:58
00:35:22
241
244
02:20:36
240
00:59:13
00:09:20
239
243
01:55:14
228
Total
No.
Items
Pres’d
-------- -------- ------227
01:09:54
669
Operator Action
Number
Time
Activity: Codeline Completion
NCR Training
Codeline Completion Operator Performance Summary Report
Avg.
Hourly
Rate
01:02:20
00:58:41
02:37:07
00:08:10
01:05:57
03:11:36
01:18:26
00:17:50
05:14:45
022
067
128
156
189
347
455
623
677
7,632
752
2,714
7,215
3,083
229
3,728
916
2,721
636
1454.9
2530.1
2076.2
2259.4
2804.9
1682.4
1423.7
936.6
2619.1
1720.2
107
47
59
110
85
1
68
2
18
9
37,059
3,882
13,952
37,959
14,838
1,116
18,720
4,808
13,587
3,266
No.
Actual
Key
Strokes
------30,368
8833.7
Avg.
Hourly
Key
Strokes
------7862.8
8199.2
7148.8
4915.9
37,059
7064.5
3,882 13060.9
13,968 10673.0
37,959 11887.0
14,838 13499.3
1,116
18,725
4,808
13,587 13078.4
3,266
No.
Key
Strokes
Credits
------30,368
29/Aug/1999
No. of
EXP P/C
Keyed/
Errors
-------
(Training)
No. of
SERIAL
Keyed/
Errors
-------
No. of
BANK
Keyed/
Errors
-------
No. of
ACCOUNT
Keyed/
Errors
-------
No. of
AMOUNT
Keyed/
Errors
------5,994
74
636
9
2,708
1
17
907
2
3,708
68
227
1
3,066
85
7,185
110
2,707
1
58
754
47
7,617
107
No. of
TRNCODE
Keyed/
Errors
-------
Page 1
********** END OF REPORT **********
00:22:11
014
Total
No.
Items
Total
Keyed
Fields
Corr’d
-------- ---------- ------- ------- ------003
03:51:44
6,014 1557.1
74
Operator Action
Number
Time
Activity: Amount Keying
NCR Training
Amount Keying Operator Performance Summary Report
399
400
---------05:44:53 *
02:22:07
06:07:39 *
04:09:47 *
04:29:20 *
05:58:27
04:20:14 *
03:36:31 *
04:36:50 *
02:44:03
06:11:07 *
05:17:47
04:18:04 *
03:14:49 *
06:09:45
03:29:58 *
04:46:02 *
--------008
013
050
051
055
056
058
060
064
066
069
070
074
076
078
136
141
Total
No.
Items
--------21,476
15,790
25,766
19,237
24,038
27,665
31,277
24,896
25,270
15,204
42,432
18,116
28,314
10,802
28,977
25,568
29,955
Avg.
Hourly
Rate
--------3,736.2
6,666.4
4,205.0
4,620.9
5,355.0
4,630.8
7,211.3
6,899.1
5,476.9
5,560.7
6,860.2
3,420.4
6,583.0
3,326.8
4,702.2
7,306.3
6,283.5
Total
No.
Batches
--------127
73
142
99
135
133
148
131
117
73
213
89
127
50
132
152
151
Total No.
Items
Inserted
--------126
113
222
117
140
185
129
142
162
78
252
98
166
82
183
192
147
Total No.
Fields
Keyed
--------852
513
840
749
869
1,068
1,135
974
1,012
574
1,788
641
1,150
412
1,047
957
1,049
01/Jan/2003 to 02/Feb/2003
2
2
1
7
Total No.
Keyd Flds
Corrected
--------2
(Administration)
No.
Images
Rejected
---------
No.
Actual
Keystroke
--------7,331
5,245
8,743
6,398
7,629
9,905
8,803
8,051
8,180
4,611
12,344
5,311
8,439
3,530
9,311
9,017
8,342
No.
Keystroke
Credits
--------9,544
7,288
13,061
8,422
10,056
13,261
11,188
10,786
11,063
5,981
18,705
6,981
11,669
5,036
12,351
12,383
10,962
Page 1
********** END OF REPORT **********
Action
Time
Operator
Number
Activity: Balancing
ANY BANK
Balancing Operator Performance Summary Report
Total
No.
Items
--------
2
---------00:03:16
00:01:47
00:00:27 *
00:02:14
00:28:01
00:01:08 *
00:03:47
00:00:21 *
00:00:21 *
00:00:21 *
00:01:17 *
00:00:22 *
Total
No.
Items
-------86
114
Avg.
Total No. Total No. Total No.
Hourly
Items
Fields
Keyd Flds
Rate
Inserted Keyed
Corrected
-------- --------- --------- --------1,579.6
3,835.5
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
No.
Blocks
Batches
Batches
MICR
Misenc
Miskey
Images
Split
Split
Moved
Misreads
Rejected
-------- -------- --------- ---------- --------- -------- -------
6
Action
Time
Operator: 1
9
No.
Blocks
Batches
Batches
MICR
Misenc
Miskey
Images
Split
Split
Moved
Misreads
Rejected
-------- -------- --------- ---------- --------- -------- -------
Operator: 1
Page 1
No.
Blocks
Batches
Batches
MICR
Misenc
Miskey
Images
Split
Split
Moved
Misreads
Rejected
-------- -------- --------- ---------- --------- -------- ------2
2
Operator: 1
Avg.
Hourly
Items
Fields
Keyd Flds
Rate
Inserted Keyed
Corrected
-------- --------- --------- --------0.0
97.1
10
34
0.0
0.0
0.0
0.0
0.0
0.0
22/Oct/2004 to 26/Oct/2004
(Administration)
Total
Avg.
No.
Hourly
Items
Fields
Keyd Flds
Items
Rate
Inserted Keyed
Corrected
---------- -------- -------- --------- --------- --------00:39:31
114
173.1
22
18
Action
Time
---------00:00:03
00:30:54 *
50
00:00:16
00:00:03
00:00:03
00:06:42
00:01:12
00:05:27
Station: idt060-2
Action
Time
Station: IDT060
NCR Training
Block Balancing Operator Performance Detail Report
401
402
--------32
22
--------52
10
--------10
3
---------
Total No.
Holds
Removed
Total No.
Items
Made
Non-Nego
tiable
---------
Operator: bb77174
---------
Total No.
of Hold
Deposits
No Change
---------
Total No of
NonNegotiable
Deposits
No Change
---------11
Total No
of
Deposits
Returned
Completed
--------8
Page 1
Total No
Deposits
Returned
Incomplete
********** END OF REPORT **********
-----165.9
112.1
-------364
83
-------02:11:38
00:44:25
Total No.
Holds
Applied
Total No.
Deposits
Hold
Reviewed
Total No.
Deposits
Reviewed
Action
Time
Total No.
Deposits
Non-Neg.
Reviewed
Avg.
Hourly
Rate
(Administration)
22/Oct/2006 to 26/Oct/2006
Station: YourBank23
Your Bank
Deposit Review Operator Performance Detail Report
Total No
of
Deposits
Timed
Out
--------22
Cum.
Total
No.
Items
---------
Cum.
Avg.
Hourly
Rate
---------
Cum
Cum.
Cum.
Items
Fields
Keyd Flds
Inserted Keyed
Corrected
--------- --------- ---------
Cum.
No.
Images
Rejected
---------
22/Oct/2004 to 26/Oct/2004
--------0
Cum.
Blocks
Split
(Administration)
Cum.
Batches
Moved
Cum.
MICR
Misreads
Cum.
Misenc
Cum.
Miskey
---------- ---------- ----------- --------- ---------0
0
0
0
0
Cum.
Batches
Split
Page 1
********** END OF REPORT **********
-----------0000:00:04
Cum.
Action
Time
Activity: Offline Expert Block Balancing
NCR Training
Expert Block Balancing Operator Grand Total Performance Report
403
404
Cum.
Total No.
KeyFields
Corrected
--------7
Cum.
No.
Images
Rejected
---------
(Workgroup 4
Cum.
No.
Actual
Keystroke
--------20,273
Cum.
No.
Keystroke
Credits
--------27,475
Page 1
********** END OF REPORT **********
Cum.
Total No.
Fields
Corrected
--------2,207
30/Aug/1999
Cum.
Cum.
Cum.
Cum.
Total
Avg.
Total
Total No.
No.
Hourly
No.
Items
Items
Rate
Batches
Inserted
---------- --------- --------- --------- --------11:21:36 *
77,055
6,783.0
382
435
Cum.
Action
Time
Activity: Balancing
NCR BANK
Balancing Operator Grand Total Performance Report
--------9,999,999
9,999,999
9,999,999
-------99:99:99
99:99:99
99:99:99
-------9,999.99
9,999.99
9,999.99
Cum.
Avg.
Hourly
Rate
--------9,999,999
9,999,999
9,999,999
Total No.
Deposits
Created
for Review
-------9,999.99
9,999.99
9,999.99
Avg.
Hourly
Rate
------------999,999
999,999
999,999
Cum. Total No
Deposits
NonNegotiable
Reviewed
Total No.
Deposits
Created for
Hold
Review
---------9,999,999
9,999,999
9,999,999
Total No.
Deposits
Created for
NonNegotiable
Review
------------999,999
999,999
999,999
Activity: %comp_type_name
--------9,999,999
9,999,999
9,999,999
Cum.
Total No.
Deposits
Hold
Reviewed
--------9,999,999
9,999,999
9,999,999
Cum.
Total No
Holds
Reviewed
--------9,999,999
9,999,999
9,999,999
Total No
Automatic
Holds
Applied
------------9,999,999
9,999,999
9,999,999
Total No.
Automatic
NonNegotiable
Changes
Cum.
Total No
of Hold
Deposits
No
Change
-------999,999
999,999
999,999
----------999,999
999,999
999,999
Total No
Deposits
Flagged for
ReReview
---------999,999
999,999
999,999
Cum.
Total No.
Items
NonNegotiable
Operator: Autorole
--------9,999,999
9,999,999
9,999,999
Cum.
Total No
Holds
Applied
01/Jan/2006 to 02/Feb/2006
(Administration)
--------999,999
999,999
999,999
Total No
Deposits
Processed
------------999,999
999,999
999,999
Cum.
Total No of
NonNegotiable
Deposits No
Change
Page 1
********** END OF REPORT **********
-------99:99:99
99:99:99
99:99:99
Action
Time
Station: %station_name
Cum.
Total No.
Deposits
Reviewed
Cum.
Action
Time
Activity: Codeline Completion
ANY BANK
Deposit Review Operator Grand Total Performance Report
---------999,999
999,999
999,999
Cum.
Total No
Deposits
Returned
Incomplete
----------999,999
999,999
999,999
Cum.
Total No of
Deposits
Returned
Completed
--------999,999
999,999
999,999
Cum.
Total No
of
Deposits
Timed Out
405
406
---------14:05:35
14:31:18
14:33:34
14:57:12
15:08:00
18:34:56 *
18:43:41
18:53:29
19:03:43
21:32:52
21:42:04
22:09:00
22:11:06
---BAL
CLC
BAL
CLC
BAL
BAL
BAL
CLC
BAL
CLC
BAL
BAL
EBAL
-------14:31:16
14:33:33
14:57:10
15:07:58
17:55:04
18:43:36
18:53:26
19:03:41
21:32:49
21:42:02
22:02:02
22:11:05
22:16:56
SESSION
END TIME
-------00:25:41
00:02:15
00:23:36
00:10:46
02:47:04
00:08:40
00:09:45
00:10:12
02:29:06
00:09:10
00:19:58
00:02:05
00:05:50
SESSION
DURATION
SESSION
ACTION
TIME
-------00:23:35
00:02:01
00:23:36
00:10:26
02:25:02
00:08:40
00:09:45
00:09:54
01:52:14
00:08:53
00:19:58
00:02:03
00:05:48
WAIT FOR
WORK
TIME
-------00:00:01
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:02
00:00:02
WAIT FOR
WORK
%
-------0.06
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
1.60
0.57
WORK
READY
TIME
--------
WORK
READY
%
--------
01/Jan/2003 to 02/Feb/2003
Workgroup: Administration
-------00:02:05
00:00:00
00:00:00
00:00:00
00:22:02
00:00:00
00:00:00
00:00:00
00:36:52
00:00:00
00:00:00
00:00:00
00:00:00
SUSPEND
DURATION
SYSTEM
OVERHEAD
%
-------0.00
10.37
0.00
3.10
0.00
0.00
0.00
2.94
0.00
3.09
0.00
0.00
0.00
Operator: 008
---------17:04:21
17:27:53
18:33:01
19:33:38
20:40:31
---BAL
BAL
BAL
BAL
BAL
-------17:19:00
18:21:55
18:50:50
20:40:25
20:40:58
SESSION
END TIME
-------00:14:39
00:54:02
00:17:49
01:06:47
00:00:27
SESSION
DURATION
SESSION
ACTION
TIME
-------00:14:39
00:42:25
00:17:49
01:06:47
00:00:27
WAIT FOR
WORK
TIME
-------00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
WAIT FOR
WORK
%
-------0.00
0.00
0.00
0.00
0.00
WORK
READY
TIME
--------
01/Jan/2003 to 02/Feb/2003
Workgroup: Administration
WORK
READY
%
--------
-------00:00:00
00:11:37
00:00:00
00:00:00
00:00:00
SUSPEND
DURATION
SYSTEM
OVERHEAD
%
-------0.00
0.00
0.00
0.00
0.00
Operator: 013
==============================================================================================================
TOTALS:
Duration: 02:33:44
Action Time: 02:22:07
Wait For Work Time: 00:00:00
SESSION
START TIME
ACTV
ANY BANK
==============================================================================================================
TOTALS:
Duration: 07:24:08
Action Time: 06:21:55
Wait For Work Time: 00:00:05
SESSION
START TIME
ACTV
ANY BANK NA
Auto-Activity Report Samples
This section contains samples of all printable Auto-Activity reports. This includes the following:
!
!
!
Entry Item reports
!
!
All Items report
!
!
!
Suspense Items In EPU Kill Pockets report
!
!
Items Reassigned from EPU Kill Pocket report
!
Items Pull report
!
SMM Results report
!
!
Tray Set reports
!
!
!
!
Reassigned Pocket: ESU Operator Matched Item Audit report
ATM reports
!
407
408
DR COUNT
-------0
TOTAL DR+CR COUNT
-----------------0
CR TOTAL
---------------0.00
DR TOTAL
---------------0.00
Block: 1000000007
Page 1
DR COUNT
-------0
37
55
55
TOTAL DR+CR COUNT
-----------------0
46
61
69
Entry: 3
CR TOTAL
---------------0.00
8,989.15
9,366.73
9,494.83
DR TOTAL
---------------0.00
8,989.15
9,366.73
9,494.83
Block: 1000000008
**********
END OF REPORT
**********
Block Totals:
187
29
147
176
27,850.71
27,850.71
-----------------------------------------------------------------------------------------------------Entry Totals:
210
29
147
176
27,850.71
27,850.71
CR COUNT
-------0
9
6
14
Host Entry: 3
BATCH No.
TOTAL ITEMS
-------------- ----------1000000015
3
0510
47
0519
64
0516
73
Cycle: 1
Block Totals:
23
0
0
0
0.00
0.00
------------------------------------------------------------------------------------------------------
CR COUNT
-------0
Entry: 3
NCR Training Entry Summary Report
Host Entry: 3
BATCH No.
TOTAL ITEMS
-------------- ----------1000000014
23
Cycle: 1
Date: 29/Aug/1999
BATCH No.
--------0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
0515
Cycle: 1
TYPE RECORD
DISTRIBUTION NAME
---- ------ --------------------10 TRANSIT_ITEM_2
10 TRANSIT_ITEM_2
9 TRANSIT_ITEM_1_HIGH_
31 ADJ_PIGGY_BACK_DR
11 TRANSIT_ITEM_3
13 ONUS_PERSONAL_CHK
11 TRANSIT_ITEM_3
11 TRANSIT_ITEM_3
CR
16 ONUS_PERSONAL_DEPOSI
11 TRANSIT_ITEM_3
11 TRANSIT_ITEM_3
11 TRANSIT_ITEM_3
CR
CR
25 ADJ_TELLER_ERROR_CR
7 CASH_IN
11 TRANSIT_ITEM_3
CR
23 RESEARCH_CREDIT_OUTS
11 TRANSIT_ITEM_3
11 TRANSIT_ITEM_3
11 TRANSIT_ITEM_3
11 TRANSIT_ITEM_3
11 TRANSIT_ITEM_3
25 ADJ_TELLER_ERROR_DR
CR
7 CASH_IN
NP
22 NON_ITEM
Entry: 1
NCR Training All Items Report
Host Entry: 1
DRN
-----------------0108299908000201
0108299908000202
0108299908000203
0108299908000204
0108299908000200
0108299908000205
0108299908000206
0108299908000195
0108299908000207
0108299908000208
0108299908000209
0108299908000197
0108299908000210
0108299908000211
0108299908000212
0108299908000213
0108299908000214
0108299908000215
0108299908000211
0108299908000216
0108299908000216
0108299908000217
0108299908000218
0108299908000219
0108299908000220
0108299908000221
0108299908000222
0108299908000223
0108299908000224
0108299908000225
0108299908000226
0108299908000227
0108299908000228
0108299908000229
0108299908000230
0108299908000223
0108299908000231
0108299908000232
0108299908000233
0108299908000234
0108299908000235
Date: 29/Aug/1999
EXPT
SERIAL
FRDABA
ACCOUNT
TRAN
AMOUNT
---- ---------- --------- -------------- ------- ---------161000075
043802161988
1342
19500
161000075
043901675337
1159
7500
160000513
044001500624
17500
160000513
044100908153
19500
P
12121 161000017
69006900
10000
141000011
044203491514
19500
161000017
044303096449
17500
S
127603 141000011
030302362111
6000
160000513
044400200116
19500
141000011
044506560470
28000
161000017
044603106030
10000
S
160000513
030500056962
2000
160000513
044705673111
10000
161000017
044803335699
96
22000
141000011
044901481803
4000
141000011
045001142409
3000
141000011
045100202085
500
160000513
045202002290
10000
A
161000017
044803335699
4500
161000017
045303151559
96
146601
A
161000017
61211297
96
43123
007126 612122004
0454
96
90000
161000017
045503001244
38194
160000513
045601000674
4929
160000513
045700714564
17172
160000513
045801000806
16109
141000011
045901652281
23320
009577 60700000
0460
96
296851
015339 160000513
046100009035
45000
123456 141000011
046200616026
80470
123457 141000011
046300616026
39253
161000017
046403371790
30000
123458 141000011
046500616026
36989
123459 141000011
046600616026
443
123460 141000011
046700616026
55696
A
161000017
61211297
9000
161000017
046803187551
96
84692
006562 612122004
0469
11461
160000513
047000904138
11194
66556655
0471
160000513
047200508149
8298
Page 4 of 5
409
410
9494.83
0.00
Host Entry: 3
Block: 1000000008
DRN
AMOUNT
TYPE EXPT
------------------ ---------- ---- ---0108299908000657
262551
A
0108299908000663
107200
CR
0108299908000664
5000
0108299908000665
2500
0108299908000666
5000
0108299908000667
2500
0108299908000668
2500
0108299908000669
57200
0108299908000670
2500
0108299908000671
2500
0108299908000663
27500
A
0108299908000672
30000
CR
0108299908000673
15000
0108299908000674
15000
0108299908000675
17500
CR
0108299908000677
7500
0108299908000678
10000
0108299908000679
57916
O
0108299908000676
172571
CR
0108299908000680
13922
0108299908000681
34132
0108299908000682
2571
0108299908000683
1889
0108299908000684
30000
0108299908000685
2728
0108299908000676
87329
A
Header Amount: 0.00<NP>
Total Credits:
9494.83
Total NPCR...:
0.00
Entry: 3
NCR Training Batch Proof List Report
DRN
AMOUNT
TYPE EXPT
------------------ ---------- ---- ---0108299908000618
949483 NP
0108299908000619
73794 CR
0108299908000620
2835
0108299908000621
4000
0108299908000622
10107
0108299908000623
23852
0108299908000624
3000
0108299908000625
2000
0108299908000626
2000
0108299908000627
3000
0108299908000628
23000
0108299908000629
37750 CR
0108299908000630
8000
0108299908000631
2500
0108299908000632
20798
0108299908000633
6452
0108299908000634
38500 CR
0108299908000635
20000
0108299908000636
10000
0108299908000637
500
0108299908000638
2500
0108299908000639
2500
0108299908000634
3000
A
0108299908000640
43269 CR
0108299908000641
42603 NP
0108299908000642
529
0108299908000643
137
0108299908000640
42603
A
0108299908000644
76078 CR
0108299908000645
35631
0108299908000646
27710
O
0108299908000647
18007
0108299908000648
4400
0108299908000649
18040
0108299908000650
10000 CR
0108299908000651
42270 CR
0108299908000652
26135
Items in Batch.: 73
Total Debits...:
Total NPDR.....:
Cycle: 1
Date: 29/Aug/1999
Batch: 0516
Page 1 of 1
**********
BATCH No.
-----------0520
0517
0517
0517
0517
0517
0517
0517
0517
0517
0517
0514
0514
0514
0514
0514
Cycle: 1
Host Entry: 2
Entry: 2
END OF REPORT
**********
Page 1 of 1
FRDABA
ACCOUNT
TRAN
AMOUNT
--------- -------------- ------ ---------161000017
019902100080
4000
161000017
013901142376
3809
161000017
015902434590
11089
161000017
016602244202
96
13500
161000017
61221296
10
161000017
61211297
54059
161000017
019402320179
17500
161000017
69006900
52598
161000017
61211297
14400
160000513
014201200830
6240
161000017
022102083943
33260
161000017
03000309
1100
161000017
61211297
96
4000
161000017
61211297
96
2000
161000017
61211297
15200
161000017
61211297
10000
NCR Training Adjustments / Corrections Report
DRN
ADJ SERIAL
FIELD 10 FIELD 9
------------------ --- ---------- -------- ------0108299908000375
0108299908000317
0108299908000337
18
0108299908000344
15
0108299908000351
41
00326719
0108299908000351
22
0108299908000370
15
0108299908000383
32
12
0108299908000389
26
0108299908000320
0108299908000396
19
0108299908000422
18
0108299908000425
23
0108299908000427
23
0108299908000431
22
0108299908000443
25
Date: 29/Aug/1999
411
412
7
7
1701638
1701638
ANY BANK
50001
50001
50001
18 (Debit)
18 (Debit)
18 (Debit)
CLASSIFICATION
-------------------------18 (Debit)
Entry: 3741
5000
4000
5000
AMOUNT
---------67200
Suspense Items in EPU Kill Pockets Report
BTM BATCH NO.
------------50001
**********
01 74144886
01 74143197
01 74142621
DRN
----------01 74142570
Host Entry: 3741
END OF REPORT
6
1701637
**********
POCKET
-----7
TRAY NO.
-------1701638
Cycle: 1
Date: 7/Apr/2004
d061000010d
d061000010d
d502111002d
d061000010d
10 211 403c 5458
10 420 898c 4297
12206c
64 829 065c 2388
CODELINE
------------------------------
Page 1
**********
TRAY NO.
-------1701635
1701635
1701635
1701635
1701635
Cycle: 1
ANY BANK
**********
DRN
------------74139892
74141971
74142620
74143196
74144885
SERIAL
-----150846
TRANSIT
--------061112788
325272021
Entry: 3741
ACCOUNT
-------------000101111566
808943545
Suspense Items in EPU Reject Pocket Report
BTM BATCH NO.
------------50001
50001
50001
50001
Host Entry: 3741
END OF REPORT
TRAY SEQ
---------108
1334
1658
1921
2543
Date: 12/Apr/2004
3258
TRNCOD
------
AMOUNT
---------7300
10000
5000
Page 1
413
414
5
6
8
5
5
5
5
325
326
328
325
325
325
325
7
7
6
6
1
1
2
2
NEW PKT
------6
**********
D
D
D
D
D
D
R
R
REASON
-----D
0108299908000675
0108299908000672
0108299908000655
0108299908000654
0108299908000641
0108299908000591
0108299908000542
0108299908000512
DRN
-------------------0108299908000510
Entry: 3
Page 1
CLASSIFICATION
AMOUNT
CODELINE
------------------------------------- ---------- -------81 (Deposit Slip)
14100
c03795280c
d161000017d
96
177 (Research Credit)
77842
d161000017d
96
177 (Research Credit)
229530
d161000017d
96
5 (Unknown)
10000
d161000017d0342-02055101 c
5 (Unknown)
42603
c000982c
d612222001d0392c 96
81 (Deposit Slip)
25351
c02770452c
d161000017d
96
81 (Deposit Slip)
5000
c02770453c
d161000017d
96
81 (Deposit Slip)
30000
c03043282c
d161000017d
96
81 (Deposit Slip)
17500
c02940870c
d161000017d
96
NCR Training Items Reassigned from EPU Kill Pockets Report
Host Entry: 3
END OF REPORT
5
325
**********
ORIG PKT
-------5
TRAY NO.
-------325
Cycle: 2
Date: 29/Aug/1999
SERIAL
-----100010
Bank
--------010001
ACCOUNT
-------------9999999
TRNCOD
--------
AMOUNT
------------1000
KITCHENER_BANK
19/Mar/2001 16:45:46
Page 1
SERIAL
-----100005
100009
100006
Bank
--------124001
124001
124001
ACCOUNT
-------------12345678
12345678
12345678
TRNCOD
--------
AMOUNT
------------200
1900
10100
BANK_ONTARIO
19/Mar/2001 16:45:46
Page 2
19/Mar/2001 16:45:46
Page 3
**********
END OF REPORT
**********
Total
Total
Total
Total
Total NP
Total NP
Items
Amount
Debits
Credits
Debits
Credits
------------------ ------ ------- ------- -------- ------------ --------BANK_ONTARIO
3
12200
12200
0
0
0
KITCHENER_BANK
1
1000
1000
0
0
0
===============================================================================
Grand Total:
4
13200
13200
0
0
0
Total Name
Bank of Waterloo
Items Pull Report - Sample
...............................................................................
DRN
------------238508000013
238508000030
238508000445
Bank of Waterloo
...............................................................................
DRN
------------238508000021
Bank of Waterloo
415
416
**********
---------DB
DB
DB
DB
DB
CR/DB/NP
DRN
SERIAL
1610-0001
627637504
BANK
ACCOUNT
SERIAL
BANK
END OF REPORT
**********
------------- -------- --------000100000932
00020051610-0001
000100000933
00020051610-0001
000100000934
00020051410-0001
000100000935
00020061610-0001
000100000937
00020061610-0001
DRN
1610-0001
734549178
-----------977143125
182045561
027218030
419646961
932201602
ACCOUNT
----------
TRNCOD
----------
TRNCOD
Entry: 8222
------------- -------- --------- -----------000100000952
0002006 1410-0001 507717219
000100000953
0002006 1610-0001 932209797
000100000954
0002006 1600-0051 914745438
Dep. R/T :
Dep. Acct:
---------DB
DB
DB
CR/DB/NP
Dep. R/T :
Dep. Acct:
NCR Training
Misenocde Detail Report
Encoded
Amnt.
----------0000022672
0000001383
0000016285
0000010045
0000077671
Actual
Pocket Tray
ON-US Cnt
Amnt.
---------- -------- ------- ------------4468
7
8222001
YES
1
45454
7
8222001
YES
2
4445
3
8222001
NO
3
0000077671
1
8222001
YES
4
0000068049
7
8222001
YES
5
Encoded
Actual
Pocket Tray
ON-US Cnt
Amnt.
Amnt.
----------- ---------- -------- ------- ------------0000038837 1425
3
8222001
NO
1
0000032599 3256
7
8222001
YES
2
0000062552 2543
3
8222001
NO
3
Date: 08/Sep/2004
Page 1
The following example shows the format of the report for 3890 Capture.
In this example:
There are 5 pockets at the ESU, and 5 pockets defined in the “low-speed” sort pattern:
!
ImageMark ESU Pocket 1 – 3890 R Pocket (Exception pocket)
!
ImageMark ESU Pocket 2 – 3890 pocket 1 – on-us A
!
ImageMark ESU Pocket 3 – 3890 pocket 2 – on-us B
!
ImageMark ESU Pocket 4 – 3890 pocket 3 – on-us C
!
ImageMark ESU Pocket 5 – 3890 pocket 4 – transit
The report is sorted by DRN within “low-speed” pocket number. When a good item is keyed, and
any field is changed it becomes a low-speed item. The balancing operator is supposed to pull the
item if it was a good item, but they have changed either the amount, or a non-amount field.
In this example, 11 good items were changed at Balancing – the amount may have been changed,
and/or other non-amount fields may have changed.
!
four “on-us A” items were changed., and need to be pulled from pockets 5, 4, 4 and 30
respectively. In this example, one item was a non-proof batch header that got misread at
capture as a credit, and got re-keyed as a batch header. Likely this item doesn’t need to be
pulled, but is listed on the report just because it got keyed. A balancing G/L debit item needs
to be generated totaling $6.00 for the 3 credit items, and they need to go with the output
pocket 2 from the ESU “R” run that included entry 1234.
!
no “on-us B” items were changed
!
three “on-us C” items were changed, and need to be pulled from pockets 10, 5, and 15
respectively. Two are on-us debits, and one is an on-us credit, so two balancing items need
to be generated; a $200.00 debit, and a $400.00 credit to create balanced transactions for
these 3 items, and they need to go with the output pocket 4 from the ESU “R” run that included
entry 1234
!
four transit items were changed. and need to be pulled from pockets 4, 2, 4 & 3 respectively.
A balancing credit item needs to be generated totaling $100.00 for these 4 items, and they
need to go with the output pocket 5 from the ESU “R” run that included entry 1234. This
pocket is re-primed on the 3890.
417
418
Tray No.
1234010
1234008
1234008
99123456
99123433
1234010
1234030
1234008
1234004
1234008
1234006
10
5
15
Sub-Total:
4
2
4
3
Sub-Total:
Total:
%Bank Name
5
5
5
5
5
4
4
4
4
Low-Speed Pkt
2
2
2
2
2
Host Entry: 1234
Orig Pkt
5
4
4
30
Sub-Total:
Cycle: %cycle
Date: %date
DR
DR
DR
DR
DR
CR
DR
Type
CR
CR
NP
CR
Non-Proof:
1200000175
1200000223
1200011033
1200014888
Non-Proof:
1200000056
1200012123
1200015999
Non-Proof:
DRN
1200000123
1200000199
1200000200
1200011045
Non-Proof:
Entry: 1234
0
9999999
9999999
9999999
9999999
0
9999999
9999999
9999999
0
Serial
9999999
9999999
9999999
9999999
100456789
Credit:
999999999
999999999
999999999
999999999
Credit:
999999999
999999999
999999999
Credit:
20600
99999999
99999999
99999999
99999999
0
99999999
99999999
99999999
20000
Debit:
99999
99999
99999
99999
Debit:
99999
99999
99999
Debit:
99999
Debit:
Trncode
99999
99999
Page %page
Bank
Account
999999999 99999999
999999999 99999999
5544-5544 100456789
999999999 99999999
Credit:
600
50000
1000
2000
3000
4000
10000
10000
20000
30000
40000
300
0
Amount
100
200
OR&OEP
OEP
OR&OEP
OEP
OEP
OR&OEP
OEP
OEP
OEP
OEP
ESUMAT
ESUMAT
ESUMAT
ESUMAT
ESUMAT
ESUMAT
ESUMAT
ESUMAT
ESUMAT
ESUMAT
OEP
OR&OEP
ESUMAT
ESUMAT
EXCEPTION
--------OR&OEP
MATCH
-----ESUMAT
Cycle: 2
ANY BANK NA
01 74257477
01 74257324
01 74251031
01 74248942
01 74258097
01 74256149
01 74256148
01 74256030
01 74254779
01 74254717
01 74253981
01 74251476
DRN
-------------------01 74248585
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
ON-US
----YES
28500
40446
25000
24111
61731
28000
28000
13162
1016600
25000
56587
750215
AMOUNT
-----------189238
Entry: 3761-03-01-00-00-00
7/Apr/2004
DB
DB
DB
CR
CR
DB
CR
DB
DB
DB
CR
CR
1000003300
d06 0000 0d
67 42!
1000003300
1000003300
c007504c d06100000!!6!!b!b!6!!!!!!!!!!6!!
!0 0 9
1000003299
d502201886d !!!!2272!!!5c
1000003300
3!!!!!-!
1000003299
d!!d
1000003300
1000003300
c054603cd061000010818769513d
2
25!b!6!6!7!
3
c!c!!6c!7
7!!!!!!!!!
2 !!!!67!! 5!22!!!6!!
1000003300
d507000008dd 23 266 269 c9997
1000003300
52!
0 26
1000003300
RECONCILED TRAY
--------------1000003299
d!!!!
Operator: 123
Page 1
1000003300
c003697c d061000010d12 612 461c
FROM ENTRY
----------
Tray: 1000003292
CR/DB/NP
-------CR
OnUs Reconciled/Dispatched - Capture Reconciliation Audit Report
419
420
Entry: 3537-03-01-00-00-00
7/Apr/2004
Tray: 1000000256
Operator: 123
NO
NO
NO
******
005092
065000090
072412927
065000090
354826
2080097401
47986
2000
114372
0
0
0
DB
DB
DB
NO
061100790
9000
0
DB
NO
267077627
10605
0
DB
**********
END OF REPORT
**********
====================================================================================================
TRAY TOTALS
183963 (
5 ITEMS)
---------------------------------------------------------------------------------------------------POCKET 0 TOTALS
10605 (
1 ITEMS)
----------------------------------------------------------------------------------------------------
01 73172571
---------------------------------------------------------------------------------------------------POCKET 0 TOTALS
9000 (
1 ITEMS)
----------------------------------------------------------------------------------------------------
01 73168192
---------------------------------------------------------------------------------------------------POCKET 0 TOTALS
164358 (
3 ITEMS)
----------------------------------------------------------------------------------------------------
01 73168170
01 73172552
01 73168169
DRN
ON-US SERIAL BANK
ACCOUNT
TRNCOD AMOUNT
PKT CR/DB/NP
-------------------- ----- ------ --------- -------------- ------ ------------ --- -----------------------------------------------------------------------------------------------------------
Cycle: 1
ANY BANK NA
Capture Reconciliation Audit Pocket Summary Report
Page 1
ADJOR&SUS
TRUMIS
00110617949
00110853789
00110165679
DRN
-------------------00110291656
YES
NO
YES
ON-US
----NO
539245
357421
605559
AMOUNT
---------992918
Entry: 0002-03-01-00-00-00
29/Aug/1999
NP
NP
NP
CR/DB/NP
-------CR
FROM ENTRY
----------
Tray: 1000000052
7476
8698
6743
RECONCILED TRAY
--------------3525
0995203491
4376325102-
6983744012-
2340463791
Operator: 666
Page 29
**********
END OF REPORT
**********
----------------------------------------------------------------------------------------------------------------------TOTALS
CR:
15,407.69
DB:
409.54
NP:
22,513.08
Total # Items:
11
-----------------------------------------------------------------------------------------------------------------------
ADJOR&SUS
UNRSLV
ESUMAT
FREE
EXCEPTION
--------ADJOEP&SU
MATCH
-----ESUMAT
Cycle: 1
NCR Training - Bank 1
Reassigned Pocket - ESU Operator Matched Item Audit Report
421
422
9414.57
Host Entry Number: 2
29/Aug/1999
**********
END OF REPORT
**********
TRAY
ESU
3890
TOTAL
HEADER
POCKET POCKET
TOTAL
NUMBER
NUMBER
NUMBER NUMBER
AMOUNT
ITEMS
---------- ------ ------ ------------- -----1000000052
1
2.00
8
1000000045
2
1
0.00
4
1000000046
3
2
855.33
18
1000000047
4
3
5301.53
29
1000000048
5
4
3152.08
9
1000000049
6
5
0.00
2
1000000050
7
6
0.00
3
1000000051
8
7
0.00
2
=================================================
9310.94
75
Input Tray Amount:
Entry Number: 2
NCR Training
ESU Pocket Total Report
: 02-00-00-00-I-000
Host Entry:10
Entry: 10
Date: 30/Aug/2002
Page 1
**********
DB: $
9999-9999
9999-9999
9999-9999
9999-9999
9999-9999
**********
0.00
END OF REPORT
CR: $
00125
71189
24065550
24065551
TOTALS
00157
51256
87342
24065471
24065472
24065473
ATM Number: 24156
1,700.87
NP: $
657834
98765320134
887766554433
0.00
CR
DB
CR
DB
DB
Total #Items: 5
$250.00
$100.00
$1,350.87
2
4
2
3
4
2
7
2
3
7
DRN
SERIAL
BANK
ACCOUNT
TRAN
AMOUNT
CR/DB/NP
TRAY No.
PKT
--------------------------------------------------------------------------------------------------------------
Cycle:1
Putaway Transaction Report - Bank of Waterloo
423
This section contains a sample of the MIE Exception report.
424
=
=
=
=
005
001
89
P9901
= 001
= P9901
= 89
= SEND
= SYSTEM01
DocType
BLOCK
BATCH
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
* D
RecID
0xb2
0xb6
0x91
0x91
0x91
0x91
0x91
0x91
0x91
0x91
0x55
0x91
0x91
0x91
0x91
0x91
0x91
0x91
0x91
0x91
0x91
0x91
0x91
0x91
0x91
0x91
0x91
0x91
0x91
0x91
0x55
CorCD(HEX)
0x00(GOOD )
0x00(GOOD )
0x14(MOVDEL)
0x14(MOVDEL)
0x14(MOVDEL)
0x14(MOVDEL)
0x14(MOVDEL)
0x14(MOVDEL)
0x14(MOVDEL)
0x14(MOVDEL)
0x14(MOVDEL)
0x14(MOVDEL)
0x14(MOVDEL)
0x14(MOVDEL)
0x14(MOVDEL)
0x14(MOVDEL)
0x21(CORREJ)
0x21(CORREJ)
0x21(CORREJ)
0x21(CORREJ)
0x21(CORREJ)
0x21(CORREJ)
0x44(MOVADD)
0x44(MOVADD)
0x44(MOVADD)
0x44(MOVADD)
0x44(MOVADD)
0x44(MOVADD)
0x44(MOVADD)
0x44(MOVADD)
0x44(MOVADD)
DRN
08040602578989001895
08040602578989001896
08040602578989001907
08040602578989001908
08040602578989001909
08040602578989001910
08040602578989001911
08040602578989001912
08040602578989001913
08040602578989001914
08040602578989001915
08040602578989001916
08040602578989001917
08040602578989001918
08040602578989001919
08040602578989001920
08040602578989001924
08040602578989001925
08040602578989001926
08040602578989001927
08040602578989001928
08040602578989001929
08040602578989001907
08040602578989001908
08040602578989001909
08040602578989001910
08040602578989001911
08040602578989001912
08040602578989001913
08040602578989001914
08040602578989001915
POD
00508221400FSMG00001
00508221400FSMG00002
00508221400FSMG00049
00508221400FSMG00050
00508221400FSMG00051
00508221400FSMG00052
00508221400FSMG00053
00508221400FSMG00054
00508221400FSMG00055
00508221400FSMG00056
00508221400FSMG00057
00508221400FSMG00058
00508221400FSMG00059
00508221400FSMG00060
00508221400FSMG00061
00508221400FSMG00062
00508221400FSMG00066
00508221400FSMG00067
00508221400FSMG00068
00508221400FSMG00069
00508221400FSMG00070
00508221400FSMG00071
00508221400FSMG00072
00508221400FSMG00072
00508221400FSMG00072
00508221400FSMG00072
00508221400FSMG00072
00508221400FSMG00072
00508221400FSMG00072
00508221400FSMG00072
00508221400FSMG00072
=========================================================================
REQUEST
CommandName
SystemID
EDIT
Bank
SortPatternName
DeviceNumber
JOB
JobNumber
BankNum
Device
SortPattern
Amount
PC
ACCT
FLD4 TR
52843 098
51943
0000005555
12345678913
0000004444
12345678912
0000002222
0600120006
5526
0000000020
12345678901
0000000040
12345678901
0000000014
12345678901
0000000040
12345678901
0000000040
12345678901
0000000033
12345678901
0000007777
00600304344
9559
0000000040
12345678901
0000000040
12345678901
0000005555
12345678913
0000003333
12345678911
300
12345678901
100
12345678901
200
12345678901
300
00600304344
9559
100
12345678901
200
12345678911
0000005555
12345678913
0000004444
12345678912
0000002222
0600120006
5526
0000000020
12345678901
0000000040
12345678901
0000000014
12345678901
0000000040
12345678901
0000000040
12345678901
0000000033
12345678901
FLD6
SER
5940-0000 0323491
5500-0000 01193764
10101234
10101234
101100634
10100100
10201111
10111482
80000003
80000013
50000001
101100634
80000002
80000011
10101234
10101234
8000-0003
8000-0005
8000-0006
101100634
1020-1111
1010-1234
10101234
10101234
101100634
10100100
10201111
10111482
80000003
80000013
50000001
Pkt
11
11
13
13
16
13
21
33
21
22
64
16
22
22
13
13
15
15
15
15
15
15
13
13
16
13
21
33
21
22
64
HiLo
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
L
L
L
L
L
L
H
H
H
H
H
H
H
H
H
CapBnk
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
Commgl
1
1
1
1
1
1
1
1
1
1
98
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
98
425
426
Glossary
3890
IBM’s high-speed reader/sorter transport; processes 100,000 documents per hour.
A
Active Node
A server system that is running and participating in cluster operations.
Adjustment
An electronic procedure to correct an error in a customer deposit or teller work. Most adjustments
cause an Advice Notice to be generated.
Note: The customer could be another bank.
Advice Notice
A letter that is generated as a result of an adjustment. Includes image(s) of the relevant item(s) and
tapes (if available). Advises the customer or teller of the error and the action taken.
B
Balanced I-String
An I-string generated by the ImageMark BIE autorole, after ImageMark has balanced an entry that
was captured first pass on an EPU. Also generated from a prime I-string captured on a 3890 first
pass, which needs to be balanced, on either ImageMark or on the CPCS side.
BAP
See Base Application Processor.
427
Glossary
Base Application Processor (BAP)
A server that manages workflow and operations for the ImageMark Capture system and provides
the interface to the customer’s host system. The Base AP stores configuration and application
information, user information, workflow details, and statistical data for reports.
Batch
An NCR ImageMark Capture unit of work; a group of transactions, often assembled by the teller in
Over-the-Counter POD, or a bundle of work coming in from inclearings, typically containing 200300 items with a batch header and optional batch trailer. In large deposits or inclearings, these
batches could be considerably larger but it is recommended to keep them small.
Batch Header
A control document placed at the beginning of a batch. Must be encoded with a unique serial number
that may include the branch number.
Batch Trailer
Optional control document placed at the end of a batch.
Block
A unit of work containing many transactions. Usually begins with a block header. Typically contains
2000-3000 items. In large deposit or inclearings work, the blocks could be much larger but it is still
recommended to keep them to this size.
Block Header
A control document placed at the beginning of a block.
C
Check Processing Control System (CPCS)
Software used by banks for account posting, float, bundle lists and cash letters. CPCS resides and
runs on IBM mainframes, and normally uses IBM 3890 transports for capturing and sorting items.
Cluster
A group of independent computer systems, referred to as nodes, working together as a unified
computing resource.
Cluster Service
The essential software component that controls all aspects of server cluster operation and manages
the cluster database. Each node in a server cluster runs one instance of the cluster service.
428
Glossary
Codeline
The MICR (Magnetic Ink Character Recognition) information at the bottom of the item. Contains all
the information needed by the check clearing system.
Commingle
Commingling means processing work for multiple banks. An item called Presenting Bank Item
designates the bank being processed. In ImageMark, the presenting bank number is encoded on
the Block Header and the presenting bank item will not be run in ImageMark Transaction Manager.
In SuperMICR, non-commingle item record IDs differ from commingle.
CPCS
See Check Processing Control System.
Cutslip
Used in CPCS processing. A control document that is fed automatically from the merge hopper after
a certain number of items have been processed. Sometimes referred to as a divider.
Cycle
The grouping that determines the posting date of the work. Each unit of work is associated with a
particular cycle. Could be used to track the work for one shift or for one day.
Cycle Posting Date
The date on which a cycle is posted to the consolidation server. Set by a supervisor. For unencoded
POD or pre-encoded POD work, the cycle posting date refers to the date when the customer will
get credit for their deposit. For inclearings work, the depositor is the bank or clearing house or federal
reserve branch that returned your on-us checks. The cycle posting date refers to the date when that
institution will get credit for their “deposit”.
D
DAP
See Data Application Processor.
Data Application Processor (DAP)
A server that monitors and manages work throughout the ImageMark Capture system. Each DAP
can support up to three DSs.
429
Glossary
Data Server (DS)
A server that contains the database of document images and codeline information. (In the case of
3890 captured work, the images are not stored in the database. They are stored on the VECTORsgi
ICC/ICS (Image Capture Controller / Image Capture Server)). Each DS can support up to two EPUs
and multiple IDTs.
Deposit Review Autorole (DRA)
A function of ImageMark Transaction Manager that automatically removes non-negotiable items
from the document stream. TM creates Advice Notices to notify customers whose accounts are
affected by these items.
Document Preparation (doc prep)
Getting items ready for processing on the Entry Processing Unit. Includes “grooming” (removing
paper clips, staples etc.), organizing into trays and capturing images of adding machine tapes.
Document Reference Number (DRN)
A sequential number assigned by the Image Capture application, and printed on each item
processed at the Capture transport. Uniquely identifies the item within the cycle. Parameters identify
the exact makeup of this flexible but unique item. In the case of 3890 captured entries, the DRN is
assigned from the ISN (item sequence number) that was assigned & endorsed on each item by the
CPCS MICR application.
DRA
See Deposit Review Autorole.
DRN
See Document Reference Number.
DS
See Data Server.
E
Effective Date
The SuperMICR term for the cycle posting date.
EIPS
See Enhanced Item Processing System.
430
Glossary
Encode
To print magnetic or optical characters in the codeline area of an item.
Encode and Sort Unit (ESU)
A machine that encodes the codeline information on the documents and then sorts the documents
into pockets.
Endpoint
Final destination of a processed item.
Endorse
To print non-magnetic information on an item (not in the codeline area).
Enhanced Item Processing System (EIPS)
NCR software used to control imaging systems.
Entry
A unit of work processed at Image Capture. Consists of multiple blocks and batches. Typically the
size is about 10,000 items but can be larger depending on your site’s processes. This is the largest
unit of work that can be balanced.
Entry Number
A four-digit number that ImageMark uses to identify a new Entry. In CPCS, the Tracer Group account
field includes the 4-digit entry number. In SuperMICR, the EPU assigns a unique entry number. The
Entry number is used at Capture Reconciliation to identify work in process.
Entry Processing Unit (EPU)
A machine that captures the images of checks, deposit slips, and other internal bank documents
and stores their images and codeline information. The EIPS EPU captures information into flat files,
and EPA loads this information into the database.
EPU
See Entry Processing Unit.
ESU
See Encode and Sort Unit.
431
Glossary
Exception Item
An item that requires the attention of the Capture Reconciliation operator, possibly because the ESU
could not match with an item in the database, or because it has been outsorted for further research.
I
I-String
Input string created by CPCS at prime pass capture on the 3890. Contains a list of records, one for
each item. Each record contains information about the item, such as field values, item type flags,
record ID, and pocket number.
ICC
See Image Capture Controller.
ICS
See Image Capture Server.
Image Capture Controller (ICC)
A VECTORsgi term. A server that supports one or more 3890 transports within a 3890 Capture
system.
Internet Information Services (IIS)
a set of Internet-based services for servers using Microsoft Windows. It is the world's second most
popular web server in terms of overall websites behind the Apache HTTP Server although the gap
is decreasing according to Netcraft. The servers currently include FTP, SMTP, NNTP, and
HTTP/HTTPS.
Image Capture Server (ICS)
See Image Capture Controller.
Image Capture
An NCR ImageMark Capture application that runs on the Entry Processing Unit (EPU) and controls
one or more of the following functions:
432
!
capturing electronic images of items
!
endorsing specified information on the item
!
capturing item images
!
sorting the items into specified pockets
Glossary
Inclearings
On-us work that was initially processed by another bank (bank of first deposit).
ISN
See Item Sequence Number.
Item Sequence Number
Sequential number printed on each item processed on a 3890 transport.
K
Kill Pocket/Tray
Contains items that do not require any further NCR ImageMark Capture processing, such as On-us
items and cash tickets. If a kill pocket contains transit items, then this pocket is ready for Kill Bundle
Listing and Cash Letter print. Then the tray of items is dispatched to its destination (Endpoint) via
courier.
Note: Each pocket has separate ImageMark vs. 3890 pocket types. A pocket may be considered
an ImageMark Kill, but 3890 Rehandle. In that case, the pocket must be rehandled on a 3890
for additional sorting.
M
Magnetic Ink Character Recognition (MICR)
A type of recognition that relies on detecting characters that have been machine printed in magnetic
ink to rigid specifications. The distinctive shape of each character and amount of magnetic ink in
each character are strictly defined by ANSI.
MICR
See Magnetic Ink Character Recognition.
NNetwork
A cluster object that carries internal communication between nodes and/or provides client access
to cluster resources.
Node
A server system that is an active or inactive member of a server cluster.
433
Glossary
O
OCR
See Optical Character Recognition.
OEP
See Over Encode Protect.
On-us Items
Items that are drawn on your bank. These may be either debits (checks & cash-out tickets) or credits
(deposit slips & cash-in tickets).
Optical Character Recognition (OCR)
A type of recognition that relies on detecting characters that have been machine printed to rigid
specifications that allow them to be read by an optical character reader (OCR reader). The distinctive
shape of each character is strictly defined by ANSI. OCRA and OCRB are two widely used OCR
fonts.
Over Encode Protect (OEP)
The system does not encode information on items marked as OEP. The codeline doesn't contain
enough space between existing fields to encode a missing field. The operator will either add a strip
to the bottom of the item and encode the strip, or put the item into a carrier envelope, then encode
the carrier envelope.
P
Parameter Set
A collection of many parameter files, specifying how to process a type of work (not an individual
item). When an entry is captured, the parameter set must be selected before you begin, and this
parameter set controls how the work is processed throughout the workflow. For example, the
parameter set might specify that debits are processed before credits. There may be different
parameter sets to process different types of documents.
PCS
See Proof Correction System.
434
Glossary
Piggyback
An item that moves down the track behind another item and is therefore hidden from the system. If
front and rear imaging is turned on, the system captures the front image of the front item and the
rear image of the hidden item, but thinks it is one item.
Posting Date
The date on which a cycle is processed. Set by a supervisor. This is often referred to as the effective
date or cycle date.
Primary Job
Term used by SuperMICR for a prime-pass capture. The information sent to the host by the system
is called a primary job. Equivalent to a CPCS balanced I-string. If the reader/sorter performs a prime
capture the data captured on the host is called the primary job.
Prime I-String
An unbalanced I-string generated by running pre-balanced OTC (over-the-counter) work previously
encoded and balanced (at single-pocket proof stations) first pass on a 3890.
Proof Correction System
A Fiserv product used to generate adjustments and print/fax advice notices, similar to ImageMark
Transaction Manager’s Balancing and Advice Notice Printing roles.
R
R Pocket
On the 3890, this is the pocket where all rejects (items that failed Recognition) are sent during
capture. On the EPU, only control documents, such as tracers, block and batch headers, go to the
R pocket.
Rehandle Tray
A tray of items that require further processing at the ESU or 3890.
Rehandle Pocket
A pocket of items that require further processing at the ESU or 3890.
Reject Item
An item that is rejected at the EPU or reader/sorter because the codeline could not be recognized.
The physical item is placed in the reject pocket; the image is sent to Codeline Completion.
435
Glossary
Reject Pocket
The bin used to store rejected documents.
Resource
A physical or logical entity that is capable of being owned by a node, brought online and taken offline,
moved between nodes, and managed as a cluster object. A resource can be owned by only a single
node at any point in time. A resource is an instance of a resource type.
Routing Transit Number
This is another name for the Bank number.
S
Secondary Job
Term used by SuperMICR for a second pass of a rehandle pocket off a prime capture run. If a
reader/sorter performs a second pass the data captured on the host is called the Secondary Job.
Showout
An adjustment to a transaction that is out-of-balance by less than a specified amount. This will be
“written off” and not charged back to the customer or teller. (This can also be called “over and short”
or various other names by different banks.)
Sorter
Transport for sorting items. Typically this is an IBM 3890 reader/sorter. Not an EPU or ESU.
SuperMICR
Software used by banks for account posting, float, bundle lists and cash letters. SuperMICR resides
and runs on IBM mainframes, and normally uses IBM 3890 transports for capturing and sorting items.
Suspense Pool
An electronic holding area for item images/information for items that were captured within the wrong
transaction.
Software Optical Character Recognition (SWOCR)
An ActiveX Control OCX that enables the recognition of standard codeline encode formats from an
image.
436
Glossary
T
Tracer Group Documents
Used in CPCS processing. Control documents placed at the beginning of an Entry and used to
provide information for further processing by a reader/sorter. The Tracer Group account field
includes the 4-digit entry number and a 3-digit incrementing slip number. The Routing Transit field
identifies the item as a tracer group. Typically a bank runs a pack of approximately 50 tracers at the
beginning of each entry, and a certain programmable # of these are placed into the “R” pocket, and
each rehandle pocket.
Transit Items
Items that will be forwarded to the issuing bank.
Transaction
A complete deposit, consisting of at least one credit (usually a deposit slip) and one or more debits
(usually checks).
Transport
A generic name for the hardware that processes large volumes of items. The Entry Processing Unit
and the Encode and Sort Unit are both transports.
Tray
A container used for organizing and transferring items from one stage of the process to the next.
Tray Headers
An ImageMark control document used to identify physical trays of items in a CPCS environment.
They are used to identify the tray when selecting work at the ESU. The ESU can feed Tray Headers
to the front of each output tray if required.
Note: When the ESU processes the 3890 R pocket, there is no tray header to identify the work.
Instead, the first tracer is used to identify the tray.
Tray Set
A unit of work processed at the ESU. Consists of one or more physical trays of items that were
sorted into the same pocket at the EPU.
437
Glossary
U
Universal Batch Header
An item with a codeline that can be treated as either a batch header or a cutslip, depending on
whether it is inbound or outbound work.
438
Index
Symbols
348
A
access security
accounts
types 262
domains
about supporting 270
BAPs in same domain 269
databases in different domains 269
databases in same domain 269
remote IDT workstations 270
server 262
system 262, 268
domain security 269
supporting organizational units 269
Access Security Manager
assigning permissions
by activity 154
by user 152
creating
new workgroups 146
user accounts 148
deleting
user accounts 151
workgroups 147
modifying
user accounts 150
workgroups 146
removing user permissions 156–157
starting 144
accounts
access security types 262
system access security 262
active directory
about 260
activities
loading 72, 77
managing 71
remote 30, 35
shutting down 72, 313
station control 71
stopping an auto-activity 77
unloading 73
viewing 71
viewing activities for a workflow interaction 44
viewing workflow interactions by activity 43
Activities dialog 82, 313
adding
cycles 45
parameter sets
about 133
by package 134
by station 138
printers 284
software
by package 128
by station 131
station 112
station groups 108
stations 111
workstations 103
description 183
sample 344
description 244
Adjustments/Corrections report
sample 411
administration tasks for a server cluster 292
diagnostic alerts, setting up 293
ImageMark package version monitoring 292
ImageMark services, starting and stopping 295
scheduled tasks, managing 296
Advice Notice Export utility
about 280
configuring your system 280
running 280
439
Index
saving flat files 282
saving TIFF files 280
Advice Notice Utility
configuration file format 280
Advice Notices
saving as TIFF files 280
aging out second source records 56
AK (See Amount Keying)
All Items report
description 242
sample 409
Amount Keying
Grand Total Performance report 234
Operator Performance Detail Report 230
Operator Performance Summary report 227
sample 399
Amount Suspect Summary report 183
description 183
sample 345
application
loading instance 81
managing instances 81
unloading instance 84
Application Display window 27
Application Manager
exporting a normal entry unit of work 60
Image Quality Status, viewing 62
overview 25
starting 26
Archive Status
dialog 91
information
archived 91
generated 91
viewing 87
assigning permissions 152, 154
At end 36
ATM Adjustments File report 185
ATM reports
description 184, 253
list of 253
printing 180
Audit Exceptions report 189
description 189
sample 348
Audit reports
description 185
list of 185
audit reports 185
Full Audit report 186
ImageMark Audit report 186
auto-activities
loading for report redirection 66
stopping and restarting 77
unloading for report redirection 65
Auto-Activity reports
description 241
440
list of 407
auto-assign activity 29
sample 351
automatic file cleanup 291
automatic reports
Entry Item reports 241
automatically print or save End-of-Cycle reports
165
B
back-up
Base AP system 298
non-Base AP system 299
Windows file systems 299
creating 299
requirements 299
Windows-based subsystems to tape 298–299
BAL (See Balancing)
Balanced Item Export
recovering from duplicate entry numbers 311
resending work 300
viewing work status 85
Balancing
Operator Grand Total Performance report
sample 404
Operator Performance Detail report 231
sample 400
Balancing Operator Enhanced Performance Detail
report
description 238
BAP
restoring 315
Base Application Processor (BAP) 104, 327
description 243
sample 410
BIE
See also Balanced Item Export
BIE Deadline report
description 194
sample 353–356
description 194
Block Balancing
sample 401
sample 396
bottlenecks, identifying 31
Index
branch capture integration 93
identifying problems with 335
problems
bank diverts work to another site 336
files not imported 335
no teller files from branch 336
no teller files to import 335
SMM imports duplicate file 336
SMM not matching UoW 335
SMM not picking up UoW 335
SMM running slowly 336
UoW held at SMM 335
resubmitting work 95
viewing second source images 96
Branch Rankings report
sample 364–365
description 197
sample 364
description 196
sample 360
description 198
BTM reports
description 196
list of 196
Bundle List report
description 200
sample 369
C
capacity settings 273
capture files (for Distributed Capture), cleaning up 290
description 251
sample 420
description 249
sample 419
CAR auto-activity
starting normal mode 334
starting shuffle mode 332
CAR Performance Summary report 343
description 216
sample 384
CAV Performance Summary report 343
description 216
sample 385
changing
CPCS entry number for cycle 57
host entry number for a duplicate host entry (for
Distributed Capture) 288
server status 78
station attributes 114
station identification 114
station types 116
workstations 103
changing reporting periods 160
CLC (See Codeline Completion)
cleaning up capture files (for Distributed Capture) 290
cleaning up files on the transports 291
cleanxprt.pl 291
cluster configuration
administration tasks 292
Codeline Completion
sample 398
Configuration Manager tasks
adding
parameter sets 133
parameter sets by station 138
software by package 128
software by station 131
station groups 108
workstations 103, 111
changing
station attributes 114
station identification 114
station types 116
workstations 103
configuring
software by station 131
stations 105
deleting workstations 103
identifying stations 112
modifying
services 141
station groups 109
removing
parameter sets 137
station groups 110
station software 132
stations 119
starting 104
switching EPUs or ESUs 117
configuring
notification 325
software
by package 128
by station 131
corrupt EIPS files on Data Server, replacing 287
CPCS entry number, changing 57
creating
cycles 45
user accounts 148
441
Index
cron jobs
set stale date script 277
current error log filename 327
Cycle Manager 45
cycles
about 45
adding a new cycle 45
changing CPCS entry number 57
closing 49
deadlines, managing 52
ending 50
managing 45
modifying 48
number field 83
opening 49
opening a new cycle 46
opening existing 47
posting date 24, 46–47, 49, 51
reasons for modifying 48
removing 47
reopening 50
state
close 83
empty 83
open 83
validating (for Distributed Capture) 286
viewing SuperMICR job number information
D
Daily Corrections Export Reports
list of 201
Daily Corrections Export reports
description 201
Data Server (DS)
configured with RSS 332
date/time setting 285
Delete Cycle
marking operator performance data for
deletion 170
deleting
reports from spooler 68
user accounts 151
workgroups 147
workstations 103
Deposit Review
sample 405
sample 402
sample 397
442
58
description 192
sample 350
Deposit Review Non-Negotiable Items report
sample 381
diagnostic alerts
setting up for a server cluster 293
diagnostic alerts, setting up for a server cluster 293
Diagnostics
acknowledging messages 323
configuring notification 325
printing alert messages 324
starting 318
viewing message details 321
displaying
detailed operator information 32
invalid posting dates (for Distributed Capture) 287
Distributed Capture
changing host entry number for a duplicate host
entry 288
cleaning up capture files 290
integrating consolidation server 270
replacing corrupt EIPS files on Data Server 287
validating cycles 286
imdeletedates 286
imdisplaydates 287
imloaddates 286
domains
security requirements 269
supporting 270
DRA 36
duplicate entry numbers, recovering from 311
E
EBAL (See Expert Balancing)
description 221
sample 392
EIE
auto-activity, recovering lost entry 305
See also Encoded Item Export
EIE Deadline report
description 195
sample 357
EIE, BIE, and SIE Deadline reports
description 194
eips_cleanup.pl 291
EIR
See Entry Item reports
See also reports, auto-activity reports
EIR Deposit Corrections report
description 246
EIR Deposit Review Host Results report
Index
description 246
eirPrint 178
emergency recovery procedures 338
emergency logical log backup 338
recovering from system failure 339
End of Day Daily Corrections Export report 201
audit reports 185
descriptions 182
list of 182, 342
printing manually 166
end-of-cycle reports
audit reports
entries, exporting 60
Entry Item reports
about 241
description 241
list of 241
Entry Level Daily Corrections Export report 202
entry numbers, recovering from duplicates 311
description 242
sample 408
environment variable changes
implementing 77
EPU
cleaning up files 291
switching stations 117
taking out of service 117
EPU Exception Item Reports
list of 206
description 206
EPU Transport Performance Summary report
description 222
description 222
sample 393
error log files 327
locating 327
sample messages from log file 328
viewing current day’s file 327
viewing log history files 327
error messages
description of components 328
filtering 319
finding version numbers 331
help information 322
locating error message groupings 331
phoning for second-level support 331
reading error log file 330
reading message text 331
referencing other publications for additional
help 331
severity codes 330
viewing details 321
viewing history log files 330
ESU
cleaning up files 291
switching stations 117
taking out of service 117
ESU Operator Matched Item Audit report
description 252
description 251
sample 422
ESU Transport Performance Summary report
description 223
description 223
sample 394
Exception Items in Kill Pocket report
description 207
excluded servers 123
excluding a storage space 126
Expert Balancing
Expert Block Balancing
sample 403
Expert Link
about 313
restarting 314
stopping 314
Export Log
details 86
viewing 85–86
F
failure of RSS 332
file
printing to 68
recovery for IDT and TSS workstations
files, cleaning up 291
filtering
reports displayed in Print Spooler 66
workload displayed in
Load dialog (Volume tab) 33
Work In Progress dialog 35–36
description 208
sample 374
Free dialog 125
315
443
Index
Free Storage Space dialog 124
freeing
databases
troubleshooting 326
storage space 124
error messages 326
when to 20
G
gen_prod.sql 274
description 233
for Deposit Review 236
group
reassigning a station for 74
restoring a station to 76
H
handling error messages
consulting second-level support 331
referencing other publications 331
hardware
order of powering down 258
order of powering on
powering down 258
powering on 259
powering up 259
history error log filename 327
holding back work 39
host cycle number 300
field 51, 83
host entry number (CPCS), changing 57
host link
restarting 313
See also Expert Link
I
identifying
bottlenecks
444
31
stations 112
IDT
backing up 312
restoring 312
IDT workstation file recovery 315
Image Quality Failure Detail report 209
sample 375
Image Quality Rejects, exporting 55
Image Quality Review Performance Summary
report 224
sample 395
Image Quality Status, viewing 62
sample 376
Image Quality Transport Performance Summary
report 210
sample 377
ImageMark
package version monitoring 292
services, starting and stopping 295
description 186
sample 347
imdeletedates 286
imdisplaydates 287
imloaddates 286
importing Base AP databases 315
In Progress 36
IN/OUT workflow activity information 43
description 199
sample 367
Initialize dialog 123
Initialize Storage Space dialog 122
initializing
databases
troubleshooting 326
storage space 122
error messages 326
instance
loading 81
managing 81
unloading 84
interactions
components 43
viewing activities for 44
viewing by activities 43
workflow activity information 43
interpreting reports 159
intializing
storage space
conditions 20, 22
when to 22
why to 22
I-string
resending using a different host cycle number
description 211
210
300
Index
sample 378
description 197
sample 362
description 211
sample 379
Items Pull report
description 212
sample 415
Items Pull report - High Dollar
sample 380
Items Pull reports
description 212
Items Reassigned from EPU Kill Pockets report
description 245
sample 414
description 197
sample 363
J
job number, viewing SuperMICR information
58
L
Line printer 68
Load dialog
Completion tab information
Estimated completion time field 34
percent field 34
Total and Printed fields 34
Volume, UoW, and Time fields 34
identifying bottlenecks 31
Operators tab information
Operator column 32
Rate column 32
Total field 32
queue color 31
Summary tab information
Operators column 30
Optimal column 30
Printed column 30
Throughput column 30
Total column 30
Volume column 30
viewing 28
Volume tab filters
entry number 33
parameters 33
servers 33
Volume tab information
Count row 33
Value row 33
loading
activities 72, 77
application 82
application instance 81
auto-activities for report redirection 66
invalid dates (for Distributed Capture) 286
description 248
sample 418
M
managing
access security 262
activities 71
application instances 81
cycles 45
print spooler 64
recognition 271
system access security accounts 262
system environment 260
user accounts 148
user workgroups 145
workload 28
workload by operator activity 28
workload by unit-of-work type 35
manual file cleanup 291
matched records, printing 181
description 207
messages
acknowledging 323
filtering by
date 319
station 319
time 320
type 319
viewing details 321
MIE
MIE Exception report
description 254
printing 254
sample 425
description 247
sample 416
sample 349
Modified Entry report (CPCS)
445
Index
description 191
Modified Entry Report (SuperMICR)
description 191
modifying
cycle attributes 51
cycle host entry number 51
cycle state 48
cycles, reasons for 48
entries 57
posting deadline 52
station groups 109
station services 141
system capacity settings 273
considerations for changing system
capacity 273
user accounts 150
workgroups 146
monitoring SMM processing 93
Operator Performance reports
description 221
list of 221, 391
printing manually 168
description 226
description 225
operator statistics
deleting 170
description 225
Optional Field Completion
Operator Performance Summary report 226, 229
order for configuring components 105
organizational units
about 261
output
to printer list box 65
to spooler list box 65, 69
N
description 196
sample 361
description 213
sample 381
normal entry unit of work
exporting 60
P
O
Open Cycle Dialog 46
opening
cycles 46
existing cycles 47
operator
accounts
changing 150
creating 148
deleting 151
managing 148
user ID 149
displaying detailed information about
permissions
assigning by activity 154
assigning by user 152
removing 156–157
description 230
446
32
parameter changes
implementing 77
parameter sets
adding 133
adding by station 138
notes on adding parameter sets 133
removing 137
removing by station 142
password settings 268
passwords 151
performing a restore of stations 315
perl script interpreter 260
permissions
removing 156–157
PIE
description 213
sample 382
posting deadline 52
modifying 52
powering down system hardware 258
powering on system hardware 259
print spooler
dialog 64
managing 64
redirecting reports
Index
to printer 69
to spooler 64
printers
adding 284
FILE 68
line 68
lpsiips 68
printing
automatically 165
Entry Item reports, eirPrint 178
reports after end of cycle 174
reports before end of cycle 174
reports, about 159
Tray Set reports, tsrPrint 180
printing reports 68
priority
changing for work 38
viewing 37–38
Processed Envelopes by Transaction Number
Sequence report 185
Processed Envelopes in Posting Sequence report
description 253
sample 423
185
R
Reassigned Pocket - ESU Operator Matched Item Audit
report
sample 421
reassigning a station for another group 74
recognition
managing 271
restarting 271
unit self test utility 272
Recognition Performance Statistics
CAR Performance Summary report 343
CAV Performance Summary report 343
RSS Performance Summary report 343
RSS Reclassification report 343
description 215
list of 215
Recognition Sub-System
See also RSS
Reconciliation Operator reports
description 237
recovering from system failure 339
redirecting reports
to printer 69
to spooler 64
releasing held work 40
remote activity types 30, 35
removing
cycles 47
dates from invalid posting date listings (for Distributed
Capture) 286
parameter sets 137
station groups 110
station software 132
stations 119
unused ImageMark-generated Windows
accounts 262
user permissions 156–157
replacing corrupt EIPS files on Data Server (for
Distributed Capture) 287
Report utility
cancelling print jobs 173
saving reports 166, 168, 254
viewing print jobs 171
reporting periods
changing 160
deleting statistics 170
reports
about reporting periods 169
Adjustment Summary report 183, 344
Adjustment/Corrections report 244
Adjustments/Corrections report 411
All Items report 242, 409
Amount Keying Operator Performance Summary
report 399
Amount Suspect Summary report 183, 345
ATM Adjustments File report 185
ATM reports 184
Auto-Activity reports 241, 407
Automatic Codeline Completion Statistics
report 351
Balancing Operator Enhanced Performance Detail
report 238
Balancing Operator Grand Total Performance
report 404
Balancing Operator Performance Summary
report 400
Batch Proof List report 243, 410
BIE Deadline Report 354
BIE Deadline report 194, 353
Block Balancing
Block Balancing Operator Sessions Activity
report 396
Branch Rankings report 364–365
BTM Batches Aged Out report 197, 364
BTM Batches Not Received report 196, 360
BTM Branch Rankings report 198
Bundle List report 200, 369
Capture Reconciliation Audit Pocket Summary
report 251, 420
Capture Reconciliation Audit report 249, 419
447
Index
CAR Performance Summary report 216, 384
CAV Performance Summary report 216, 385
Codeline Completion Operator Performance
Summary report 398
deleting from spooler 68
Deposit Review
Deposit Review Audit report 192, 350
Deposit Review Non-Negotiable Items report 381
Deposit Review Operator Grand Total Performance
report 405
Deposit Review Operator Sessions Activity
report 397
ECU Transport Performance report 221, 392
EIE Deadline report 195, 357
EIR Deposit Corrections report 246
EIR Deposit Review Host report 246
End of Day Daily Corrections Export report 201
End-of-Cycle reports 182, 342
Entry Level Daily Corrections Export report 202
Entry Summary report 242, 408
EPU Transport Performance Summary report 222
EPU Transport Sessions Performance report 222,
393
ESU Operator Matched Item Audit report 252
ESU Pocket Total report 251, 422
ESU Transport Performance Summary report 223
ESU Transport Sessions Performance report 223,
394
Expert Block Balancing Operator Grand Total
Performance report 403
Forced Adjustment report 208, 374
Image Quality Failure Detail report 209, 375
Image Quality Review Performance Summary
report 224, 395
Image Quality Test Performance Summary
report 210, 376
Image Quality Transport Performance Summary
report 210, 377
ImageMark Audit report 186, 347
Incorrectly Matched Items report 199, 367
Items Aged Out report 211, 378
Items Missing from BTM Batches Received Today
report 197, 362
Items Not Received report 211, 379
Items Pull report 212, 415
Items Pull report - High Dollar 380
Items Pull reports 246
description 246
Items Reassigned from EPU Kill Pockets
report 245, 414
Items Received without BTM Batches Today
report 197, 363
Low-Speed Items in High-Speed Pockets
report 248, 418
Merchant Summary report 207
448
MIE Exception report 254, 425
printing 254
Misencode Detail report 247, 416
Modified Entry report 349
Modified Entry report (CPCS) 191
Modified Entry Report (SuperMICR) 191
Next Day BTM Batches Received report 196, 361
Non-Negotiable Items report 213, 381
Operator Performance reports 221, 391
operator performance reports
for Optional Field Completion 232
for Optional Field Completion 229
Operator Sessions Activity report 225
Pocket Listing report 213, 382
printing 68, 180
printing after end of cycle 174
printing automatically 165
printing before end of cycle 174
printing End-of-Cycle reports 166
printing Operator Performance reports 168
Processed Envelopes by Transaction Number
Sequence report 185
Processed Envelopes in Posting Sequence
report 185
Putaway Transaction report 253, 423
Reassigned Pocket - ESU Operator Matched Item
Audit report 421
description 215
redirecting
to printer 69
to spool 64
regenerating 172
reporting periods, changing 160
Research Items - Exception Items in Kill Pocket
report 207
Research Items - Exception items in Kill Pocket
report 373
Resource Allocation report 240, 406
RIR Document Distribution report 218, 387
RSS Performance Summary report 215, 383
RSS Reclassification report 217, 386
saving automatically 165
Second Source Match and Merge Performance
Summary report 219, 388
SIE Deadline report 195, 359
SMM Results report 246
Suspense Items in EPU Kill Pockets report 244,
412
Index
413
245,
Teller Keying Errors Detail report 199, 368
Teller Ranking report 198, 366
Truly Missing and Free report 219, 389
types of 159
Unmatched ATM Envelope report 184, 346
Unresolved Suspense Items report 206, 371–372
User Permission and Login Information report 220,
390
viewing 66
Reports utility
starting 164
Research Items - Exception Items in Kill Pocket report
description 207
sample 373
Resending a string using a different host cycle
number 300
resending work
to BIE 300
to SIE 300
resenditemexport utility 300
description 240
sample 406
restarting
host link 313
RSS auto-activity 271
restoring
station to original group 76
stations 315
RIR Document Distribution report 218
sample 387
RPT_FIELD_DEFNS
related report 212
rptperiod.cfg file 163
rptperiod.cfg_sample file 160
RSS
auto-activity
managing 271
restarting 271
testing 272
responding to failure 332
See also Recognition Sub-System
RSS Performance Summary report 343
description 215
sample 383
RSS Reclassification report 343
description 217
sample 386
S
sample error log file messages
328
saving reports
to FILE 68
scheduled tasks
capture file cleanup 290
sample 277
set stale date script 275, 278
setting up for
regular environment 276
time-of-day environment 278
scheduled tasks, managing for a server cluster 296
Second Source
browser software, configuring IDT 103
records, deleting old ones 56
viewing item images 96
Second Source Adjustment file 185
Second Source Match and Merge Performance
Summary report
description 219
sample 388
Second Source View dialog 93
customizing 95
security enhancements 121
security procedures 151
server cluster
administration tasks 292
ImageMark package version monitoring 292
ImageMark services, starting and stopping 295
scheduled tasks, managing 296
setting up diagnostic alerts 293
Services dialog 75
Set Priority dialog 37–38, 40, 60, 63, 178, 301,
303, 305, 307, 309
set stale date script
sample cron job 277
setting up a cron job 277
setting up a scheduled task 275
setting up a scheduled task for a time-of-day sort
environment 278
setting priority type
high 38
low 38
normal 38
severity codes of error messages 330
shuffle mode 332
shutting down
activities 72, 77
Capture hardware 258
SIE
See also Sub-pass Item Export
SIE Deadline report
description 195
sample 359
SIE, BIE, and EIE Deadline reports
description 194
SMM
auto-activity
identifying problems with 335
449
Index
disabling shuffle mode 96
enabling shuffle mode 95
monitoring processing 93
pushing work past 95
resubmitting work 95
viewing item images 96
SMM Results report
description 246
ssreport.pl 180
starting
Access Security Manager 144
Application Manager 26
Capture hardware (See powering on system
hardware)
Configuration Manager 104
Diagnostics 318
Reports utility 164
start-of-cycle
archiving report files 18
checking system messages 19
cycles
about associating 23
opening 23
ending cycles 21
exporting suspense items 16
freeing a storage space 21
initializing a storage space 22
printing reports 17
procedures 15
station groups 106
creating and modifying 103
modifying 109
removing 110
stations
adding 111
adding parameter sets 138
changing attributes 114
changing identification 114
changing type 116
identifying 112
modifying services by 141
reassigning 74
reassigning for another group 74
removing 119
removing parameter sets 142
restoring 315
restoring to original group 76
software
adding 131
adding by package 128
configuring by package 128
removing 132
removing by package 130
Stations dialog 74
statistics
deleting 170
status, maintain activity information 65
storage space
450
about 20
conditions for freeing 124
freeing status 125
initialization status 123
making space on the system 20
options for utilizing 20
Storage Space Manager
adding a user 121
storage space manager
about 120
storage spaces
excluding 126
freeing 21, 124
initializing 122
managing 120
monitoring state 127
Sub-Pass Item Export
resending work 300
viewing work status 85
sub-type column 36
SuperMICR, viewing job number information 58
Suspense Items in EPU Kill Pockets report
description 244
sample 412
description 245
sample 413
suspense items, exporting 55
switching EPUs or ESUs 117
system
capacity settings
modifying 273
viewing 273
environment, perl script interpreter 260
powering down 258
powering on 259
resetting date and time 285
shutting down 258
starting up 259
system changes
making them take effect 77
system maintenance 257
access security 262
domain security requirements 269
password settings 268
supporting organizational units 269
T
taking EPU out of service 117
taking ESU out of service 117
teller file
about 93
Index
description 199
sample 368
Teller Ranking report
description 198
sample 366
testing RSS auto-activity 272
testru utility 272
TIFF files
saving Advice Notices as 280
time-of-day sort
posting deadline 52
setting up a set stale date scheduled task 278
Transport Performance Statistics reports
description 222
Tray Set reports
description 249
list of 249
troubleshooting
activity fails spontaneously 337
emergency recovery 338
freeing storage spaces 326
handling error messages
phoning for second-level support 331
reading error log file 330
referencing other publications for additional
help 331
initializing storage spaces 326
reports did not generate 172
RSS failure 332
description 219
sample 389
TSR
See Tray Set reports
See also reports, auto-activity reports
tsrPrint 180
TSS
backing up 312
restoring 312
TSS workstation file recovery 315
U
unit-of-work
interaction 36
sub-types
all 36
batch 36
input processed 36
input ready 36
output 36
transaction 36
types
advice notice 36
DDR 36
DDR with Images 36
entry 35
tray 35
tray set 35
viewing Work In Progress 35
See also Work In Progress
unit-of-work sub-types 36
unloading
activities 73
application instance 84
auto-activities for report redirection 65
Unmatched ATM Envelope report 184
sample 346
description 206
sample 371–372
UoW
See unit-of-work
See also Work In Progress, unit-of-work types
user
accounts
creating 148
deleting 151
managing 148
modifying 150
passwords 151
permissions 152
removing 156–157
User Permission and Login Information report 220
sample 390
using Report utility
cancelling print jobs 173
saving reports 166, 168, 254
viewing print jobs 171
using Reports utility
starting utility 164
V
validating cycles (for Distributed Capture)
imdeletedates 286
imdisplaydates 287
imloaddates 286
version monitoring 292
viewing
activities 71
activities for an interaction 44
286
451
Index
archive status 91
export log details 86
external capture station status 79
load queues 31
message details 321
remote activities 30, 35
reports 66
server status 78
system capacity settings 273
workflow interactions 43
workload
by operator activity 28
by unit-of-work type 35
W
work
holding back 39
releasing 40
Work In Progress
dialog 35
changing work priority 38
displaying 35, 37–40, 93
holding back work 39
releasing held work 40
viewing
specific type of work 35
unit-of-work sub-types 36
unit-of-work types 35
viewing 35, 39–40, 93
workflow
diagrams 98
viewing
activities for an interaction 44
interactions by activity 43
workgroups
creating new groups 146
deleting 147
managing users in 145
modifying 146
workload
managing by operator activity 28
managing by unit-of-work type 35
452
B004-0000-0609
December 1, 2006

ImageMark Transaction Manager 4.2 - Susan E. Smith

Transcription

Similar documents

RE/MAX vs. THE INDUSTRY

XR650 Brochure

Morgan Stanley Smith Barney Benefit Access Quick

M-Line 4500

Harborstone Credit Union

instructions for housing deposit ($250.00 usd)

Helsinki | 12 November, 2015

Vendmaster Brochure

States, Robert J.

BattleNet 360 - Delex Systems, Inc