HP3000-L Archives

May 2000, 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:
"Leonard S. Berkowitz" <[log in to unmask]>
Reply To:
Date:
Wed, 10 May 2000 15:30:30 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (62 lines)
I can imagine a little system with a TurboImage data base in which you maintain
entries that cross-reference the HPJOBNAME to a particular printer. The logon
UDC could do a lookup. You probably would not have to write a program -- if you
have MPEX -- but just use their data base functions. If you do not have MPEX,
you would have to do some programming.  Yes it would be a paid to enter Bob
Graham's jillion remote users, but it will have to be done somewhere.

I can also imagine storing this in a KSAM file and performing a
FCOPY.....;SUBSET="!HPJOBNAME" to a disk file and setting a variable to the part
of the record that identifies the printer. Same issue with the jillion remote
users.

Both of these suggestions will add some overhead to the logon process, and HELLO
is probably the most expensive command  there is.
===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax:   617-509-3737







Pedro Gonzalez <[log in to unmask]> on 05/10/2000 02:19:35 PM

Please respond to [log in to unmask]








 To:      [log in to unmask]

 cc:      (bcc: Leonard Berkowitz/CORP/HPHC)



 Subject: [HP3000-L] Secret Identity








Our company is expanding to have remote sites and VT users from these
sites.  I would like to know who these users are when they sign on so I
can redirect their reports to their local printers.  I'd like to hear how
some of you do this?  Not all the jobs in our system ask the user where
the report will be printed.

**********
Posted from www.3kworld.com

ATOM RSS1 RSS2