[710] in Enterprise Print Delivery Team
Re: retipm and retipm2 have been defined...
daemon@ATHENA.MIT.EDU (Rocklyn Clarke)
Tue Nov 21 19:05:14 2000
Date: Tue, 21 Nov 00 18:59:34 EST
From: Rocklyn Clarke <RCLARKE@MIT.EDU>
To: Theresa M Regan <tregan@MIT.EDU>
cc: r3-admin@MIT.EDU,
Enterprise Printing Delivery Project Team <printdel@MIT.EDU>
In-Reply-To: <200011191452.JAA11289@melbourne-city-street.MIT.EDU>
Message-Id: <001121.190321.EST.RCLARKE@MIT.EDU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Hi Theresa,
Thanks for trying! I agree that we should meet. Perhaps some of the members
of the Enterprise Printing Delivery Team could join you at an upcoming meeting
of the R3-Admin Team. This way we should have most of the right people in the
room. What do you think? How about the 11/27 meeting?
Rocklyn
-------
On Sun, 19 Nov 2000 09:52:09 -0500 you said:
>Hi Rocklyn,
>
>I have created the two output device definitions in SAP R/3 (SF2). And, as
>expected, they have errored; there is no associated spool definition for
>them on the SF2 R/3 server. The exact error is: /usr/bin/lpr: retipm:
>unknown printer and /usr/bin/lpr: retipm2: unknown printer
>
>Usually, the required printer definitions are created and propagated,
>daily, to each R/3 server based on a nightly feed from moira (ae and fiber,
>only) to windsurf.
>
>If a team member from ASST would create printer definitions for "retipm"
>and "retipm2", that would be most helpful.
>
>I am not sure if others are as confused as I am... I would find a meeting
>helpful where we review the existing process for printers, print queues and
>R/3 output device definitions and consider how IPM print queues may
>intersect the existing process and where the process s/b enhanced.
>
>Possibly, it is time to consider any updates to the the following web page:
>
> <http://web.mit.edu/is/help/print/>
>
>and, possibly, include a visual diagram.
>
>Potential areas to include:
>
> New Printer
> IP, hostname, queue names
> discern which servers (ae, fiber, plunder -- should each
>plunder/pillage queue have an associated ae or fiber queue)
> agree on standards for how the data is presented/represented in moira
> flow of data from moira (ae, fiber, plunder/pillage) to R/3 servers
> R/3 output definitions (many choices, in particular, the short name,
>color, duplex settings)
> review current test / confirmation practices
> propagating to other R/3 environments
> problem identification and resolution
>
>
> Existing Printer
> similar to above ...
>
>Thanks,
>Theresa
