[2073] in Enterprise Print Delivery Team
Re: 300 DPI v. 600 DPI and test printouts
daemon@ATHENA.MIT.EDU (Theresa M Regan)
Mon Dec 17 12:37:13 2001
Message-Id: <5.0.2.1.2.20011217122522.0bcf1820@hesiod>
Date: Mon, 17 Dec 2001 12:38:09 -0500
To: "Lynne E. Durland" <durland@MIT.EDU>,
"Rocklyn E. Clarke" <rclarke@MIT.EDU>
From: Theresa M Regan <tregan@MIT.EDU>
Cc: printdel@MIT.EDU, r3-print@MIT.EDU
In-Reply-To: <5.0.2.1.2.20011217094745.03e5d6e0@hesiod>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Hi Lynne and Rocklyn,
Thanks... Since all of these are IPM requirements and I do not quite
understand the order in which the pieces need to fall, so, that SAP R/3
print requests will not be rejected if a detail or two are not in sync, is
it possible to accept them and place them in a "to be reviewed" state?
For SAP R/3, these rejected print requests are sitting in SAP R/3 and I am
guessing that the Athena print request is gone and would need to be recreated.
Thanks,
Theresa
At 09:51 AM 12/17/2001 -0500, Lynne E. Durland wrote:
>Theresa,
>
>Yes, there is an account info page, where end users MUST enter a cost
>object and building and room number. What Rocklyn was trying to do was
>validate that the information is there before submitting the jobs. For
>jobs being printed on the IBM printers the userid is used to pull the
>building and room information to put on the separator sheet, so the print
>can be put in the campus mail for delivery. Yes, anyone printing through
>IPM will need to go to the web pages once, before printing the first time,
>go to the account info page, and enter the information. This information
>is used both on the separator sheet and for accounting and reporting.
>
>Hope this helps,
>
>Lynne
>
>At 06:10 AM 12/17/2001, Theresa M Regan wrote:
>>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
>
>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
