MICR Printing

To Doug Barnes and the midrange list,

        We are currently using IBM's 4028's modified by Troy to produce MICR
checks. However, this is a dead end because IBM went to Troy and said,
"Thou shalt only modify printers for us." and Troy said, "But the herd is
buying HPs. Good-bye." And thus the business partnership got a divorce.

        Now, IBM is in bed with Rosetta Technologies who modifies IBM's
network printers. While these printers do look attractive, I can't help but
wonder when the divorce will occur.

        Is there an alternative? Yes. Troy is now modifying HP printers.
These printers also look attractive to us. There is a place called GANSON
ENGINEERING (I think) that has a MICR solution but the product and vendor
do not look attractive to me.

        For us (Clackamas E.S.D.), I store all of the elements that make a
check unique for a client and bank account (we have many) in a definition
record and then use the record to lay down the different elements of the
check. The compiled printer file is an AFP DDS PRTF. This means the
printer must be an IPDS printer. Signatures are stored as fonts on 4028
font cards. Logos also.

        The HP solution means to us: No changes to software and a IPDS
card is required for the printer (PRAM makes some). Signatures would be
burned into a SIMM and plugged into the printer. The printer is then secured
with password on the printer. No cards to lose or lock up. No password,
no checks. With the sig cards, no card, spoiled checks as a font
substitution was performed and the "call characters" for the signature
were printed instead, usually "ABC".

        The Rosetta solution means: Scrap most of my DDS coding because
to use the printer, you must use their CheckServer/400 software which
takes a "raw data" spool file and uses that to lay down the elements of
the check. Signatures are now on the AS/400 as a resource and that resource
is secured by the CheckServer/400 software with a password.

I am told that resources are locked up above and beyond normal AS/400
security but I don't believe it, at least not yet. I believe it is
possible to ignore CheckServer/400 and use a resource in a AFP DDS PRTF
like I currently am.

        The Rosetta solution also can print a "check copy" at the same time
as the check, which would be nice.

        I haven't made a decision yet. First I want to see the Rosetta
solution working someplace. My director is going to want to know if a
resource (signature) is really protected even from guys like me. But I
can't help but wonder how long the honeymoon will last.

        If pressed today for a decision, I would have to go with the
HP/TROY solution: with no changes to software, the solution is all
hardware based and I don't have to buy CheckServer/400 at some
tiered price. The 4028s and HPs do continue to require a 5494 at each
site. Rosetta does not, but we are unsure of how our disaster recovery
plan would change with Rosettas.

        I hope this helps.

Thain M. Howard, Finance & Payroll Project Leader
Clackamas ESD, P.O. Box 216, Marylhurst, OR 97036
(503) 635-0502
thoward@clackesd.k12.or.us

=====================================================
= Thain M. Howard, Project Leader, Clackamas E.S.D.
= Work: thoward@clackesd.k12.or.us
= Home: ThainHoward@CompuServe.com
=====================================================
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *