[2067] in Enterprise Print Delivery Team
Re: 300 DPI v. 600 DPI and test printouts
daemon@ATHENA.MIT.EDU (Lynne E. Durland)
Mon Dec 17 09:47:37 2001
Message-Id: <5.0.2.1.2.20011217094537.00acf688@hesiod>
Date: Mon, 17 Dec 2001 09:47:11 -0500
To: Theresa M Regan <tregan@MIT.EDU>, "Rocklyn E. Clarke" <rclarke@MIT.EDU>
From: "Lynne E. Durland" <durland@MIT.EDU>
Cc: debbie@MIT.EDU, mprudden@MIT.EDU, Allan Davidson <davidsoa@MIT.EDU>,
"David M. Rosenberg" <Rosenberg@MIT.EDU>, r3-print@MIT.EDU,
printdel@MIT.EDU
In-Reply-To: <5.0.2.1.2.20011217055108.0bcd5e28@hesiod>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Theresa,
No. You are not in the list of userids allowed to print to those
queues. GLTW, GLTE and GLMP have a list of users that was sent by Gill
Emmons. I just double checked the list on pillage and you are not on
it. I will go double check the list in the mail from Gill to be sure I
didn't miss anyone.
Lynne
At 05:54 AM 12/17/2001, Theresa M Regan wrote:
>Hi Rocklyn,
>
>Does this explanation apply to my experiences too?
>
>Thanks,
>Theresa
>
>
>At 05:37 AM 12/17/2001 -0500, Rocklyn E. Clarke 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
>
Lynne E. Durland
Information Systems
Database Services
W91-109
O: 617-258-5857
C: 617-293-8091
H: KB1FEM
"When one door of happiness closes, another opens; but often we look so
long at the closed door that we do not see the one which has been opened
for us."
--Helen Keller
