[2065] in Enterprise Print Delivery Team
Re: 300 DPI v. 600 DPI and test printouts
daemon@ATHENA.MIT.EDU (David F Lambert)
Mon Dec 17 08:32:06 2001
Message-Id: <200112171332.IAA17117@pacific-carrier-annex.mit.edu>
Date: Mon, 17 Dec 01 08:16:46 EST
From: David F Lambert <LAMBERT@MITVMA.MIT.EDU>
To: Theresa M Regan <tregan@MIT.EDU>, "Rocklyn E. Clarke" <rclarke@MIT.EDU>
cc: Enterprise Printing Delivery Project Team <printdel@MIT.EDU>,
r3-print@MIT.EDU
In-Reply-To: Message of Mon, 17 Dec 2001 06:10:04 -0500 from <tregan@MIT.EDU>
Hi Theresa,
Yes, the delivery info & cost object will be a general requirement (sorry
the code was turned on prematurely). It will be required for all print
submits including SAP.
Our initial goal was to verify a person's authorization to charge to a
specified cost object. We had planned to eventually verify authorizations
via the Roles DB. However, at a meeting with CAOTech a couple
of months, Bil quickly noted that most of the current EP1 users don't
have authorization to charge to any cost object. With that in mind,
we decided to still require a cost object for usage tracking purposes
but not verify the authorization. We did check to see if our SAP
implementation could accommodate $0 dollar spending limits but were
told it couldn't.
The requirement for the delivery address was to insure we knew where
to deliver the output. We don't plan to expand our existing delivery
service. For all locations except for those existing large customers
in the Main Group & E19, we'll be using Mail Services for the delivery
function.
-Dave
On Mon, 17 Dec 2001 06:10:04 -0500 Theresa said:
>Hi Rocklyn,
>
>My last understanding with regards to which print jobs would or would not
>be accepted by a print queue was limited to their Kerberos principal being
>validated. Last week's e-mail exchange (or the week's before) was
>highlighting either an Athena list or a listserv list as a possible
>mechanism for identifying "who" may print to which queues. Your note
>suggests more information is required and mentions a web submission
>page. Is this web submission page a general requirement, including, print
>requests originating from SAP R/3?
>
>Thanks,
>Theresa
>
>
>At 05:37 AM 12/17/2001 -0500, you wrote:
>>Hello David et al,
>>
>>Your print job was rejected because I revised our LPRng filter software to
>>detect print submissions from users for whom cost object, building, or
>>room number were not available. As you may know, these should be set by
>>going initially to our job submission web page. They will be retained in
>>our database thereafter and automatically applied to print jobs (whether
>>submitted from the web or via lpr) thereafter. This information can be
>>revised at any time by submitting another job from the job submission web
>page.
>>
>>It was not my intention to actually reject jobs which lacked this
>>information at this time (although we do plan to do this eventually). Our
>>plan is to warn users first to give them ample time to set up their
>>information before we start rejecting jobs. Unfortunately, I forgot to
>>comment out the code that actually rejects the jobs and your printjob was
>>rejected (along with several others) as a result. Please forgive me. I
>>have "toned down" the software so your print jobs should work now.
>>
>>Rocklyn
>>
>>--------
>>At 10:44 PM -0500 12/14/01, David M. Rosenberg wrote:
>>>Earlier this evening (14-Dec-2001), I generated four SAPscript files in PS1
>>>with requests for them to print to queue GLTW. The files (in PS1) have
>>>spool numbers 28284, 28287, 28290, and 28292. I noticed that in SAP all
>>>four of them have the status "ERROR". When you drill down on the error, you
>>>the get status "Incorrect (Error sending data)". When you drill down on
>>>that, you get the log which I have appended after my signature (actually
>>>the file name differs slightly for the four files).
>>>
>>>These are test files to help PrintDel check disk space. I suspect that the
>>>files probably were transferred to pillage. Since they are not real
>>>production files, I don't want them printed, although PrintDel might.
>>>
>>>What do you advise?
>>>
>>>/David M. Rosenberg rosenberg@mit.edu 1-617-253-8054
>>>
>>> SAP spool error log
>>> =====================
>>>
>>>Print request processing log
>>>
>>>The host spool is reporting errors
>>>
>>>Message from host spool:
>>>/usr/bin/lpr: /usr/sap/PS1/D10/data/0010jDDl.PS1: not linked, copying instead
>>>End of host spool message
>>>
>>>Errors occurred processing this print request
>>>
>>>Error during print request output. l_rc = 1
>>>
>>>There may be no printout
>
>
