HP3000-L Archives

June 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Neil Harvey <[log in to unmask]>
Reply To:
Neil Harvey <[log in to unmask]>
Date:
Tue, 8 Jun 1999 07:55:23 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (69 lines)
Fernando

First Prize.
If the printers are on your network with Jet Direct cards, you could
configure them as normal spooled printers directly on your HP3000.

You could put the ldev number of the printer nearest the user onto the user
record or logon script (say), and issue a file equation directing the output
to the relevant printer during logon, or as part of the process they use to
request a print.

Second Prize.
If the printers are attached to the PC's via parallel/serial cables, a
cunning combination of Samba/iX client and Windows Printer Sharing could
probably be used to move spool files from the HP3000 to the PC printer. More
on this from the experts - Lars, Jens.

But it would be better to put Jet Direct cards into the printers and share
them.

Do away with Forms.
Since they are laser jets, you could use software like Formation or the
others to design forms and then deploy them during the print process, thus
doing away with the tyranny and inconvenience of pre-printed forms (some
would argue that you would be swapping tyrannies and inconvenience, but
that's another subject....).

Do away with Paper reports altogether.
Put Apache/iX onto your HP3000, and don't print forms, publish them.
We have achieved this successfully using simple <pre> </pre> tags to retain
the structure of reports.
We used to have a whole department prints, sorting and distributing reports
to users.
Now we have two command files and a Cobol program that :publish reports into
a specified area (Daily, Weekly, Management, Beanie) and :publink these to
users (the publish command actually puts the file into the web directory,
the publink command puts a link to it into the user directory).

The Cobol program rebuilds an index after every publish/publink command, and
the reports are grouped by Type and Date. (No doubt it could be written as a
command script, or in Perl - but hey, I know Cobol!)

Users know that their overnight/on request reports are available going back
many days.

Also the reports published this way are searchable within the web browser,
so the Beanies can look for that elusive $2.83 that makes April '99 debtors
not balance.....

What we found, of course, is that for a few weeks the diehard paper people
insisted on retrieving their reports and actually printing them, but this
burning desire to reduce our planet to a charred crust soon diminishes.

BIG savings can be achieved this way - paper costs money, toner/ink
cartridges cost money, printers (still) cost money, but Apache/iX and the
Browser are Free!

In our environments (health care) we have many laser printers shared
successfully between Vanilla Windows users, NT servers, HP3000's, UNIX etc.
using Jet Direct cards (internal or external), and it works well.

I hope these ramblings give you some pointers.

Good luck

Regards

Neil

ATOM RSS1 RSS2